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, both my eth0 (b44) and eth1 (ipw2200 wireless) interfaces are taken down. On resume, the modules are loaded and whereami runs but almost inevitably doesn't find eth0 and tries to connect wirelessly. Simply running whereami again never works, because the "testmii" script in whereami does "ifconfig eth0 down" when it's unsuccessful, then future whereamis won't even try eth0 until I do "ifconfig eth0 up". I'm not sure what the best solution to fix this is. I'd rather not hack the whereami scripts unless I felt I was doing something worth submitting a patch for. I could probably do "ifconfig eth0 up" as a last step from whereami, so that a future invocation could at least test it. There doesn't seem to be a way to force the interface up _before_ starting the whereami's detection (which probably wouldn't help anyway, as the first time it _is_ coming up, it just isn't there when I need it). I might stick something in /etc/default/acpi-support to lengthen the time before whereami gets invoked (I added whereami to STOP_SERVICES), but that seems a bit dicey. 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 detection method I use). -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
