Dan,
Any suggestions for how to debug the fact that NM isn't receiving
link-up/link-down events from my e1000 after suspend/resume? I really don't
know enough of the udev/hal/dbus interaction to know where to start looking,
nor do I understand the underlying protocols well enough to know how to
On Wed, 2005-08-10 at 11:19 -0400, Derek Atkins wrote:
Any suggestions for how to debug the fact that NM isn't receiving
link-up/link-down events from my e1000 after suspend/resume? I really don't
know enough of the udev/hal/dbus interaction to know where to start looking,
nor do I
On Wed, 2005-08-10 at 11:36 -0400, Derek Atkins wrote:
Yep. I see kernel-log linkup/linkdown messages just fine after a
suspend/resume.. And if I stop NetworkManager I can ifup eth0 and it works
just fine.
Is the device still listed in HAL?
Now that I know where to look and I can see if
Quoting Robert Love [EMAIL PROTECTED]:
On Wed, 2005-08-10 at 11:36 -0400, Derek Atkins wrote:
Yep. I see kernel-log linkup/linkdown messages just fine after a
suspend/resume.. And if I stop NetworkManager I can ifup eth0 and it works
just fine.
Is the device still listed in HAL?
How do
Quoting Dan Williams [EMAIL PROTECTED]:
I'm looking at this too, my e1000 driver seems to take a _really_ long
time to notify the netlink socket that the device has changed status
(like 20s or so?). That's not cool. I'm attempting to distill a
testcase that I could send to kernel people, you
On Wed, 2005-08-10 at 11:45 -0400, Derek Atkins wrote:
Now that I know where to look and I can see if the netlink socket
needs to get
reset after a resume..
I have an e1000 and it works fine after resume..
What version of NM? I'm using STABLE_0_3 on FC3.
In 0.3, I think we're using
On Wed, 2005-08-10 at 11:45 -0400, Derek Atkins wrote:
How do I tell?
$ hal-device | grep eth0
Now that I know where to look and I can see if the netlink socket
needs to get
reset after a resume..
I have an e1000 and it works fine after resume..
What version of NM? I'm using
On Wed, 2005-08-10 at 11:47 -0400, Derek Atkins wrote:
Quoting Dan Williams [EMAIL PROTECTED]:
I'm looking at this too, my e1000 driver seems to take a _really_ long
time to notify the netlink socket that the device has changed status
(like 20s or so?). That's not cool. I'm attempting
On Wed, 2005-08-10 at 11:51 -0400, Robert Love wrote:
On Wed, 2005-08-10 at 11:45 -0400, Derek Atkins wrote:
Yah, it might not be NM... but I don't think its HAL, because those
things don't do the link monitoring. If NM can see the device, then all
of that is working.
Hal 0.4x does netlink
