Kernel 3.5.0 Available for F17

[dd_wizard]

Check koji if you want to try it out. It's working fine here.

dd_wizard

[ryptyde]

Just installed it on laptop and working here also.

phil

[dcharlespyle]

I installed it. Now I am seeing messages in abrt about a "tainted kernel." I have not installed any new drivers and I am not using proprietary drivers of any kind at the moment, either. I am on a fresh and updated re-install of Fedora 17 after an attempted installation of Rawhide gave me an unbootable system without networking.

That rawhide kernel also threw an error about a tainted kernel, so there is something in common between 3.5.0 and 3.6.0 that causes it.

I am wondering if it has something to do with the bluetooth module. I do not use bluetooth on my computer so I thought it was really odd to see drivers loading for bluetooth while the system was booting up and throwing errors up all over the place.

At least I am not getting kernel panics like I did with 3.6.0 when I installed and tried to run rawhide for a day or so.

[DBelton]

Interesting. As far as the 3.5.0 kernel, running a pure vanilla Fedora 17 kernel gives me a Not tainted message.

[root@tower20 /]# dmesg | grep tainted
[46061.712093] Pid: 0, comm: swapper/1 Not tainted 3.5.0-1.fc17.x86_64 #1

You should be getting a message that specifically tells you what module taints the kernel. If a module has a non-GPL license or doesn't specify the license, you will get the kernel taint message.

Do a dmesg | grep taints and see if you can find what module is tainting the kernel.

[dcharlespyle]

Well, I am not getting that error now. Of course, I just noticed that I am now at 3.5.0-2 rather than at 3.5.0-1. I have no plans to go back to 3.5.0-1 after experiencing 3.5.0-2. This one is working wonderfully, so far as I can tell. I'm not even getting messages about things being "not tainted." Go figure. :-)

I had several failed attempts with Rawhide and decided to go back to Fedora 17 for now. After the network re-install was finished, I went to the 3.5.0-2 koji page by mistake and installed that kernel. It was not until I visited this page again that I noticed that I had installed the wrong kernel for the purposes of testing.

Sorry about that. With the one I am on now at least it does not throw any errors and I have no report from abrt about it either. Apologies for not being able to do as you asked.

[Dutchy]

It has hit the updates repos!
Pretty quick again, kudos!

[rich1974]

unfortunatelly, today i update the kernel to 3.5 and my gnome-shell is broken. the screen is flickering or is all blank. when it is flickering, i can enter the tty and reboot, but in blank screen, i can do nothing, only hard shutdown.
using the kernel 3.4 the machine works fine.
my hardware is a dell inspirion 1521 with ATI mobility radeon X1270.

[hadrons123]

My dell is working great. No issues with new kernel 3.5.
@rich1974
You can always boot into the older kernel.

[lightman47]

It just updated into my 32 bit FC17 pc and the subsequent boot into it produced a message about ICE not being able to get a listening socket, then presented me with a logout 'pop-up'. I click it and then Gnome came up. <???>

[errorxp]

It just updated into my 32 bit FC17 pc and the subsequent boot into it produced a message about ICE not being able to get a listening socket, then presented me with a logout 'pop-up'. I click it and then Gnome came up. <???>

I've had one of those as well very rarely, something to do with tmp lock files I believe.

[zc456]

Just updated and about to restart!

Update
Working fine so far.

[mikee]

Looks like it's been yanked from kernel.org.
There is no longer a 3.5.0 there, but there is a 3.6 RC1.

I found this link:

http://www.phoronix.com/scan.php?pag...tem&px=MTE1MTI

Funny.
I have been waiting for the 3,5 kernel for some fixed in the i915 driver for my home desktop!!

[DBelton]

It just updated into my 32 bit FC17 pc and the subsequent boot into it produced a message about ICE not being able to get a listening socket, then presented me with a logout 'pop-up'. I click it and then Gnome came up. <???>

I used to get that until I started deleting all files in my /tmp upon shutdown. Fedora used to do that, then with the switch to systemd, somehow they are no longer clearing /tmp on shutdown.

What happened is if by some chance, Gnome got the same PID as a previous boot, then it would spit out that error since the socket file would already exist.

to fix, I created a script that runs on shutdown and placed it in /usr/lib/systemd/system-shutdown/

(I called mine cleartmp.sh)

/usr/lib/systemd/system-shutdown/cleartmp.sh

#!/bin/bash
mount / -orw,remount
rm -Rf /tmp/*
rm -Rf /tmp/.*
mount / -oro,remount

Edit:
Make sure it's set to executable as well. chmod +x /usr/lib/systemd/system-shutdown/cleartmp.sh

[ferry]

After updating to kernel 3.5.0 booting stops after grub. The last output is: Loading initial ramdisk ...
There is only black screen after this. I do not see any action and I have to make hard restart.
Previous kernel 3.4.6 is working without any problem.

I have notebook HP Compaq 6820s (Intel Core Duo T2410, graphic card ATI Mobility Radeon X1350)

[wneumann]

Same problem as Ferry: Boot of kernel 3.5.0-2 stops after message "loading initial ramdisk" and screen goes blank with no hard disk action. Computer responds to ctl-alt-del to restart, and 3.4 kernels boot fine.

Dell Latitude D410