Problem with ethernet card, can't connect to internet

clemsontiger · 07-29-2006, 10:04 PM

Ok, so I've got a dual boot system with Windows Xp and a linux distro (I had Fedora 5 initially, then tried Ubuntu). My problem is that my ethernet card is not able to connect to the internet in either distro. My card is integrated with my mother board (MSI K9N-Neo). The funny thing is that both distros detect my card, but Fedora can't activate it when I go to network preferences. Ubuntu can detect and activate the card, but I still can't connect to the internet (it doesn't retrieve the DHCP info automatically even though it is set to do so).

So, do I need to find some kind of a driver or something, cause I tried MSI and NVIDIA's websites to find some, but MSI didn't have any for linux and the only one that NVIDIA had for linux was for nForce 430/410 mobos, but my mobo is 550. I read on some post that Windows does something to the network card that makes linux unable to use it, but I never had this problem when I put it on an old laptop I had, so I don't know what they were talking about.

Any ideas?

dalek · 07-30-2006, 02:47 AM

Can you type in

Quote:

lspci

and post what it says about the network. It should give some information. There may be a driver in the kernel for that. It may also help when someone searches google/linux too.

blackhole54 · 07-30-2006, 03:02 AM

If the interface is up, it will show up when you type in

ifconfig

If the interface is up, I doubt if it is a driver problem. If the interface is up, take it down, assign it an IP address, DNS server, etc manually that is appropriate for your network, and bring it back up. If that works, your problem is with DHCP instead of the card or driver.

If you can't get any response, try pinging another computer on your LAN or your router. Make sure that neither your local firewall or the other machine's firewall is blocking the ping attempt.

clemsontiger · 07-30-2006, 02:26 PM

I am unable to ping anything. I tried setting up the IP address etc manually, with no luck. I am using a cable internet service and had no problems before when I used linux on my laptop (3+ years old), so that is what made me think it was some kind of a hardware/driver issue. Any more ideas? Below is the output from lspci and ifconfig...

Here is my output for lspci:
0000:00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
0000:00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2)
0000:00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2)
0000:00:01.2 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1)
0000:00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2)
0000:00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
0000:00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
0000:00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2)
0000:00:06.0 PCI bridge: nVidia Corporation: Unknown device 0370 (rev a2)
0000:00:06.1 0403: nVidia Corporation: Unknown device 0371 (rev a2)
0000:00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 0374 (rev a2)
0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 0374 (rev a2)
0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 0378 (rev a2)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 0375 (rev a2)
0000:00:0f.0 PCI bridge: nVidia Corporation: Unknown device 0377 (rev a2)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:06:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5b63
0000:06:00.1 Display controller: ATI Technologies Inc: Unknown device 5b73

Here is my output for ifconfig:
eth0 Link encap:Ethernet HWaddr 00:16:17:42:7D:25
inet6 addr: fe80::216:17ff:fe42:7d25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2312 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:169803 (165.8 KiB) TX bytes:0 (0.0 b)
Interrupt:50

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:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1456 (1.4 KiB) TX bytes:1456 (1.4 KiB)

gd2shoe · 07-30-2006, 07:55 PM

This is the line from lspci that I would focus on:

0000:00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)

From a brief bout with google, it seems that the driver you need is the forcedeth module, though you may need a newer version of it than came with the distro's you have. Note that this is only after a brief search on mcp55 and linux. I could be wrong.

Quote:

http://www.ubuntuforums.org/archive/.../t-186848.html

The version of forcedeth in Breezy didn't support the MCP51 chipset, so I went to Dapper. The 0.48 version in Dapper does support the MCP51 (and MCP55), but has a bug if you dual boot to Windows. Windows leaves the card in a state that forcedeth can't access and only disconnecting your power supply for 15 seconds will reset it. This bug was apparently fixed in version 0.53 of forcedeth.

