-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
> Sorry to make you continually refer to the same place. I thought I > understood... Well I thought you start to ask question so we can improve the page. Its mostly mine braindump. It must be improved but this is better then nothing. >>> In none of the three cases can I find the IRQ listed in >>> /proc/interrupts. I would have expected to see it there. >> It means that the driver is not using any interrupts Maybe you need to load >> the "nvidia" proprietary module. > > I don't really care that it's not using the interrupt. I was just > thinking that might be the problem since the factory BIOS uses IRQ 5 > and Coreboot uses 18. If interrupts aren't the problem, I wonder > what's causing it to fail. You see some strange graphical artifacts? Maybe disable 2D/3D accel. I guess perhaps some PCI regions are incorrectly routed. Rudolf -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmkXW8ACgkQ3J9wPJqZRNVIPQCgoCBwjpWnTsC6dMaTqlKPyrJe rz0Anj5+vdJs1iO7OvHBKI1+MRbO22Mt =WSg/ -----END PGP SIGNATURE----- -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
