LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (http://www.linuxquestions.org/questions/fedora-35/)
-   -   Network not working under Fedora, but does under gentoo boot CD (http://www.linuxquestions.org/questions/fedora-35/network-not-working-under-fedora-but-does-under-gentoo-boot-cd-310222/)

BrianK 04-06-2005 12:23 AM

Network not working under Fedora, but does under gentoo boot CD
 
I just installed Fedora on an old dual proc P3 with two NICs. If I configure it to run static ip & run ifconfig, the return looks ok, but I can't ping anything, nor can anything ping me.

If I configure using DHCP, it can't find the DHCP server & times out.

If I boot up with an old gentoo install CD (which gives you a shell), it gets DHCP & I can ping anything I please.

if I lsmod under fedora, I see that the e100 module is loaded. If I lsmod nuder gentoo, I see that the eepro100 module is loaded. I tried modprobing the eepro100 under fedora (and modprobe -r the e100), but still no luck. I also changed the entries in modules.conf and hwconf from e100 to eepro100. Still no dice.

Any idea what's going on or where I begin to look?

Thanks

t3gah 04-06-2005 01:17 AM

Please tell us what kind of hardware we are dealing with.


And then the settings you are imposing and saving to the network configuration, host files, etc., before restarting the network services after you've done so.

BrianK 04-06-2005 02:28 AM

Quote:

Originally posted by t3gah
Please tell us what kind of hardware we are dealing with.


And then the settings you are imposing and saving to the network configuration, host files, etc., before restarting the network services after you've done so.

I'm not absolutely sure on the hardware. It's a Tyan motherboard with dual built-in NICs. Are you looking for info on the chipset or is there something else specific you're looking for? I'm sure I can research it to find out what you might need.
I can tell you that I loaded up an old Redhat 9 distro onto another identical machine. The network works fine & lsmod shows it having loaded the e100 module.

The settings are pretty basic:
IP: 192.168.0.61
MASK: 255.255.255.0
GW: 192.168.0.1
DNS: 192.168.0.1

I've tried DHCP as well with no luck. I know the hardware is good because, like I said, if I boot up with the gentoo boot disc, everything works fine.

sbassett 04-06-2005 10:44 AM

This has twin built in nics, have attempted this with the outgoing line plugged into each nic. Starting with one, then switching to the other if the first fails? They system maybe assigning eth0 and eth1 to different nics than it is under gentoo.

BrianK 04-06-2005 02:20 PM

Quote:

Originally posted by sbassett
This has twin built in nics, have attempted this with the outgoing line plugged into each nic. Starting with one, then switching to the other if the first fails? They system maybe assigning eth0 and eth1 to different nics than it is under gentoo.
If you're asking if I've tried both NICs, the answer is yes. I'm tried one, then the other, then rebooted for each... no go.

t3gah 04-08-2005 01:05 PM

Please post the output of

lspci -vv


And also, what version of Fedora is this?

uname -a

BrianK 04-08-2005 03:49 PM

Quote:

Originally posted by t3gah
Please post the output of

lspci -vv


And also, what version of Fedora is this?

uname -a

It's Fedora Core 3
2.6.9-1.667smp kernel

I'm thinking this may have something to do with kernel 2.6. I've built up this machine with Suse9.1, Redhat 9, Redhat 7.3, Gentoo 1.4, and Fedora 3. Those with the 2.6 kernel made for non-working NICs; those with 2.4 worked fine. Just a guess. ::shrug::

lspci -vv output:

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
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: 0
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
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: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:06.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA])
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: 32 (2000ns min), Cache Line Size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at d4000000 (32-bit, non-prefetchable) [size=16M]
Region 1: I/O ports at f000 [size=256]
Region 2: Memory at d6200000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [5c] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
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: 0
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
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: 32
Region 4: I/O ports at d400 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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: 32, Cache Line Size 08
Interrupt: pin D routed to IRQ 5
Region 4: I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
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: 32, Cache Line Size 08
Interrupt: pin D routed to IRQ 5
Region 4: I/O ports at dc00 [size=32]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
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-
Interrupt: pin ? routed to IRQ 9
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
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: 32 (2000ns min, 14000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d6202000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e000 [size=64]
Region 2: Memory at d6000000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable+ DSel=0 DScale=2 PME-

00:0e.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
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: 32 (2000ns min, 14000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at d6201000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e400 [size=64]
Region 2: Memory at d6100000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable+ DSel=0 DScale=2 PME-



t3gah 04-08-2005 04:18 PM

Here's a Ethernet Diagnosis link that has some files you compile and check the NIC's with > http://www.scyld.com/ethercard_diag.html

And the research that I've come up with says to stay away from the eepro driver and go with the driver from intel.com. > http://support.intel.com/support/net.../CS-006103.htm

Try the Intel drivers with 2.6 and get the config software too.

Oh, please do

cat /proc/interrupts


EDIT: Do Intel's Linux* Base Drivers Support the Linux 2.6 Kernel?
Quote:

Yes, all of our Intel Adapter base drivers support the Linux* 2.6 kernel.

Teaming support for the 2.6 kernel is provided by Channel Bonding available in the 2.6 kernel and does not require our ANS software.
Quote link > http://support.intel.com/support/net.../cs-010431.htm


All times are GMT -5. The time now is 12:45 PM.