KDE doesn't start after 9.10 update. Radeon? KDM?

[Chris]

After updating my ATI Radeon Mobility 9000 based laptop from Kubuntu 9.04 to 9.10 I have severe problems with the system. It seems to boot correctly and even to switch to the native resolution (1400x1050) - but it shows the error message

Ubuntu is running in low-graphics mode
Your screen, graphics card, and input device settings could not be detected correctly. You will need to configure these yourself.
Using different xorg.conf files (none, a version with "vesa", a version with "ati" or a version with "ati" and lots of detailed information) did't help

All that I can do is to select the option to go to the text console. Running "startx" there starts an KDE session just as I'd expect it to (compiz is unusable slow and has some big artefacts; disabling it, I can at least work with the system although it's feeling sluggish)

A hint for helping might be this parts of the /var/log/kdm.log:

X.Org X Server 1.6.4
Release Date: 2009-9-27
[...]
(II) [KMS] drm report modesetting isn't supported.
[...]
error setting MTRR (base = 0xd8000000, size = 0x04000000, type = 1) Invalid argument (22)
 ddxSigGiveUp: Closing log
frontend: cannot connect to X server
debconf: unable to initialize frontend: Kde
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
xinit /etc/gdm/failsafeXinit /etc/X11/xorg.conf.failsafe -- /usr/bin/X -br -once -config /etc/X11/xorg.conf.failsafe -logfile /var/log/Xorg.failsafe.log

X.Org X Server 1.6.4
Release Date: 2009-9-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-23-server i686 Ubuntu
Current Operating System: Linux yoda 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
Kernel command line: root=UUID=2f7a1c63-c3e9-4e88-a42c-3cb97715bb6a ro quiet splash locale=de_DE
Build Date: 26 October 2009 05:15:02PM
xorg-server 2:1.6.4-2ubuntu4 (buildd@)
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/var/log/Xorg.failsafe.log", Time: Fri Oct 30 18:56:58 2009
(++) Using config file: "/etc/X11/xorg.conf.failsafe"

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.

 ddxSigGiveUp: Closing log
Warning: Failsafe mode was already attempted within 30 seconds.
Warning: Falling back to gdm to report the issue.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

Fatal server error:
Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.

Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.

 ddxSigGiveUp: Closing log
^M
waiting for X server to shut down
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
2: [0xe45400]
3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0x87ff2e]
4: /usr/lib/xorg/modules//libshadow.so [0x8803e4]
5: /usr/bin/X [0x80c6b3e]
6: /usr/bin/X [0x8111bac]
7: /usr/bin/X [0x811de9c]
8: /usr/bin/X [0x812439c]
9: /usr/bin/X [0x80cf6ce]
10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0x5babb8]
11: /usr/bin/X [0x80c784c]
12: /usr/bin/X [0x816143e]
13: /usr/bin/X [0x80e17f5]
14: /usr/bin/X [0x80cc192]
15: /usr/bin/X [0x814a890]
16: /usr/bin/X [0x817bf49]
17: /usr/bin/X [0x8144516]
18: /usr/lib/xorg/modules/extensions//libglx.so [0x49ed0a]
19: /usr/bin/X(main+0x428) [0x80725a8]
20: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0x1a6b56]
21: /usr/bin/X [0x80719c1]
Saw signal 11. Server aborting.
 ddxSigGiveUp: Closing log
 ddxSigGiveUp: re-raising 11

----------------------------
Note: I just did an " $ ubuntu-bug -p xserver-xorg-core", but it didn't work. The command line showed:
  Warning: The options -p/-P are deprecated, please do not use them. See /usr/bin/ubuntu-bug --help
  ICE default IO error handler doing an exit(), pid = 22686, errno = 11
and the web page that opened said:
  Oops!
  Sorry, something just went wrong in Launchpad.
  We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
  (Error ID: OOPS-1399M3077)

[Chris (mail-christianmayer)]