Note that Breezy and Dapper mentioned here are different versions of Ubuntu. check with "lsmod" to see if the forcedeth module is getting loaded.

blackhole54 · 07-30-2006, 08:20 PM

I am not going to say it definitely is not the driver, but I find a few things interesting in your ifconfig output which I have highlighted.

It has an IPv6 (which I know almost nothing about) address. Is this expected? Can the rest of your software handle IPv6?
It appears you have been receiving packets although not transmitting. (Hmmm ... So how did you get an address w/o transmitting an DHCP request -- unless this was from your manual IP assignment.)
If this in an x86 box, I didn't think interrupts went up to 50.

O.P. or anybody else ... Any ideas?

Quote:

Originally Posted by clemsontiger

eth0 Link encap:Ethernet HWaddr 00:16:17:42:7D:25
inet6 addr: fe80::216:17ff:fe42:7d25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2312 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:169803 (165.8 KiB) TX bytes:0 (0.0 b)
Interrupt:50

lazlow · 07-30-2006, 09:03 PM

Assuming you assigned the address manually from post #4, what did you assign the ip address to be. I have a forcedeth card and (depending on how I set it up) I get a inet addr and a inet6 addr.
eth0 Link encap:Ethernet HWaddr 00:01:23:45:67:89
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:fe30:a957/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17

lazow

blackhole54 · 07-30-2006, 10:03 PM

As lazlow's post shows, newer versions of ifconfig can set/display both IPv4 and IPv6 addresses (simultaneously). Both my man page and the one at man.linuxquestions.org are out of date. What appears to be a current one is available here.

Perhaps trying to set an IPv4 address directly with ifconfig would be a worthwhile test. Ifconfig can also delete the IPv6 address.

dalek · 07-30-2006, 11:37 PM

I'll throw this in the mix too. I have a nforce ethernet port on my mobo. It was always flakey at best. I bought me a regular pci network card that I knew Linux supported and I have not had any more issues. This is what I have now:

Quote:

01:07.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 31)

That said, I could only get nforce to work at all with the forcedeath driver. The nvidia driver did nothing.

Hope that will help a little anyway.

:

blackhole54 · 07-31-2006, 01:44 AM

First, let me apologize for my assertion in post #8 that the LQ man page on ifconfig is out of date. I didn't see the references to IPv6 in it. Time to see the eye doctor!

Second, I played around with my system a little. It normally does not load the ipv6 module. When I manually loaded it, my ifconfig output immediately showed an IPv6 address for eth0 (in addition to its IPv4 address) even though I never specified one. I could add an additional one (or more) using ifconfig eth0 add.

I then took the interface down and configured it to use DHCP, but without a DHCP server on the network. When I brought it back up, the ifconfig output looked like the output in post #4, except that mine showed 35 tx packets (presumably trying for DHCP) and no rx packets.

EDIT: BTW, my NIC is a 3Com card. I don't believe the format of the ifconfig output depends on the card or driver.

clemsontiger · 07-31-2006, 11:38 AM

I used lsmod, and yes, forcedeth was listed. I tried deactivating the card and then reactivating it, but no luck. It still won't get the DHCP info (and yes, it is configured to do that).

The thread that gd2shoe found is the post that I referred to in my first post and am wondering how exactly "Windows leaves the card in a state that forcedeth can't access and only disconnecting your power supply for 15 seconds will reset it.". I mean, what "state" could windows leave the ethernet card in such that linux can't use it? It just doesn't quite make sense to me.

Anyway, it goes on to say that this was corrected w/ version .53 of forcedeth, but I'm not sure what version I'm running so how do I find that out? And are there any more ideas? Thanks to everyone who has contributed so far.

onebuck · 07-31-2006, 04:18 PM

Quote:

Originally Posted by clemsontiger

I used lsmod, and yes, forcedeth was listed. I tried deactivating the card and then reactivating it, but no luck. It still won't get the DHCP info (and yes, it is configured to do that).

