Re: make-kpkg and 2.4.16
On Tue, Nov 27, 2001 at 01:04:33PM -0800, Adam Shand wrote:
|
| > Likely you didn't include support for your root fs or the hardware
| > controlling the disk. I once left out support for my IDE controller.
| > It didn't work out too well :-).
|
| hrm, i don't think so and i just doubled checked. i copied my .config
| from my 2.4.14 kernel (which works just fine) to the new kernel tree and
| ran "make oldconfig" and answered "m" to everything i could and "n" to
| everything else.
|
| under filesystems both ext3 and ext2 are enabled. under block devices
| everything is a module except initrd (and a couple weird things).
|
| but for some reason it can't find my initrd image even though it exists
| where menu.lst says it does.
|
| here's the actual error message i get (can't cut and paste so there might
| be a typo):
|
| Linux IP multicast router 0.06 plus PIM-SM
| RAMDISK: Couldn't find valid RAM disk image starting at 0.
| Freeing initrd memory: 3348k freed
| request_module[block-major-3]: Root fs not mounted
| VFS: Cannot open root device "hda2" or 03:02
| Please append a correct "root=" boot options
| Kernel panic: VFS: Unable to mount root fs on 03:02
|
| grub config is identical to my working 2.4.14 config (except of course
| pointing to the 2.4.16 initrd and vmlinuz images). my root disk is hda2.
|
| it looks like it can't find the initrd file. with initrd what cannot
| be compiled as a module?
Did you include "--initrd" in the make-kpkg command?
-D
--
"Don't use C; In my opinion, C is a library programming language
not an app programming language." - Owen Taylor (GTK+ developer)
Reply to: