FC5
Net Llama!
netllama
Sat Jun 10 14:09:15 PDT 2006
On 06/10/2006 02:00 PM, Rick Sivernell wrote:
> Lonnie
>
>> You realize that your mail client is removing all
>> the EOL characters, right?
> No I did not, I have checked settings in
> sylpheed 2.2.5 and did not find any setting for eol.
>
>> I don't see Marvell mentioned anywhere. Again, Asus
>> user guide and spec sheet does at the following url
> http://usa.asus.com/products4.aspx?modelmenu=2&model=772&l1=3&l2=14&l3=66
> LAN -> Marvell Gbit LAN PHY 88E1111
>
> lsmod :
> forcedeth 57797 0
>
> but nothing is attached to it like:
> 8139too 61761 0
> mii 38849 2 8139cp,8139too
right, because the interface isn't up.
>
> ifconfig shows eth0 & eth1 started. however the connect led
> at the cable connection just stays on, no blinking to
> indicate any traffic.
>
> eth0 Link encap:Ethernet HWaddr 00:50:FC:8F:6F:5A
> inet addr:192.168.0.40 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::250:fcff:fe8f:6f5a/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> ...
> ...
> Interrupt:19 Base address:0x4c00
>
> eth1 Link encap:Ethernet HWaddr 00:11:2F:7F:17:EC
> inet addr:192.168.0.60 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> ...
> ...
> Interrupt:17 Base address:0x6000
The LED isn't really a reliable way to determine if things are working.
If your routing table isn't sending anything down eth1, then the LED
isn't going to flash. I don't understand why you mangled ifconfig
output, when the RX/TX info is actually the most important piece of
information here.
Are you getting a DHCP lease for the onboard NIC? If yes, then this has
nothing to do with the driver.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama at linux-sxs.org
LlamaLand http://netllama.linux-sxs.org
14:05:02 up 14 days, 18:38, 1 user, load average: 0.42, 0.47, 0.36
More information about the Linux-users
mailing list