Joern Abatz wrote:
On Sat, Jun 11, 2005 at 07:03:01PM -0500, Dan McGhee wrote:
[ Setting the IRQ ]
I looked into the kernel tree. There doesn't seem to be any documentation on
your driver (forcedeth). I looked into forcedeth.c (in drivers/net), and to
me it seems the driver doesn't take any options, but autosenses all it needs
to know (maybe I'm wrong here, I didn't write a kernel driver myself yet).
I think, drivers cannot change IRQs on the PCI bus. They must live with
whatever the Bios gave their cards. (Although it definitely didn't give it
IRQ 21) Look at what lspci says about your card. Also say 'lspci -n' and
look for the vendor:device ids in include/linux/pci_ids.h. Are they even
on the list?
Then unload the module, and reload it with 'modprobe -v'. Maybe the driver
gets a bit more specific about what it thinks it is doing.
The driver is still marked 'experimental', so you might be stumbling over a
bug. Try the newest kernel you can get, good luck ;-)
Joern, thanks for all your help. You apparently were paralleling the
work that I was doing. I haven't yet tried the unloading and loading
thing yet. In modprobe.conf I wrote:
options forcedeth irq=11
and the module did not load. I've seen other examples that have an entry
like
options <module name> irq=1,15
I haven't tried that yet either. I'm running kernel 2.6.11.11. Before I
jump back into this with both feet today, I'm going to update my bios to
see what happens. Additionally, I have the drivers from nVidia that I
can install. They may be more IRQ sensitive :) on this machine. As a
last resort, I'll turn off plug and play in the kernel. and then maybe acpi.
Thanks again.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
