---------- Original Message ---------------------------------- From: Scott Silva ssilva@sgvwater.com Reply-To: CentOS mailing list centos@centos.org Date: Tue, 09 Sep 2008 12:22:53 -0700
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
I agree but this is a newer ambit modem and if it was the case then mine and the cable guy's laptop would experience the same results.
________________________________________________________________ Sent via the WebMail system at mail.dsli.com
on 9-9-2008 1:07 PM David Petruzzella spake the following:
---------- Original Message ---------------------------------- From: Scott Silva ssilva@sgvwater.com Reply-To: CentOS mailing list centos-IFYaIzF+flcdnm+yROfE0A@public.gmane.org Date: Tue, 09 Sep 2008 12:22:53 -0700
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
I agree but this is a newer ambit modem and if it was the case then mine and the cable guy's laptop would experience the same results.
Not necessarily. Many companies focus heavy development on their windows drivers, but their linux offerings are either second-teir, or reverse engineered.
Either way, ethtool should show you detected and current link states on the connection ;
ethtool eth0 Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
On Tuesday 09 September 2008 17:00, Scott Silva wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
Robert Spangler wrote:
On Tuesday 09 September 2008 17:00, Scott Silva wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
were you logged on as root? ('$' tends to imply you were not)...
# /usr/sbin/ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes
$ /usr/sbin/ethtool eth0 Settings for eth0: Cannot get device settings: Operation not permitted Cannot get wake-on-lan settings: Operation not permitted Cannot get message level: Operation not permitted Cannot get link status: Operation not permitted No data available
On Tuesday 09 September 2008 18:18, John R Pierce wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
were you logged on as root? ('$' tends to imply you were not)...
sudo'er. Never log into root unless it really really have to.
$ /usr/sbin/ethtool eth0 Settings for eth0: Cannot get device settings: Operation not permitted Cannot get wake-on-lan settings: Operation not permitted Cannot get message level: Operation not permitted Cannot get link status: Operation not permitted No data available
Compare what you got to what I posted. You will see that you got 'Operation not permitted' Where I got 'No data available'
Robert Spangler wrote:
On Tuesday 09 September 2008 17:00, Scott Silva wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
Does mii-tool work?
On Tuesday 09 September 2008 18:20, Les Mikesell wrote:
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
Does mii-tool work?
Nope. Don't understand why. Maybe a support issue. Never really looked into it.
~ $ /sbin/mii-tool eth0 SIOCGMIIPHY on 'eth0' failed: Bad address
~ $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr ************* inet addr:************* Bcast:************* Mask:255.255.255.0 inet6 addr: fe80::211:d8ff:fe95:657d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2647570 errors:0 dropped:0 overruns:0 frame:0 TX packets:2665320 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1542512190 (1.4 GiB) TX bytes:312597978 (298.1 MiB) Interrupt:185 Memory:fac00000-0
Les Mikesell wrote:
Robert Spangler wrote:
On Tuesday 09 September 2008 17:00, Scott Silva wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
Does mii-tool work?
After recompiling the latest marvell driver ethtool responds properly.
on 9-9-2008 3:07 PM Robert Spangler spake the following:
On Tuesday 09 September 2008 17:00, Scott Silva wrote:
Either way, ethtool should show you detected and current link states on the connection ;
That is not always the case. I cannot get ethtool to work.
~ $ /sbin/ethtool eth0 Settings for eth0: No data available
And yes I have eth0 up and running.
try su - ethtool eth0
On Tuesday 09 September 2008 18:53, nate wrote:
Robert Spangler wrote:
And yes I have eth0 up and running.
What network driver?
On-board port: Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Driver: sk98lin
Robert Spangler wrote:
On Tuesday 09 September 2008 18:53, nate wrote:
Robert Spangler wrote:
And yes I have eth0 up and running.
What network driver?
On-board port: Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Driver: sk98lin
Downloading the latest driver from Marvell and compiling it did the trick. It turns out that it was a driver issue.
On Friday 19 September 2008 23:38, David Petruzzella wrote:
Robert Spangler wrote:
On Tuesday 09 September 2008 18:53, nate wrote:
Robert Spangler wrote:
And yes I have eth0 up and running.
What network driver?
On-board port: Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Driver: sk98lin
Downloading the latest driver from Marvell and compiling it did the trick. It turns out that it was a driver issue.
Nice, can you give me a link to the file and what file you downloaded please? Thnx.
-
David Petruzzella -
John R Pierce -
Les Mikesell -
nate -
Robert Spangler -
Scott Silva