Fedora 13 updates: New kernel 2.6.34.7-61 fixes NetworkManager suspend issue
Fedora is just now pushing a bunch of updates to my Fedora 13 installation, and they include an updated 2.6.34.7-61 kernel that should fix the problem with NetworkManager disappearing after resuming from suspend.
I'm going to install this and a bunch of other updates right now, and I'll test the suspend/resume vs. NetworkManager situation as soon as possible.
Now if Fedora could manage to keep the headphone-jack muting working on my sorry Conexant sound chip after a resume ... AND fix the open-source ati driver so it would actually work with my graphics chip, I'd be one happy Linux user.
4 Comments
Leave a comment
About this blog
Yes but...
I cannot launch Fedora 13 after Kernel update from 2.6.34.7-57 towards 2.6.34.7-61 ! I am stuck at the end of the white bar with Fedora 13 at the right.
So I am obliged to choose Kernel 2.6.34.7-57 to be able to run F13 !
For me, any fix of previous issues... Just a new big problem...
HP Pavilion DV8-1100 CPU Intel Core i7-720QM GPU nVidia GT23OM
Regards.
Joe
The new kernel isn't working out so well for me, either. It was supposed to fix the bug in which NetworkManager dies while resuming after suspend (and presumably this was a radeon-related bug).
Well, now when I try to suspend, not only do I lose NetworkManager, but suspend no longer works.
Same problem here and this appeared to be a solution for me: after booting F13, log in and shutdown NetworkManager. (/etc/init.d/NetworkManager stop).
After that the network is still working and suspend/resume works as usual. No further action needed.
Things only got worse for me with F13 and F14. I switched to Debian.
Now that I can get KMS/DRI working for Radeon with the open-source driver, I'm getting better results from the upcoming Fedora 15 and Ubuntu 11.04 pre-alpha/alphas.
So I could very well go back to Fedora in the F15 cycle. I'm not planning that, but you never know.