I'm replying to thank Stef for his advice, and to remark about an apparent inconsistency in the implementation of the 3c509 driver.
On Mon, 14 May 2001, Stefan Srdic wrote: > > : /lib/modules/2.2.17/net/3c509.o: invalid parameter parm_io > > That error reports that the I/O parameter used is invalid. Your base address > for > your card should read 0x210. > > Test this by directly using the insmod command: > > insmod 3c509 io=0x210 irq=11 > > If you see something like " Using /lib/modules/2.2.17/net/3c509.o" I've now got my ethernet card configured, but I was surprised that 3c509.c does not recognize the 'io' parameter. (My kernel version is 2.2.17.) When I entered the insmod command, as it appears above, I got an error 'ignored unknown variable parm_io' (paraphrase). When I read 3c509.c, I discovered that only three parameters were defined, debug, irq and xcvr. Removing the 'io=0x210' argument was enough to configure my ethernet card, and after starting pump I'm online. Apparently the io address is determined by a loop in the probe function, which looks odd. The kernel documentation says, "In many cases it is highly preferred that insmod:ing is done ONLY with defining an explicit address for the card, AND BY NOT USING AUTO-PROBING!" Though this instruction may be aimed at users of drivers, wouldn't that also apply to driver developers? Could someone comment on why the 3c509 driver does not use an io parameter? Thanks, ben taylor [EMAIL PROTECTED] / http://www.dhp.com/~mithras "If you buy a person a ticket, they'll see a movie that day. But if you show a person how to sneak in, they'll see movies for a lifetime." Mark Stanley, _Freefall_, http://www.purrsia.com/freefall/
