You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Monday, August 25th 2008, 11:23pm

KDE 4.1 Crash on Ubuntu Hardy Sony Vaio laptop with Intel i810 Graphics

[attach]xorg.conf.txt[/attach]Hi guys,

Please note, this is a cross-posting from the Hardware forum - I just saw the Graphics forum, and maybe it's more appropriate here.

I did a quick search here, and have found nothing.

I've been running KDE3 within Hardy Heron Ubuntu for some time. I had initial problems getting it to correctly detect that my laptop (an old Sony Vaio PCG-R505JSP had 1024x768 at 24bpp capability, but with some searching found a solution to that.

Just today, I decided to switch to KDE4.1, having read some of the rave reviews. Unfortunately, KDE4.1 crashes on login, an returns to the login kdm prompt. KDE3 is still running just fine (I'm posting this from KDE3, 1024x768 with no problem).

The syslog from the time of the crash contains:

25/08/08 13:01:33 ubuntu kernel [41854.741359] Xorg[5505]: segfault at 000001a4 eip 0818faaa esp bfb2d5d0 error 4
25/08/08 13:01:34 ubuntu console-kit-daemon[5165] WARNING: Unable to activate console: No such device or address
25/08/08 13:01:34 ubuntu kdm[5463] X server for display :0 terminated unexpectedly
25/08/08 13:01:43 ubuntu kdm_greet[5801] Cannot open default user face
25/08/08 13:02:17 ubuntu console-kit-daemon[5165] WARNING: Unable to activate console: No such device or address
25/08/08 13:02:17 ubuntu kdm[5463] X server for display :0 terminated unexpectedly
25/08/08 13:02:22 ubuntu kdm_greet[5999] Cannot open default user face
25/08/08 13:03:21 ubuntu NetworkManager <info> Updating allowed wireless network lists.

The Xorg log from the same time contains:

9: /usr/bin/X(compPaintWindowBackground+0x6d) [0x810530d]
10: /usr/bin/X(miWindowExposures+0xf2) [0x8121282]
11: /usr/bin/X [0x80db995]
12: /usr/bin/X(miHandleValidateExposures+0x78) [0x81373b8]
13: /usr/bin/X(MapWindow+0x3e7) [0x80790d7]
14: /usr/bin/X(ProcMapWindow+0x66) [0x808d0d6]
15: /usr/bin/X [0x815076e]
16: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
17: /usr/bin/X(main+0x48b) [0x807471b]
18: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7c9d450]
19: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting

(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(II) I810(0): xf86UnbindGARTMemory: unbind key 3

The relevant portion of the kdm log appears to be:

X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu9.2)
Current Operating System: Linux ubuntu 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686
Build Date: 13 June 2008 01:08:21AM

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: Sun Aug 24 23:44:18 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ddc" already built-in
(II) Module "ramdac" already built-in
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
Atom 4, CARD32 4, unsigned long 4
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
kdmgreet(5598) KLocalePrivate::initEncoding: Cannot resolve system encoding, defaulting to ISO 8859-1.
Link points to "/tmp/kde-root"

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7f64420]
2: /usr/bin/X(Xfree+0x21) [0x81b89b1]
3: /usr/lib/xorg/modules//libxaa.so [0xb7a9f2ed]
4: /usr/bin/X [0x816fe7f]
5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7b64e6a]
6: /usr/bin/X [0x814572a]
7: /usr/bin/X(dixChangeGC+0xaad) [0x809cb8d]
8: /usr/lib/xorg/modules//libxaa.so [0xb7ae397a]
9: /usr/lib/xorg/modules//libxaa.so [0xb7ae3dbf]
10: /usr/bin/X [0x81708af]
11: /usr/bin/X(compPaintWindowBackground+0x6d) [0x810530d]
12: /usr/bin/X(miWindowExposures+0xf2) [0x8121282]
13: /usr/bin/X [0x80db995]
14: /usr/bin/X(miHandleValidateExposures+0x78) [0x81373b8]
15: /usr/bin/X(miSlideAndSizeWindow+0xd74) [0x8138d44]
16: /usr/bin/X(compResizeWindow+0xac) [0x810611c]
17: /usr/bin/X(ConfigureWindow+0xbcb) [0x807a43b]
18: /usr/bin/X(ProcConfigureWindow+0x9d) [0x808ceed]
19: /usr/bin/X [0x815076e]
20: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
21: /usr/bin/X(main+0x48b) [0x807471b]
22: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7cfc450]
23: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting


Can anybody offer any advice here?

Is this looking like a kde4.1 problem or an Xorg problem?

Is there a newer Xorg driver for i810 that I can try?

Any and all help gratefully accepted. For the moment, I guess I'm stuck with KDE3

Thanks in advance,
Paul.

This post has been edited 1 times, last edit by "pjc007" (Sep 1st 2008, 2:24pm)


nicolaary

Beginner

Posts: 4

Location: Shanghai, China

  • Send private message

2

Saturday, August 30th 2008, 1:05pm

It could be helpful if you also add here your xorg.conf ;)

3

Monday, September 1st 2008, 2:25pm

It could be helpful if you also add here your xorg.conf ;)


Hi,

I've attached my xorg.conf (as xorg.conf.txt) to the original post.

Hope somebody can now help, as I really would love to try KDE4.1!

-PJC

4

Saturday, September 6th 2008, 11:56am

Now I'm completely confused...

So, having not gotten any useful feedback here, I decided to try recovery mode and reset my X11 settings completely.

Bizarrely, this is working fine, EXCEPT I'm now back to the 800x600 display size that I had to 'tweak' xorg.conf to get around in the first place.

The 'working' (but not really) xorg.conf is attached.

Please - any help is greatly appreciated - now I've actually *SEEN* kde4, I more than ever want to run it permanently, but there's no way I can do that at this dumb reduced resolution.

Please see original post for details of the initial crash, OR if anybody knows how to make kde4.1 correctly work with the onboard i815 in 1024x768 resolution, either using the i810 or intel driver, any help greatly appreciated!!

-paul.
pjc007 has attached the following file:
  • xorg.conf.txt (1.52 kB - 10 times downloaded - latest: Sep 27th 2009, 12:44pm)

5

Friday, September 12th 2008, 2:11pm

Still confused, but partially working...

Hi guys,

someone over in the kubuntuforums sent me an xorg.conf using the intel driver rather than the i810, and I've done some experimentation with that, as well as my working KDE 3.5 xorg.conf, and made *some* progress.

Basically, I now have a working system with KDE 4.1 at 1024x768, BUT only at 16bpp.

I can only assume that KDE 4.1 requires DRI, because having done some research, I find the Intel driver doesn't support DRI on the i815 at 24bpp, only 16bpp and below. An excerpt from the man page isn't altogether helpful, and just says:

For the i810/i815 other depths support the True‐
Color and DirectColor visuals. For the i830M and later, only the True‐
Color visual is supported for depths greater than 8. The driver sup‐
ports hardware accelerated 3D via the Direct Rendering Infrastructure
(DRI), but only in depth 16 for the i810/i815

Does anybody know if there's a solution to this that will let me run at 24bpp?

I've attached my working (16bpp) xorg.conf - the only changes I've tried so far are to switch the depth 16 to be depth 24, and to explicitly set Option "DRI" "Disable", but both of these have the same issue, in that the logon splashscreen is fine, but logging in causes the X-server to crash with the errors as shown in Post #1.

Thanks again,
Paul.
pjc007 has attached the following file:

Similar threads