On 3/14/06, Jimmy Rosen <[EMAIL PROTECTED]> wrote: > On Tuesday 14 March 2006 15.08, Daniel da Veiga wrote: > > On 3/14/06, Jimmy Rosen <[EMAIL PROTECTED]> wrote: > > > Hi folks, perhaps someone can shed some light on this problem? > > > > > > nvidia driver fails to load. In dmesg I find this: > > > > > > nvidia: module license 'NVIDIA' taints kernel. > > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ > > > 16 PCI: Setting latency timer of device 0000:03:00.0 to 64 > > > NVRM: The IO regions for your NVIDIA card are invalid. > > > NVRM: Your system BIOS may have misconfigured your graphics card. > > > NVRM: bar1 (framebuffer) appears to be wrong: 0x0 0x0 > > > ACPI: PCI interrupt for device 0000:03:00.0 disabled > > > nvidia: probe of 0000:03:00.0 failed with error -1 > > > NVRM: the NVIDIA probe routine was not called for 1 device(s)!! > > > NVRM: no devices probed, aborting! > > > NVRM: this often occurs when rivafb is loaded and claims the > > > device's resources. > > > NVRM: try removing the rivafb module (or reconfiguring your > > > kernel to remove > > > NVRM: rivafb support) and then try loading the NVIDIA kernel > > > module again. > > > > Have you tried doying what the module message told you to? Remove > > rivafb from you kernel and then load the nvidia module. > > > > > Now, this is an NVidia GeForce 6600 PCI-X card on an Intel > > > SE7525RP2 motherboard with 1GB ram. Kernel 2.6.15 gentoo sources > > > r1, nvidia drivers nvidia-kernel 1.0.6629-r5 and nvidia-glx > > > 1.0.6629-r6. > > > > > > According to what little I've found on the web, there seems to be > > > something weird with bios? I've tried cmos clear, and restarting > > > with all cards unplugged, but I can't get it to work. > > > Some sites suggested there might be some bios settings left if > > > the pci-x had been plugged in before the ram expansion, which was > > > the case here. > > > > I don't think its your BIOS, probably a imcompatibility between > > riva framebuffer support and nvidia module. As I remember, you can > > use just VESA for framebuffer and disable this specific framebuffer > > driver. That might solve your problem. > > > > -- > > Daniel da Veiga > > Computer Operator - RS - Brazil > > -----BEGIN GEEK CODE BLOCK----- > > Version: 3.1 > > GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- > > V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ > > ------END GEEK CODE BLOCK------ > > > > Hello, > > Yes, I have removed all riva support from the kernel, which didn't > help, and also tried with a small and clean 2.6.14 kernel that > doesn't have rivafb as module or compiled in. > The motherboard also has an ATI card, which I have tried disabling in > bios, but that doesn't help either. > > And in response to the other post by Mike Williams, it is of course a > PCI Express card, my whimsical mind... > > I updated to nvidia drivers 8178, which give a slightly different > dmesg, but still don't work. dmesg: > > nvidia: module license 'NVIDIA' taints kernel. > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: > NVRM: BAR1 is 0M @ 0x00000000 (PCI:0003:00.0) > NVRM: The system BIOS may have misconfigured your graphics card. > nvidia: probe of 0000:03:00.0 failed with error -1 > NVRM: The NVIDIA probe routine failed for 1 device(s). > NVRM: None of the NVIDIA graphics adapters were initialized! > < --- cut some other non-related usb stuff --- > > ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: > NVRM: BAR1 is 0M @ 0x00000000 (PCI:0003:00.0) > NVRM: The system BIOS may have misconfigured your graphics card. > nvidia: probe of 0000:03:00.0 failed with error -1 > NVRM: The NVIDIA probe routine failed for 1 device(s). > NVRM: None of the NVIDIA graphics adapters were initialized! > > > It does seem odd that the new 8178 driver probes the card twice and > thinks it has found adapter_s_. > > > Thankful for any further suggestions... I'm quite lost as to what to > do at the moment. > > Jimmy >
Well, something is wrong, a LOT wrong when it can't find the board and use it. Well, if I were you (I had some GForces some time ago), I would remove all and any support for riva or nv or nvidia from kernel, boot into the new kernel and try NVidia proprietary drivers runnign directy their stuff, not portage (it was the way I had my first NVidia working before I knew portage had nvidia stuff in the tree). -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- gentoo-user@gentoo.org mailing list
