Comment 6 for bug 6933

<email address hidden> wrote:
> On Sun, Jul 04, 2004 at 10:27:00AM +0100, Helen Faulkner wrote:
>
>>>does X work with
>>>2.6.7 if you disable the nvidia drivers?

> You should be able to change just
> Driver "nvidia" to
> Driver "nv"
> in Section "Device" of /etc/X11/XF86Config-4. You'll also want to
> comment out
> Load "glx"
> in Section "Module".

OK, I made those changes and rebooted with the 2.6.7 kernel. X didn't
work, but it gave error messages in the console rather than just hanging
with a black screen. This is probably similar to what I've seen before
with the nv module, which is why I was using the nvidia modules.

The end of the messages in /var/log/XFree86.0.log was like this:

(WW) open /dev/fb0: No such device
(WW) open /dev/fb1: No such device
(WW) open /dev/fb2: No such device
(WW) open /dev/fb3: No such device
(WW) open /dev/fb4: No such device
(WW) open /dev/fb5: No such device
(WW) open /dev/fb6: No such device
(WW) open /dev/fb7: No such device
(EE) Unable to find a valid framebuffer device
(EE) NV(0): Failed to open framebuffer device, consult warnings and/or
errors above for possible reasons
 (you may have to look at the server log to see warnings)
(II) UnloadModule: "nv"
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/X11R6/lib/modules/linux/libfbdevhw.a
(II) UnloadModule: "vgahw"
(II) Unloading /usr/X11R6/lib/modules/libvgahw.a
(II) UnloadModule: "int10"
(EE) Screen(s) found, but none have a usable configuration.

But, (here's where it got strange): I then carefully changed my
/etc/X11/XF86Config-4 file back to how it was to begin with. But then X
wouldn't boot with the older (2.6.6-2) kernel. I tried several times
and it doesn't work. The end of the messages in /var/log/XFree86.0.log
now go like this:

(--) NVIDIA(0): Linear framebuffer at 0xD0000000
(--) NVIDIA(0): MMIO registers at 0xFC000000
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(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.

However (the good news, I think...) X now does work with the 2.6.7
kernel, which is definitely wasn't doing last night. So I don't seem to
be able to reproduce the bug I reported (which is good if it's gone and
bad if it's merely hiding), but am now getting a different wierdness
(that X no longer works with the old kernel).

I did dselect-update-install today, to update anything that might fix
the bug. I didn't notice anything new that related to X or to nvidia,
but I guess something may have changed so the nvidia driver now works
with the 2.6.7 kernel but not with the 2.6.6 kernel, if that's possible.
  Or maybe trying to use the nv module has changed something.

Sorry if this too confusing to be helpful. I am confused too.

Helen.