On Tue, 2005-01-04 at 02:05 +0700, Muhammad Reza wrote: > Eric Gaumer wrote: > >>>>Dear Lists, > >>>> > >>>>I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is > >>>>what exactly i did... > >>>> > >>>>debian:/usr/src# ln -s kernel-source-2.6.8 linux > >>>>debian:/boot# cd /usr/src/linux > >>>>debian:/usr/src/linux# cp /root/config .config > >>>>debian:/usr/src/linux#patch -p1 </root/bootsplash-3.1.6-2.6.8.diff > >>>>debian:/usr/src/linux#make menuconfig > >>>>debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image > >>>>----sucess----- > >>>>debian:/usr/src/linux# cd ../ > >>>>debian:/usr/src# ls > >>>>kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches > >>>>kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux > >>>>debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb > >>>>---sucess--- > >>>> > >>>>but new compile kernel wont boot with this error... > >>>> > >>>>RAMDISK: cramfs file system found at block 0 > >>>>RAMDISK: loading 3620 block [1 disk] into ramdisk done.. > >>>>Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) > >>>> > >>>>please help me...to solved this problem.. > >>>>here is .config and menu.lst in attach.... > >>>> > >>>> > >>>> > >>>> > >>>> > >>>Since you are using a ramdisk, it would be helpful if you could post the > >>>contents of the loadmodules file on the ramdisk itself. You are most > >>>likely missing some modules needed to mount the filesystem since (3,1) > >>>is hda1. > >>> > >>>]$ mount -o loop /boot/initrd-xxx /mnt/tmp > >>>]$ cat /mnt/tmp/loadmodules > >>> > >>>lspci may also help. > >>> > >>>What kernel are you currently running? Any special file system stuff > >>>like RAID or SATA? > >>> > >>> > >>> > >>> > >>> > >>Thanks for good advice > >> > >>this differnet betwen 2.4.7 and 2.6.8 loadmodules.. > >> > >>I'm now confused, in my .config for 2.6.8 kernel (attach..) , all module > >>that need it already enabled, fyi i get this .config from Suse-9.1 > >> > >>I dont have spesial file system like you said, i just this kernel to be > >>portable... > >> > >> > >> > > > >Okay ata_piix leads me to believe you are using SATA. Is this correct? > >The new API (libata) scans for drives on the SCSI bus. Try > >root=/dev/sda1 (edit the grub entry at boot) > > > > > > > Sorry, is not correct, my drive is hda ... >
Are using SATA? It looks like mkinitrd is saying yes. If you are then your drive is no longer hda. -- Eric Gaumer <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
