Bug#558292: marked as done (kernel: ethernet interface 3c509b will only initialize at boot with 10BaseT/Half duplex.)
Your message dated Fri, 27 Nov 2009 18:36:53 +0000
with message-id <20091127183653.GI8172@decadent.org.uk>
and subject line Re: Bug#558292: kernel: ethernet interface 3c509b will only initialize at boot with 10BaseT/Half duplex.
has caused the Debian Bug report #558292,
regarding kernel: ethernet interface 3c509b will only initialize at boot with 10BaseT/Half duplex.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
558292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558292
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kernel
Severity: normal
unabel to get 3com 3c509b interface to operate at 100/full-duplex. It only
works at 10/half-duplex. Tried 3com recomended driver 3c509 and it failed
to install with fatal errors when I ran modprobe on it. After reinstalling
the standard debian driver 3c59x the interface came up at 100/full-duplex.
Rebooted the machine and problem went back to eth0 would only work at
10/half-duplex. Found documentation in /etc/src/linux-2.6.31.6/Documentation
that stated the 3c509b interface did not auto negotiate well and should be
set to 100/full no autoneg. Set the switch port to 100/full.
Again rebooted the machine and symptoms were the same, eth0 only works at 10/
half-duplex.
removed the driver and reinstalled it and then eth0 came up at 100/full-duplex.
Then added the following commands to /etc/rc.local to get the interface up
at 100/full-duplex at boot:
/etc/init.d/networking stop
sleep 4
modprobe -r 3c59x
sleep 4
modprobe 3c59x
sleep 4
ethtool -s eth0 autoneg off speed 100 duplex full
sleep 4
/etc/init.d/networking start
sleep 4
Note the sleep commands were added when the commands worked when typed at
the command line but failed in the script.
At this point I have a viable workaround as illustrated above but I thought
you would want to know that the driver does not initialize properly at boot
up time.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.6 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Fri, Nov 27, 2009 at 11:56:40AM -0500, root wrote:
[...]
> Then added the following commands to /etc/rc.local to get the interface up
> at 100/full-duplex at boot:
>
> /etc/init.d/networking stop
> sleep 4
> modprobe -r 3c59x
> sleep 4
> modprobe 3c59x
> sleep 4
> ethtool -s eth0 autoneg off speed 100 duplex full
> sleep 4
> /etc/init.d/networking start
> sleep 4
>
> Note the sleep commands were added when the commands worked when typed at
> the command line but failed in the script.
Note that in squeeze you will be able to hook ethtool commands into the
standard networking scripts, so you won't need a custom script.
> At this point I have a viable workaround as illustrated above but I thought
> you would want to know that the driver does not initialize properly at boot
> up time.
I'm closing this because I understand it to be a hardware bug that can't be
fixed. In general, autonegotiation is a good thing and the driver should
not disable it by default.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
--- End Message ---
Reply to: