Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming? Bill
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote:
Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming? Bill
I would care but NM works for me when I boot with the 2.6.22.1-33 kernel. The killswitch error is not really an error, just an indication that the killswitch was not found as it is not on my laptop.
This has been talked to death on the networkmanager-list. So it must be a different error that is causing your connection to fail.
I would bet you get the same error when you use the 2.6.22.1-27 kernel. -- ======================================================================= It's never too late to have a happy childhood. ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote:
Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming?
Umm, 'cause it works for everyone else?
Not really trying to be facetious, but it does work fine for me (Thinkpad T41, ipw2200). What's your wireless hardware?
Bill
On Tue, 2007-07-31 at 23:55 +0200, Patrick wrote:
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote: [snip]
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming?
Because afaik the issue is already fixed in 2.6.21.1-41 in updates-testing.
Ok, I am confused. If we are already using 2.6.22.1-33 , why is 2.6.21.1-41 an upgrade? That was a typo wasn't it? -- ======================================================================= I always turn to the sports pages first, which record people's accomplishments. The front page has nothing but man's failures. -- Chief Justice Earl Warren ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote:
Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming? Bill
The answer was that 2.6.22.1-41 does fix the problem. Thank you.
William John Murray wrote:
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote:
Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming? Bill
I have screamed about the new kernels for weeks. Right now I will not yum upadate another kernel. My F7 works fine with the old kernel and do not need more trouble.
The answer was that 2.6.22.1-41 does fix the problem. Thank you.
On Fri, 2007-08-03 at 06:11 -0600, Karl Larsen wrote:
I have screamed about the new kernels for weeks. Right now I will not yum upadate another kernel. My F7 works fine with the old kernel and do not need more trouble.
Well you won't know if one improves or worsens your situation unless you do try them. But you're not forced to keep on using it. I set my preferences to keep at least four kernels, I've got the space for it.
Karl Larsen wrote:
William John Murray wrote:
On Tue, 2007-07-31 at 22:10 +0100, William Murray wrote:
Hi all, I was surprised to see the lack of reaction to NetworkManager's death in F7 2.6.22.1-33 This affects my desktop and my laptop, both with wired dhcp connections. I see the following error:
Jul 31 20:24:09 BillMurray NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Moving to 2.6.22.1-27 fixes it. So does using a fixed IP and neat, no networkmanager. So why is no one else screaming? Bill
I have screamed about the new kernels for weeks. Right now I willnot yum upadate another kernel. My F7 works fine with the old kernel and do not need more trouble.
The answer was that 2.6.22.1-41 does fix the problem. Thank you.
So with all the "screaming", did you enter a bug in bugzilla? Screaming here is only mildly useful for it's cathartic benefits.
Tim wrote:
On Fri, 2007-08-03 at 06:11 -0600, Karl Larsen wrote:
I have screamed about the new kernels for weeks. Right now I will not yum upadate another kernel. My F7 works fine with the old kernel and do not need more trouble.
Well you won't know if one improves or worsens your situation unless you do try them. But you're not forced to keep on using it. I set my preferences to keep at least four kernels, I've got the space for it.
I will read this list and when people start saying how good a kernel is I will get it.
Tim:
Well you won't know if one improves or worsens your situation unless you do try them.
Karl Larsen:
I will read this list and when people start saying how good a kernel is I will get it.
I think I mostly see people mentioning problems, rather than what works, as far as kernels are concerned, at least. So far, all of the recent problems people have brought up about kernels haven't affected me, the last two or three have been fine on my system. If I'd avoided them just because of what I read on this list, I wouldn't have tried it. I think you still have to try them. So long as you don't get rid of your old kernels during an update, you can simply boot from an older one if it doesn't work for you.
-
Aaron Konstam -
Karl Larsen -
Matthew Saltzman -
Patrick Lists -
Richard England -
Tim -
William Murray