LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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-22-2013, 10:22 AM   #31
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,498

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912

I had prepared it for the slackers that doesn't want to rebuild it theirselves to test it, but it's just a matter of reverting that patch and build it

If the revert solves the blank screen problem, it can be good for Pat to have a report on that.
 
Old 05-22-2013, 12:01 PM   #32
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,119

Rep: Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818Reputation: 818
OK, so I updated the Slackware 14.0 64-bit stable SMP kernel in a Dell Inspiron 1760 (64-bit, Intel graphics). Got the black screen on reboot. Read all the stuff in this thread (including all the kernel.org commentary), wound up a little confused... well, more than a little confused.

Just what is the fix? Grab the patch(es) from kernel.org and recompile the kernel? Wait for Pat to fix the thing? Throw my hands up in horror? Definitely not gonna do my main workstation (Dell Optiplex 680, 64-bit, Intel graphics), at least until there's a fix I can understand for the problem.

Any ideas?
 
Old 05-22-2013, 12:08 PM   #33
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,498

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
if you feel like testing it, I prepared a package with the patch above reverted also for slackware64-14.0 (it includes also the modules, normally in kernel-modules package)

http://ponce.cc/slackware/testing/ke..._64-2ponce.txz

to rebuild the initrd you can use the procedure described by Pat here

http://www.slackware.com/lists/archi...ecurity.597338

Last edited by ponce; 05-22-2013 at 01:40 PM.
 
Old 05-22-2013, 12:22 PM   #34
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,274

Rep: Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587
Smile

Thanks, Pat. The new 3.2.45 kernel is now working on my Dell Optiplex GX620. All is well.

Code:
Linux thor 3.2.45-smp #2 SMP Wed May 22 00:57:33 CDT 2013 i686 Intel(R) Pentium(R) D CPU 2.80GHz GenuineIntel GNU/Linux
Code:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)

Last edited by hitest; 05-22-2013 at 12:57 PM. Reason: typo- wrong smiley :)
 
Old 05-22-2013, 12:55 PM   #35
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,984

Rep: Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555Reputation: 1555
I haven't had time to read the thread, but I encountered this (Thinkpad T400, Slackware64) and I solved worked around it by appending "nomodeset" to my kernel parameters in lilo.

Last edited by dugan; 05-22-2013 at 12:57 PM.
 
Old 05-22-2013, 01:00 PM   #36
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 134

Rep: Reputation: 53
^ That's what I did as well, then later reverted to 3.2.29 via upgradepkg.
 
Old 05-22-2013, 03:21 PM   #37
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
Quote:
Originally Posted by hitest View Post
Thanks, Pat. The new 3.2.45 kernel is now working on my Dell Optiplex GX620. All is well.
It took me a while to realise that there was an updated kernel package because my mirror had not updated. Glad to see it, though I'll probably stick with the kernel from current now as it has been working well for me.
 
Old 05-22-2013, 03:23 PM   #38
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,650
Blog Entries: 2

Rep: Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095Reputation: 4095
Quote:
Originally Posted by Eldarby View Post
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.
It works for any resolution that your videocard is able to display.
 
