Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
issues with gentoo-sources-2.6.2X, Xorg and Nvidia
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Tue May 15, 2007 12:08 pm    Post subject: issues with gentoo-sources-2.6.2X, Xorg and Nvidia Reply with quote

Hello,

I have been running gentoo-sources-2.6.19-r5 (genkernel compile) for a few months now, and when 2.6.20-r7 came down, I decided to compile that (also with genkernel) just to keep on top of the stable kernel builds. Everything went fine until it came time to start X again.

Every time X was started (either with startx or xdm) It would end up self-terminating with a "Caught signal 11" message. If I reboot and go back to 2.6.19-r5, it works fine.

I tested 2.6.20-r8 (genkernel) and 2.6.21 (manual compile) and they both have the same problems. I have no idea why X refuses to run once the 2.6.2X kernels are booted.

Just for reference, I have an AMD 64 3200+, Nvidia 7600 GS card (Nvidia Driver Version 1.0-9755) and Xorg version 7.2.0. Any other information or outputs required can be provided.

Any help with this would be much appreciated.
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5929

PostPosted: Tue May 15, 2007 12:12 pm    Post subject: Reply with quote

any kernel parameters?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Tue May 15, 2007 12:20 pm    Post subject: Reply with quote

DaggyStyle wrote:
any kernel parameters?


I'm not quite sure what you mean.
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Tue May 15, 2007 2:33 pm    Post subject: Reply with quote

did you recompile nvidia-drivers for each kernel?
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Tue May 15, 2007 2:37 pm    Post subject: Reply with quote

Yes. After compiling the 2.6.21 kernel I also did an emerge -e just for good measure.
Back to top
View user's profile Send private message
donald7
Tux's lil' helper
Tux's lil' helper


Joined: 03 Mar 2007
Posts: 136

PostPosted: Tue May 15, 2007 5:58 pm    Post subject: Reply with quote

you need to redo an emerge nvidia-drivers

see http://www.gentoo.org/doc/en/nvidia-guide.xml

donald
_________________
Linux Counter #433775

Visitez et contribuez au site gnulinux.fr
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Tue May 15, 2007 6:41 pm    Post subject: Reply with quote

I'll give that another try when I get home tonight.
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Wed May 16, 2007 1:21 pm    Post subject: Reply with quote

After booting into the 2.6.21 kernel, I re-emerged the Nvidia driver, rmmod'd the existing one, and then modprobe'd the new one in. Upon starting X I get the following still:

Quote:
Fatal server error:
Caught signal 11. Server aborting

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
Couldnt get a file descriptor referring to the console


Any ideas what could be causing this outside of re-emerging the nvidia driver?
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5929

PostPosted: Wed May 16, 2007 7:45 pm    Post subject: Reply with quote

scumm_boy wrote:
DaggyStyle wrote:
any kernel parameters?


I'm not quite sure what you mean.


quess not, can you post your grub.conf?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Wed May 16, 2007 7:49 pm    Post subject: Reply with quote

grub.conf wrote:
default 0
fallback 1
timeout 10
splashimage=(hd0,0)/grub/splash.xpm.gz

title=Gentoo Linux 2.6.21
kernel (hd0,0)/vmlinuz root=/dev/hda3

title=Gentoo Linux 2.6.19
root (hd0,0)
kernel /kernel-genkernel-x86_64-2.6.19-gentoo-r5 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3
initrd /initramfs-genkernel-x86_64-2.6.19-gentoo-r5
Back to top
View user's profile Send private message
quantumsummers
Retired Dev
Retired Dev


Joined: 24 Sep 2006
Posts: 103
Location: Earth

PostPosted: Wed May 16, 2007 10:02 pm    Post subject: Reply with quote

Hey there scumm-boy,

I had some similar issues on a similar platform after kernel & X11 upgrades & rolling nvidia-drivers back to version nvidia-drivers-1.0.8776-r1 worked for me.

NOW, this is a NASTY workaround, but I simply needed a working machine!

Given some time I will figure out why this happened & if anyone can give more useful info I would be very pleased.

Cheers,

QuantumSummers

EDIT: almost forgot: I had to remove all mention of framebuffer/splash from kernel config as well. Which is also _no_good_.
_________________
Summers

"...there are no rules here -- we're trying to accomplish something."
- Thomas A. Edison
Back to top
View user's profile Send private message
scumm_boy
n00b
n00b


Joined: 08 Jan 2007
Posts: 30

PostPosted: Wed May 16, 2007 10:14 pm    Post subject: Reply with quote

I might try rolling back to that Nvidia driver version and see if that makes a difference. Thank you for the potential work around!
Back to top
View user's profile Send private message
DaggyStyle
Watchman
Watchman


Joined: 22 Mar 2006
Posts: 5929

PostPosted: Wed May 16, 2007 11:17 pm    Post subject: Reply with quote

have you tried not using genkernel?
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
Back to top
View user's profile Send private message
depu
n00b
n00b


Joined: 05 Dec 2006
Posts: 63

PostPosted: Sat May 19, 2007 2:35 pm    Post subject: Reply with quote

maybe posting your xorg.conf and the entire error message would be more useful


Edit:
Looked around the forums
https://forums.gentoo.org/viewtopic-t-549617-highlight-nvidia+drivers+amd64.html
Back to top
View user's profile Send private message
JanErik
Guru
Guru


Joined: 28 Oct 2002
Posts: 488
Location: Finland

PostPosted: Tue May 22, 2007 1:49 pm    Post subject: Reply with quote

I have the same problem after upgrading to 2.6.21-r1 from 2.6.20-r1, I get the nvidia logo and then:

Code:
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux conroe 2.6.21-gentoo-r1 #1 SMP PREEMPT Tue May 22 09:59:08 EEST 2007 x86_64
Build Date: 23 April 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: Tue May 22 16:40:19 2007
(==) Using config file: "/etc/X11/xorg.conf"

(II) Module already built-in
(EE) NVIDIA(0): Failed to obtain a shared memory identifier.
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
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

Backtrace:
0: X(xf86SigHandler+0x6d) [0x48544e]
1: /lib/libc.so.6 [0x3bc702f650]
2: /usr/lib64/xorg/modules//drivers/nvidia_drv.so [0x2b3172a2ac0b]

Fatal server error:
Caught signal 11.  Server aborting

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.


nvidia-drivers is version 1.0.9755-r1 and the module loads without problems, X just doesn't like it.
7600 GS card here aswell, on a Core 2 Duo.
Back to top
View user's profile Send private message
JanErik
Guru
Guru


Joined: 28 Oct 2002
Posts: 488
Location: Finland

PostPosted: Mon May 28, 2007 2:34 pm    Post subject: Reply with quote

Installed gentoo-sources 2.6.21-r2 and it works fine.
Back to top
View user's profile Send private message
rtomek
Apprentice
Apprentice


Joined: 05 Jan 2007
Posts: 210
Location: Chicago

PostPosted: Wed May 30, 2007 5:31 pm    Post subject: Reply with quote

All you have to do is disable paravirtualization support in the kernel and nvidia-drivers will compile.
Back to top
View user's profile Send private message
quantumsummers
Retired Dev
Retired Dev


Joined: 24 Sep 2006
Posts: 103
Location: Earth

PostPosted: Thu May 31, 2007 3:48 pm    Post subject: Why paravirtualization Reply with quote

So the question now becomes: Why must one disable kernel paravirtualization for the latest nvidia driver to compile?

In addition, is it this kernel parameter: CONFIG_KVM_AMD=y

Finally, how did you come by this information?

Thanks,

QuantumSummers
_________________
Summers

"...there are no rules here -- we're trying to accomplish something."
- Thomas A. Edison
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Page 1 of 1

 
Jump to:  
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