Koen Vermeer wrote:
> On Thu, 2005-10-13 at 11:23 -0300, Derek Broughton wrote:
>> Not on my system... if I "ifconfig eth0 down", it goes down and stays
>> down. ifplugd will start the system beeping at me as it gains and loses
>> link
>> beat, but once the b44 stabilizes, it never runs dhclient
Robert Goley wrote:
> Don't know if this has been mentioned since I can't find all the thread,
> why not compile the bcm4400 module using module-assistant and use it
> instead of the opensource b44 module since it is causing problems? I
> have used it several times on different machines. I prefe
On Thu, 2005-10-13 at 11:23 -0300, Derek Broughton wrote:
> Not on my system... if I "ifconfig eth0 down", it goes down and stays down.
> ifplugd will start the system beeping at me as it gains and loses link
> beat, but once the b44 stabilizes, it never runs dhclient again. I can't
> tell if it
Koen Vermeer wrote:
> On Wed, 2005-10-12 at 19:26 -0300, Derek Broughton wrote:
>> Ah - what you mean is that with ifplugd running, if you do "ifconfig eth0
>> down", _ifplugd_ still thinks the interface is up. After "ifconfig eth0
>> down", the interface is definitely _down_.
>
> No, if ifplugd
Don't know if this has been mentioned since I can't find all the thread, why not compile the bcm4400 module using module-assistant and use it instead of the opensource b44 module since it is causing problems? I have used it several times on different machines. I prefer opensource drivers but
On Wed, 2005-10-12 at 19:26 -0300, Derek Broughton wrote:
> Ah - what you mean is that with ifplugd running, if you do "ifconfig eth0
> down", _ifplugd_ still thinks the interface is up. After "ifconfig eth0
> down", the interface is definitely _down_.
No, if ifplugd is running and you run a 'ifc
Tony Godshall wrote:
>
> So, anyhow, the moral of the story is this:
>
> Don't be too quick to blame software.
I'm not quite sure where that moral was to be found :-) After all, we've
already agreed that there's a basic problem with the b44 - whether it's the
driver software or the hardware is
Koen Vermeer wrote:
> On Wed, 2005-10-12 at 13:03 -0300, Derek Broughton wrote:
>> > Just some additional comments: In my case, with ifplugd running, I
>> > cannot even get eth0 down. That is, if I remove the cable, do 'ifconfig
>> > eth0 down', eth0 is still UP. Only after stopping ifplugd, I can
> ... (Incidentally, I've also had
> ifplugd completely freeze my laptop for somewhere around 10 minutes if I
> make the mistake of removing the ethernet cable immediately _before_
> shutting down the computer)
Hi.
I also use a Dell with a b44 chip (mine's an Insprion 8600).
After a couple
On Wed, 2005-10-12 at 13:03 -0300, Derek Broughton wrote:
> > Just some additional comments: In my case, with ifplugd running, I
> > cannot even get eth0 down. That is, if I remove the cable, do 'ifconfig
> > eth0 down', eth0 is still UP. Only after stopping ifplugd, I can take
> > eth0 down.
> Tha
Koen Vermeer wrote:
> Hi Derek,
>
> Just some additional comments: In my case, with ifplugd running, I
> cannot even get eth0 down. That is, if I remove the cable, do 'ifconfig
> eth0 down', eth0 is still UP. Only after stopping ifplugd, I can take
> eth0 down.
That seems a little weak. The def
Hi Derek,
Just some additional comments: In my case, with ifplugd running, I
cannot even get eth0 down. That is, if I remove the cable, do 'ifconfig
eth0 down', eth0 is still UP. Only after stopping ifplugd, I can take
eth0 down.
Additionally, I restart ifplugd on resume, because otherwise the ne
Koen Vermeer wrote:
> On Tue, 2005-10-11 at 16:15 -0300, Derek Broughton wrote:
>> Any ideas? (Please don't suggest some other network detection scheme -
>> the problem is not whereami, it's the fact that the interface needs time
>> to settle down before it can be tested, and that's going to be t
On Tue, 2005-10-11 at 16:15 -0300, Derek Broughton wrote:
> Any ideas? (Please don't suggest some other network detection scheme - the
> problem is not whereami, it's the fact that the interface needs time to
> settle down before it can be tested, and that's going to be the same no
> matter what d
When my broadcom (b44) ethernet interface is first activated, it seems to
take some time to settle down - it often gives messages like:
[5062528.574000] NETDEV WATCHDOG: eth0: transmit timed out
[5062528.574000] b44: eth0: transmit timed out, resetting
Hibernating the Dell 6000 laptop works fine,
15 matches
Mail list logo
