kdm crashes, log included

So_it_goes · November 19, 2007

This started a few weeks ago.

Now I'm regurarly kicked out to my login window.

System:

2007.1 with updates setup with easy-urpmi

2.6.17-16mdv #1 SMP Wed Sep 26 16:10:48 EDT 2007 i686 AMD Athlon 64 X2 Dual Core Processor 5200+ GNU/Linux

This is from the kdm.log file

------------------------------ START LOG ---------------------------

[root@localhost log]# tail -55 kdm.log

(EE) FBDEV(0): FBIOBLANK: Invalid argument

SetGrabKeysState - enabled

(EE) FBDEV(0): FBIOBLANK: Invalid argument

Backtrace:

0: /etc/X11/X(xf86SigHandler+0x85) [0x80c1e15]

1: [0xbfffe420]

2: /etc/X11/X(Dispatch+0x190) [0x8087ba0]

3: /etc/X11/X(main+0x495) [0x806f385]

4: /lib/i686/libc.so.6(__libc_start_main+0xdc) [0xb7d2ed8c]

5: /etc/X11/X(FontFileCompleteXLFD+0x1e9) [0x806e6b1]

Fatal server error:

Caught signal 11. Server aborting

X Window System Version 7.2.0

Release Date: 22 January 2007

X Protocol Version 11, Revision 0, Release 7.2

Build Operating System: UNKNOWN Current Operating System: Linux localhost 2.6.17-16mdv #1 SMP Wed Sep 26 16:10:48 EDT 2007 i686

Build Date: 11 September 2007

Before reporting problems, check http://wiki.x.org

to make sure that you have the latest version.

Module Loader present

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.0.log", Time: Mon Nov 19 10:17:50 2007

(==) Using config file: "/etc/X11/xorg.conf"

(EE) FBDEV(0): FBIOBLANK: Invalid argument

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

(EE) FBDEV(0): FBIOBLANK: Invalid argument

QImage::convertDepth: Image is a null image

QImage::smoothScale: Image is a null image

(EE) FBDEV(0): FBIOBLANK: Invalid argument

------------------------------ END LOG ---------------------------

KDE or mandriva ??

//

Edited November 19, 2007 by So_it_goes

Ixthusdan · November 19, 2007

Could be x or kde updates.

Try launching x without kdm. At the boot loader, hit escape and type "linux init3".

Once you have gotten to a command line login, type "startx" and see if x launches. If x is good, then double check your updates for kde. If x has problems, check for updates for x. Also, be sure you have not inadvertently mixed sources for a different version of Mandriva. You could install gdm if kdm has a problem. "urpmi gdm"

scarecrow · November 19, 2007

It's the xorg settings- most probably.

cat /etc/X11/xorg.conf

(should be fairly long)

So_it_goes · November 20, 2007

Hi

Thanks for the help.

Installed straight from a 2007 Spring CD/DVD, previous problems on another computer was hardware related( now running 2008.0 ).

So no mix of versions.

# init 3

# startx

Is working.

"check your updates for kde" ... "check your updates for x"

The updates are the latest according to the 'update button'( in sync with MCC updates).

gdm is already installed , but running it would not solve the problem.

I'm more intrested in why this happens and tools to trace it.

But thanks for the suggestion.

-----

xorg.conf

The basic root of problems ?? :-)

[root@localhost X11]# cat !$

cat xorg.conf

# File generated by XFdrake (rev 142098)

# **********************************************************************

# Refer to the xorg.conf man page for details about the format of

# this file.

# **********************************************************************

Section "Files"

# font server independent of the X server to render fonts.

FontPath "unix/:-1"

# minimal fonts to allow X to run without xfs

FontPath "/usr/share/fonts/misc:unscaled"

EndSection

Section "Extensions"

Option "Composite"

EndSection

Section "ServerFlags"

#DontZap # disable <Crtl><Alt><BS> (server abort)

#DontZoom # disable <Crtl><Alt><KP_+>/<KP_-> (resolution switching)

AllowMouseOpenFail # allows the server to start up even if the mouse does not work

EndSection

Section "Module"

Load "dbe" # Double-Buffering Extension

Load "v4l" # Video for Linux

Load "extmod"

Load "type1"

Load "freetype"

EndSection

Section "InputDevice"

Identifier "Keyboard1"

Driver "kbd"

Option "XkbModel" "pc105"

Option "XkbLayout" "se"

Option "XkbOptions" "compose:rwin"

EndSection

Section "InputDevice"

Identifier "Mouse1"

Driver "mouse"

Option "Protocol" "ExplorerPS/2"

Option "Device" "/dev/mouse"

EndSection

Section "Monitor"

Identifier "monitor1"

VendorName "Generic"

ModelName "1280x1024 @ 60 Hz"

HorizSync 31.5-64.3

VertRefresh 50-70

# TV fullscreen mode or DVD fullscreen output.

# 768x576 @ 79 Hz, 50 kHz hsync

ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

# 768x576 @ 100 Hz, 61.6 kHz hsync

ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616

EndSection

Section "Device"

Identifier "device1"

BoardName ""

Driver "fbdev"

Option "DPMS"

EndSection

Section "Device"

Identifier "device1"

BoardName ""

Driver "fbdev"

Option "DPMS"

EndSection

Section "Screen"

Identifier "screen1"

Device "device1"

Monitor "monitor1"

DefaultColorDepth 16

Subsection "Display"

Depth 8

Modes "1280x1024" "1024x768" "800x600" "640x480"

EndSubsection

Subsection "Display"

Depth 15

Modes "1280x1024" "1024x768" "800x600" "640x480"

EndSubsection

Subsection "Display"

Depth 16

Modes "1280x1024" "1024x768" "800x600" "640x480"

EndSubsection

Subsection "Display"

Depth 24

Modes "1280x1024" "1024x768" "800x600" "640x480"

EndSubsection

EndSection

Section "ServerLayout"

Identifier "layout1"

InputDevice "Keyboard1" "CoreKeyboard"

InputDevice "Mouse1" "CorePointer"

Screen "screen1"

EndSection

[root@localhost X11]#

//

scarecrow · November 20, 2007

Section "Device"
Identifier "device1"

BoardName ""

Driver "fbdev"

Option "DPMS"

EndSection

Try changing it to

Section "Device"
Identifier "device1"
BoardName ""
Driver "vesa"
Option "DPMS"
EndSection

although there surely is a more suitable driver for your videocard than plain vesa.

Notice also that the above section is included twice, which isn't correct (unless it's your fault at copypasting here). If it's really included twice, remove one of the two references.

There are also other annoyances in your xorg configuration- e.g. there's only the swedish keyboard layout enabled, but not the english one (which is needed quite often), the screen layouts are incomplete (which may cause issues with CRT devices), but let's fix the obvious mistakes first...

Edited November 20, 2007 by scarecrow

So_it_goes · November 22, 2007

Hi

Yes,cut and paste error.

Changed from "fbdev" to "vesa" and restarted.

Have to run it a few days to verify if the problem is still there.

Yes , I'm missing the english keyboard, but I cope with the swedish layout

( not the only user ),

My monitor wasn't recognized , I changed that with the sys hardwarre config tool.

//

scarecrow · November 22, 2007

OK, take your time, but you shouldn't have any real issues with the vesa driver. However, if you mention which videocard you have, we might find a driver which will have a better overall performance, especially when coming to 3D abilities and composite effects.

So_it_goes · November 22, 2007

OK, take your time, but you shouldn't have any real issues with the vesa driver. However, if you mention which videocard you have, we might find a driver which will have a better overall performance, especially when coming to 3D abilities and composite effects.

Hi

As ususal my phrasing is a bit off the mark,.

I meant waiting for the the kde shutdowns, not to check the vesa setup.

Card ?

HD 2400 Pro ATI

//

So_it_goes · November 23, 2007

Hi

Discovered one problem with VESA.

Whenever I switch to a console screen<CTRL><ALT>-F1 and switch back to the GUI screen <CTRL><ALT>-F7.

The colors are messed up really bad.

Is there a reload 'Working environment' ??

//

scarecrow · November 23, 2007

Reloading the desktop/window manager depends on what you're using. If you're using KDE, no, you can't do it on the fly- you must logout and then back in

I believe things will improve by just changing "vesa" to "radeon" and restarting the x-server, although you can certainly do more, including the usage of the proprietary ATi driver (fglrx).

So_it_goes · November 24, 2007

Tried with radeon , didn't work at all.

Works best with fbdev, whatever that is.

OK for me right now.

In HardDrake - hardware,the card shows up as

ATI Technologies In.

Unknown

VGA compatible controler.

So it seems this card isn't open-sourced yet.

Will try with proprietary ATi driver later.

But Ontopic again :

I'll try with these settings(fbdev) to see if kdm crashes.

Thanks for the halp.

//

Sign In

kdm crashes, log included

Recommended Posts

So_it_goes

Link to comment

Share on other sites

Ixthusdan

Link to comment

Share on other sites

scarecrow

Link to comment

Share on other sites

So_it_goes

Link to comment

Share on other sites

scarecrow

Link to comment

Share on other sites

So_it_goes

Link to comment

Share on other sites

scarecrow

Link to comment

Share on other sites

So_it_goes

Link to comment

Share on other sites

So_it_goes

Link to comment

Share on other sites

scarecrow

Link to comment

Share on other sites

So_it_goes

Link to comment

Share on other sites

Join the conversation

Browse

Activity