I have a "Samsung X10plus" laptop with the builtin ethernet interface
"Broadcom 4400 10/100BaseT". I am running the "Sarge" snapshot from
Dec 5th.
I have my laptop connected to the ethernet before I start booting.
After I had booted my system I submit the command
"mii-tool eth0"
and the respond is
No MIT transceiver present.
Then I start "eth0" manually (ifup eth0). Everything works fine. I
get a network connection. Now I stop it again (ifdown eth0) and I
unplug the ethernet cable. When I now submit the command "mii-tool
eth0" I get the answer I was expecting
eth0: no link
My question is why do I get the message "No MIT transceiver present"
right after the booting?
This behavior makes it impossible to detect if I am hooked to the
network and automatically startup my ethernet interface.
Any help or any pointer would be appreciated.
Thank you in advance,
Norbert
--
+-------------------------------------------------------------------+
| Norbert E. Gruener http://www.MPA-Garching.MPG.de/~nog/ |
| Max-Planck-Institut <n...@MPA-Garching.MPG.de> |
| fuer Astrophysik PGP encrypted mail preferred |
| PGPprint(RSA): 66 64 C0 D0 6F 1A 16 02 C2 C6 37 83 3A 5F 88 9B |
| PGPprint(DH): 8B9A CB28 79DC 4C4F 5A0F 08A8 2771 2A99 A091 FBE8 |
| PGPprint(DSS): 8900 2CB4 F3D3 124F 7ED2 F681 EA2D 11CA BE19 6642 |
+-------------------------------------------------------------------+
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Perhaps the module (b44 I believe) is not yet loaded then?
--
"Codito ergo sum"
Roel Schroeven
>Hi all,
>
>I have a "Samsung X10plus" laptop with the builtin ethernet interface
>"Broadcom 4400 10/100BaseT". I am running the "Sarge" snapshot from
>Dec 5th.
>
>I have my laptop connected to the ethernet before I start booting.
>After I had booted my system I submit the command
>
> "mii-tool eth0"
>
>and the respond is
>
> No MIT transceiver present.
>
>
>Then I start "eth0" manually (ifup eth0). Everything works fine. I
>get a network connection. Now I stop it again (ifdown eth0) and I
>unplug the ethernet cable. When I now submit the command "mii-tool
>eth0" I get the answer I was expecting
>
> eth0: no link
>
>
>My question is why do I get the message "No MIT transceiver present"
>right after the booting?
>
>This behavior makes it impossible to detect if I am hooked to the
>network and automatically startup my ethernet interface.
>
>Any help or any pointer would be appreciated.
>
>Thank you in advance
>
>
Weird. What kernel are you running? I have a Dell Poweredge 1750 with
two Broacam 5704s running the 2.6 kernel that works fine wrt mii-tool.
--
-- Skylar Thompson (sky...@cs.earlham.edu)
-- http://www.cs.earlham.edu/~skylar/
It's kernel 2.4.27 which is part of Sarge.
Norbert
--
Ceterum censeo | PGP encrypted mail preferred.
Redmond esse delendam. | PGP Key at www.MPA-Garching.MPG.de/~nog/
>It's kernel 2.4.27 which is part of Sarge.
>
>
Weird. A friend of mine has a Dell laptop with a Broadcom 4400 running
Debian Woody with the v2.4. I'll see if I can take a look at the boot
sequence when she's in town next week, and let you know what I see. I
don't remember seeing it, but I've never looked for it either.
--
-- Skylar Thompson (sky...@cs.earlham.edu)
-- http://www.cs.earlham.edu/~skylar/
I tried it, and my machine exhibits exactly the same behavior (with
kernel 2.6.8-1-686). I don't know what's causing it.
Anyway, I installed laptop-net for automatically starting the network,
and it seems to work just fine.
--
"Codito ergo sum"
Roel Schroeven
> Norbert Gruener wrote:
>
>> It's kernel 2.4.27 which is part of Sarge.
>>
>>
> Weird. A friend of mine has a Dell laptop with a Broadcom 4400 running
> Debian Woody with the v2.4. I'll see if I can take a look at the boot
> sequence when she's in town next week, and let you know what I see. I
> don't remember seeing it, but I've never looked for it either.
>
I got a hold of the laptop, and noticed that error too. I upgraded it to
v2.6, and still saw the error. It looks like it might be an issue with
the NETDEV WATCHDOG (which I'm guessing reacts to state changes in the
NIC). The state for the NIC when the driver is initially loaded is set
to down, and it takes a few seconds for the watchdog to switch the state
to up.
thank you for your effort. I really appreciated your help. I think I
got a feeling what is going wrong. So I will do some more testing.
Thank you very much,
Norbert
--
Ceterum censeo | PGP encrypted mail preferred.
Redmond esse delendam. | PGP Key at www.MPA-Garching.MPG.de/~nog/