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 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...
>
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 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
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
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 he couldn't d
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
16 matches
Mail list logo
