[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: eth0 problems..



25232 is the size and the 1 is how many times it is used, this part is
completely normal.

>>> Simon Buchanan <nmc@orcon.net.nz> 09/27/04 10:05 PM >>>
Hi Doug,

the lsmod results in a line like this in the middle:

3c59x 25232 1

BUT, looking in /etc/modules.conf and /etc/modules... there in no entry 
with anything near this? Strange

Doug Griswold wrote:
> Do a lsmod and look for the 3 com module that is loaded.  Then look in
> /etc/modules.conf and modules to see if you have a options line near
> that module that might be setting the duplex.  You can always set the
> duplex by using "ethtool -s eth0 speed 100 duplex full autoneg off" 
but
> if you aren't near the box you could kill your ethernet connection if
> you aren't really connected to a 100Mbit hub or switch.  
> 
> Here's some more info:
> 
> Linux recognizes the card but seems to run in the wrong mode (e.g.
> 10Mbit instead of 100Mbit) :
> 
> This can be solved with an appropriate entry in the options line
> mentioned above. With this line you can switch the driver to the
desired
> mode (thereby switching off the autodetection of the driver). Here's
an
> excerpt from Donald Beckers Homepage, which explains some details :
> 
> An example of loading the vortex module is
>         insmod 3c59x.o debug=1 options=0,,12
> This sets the debug message level to minimal messages, sets the first
> card to
> the 10baseT transceiver, the second to the EEPROM-set transceiver, and
> the
> third card to operate in full-duplex mode using its 100baseTx
> transceiver.
> (Note: card ordering is set by the PCI BIOS.)
> 
> Possible media type settings
>         0       10baseT, or use default setting.
>         1       10Mbps AUI
>         2       undefined (special case: 10baseT from the LILO prompt)
>         3       10base2 (BNC)
>         4       100base-TX
>         5       100base-FX
>         6       MII (always the correct transceiver type on the 3c905)
>         8       
> 
>         16      Full-duplex bit
>                 16 10baseT full-duplex
>                 20 100baseTx full-duplex
>         32      Bus-master enable bit (experimental use only!)
> 
> E.g., If you want to run the card in Full-Duplex 100Mbit-Mode, enter
the
> following parameters in the options line :
> 
> options 3c59x          options=12
> 
> 
> 
>>>>Simon Buchanan <nmc@orcon.net.nz> 09/27/04 9:08 PM >>>
> 
> The output of lispci is:
> 
> 0000:00:12.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX 
> [Boomerang]
> 
> Im pretty sure that i havent coded anything... This is a standard
debain
> 
> woody install on a Althon XP box...
> 
> 
> 
> Doug Griswold wrote:
> 
>>Are you sure that you havn't hard coded the duplex in a script or
>>elsewhere?  lspci should show you which nic you have in the server.  
>>
>>
>>
>>>>>Simon Buchanan <nmc@orcon.net.nz> 09/27/04 8:40 PM >>>
>>
>>Here is the output of ethtool... i cant remember what the nic is...:
>>
>>Settings for eth0:
>>
>>         Supported ports: [ TP MII ]
>>         Supported link modes:   10baseT/Half 10baseT/Full
>>                                 100baseT/Half 100baseT/Full
>>         Supports auto-negotiation: Yes
>>         Speed: 10Mb/s
>>         Duplex: Half
>>         Port: MII
>>         PHYAD: 0
>>         Transceiver: internal
>>         Auto-negotiation: off
>>         Supports Wake-on: pumbg
>>         Wake-on: d
>>
>>Doug Griswold wrote:
>>
>>
>>>Try checking with ethtool.  Which nic are you using?
>>>
>>>
>>>
>>>
>>>>>>Simon Buchanan <nmc@orcon.net.nz> 09/27/04 8:13 PM >>>
>>>
>>>Hi There, i have a debian woody box that i am connected to via ssh,
>>
>>here
>>
>>
>>>is the ifconfig:
>>>
>>>eth0      Link encap:Ethernet  HWaddr 00:50:FC:XX:XX:XX
>>>          inet addr:203.109.xxx.xx  Bcast:203.109.xxx.xx 
>>>Mask:255.255.255.xxx
>>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>          RX packets:4109 errors:0 dropped:0 overruns:0 frame:0
>>>          TX packets:1079 errors:8 dropped:0 overruns:0 carrier:16
>>>          collisions:23 txqueuelen:100
>>>          RX bytes:809755 (790.7 KiB)  TX bytes:169903 (165.9 KiB)
>>>          Interrupt:16 Base address:0xa000
>>>
>>>When i check the link with mii-tool i get the following response:
>>>
>>>box:/etc# mii-tool -v eth0
>>>eth0: 10 Mbit, half duplex, no link
>>>  product info: vendor 00:00:00, model 0 rev 0
>>>  basic mode:   10 Mbit, half duplex
>>>  basic status: no link
>>>  capabilities:
>>>  advertising:
>>>
>>>NO LINK? But im connected to the thing - and its connected to a
>>
>>100Mbit 
>>
>>
>>>hub... Is this a problem with the ethernet card?
>>>
>>>Thanks
>>>
>>>Simon
>>>
>>>
>>
>>
>>
> 
> 


-- 
To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org




Reply to: