OOPS on modprobe 3c2000
Zach Wilkinson
zachw at termdex.com
Sat Nov 8 23:18:44 UTC 2003
Downloaded patch from Syskonnect.
http://syskonnect.com/syskonnect/support/driver/readme/linux/patch.htm
I've never patched a kernel before so I'm unfamiliar with this output:
patching file linux/drivers/pci/pci.ids
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 2280.
Hunk #2 FAILED at 3387.
Hunk #3 FAILED at 3644.
Hunk #4 succeeded at 3741 (offset 18 lines).
Hunk #5 FAILED at 4973.
Hunk #6 FAILED at 6106.
5 out of 6 hunks FAILED -- saving rejects to file
linux/drivers/pci/pci.ids.rej
Got a lot of these...
Don't know if I did that right or not.
lspci did return that ID as my 3Com chip, so we're correct there.
Zach
On Sat, 2003-11-08 at 08:41, Xose Vazquez Perez wrote:
> Zach Wilkinson wrote:
>
>
> > OK. I've tried sk98lin. I think this is the correct driver for my chip
> > because I get the same errors that I got with the Asus 3c2000 driver. But,
> > obviously, it still doesn't work. oh, well.
> > I've heard that the new FreeBSD 4.9 has support for this chip where 5.1 does
> > not. Perhaps this chip is different enough that support is in sk98lin or
> > 3c2000 isn't there yet. At least with changes in the kernel used by FC1.
> > Just speculating.
>
>
> try latest drivers from 2.4.23-preX or http://syskonnect.com/syskonnect/support/driver/zip/linux/
>
> get a # lspci ; echo; lspci -n
> and if pci.ids is any of these:
>
> 10b7:1700 -> this is a 3com board
> 1148:4300
> 1148:4320
> 1186:4c00
> 11ab:4320
> 1371:434e
> 1737:1032
> 1737:1064
>
> the driver should work.
More information about the users
mailing list