| 1 |
My guess is tha while inside the initrd a kenrel module was loaded and it was something that you needed to read the boot volume. Are you statically or modulely including your sata drivers?
|
| 2 |
Sent via BlackBerry from T-Mobile
|
| 3 |
|
| 4 |
-----Original Message-----
|
| 5 |
From: Harry Putnam <reader@×××××××.com>
|
| 6 |
|
| 7 |
Date: Wed, 10 Dec 2008 17:07:44
|
| 8 |
To: <gentoo-user@l.g.o>
|
| 9 |
Subject: [gentoo-user] Tragic kernel building for vmware gentoo guest on WinXP
|
| 10 |
|
| 11 |
|
| 12 |
I've started a new thread on my kernel troubles. I thought the thread
|
| 13 |
subject should be more indicative of the semi OT nature of the query.
|
| 14 |
|
| 15 |
Also thought it might make the information that accrues here more
|
| 16 |
findable for any future searchers.
|
| 17 |
|
| 18 |
Here is the general setup and the general problem:
|
| 19 |
|
| 20 |
vmware appliance made from gentoo-2008.0
|
| 21 |
|
| 22 |
|
| 23 |
I downloaded this appliance from a friendly sight that has all kinds.
|
| 24 |
The appliance was built in July and so needed some updating. I
|
| 25 |
|
| 26 |
www.bagvapp.com
|
| 27 |
|
| 28 |
So cutting to the chase here. All software updated nicely but when I
|
| 29 |
started fooling with the kernel I hit a brick wall.
|
| 30 |
|
| 31 |
The original is 2.6.24-r8. Apparently built with genkernel as it has
|
| 32 |
just about everthing possilbe enabled.
|
| 33 |
|
| 34 |
The original setup was rigged to boot with an initrd
|
| 35 |
(from grub)
|
| 36 |
|
| 37 |
title=linux-2.6.24-gentoo-r8
|
| 38 |
root (hd0,0)
|
| 39 |
kernel /kernel-genkernel-x86-2.6.24-gentoo-r8
|
| 40 |
root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sdb3
|
| 41 |
initrd /initramfs-genkernel-x86-2.6.24-gentoo-r8 vga=0x317
|
| 42 |
|
| 43 |
And originally used /dev/sda3 for root.
|
| 44 |
|
| 45 |
It worked just fine. But none of my attempts to bring the kernel up
|
| 46 |
to date have worked. All failing with a error message something like:
|
| 47 |
`/dev/sdb3 is not a valid device'.
|
| 48 |
|
| 49 |
But of course it is because reverting to the original kernel allows a
|
| 50 |
successful boot.
|
| 51 |
|
| 52 |
You'll notice I've since moved root from /sda3 to sdb3... expanding
|
| 53 |
everthing. That is not the cause of the problem though since the
|
| 54 |
original kernel boots just fine with the edit to /dev/sdb3 as root.
|
| 55 |
|
| 56 |
I will post exact error messages in a bit but I'd gotten rid of the
|
| 57 |
extra sources.. and was about to give up messing with this.
|
| 58 |
|
| 59 |
I'm redownloading the latest gentoo-source and will post what ever
|
| 60 |
errors occur with it. I'll build using the old kernel config as
|
| 61 |
basis. And ditch the initrd.
|
| 62 |
|
| 63 |
(hours later)
|
| 64 |
|
| 65 |
Looks like I fogot to mail the message above so even better... Now I
|
| 66 |
have a screen shot of the messages.
|
| 67 |
|
| 68 |
I've compiled 2.6.27-r5 using the config that works with 2.6.24-r8 as
|
| 69 |
the basis. I did prune out a few things... all wireless some hid and
|
| 70 |
most usb.
|
| 71 |
|
| 72 |
This kernel fails as I expected and here is small screen shot of the
|
| 73 |
error. It appears something is lacking that lets the kernel know that
|
| 74 |
/dev/sda1 (boot) and /dev/sdb3 are valid /boot and /
|
| 75 |
|
| 76 |
Here are the grub lines:
|
| 77 |
|
| 78 |
title=/dev/sda1 hp 2.6.27-r5 NO INTITRD
|
| 79 |
root (hd0,0)
|
| 80 |
kernel /kernel-2.6.27-r5 root=/dev/sdb3 video=vesafb:mtrr3,ywrap vga=0x317
|
| 81 |
|
| 82 |
Screen shot of boot messages: |
Archives