On Fri, Jul 25, 2003 at 11:24:34AM -0500, Andrew Gaffney wrote: > William Hubbs wrote: > > >00:0e.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) > > Subsystem: Lite-On Communications Inc LNE100TX > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > > Stepping- SERR+ FastB2B- > > Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 64 > > Interrupt: pin A routed to IRQ 12 > > Region 0: I/O ports at dc00 [size=256] > > Region 1: Memory at dbfefe00 (32-bit, non-prefetchable) [size=256] > > Expansion ROM at dbf40000 [disabled] [size=256K] > > > >00:10.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) > > Subsystem: Lite-On Communications Inc LNE100TX > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > > Stepping- SERR+ FastB2B- > > Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 64 > > Interrupt: pin A routed to IRQ 10 > > Region 0: I/O ports at de00 [size=256] > > Region 1: Memory at dbfeff00 (32-bit, non-prefetchable) [size=256] > > Expansion ROM at dbf80000 [disabled] [size=256K] > > Do you have 2 of these cards? If so, I think the kernel can only > activate one of them when the driver is built in. Try compiling the > driver as a module and modprobe'ing it twice.
Hi Andrew, Yes, I have two cards. Under the 2.4 series kernel, it works fine and activates both cards even if the driver is built in. But, I will definitely try compiling as a module next and see what that does. Thanks, William -- [EMAIL PROTECTED] mailing list
