LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-22-2010, 12:57 PM   #1
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,218

Rep: Reputation: 176Reputation: 176
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.

Last edited by cwizardone; 09-22-2010 at 12:58 PM.
 
Old 09-22-2010, 01:08 PM   #2
rob.rice
Member
 
Registered: Apr 2004
Distribution: slack what ever
Posts: 784

Rep: Reputation: 99
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
 
Old 09-22-2010, 01:32 PM   #3
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,218

Original Poster
Rep: Reputation: 176Reputation: 176
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 *)
 
Old 09-22-2010, 01:35 PM   #4
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,218

Original Poster
Rep: Reputation: 176Reputation: 176
Now having some minor video problems in Xfce.
Think I'll re-install the previous kernel packages.
 
Old 09-22-2010, 02:04 PM   #5
vss2094
Member
 
Registered: Aug 2009
Location: Jeddah, KSA
Distribution: Slackware64-Multilib**
Posts: 49

Rep: Reputation: 16
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
 
Old 09-22-2010, 02:10 PM   #6
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
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.
 
Old 09-22-2010, 02:51 PM   #7
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,218

Original Poster
Rep: Reputation: 176Reputation: 176
Quote:
Originally Posted by Lufbery View Post
...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.
 
Old 09-22-2010, 03:44 PM   #8
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,920
Blog Entries: 51

Rep: Reputation: Disabled
No problems here after the kernel update. I used slackpkg, with all fingers crossed.
 
Old 09-22-2010, 05:15 PM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,443

Rep: Reputation: 409Reputation: 409Reputation: 409Reputation: 409Reputation: 409
Quote:
Originally Posted by Lufbery View Post
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.
 
Old 09-22-2010, 05:28 PM   #10
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 421

Rep: Reputation: 58
Quote:
Originally Posted by Richard Cranium View Post
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.
 
Old 09-22-2010, 07:27 PM   #11
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,342

Rep: Reputation: 184Reputation: 184
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.
 
Old 09-22-2010, 08:15 PM   #12
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by Richard Cranium View Post
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,
 
Old 09-22-2010, 11:26 PM   #13
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,379

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
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.
 
Old 09-23-2010, 03:41 AM   #14
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
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.

Last edited by GazL; 09-23-2010 at 03:45 AM. Reason: typo
 
Old 09-23-2010, 04:13 AM   #15
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,920
Blog Entries: 51

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
libgmp and libpng in latest -current upgrades dive Slackware 37 03-05-2010 11:40 AM
LXer: Why the latest IE flaw proves Linux got it right from the start LXer Syndicated Linux News 0 12-21-2008 08:10 AM
Downloaded latest upgrades and now cant boot mpooley Ubuntu 8 06-19-2007 01:43 AM
synaptic 0.57.5 breaks; latest unstable, watch updates & upgrades Nix_Hard MEPIS 1 10-06-2005 07:55 PM
Flaw in kernel 2.4.26 gstasica Linux - General 3 07-16-2004 03:27 PM


All times are GMT -5. The time now is 10:12 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration