Re: custom kernel boot problem: can't access tty
SOLUTION: to can't access tty; job control turned off Apologies for answering my own post, but this seems to be a problem many people have had. For some reason (there could be many) the boot kernel can't mount the root file system and hence cannot find all devices and tools to run the login. In my case booting a custom kernel there were no modules for squashfs and unionfs so those file systems which include the root could not be moutned. Installed squashfs-source and unionfs-source, build the kernel the build the extra modules for squashfs and unionfs with make install. Kernel must be built first as squashfs and uniofs make needs the build from /lib/modules/kernel-version/build. Ran update-initramfs -u -k custom kernel version to make the initrd. Rebuilt the compressed file system. Now linux boots and runs live from a USB memory stick with a custom kernel. Hope this helps others with the same problem. Cheers, Rob Key Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
custom kernel boot problem: can't access tty
Hi, I compiled a debian custom kernel 2.6.18 to boot a USB flash drive. The stock kernels work perfectly, but my custom kernel mounts the root fs and then gives the error message: /bin/sh Can't access tty; Job control stopped The booting process stops. The console , tty devices are all there, stock kernel works perfectly what is wrong? Thanks Rob Key Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
Kernel boot problem?
Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip The other two kernels i did get stuck on this. snip VFS: Cannot open root device hda1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip The only difference in the two messages is the unknown-block section. I used the old .config file so i would have what i needed for the new kernel and all i added was select a few sound card things. Have i added something that i shouldnt have ? or something i have missed ? I have checked the root= line in the grub config and it reads the same as the current kernel which is 2.6.7-1 and the one i am trying to compile is 2.6.8 Thanks in advance :) Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
#secure method=pgp mode=sign -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grant [EMAIL PROTECTED] writes: Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBNLybUzgNqloQMwcRAoDBAKCNsyVxXUMAZ7x+wU7ar+OV/snaXACfd8Ny vM6MkC8zmBqqXXbJXSclxSM= =4R3O -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
Paul Johnson wrote: #secure method=pgp mode=sign -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grant [EMAIL PROTECTED] writes: Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBNLybUzgNqloQMwcRAoDBAKCNsyVxXUMAZ7x+wU7ar+OV/snaXACfd8Ny vM6MkC8zmBqqXXbJXSclxSM= =4R3O -END PGP SIGNATURE- Hey, Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... Thanks. Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
On Wed, Sep 01, 2004 at 01:43:47AM +0100, Grant wrote: Paul Johnson wrote: Grant [EMAIL PROTECTED] writes: I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... VFS: Cannot open root device hda1 or unknown-block(3,1) Try compiling your IDE controller and drive drivers into the kernel. (if you're one of the 1e-something of us who uses SCSI, change the directions.) -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
Stefan O'Rear wrote: On Wed, Sep 01, 2004 at 01:43:47AM +0100, Grant wrote: Paul Johnson wrote: Grant [EMAIL PROTECTED] writes: I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... VFS: Cannot open root device hda1 or unknown-block(3,1) Try compiling your IDE controller and drive drivers into the kernel. (if you're one of the 1e-something of us who uses SCSI, change the directions.) Hey, *slaps forhead!* I didnt think someone said about doing that for the filesystems, i never thought about it might need it for other things, i guess that initrd is quite important if you use modules for your kernel... Anyways i will give that a try. Thanks again Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel boot problem
Hi, hope you can boot with your previous kernel or from disk. If so, look for error messages in the log files: /var/log/dmesg, kern.log or syslog. HTH, Joachim On Fri, Mar 15, 2002 at 06:21:54PM +0100, [EMAIL PROTECTED] wrote: I can't boot my new kernel 2.4.10, the boot process looks like : LILO Loading Linux ... Uncompressing Linux ... Ok booting the kernel and then nothing else ! -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln
Re: kernel boot problem
On Fri, Mar 15, 2002 at 06:21:54PM +0100, [EMAIL PROTECTED] wrote:
I can't boot my new kernel 2.4.10, the boot process looks
like :
LILO Loading Linux ...
Uncompressing Linux ... Ok booting the kernel
and then nothing else !
Look for Debian install disk set (CD/FD) and boot from it with rescue
root=/dev/hdx with x being your real root partition number.
Then set up lilo and mbr(if used).
lilo: edit /etc/lilo.conf and run lilo.
mbr: read man install-mbr.
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D
Visit Debian reference http://www.debian.org/doc/manuals/quick-reference/
There are 6 files: index.{en|fr|it}.html quick-reference.{en|fr|it}.txt
I welcome your constructive criticisms and corrections.
kernel boot problem
I can't boot my new kernel 2.4.10, the boot process looks like : LILO Loading Linux ... Uncompressing Linux ... Ok booting the kernel and then nothing else ! thanks for help.
Kernel boot problem!
When I boot up my Linux box it get's stuck on LILO Loading Linux... This has never happened before. I just compiled and installed a sound supporting kernel, but that has been working until now. I installed my kernel backup but it still does the same thing. The only way that I can boot my computer is with the bootdisk that I created during setup. Jeff __ Get Your Private, Free Email at http://www.hotmail.com
