Flaw in latest Kernel upgrades?
 

Just installed the latest kernel upgrades, rebooted, fired up KDE and got this message:

"KDE detected that one or more internal sound devices were removed.

Do you want KDE to permanently forget about these devices?

The list of the devices KDE thinks can be removed:

Capture: HDA Intel (AD198x Analog)

Output: HDA Intel (AD198x Analog)

Output: HDA Intel (AD198x Digital)"

It then asked, "yes, cancel, manage devices."

When I clicked on "manage" it showed Esound as the only device, but
it didn't work.

So, was something was left out when the packages were compiled?

Thanks.

where did you get this kernel ?
I never ever I mean NEVER EVER !! up grade my kernel with out configuring it EVER .
you just don't do that
unless
you want something broken on your system

See the latest changelogs:

http://www.slackware.org/changelog/c...hp?cpu=x86_64:

Wed Sep 22 03:03:58 UTC 2010
a/kernel-firmware-2.6.33.4-noarch-2.txz: Rebuilt.
a/kernel-generic-2.6.33.4-x86_64-2.txz: Rebuilt.
This kernel has been patched to fix security problems on x86_64:
64-bit Compatibility Mode Stack Pointer Underflow (CVE-2010-3081).
IA32 System Call Entry Point Vulnerability (CVE-2010-3301).
These vulnerabilities allow local users to gain root privileges.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-3081
http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-3301
(* Security fix *)
a/kernel-huge-2.6.33.4-x86_64-2.txz: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
a/kernel-modules-2.6.33.4-x86_64-2.txz: Rebuilt.
d/kernel-headers-2.6.33.4-x86-2.txz: Rebuilt.
k/kernel-source-2.6.33.4-noarch-2.txz: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
kernels/*: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)
usb-and-pxe-installers/usbboot.img: Rebuilt.
Patched for CVE-2010-3081 and CVE-2010-3301.
(* Security fix *)

Now having some minor video problems in Xfce.
Think I'll re-install the previous kernel packages.

By the way it work just fine here.

upgraded kernel this afternoon in usual way with slackpkg.
KDE in use here, audio & video works fine, just used google video chat.

And I turned to Multilib last week.

may be some deep thought required, for what went wrong during upgrade :)

Cwizardone,

I'll be interested in finding out if others have the same problems (of if I do once I get around to installing the patched kernels). This should be a drop-in fix, even for multi-lib systems, right?

One needs to rerun LILO after upgrading to the patched kernel, but I don't think it's necessary to recreate the initrd (although that might be a good idea anyway).

Problems with audio and video, I think, point to module problems. But perhaps I'm off-base.

I think you are correct. However, I've re-installed the previous packages and the "problems" have gone away. :)
I'll wait awhile before trying the new packages again.

No problems here after the kernel update. I used slackpkg, with all fingers crossed.

If you are loading modules in your initrd, you should. I don't know why you would think otherwise.

Here's a clue when it's prudent to run mkinitrd after a kernel change:

I just updated with slackpkg HDA Intel sound drivers still work, couldn't remember modules to load in mkinitrd so took a gamble on old initrd.gz and it worked.

Because I wasn't sure what changed with the modules. My initrd just loads the JFS module.

Still, the post below yours makes it clear that doing so is a great idea.

For those who aren't aware, there's a great script for generating the mkinitrd command: /usr/share/mkinitrd/mkinitrd_command_generator.sh.

Regards,

You should rebuild your initrd.gz to include the rebuilt kernel modules.
It is easy.
1. cd /boot
2. /usr/share/mkinitrd/mkinitrd_command_generator.sh (this is Alien_Bob's very useful tool)
3. Copy the output from the above into the command line and run it.
4. Rerun lilo.

Is a initrd rebuild really necessary? The modules will still be the same. It's the same kernel version after all, and the patches don't look like they impact any modules to me. Obviously, it's safest to rebuild just to be on the safe side, but in this case I'm not convinced it's necessary.

I agree. I'm no expert, but I didn't rebuild the initrd, and everything is working. I booted into the huge kernel, ran mkinitrd_command_generator.sh, and it was exactly the same as with the pre-update kernel. So nothing's changed.

I that I know is that the upgraded kernel doesn't play at all nicely with the latest fglrx driver-it won't even install

We will probably spend more time discussing the necessity of rebuilding an initrd than it would take to simply do it.

However, if the modules were the same, then why did Pat release a new modules package? That implies that there might/should be some difference. Me? I like my system to come up when I reboot it versus muttering bad words when it doesn't because I cut a corner during an upgrade. YMMV.

Most likely he was just following his usual procedure for putting new kernel packages out and didn't give it much thought. I would have done the same.

Also, like you I would always update the kernel and modules as a pair, regardless of whether I thought it was technically necessary or not.

Just to be clear, I was not suggesting that anyone shouldn't, I was just wondering out-loud about whether it was 'technically' necessary.

lol. I wish I hadn't said anything now! ;)

I don't know about anybody else, but like I said, mine's working OK with the new generic kernel and the old initrd.

:D

Aww, come on. I want to argue about it some more! (not really)

I ran when I first installed slackware on this computer and for some reason it didn't pick up on all the modules needed for the initrd to boot. I know how to find the modules, I just got lazy and took the gamble. If it had been a version change, I wouldn't have took the gamble, on second thought, maybe I will on the next version change just to see what would happens, this is a play toy anyways and not a production machine.

That hasn't been my experience at all. On my test system (which has a 4850) the only recent recompile I had to do was against the X update. The kernel update didn't cause even a slight hiccup.

So... during the "slackpkg upgrade-all" process, where is the opportunity to configure the kernel? Now I'm afraid to run it.

There isn't an opportunity to configure the kernel because slackpkg is installing a pre-compiled kernel. There is no reason to configure it.

Near as I can figure, rob.rice confused the official Slackware kernels (which is what slackpkg deals in) with a kernel from kernel.org, which you would have to configure and compile.

No problem on my end, attribute this to PEBKAC.

I finally got around to installing the updated kernel packages. I did recreate my initrd, just because it seems the right thing to do (although it probably isn't necessary :) ), and then I reran lilo.

No problems. Everything is okay on my computer.

Regards,

I got the message
 

I manually upgraded the kernel to 2.6.35.5, because that's how I do it, and sound works; however I did receive the "KDE detected that one or more internal sound devices were removed" message. I'm using xfce4. I think the message occurred during the first run of digikam. Instead of choosing the "manage" option, I chose the "forget" option. And apparently it did, because there was no audio after that.

Upon reboot, audio was back, and the message has yet to recur, even when opening digikam.

hmm.