LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-21-2013, 11:14 AM   #16
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,817

Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817

Quote:
Originally Posted by tronayne View Post
I went looking and found that /etc/rc.modules was still linked to rc.modules-3.2.29-smp.
I noticed that too but it isn't the problem, since as ponce pointed out the files are the same. For pure tidiness I also fixed the symlink, though as expected it did not fix the issue.
 
Old 05-21-2013, 11:32 AM   #17
Eldarby
LQ Newbie
 
Registered: May 2011
Distribution: Arch
Posts: 25

Original Poster
Rep: Reputation: 1
I'm going to try some of the suggested ideas. I'll report back later.

TobiSGD: Would this work on non-standard resolutions? I've got a 1024x600 netbook display. If necessary I could plug in a 1920x1080 monitor over a VGA cable, too. Just not sure if either of those resolutions would be usable with the video= setting.

Quote:
Originally Posted by ryanpcmcquen View Post
I am affected by this as well on my Asus 1000he.
That's what I've got, too. Exact same.

This is pretty bad. I upgraded because this security issue sounded pretty serious (I've seen several other distros releasing kernel patches this morning), and now I don't even have a usable system. This kinda blows.

Why can't Slackware install and support multiple kernels in lilo's boot menu instead of clobbering over the old one? I've seen other distros support multiple kernels, like Gentoo and Ubuntu. Should this be suggested to Patrick and the team, in case this happens again, or is this one of those things Pat already made a decision against a while back? I know if there's a reason for not doing something in Slackware, it's usually a good reason, so I'm not sure if it would be worth recommending or not.

Last edited by Eldarby; 05-21-2013 at 11:45 AM. Reason: :nosaeR
 
Old 05-21-2013, 11:44 AM   #18
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,037

Rep: Reputation: 756Reputation: 756Reputation: 756Reputation: 756Reputation: 756Reputation: 756Reputation: 756
Quote:
Originally Posted by ruario View Post
I noticed that too but it isn't the problem, since as ponce pointed out the files are the same. For pure tidiness I also fixed the symlink, though as expected it did not fix the issue.
Huh.

Well, OK, but (1) didn't and (2) did -- must be magic? Dang thing's sitting there mumbling to itself and working just fine.

I'll try the laptop that I don't use too often and see what happens there (again, these are Slackware 14.0 stable, stock SMP kernel -- the one that's working is a 32-bit, the laptop is 64-bit and I'll see if it fries it brains).

Sigh.
 
Old 05-21-2013, 12:13 PM   #19
ryanpcmcquen
Member
 
Registered: Apr 2013
Distribution: Slackware
Posts: 56

Rep: Reputation: Disabled
Quote:
Originally Posted by Eldarby View Post
Why can't Slackware install and support multiple kernels in lilo's boot menu instead of clobbering over the old one? I've seen other distros support multiple kernels, like Gentoo and Ubuntu. Should this be suggested to Patrick and the team, in case this happens again, or is this one of those things Pat already made a decision against a while back? I know if there's a reason for not doing something in Slackware, it's usually a good reason, so I'm not sure if it would be worth recommending or not.
As far as I know Eldarby (someone correct me if I'm wrong here), you can put as many kernel images as you want in /etc/lilo.conf, it just isn't automatic like with GRUB/GRUB2 (I personally hate GRUB, it's so complicated, so many *.conf files).
 
1 members found this post helpful.
Old 05-21-2013, 12:28 PM   #20
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 803

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Quote:
Originally Posted by Eldarby View Post
This is pretty bad. I upgraded because this security issue sounded pretty serious (I've seen several other distros releasing kernel patches this morning), and now I don't even have a usable system. This kinda blows.
As long as you don't have potential hostile local users with remote shell access, there is no reason for panic. It's "just" a local privilege escalation issue. In the usual desktop scenario, it is just as dangerous as the possibility to "root" your smartphone.

Last edited by jtsn; 05-21-2013 at 12:30 PM.
 
Old 05-21-2013, 05:16 PM   #21
majekw
LQ Newbie
 
Registered: May 2011
Posts: 1

Rep: Reputation: Disabled
I was also affected by this 'upgrade' but I found a solution.
I found this: https://bugzilla.kernel.org/show_bug.cgi?id=58511
When I reverted this patch ( https://git.kernel.org/cgit/linux/ke...20ec5778d1f311 ) and recompiled/installed kernel modules, it works again.
 
Old 05-21-2013, 06:54 PM   #22
johnbristol
LQ Newbie
 
Registered: Feb 2008
Posts: 12

Rep: Reputation: 2
deleted

Last edited by johnbristol; 05-21-2013 at 06:55 PM. Reason: error
 
Old 05-21-2013, 07:02 PM   #23
angryfirelord
Member
 
Registered: Dec 2005
Posts: 498

Rep: Reputation: 59
Same issue here. I thought I screwed something up when I installed it onto my netbook since I had to take it apart to put in a new wireless card. Good to know a patch has been created, so 3.2.46 should fix it.
 
Old 05-21-2013, 07:52 PM   #24
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 121

Rep: Reputation: 42
This seemed to be a good time to have a slightly outdated local mirror, hehe (though now that I think about it, 3.2.29 packages should still be in the updated archive as 3.2.45 should be in /patches.) I was able to downgrade safely back to the old 3.2.29 packages, something that would seem dangerous to do on (ahem) more sophisticated distros. Chalk one up for the Slackware package management system!

Last edited by zakame; 05-21-2013 at 07:54 PM. Reason: mumble
 
1 members found this post helpful.
Old 05-21-2013, 09:41 PM   #25
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,482

Rep: Reputation: 421Reputation: 421Reputation: 421Reputation: 421Reputation: 421
Quote:
Originally Posted by ryanpcmcquen View Post
As far as I know Eldarby (someone correct me if I'm wrong here), you can put as many kernel images as you want in /etc/lilo.conf, it just isn't automatic like with GRUB/GRUB2 (I personally hate GRUB, it's so complicated, so many *.conf files).
Yeah, but it kinda sucks to remember that you forgot to run lilo after a kernel upgrade immediately after you pressed "enter" to the "shutdown -r now" command.

It still sucks to remember that you forgot to run the grub-mkconfig command after a kernel upgrade immediately after you pressed "enter" to the "shutdown -r now" command, but you can interactively fix your boot so you *can* run the bloody thing when the system comes up.

Since I've got my root directory on an LVM over a RAID array, the slackware install disk doesn't help a whole lot to reboot in that environment. Oh, you *can* do it, but it's a real PITA. Bog knows that I've done it enough times. :-/
 
Old 05-21-2013, 10:17 PM   #26
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,252

Rep: Reputation: 630Reputation: 630Reputation: 630Reputation: 630Reputation: 630Reputation: 630
This is why you install new kernels alongside the old kernel and keep an entry in lilo.conf pointing to the old kernel. You can pass -o to mkinitrd to name the initrd something other than initrd.gz so you can have multiple initrds available too. Of course, doing this breaks slackpkg (and pkgtools) because it finds multiple packages with the same name, but blacklisting the kernel packages in slackpkg and making sure to always installpkg/removepkg explicit kernel versions rather than the more generic 'kernel-generic', for example, and never upgradepkg'ing kernels, allows this to be painless. Even if you forget to run lilo, you have the old kernel version to fall back on.
 
1 members found this post helpful.
Old 05-21-2013, 10:27 PM   #27
ryanpcmcquen
Member
 
Registered: Apr 2013
Distribution: Slackware
Posts: 56

Rep: Reputation: Disabled
At least slackpkg will prompt you to run LILO after a kernel upgrade. :-)
 
Old 05-21-2013, 10:55 PM   #28
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Would be more user-friendly if kernel updates were handled conservatively.

My work-around is not using upgradepkg. I use installpkg, copy and edit the existing grub menu.lst items for the new kernel version. That way I can reboot safely should the new version cause headaches.

Not to mention there is always a punch list when updating a kernel: update nvidia, virtualbox, and lirc kernel modules, and compare the previous and new rc.modules-* files. I forgot to perform that last one today and I spent time scratching my head why I had no sound in one of my machines after the update.

Perhaps in addition to the "Remember to update lilo" message, the slackpkg reminder could print something like "Remember to update lilo/grub, third-party kernel modules such as nvidia, virtualbox, and lirc, and review the new rc.modules files for necessary changes.

When all is calm and I'm comfortable the new kernel and updated kernel modules are functioning correctly, then I use removepkg to remove the previous kernel version and modules, and update the grub menu.lst.
 
Old 05-22-2013, 08:37 AM   #29
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,434

Rep: Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867
Quote:
Originally Posted by majekw View Post
I was also affected by this 'upgrade' but I found a solution.
I found this: https://bugzilla.kernel.org/show_bug.cgi?id=58511
When I reverted this patch ( https://git.kernel.org/cgit/linux/ke...20ec5778d1f311 ) and recompiled/installed kernel modules, it works again.
I've tried to prepare a testing kernel-generic (remember you need an initrd!) package (it includes also the stuff in the kernel-modules one inside) with the patch reverted.

If anybody having the black screen problem with an intel GPU on slackware-14.0 32bit can test it...

http://ponce.cc/slackware/testing/ke...686-2ponce.txz
 
2 members found this post helpful.
Old 05-22-2013, 09:04 AM   #30
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,817

Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817
@ponce: Thanks ponce. That was really nice of you to make available. You are also one of the few here who has developed enough trust that I (and probably others) would consider taking a binaries for such a key package. That said, I still haven't noticed any problems with using the 3.8.13 kernel from current (and indeed I have noticed some improvements) so I'll probably stick with it for now. However, if I do encounter problems (and assuming Pat doesn't provide another kernel) yours will be next on my list.
 
  


Reply

Tags
black screen, kernel, slackware 14, upgrade


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
[SOLVED] Laptop with via chrome9 slackware black screen on boot splintercdo Linux - Laptop and Netbook 14 02-05-2011 08:07 AM
Activated desktop effects in Ubuntu and resulted in black screen Mooney Linux - Newbie 1 05-23-2008 11:25 AM
PC failed to boot with a dark screen resulted satimis Linux - Hardware 9 05-16-2007 08:59 PM
Slackware 9.1 new kernel compile displays black screen on boot. Krenn Slackware 3 03-29-2004 02:33 PM
Black screen during boot up after new 2.6.1 kernel cjdock Slackware 17 02-01-2004 03:36 PM


All times are GMT -5. The time now is 03:26 AM.

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