You are not logged in.
Hi archers!
Netcfg is usually failing on establishing a connection for me. I have to continue trying until it succeed, as the log shows below. There is nothing fancy in my netcfg profile, it is just a static IP.
A simple ifconfig eth0 192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255 always succeed.
I first thought there was an error with my setup and netcfg, but I relize that netcfg would only allow a 1000mbit connection, while the ifconfig method would settle with a 100mbit
In a terminal:
[root@lab me]# until netcfg wired-static-lab ; do echo ; done
:: wired-static-lab up [BUSY] > No connection
[FAIL]
:: wired-static-lab up [BUSY] > No connection
[FAIL]
:: wired-static-lab up [BUSY] > No connection
[FAIL]
:: wired-static-lab up [BUSY] > No connection
[FAIL]
:: wired-static-lab up [BUSY] > No connection
[FAIL]
[b]:: wired-static-lab up [DONE][/b]
[root@lab me]#Meanwhile in /var/log/everything.log
Jun 4 14:38:32 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:32 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 4 14:38:36 lab kernel: sky2 eth0: disabling interface
Jun 4 14:38:36 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:36 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 4 14:38:40 lab kernel: sky2 eth0: disabling interface
Jun 4 14:38:40 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:40 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 4 14:38:44 lab kernel: sky2 eth0: disabling interface
Jun 4 14:38:44 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:44 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 4 14:38:48 lab kernel: sky2 eth0: disabling interface
Jun 4 14:38:48 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:48 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 4 14:38:52 lab kernel: sky2 eth0: disabling interface
Jun 4 14:38:52 lab kernel: sky2 eth0: enabling interface
Jun 4 14:38:52 lab kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
[b]Jun 4 14:38:56 lab kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
Jun 4 14:38:56 lab kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready[/b]
Jun 4 14:39:06 lab kernel: eth0: no IPv6 routers presentI can live with doing a loop with netcfg for a Gbit connection. I just have some questions:
Why is this happening?
How can I solve it?
Is there a way to change the speed while the interface is up?
(Yes, the cable is plugged in all the time!)
I would be grateful for your help
Last edited by Isola (2010-06-04 23:27:28)
Offline
Is there a way to change the speed while the interface is up?
Have a look at ethtool.
Offline
Have you got Intel's D510MO motherboard with Atom cpu? There's a bug you describe. It gets fixed by newer bios.
Offline
Isola wrote:Is there a way to change the speed while the interface is up?
Have a look at ethtool.
Hmm, I'm probably doing something wrong. When I try to switch from 1000 to 100 with ethtool the LED indicating connectivity goes from orange to black, and then back to orange. Green is 100, orange is 1000. Same thing with 100 to 1000 (Green goes back to green, instead of going to orange)
Have you got Intel's D510MO motherboard with Atom cpu? There's a bug you describe. It gets fixed by newer bios.
Nope, it is however a intel motherboard. I could update the BIOS and try, because I know that there is a newer version available for it, which fixes a power button issue or something. I'm just a bit afraid of breaking everything if I update it.
If anyone knows about the card I'm using, here is what lspci tells about it:
Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 13)I'll see what a search turns up on that card. Anyway, I always get a Gbit-connection when booting with Windows, and because of that I don't think it is related to BIOS.
Offline
After some searching I found out that there have been some issues with this card. From looking at all the issues other people had I guess I'm one of the lucky ones ^^. These issues seems to be fixed by now though.
So... I'll try another Gbit-card, a realtek based I think, and see if that one works better.
Offline
With the other Gbit-card I always get 1000mbit. Doesn't seem to matter if I use netcfg or ifconfig.
Jun 5 01:16:58 lab kernel: r8169: eth1: link upI still can't get ethtool to change speed while it is running though, but that's not important to me.
So something seems wrong with the Marvell card. I guess I'll have to wait for a updated driver for it. Meanwhile I'll settle with looping netcfg until a Gbit-connection succeed.
Offline