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.
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,
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-bl
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
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.
VFS: Cannot open root device "hda1" or unk
<#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.
>
> VFS: Cannot open root device "hda1" or unknown-
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.
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)
The ot
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
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 :
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.
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 comp
11 matches
Mail list logo