On Sunday 07 January 2001 07:33 pm, David Nelson wrote: I was able to solve my IRQ conflict and get my modem, Ethernet, and even my sound card, all working at the same time by simply moving my Ethernet card to a different slot. I don't know if it was necessary or not but after moving the Ethernet card I booted into Win98 and let Windows "discover" the card and reload its drivers. After that was taken care of I booted into Linux and enabled eth0, then tried my modem and sound. Both work! Yeah!!! Seems that this is how things changed: Device Old IRQ New IRQ Modem 11 11 Ethernet 11 09 SoundCard 09 05 > Hello All, > > Well I got my modem to work and moved on to getting my Ethernet card to > work. Unfortunately, after I enable eth0 using Linux Config I am no longer > able to dial up my ISP using Kppp. It tells me the modem is busy. > Interestingly, if I enable eth0 while I am connected to the net via the > modem the modem connection continues to work, however once I disconnect, I > get the modem busy error as soon as I try to reconnect. Also, I am not able > to ping a machine on the local Ethernet network until I close the PPP > connection. Once the ppp connection is closed the Ethernet card seems to > work fine. > > Any ideas on getting both of these devices fully functional at the same > time? > > :) > > System Info: > 650MHz AMD Athlon > Jabil (Kadoka) AMD Motherboard /w AMD 750 Chipset, 128 MB of RAM > Running Linux-Mandrake 7.2 download version > More info including the full output of "lspci -bv" & "setserial -g > /dev/ttyS?" are online here: <http://www.mhtc.net/~lanelson/sysinfo.html> > > Hardware Info: > PCI Modem: USR/3COM 56K FAX Modem Model:5610, FCC reg. num: > 4X2USA-32034-M5-E, P/N: 3CP2977-OEM > > Info as reported by: lspci -bv > 00:0f.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev > 01) (prog-if 02 [16550]) > Subsystem: US Robotics/3Com USR 56k Internal FAX Modem (Model 2977) > Flags: medium devsel, IRQ 11 > I/O ports at ffa8 > Capabilities: [dc] Power Management version 2 > > PCI Ethernet adapter: LinkSys LNE100TX (ver. 4.1) supported by a driver > called "tulip"
