On Tue, 2002-10-01 at 17:27, Christopher Mahmood wrote:
* Johnathan Bailes (johnathan.bailes@esi.baesystems.com) [021001 14:05]:
No. There is no other device using the IRQ 10 that I could tell. Is there an easy way to check for conflicting IRQs?
cat /proc/interrupts
Also, as an added note I have three boxes acting the very same way.
It would be very odd if three of the them had the same IRQ conflict. Not saying that it could not be the case.
Possible, but yes it's unlikely. I just looked at your ifconfig output again and it looks like the card is set at 100bT, not 1000bT. This card cannot be forced into gigabit mode, it can only get it from autonegotiation (at least that's how it used to be, might be worth looking at the code). Let me guess, a Cisco switch?
It is a cisco switch but I have even more information. All three boxes after using the suse certified driver claim they cannot read the MAC addr from NVRAM and they are using the default which is the same address. Could this be causing and why won't it read the MAC address.
--
-ckm
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Johnathan Bailes BAE Systems ESI "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." - Doug Gwyn ---