On Fri, 2006-03-17 at 01:14 -0500, fedora-test-list-request@xxxxxxxxxx
wrote:
> > But..it fails to bring up the networking. I can fix this with
> > service network restart
> > (NetworkManager doesn't think there is an eth0 to start)
>
> This should be fixed with NetworkManager-0.6.0-3 , which will be in
> FC5
> final.
Unfortunately not. I see the /var/log/messages has more info:
Mar 17 08:11:59 billmurray kernel: tg3: tg3_reset_hw timed out for eth0,
firmware will not restart magic=4b657654
Mar 17 08:12:02 billmurray kernel: VFS: busy inodes on changed media.
Mar 17 08:12:02 billmurray kernel: VFS: busy inodes on changed media.
Mar 17 08:12:02 billmurray NetworkManager: <information> eth0:
Device is fully-supported using driver 'tg3'.
Mar 17 08:12:02 billmurray NetworkManager: <information>
nm_device_init(): waiting for device's worker thread to start
Mar 17 08:12:03 billmurray NetworkManager: <information>
nm_device_init(): device's worker thread started, continuing.
Mar 17 08:12:03 billmurray NetworkManager: <information> Now
managing wired Ethernet (802.3) device 'eth0'.
Mar 17 08:12:03 billmurray NetworkManager: <information>
Deactivating device eth0.
Not sure if this this is the best approach, but I
copied /etc/pm/hooks/10NetworkManager to 9network, and made
it shutdown and re-start network services, so now I get a little
'reconnected to network' flash up when I open the lid.
This seems not bad to me - suspending may well mean moving, maybe
plugging in/unplugging cables, why not restart networking...
Bill
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list