Won't connect to network on fresh start only on reboot

superscrappy · 05-23-2005, 04:24 PM

I am currently trying to set up a headless web server with one of my old computers. I am running Fedora Core 3 and Apache 2.0 for the webserver. The problem I am having is that the eth0 will not connect to the network on a fresh start (the computer starting from power off). It is only possible to connect to the local network once I reboot.

The weird thing is that if I set the connection to static, ifconfig says that eth0 is connected with a valid ipaddress, but I cannot ping/connect to the router or anyother computers on the network, I can ping the given local ipaddress however. when I log onto the router from a different computer on the local network the router lists the computer as being connected.

If I set the ip address to dhcp it never establishes a connection at all on first bootup.

Upon rebooting the system everything works as it should. I have tried different routers (same brand different model) but that has no effect. Below is the status of the config files for the network (there are two: one for when the network works and the other for when it doesn't). Notice that the configuration files are exactly the same for the working and non working status.

The only difference I have noticed is in the bootup log. Something extra is happening on the reboot that I believe is fixing my problem. I a section from the boot log that has to deal with the network and is different for the two different start ups (one from power off and one from reboot).

First the configurations for the nonworking setup as well as the results of some network commands: ******************************

/etc/sysconfig/network-script/ifcfg-eth0

Code:

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.1.5
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
IPV6INIT=no
GATEWAY=192.168.1.1
HWADDR=00:10:4b:2c:40:69

/etc/sysconfig/network

Code:

NETWORKING=yes
HOSTNAME=localhost.localdomain

/etc/resolv.conf

Code:

; generated by /sbin/dhclient-script
nameserver 192.168.1.1
search localdomain

/sbin/ifconfig

Code:

eth0      Link encap:Ethernet  HWaddr 00:10:4B:2C:40:69
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::210:4bff:fe2c:4069/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:4823 (4.7 KiB)
          Interrupt:10 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2205 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2915900 (2.7 MiB)  TX bytes:2915900 (2.7 MiB)

/sbin/ifup eth0 (with dhcp this time, if its static the same result as above occurs)

Code:

Determining IP information for eth0...PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2998ms
, pipe 4
 failed.

/var/log/boot.log (this is with dhcp enabled, result is different for static)

Code:

May 19 20:19:23 localhost nfslock: rpc.statd startup succeeded
May 19 20:19:24 localhost rpcidmapd: rpc.idmapd startup succeeded
May 19 20:19:24 localhost netfs: Mounting other filesystems:  succeeded
May 19 20:19:21 localhost ifup: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
May 19 20:19:21 localhost ifup:
May 19 20:19:21 localhost ifup: --- 192.168.1.1 ping statistics ---
May 19 20:19:21 localhost ifup: 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
May 19 20:19:21 localhost ifup: , pipe 4
May 19 20:19:21 localhost ifup:  failed.
May 19 20:19:21 localhost network: Bringing up interface eth0:  failed

And the working config setup and command results:************************************************

/etc/sysconfig/network-script/ifcfg-eth0

Code:

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.1.5
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
IPV6INIT=no
GATEWAY=192.168.1.1
HWADDR=00:10:4b:2c:40:69

/etc/sysconfig/network

Code:

NETWORKING=yes
HOSTNAME=localhost.localdomain

/etc/sysconfig/resolv.conf

Code:

; generated by /sbin/dhclient-script
nameserver 192.168.1.1
search localdomain

/sbin/ifconfig

Code:

eth0      Link encap:Ethernet  HWaddr 00:10:4B:2C:40:69
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::210:4bff:fe2c:4069/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:115 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8444 (8.2 KiB)  TX bytes:11773 (11.4 KiB)
          Interrupt:10 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1959 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1959 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2420522 (2.3 MiB)  TX bytes:2420522 (2.3 MiB)

/var/log/boot.log (with dhcp enabled)

Code:

May 19 20:06:39 localhost nfslock: rpc.statd startup succeeded
May 19 20:06:37 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf
May 19 20:06:37 localhost ifup:  done.
May 19 20:06:37 localhost NET: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
May 19 20:06:37 localhost network: Bringing up interface eth0:  succeeded

Note for a static IP I get the following for both working and nonworking configs.

Code:

May 25 22:58:20 webhost network: Bringing up interface eth0:  succeeded

It looks as if the dhclient-script is correcting my resolv.conf file but as I have shown the file is the exact same in the working and nonworking state.

I am fairly new to linux admin and this is about the extent of my knowledge so please bear with me.

Thanks,
-Scrappy

superscrappy · 05-23-2005, 04:29 PM

The ipaddress for the nonworking ifconfig result should say:

192.168.1.5

in order to match the config file ( this was simply a typo and not the cause of the problem)

osvaldomarques · 05-23-2005, 08:46 PM

Hi Super,

First of all, did you look for the routes ("/sbin/route") in both cases?
I did look your config and the once strange thing I found is your hostname: "localhost" is almost a synonym to "lo" and 127.0.0.1.
I already saw machines configured this way but they were not good performers. In several hosts files there are notes to not mix the hostname with "127.0.0.1" and, by consequence, I suppose, with "localhost" also.
May be it confuses the kernel routes, with unpredictable results. I would suggest you to change the "/etc/sysconfig/network" to a different name and update /etc/hosts to make sure you have:

Code:

127.0.0.1  localhost

192.168.1.5  yourhost.yourdomain   yourhost

I hope this helps you. Good luck!

Osvaldo.

superscrappy · 05-24-2005, 08:03 AM

Thanks Osvaldo,

the routes are the same for the working and nonworking config:

Code:

/sbin/route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

however there is about a 5 second delay before the last default route shows up in the nonworking config.

I also changed my /etc/sysconfig/network file to show the following:

Code:

/etc/sysconfig/network
NETWORKING=yes
HOSTNAME=webhost.webdomain

and my /etc/hosts file to:

Code:

 /etc/hosts
127.0.0.1     localhost
192.168.1.5       webhost.webdomain     webhost

But I still cannot connect on a fresh start. Do you happen to know what these lines mean in the boot up log:

Code:

/var/log/boot.log
May 19 20:06:37 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf
May 19 20:06:37 localhost ifup: done.
May 19 20:06:37 localhost NET: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
May 19 20:06:37 localhost network: Bringing up interface eth0: succeeded

I thought it was just updating my networking files but this step doesn't happen on a fresh start.

Thanks again for your help, it's much appreciated.

-S

osvaldomarques · 05-24-2005, 09:54 AM

Hi Super,

What route is that 169.254.0.0? Do you have 2 subnetworks on the same ethernet? I didn't see any previous reference to it. Take a look on that.

Cheers,

Osvaldo.

superscrappy · 05-24-2005, 04:28 PM

Osvaldo,

I have no clue where that came from. I know at one time I might have turned one of my linux boxes into a DNS in an attempt to fix my current problem. Maybe this is where it came from. It shows up on all three of my linux systems but not on my roomates WinXP (we are all on the same local network). There should only be one network. My setup is the typical local network controlled by a router that connects to the internet.

I tried the following:

Code:

/sbin/route del -net 169.254.0.0 netmask 255.255.0.0 dev eth0

Deleting that strange route had no effect on the working or nonworking config.

Another interesting thing is that our internet connection seems to be going out a lot ever since I've been messing around with this server. Could just be my provider but I don't really have a clue if I could be effecting the connection or not.

Is there a way to find out why/where this 169.254.0.0 address is coming from?

Again I apologize for my lack of admin knowledge.

Thanks for your help,

-S

osvaldomarques · 05-24-2005, 10:08 PM

Hi Super,

I did some research (google) on this address and discovered this is the APIPA, (Automatic Private IP Address). It's a reserved address for stations configured for DHCP client which don't find a dhcp server.I already found that there are some discussion on Red Hat Mailing List on FC3. This remembered me about another thread here in LQ about resolving issues on FC3. This thread Core 3 DNS resolving problem deserves your visitation.

Good luck!

Osvaldo.

superscrappy · 05-25-2005, 06:23 PM

Thanks Osvaldo,

I inserted the alias commands into my modprobe.conf file, and it had no effect.

I also disabled APIPA w/IP address: 169.254.0.0
with

Code:

NOZEROCONF=yes in my ifcfg file.

Restarting my network connection takes away the strange address but has no effect on my connection.

Also upon rebooting the following routes appear (note I have left the NOZONECONF=YES option on):

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 lo
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

The also has no effect.
I tried disabling the firewall /sbin/service iptables stop
I can still not ping anything besides my own computer.

I still don't understand how I can have a static IP address and the router says its connected and yet I cannot ping anything outside my computer, including the router. Also when I type the command:

Code:

/sbin/ethtool eth0
Settings for eth0:
No data available

Thanks for the suggestions, do you have any other ideas??

Thanks,
-S

osvaldomarques · 05-25-2005, 08:14 PM

Hi Super,
Looking at your last post, some things changed. The address 196.254.0.0 is now on "lo" interface. I suggest you to look the "/etc/sysconfig/network-scripts/ifcfg-lo". All the configurations in that file must be 127.0.0.something. It cannot have any NOZEROCONF option. If there is one, delete it.
As your overall configuration, I'm breaking my mind to understand why do you need dhcp. All your addresses are static, including the gateway and dnsserver. I wonder if you are getting this 169.254 because, as you have a fixed address, you cannot get a dynamic one and the logic is establishing a APIPA because you couldn't get it. (I hope I'm being clear as my English vocabulary is very limited.)

I re-read all the thread to see what we are missing and I think I found the reason for dhclient being invoked. It's in the "/etc/sysconfig/network-scripts/ifcfg-eth0": you have "PEERDNS=yes" and "USERCTL=yes". I would suggest you to change both to "no". PEERDNS means "get the dns address from the peer when establish the connection". It's used when you have a ppp or you are driven by dhcp. You don't need it because you know the dns server is 192.168.1.1. The second is already used by dynamic interfaces which must be manipulated by a normal user.

Good luck!

Osvaldo.

superscrappy · 05-26-2005, 08:42 AM

Osvaldo,

Thanks again for the help. I should clarify something from my original post. The boot.log that I displayed was when I tried to connect with dhcp. When I set everything to static I don't get that message at boot. Instead I get the following for both (working and nonworking) configurations:

Code:

May 25 22:58:20 webhost network: Bringing up interface eth0:  succeeded

Sorry about the confusion, that was my fault for not explaining that. But even though it says eth0 is up I still cannot ping the router.

My ifcfg-lo is as follows:

Code:

DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback

So from what I can tell it looks OK. I turned the PEERDNS and USERCTL to no but this again had no effect (but I assume you where thinking the dhcp client was being called because of these settings due to my unclear original post).
Looking at my original ifconfig results I see that (RX packets:0 and RX bytes:0 (o.o b) ) I assume these are the packets received. Which would make since for an unconnected eth0, but then again my router sees the connection and identifies the right MAC address for my NIC. Puzzling

Anyway, sorry about the bad original info I hope this clarifies my predicament better.

-S

osvaldomarques · 05-26-2005, 10:13 AM

Hi Super,

Now I need to look for some ground. You told in the first post you got an old machine. How old is that? Does it use ISA network board? Does the route shows the 169.254.0.0 yet? May you post the following details of the configuration:

Code:

lspci -vv
lspci -n
cat /proc/cpuinfo
cat /proc/ioports
cat /proc/interrupts
lsmod

Just for the sake of clarity, tell me if I'm right: I understood that the network does not work on the power up but works after a reboot. If your answer is "yes", I would you to try another nic. We must note that when the machine is powered up, the mother board gives an electrical reset to all the logic. On reboot it's just a soft reset. May be some component in the nic is sensitive to this difference.

Osvaldo.

superscrappy · 05-26-2005, 07:16 PM

Osvaldo,

Quote:

I understood that the network does not work on the power up but works after a reboot.

Thats exactly my problem. On reboot a static or dhcp setting works, but neither works on bootup even though a static setup claims it is connected and so does the router. I will look around for another NIC and let you know if I have any luck.

My current NIC is an ISA card: 3COM - NET ETHER 10/100BOARD PCI

The computer was mfg in 2000.
route is still showing the 169.254.0.0 address for lo device

here is the info you requested. Note this was taken when the network was not working, I don't know if that matters or not.

/sbin/lspci -vv

Code:

00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
        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
        Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [a0] AGP version 1.0
                Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (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: 128
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        I/O behind bridge: 00009000-00009fff
        Memory behind bridge: f6000000-f7ffffff
        Prefetchable memory behind bridge: fc000000-fdffffff
        Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
        BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B+

00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
        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

00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master])
        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
        Region 4: I/O ports at 10e0 [size=16]

00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
        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 D routed to IRQ 9
        Region 4: I/O ports at 10c0 [size=32]

00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
        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

00:0e.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08)
        Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort+ <MAbort- >SERR- <PERR-
        Latency: 96 (3000ns min, 32000ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 1080 [size=64]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0f.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
        Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100
        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: 80 (2500ns min, 2500ns max), Cache Line Size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at 1000 [size=128]
        Region 1: Memory at f4000000 (32-bit, non-prefetchable) [size=128]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
        Subsystem: 3Dfx Interactive, Inc.: Unknown device 103a
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=32M]
        Region 1: Memory at fc000000 (32-bit, prefetchable) [size=32M]
        Region 2: I/O ports at 9000 [size=256]
        Capabilities: [54] AGP version 1.0
                Status: RQ=8 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit+ FW- AGP3- Rate=x1,x2
                Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
        Capabilities: [60] Power Management version 1
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

