[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 3C905 with AsusTek K7V



I am using the latest Debian kernel, whatever that may be. I'm sure you are more up on it than I am. I just downloaded it yesterday from the Debian ftp site. I really don't think this is a software problem either, because I had the exact some problem with a different nic (an NE2000 compliant generic card) using RedHat.

I looked all through my BIOS settings, and believe it or not, there is no PnP operating system, which surprised me. It's an AWARD bios, and I don't particularly like it. Anyway, I did set the IRQ for PCI slot 3 ( and that is the slot the nic is plugged into) to 5, and I also enabled the "Reserve IRQ 5 for legacy device" option.  I get the same results you see below with and without the "Reserve IRQ 5" setting.

I realize that the IRQ 255 line is definitely not good, but I think the problem is occurring in the line just before that:

The PCI BIOS has not enabled the device at 0/80. Updating PCI command 0004->0005

unfortunately, I have no idea what to do about it.

I seem to recall problems with older 3c59x.o modules and newer 3C905 NICs.
Newer kernels have a module that works; older ones need to have the newer
version of the module (available from Don Becker's site,
http://www.scyld.com/network/index.html) patched in. SInce you don't say
what version of Debian or what kernel you are using, you might be
experiencing this problem.

In the output you sent, the key line is:

>eth0: 3Com 3c59x Boomerang 100baseTx at 0xa400, 00:60:97:ba:91:1d, IRQ 255
>  *** Warning: IRQ 255 is unlikely to work! ***

Do you really get this same line when you set... the IRQ for the card to 5
in the BIOS"? Did you also set the BIOS to "non-PnP" operating system?

At 01:09 AM 5/24/00 -0700, Nolan Clark wrote:
>My 3C905 nic does not seem to work with the K7V motherboard. The card works
>fine in windows, but it will not work in redhat or debian linux.  Redhat
>didn't have much in the way of errors, but debian produced some very
>interesting things during boot up:

Reply to: