LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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-25-2013, 09:15 PM   #61
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45

Quote:
Originally Posted by volkerdi View Post
You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.
Thanks, Pat I really appreciate your response.
 
Old 05-26-2013, 01:59 AM   #62
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 volkerdi View Post
You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.
Hmmm .... weird. I used the binary kernel packages from -current and was able to successfully recompile the VirtualBox kernel module (I have even tested VirtualBox and it works) but you are obviously much more experienced with this stuff so to avoid potential problems in the future I will recompile 3.8.13, just to be safe.

Thanks for the tip. I learned something new!

EDIT: Ok, 3.8.13 is now recompiled. So I have the system just right for me.

Last edited by ruario; 05-26-2013 at 04:16 PM.
 
Old 05-26-2013, 02:58 AM   #63
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}
Posts: 215

Rep: Reputation: 122Reputation: 122
Fine with 3.4.47

Quote:
Originally Posted by ruario View Post
I only complied 3.4.47 (generic) since there is no package, for 3.8.13 I just used the packages from -current on 14.0. No problems. EDIT: I also compiled up 3.9.4 and it seemed fine as well.
I built the 3.4.47 (huge) kernel using Patrick's config and left the machine running overnight, after launching lots of applications and mounting two USB hard drives. The system seems to be rock-solid again and I couldn't see any issues so far. I guess the 3.4.x kernel has matured since the release of Slackware 14.0.

Now I'll see what happens with 3.8.13 from -current, but since 3.8.x is EOL and 3.4.x has long term support, I think I'll stick to the latter.

Anyway, I found ruario's and Patrick's tips most helpful, thanks!

Philip
 
Old 05-26-2013, 03:48 AM   #64
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 Philip Lacroix View Post
Now I'll see what happens with 3.8.13 from -current, but since 3.8.x is EOL and 3.4.x has long term support, I think I'll stick to the latter.
F.Y.I. (just in case you missed the news) the 3.8.x kernel will be receiving extended support from the Ubuntu kernel team (since Ubuntu 13.04 "Raring" uses this kernel). So you will continue to be able to get security updates until August 2014 at least. Granted this is a couple of months less than the projected EOL for 3.4.x (October 2014) but still long enough that you might want to give 3.8.13 a serious consideration if it performs better for you (it does for me).

EDIT: By the way new releases of stable patches for the 3.8.x kernel will be announced at kernel-team@lists.ubuntu.com. You might want to follow this if Pat changes his mind and decides against 3.8.x for the next Slackware stable release.

Last edited by ruario; 05-26-2013 at 03:56 AM.
 
1 members found this post helpful.
Old 05-26-2013, 05:08 AM   #65
Philip Lacroix
Member
 
Registered: Jun 2012
Distribution: Slackware{,-current}
Posts: 215

Rep: Reputation: 122Reputation: 122
Fine with 3.8.13 too

Quote:
Originally Posted by ruario View Post
F.Y.I. (just in case you missed the news) the 3.8.x kernel will be receiving extended support from the Ubuntu kernel team (since Ubuntu 13.04 "Raring" uses this kernel). So you will continue to be able to get security updates until August 2014 at least. Granted this is a couple of months less than the projected EOL for 3.4.x (October 2014) but still long enough that you might want to give 3.8.13 a serious consideration if it performs better for you (it does for me).

EDIT: By the way new releases of stable patches for the 3.8.x kernel will be announced at kernel-team@lists.ubuntu.com. You might want to follow this if Pat changes his mind and decides against 3.8.x for the next Slackware stable release.
Much appreciated, thanks! This sounds interesting and I saved a bookmark of it. I don't see any issues with 3.4 so far, but I'll keep an entry in lilo for 3.8.13 as well, if it works.

EDIT: I rebuilt the 3.8.13 kernel on Slackware 14.0 using config-generic-smp from -current, and it really seems to be another good option to solve the mentioned 3.2.45 issues.

Best regards,
Philip

Last edited by Philip Lacroix; 05-26-2013 at 01:42 PM.
 
Old 05-26-2013, 02:10 PM   #66
rpeter
LQ Newbie
 
Registered: Jan 2008
Location: Hungary
Distribution: Slackware
Posts: 7

Rep: Reputation: 0
I also have the same problem with the rebuilt 3.2.45 kernel as Ruario (and others).
After command startx different window managers (blackbox, fluxbox, kde) were frozen, I couldn't use the keyboard and needed to do forced reboot.
My CPU is also Intel Core i3.
I installed back the old 3.2.29 kernel temporarily.
 
Old 05-26-2013, 07:57 PM   #67
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 135

Rep: Reputation: 20
I was going to post this in a separate thread but it seems related so I'll add it here for reference.

I use a virtualbox guest vm that I clone and copy to a desktop and a laptop as needed (for experimentation, testing stuff etc.)
The guest runs Slackware 14.0 with the 3.2.29 stock kernel, upgrading to 3.2.45 was straightforward as usual but launching X within the guest brought up a frozen black screen with a blinking cursor at the top left corner. I rebooted the guest and tried again after uninstalling/reinstalling the guest additions but that didn't help.

