Kernel 3.4.1: the Linux kernel you've been looking for

[oshunluvr]

Anyone tried this with the nvidia drivers installed yet? Looks like I may be the first...




...swell foop?

[Fintan]

Cheers to that. I love a good G&T

[SteveRiley]

Sigh. It's almost 3:00 AM here, I'm enjoying the buzz of stiff gin tonic, and the alprazolam has crossed my blood-brain barrier. I will examine your post in greater detail tomorrow, after my morning conference call. For now, it's time for me to power down the X1 and drift into slumberrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrzzzzzzzzzzzzzzzzzzz zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

[Fintan]

Right I am going blind. wow. anyway did:

sudo dpkg -P linux*3.4.1*

then

sudo rm -rfv /lib/modules/3.4.1*

Got the right .deb:

linux-image-3.4.1-030401-generic_3.4.1-030401.201206041411_amd64.deb

then did:
~/Downloads/Kernel3.0/Kernel3.4/Kernel3.4.1$ sudo dpkg -i linux*3.4.1*.deb

and get this:

.....dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-extra-3.4.1-030401-generic:
linux-image-extra-3.4.1-030401-generic hängt ab von linux-image-3.4.1-030401-generic; aber:
Paket linux-image-3.4.1-030401-generic ist nicht installiert.
dpkg: Fehler beim Bearbeiten von linux-image-extra-3.4.1-030401-generic (--install):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
linux-image-3.4.1-030401-generic_3.4.1-030401.201206041411_amd64.deb
linux-image-extra-3.4.1-030401-generic
fintan@fintanws2:~/Downloads/Kernel3.0/Kernel3.4/Kernel3.4.1$

Lost now.

[sumski]

linux-headers-3.4.1-030401_3.4.1-030401.201206041411_all.deb

linux-image-3.4.1-030401-generic_3.4.1-030401.201206041411_i386.deb

linux-image-extra-3.4.1-030401-generic_3.4.1-030401.201206041411_amd64.deb

There's your problem, you've downloaded 32bit kernel

[Fintan]

The -i switch is for installing packages contained within .deb files. To get rid of the packages, you need to use the -r switch to remove them or the -P switch to purge them, and in either case you need to specify the package name, not the .deb filename. So your statement here is a bit confusing.

Sorry that was a typo. I did:

sudo dpkg -P linux*3.4.0*

Very weird. Would you mind editing /etc/default/grub and removing the # in front of the line that begins with GRUB_TERMINAL, running sudo update-grub, and then reporting back with some details about how far along the boot process your computer gets before it hangs?

I'll have a look at that now.

Edit: Hmm. I had to remove the 3.4.1 kernel so I could update my firefos to version 13.
When reinstalling the kernel I get this:

......Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.4.1-030401-generic /boot/vmlinuz-3.4.1-030401-generic
update-initramfs: Generating /boot/initrd.img-3.4.1-030401-generic
W: Possible missing firmware /lib/firmware/radeon/ARUBA_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/ARUBA_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/ARUBA_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/VERDE_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/VERDE_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/VERDE_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/VERDE_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/VERDE_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/PITCAIRN_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/PITCAIRN_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/PITCAIRN_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/PITCAIRN_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/PITCAIRN_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/TAHITI_rlc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/TAHITI_mc.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/TAHITI_ce.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/TAHITI_me.bin for module radeon
W: Possible missing firmware /lib/firmware/radeon/TAHITI_pfp.bin for module radeon
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.4.1-030401-generic /boot/vmlinuz-3.4.1-030401-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.4.1-030401-generic /boot/vmlinuz-3.4.1-030401-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.4.1-030401-generic /boot/vmlinuz-3.4.1-030401-generic
Generating grub.cfg ...
Found background: /home/fintan/Downloads/KDE/Backgrounds/LogoBackgroundFGC_Grub.png
using custom appearance settings
Found background image: /home/fintan/Downloads/KDE/Backgrounds/LogoBackgroundFGC_Grub.png
Found linux image: /boot/vmlinuz-3.4.1-030401-generic
Found initrd image: /boot/initrd.img-3.4.1-030401-generic
Found linux image: /boot/vmlinuz-3.2.0-25-generic
Found initrd image: /boot/initrd.img-3.2.0-25-generic
Found linux image: /boot/vmlinuz-3.2.0-24-generic
Found initrd image: /boot/initrd.img-3.2.0-24-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
Found Windows 7 (loader) on /dev/sda2
done
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-extra-3.4.1-030401-generic:
linux-image-extra-3.4.1-030401-generic hängt ab von linux-image-3.4.1-030401-generic; aber:
Paket linux-image-3.4.1-030401-generic ist nicht installiert.
dpkg: Fehler beim Bearbeiten von linux-image-extra-3.4.1-030401-generic (--install):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
linux-image-extra-3.4.1-030401-generic
fintan@fintanws2:~/Downloads/Kernel3.0/Kernel3.4/Kernel3.4.1$

I didn't see that before, must have been too excited

[SteveRiley]

A number of curiosities about your post jump out.

sudo dpkg -i linux*3.4.0*.deb to remove that kernel.

