You are not logged in.
- Topics: Active | Unanswered
#26 2005-12-14 17:56:40
- Romashka
- Forum Fellow
- Registered: 2005-12-07
- Posts: 1,054
Re: I cant boot with 2.6.14 from testing
I have VMware Workstation 5.5 :-)
My VMware machine has one IDE disk.
other specifications from VMware Manual:
Chip Set
• Intel 440BX-based motherboard
• NS338 SIO
• 82093AA IOAPIC
I cannot post my mkinitrd.conf because I cannot grab it from VMware (yet).
I can grab only .bmp image but this forum does not allow attaching of files.
I'll try to send my config files tomorrow. But there is nothing special. I heve just disabled booting from SCSI and USB.
I have tried both full and auto images.
It works both newest and older kernel but only with old mkinitrd 1.01-18.
There must be a bug in mkinitrd, introduced between 1.01-23 and 1.01-18.
Please examine changes from 1.01-18 to 1.01-23.
to live is to die
Offline
#27 2005-12-14 22:13:59
- apeiro
- Daddy
- From: Victoria, BC, Canada
- Registered: 2002-08-12
- Posts: 771
- Website
Re: I cant boot with 2.6.14 from testing
Hi Romashka,
Ah, I have a feeling this is LILO's fault -- it uses actual device numbers rather than the /dev pathnames, so when mkinitrd tries to parse /proc/cmdline for the root device, it fails.
I will test and get back to you.
Offline
#28 2005-12-14 22:36:09
- apeiro
- Daddy
- From: Victoria, BC, Canada
- Registered: 2002-08-12
- Posts: 771
- Website
Re: I cant boot with 2.6.14 from testing
Yes, this is indeed the problem.
Short-term fix: Use GRUB
I'll get back to you with a real fix.
Offline
#29 2005-12-15 01:15:52
- apeiro
- Daddy
- From: Victoria, BC, Canada
- Registered: 2002-08-12
- Posts: 771
- Website
Re: I cant boot with 2.6.14 from testing
Hi Romashka,
I think I've squashed this bug. Please try mkinitrd-1.01-24.
Offline
#30 2005-12-15 01:39:24
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: I cant boot with 2.6.14 from testing
To judd: http://www.zeroflux.org/pics/jam1/IMG_0357.jpg it is a very very very pretty girl, so beautiful smile.
It's a trap! That's a guy!
(kidding)
Offline
#31 2005-12-15 09:30:21
- Romashka
- Forum Fellow
- Registered: 2005-12-07
- Posts: 1,054
Re: I cant boot with 2.6.14 from testing
To apeiro:
Ah, I have a feeling this is LILO's fault -- it uses actual device numbers rather than the /dev pathnames, so when mkinitrd tries to parse /proc/cmdline for the root device, it fails.
Yes, but old mkinitrd-1.01-18 works when /proc/cmdline has 303 as root.
I just wonder what change made it not working in mkinitrd-1.01-23.
Anyway, right now I in the middle of upgrade process. :-)
I hope that with the new mkinitrd-1.01-24 the problem is fixed.
Thanks for fast bug-squashing!
Mmmm... I am starting to love bug-hunting! :twisted:
to live is to die
Offline
#32 2005-12-15 09:57:25
- Romashka
- Forum Fellow
- Registered: 2005-12-07
- Posts: 1,054
Re: I cant boot with 2.6.14 from testing
It works! mkinitrd-1.01-24 is OK! Finally!
Thanks, Judd!
to live is to die
Offline
#33 2005-12-15 10:18:03
- Romashka
- Forum Fellow
- Registered: 2005-12-07
- Posts: 1,054
Re: I cant boot with 2.6.14 from testing
Found another bug. :twisted:
mkinitrd ignores all modules in ADD_MODULE array except the firsrst one.
to live is to die
Offline
#34 2005-12-15 16:24:07
- Samuel Cengel
- Member
- From: Slovak Republic
- Registered: 2005-11-19
- Posts: 55
Re: I cant boot with 2.6.14 from testing
To phrakture: 
Offline
#35 2005-12-15 16:28:24
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: I cant boot with 2.6.14 from testing
Found another bug. :twisted:
mkinitrd ignores all modules in ADD_MODULE array except the firsrst one.
Hmm, that's probably because it's not supposed to be an array.
ADD_MODULE="a b c d e"works for me - if it's an array, referencing it only returns the first item.
I guess one or the other should be chosen and the actual syntax should be made more clear.
Offline
#36 2005-12-15 16:37:55
- Samuel Cengel
- Member
- From: Slovak Republic
- Registered: 2005-11-19
- Posts: 55
Re: I cant boot with 2.6.14 from testing
yes
..........="moduleX moduleY"
Offline
#37 2005-12-15 16:44:20
- Romashka
- Forum Fellow
- Registered: 2005-12-07
- Posts: 1,054
Re: I cant boot with 2.6.14 from testing
Ooops, sorry. :oops:
But there was ADD_MODULE=() in my rc.conf so I just added module names between brackets.
to live is to die
Offline
#38 2005-12-15 18:17:50
- apeiro
- Daddy
- From: Victoria, BC, Canada
- Registered: 2002-08-12
- Posts: 771
- Website
Re: I cant boot with 2.6.14 from testing
Yes, but old mkinitrd-1.01-18 works when /proc/cmdline has 303 as root.
I just wonder what change made it not working in mkinitrd-1.01-23.
That's because the older mkinitrd versions would hardcode your root device into the /linuxrc boot script.
In the latest version, I have swiped nash's mkrootdev routine and added it as a busybox applet, which we can use in /linuxrc. It scans /proc/sys/kernel/real-root-dev and creates a /dev/root which points to your actual root device, whatever it may be. This is more flexible and allows us to package an initrd-full with the kernel package itself.
Offline