The thread that gd2shoe found is the post that I referred to in my first post and am wondering how exactly "Windows leaves the card in a state that forcedeth can't access and only disconnecting your power supply for 15 seconds will reset it.". I mean, what "state" could windows leave the ethernet card in such that linux can't use it? It just doesn't quite make sense to me.

Anyway, it goes on to say that this was corrected w/ version .53 of forcedeth, but I'm not sure what version I'm running so how do I find that out? And are there any more ideas? Thanks to everyone who has contributed so far.

Hi,

The only thing windows could save/change that could affect the device would be cmos changes on said device. The POST would reset all devices to init state be for linux or windows. Most devices do have independent utilities if this would need to be done for device cmos setup.

Please post the output relative to the eth device;

Code:

#dmesg |grep eth      #see at boot time
#ifconfig -a          #current
#lspci -vv            #very verbose
                      # post all to check for conflicts
#lsmod                #modules

If your on board eth device is indeed recognized then statically as root;

Code:

#ifconfig eth0 192.168.0.10        #set IP
#route add default gw 192.168.0.1  #set gateway, use yours
#ping 192.168.0.1                  #ping gateway
#ping 64.233.167.99                #outside LAN
#ping google.com                   #check DNS

blackhole54 · 07-31-2006, 06:16 PM

Quote:

Originally Posted by clemsontiger

I mean, what "state" could windows leave the ethernet card in such that linux can't use it? It just doesn't quite make sense to me.

Quote:

Originally Posted by gwsandvik

The only thing windows could save/change that could affect the device would be cmos changes on said device. The POST would reset all devices to init state be for linux or windows.

I am not familiar with the details of the electronics for a PC, but I do know that POST doesn't alway reset everything. I have an internal (hardware) modem that sometimes gets itself into a state I can't talk to it. The only solution I have found is to power cycle the computer. Even a hard reset is not sufficient. But in the case of clemsontiger's ethernet hardware, I am surprised that disconnecting the power supply would accomplish something that simply turning the machine off would not.

EDIT: BTW, If you don't have source for your driver and you don't have the package it was installed from, you could try to use the strings command on its .o file to see if anything about the version is revealed.

clemsontiger · 07-31-2006, 07:47 PM

Here is the info you asked for gwsandvik...
dmesg |grep eth
----------------------------------------------
[ 15.130922] Driver 'sd' needs updating - please use bus_type methods
[ 16.935330] forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.48.
[ 17.448645] eth0: forcedeth.c: subsystem: 01462:7260 bound to 0000:00:08.0
[ 27.135777] Modules linked in: irtty_sir sir_dev usblp psmouse irda serio_raw snd_hda_intel snd_hda_codec shpchp pci_hotplug crc_ccitt pcspkr snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc af_packet sg evdev ext3 jbd ide_generic ehci_hcd ohci_hcd forcedeth usbcore ide_cd cdrom generic amd74xx sd_mod sata_nv libata scsi_mod thermal processor fan capability commoncap vga16fb cfbcopyarea vgastate cfbimgblt cfbfillrect fbcon tileblit font bitblit softcursor
[ 78.952911] eth0: no IPv6 routers present

