LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 02-27-2010, 01:56 PM   #1
sid77
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackintosh 12.1/current Slackware 13.0 Slackware64 13.0
Posts: 19

Rep: Reputation: 0
Slackware64-13.0 multilib can not build valid initrd for kernels 2.6.30


Hello all,
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-2.6.29.6 with an initrd set up using mkinitrd.conf
Everything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error.
On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds. Can anyone confirm this strange behaviour? In case, got any workaround or suggestions?

Thanks in advance for any help,
Marco
 
Old 02-28-2010, 10:17 AM   #2
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 237

Rep: Reputation: 30
The multilib capability doesn't affect the initrd setup process. The problem should be either in the links in /boot (System.map and so on) or in your lilo.conf. Did you try to get a suggestion of the mkinitrd command you need using '/usr/share/mkinitrd/mkinitrd_command_generator.sh -r'?
 
Old 02-28-2010, 02:50 PM   #3
sid77
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackintosh 12.1/current Slackware 13.0 Slackware64 13.0
Posts: 19

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by escaflown View Post
The multilib capability doesn't affect the initrd setup process.
I'd also say that, but...

Quote:
Originally Posted by escaflown View Post
The problem should be either in the links in /boot (System.map and so on) or in your lilo.conf. Did you try to get a suggestion of the mkinitrd command you need using '/usr/share/mkinitrd/mkinitrd_command_generator.sh -r'?
I can assure that mkinitrd options are ok as I copied them from a working machine without multilib, I also double check links whenever I install a new kernel. I'm pretty confident they're ok. By the way: I'm typing these very lines on a custom 2.6.29.6 kernel. The mkinitrd stuff is ok, really.
 
Old 02-28-2010, 03:44 PM   #4
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Slackware64-14.1 (multi-lib) KDE 4.11.4
Posts: 1,422

Rep: Reputation: 137Reputation: 137
I can confirm that you can build and boot an initrd.gz for kernel 2.6.32.7 and the ext4 filesystem using Slackware64-current with the multi-lib packages installed.

samac
 
Old 02-28-2010, 05:30 PM   #5
escaflown
Member
 
Registered: Apr 2009
Location: Canada
Distribution: Slackware
Posts: 237

Rep: Reputation: 30
Quote:
Originally Posted by sid77 View Post
I'd also say that, but...


I can assure that mkinitrd options are ok as I copied them from a working machine without multilib, I also double check links whenever I install a new kernel. I'm pretty confident they're ok. By the way: I'm typing these very lines on a custom 2.6.29.6 kernel. The mkinitrd stuff is ok, really.
Weird. I dual boot between a 32 bit version of slackware and a 64-bit-current version of slackware with multilib enabled without any problem.
 
Old 02-28-2010, 11:16 PM   #6
Cheesesteak
Member
 
Registered: Jun 2008
Distribution: Slackware
Posts: 100

Rep: Reputation: 24
How large is your initrd?

Did you try the option large-memory in your lilo.conf file?
 
Old 03-01-2010, 04:23 AM   #7
Martinezio
Member
 
Registered: May 2009
Location: Warsaw, Poland
Distribution: Slackware64-current
Posts: 191

Rep: Reputation: 32
Hi, I also have this issue, but I think, that it is combined rather with kernel, than glibc version. I had no problem with mkinitrd with some older kernels. This problem starts with 2.6.30 kernels.
Maybe some upgrade of mkinitrd tool is needed?
 
Old 03-01-2010, 05:21 AM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,238

Rep: Reputation: Disabled
Slackware-current has the 2.6.32.7 kernel and I can create initrd's without any problem (32-bit, 64-bit and multilib systems). Likewise, I don't see why Slackware-13.0 should not be able to create a wrorking initrd for newer kernel versions.
You can try upgrading to the mkinitrd package that is part of Slackware64-current, but if you do that, make sure you have a "rescue" entry in your /etc/lilo.conf that allows you to boot your computer in case the new mkinitrd does not work for Slackware 13.0.

Eric
 
Old 03-01-2010, 09:05 AM   #9
sid77
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackintosh 12.1/current Slackware 13.0 Slackware64 13.0
Posts: 19

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by Cheesesteak View Post
Did you try the option large-memory in your lilo.conf file?
Ok, this is probably it! I was so puzzled by this strange behaviour that I forgot to double check lilo.conf: in the old config file I had that option enabled, while the current one hasn't it.
I'll test it tonight or tomorrow and report back. Thanks to anyone who chimed in for help.

ciao
 
Old 03-02-2010, 02:11 AM   #10
Martinezio
Member
 
Registered: May 2009
Location: Warsaw, Poland
Distribution: Slackware64-current
Posts: 191

Rep: Reputation: 32
Quote:
Originally Posted by Martinezio View Post
This problem starts with 2.6.30 kernels.
OOooopsss... Damn me I was telling about 2.6.33 kernel, not 2.6.30. Mea maxima culpa Sorry.
 
Old 03-03-2010, 03:20 AM   #11
sid77
LQ Newbie
 
Registered: Mar 2008
Distribution: Slackintosh 12.1/current Slackware 13.0 Slackware64 13.0
Posts: 19

Original Poster
Rep: Reputation: 0
I confirm it was the missing "large-memory" option. thanks!
 
Old 03-03-2010, 03:32 AM   #12
Cheesesteak
Member
 
Registered: Jun 2008
Distribution: Slackware
Posts: 100

Rep: Reputation: 24
Awesome!
 
  


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
[SOLVED] Transcode will not compile in Slackware64-13.0, Multilib TSquaredF Slackware 9 04-07-2010 10:39 PM
[SOLVED] Google Earth Slackware64 Multilib mlangdn Slackware 20 03-19-2010 03:35 AM
[SOLVED] Slackware64-current multilib: Many improvements, few snags gargamel Slackware 7 11-15-2009 07:23 AM
[SOLVED] Slackware64 multilib - E17 compiling problem? kukibl Slackware 1 10-08-2009 10:50 AM
slackware64 + multilib or simply install 32-bit? [GOD]Anck Slackware 1 08-31-2009 03:51 AM


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