> This was helpful, at least intellectually. I've emerged > prism54-firmware and get a single file called isl3890. It's placed in > /lib/firmware. The FC2 box doesn't have that file, but I'm not sure > yet whether that file is approparite for this specific card. >
I thought it might not be. Can you find a similar file on the CD that came with the D-Link card? Maybe copying that over? > Actually, FC2 doesn't have a /lib/firmware directory. It does have > /etc/firmware which seems like a reasonable place. That directory has > one file: > > [EMAIL PROTECTED] firmware]$ ls -la > total 436 > drwxr-xr-x 2 root root 4096 Jan 10 12:51 . > drwxr-xr-x 71 root root 12288 Jan 11 10:23 .. > -rw-r--r-- 1 root root 425816 May 7 2004 microcode.dat > [EMAIL PROTECTED] firmware]$ > > > which may be the Intel microcode. Not sure. There is also > /lib/modules/2.6.5-1.358/kernel/drivers/firmware with one file there > also, but this is shooting in the dark. I'm not sure how to figure out > what script would be loading the firmware to see where it's looking. > There are a lot of possible scripts as a lot of network cards, and others, are just FPGA asics that get programmed on initialization. More of these will show up, especially as the networking cards get more programmable. > Does "eth1: failed to initialize firmware (err = -110)" mean it > couldn't find it or couldn't load it? (I.e. - the stack size issue > that is there under ndiswrapper, and I suppose Gentoo also.) > I really don't know. I'd guess that it couldn't actualyl start the firmware - if it's the wrong firmware, it might load, but have the wrong information to start up. Bob - -- [email protected] mailing list