ifconfig -a
-----------------------------------------
eth0 Link encap:Ethernet HWaddr 00:16:17:42:7D:25
inet6 addr: fe80::216:17ff:fe42:7d25/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2495 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:181547 (177.2 KiB) TX bytes:0 (0.0 b)
Interrupt:50

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:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1456 (1.4 KiB) TX bytes:1456 (1.4 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lspci -vv
--------------------------------------------------------
0000:00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0
Capabilities: <available only to root>

0000:00:01.0 ISA bridge: nVidia Corporation MCP55 LPC Bridge (rev a2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0

0000:00:01.1 SMBus: nVidia Corporation MCP55 SMBus (rev a2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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 4: I/O ports at 2d00 [size=64]
Region 5: I/O ports at 2e00 [size=64]
Capabilities: <available only to root>

0000:00:01.2 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-

0000:00:02.0 USB Controller: nVidia Corporation MCP55 USB Controller (rev a1) (prog-if 10 [OHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 58
Region 0: Memory at feafb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:02.1 USB Controller: nVidia Corporation MCP55 USB Controller (rev a2) (prog-if 20 [EHCI])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin B routed to IRQ 225
Region 0: Memory at feafac00 (32-bit, non-prefetchable) [size=256]
Capabilities: <available only to root>

0000:00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1) (prog-if 8a [Master SecP PriP])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (750ns min, 250ns max)
Region 4: I/O ports at ffa0 [size=16]
Capabilities: <available only to root>

0000:00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 225
Region 0: I/O ports at d800 [size=8]
Region 1: I/O ports at d480 [size=4]
Region 2: I/O ports at d400 [size=8]
Region 3: I/O ports at d080 [size=4]
Region 4: I/O ports at d000 [size=16]
Region 5: Memory at feaf9000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a2) (prog-if 85 [Master SecO PriO])
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin B routed to IRQ 233
Region 0: I/O ports at cc00 [size=8]
Region 1: I/O ports at c880 [size=4]
Region 2: I/O ports at c800 [size=8]
Region 3: I/O ports at c480 [size=4]
Region 4: I/O ports at c400 [size=16]
Region 5: Memory at feaf8000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>

0000:00:06.0 PCI bridge: nVidia Corporation: Unknown device 0370 (rev a2) (prog-if 01 [Subtractive decode])
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-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:06.1 0403: nVidia Corporation: Unknown device 0371 (rev a2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin B routed to IRQ 233
Region 0: Memory at feaf4000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>

0000:00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 7260
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-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 50
Region 0: Memory at feaf3000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at c080 [size=8]
Region 2: Memory at feafa800 (32-bit, non-prefetchable) [size=256]
Region 3: Memory at feafa400 (32-bit, non-prefetchable) [size=16]
Capabilities: <available only to root>

0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 0374 (rev a2) (prog-if 00 [Normal decode])
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:0c.0 PCI bridge: nVidia Corporation: Unknown device 0374 (rev a2) (prog-if 00 [Normal decode])
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:0d.0 PCI bridge: nVidia Corporation: Unknown device 0378 (rev a2) (prog-if 00 [Normal decode])
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 0375 (rev a2) (prog-if 00 [Normal decode])
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:0f.0 PCI bridge: nVidia Corporation: Unknown device 0377 (rev a2) (prog-if 00 [Normal decode])
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: feb00000-febfffff
Prefetchable memory behind bridge: 00000000d0000000-00000000dff00000
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
Capabilities: <available only to root>

0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
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-
Capabilities: <available only to root>

0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
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-

0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
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-

0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
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-
Capabilities: <available only to root>

0000:06:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5b63 (prog-if 00 [VGA])
Subsystem: Diamond Multimedia Systems: Unknown device 0430
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Interrupt: pin A routed to IRQ 66
Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
Region 1: I/O ports at e000 [size=256]
Region 2: Memory at febf0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at febc0000 [disabled] [size=128K]
Capabilities: <available only to root>

0000:06:00.1 Display controller: ATI Technologies Inc: Unknown device 5b73
Subsystem: Diamond Multimedia Systems: Unknown device 0431
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-
Latency: 0, Cache Line Size: 0x10 (64 bytes)
Region 0: Memory at febe0000 (32-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: <available only to root>

lsmod
------------------------------------------
Module Size Used by
nls_cp437 8320 1
vfat 16768 1
fat 57136 1 vfat
usb_storage 81984 1
ipv6 300416 8
rfcomm 45600 0
l2cap 30464 5 rfcomm
bluetooth 59268 4 rfcomm,l2cap
ppdev 11400 0
radeon 124320 1
drm 96296 2 radeon
cpufreq_userspace 9184 0
cpufreq_stats 8264 0
freq_table 6464 1 cpufreq_stats
cpufreq_powersave 3328 0
cpufreq_ondemand 9768 0
cpufreq_conservative 10984 0
video 18824 0
tc1100_wmi 9096 0
sony_acpi 7188 0
pcc_acpi 16128 0
hotkey 13768 0
dev_acpi 15364 0
container 6272 0
button 8864 0
acpi_sbs 24600 0
battery 12296 1 acpi_sbs
i2c_acpi_ec 7040 1 acpi_sbs
i2c_core 26624 1 i2c_acpi_ec
ac 7176 1 acpi_sbs
nls_utf8 3584 2
ntfs 101376 1
dm_mod 63176 1
md_mod 76792 0
parport_pc 40944 0
lp 15040 0
parport 44172 3 ppdev,parport_pc,lp
floppy 74120 0
tsdev 10240 0
irtty_sir 11264 0
sir_dev 23928 1 irtty_sir
usblp 16128 0
psmouse 40452 0
irda 221548 2 irtty_sir,sir_dev
serio_raw 9732 0
snd_hda_intel 21664 1
snd_hda_codec 175048 1 snd_hda_intel
shpchp 51360 0
pci_hotplug 33168 1 shpchp
crc_ccitt 3584 1 irda
pcspkr 3592 0
snd_pcm_oss 59424 0
snd_mixer_oss 20608 1 snd_pcm_oss
snd_pcm 104712 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer 29064 1 snd_pcm
snd 68576 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 13216 1 snd
snd_page_alloc 13968 2 snd_hda_intel,snd_pcm
af_packet 28172 2
sg 43568 0
evdev 14464 1
ext3 145936 1
jbd 70952 1 ext3
ide_generic 2816 0
ehci_hcd 34568 0
ohci_hcd 23684 0
forcedeth 27908 0
usbcore 145980 5 usb_storage,usblp,ehci_hcd,ohci_hcd
ide_cd 35744 0
cdrom 41144 1 ide_cd
generic 7300 0
amd74xx 16944 0 [permanent]
sd_mod 21504 6
sata_nv 12420 6
libata 86048 1 sata_nv
scsi_mod 160504 4 usb_storage,sg,sd_mod,libata
thermal 16524 0
processor 29224 1 thermal
fan 6408 0
capability 7176 0
commoncap 9728 1 capability
vga16fb 15120 1
cfbcopyarea 5120 1 vga16fb
vgastate 10368 1 vga16fb
cfbimgblt 4224 1 vga16fb
cfbfillrect 5760 1 vga16fb
fbcon 43136 72
tileblit 4096 1 fbcon
font 9984 1 fbcon
bitblit 7424 1 fbcon
softcursor 3712 1 bitblit

onebuck · 07-31-2006, 09:28 PM

Quote:

Originally Posted by blackhole54

I am not familiar with the details of the electronics for a PC, but I do know that POST doesn't alway reset everything. I have an internal (hardware) modem that sometimes gets itself into a state I can't talk to it. The only solution I have found is to power cycle the computer. Even a hard reset is not sufficient. But in the case of clemsontiger's ethernet hardware, I am surprised that disconnecting the power supply would accomplish something that simply turning the machine off would not.

Hi,

Then you have a definite hardware problem with the modem. Your modem does not acknowledge the reset line. Could be buss timing problem for the modem. Is the modem a pci? What buss speed?

Quote:

But in the case of clemsontiger's ethernet hardware, I am surprised that disconnecting the power supply would accomplish something that simply turning the machine off would not.

Some NIC have WOL (wake on LAN) and this will keep the NIC looking for a trigger. Therefore if he doesn't need WOL then I would check the BIOS to disable this. His power cycling indicates this indeed is the problem.