Kernel 3.5.0 Available for F17

[zuchov]

Thanks charles, Ill try that right away!

---------- Post added at 03:48 AM ---------- Previous post was at 03:35 AM ----------

Reporting: Booted into 4.6 kernel, didnt see any suspicious in /boot directry; latest kernel named 3.5.0-2. Tried remove this kernel with Yum --> 'No package marked for removal'. Trying 'yum remove 3.5.*' gets me 0:3.5.0-2!! Im hitting the y key now..

Booting 4.6 . Failed to start LSB. Boot procedure stops at sendmail transport client. I do have promts at the other terminals (virtual ones). What do I do?

Update: Updated kernel, back on 3.5.0-2. fails with lsb again, lagging (30-45 seconds) on sendmail mail.. AND 'Failed to start Wait for Plymouth Boot Screen to Quit'

Turned out to be graphic drivers somehow: during boot its pausing like before, cannot start the quit plymouth, but am up and going with my desktop just like before.

My 'soloution: yum install akmod-nvidiax86_64 + nvidia-xconfig --> rebooted

[dcharlespyle]

Originally Posted by zuchov

...

My 'soloution: yum install akmod-nvidiax86_64 + nvidia-xconfig --> rebooted

That is the best case scenario for those using nVidia and proprietary AMD drivers. You should not have any problems with kernel updates so long as you keep the akmod up-to-date with each release of the driver.

I've mentioned this elsewhere. If there is an akmod available for your video driver it is best to install it because it is supposed to rebuild and automatically install your video modules at kernel update so you don't have to do it manually. Saves a lot of headaches.

[RaiTulo]

History: FC16 Preupgrade to FC17.

Kernel-3.5.1 get problem to boot up.

dmesg attached.

[ferry]

Originally Posted by ferry

fb: conflicting fb hw usage radeondrmfb vs. VESA VGA - removing generic driver.

The same with kernel 3.5.1. Booting process stopped at the same point.
It seems that my ATI Mobility RADEON X1350 has bad luck.

I also tried to boot Kubuntu 12.10 aplha 3 with kernel 3.5.0 in live mode with similar output.

[dcharlespyle]

Originally Posted by ferry

The same with kernel 3.5.1. Booting process stopped at the same point.
It seems that my ATI Mobility RADEON X1350 has bad luck.

I also tried to boot Kubuntu 12.10 aplha 3 with kernel 3.5.0 in live mode with similar output.

That is most likely not the cause of your crash. I see the same error in dmesg and Xorg.0.log, and booting is fine. What is causing the crash and stopping booting occurs directly after that error. Unfortunately, you won't see what that is without additional debugging set for the kernel.

[LongTimeDabbler]

uname -a
Linux fedora.localdomain 3.5.0-2.fc17.x86_64 #1 SMP Mon Jul 30 14:48:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Updated via repositories and all just works for me - no issues.

[mese79]

I have a hp tm2 touchsmart laptop and touch screen doesn't work with kernel 3.5.x.
Here is xinput output on kernel 3.4 :

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E3 Finger touch             	id=9	[slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E3 Pen stylus               	id=10	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=13	[slave  pointer  (2)]
⎜   ↳ Wacom ISDv4 E3 Pen eraser               	id=15	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ HP Webcam                               	id=11	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=12	[slave  keyboard (3)]
    ↳ HP WMI hotkeys                          	id=14	[slave  keyboard (3)]

And for kernel 3.5.1:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ HP Webcam                               	id=9	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ HP WMI hotkeys                          	id=12	[slave  keyboard (3)]

I hope this fixes soon.

[sulley]

F17 x64, i3 CPU, intel GPU, it's stuck in login session after updated to 3.5.2, the mouse and keyboard seems not work fine

[dcharlespyle]

kernel 3.5.2 is working fine for me, with one exception. I am now seeing the following in dmesg:

$ dmesg | grep conflicts
[   11.973754] ACPI Warning: 0x0000000000000860-0x000000000000087f SystemIO conflicts with Region \_SB_.PCI0.GFX0.TCOI 1 (20120320/utaddress-251)
[   11.976815] ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \PMRG 1 (20120320/utaddress-251)
[   11.978966] ACPI Warning: 0x0000000000000500-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.SBRG.SVC2 1 (20120320/utaddress-251)

I haven't the faintest idea what this is doing at the moment.

Update: 3.5.2-3 still shows the above error.

[dd_wizard]

I'm getting similar messages, and after a little research I found this active kernel bug. Since there is a patch in the works, it should land in Fedora shortly. However, Comment #12 in that bug report suggests that at least our Watchdog timers are broken for now.

dd_wizard

[dcharlespyle]

I am looking forward to seeing this fixed, then.

[ferry]

Originally Posted by ferry

The same with kernel 3.5.1. Booting process stopped at the same point.
It seems that my ATI Mobility RADEON X1350 has bad luck.

I also tried to boot Kubuntu 12.10 aplha 3 with kernel 3.5.0 in live mode with similar output.

I tried ROSA Desktop 2012: Alpha-version with kernel 3.5.1 and it worked without any problem.

[dcharlespyle]

Originally Posted by ferry

I tried ROSA Desktop 2012: Alpha-version with kernel 3.5.1 and it worked without any problem.

I tried LinuxMint 13 and installed kernel 3.5.1. I ended up with corrupted NTFS partitions. Go figure...

[urban1]

I'm having a similar problem to ferry, but with later kernals.

My boot menu shows the following kernals:

3.6.5-1
3.6.3-1
3.6.4-1
(yeah, I know, they are not in sequence, but that's how they show)

The only kernel I can boot with is 3.6.4-1. With the other two, I don't even get the ramdisk message, only a message that reads 'ACPI Inalid PBLK length [5]. My understanding that this message is correct. When booting with 3.6.4-1, however, the message flashes followed by the ramdisk message and then a valid boot. When booting with the other two kernals, the computer hangs after the ACPI display.

Because I only have a single kernal that works, I'm not going to be updating for a while because that one would be pushed off the bottom (I guess).

Hopefully, someone here has some experience with the problem. I am a pretty unsophisticated user but my administrator is pretty knowledgeable about the situation.

Thanks, everyone (anyone) for any responses.

Bob

[dcharlespyle]

"ACPI Invalid PBLK length [5]" is a warning from the kernel that there is an issue with a buggy BIOS that the kernel has a problem with. Try to update your BIOS to the latest available for your motherboard.

A workaround is to use chkconfig to turn acpid off.

Another workaround is to put acpi=off in your kernel line for the newer kernels to see if you can boot the other kernels with the issue. (This should be a last resort as some computers won't boot if you use this).

Also, check your BIOS's ACPI settings. Sometimes there are issues with one or more settings. It is the soft-off option that causes this error a lot in certain BIOS versions. Try also changing one of the other settings from S1 to S3 or vice versa to see what happens.

The most important thing is to make your motherboard manufacturer aware of the problem and to make sure you are up-to-date with the latest BIOS version for your board.

Not booting at all may be another issue in addition to the above but these are the first to check.