Hmm….video card dramas
Just upgraded to kernel 2.6.15 and got this message on boot up:
nvidiafb: nVidia device/chipset 10DE0110 nvidiafb: EDID found from BUS1 nvidiafb: Unable to detect which CRTCNumber ...Defaulting to CRTCNumber 0
After which it stalled. I’m guessing it’s something to do with the new nvidiafb driver option I saw in this kernel’s config. Why did I throw out that old Matrox G400?
November 8th, 2008 at 11:10 am
I have the same with the latest 2.6.27.4 kernel.
We have the same card N11 [Geforce2 MX/MX 400].
The computer doesn’t freeze, it is still possible to login and restart it.
I have a felling of that the output is switched to a fbconsole but not the screen.
However I can see in my Xlog file that CRT 0 is indeed the right output.
My output from dmesg when I try to boot with nvidiafb is
nvidiafb 0000:01:00.0: PCI INT A -> GSI 16 (lewel, low) -> IRQ 16
nvidiafb: EDID found from BUS1
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
nvididafb: Unable to detect which CRTCNumber…
…Defaulting to CRTCNumber 0
// The screen is frozen from this point on without anymore output.
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
nvidiafb: PCI nVidia NV11 framebuffer (64MB @ 0xE0000000)
It seems that X does not have any problem reading the EDID and chosse resolution and output.
There is also another nVidida based card integrated on the motherboard and there is no clear why to turn it of. It does not appear anywhere once the system is booted but it seem that it has reserved graphic memory (is this used by my other card to) could it be that cards dbus that complicates this?
//Brainz