Old 05-22-2013, 04:18 PM   #39
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,498

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
Quote:
Originally Posted by ruario View Post
It took me a while to realise that there was an updated kernel package because my mirror had not updated.
I missed that too, so the testing ones will be of no use (I'll remove them).
 
Old 05-22-2013, 04:25 PM   #40
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
Quote:
Originally Posted by ponce View Post
I missed that too, so the testing ones will be of no use (I'll remove them).
Thanks for your work on this, Ponce!
 
Old 05-22-2013, 04:35 PM   #41
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 876

Rep: Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826
Quote:
Originally Posted by ponce View Post
I missed that too, so the testing ones will be of no use (I'll remove them).
Actually ponce, you beat me by about a half hour due to my crappy upload speed.
 
Old 05-22-2013, 08:07 PM   #42
Eldarby
LQ Newbie
 
Registered: May 2011
Distribution: Arch
Posts: 25

Original Poster
Rep: Reputation: 1
Thank you so much, Pat! Wow, that was quick. Much <3 for making the best distro I've ever used.

Quote:
Originally Posted by Diantre View Post
chmod -x /etc/rc.d/rc.font
Quote:
Originally Posted by TobiSGD View Post
It works for any resolution that your videocard is able to display.
Thank you both, but unfortunately neither of those solved the problem. I appreciate the attempts at helping me all the same. I'm going to try the nomodeset trick next reboot. I'm glad I had this live OS on a USB stick to fall back on to come here for help!

Quote:
Originally Posted by ryanpcmcquen View Post
I personally hate GRUB, it's so complicated, so many *.conf files.
Multiple *.conf files I can handle, it's that stupid hd(x,y) syntax GRUB uses that makes me mad. Everything in Linux uses a very clear, easy to follow way of doing things: /dev/sdX#. Then along comes GRUB and OH HOH HO, guess what you bastard, you're gonna have to learn this whole new crazy moon language just to configure your boot loader, only to never use that syntax for anything else you're doing in Linux ever again, except for messing around in GRUB some more.

Quote:
Originally Posted by ryanpcmcquen View Post
At least slackpkg will prompt you to run LILO after a kernel upgrade. :-)
Yes, but did it prompt you to run mkinitrd?

Not a perfect solution there, either, you gotta admit. I'm just glad I remembered that step, if I'd just trusted that slackpkg prompt to handle everything for me I'd have had even more problems to work on.

Quote:
Originally Posted by jtsn View Post
It's "just" a local privilege escalation issue.
I know, I'd like to feel safe allowing certain friends of mine to hang their black hats in my apartment again. Those guys have a strange sense of humour sometimes.

Quote:
Originally Posted by T3slider View Post
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.
Good advice. I'm going to do this. I've still got my trusty Slackware DVD, I'll just go back and revert the damage as zakame did with his local mirror, then I can get things set up your way real soon. Before I do, though, I want to make sure I'm doing this properly.

Should *all* kernel-related packages be blacklisted and installpkg'd by hand, or are there some I should still be using slackpkg/upgradepkg on instead? I know the kernel itself and probably the source too should be installpkg'd to have multiple versions, but would I want to also do the same with the firmware, headers, etc.? If I could get a breakdown of which packages to handle in which fashion that would really help.

Sorry to ask you to hold my hand, I just feel a lot safer asking someone experienced when it comes to anything kernel-related.

Last edited by Eldarby; 05-22-2013 at 08:15 PM. Reason: omg wow it's him
 
Old 05-22-2013, 08:22 PM   #43
s3phir0th115
LQ Newbie
 
Registered: Jan 2007
Distribution: Slackware
Posts: 22

Rep: Reputation: 3
For anyone that hasn't seen the changelog entry:

Quote:
Wed May 22 14:11:13 UTC 2013
patches/packages/linux-3.2.45/*: Rebuilt.
It appears a bad commit slipped into 3.2.45 and it's causing problems on
systems that use Intel graphics. The commit has been reverted in the kernel
source packages and the kernels and modules have been rebuilt. If you ran
into the black screen problem before, this should fix it up.
So, no need for manual fixes now, just do the upgrade again.
 
1 members found this post helpful.
Old 05-22-2013, 10:38 PM   #44
Eldarby
LQ Newbie
 
Registered: May 2011
Distribution: Arch
Posts: 25

Original Poster
Rep: Reputation: 1
nomodeset got me in, the new upgrade finalized the fix. Marking this solved! Thanks so much, everyone!
 
Old 05-22-2013, 10:52 PM   #45
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Originally Posted by Eldarby View Post
Should *all* kernel-related packages be blacklisted and installpkg'd by hand, or are there some I should still be using slackpkg/upgradepkg on instead? I know the kernel itself and probably the source too should be installpkg'd to have multiple versions, but would I want to also do the same with the firmware, headers, etc.? If I could get a breakdown of which packages to handle in which fashion that would really help.
You don't have to blacklist kernel-firmware since that is kernel version-agnostic (or nearly). kernel-headers doesn't need to be blacklisted either since you should always stick with whatever Slackware ships anyway, so you won't need to have side-by-side packages for that. kernel-modules, kernel-source, kernel-generic and kernel-huge are best blacklisted and dealt with manually using installpkg/removepkg (and not upgradepkg). If the kernel is rebuilt (patched or something), but is the same kernel version, then it will clobber the existing directories (/boot/vmlinuz-generic-$(uname -r), /lib/modules/$(uname -r), and /usr/src/linux-$(uname -r)), overwriting files, and will negate any benefit you get from manually installing the package -- but it will not harm anything since removepkg'ing the old package after everything works will make sure it doesn't remove any files present in the new package. It is unlikely, though, that just a patched version of the same kernel will cause too many problems. If they are different kernel versions (as in this past upgrade) then the old kernel will still remain fully functional, and the new kernel installed alongside it will really be independent. Just make sure you specify the explicit kernels in lilo.conf instead of using the /boot/vmlinuz symlink. Also note that if you do have two kernel versions installed and you then use upgradepkg, both kernels will be removed and the new kernel installed -- so you really should be vigilant about just not using upgradepkg ever for kernels to avoid that.
Quote:
Originally Posted by Eldarby View Post
Sorry to ask you to hold my hand, I just feel a lot safer asking someone experienced when it comes to anything kernel-related.
No problem -- one of the reasons I love Slackware is because you can do things like this (installing multiple kernel packages that would otherwise conflict) without having to worry about the package manager breaking.
 
  


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


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

Main Menu
Advertisement
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