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
 
LinkBack Search this Thread
Old 04-14-2009, 10:47 AM   #1
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
New current kernel 2.6.29.1 on VirtualBox


I've just updated my virtual version of Slackware current which updated the kernel to version 2.6.29.1. I run this in VirtualBox.

It now hangs on boot up when loading the kernel. I have booted using a CD image, chrooted and re-ran lilo to be sure and updated VirtualBox to version 2.2.0 r45846 to try and fix this but no joy.

Prior to this I was running current with the old kernel as I hadn't updated my copy for a little while - version 2.6.28.8 was fine.

Anyone running the new current updates in VirtualBox or any ideas ?
 
Old 04-15-2009, 11:16 AM   #2
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
In the interest of continuity I should let you know I have fixed this - I'm happy again ! I had to boot using a 12.2 install CD and create a new initrd for the VM and rerun lilo with settings for the generic kernel in place. It then booted and I ran "slackpkg install-new" on the VM which found several packages. I fiddled with the initrd for a while and reran mkinitrd. It now boots with the generic or hugesmp.s kernels. Even my updated version of KDE 4 runs OK which it didn't before ! Happy days
 
Old 04-15-2009, 11:43 AM   #3
Noddegamra
LQ Newbie
 
Registered: Feb 2009
Location: California
Distribution: Slackware
Posts: 20

Rep: Reputation: 0
Thanks for the update! Just yesterday I installed -current in VirtualBox and was having the same problem.
 
Old 04-15-2009, 12:09 PM   #4
joutlancpa
Member
 
Registered: Apr 2009
Location: Orlando, FL
Distribution: Scientific Linux 6 x64
Posts: 211
Blog Entries: 1

Rep: Reputation: 31
Quote:
Originally Posted by bgeddy View Post
In the interest of continuity I should let you know I have fixed this - I'm happy again ! I had to boot using a 12.2 install CD and create a new initrd for the VM and rerun lilo with settings for the generic kernel in place. It then booted and I ran "slackpkg install-new" on the VM which found several packages. I fiddled with the initrd for a while and reran mkinitrd. It now boots with the generic or hugesmp.s kernels. Even my updated version of KDE 4 runs OK which it didn't before ! Happy days
What does slackpkg-install-new do? i.e. what's the purpose? I'm getting ready to reinstall if I can't get my system back up...thanks
 
Old 04-15-2009, 04:48 PM   #5
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Thanks for the update! Just yesterday I installed -current in VirtualBox and was having the same problem.
Oh dear - sorry to hear that ! Overall I'm not sure what actually fixed this - as is so often the case when things go wrong I was just mucking about with things late into the night and today I thougt "right - I'm going to fix this and be logical about the process". With hindsight I would have been more careful with the update as this was my first time trying slackpkg. I usually make my own update process given the contents of the current Changelog.txt and be very precise about things - especially when kernel or glibc updates are around.

If I can assist in any way I will try - maybe you could post more information. If there is any advice it would be to ensure kernel and kernel modules are updated correctly and lilo updates are correct.

Quote:
What does slackpkg-install-new do? i.e. what's the purpose? I'm getting ready to reinstall if I can't get my system back up...thanks
@thezoid - I have seen your thread about generic kernel update problems. I hope you have kept the huge kernel in place as that worked for you. It's all about building the initrd right and updating lilo. It's not hard but to the uninitiated there are hurdles to overcome. I'll follow your thread and help if I can.

Anyway, "slackpkg" is a relatively new addition to Slackware which is a script to update the stock Slackware packages from a mirror amongst other things. Have a look at "man slackpkg" for more information. Traditionally I would tackle this by keeping a copy of the /patches and /current trees and updating from them. Now this is very much easier with the new tool.
 
Old 04-15-2009, 07:27 PM   #6
Noddegamra
LQ Newbie
 
Registered: Feb 2009
Location: California
Distribution: Slackware
Posts: 20

Rep: Reputation: 0
Quote:
Originally Posted by bgeddy View Post
Oh dear - sorry to hear that ! Overall I'm not sure what actually fixed this - as is so often the case when things go wrong I was just mucking about with things late into the night and today I thougt "right - I'm going to fix this and be logical about the process". With hindsight I would have been more careful with the update as this was my first time trying slackpkg. I usually make my own update process given the contents of the current Changelog.txt and be very precise about things - especially when kernel or glibc updates are around.

If I can assist in any way I will try - maybe you could post more information. If there is any advice it would be to ensure kernel and kernel modules are updated correctly and lilo updates are correct.
Actually, it was pretty much just that lilo didn't update correctly when I installed. I guess I didn't pay attention to if it succeeded or failed (I was very tired and just wanted to finish it before bed).

I had originally upgraded it from 12.2. In 12.2, I tried upgrading the kernel to 2.6.29.1 just for the fun of it, but for some reason it wouldn't boot. Not from a lack of an initrd (ext2/3/4 were compiled in). The kernel just wouldn't load at all, just sitting there after the lilo prompt at a black screen. So I decided to just jump in and try -current because I never really had before.

When I tried booting after the installation, lilo gave me the two options from the 12.2 setup (Linux, the default, and Linux-new, the 2.6.29.1 kernel). It didn't matter which one I selected (even though the Linux entry should have pointed to /boot/vmlinuz, the same as in -current), it would just sit at the black screen.

So I took your advice, booted from the CD, then chrooted in an re-ran lilo. Everything is just peachy now.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Virtualbox kernel modules won't load after updating kernel in openSUSE 11.0 JamesHall Suse/Novell 6 02-03-2009 04:36 PM
Can't Compile VirtualBox 1.6.6 In Slackware Current Woodsman Slackware 8 12-18-2008 02:36 PM
virtualbox kernel donsimak Linux - Kernel 1 12-18-2008 01:05 AM
virtualbox kernel Brian H Linux - Newbie 14 08-26-2008 05:47 AM
Cannot run Virtualbox in Custom Kernel davcefai Debian 7 05-28-2008 11:29 PM


All times are GMT -5. The time now is 03:30 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