lspci -vvv:

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 01)
        Subsystem: Acer Incorporated [ALI] Device 001f
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+ DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 66 (2000ns min), Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 3000 [size=256]
        Region 2: Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at d0120000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel modules: radeon, radeonfb

[fpe (f-esser)]

Same problem here, I use a ATI Radeon HD4870 (RV770 chip).
Since I upgraded to Kubuntu 9.10, every about 2-3 startups KDE is not starting, but instead I get this GTK-like message "Ubuntu is running in low-graphics mode".

I found out that if I click on console login, and then do a Ctrl+F2 and Ctrl+F7 again, suddenly KDE starts up magically, running perfectly normal, even with 3D desktop effects.

lspci -vvv
01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4870]
        Subsystem: ATI Technologies Inc Device 0502
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 29
        Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 2: Memory at f7ee0000 (64-bit, non-prefetchable) [size=64K]
        Region 4: I/O ports at c000 [size=256]
        Expansion ROM at f7ec0000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: fglrx_pci
        Kernel modules: fglrx, radeon

[dymo0815 (sins)]

Same problem here. I use a Dell Inspiron 6400. The Problem was after upgrade 8.10 -> 9.04 -> 9.10 at the same day.
At the beginning it works good, but afer some days, the only way to use my installation is boot in recovery mode, reconfigure packages and then I can boot only one time in normal boot.

[dymo0815 (sins)]

I've got a workaround which I can live!
Problem is: Every poweron will start ubuntu in low graphics mode. Sadly I get never ever a chance to work in that mode, cause it drives my Monitor with 125kHz V-Sync and 280Hz H-Sync. Every reboot didn't help.
BUT:
If I bootup for only one time in recovery mode and use "resume normal bootup" (or so...), ubuntu starts in textmode without X. Now I login normally and type "xinit" on the console. The X-Server will startup normal in correct resolution and a xterm window waits for input. I end the session with Ctrl-D and reboot. Now it works fine and every reboot till the next power down.
My notebook is a Dell inspiron 6400 with an internal intel graphics 945GM.
Hope it helps...
Rainer

[Chris (mail-christianmayer)]

Ist it possible that this is actually an starting up problem? How can I debug the upstart mechanism?

[dymo0815 (sins)]

Hi Chris,

I'm not really shure, it seems really strange... When I look in some other bugreports it seem's any people have the same problem like mine. So there is also someone with an workaround using GDM instead of KDM. I will try to test it also, but today I try to startup directly with normal boot and not with the recovery and xinit trick and today it works normal.
I don't really know how I can help you. Do you need some more log files, please tell me which log's you need. I keep my eyes on this bug. I'll inform you also if the bug never occure. OK?

best regards + have a nice weekend,
Rainer

[Felix (apoapo)]

Is my bug a possible duplicate of this one?

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/486702

[Flow (neuville)]

Same problem here (After Upgrade and switch to KDE from Gnome). I also believe it is a "timing" problem in the upstart mechanisms - but I do not know how to debug this properly.

[dymo0815 (sins)]

Hi Chris,

since Sunday (22th) all cold starts/reboot was now normally without any problems. Maybe a bugfix last Week repared it. So my Problem seem's to be fixed.

Thanks,
Rainer

[Chris (mail-christianmayer)]

Doing all updates the system is offering didn't change anything. :(

So my system is still anoying me. I can only work with it by "exiting to the console" and running the command "sudo initctl restart kdm" there. This gives me a normal desktop as expected - but only after manual interaction.

If that's an upstart problem (what I'm really thinking now), how can I debug it? And what's the right package to add to this bug report?

[samael (samuele)]

Same problem here. Can't report details now as I don't have the PC with me. Let me know if you need some more infos.

[Chris (mail-christianmayer)]

One (some?) of the last updates seem to have improved the situation a lot. But I still get sometimes the bad behaviour described above. (probably went from 1 in 10 to 9 in 10 normal start ups)

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[Chris (mail-christianmayer)]

I guess this was solved with 10.04 - at least I don't remember any
problems at the end any more. I used that box till last December and
didn't update to 10.10 as the new box was already on the horizont.