On Sun, Jul 18, 2010 at 13:39, Andrei Popescu wrote:
> On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> > >
> > > Could you please elaborate on that? How can UUID fail if you have
> > > modules compiled in the kernel, since UUID is a property of the
> > > filesystem?
> >
> > Even if every driver
On Sb, 17 iul 10, 23:10:39, Anand Sivaram wrote:
> >
> > Could you please elaborate on that? How can UUID fail if you have
> > modules compiled in the kernel, since UUID is a property of the
> > filesystem?
>
> Even if every driver is compiled into the kernel, an initrd may be required
> to
> use
On Sat, Jul 17, 2010 at 12:23, Andrei Popescu wrote:
> On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> > >
> > It is necessary to use initrd image while using UUID. So UUID method may
> > not work with custom kernels where drivers are compiled in.
>
> Could you please elaborate on that? How ca
On Sat, Jul 17, 2010 at 12:23, Andrei Popescu wrote:
> On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> > >
> > It is necessary to use initrd image while using UUID. So UUID method may
> > not work with custom kernels where drivers are compiled in.
>
> Could you please elaborate on that? How ca
On Sb, 17 iul 10, 09:06:02, Anand Sivaram wrote:
> >
> It is necessary to use initrd image while using UUID. So UUID method may
> not work with custom kernels where drivers are compiled in.
Could you please elaborate on that? How can UUID fail if you have
modules compiled in the kernel, since U
On Fri, Jul 16, 2010 at 20:54, H.S. wrote:
> On 10-07-16 10:56 AM, H.S. wrote:
>
>> On 16/07/10 05:59 AM, Sunita Barve wrote:
>>
>>> I have been using debian 5.0.3. I had changed disk and had connected on
>>> two
>>> different machines. Now I am getting the following error
>>>
>>
>> I am in a sim
On 10-07-16 10:56 AM, H.S. wrote:
On 16/07/10 05:59 AM, Sunita Barve wrote:
I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error
I am in a similar situation.
kinit: trying to resume from /dev/sda5
kinit:No resume
On 16/07/10 05:59 AM, Sunita Barve wrote:
> I have been using debian 5.0.3. I had changed disk and had connected on two
> different machines. Now I am getting the following error
I am in a similar situation.
> kinit: trying to resume from /dev/sda5
> kinit:No resume image, doing normal boot...
>
I have been using debian 5.0.3. I had changed disk and had connected on two
different machines. Now I am getting the following error
kinit: trying to resume from /dev/sda5
kinit:No resume image, doing normal boot...
Target filesystem doesnt have /sbin/init.
run-init: /bin/sh: No such file or dire
will shed more light on the problem.
Regards,
Anim
> Subject: FW: FW: Kernel panic error
>
>
>
>
> > > From: Jerome R. Acks
> > > [mailto:[EMAIL PROTECTED]
> > > Sent: 24 October 2003 03:47
> > > To: Anim Asante
> > >
On Mon, Oct 27, 2003 at 06:45:28AM +, Anim Asante wrote:
> <[EMAIL PROTECTED]> wrote: >
> >
> > From: Jerome R. Acks
> > [mailto:[EMAIL PROTECTED]
> > Sent: 24 October 2003 03:47
> > To: Anim Asante
> > Cc: [EMAIL PROTECTED]
> > Subjec
--- "Asante, Emmanuel [ING-WBK]"
<[EMAIL PROTECTED]> wrote: >
>
> -Original Message-
> From: Jerome R. Acks
> [mailto:[EMAIL PROTECTED]
> Sent: 24 October 2003 03:47
> To: Anim Asante
> Cc: [EMAIL PROTECTED]
> Subject: Re: Kernel panic error
On Wed, Oct 22, 2003 at 11:10:02AM +0100, Anim Asante wrote:
> > > I have got a grub menu.lst file with a section of
> > the
> > > file looking like this
> > > ?root (hd1,0)
> > > ?kernel /vmlinuz root=/dev/hdb1
> > > ?boot
> > > ?
> > > When I restart my machine and select this option,
>
--- Anim Asante <[EMAIL PROTECTED]> wrote: > >
-Original Message-
> > From: Bill Marcum [mailto:[EMAIL PROTECTED]
> > Sent: 22 October 2003 07:01
> > To: [EMAIL PROTECTED]
> > Subject: Re: Kernel panic error
> >
> >
> > On T
> -Original Message-
> From: Bill Marcum [mailto:[EMAIL PROTECTED]
> Sent: 22 October 2003 07:01
> To: [EMAIL PROTECTED]
> Subject: Re: Kernel panic error
>
>
> On Tue, Oct 21, 2003 at 07:27:29AM +0100, Anim
> Asante wrote:
> > I have got a gru
On Tue, Oct 21, 2003 at 07:27:29AM +0100, Anim Asante wrote:
> I have got a grub menu.lst file with a section of the
> file looking like this
> root (hd1,0)
> kernel /vmlinuz root=/dev/hdb1
> boot
>
> When I restart my machine and select this option, the
> boot up process begins up
> to a poin
I have got a grub menu.lst file with a section of the
file looking like this
root (hd1,0)
kernel /vmlinuz root=/dev/hdb1
boot
When I restart my machine and select this option, the
boot up process begins up
to a point and it gives the following error message:
Warning: unable to open an initial
On Sun, Oct 13, 2002 at 10:13:24AM -0400, [EMAIL PROTECTED] wrote:
> Every so often (roughly about 15 minutes) I get the following error
> screen.
You're using a fairly recent computer. Try a new kernel image,
"apt-cache search kernel-image" to get a list of kernel images you can
try out. If th
System
Pentium III 733 Mz
512 Mb RAm
40GB Seagate Hard drive
RIVA TNT-2 Model 64 Graphics Card
Keyboard 105 Keys with extra buttons Internet, Sleep, and Email
Mouse with Two buttons and a wheel
Internal Modem card no details known
Dear All
I have just loaded Debian Linux 3.0 Woody on the above sys
Just an idea :)
Its not a scsi CDROM drive is it, have seen similar type problems with NT
booting of
scsi cdrom. If it is does the kernel have support for the scsi controller ???
Syrus Nemat-Nasser wrote:
> Hello folks.
>
> This is not Debian-specific, but my brother-in-law got a kernel panic
Hello folks.
This is not Debian-specific, but my brother-in-law got a kernel panic
while booting of a Linux installation CD:
>I got the following booting off of a CD while installing on a new
>machine.
>
> VFS: Cannot open root device 08:21
> Kernel panic: VFS: Unable to mount root fs on 08:2
Solved! The problem was a Kernel panic error on startup, just after resetting
the SCSI bus. Many thanks to Peter S. Galbraith, Bob McGowan, and Nathan Norman.
Norman both identified the problem as "the (in)famous AHA-2740/2840 boot
failure". He offered to build me a kernel but said h
Nathan E Norman wrote:
> On 21 May 1998, Paul Mackinney wrote:
>
> : Booting for the first time from recovery disk, I get the following
> : error just after it resets the SCSI bus:
> :
> : aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
> : scsi0: BRKADRINT error(0x1):
> : Illegal Hos
On 21 May 1998, Paul Mackinney wrote:
: Booting for the first time from recovery disk, I get the following
: error just after it resets the SCSI bus:
:
: aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
: scsi0: BRKADRINT error(0x1):
: Illegal Host Access
: Kernel panic: scsi0: BRKADRINT
Booting for the first time from recovery disk, I get the following error just
after it resets the SCSI bus:
aic7xxx: (aic7xxx_isr) Encountered spurious interrupt.
scsi0: BRKADRINT error(0x1):
Illegal Host Access
Kernel panic: scsi0: BRKADRINT, error 0x1, segaddr 0x0.
The system is an HP NetSer
25 matches
Mail list logo
