LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Flaw in latest Kernel upgrades? (http://www.linuxquestions.org/questions/slackware-14/flaw-in-latest-kernel-upgrades-833831/)

cwizardone 09-22-2010 12:57 PM

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.

rob.rice 09-22-2010 01:08 PM

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

cwizardone 09-22-2010 01:32 PM

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 *)

cwizardone 09-22-2010 01:35 PM

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

vss2094 09-22-2010 02:04 PM

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 :)

Lufbery 09-22-2010 02:10 PM

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.

cwizardone 09-22-2010 02:51 PM

Quote:

Originally Posted by Lufbery (Post 4105927)
...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.

brianL 09-22-2010 03:44 PM

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

Richard Cranium 09-22-2010 05:15 PM

Quote:

Originally Posted by Lufbery (Post 4105927)
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).

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

Chuck56 09-22-2010 05:28 PM

Quote:

Originally Posted by Richard Cranium (Post 4106066)
If you are loading modules in your initrd, you should.


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

a/kernel-modules-2.6.33.4-x86_64-2.txz: Rebuilt.

colorpurple21859 09-22-2010 07:27 PM

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.

Lufbery 09-22-2010 08:15 PM

Quote:

Originally Posted by Richard Cranium (Post 4106066)
If you are loading modules in your initrd, you should. I don't know why you would think otherwise.

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,

allend 09-22-2010 11:26 PM

Quote:

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.
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.

GazL 09-23-2010 03:41 AM

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.

brianL 09-23-2010 04:13 AM

Quote:

Originally Posted by GazL (Post 4106432)
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.

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.


All times are GMT -5. The time now is 07:43 AM.