| View previous topic :: View next topic |
| Author |
Message |
VValdo
Guru
Joined: 08 Jan 2005
Posts: 395
|
 Posted: Mon Jun 19, 2006 4:39 am Post subject: kernel 2.6.17 & nvidia issues? |
 |
|
New Kernel today.
Enable Video For Linux API 1 (DEPRECATED) (VIDEO_V4L1)
Enable Video For Linux API 1 compatible Layer (VIDEO_V4L1_COMPAT)
Enable firmware EDID (FB_FIRMWARE_EDID)
I said Yes (recommended) to all three of these.
Anyone else have subsequent problems when starting up w/nvidia?
(by problems I mean vertical bars on the screen.)
I guess I'll try to narrow down the issue to which is causing it.
W |
|
| Back to top |
|
 |
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Mon Jun 19, 2006 4:56 am Post subject: |
|
|
Those aren't really required for the nvidia driver.
Please post the log from /var/log/Xorg.0.log to see why the X won't start. Without more details, we'll all be just guessing. |
|
| Back to top |
|
|
VValdo
Guru
Joined: 08 Jan 2005
Posts: 395
|
| Posted: Mon Jun 19, 2006 6:32 am Post subject: |
|
|
| Headrush wrote: | Those aren't really required for the nvidia driver.
Please post the log from /var/log/Xorg.0.log to see why the X won't start. Without more details, we'll all be just guessing. |
well, it seems to be something else...
from Xorg.0.log:
| Quote: | (II) XINPUT: Adding extended input device "Mouse0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/util, removing from list!
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x95) [0x487055]
1: /lib/libc.so.6 [0x2b9ee7b9c700]
2: /usr/bin/X(NumMotionEvents+0x12) [0x444352]
3: /usr/bin/X(CreateConnectionBlock+0x51) [0x432221]
4: /usr/bin/X(main+0x8b5) [0x433055]
5: /lib/libc.so.6(__libc_start_main+0xdc) [0x2b9ee7b8a63c]
6: /usr/bin/X(FontFileCompleteXLFD+0x9a) [0x43209a]
Fatal server error:
Caught signal 11. Server aborting
|
The thing is, I just recently (last night) did an update of gcc from 3.4.5 to 4.1.1, and after emerge -e system , today I suddenly discover that gcc -v tells me gcc 3.4.5 is back! Although I'm very sure it was set to 4.11 prior to the emerge -e system.
Well, today I do an emerge -e system again, and lo and behold it goes back to making 3.4.5 default. It's like the gcc-config isn't taking or something. So now I'm rebuilding the entire toolchain a peice at a time with 4.1.1 and spot-checkign to see why it keeps changing back.
THEN I'll rebuild the kernel again and then probably xorg too to see if it fixes everything.
In the meanwhile, it's all ssh cuz my screen is hosed.
W |
|
| Back to top |
|
|
VValdo
Guru
Joined: 08 Jan 2005
Posts: 395
|
|
| Back to top |
|
|
VValdo
Guru
Joined: 08 Jan 2005
Posts: 395
|
| Posted: Mon Jun 19, 2006 10:23 am Post subject: |
|
|
Well, having fixed that gcc-problem, I can now confirm that the kernel is the culprit.
I load w/2.6.16 and X runs fine.
I load w/2.6.17 and X takes a dump as noted above. I re-emerged nvidia-kernel and nvidia-glx w/the new kernel, so that's not the problem...
W |
|
| Back to top |
|
|
Genjix
Apprentice
Joined: 23 Jun 2005
Posts: 163
|
| Posted: Mon Jun 19, 2006 1:47 pm Post subject: |
|
|
| see what happens when you downgrade nvidia-glx and nvidia-kernel. |
|
| Back to top |
|
|
VValdo
Guru
Joined: 08 Jan 2005
Posts: 395
|
| Posted: Mon Jun 19, 2006 11:33 pm Post subject: |
|
|
| Genjix wrote: | | see what happens when you downgrade nvidia-glx and nvidia-kernel. |
Same problem:
| Quote: | # X
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.17-gentoo x86_64
Current Operating System: Linux timberline 2.6.17-gentoo #8 Mon Jun 19 15:41:33 PDT 2006 x86_64
Build Date: 19 June 2006
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 Jun 19 16:31:22 2006
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/util, removing from list!
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Backtrace:
0: X(xf86SigHandler+0x171) [0x47af71]
1: /lib/libc.so.6 [0x2ad3983ab700]
2: X(NumMotionEvents+0x12) [0x440d32]
3: X(CreateConnectionBlock+0x53) [0x4314a3]
4: X(main+0x447) [0x431e67]
5: /lib/libc.so.6(__libc_start_main+0xdc) [0x2ad39839963c]
6: X(FontFileCompleteXLFD+0x9a) [0x43105a]
Fatal server error:
Caught signal 11. Server aborting
Segmentation fault |
Dunno if this helps:
| Quote: | # gdb X
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/X
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.17-gentoo x86_64
Current Operating System: Linux timberline 2.6.17-gentoo #8 Mon Jun 19 15:41:33 PDT 2006 x86_64
Build Date: 19 June 2006
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 Jun 19 16:32:04 2006
(==) Using config file: "/etc/X11/xorg.conf"
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[tcsetpgrp failed in terminal_inferior: Operation not permitted]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/util, removing from list!
Program received signal SIGSEGV, Segmentation fault.
0x0000000000440d32 in NumMotionEvents ()
(gdb) bt
#0 0x0000000000440d32 in NumMotionEvents ()
#1 0x00000000004314a3 in CreateConnectionBlock ()
#2 0x0000000000431e67 in main () |
when I go back to kernel 2.6.16 it works fine.
W |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