Aside from reverting to 3.2.29, found only these 2 workarounds:
-remove the guest additions, X starts working again (issue re-occurs if I reinstall the additions)
-upgrade to 3.8.13, this apparently resolves everything with no issues so far, guest + X + additions working smoothly.


Quote:
Originally Posted by volkerdi View Post
You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.
Thanks for the tip.
 
1 members found this post helpful.
Old 05-27-2013, 12:58 PM   #68
gonzas
LQ Newbie
 
Registered: Aug 2009
Distribution: Slackware 14.0
Posts: 5

Rep: Reputation: 0
Quote:
Originally Posted by dr.s View Post
I use a virtualbox guest vm that I clone and copy to a desktop and a laptop as needed (for experimentation, testing stuff etc.)
The guest runs Slackware 14.0 with the 3.2.29 stock kernel, upgrading to 3.2.45 was straightforward as usual but launching X within the guest brought up a frozen black screen with a blinking cursor at the top left corner. I rebooted the guest and tried again after uninstalling/reinstalling the guest additions but that didn't help.

Aside from reverting to 3.2.29, found only these 2 workarounds:
-remove the guest additions, X starts working again (issue re-occurs if I reinstall the additions)
-upgrade to 3.8.13, this apparently resolves everything with no issues so far, guest + X + additions working smoothly.
I have the same issue. Have you found what causes the problem? I would like to keep both the additions and 3.2.45 :-)
Thank you.
 
Old 05-27-2013, 01:27 PM   #69
Cesare
Member
 
Registered: Jun 2010
Posts: 30

Rep: Reputation: 32
Quote:
Originally Posted by Cesare View Post
Back to 3.2.29 for me.
...and forward to 3.4.47

As other users did before me, I built 3.4.47 with Pat's 3.4.11 config and the result has been working fine so far - no glitches, no crashes.

After the upgrade, all of my Slackware VMs (QEMU-KVM) paniced immediately and wouldn't boot any longer. This was easily fixed by replacing "-cpu native" with "-cpu kvm64,+sse3" in my run script (I need the SSE3 capability and "native" was the easiest way to get it).

If newer kernels don't work for you, rebuilding with this patch should be all you need to get a non-exploitable 3.2.29.
 
Old 05-27-2013, 01:41 PM   #70
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
Quote:
Originally Posted by volkerdi View Post
You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.
Ahhh okay... I get it now. When you offer a new kernel package in stable you use the same version of gcc that was used at the time of release, which is why 3.2.45 works fine for me, but if I go any further I may run into problems. Took me a while to figure it out but I'm on the same page now.
 
Old 05-28-2013, 12:20 AM   #71
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 135

Rep: Reputation: 20
Quote:
Originally Posted by gonzas View Post
I have the same issue. Have you found what causes the problem? I would like to keep both the additions and 3.2.45 :-)
Thank you.
Just guessing something must have been introduced in 3.2.45 that makes guest additions fail, X + 3.2.45 without the additions worked well. I'd be curious to try again when Virtualbox releases an update.

I uninstalled/reinstalled and tested the guest additions with other kernels (3.4.x and 3.8.x) in the same VM and everything worked as expected.
 
Old 05-28-2013, 05:54 PM   #72
ecoslacker
LQ Newbie
 
Registered: Feb 2011
Location: Mexico
Distribution: Slackware
Posts: 17

Rep: Reputation: 0
Cannot enter to X session with the new rebuild 3.2.45 kernel

Sometimes the graphical session in KDE gets frozen and sometimes I cannot enter to graphical session even, with the new rebuild 3.2.45 kernel.

Little help: How can I install back the old 3.2.29 kernel?

Thanks
 
Old 05-28-2013, 06:16 PM   #73
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 ecoslacker View Post
Sometimes the graphical session in KDE gets frozen and sometimes I cannot enter to graphical session even, with the new rebuild 3.2.45 kernel.

Little help: How can I install back the old 3.2.29 kernel?

Thanks
Is this with Intel graphics again?

I've been pointed to another suspicious commit and might be forced to do a third build. Giving much credit to whether a kernel series is designated LTS isn't looking like it matters as much as we may have thought. If 3.2.x had been dead, we'd have patched the CVE and had it right the first time.
 
4 members found this post helpful.
Old 05-28-2013, 09:49 PM   #74
dc_eros
Member
 
Registered: Nov 2006
Distribution: Slackware
Posts: 292

Rep: Reputation: 39
FYI, I have updated to the kernel patch few days after the last 14.0 update (the rebuilt one). I still encounter freeze issue with my Intel HD Graphics 3000.

I decided to downgrade to the original 3.2.29 to make my machine usable again.

@ecoslacker - pass "nomodeset" at lilo prompt so you can work on your machine with minimal graphics then download the original 3.2.29 kernels and install it again via installpkg.
 
Old 05-29-2013, 10:36 AM   #75
PrinceCruise
Member
 
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 14.1/Current, CentOS 6.5/7.0
Posts: 792

Rep: Reputation: Disabled
So if I'm not wrong, the issue with upgrading kernel to 3.2.45 is still pretty much there even after the second rebuild?
I've still not upgraded my 32 bit stable box with Intel HD graphics, but I have downloaded that second rebuild already.

Regards.
 
  


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 06:20 PM.

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