On 18 Jun 2002, Gordon Messmer wrote:
> Seems very odd. It's the same error I got when trying to boot from a
> DAC960 controller. The problem, in my case, was that the kernel doesn't
> recognize the DAC960's device names when it's parsing its parameters.
> In order to correct the problem, I had
Seems very odd. It's the same error I got when trying to boot from a
DAC960 controller. The problem, in my case, was that the kernel doesn't
recognize the DAC960's device names when it's parsing its parameters.
In order to correct the problem, I had to pass the kernel the hex values
of the majo
On Mon, 17 Jun 2002, Matthew Saltzman wrote:
> On 17 Jun 2002, Gordon Messmer wrote:
>
> > On Mon, 2002-06-17 at 11:25, Matthew Saltzman wrote:
> > > I've had no replies yet, so I will ask again.
> > >
> > > On booting with the 2.4.9-34 kernel, I get the message in the subject
> > > line. The er
On Fri, 14 Jun 2002, I wrote:
> OK I just started having this problem also.
>
> /initrd exists, / is not full, permissions on /sbin/init look OK.
>
> The problem occurs with the 2.4.9-34 and 2.4.9-31 kernels, but not the
> 2.4.7-10 kernel that shipped with 7.2 originally.
One more piece of infor
OK I just started having this problem also.
/initrd exists, / is not full, permissions on /sbin/init look OK.
The problem occurs with the 2.4.9-34 and 2.4.9-31 kernels, but not the
2.4.7-10 kernel that shipped with 7.2 originally.
All file systems are ext3.
/etc/fstab:
---
LABEL=/
Patrick,
The directory /initrd already exist.
[]'s
Renato
- Original Message -
From: "Patrick Nelson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 12, 2002 10:07 PM
Subject: RE: Kernel panic: No init found. Try passing init= opt
Renato P Cardoso wrote:
-
> > Hello,
> >
> > This is the second time that I have this same problem. Anyone
> knows how
> > to fix this kernel panic? I am using Red Hat 7.2
> >
> > Freeing initrd memory: 321k freed
> > EXT2-fs warning: checktime reached, running e2fsck i
rdoso [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 5:49 PM
To: [EMAIL PROTECTED]
Subject: Re: Kernel panic: No init found. Try passing init= option to
kernel.
I never have recompiled the kernel on this system.
All partitions is using ext3 filesystem.
[]'s
Renato
- Origin
ave
and
> the patches of the files and images are the same.
> Do you or anyone have any idea how could I fix this problem?
>
> []'s
> Renato
> - Original Message -
> From: "scott.list" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
?
[]'s
Renato
- Original Message -
From: "scott.list" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 12, 2002 2:37 PM
Subject: Re: Kernel panic: No init found. Try passing init= option to
kernel.
> When this happendd to me, /etc/lilo.conf was
Renato P Cardoso wrote:
> Hello,
>
> This is the second time that I have this same problem. Anyone knows how
> to fix this kernel panic? I am using Red Hat 7.2
>
> Freeing initrd memory: 321k freed
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (e
enato
- Original Message -
From: "scott.list" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 12, 2002 2:37 PM
Subject: Re: Kernel panic: No init found. Try passing init= option to
kernel.
> When this happendd to me, /etc/lilo.conf was messed up an
When this happendd to me, /etc/lilo.conf was messed up and pointing
root to the wrong partition. PITA to straighten out but once done,
all was OK again. Your messages show a comma in the path which I
assume is not what one would want. (/sysroot,/sysroot/initrd)
HTH,
Scott
- Original Messa
13 matches
Mail list logo