lspci -n

Code:

00:00.0 Class 0600: 8086:7190 (rev 03)
00:01.0 Class 0604: 8086:7191 (rev 03)
00:07.0 Class 0601: 8086:7110 (rev 02)
00:07.1 Class 0101: 8086:7111 (rev 01)
00:07.2 Class 0c03: 8086:7112 (rev 01)
00:07.3 Class 0680: 8086:7113 (rev 02)
00:0e.0 Class 0401: 1274:1371 (rev 08)
00:0f.0 Class 0200: 10b7:9055
01:00.0 Class 0300: 121a:0005 (rev 01)

cpuinfo

Code:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 3
cpu MHz         : 647.405
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips        : 1277.95

ioports

Code:

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
1000-107f : 0000:00:0f.0
  1000-107f : 0000:00:0f.0
1080-10bf : 0000:00:0e.0
  1080-10bf : Ensoniq AudioPCI
10c0-10df : 0000:00:07.2
  10c0-10df : uhci_hcd
10e0-10ef : 0000:00:07.1
  10e0-10e7 : ide0
  10e8-10ef : ide1
7000-701f : 0000:00:07.3
8000-803f : 0000:00:07.3
9000-9fff : PCI Bus #01
  9000-90ff : 0000:01:00.0

interrupts

