blank screen, no ttys, no mouse on boot after last update

Bug #480970 reported by josvanr
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

Have been running kubuntu 9.10 with kde and gnome (on laptop
packard bell bg46). After running the last update and
rebooting, I see the blue kubuntu logo with progress bar, but
then only a blank screen. I tried to switch to a text terminal
(alt-fn) but that doesn't work. When I choose the previous
kernel in grub (2.6.31-14-generic) I see the same. Using the
kernel before that to start up (2.6.27-14-generic) kubuntu
starts in a low graphics mode (hence I can write this mail).
Then kdm start up and I can start kde or gnome.
But still I have no mouse, but my wacom graphics tablet does
work. What is the way to proceed in a case like this? Is there
some way to repeat the update (in case something went wrong?)

Here I some error messages I see when kubuntu is saying it is
starting in low graphics mode:

(EE) intel(0): [drm] Failed to open DRM device for: No such file or directory
(EE) intel(0): [drm] Failed to open DRM master
(EE) intel(0): [drm] Failed to initialize kernel memory manager
(EE) SynPS/2 Synaptics touch pad: Unable to query/initialize Synaptics hardware
(EE) PreInt failed for input device "SynPS/2 Synaptics TouchPad"
(EE) config/hal: New input device request failed (8 )

Have been running kubuntu 9.10 with kde and gnome (on laptop
packard bell bg46). After running the last update and
rebooting, I see the blue kubuntu logo with progress bar, but
then only a blank screen. I tried to switch to a text terminal
(alt-fn) but that doesn't work. When I choose the previous
kernel in grub (2.6.31-14-generic) I see the same. Using the
kernel before that to start up (2.6.27-14-generic) kubuntu
starts in a low graphics mode (hence I can write this mail).
Then kdm start up and I can start kde or gnome.
But still I have no mouse, but my wacom graphics tablet does
work. What is the way to proceed in a case like this? Is there
some way to repeat the update (in case something went wrong?)

Here are some error messages I see when kubuntu is saying it is
starting in low graphics mode:

(EE) intel(0): [drm] Failed to open DRM device for: No such file or directory
(EE) intel(0): [drm] Failed to open DRM master
(EE) intel(0): [drm] Failed to initialize kernel memory manager
(EE) SynPS/2 Synaptics touch pad: Unable to query/initialize Synaptics hardware
(EE) PreInt failed for input device "SynPS/2 Synaptics TouchPad"
(EE) config/hal: New input device request failed (8 )

My graphics card is Intel GM965/GL960

josvanr

Revision history for this message
josvanr (josvanr) wrote :

hello, I just tried the latest (9.10) live cd. This boots up the system with no trouble...

Revision history for this message
Oscar Andreis (oscarand77) wrote :

I have the same problem too. My karmic worked well for a couple of days after the last software update. Suddently I've the "Ubuntu running in low-graphics mode" error at startup, and the very strange thing is that if I clink OK and than select "Run in console mode", th boot continue correctly and I use Kubuntu without any problem...

Revision history for this message
Gary Scott (garygsscott) wrote :

Same problem for me on Samsung NC-10

Revision history for this message
R4v3n (philippe-raven) wrote :

Same problem with Dell Lattitude E4300 just after the X.org upgrade from last update. Can't do anything, can't use ubuntu.

Revision history for this message
Gerald Senarclens de Grancy (trainer) wrote :

I have the same issue on a Toshiba Satellite U400. It uses an Intel 4500MHT graphics chip. The problem occurs since restarting after the update to kernel 2.6.31-15-generic (and whatever came along with that update), but is still there for kernel 2.6.31-16-generic. Booting in the safe mode doesn't work either. Kernel 2.6.28 boots in low-graphics mode but it's horribly slow and the mouse doesn't work. The error messages in the log are
184:(EE) intel(0): [drm] Failed to open DRM device for : No such file or directory
185:(EE) intel(0): Failed to become DRM master.
391:(EE) intel(0): Failed to initialize kernel memory manager
532:(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
533:(EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
535:(EE) config/hal: NewInputDeviceRequest failed (8)

The failsafe error log has the following output:
1789:(EE) config/hal: couldn't initialise context: unknown error (null)
1867:(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
1868:(EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
1870:(EE) config/hal: NewInputDeviceRequest failed (8)

The same issue occurs also on my work laptop which uses an Intel graphics device as well, also since rebooting after the update to Kernel 2.6.31-15.

Revision history for this message
jconstable (jconstable007) wrote :

same issue here, how ever after about the third reboot, I do get a message pop up about "running in low graphics mode" and click on "ok" (i think) another screen comes up with a couple of different selections
-run in low graphics mode this one time
-start troubleshooting...
and some others.
upon selecting run in low graphics mode
the system goes to a terminal login screen.
after logging in, I type "startx" and all things are normal.
Dell Latitude CPX-j with ATI Rage Mobility graphics.
if you need a log to review, please let me know which one. I do have a Xorg.O.log but it is something like 30k.

here is part of it relating to the graphics driver.

II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
 compiled for 1.6.4, module version = 6.12.99
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "mach64"
(II) Loading /usr/lib/xorg/modules/drivers//mach64_drv.so
(II) Module mach64: vendor="X.Org Foundation"
 compiled for 1.6.3, module version = 6.8.2
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
 compiled for 1.6.3, module version = 2.2.1
 Module class: X.Org Video Driver
 ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
 compiled for 1.6.0, module version = 0.4.0
 ABI class: X.Org Video Driver, version 5.0
(II) MACH64: Driver for ATI Mach64 chipsets
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 01@00:00:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"

Revision history for this message
Gary Scott (garygsscott) wrote :

Interesting, this problem seems to be related to using Kubuntu/KDE in my case (on the Samsung NC10) as issuing the following statement :-

sudo dpkg-reconfigure gdm

and selecting gdm as the default desktop for ubuntu and after reboot using "gnome" session from the login drop-down (instead of kde) solved the issue.

I did have some problems with my synaptics touchpad after this (e.g. not working) but an update to the latest kernel 2.6.31-16 solved this also.

Hopefully this may help some others and point others also in the direction of what the issue may be.

Cheers,
Gary

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.