On Sat, Jan 11, 2003 at 03:49:35PM +0200, Michelle Konzack wrote:
> Hello Phil,
>
> Am 18:27 2003-01-09 +0000 hat Phil Reynolds geschrieben:
>
> ># cat /proc/pci
>
> > Bus 1, device 0, function 0:
> > Ethernet controller: (rev 16).
> > Master Capable. Latency=64. Min Gnt=10.Max Lat=5.
>
> OK, there is a NIC
> . . .
> They found a compatible 3c59x NIC
>
> >3c575_cb: RequestIO: Out of resource
> >PCI: No IRQ known for interrupt pin A of device . Please try using
> pci=biosirq.
>
> Not found, so you do not need the module...
>
> >3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> >: 3Com PCI 3CXFEM656C Tornado+Winmodem CardBus at 0x0. Vers LK1.1.16
> >PCI: Setting latency timer of device to 64
> > *** Warning: IRQ 0 is unlikely to work! ***
>
> OK, your PCMCIA is 3c59x compatibel...
>
> But they need an interrupt.
> Maybe you must setup the IRQ manualy...
> On the other hand the IRQ problem may be a
> problem of the Winmodem and not of the NIC...
>
> >Any suggestions would be welcome.
Now that you know the name of the module, you can create an options
line for it in modutils; then whenever the module is called for the
system will act as if these options had been given on the command line.
Usually it's *sound* that needs that, but anyways you can try
`````
options 3c59x (whatever options you can get to work at commadline)
'''''
Doublecheck the name of the module that loads; or if it bails and
removes itself, mess around on the commandline with modprobe or insmod
manually feeding it commandline options until you're happy with the
results. Then add a file like loccal-ether to /etc/modutils with your
options line, and re-run update-modules to recreate /etc/modules.conf
cleanly.
* Heather Stern * star@ many places...
* Starshine Technical Services -*- 800 938 4078
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