Code:

           CPU0
  0:     637069          XT-PIC  timer
  1:       1551          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
  9:          0          XT-PIC  uhci_hcd
 10:        189          XT-PIC  eth0
 11:       3551          XT-PIC  Ensoniq AudioPCI
 12:       4290          XT-PIC  i8042
 14:      11928          XT-PIC  ide0
 15:       9962          XT-PIC  ide1
NMI:          0
ERR:          0

lsmod

Code:

Module                  Size  Used by
parport_pc             24705  1
lp                     11565  0
parport                41737  2 parport_pc,lp
autofs4                24005  0
i2c_dev                10433  0
i2c_core               22081  1 i2c_dev
sunrpc                160421  1
ipt_REJECT              6465  1
ipt_state               1857  6
ip_conntrack           40693  1 ipt_state
iptable_filter          2753  1
ip_tables              16193  3 ipt_REJECT,ipt_state,iptable_filter
uhci_hcd               31449  0
snd_ens1371            27557  1
snd_rawmidi            26725  1 snd_ens1371
snd_seq_device          8137  1 snd_rawmidi
snd_pcm_oss            47609  0
snd_mixer_oss          17217  1 snd_pcm_oss
snd_pcm                97993  3 snd_ens1371,snd_pcm_oss
snd_timer              29765  1 snd_pcm
snd_page_alloc          9673  1 snd_pcm
snd_ac97_codec         64401  1 snd_ens1371
snd                    54053  9 snd_ens1371,snd_rawmidi,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_ac97_codec
soundcore               9889  1 snd
gameport                4801  1 snd_ens1371
3c59x                  36585  0
floppy                 58609  0
dm_snapshot            17029  0
dm_zero                 2369  0
dm_mirror              23341  2
ext3                  116809  2
jbd                    74969  1 ext3
dm_mod                 54741  6 dm_snapshot,dm_zero,dm_mirror

Thanks again for your help,
-S

osvaldomarques · 05-29-2005, 10:44 AM

Hi Super,

Looking for the installed modules, it seems you have a firewall. Would you try to disable it to see if it is the responsible for the lack of network?

Did you try to change the nic? By the way, this nic is a PCI type, not ISA. The former were the boards compatible with the ancient pcs, since the AT generation.

Have a nice Sunday.

Osvaldo.

superscrappy · 05-31-2005, 01:37 PM

Osvaldo,

I switched out my NIC w/ my roomates and it worked perfectly. I probably should have tried this early, I was thinking it had to be the software since the card worked on reboot, but aparently I was wrong. Thanks for all the help!!

-S