View previous topic :: View next topic |
Author |
Message |
lonblu Tux's lil' helper
Joined: 28 Mar 2004 Posts: 80 Location: Treviso
|
Posted: Mon Jun 28, 2004 1:09 pm Post subject: nvidia doesn't work with kernel 2.6.7 |
|
|
Actually I'm happily using 2.6.5kernel with nvidia-kernel 4496
I compiled the latest gentoo-dev-sources 2.6.7-r3 without the fstack option (4-8kb) but my nvidia card doesn't work with the nvidia-kernel (4496 or 5535)
This is what I get on XFree.0.log when starting kdm
Code: |
(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.6
(**) NVIDIA(0): Depth 16, (--) framebuffer bpp 16
(==) NVIDIA(0): RGB weight 565
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo"
(--) NVIDIA(0): Linear framebuffer at 0xD0000000
(--) NVIDIA(0): MMIO registers at 0xDC000000
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.
|
this is /var/log/messages
Code: |
Jun 28 13:45:35 tux 0: nvidia: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004
Jun 28 13:46:12 tux 0: NVRM: client supports wrong rm api version!!
Jun 28 13:46:12 tux 0: NVRM: aborting to avoid catastrophe!
Jun 28 13:46:13 tux kdm: :0[8346]: IO Error in XOpenDisplay
Jun 28 13:46:13 tux kdm[8339]: X server for display :0 terminated unexpectedly
Jun 28 13:46:13 tux kdm[8339]: Display :0 cannot be opened
Jun 28 13:46:13 tux kdm[8339]: Unable to fire up local display :0; disabling.
|
Only "vesa" is working
"nv" is not workging in any case becouse I use a lcd 19" monitor (do you know some tricks or options about this?): X is loaded but I can only see a green screen _________________ Pentium 3 866hz/GI, 520MBRam, 2xMaxtor ATA133/7200 80-120GB con Maxtor-Promise ATA133 Controller, Elsa Gloria III (Nvidia quadro2pro), Scheda TV PinnaclePCTV , waitec8/1 DVD+-rw, ARTEC32x12x48x kernel-2.6.7-gentoo-r11(,sony LCDTFT19" |
|
Back to top |
|
|
the_sphynx Apprentice
Joined: 19 May 2004 Posts: 156 Location: Thornton, CO
|
Posted: Mon Jun 28, 2004 3:07 pm Post subject: |
|
|
There is a post on the forums that discusses this issue as well as the "invalid module format" error that most people are getting. Sorry I don't have a link to it, but it really isn't that hard to find. If I remember right it is a bit of a task to fix. _________________ Folding@Home User 285941 |
|
Back to top |
|
|
theDreamer Tux's lil' helper
Joined: 20 Oct 2003 Posts: 118
|
Posted: Mon Jun 28, 2004 3:22 pm Post subject: solution |
|
|
simple solution:
Code: | ACCEPT_KEYWORDS=~x86 emerge -v nvidia-kernel nvidia-glx |
this is a newer version of nvidia driver which works better with 2.6.6+ (unless you have dual cpu).. _________________ Cheers,
Nir Dremer
www.dremer.org |
|
Back to top |
|
|
the_sphynx Apprentice
Joined: 19 May 2004 Posts: 156 Location: Thornton, CO
|
Posted: Mon Jun 28, 2004 3:29 pm Post subject: |
|
|
I didn't realize that it was that easy, although it had been a few weeks since I had really started looking for this problem. _________________ Folding@Home User 285941 |
|
Back to top |
|
|
lonblu Tux's lil' helper
Joined: 28 Mar 2004 Posts: 80 Location: Treviso
|
Posted: Tue Jun 29, 2004 9:09 am Post subject: |
|
|
thank I think it was becouse I wasn't upgrading nvidia-glx but only nvidia-kernel
I'll try
thanks _________________ Pentium 3 866hz/GI, 520MBRam, 2xMaxtor ATA133/7200 80-120GB con Maxtor-Promise ATA133 Controller, Elsa Gloria III (Nvidia quadro2pro), Scheda TV PinnaclePCTV , waitec8/1 DVD+-rw, ARTEC32x12x48x kernel-2.6.7-gentoo-r11(,sony LCDTFT19" |
|
Back to top |
|
|
Locke355 Tux's lil' helper
Joined: 21 May 2002 Posts: 98
|
Posted: Tue Jun 29, 2004 10:55 am Post subject: Re: solution |
|
|
theDreamer wrote: | simple solution:
Code: | ACCEPT_KEYWORDS=~x86 emerge -v nvidia-kernel nvidia-glx |
this is a newer version of nvidia driver which works better with 2.6.6+ (unless you have dual cpu).. |
what do you mean if you mean "unlessyou have dual cpu" ? I am running SMP for hyperthreading, so that is why I am asking.
I just upgraded to the 5336 driver and 2.6.7-r6 kernel, and when i EXIT XFree, I lose monitor sync (monitor says it is going into standby mode) .. and i need to ctrl-alt-del.
Does anyone have any ideas for a fix? |
|
Back to top |
|
|
theDreamer Tux's lil' helper
Joined: 20 Oct 2003 Posts: 118
|
Posted: Tue Jun 29, 2004 11:10 am Post subject: dual cpu |
|
|
the 5336 driver is working excellent for me.
but from dual cpu forums i read that many encountered problem with it.
i'm not certain if hyper-threading will cause the same problem as two+ real processors.
the problem is that the driving is crashing and the picture freezes...
check www.2cpu.com for more information.
my suggestion is to check this problem only if you encounter it. _________________ Cheers,
Nir Dremer
www.dremer.org |
|
Back to top |
|
|
wanx n00b
Joined: 30 Jun 2004 Posts: 10
|
Posted: Wed Jun 30, 2004 12:42 am Post subject: |
|
|
after updating the kernel and glx packages, adjusting the XF86Config per the documentation's instructions, i get a blank screen on startx. i'm currently updating xfree using the "~x86" flag.
any more clues to my quandry? |
|
Back to top |
|
|
electrofreak l33t
Joined: 30 Jun 2004 Posts: 713 Location: Ohio, USA
|
Posted: Wed Jun 30, 2004 2:19 am Post subject: |
|
|
I have the same problem, and it is really making me made. I just installed gentoo (fresh install, used to use debian) and when I get the nvidia stuff emerged, I run 'modprobe nvidia' and I get:
Code: | bash-2.05b# modprobe nvidia
FATAL: Error inserting nvidia (/lib/modules/2.6.7-gentoo-r6/video/nvidia.ko): Invalid module format |
I tried the same exact thing with both 4496 and 5535. As you can see from that, I'm using 2.6.7-gentoo-r6, and I don't have that kernel stacks option on. It worked wonderfully in debian, and i'm very puzzled as to why it doesn't work now in gentoo.
Right now i'm running just plain xfree (kde is compiling right now) with just the nv option in the xfree config. |
|
Back to top |
|
|
30726 Veteran
Joined: 24 Sep 2003 Posts: 1501
|
Posted: Wed Jun 30, 2004 2:34 am Post subject: |
|
|
I got the same problem when I tested mm-sources-2.6.7-r2. Vanilla development-sources works though, so use that for now. |
|
Back to top |
|
|
wanx n00b
Joined: 30 Jun 2004 Posts: 10
|
Posted: Wed Jun 30, 2004 2:40 am Post subject: |
|
|
after updating the kernel and glx packages, adjusting the XF86Config per the documentation's instructions, i get a blank screen on startx. i'm currently updating xfree using the "~x86" flag.
any more clues to my quandry? |
|
Back to top |
|
|
30726 Veteran
Joined: 24 Sep 2003 Posts: 1501
|
Posted: Wed Jun 30, 2004 2:50 am Post subject: |
|
|
wanx wrote: | after updating the kernel and glx packages, adjusting the XF86Config per the documentation's instructions, i get a blank screen on startx. i'm currently updating xfree using the "~x86" flag.
any more clues to my quandry? |
What kernel are you using? Read my previous post. |
|
Back to top |
|
|
wanx n00b
Joined: 30 Jun 2004 Posts: 10
|
Posted: Wed Jun 30, 2004 3:36 am Post subject: |
|
|
i'm using 2.6.7-gentoo-r6
the clever thing about this particular problem is that it hard locks the system and writes nothing to the error log...
i'm considering just not using glx, and letting "nv" run X
would that be wise? |
|
Back to top |
|
|
30726 Veteran
Joined: 24 Sep 2003 Posts: 1501
|
Posted: Wed Jun 30, 2004 3:39 am Post subject: |
|
|
wanx wrote: | i'm using 2.6.7-gentoo-r6
the clever thing about this particular problem is that it hard locks the system and writes nothing to the error log...
i'm considering just not using glx, and letting "nv" run X
would that be wise? |
It's either that, or changing to a kernel that doesn't have this issue.
Code: | emerge development-sources |
|
|
Back to top |
|
|
wanx n00b
Joined: 30 Jun 2004 Posts: 10
|
Posted: Wed Jun 30, 2004 3:47 am Post subject: |
|
|
i'll just do without gl support...nothing i can think of in my daily use would require it
FWIW...it's a Dell i8100--not exactly a powerhouse |
|
Back to top |
|
|
haxwell n00b
Joined: 31 Oct 2003 Posts: 2 Location: Washington State
|
Posted: Wed Jun 30, 2004 5:35 am Post subject: |
|
|
Hi,
I ran into this issue when upgrading nvidia-kernel. I'm running a Northwood P4 with hyperthreading and kernel 2.6.7-mm2 SMP. At first I was seeing the "client supports wrong version of rm api" so I upgraded nvidia-glx to 1.0.5336-r2 and I was able to get X started again. When trying to down rev, I would see the "invalid module format" errors when loading the module. However, even though X starts, when the nvidia module is unloaded it causes a kernel panic and hangs the box, also all the frame buffer consoles are broken and switching from X to a VT locks the box. I used to get ~3000 FPS in glxgears, now it is around 1000. Obviously somthing is broken and the real point to my ramble here is to serve as a warning not to upgrade the nvidia-kernel or -glx on SMP kernels until this is fixed. |
|
Back to top |
|
|
theDreamer Tux's lil' helper
Joined: 20 Oct 2003 Posts: 118
|
Posted: Wed Jun 30, 2004 8:01 am Post subject: complete solution |
|
|
The nvidia driver does not like frame buffer / boot splash / ...
compile the kernel in normal console textual mode and i believe you wont have this problem... _________________ Cheers,
Nir Dremer
www.dremer.org |
|
Back to top |
|
|
electrofreak l33t
Joined: 30 Jun 2004 Posts: 713 Location: Ohio, USA
|
Posted: Wed Jun 30, 2004 3:00 pm Post subject: |
|
|
wanx wrote: | i'm using 2.6.7-gentoo-r6
the clever thing about this particular problem is that it hard locks the system and writes nothing to the error log...
i'm considering just not using glx, and letting "nv" run X
would that be wise? |
I just decided I have to have the nvidia drivers, and since somone said 2.6.5 worked, I just went ahead and used 2.6.5 works fine now. |
|
Back to top |
|
|
|