The -i switch is for installing packages contained within .deb files. To get rid of the packages, you need to use the -r switch to remove them or the -P switch to purge them, and in either case you need to specify the package name, not the .deb filename. So your statement here is a bit confusing.

sudo dpkg -i linux*3.4.1*.deb

That looks fine.

sudo update-grub

This should be an unnecessary step, as the .debs contain post-install scripts to update GRUB and your initrd automatically.

Rebooted and booted 3.4.1 kernel. Boot hangs at the grub splash.
Shut down-> booted 3.4.1 recovery mode. Boot hangs at:

Very weird. Would you mind editing /etc/default/grub and removing the # in front of the line that begins with GRUB_TERMINAL, running sudo update-grub, and then reporting back with some details about how far along the boot process your computer gets before it hangs?

[Fintan]

Hmmm...this kernel does not like my laptop at all.
This is what I did:
- sudo dpkg -i linux*3.4.0*.deb to remove that kernel. Wanted to do that anyway.
That went well so:
- Downloaded all four kernel .debs for 64 bit then:

cd /home/fintan/Downloads/Kernel3.0/Kernel3.4/Kernel3.4.1

sudo dpkg -i linux*3.4.1*.deb

This went well so:

sudo update-grub

Rebooted and booted 3.4.1 kernel. Boot hangs at the grub splash.
Shut down-> booted 3.4.1 recovery mode. Boot hangs at:

Switching to clocksource tsc

Edit: Just out of curiousity I opened up synaptic at that threw me a dependancy error message so I checked and found that:
Linux kernel image for version 3.4.1 on 64 bit x86 SMP was missing something. Under properties->dependancies:

depends: linix-image-3.4.1-030401-generic.

These are the kernel files I downloaded:

linux-headers-3.4.1-030401-generic_3.4.1-030401.201206041411_amd64.deb

linux-headers-3.4.1-030401_3.4.1-030401.201206041411_all.deb

linux-image-3.4.1-030401-generic_3.4.1-030401.201206041411_i386.deb

linux-image-extra-3.4.1-030401-generic_3.4.1-030401.201206041411_amd64.deb

[SteveRiley]

so far so good .........

thanks SteveRiley 8)

My pleasure. Glad it's working for you now.

[SteveRiley]

Nice find. Thanks for that.

[sumski]

It seems it is built on latest LTS, but for latest development release

[SteveRiley]

I gave it a quick look. Why is bug assigned to xserver-xorg-intel? I ran through few comments, and as far i see, there are users of all graphic cards, with both open and closed drivers?

Unfortunately, the bug has become a trove of mangled information. It's been bounced around to multiple packages, and for a time even had a goofy title that implied the freezing happened only when watching videos.

I personally haven't experienced any kind of crash (using 3.2 kernel + fglrx), and i also installed Kubuntu Precise on my girlfriends laptop (Dell N5110 - integrated Intel), and there are no crashed for her either (although, i did installed Intel driver from x-updates ppa, but no crashes prior to that).

My X1, which I actually put through more challenges than my T520, has had zero freezes. But the T520 -- not so lucky. Part of the difficulty in diagnosing the problem is likely because no one has been able to identify a root cause yet.

Regarding mainline ppa, don't know if i understood correctly, but it is built on latest LTS release, so there shouldn't be issues running the builds on Precise? Or am i missing something?

My suspicion is that kernels labeled "-quantal" are compiled with that release's toolchain.

[sumski]

Dunno how many of you have experienced problems, but there's been a raging issue for a while where machines will crash hard. They become completely nonresponsive: no TTYs, mouse movement, frozen second hand on an analog clock, and not even magic SysRq works.

Launchpad bug 993187 is tracking it, but alas, because so many people chimed in with other kinds of freeze-up issues, the bug was closed as "won't fix." That's somewhat irritating, but also understandable -- the bug report is rather useless in its current state.

I have been suffering with this issue on my T520 for about three weeks now. Reliably, once or twice a day, my computer would lock up hard. I have tried a variety of kernels and Xorg drivers, none of which appeared to fix the issue. Consistently and curiously, the lock up would occur during a mouse movement, and a few of the bug reports indicate the same.

This morning I tried yet another kernel: 3.4.1 from the mainline PPA. Although it's labeled for Quantal, it runs without incident on Precise. And I'm happy to report that I've gone the entire day without a single crash. I will continue to use this kernel for a while and monitor its behavior. If you're having issues with any of the 3.2 kernels (which most distros appear to have abandoned, according to one comment in the bug), you might try the 3.4.1, too.

I gave it a quick look. Why is bug assigned to xserver-xorg-intel? I ran through few comments, and as far i see, there are users of all graphic cards, with both open and closed drivers?
I personally haven't experienced any kind of crash (using 3.2 kernel + fglrx), and i also installed Kubuntu Precise on my girlfriends laptop (Dell N5110 - integrated Intel), and there are no crashed for her either (although, i did installed Intel driver from x-updates ppa, but no crashes prior to that).
Regarding mainline ppa, don't know if i understood correctly, but it is built on latest LTS release, so there shouldn't be issues running the builds on Precise? Or am i missing something?

[vinnywright]

so far so good .........

thanks SteveRiley 8)

VINNY

[vinnywright]

done ....time to reboot and see what we will see

VINNY