[SOLVED] Can't load desktop after updates

JosephS · 10-08-2011, 11:57 PM

I installed a number of updates yesterday. Today I rebooted my computer and can't load the desktop. All I get is a blue screen with a white patch in the middle where my login name and password should be. Does anyone know of a problem with any of the last updates and how I would fix this?

Thanks

cynwulf · 10-09-2011, 04:22 AM

Have a look at /var/log/dpkg.log to see what was upgraded.

Also grep /var/log/Xorg.0.log for errors and warnings.

kasl33 · 10-09-2011, 12:38 PM

Try manually starting the xserver by following these steps and see if it helps:

1. Reboot
2. When the bootloader comes up, press the "e" key while highlighting Debian
3. When it brings up options to be edited, select the kernel and press "e" again
4. Now, at the end of the kernel line, simply add the number "3"
5. Press Enter and then press the letter "b"

(none of the above should have quotes - I put them there so they would stand out)

Eventually, the computer will take you to a CLI login screen - you will now be in runlevel 3.

Login with your username and password and then type (without quotes) startx

Do you now get a GUI?

If so, then my guess is that the GDM is messed up.

TobiSGD · 10-09-2011, 12:46 PM

This will not work, on Debian and most derived distros the default runlevel is 2 and the runlevels 2-5 simply are the same.

kasl33 · 10-09-2011, 01:01 PM

Quote:

Originally Posted by TobiSGD

This will not work, on Debian and most derived distros the default runlevel is 2 and the runlevels 2-5 simply are the same.

Interesting fact - and verified.

I believe that in this case, we can use runlevel 1 instead of 3 - 1 being single-user mode... I haven't tried this one so it's a logical guess.

cynwulf · 10-09-2011, 01:24 PM

There were a lot of updates yesterday apparently due to the 6.0.3 point release. Have a look at this thread on the mepis forums: http://forum.mepiscommunity.org/view...p?f=84&t=31765

jens · 10-10-2011, 09:01 AM

Quote:

Originally Posted by caravel

There were a lot of updates yesterday apparently due to the 6.0.3 point release. Have a look at this thread on the mepis forums: http://forum.mepiscommunity.org/view...p?f=84&t=31765

.
"#chmod 777 /var/tmp" (as posted in that thread) doesn't set the sticky bit (-t or 1xxx).

JosephS · 10-10-2011, 11:53 AM

Quote:

caravel
Have a look at /var/log/dpkg.log to see what was upgraded.
Also grep /var/log/Xorg.0.log for errors and warnings.

Code:

/var/log/dpkg.log
I checked the packages that were updated and these are the
ones I found:
python-uno 1:3.2.1-11+squeeze4
python-central 0.6.16+nmu1
base-files 6.0squeeze3
hicolor-icon-theme 0.12-1
linux-base 2.6.32-38
linux-image-2.6.32-5-686 2.6.32-38
aptitude 0.6.3-3.2+squeeze1
openssh-client 1:5.5p1-6+squeeze1
openssl 0.9.8o-4squeeze3
foo2zjs 20090908dfsg-5.1+squeeze0
grub-common 1.98+20100804-14+squeeze1
grub-pc 1.98+20100804-14+squeeze1
policykit-1 0.96-4+squeeze1
update-inetd 4.38+nmu1+squeeze1
usbutils 0.87-5squeeze1
akonadi-server 1.3.1-3+squeeze1

Code:

/var/log/Xorg.0.log
(II) LoadModule: "nv"
(II) Loading /usr/lib/xorg/modules/drivers/nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 2.1.17
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
(II) Primary Device is: PCI 01@00:00:0
(--) NV: Found NVIDIA Vanta at 01@00:00:0
(EE) NV: Kernel modesetting driver in use, refusing to load
(EE) No devices detected.

Fatal server error:
no screens found

I tried to reinstall driver: modprobe nv_drv.so
It told me that the driver could not be found. It is located in /usr/lib/
xorg/modules/drivers. How do I get linux to load this driver?

I read the article at http://forum.mepiscommunity.org/view...p?f=84&t=31765
and tried a few things:
#chmod 777 /var/tmp

Xorg -configure

I don't know what else to do. Appreciate advice.

Thanks

TobiSGD · 10-10-2011, 12:02 PM

Sere seems to be a different driver (most likely nouveau) claiming that device at boot time. Add nouveau to the file /etc/modprobe.d/blacklist.conf and reboot.

jens · 10-10-2011, 12:03 PM

Quote:

Originally Posted by JosephS

Code:

/var/log/dpkg.log
I checked the packages that were updated and these are the
ones I found:
python-uno 1:3.2.1-11+squeeze4
python-central 0.6.16+nmu1
base-files 6.0squeeze3
hicolor-icon-theme 0.12-1
linux-base 2.6.32-38
linux-image-2.6.32-5-686 2.6.32-38
aptitude 0.6.3-3.2+squeeze1
openssh-client 1:5.5p1-6+squeeze1
openssl 0.9.8o-4squeeze3
foo2zjs 20090908dfsg-5.1+squeeze0
grub-common 1.98+20100804-14+squeeze1
grub-pc 1.98+20100804-14+squeeze1
policykit-1 0.96-4+squeeze1
update-inetd 4.38+nmu1+squeeze1
usbutils 0.87-5squeeze1
akonadi-server 1.3.1-3+squeeze1

Code:

/var/log/Xorg.0.log
(II) LoadModule: "nv"
(II) Loading /usr/lib/xorg/modules/drivers/nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
        compiled for 1.7.7, module version = 2.1.17
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
(II) Primary Device is: PCI 01@00:00:0
(--) NV: Found NVIDIA Vanta at 01@00:00:0
(EE) NV: Kernel modesetting driver in use, refusing to load
(EE) No devices detected.

Fatal server error:
no screens found

I tried to reinstall driver: modprobe nv_drv.so
It told me that the driver could not be found. It is located in /usr/lib/
xorg/modules/drivers. How do I get linux to load this driver?

I read the article at http://forum.mepiscommunity.org/view...p?f=84&t=31765
and tried a few things:
#chmod 777 /var/tmp

Xorg -configure

I don't know what else to do. Appreciate advice.

Thanks

Does it work in root (use xinit)?

Quote:

How do I get linux to load this driver?

modprobe [your-driver] should at least give an error if it exists.

Quote:

Xorg -configure

This will only create an xorg.conf in your current location.

Quote:

I tried to reinstall driver: modprobe nv_drv.so

modprobe will only start the driver, it doesn't install anything.

You could consider using the nvidia driver from Nvidia

JosephS · 10-11-2011, 11:40 AM

Quote:

TobiSGD
There seems to be a different driver (most likely nouveau) claiming that device at boot time. Add nouveau to the file /etc/modprobe.d/bblacklist.conf and reboot.

Thanks I didn't think of that. I also edited a line in /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="quiet". I changed quiet to nomodeset. I found this in another post:
http://www.linuxquestions.org/questi...nstall-834100/
I don't know if that was necessary, but my Desktop is good now.