Member Avatar for grumpysnake

my system fails to boot through to graphical interface.
near the end, it reverts to text, making me log in as single user.
what do i type in at the prompt to remedy the problem.
i am using 10.1 community.

  • 2 Contributors
  • 2 Replies
  • 70 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by grumpysnake

Dani AI

Generated

Good result from the thread: pointed the right direction and confirmed a manual graphical session succeeds, so the immediate task is to make the graphical login start reliably at boot and to capture any errors that prevented it from coming up automatically.

Quick, practical checks (run from a shell as root or with sudo):

  • Inspect the X server log for errors (look for lines marked (EE) or (WW)) in the usual X log location to see why the display manager might have failed.
  • Check the system and display-manager logs (the distro stores these under /var/log); they often show service startup failures or permission problems.
  • Confirm /tmp permissions and the ownership of the user's X authority file — incorrect permissions on /tmp or a wrong-owned .Xauthority will stop automatic logins or the DM from launching.
  • Verify that the correct video driver/kernel module is present (look at PCI device info and kernel messages) in case the DM is aborting when it cannot initialize the graphics device.

If the logs show X configuration errors, use the distribution-config tool to regenerate or adjust the X configuration and back up any configuration files before editing. To make the fix permanent, enable the display-manager service for the graphical boot target using your distro's boot-service tool (Mandrake/Mandriva exposes this in its control center or via the SysV runlevel service tools).

Further reading / troubleshooting references:

Member Avatar for dontcare

my system fails to boot through to graphical interface.
near the end, it reverts to text, making me log in as single user.
what do i type in at the prompt to remedy the problem.
i am using 10.1 community.

Did you try startx or X under root, your init runlevel might be set to 3. If startx or X does not load you need to configure X using the command xf86config. If startx works then you need to edit /etc/inittab, using a text editor. Set the runlevel to the number containing your session managers.

Member Avatar for grumpysnake

startx did the job just fine.
many thanks for the info, may require youre advice again.

cranky python.esq :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.