On Tue, Apr 20, 2004 at 03:10:58PM +0200, Philippe Dhont (Sea-ro) said
> My new kernel is compiled with ext2, ext3 and the others also.
> My filesystem is ext3.
In the kernel or as modules? They have to be builtin for it boot.
> When i reboot my system i can choose to boot the debian2.6.5 but
Philippe Dhont (Sea-ro) wrote:
Hi,
I installed debian SARGE with grub and everything works fine.
I downloaded the latest stable kernel, compiled everything and put the
boot lines in the grub configuration
Menu.lst
This was before:
Title Debian 2.4.25
Root (hd0,0)
Kernel /vmlinuz-2.4.25-1-386 root
On Tuesday 26 August 2003 14:56, Joris Huizer wrote:
> --- Alphonse Ogulla <[EMAIL PROTECTED]> wrote:
> > Hi all,
> > Just compiled kernel 2.4.21 but cannot boot it
> > despite creating the initrd
> > image and respective links in / to files in /boot.
> > The last 5 lines printed on screen before h
On Tue, Aug 26, 2003 at 12:40:44PM +0300, Alphonse Ogulla wrote:
| Just compiled kernel 2.4.21 but cannot boot it
| VFS: Cannot open root device "301" or 03:01
You probably forgot to include the driver for your hard disk when you
built the kernel. Follow Joris' suggestion for enabling the drive
--- Alphonse Ogulla <[EMAIL PROTECTED]> wrote:
> Hi all,
> Just compiled kernel 2.4.21 but cannot boot it
> despite creating the initrd
> image and respective links in / to files in /boot.
> The last 5 lines printed on screen before hang-up
> are printed below.
>
> RAMDISK: Couldn't find valid
On Fri, Dec 06, 2002 at 08:26:48AM -0600, Shyamal Prasad wrote:
> Paul,
>
> To be fair, you should point out that this is an opinion that run's
> contrary to how Debian's 2.4 kernels are packaged.
Yes, I realise this, however, when compiling one's own kernel from the
kernel archive (oppose to th
In article <20021206045426.GA22017@ursine>, Paul Johnson wrote:
>
> Wait, are you trying to boot a kernel that doesn't have ext3 compiled
> in on a system whose /etc/fstab specifies the / partition as being
> ext3?
Nope, ext2/ext3 have been included in the vmlinuz-image all along.
I'll throw in
Just a thought, but do you have ide and/or scsi as modules instead of
compiled into the kernel? You will get this message if the kernel can't
mount the root partition because it doesn't have the necessary drivers to
talk to the disk on which the root partition sits. That is, if / is on an
ide disk
"Paul" == Paul Johnson <[EMAIL PROTECTED]> writes:
Paul> Support for your root device hardware and filesystem should
Paul> be part of your kernel for maximum ease and reliability.
Paul> Pretty much everything else that can be moduled out should.
Paul,
To be fair, you should point
On Sat, Dec 07, 2002 at 12:38:37AM +1300, Richard Hector wrote:
> It is? I thought that was the usual way to do it (with 2.4 kernels,
> anyway) ... should I look at recompiling my kernel with my SCSI drivers
> built in instead? Or are you specifically referring to filesystem
> drivers rather than a
On Fri, 2002-12-06 at 17:54, Paul Johnson wrote:
> You can't get away with having your root partition being a
> filesystem for which you must load a module to support. Unless you
> use initrd, but that's messy and not very failproof.
It is? I thought that was the usual way to do it (with 2.4 ker
On Thu, Dec 05, 2002 at 07:10:42PM +, Stig Are M. Botterli wrote:
> > I had kernels bigger than 1 MB - no problem.
> > It would help if you remember what things you configured as modules.
>
> Unfortunately, I don't.
Wait, are you trying to boot a kernel that doesn't have ext3 compiled
in on a
In article <[EMAIL PROTECTED]>, Klaus Imgrund wrote:
> On Thu, 05 Dec 2002 15:16:29 +
>>
> I had kernels bigger than 1 MB - no problem.
> It would help if you remember what things you configured as modules.
Unfortunately, I don't.
> If you got i.e a driver for the wrong sound card compiled i
On Thu, 05 Dec 2002 15:16:29 +
"Stig Are M. Botterli" <[EMAIL PROTECTED]> wrote:
> In article <20021205080347.GE7442@ursine>, Paul Johnson wrote:
> >
> > On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli
> > wrote:> Basically, if my /boot/vmlinuz image exceeds a certain size
> >
In article <20021205080347.GE7442@ursine>, Paul Johnson wrote:
>
> On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote:
>> Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se=
>> ems be
>> somewhere around 90 bytes), the following occurs on boot:
>
> Who
Paul Johnson said:
> Whoa! Huge kernel! Module some of that stuff out and it should
> help if there's some hidden size limitation. I have a pretty big
> kernel, the bzImage is 644,225 bytes.
sounds like a 2.4.x kernel. I was amazed how huge the 2.4.x kernel
got. my biggest 2.2.x kernel I think
On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote:
> Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be
> somewhere around 90 bytes), the following occurs on boot:
Whoa! Huge kernel! Module some of that stuff out and it should
help if there's s
Sorry,
I've found the problem my fault I was playing with ext3 about the time it
came in the kernel and for some reason the filesystem was identified as ext3
but was ext2.
Sorry again
Nick
Thus spake Philip Blundell:
> On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote:
> > I'm trying to get a server built with 2.2r4 potato cd and keep getting
> > the above error. I tried the boot options in f2-f8 and tried mounting
> > various root.bins from specifying floppy0 at boo
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote:
> I'm trying to get a server built with 2.2r4 potato cd and keep getting
> the above error. I tried the boot options in f2-f8 and tried mounting
> various root.bins from specifying floppy0 at boot: then got kernel
> panic: no init
>
> Dell Latitude CPi D300XT 128MB Ram PII 300Mhz
>
> lilo.conf
>
> vga=1
> append="apm=on"
> default=Linux22
>
> # kernel 2.4.12
> image=/vmlinuz
> initrd=/boot/initrd
> label=LinuxNew
> read-only
>
> # kernel 2.4.10
> image=/vmlinuz.old
> initrd=/boot/initrd-2.4.10-686
>
> > > <>
> > >
> > > Now, I'm really confused. I haven't been able to
> > get
> > > any of the 2.4.x debian kernel packages to boot
> > and
> > > everything I had read previously in the list
> > archives
> > > indicated that the initrd line was necessary for
> > 2.4.x
> > > kernels. I never had an
--- Shaul Karl <[EMAIL PROTECTED]> wrote:
> >
> > --- Xeno Campanoli <[EMAIL PROTECTED]> wrote:
> > > Shaul Karl wrote:
> > > >
> > > > > As my subject line indicates, I'm getting
> the
> > > diagnostic:
> > > > >
> > > > > Kernel panic: VFS: Unable to mount
> root fs
> > > on 01:00
> > >
>
> --- Xeno Campanoli <[EMAIL PROTECTED]> wrote:
> > Shaul Karl wrote:
> > >
> > > > As my subject line indicates, I'm getting the
> > diagnostic:
> > > >
> > > > Kernel panic: VFS: Unable to mount root fs
> > on 01:00
> > > >
> > > > when I try to boot up with my home grown kernel.
> > I
Thus spake Charles Baker:
>
> --- Xeno Campanoli <[EMAIL PROTECTED]> wrote:
> > Shaul Karl wrote:
> > >
> > > > As my subject line indicates, I'm getting the
> > diagnostic:
> > > >
> > > > Kernel panic: VFS: Unable to mount root fs
> > on 01:00
> > > >
> > > > when I try to boot up with my
--- Xeno Campanoli <[EMAIL PROTECTED]> wrote:
> Shaul Karl wrote:
> >
> > > As my subject line indicates, I'm getting the
> diagnostic:
> > >
> > > Kernel panic: VFS: Unable to mount root fs
> on 01:00
> > >
> > > when I try to boot up with my home grown kernel.
> I've tried several
> > >
Shaul Karl wrote:
>
> > As my subject line indicates, I'm getting the diagnostic:
> >
> > Kernel panic: VFS: Unable to mount root fs on 01:00
> >
> > when I try to boot up with my home grown kernel. I've tried several
> > things with lilo on this, but I'm stumped. rdev indicates the root
>
> As my subject line indicates, I'm getting the diagnostic:
>
> Kernel panic: VFS: Unable to mount root fs on 01:00
>
> when I try to boot up with my home grown kernel. I've tried several
> things with lilo on this, but I'm stumped. rdev indicates the root
> partition is /dev/hda1, which
Make sure that you have compiled the ide and ext2 into the kernel and not
just made them loadable mods.
Xeno Campanoli wrote:
Subject:
Kernel panic: VFS: Unable to mount root fs on 01:00
From:
Xeno Campanoli <[EM
> As my subject line indicates, I'm getting the diagnostic:
>
> Kernel panic: VFS: Unable to mount root fs on 01:00
i would say the #1 cause of this is lack of support for
the disk controller which the root drive is hooked to
compiled into the kernel(it can't be a module).
first thing to c
- Original Message -
From: "Dave Sherohman" <[EMAIL PROTECTED]>
To: "Debian User List"
Sent: Monday, October 08, 2001 4:52 PM
Subject: Re: Kernel Panic: VFS Unable to mount root fs on 21:04
> On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote:
&
> > During the install of the 2.4 kernel package. I goot a message about
> > needing to add a initrd line to lilo.conf.
This is probably the cause of your problem. I had the same problem the
first time I installed a 2.4 kernel package with apt-get.
Just follow the instructions and edit your lilo.c
On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote:
> I'm trying to set up a new machine this weekend, and i'm in trouble.
I know you needed a solution by Monday, so this is a bit late, but I
haven't seen anyone else post an explanation of what the error
actually means, so...
> Now, I hav
- Original Message -
From: "Stan Brown" <[EMAIL PROTECTED]>
To: "Debian User List"
Sent: Saturday, October 06, 2001 8:17 PM
Subject: Kernel Panic: VFS Unable to mount root fs on 21:04
> I'm trying to set up a new machine this weekend, and i'm in trouble.
>
> I installed a minimal "stable
its possible you forgot to include scsi support in your kernel, i have
made that mistake and gotten that error many times.
nate
[mailto:[EMAIL PROTECTED] ]--
Linux System Administrator http://www.firetrail.com/
Firetrail Internet Services
On Mon, Oct 18, 1999 at 05:09:13PM -0700, T.V.Gnanasekaran wrote:
> hello,
> I am trying to install kernel 2.2.12. I compiled as documented in the
> README of the kernel source distribution. I edited lilo.conf and exec
> lilo and added. My root dev=/dev/sda3 (extend partition) boot=/dev/sda
> But
I went through "make config" again while reading the
"Configure help file for the source (along with making
the image and the other processes), and, upon boot, the new
kernel got as far as
VFS: root fs mounted [...]
then it simply stopped. ...anyone have any info that would
help here? Does
On Sat, Sep 19, 1998 at 11:41:24PM +0200, Miquel van Smoorenburg wrote:
> In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
> > VFS: Can't open root device 03:01
> > Kernel Panic: VFS unable to mount root fs on 03:01
>
> Sounds like you didn't compile in the driver for your hardd
On Sat, Sep 19, 1998 at 03:41:47PM -0500, Mark Panzer wrote:
> > What do these messages mean, what have I done to myself, and how can I undo
> > it?
> >
>
> Next time also try to use the kpkg utility, all you do is enter the
> source directory enter kpkg and it creates a .deb of the kernel (well
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
Sounds like you didn't compile in the driver for your harddisk. You
did compile in (not as module) the IDE driver right? And support
for the
In article <[EMAIL PROTECTED]>,
Samuel Landau <[EMAIL PROTECTED]> wrote:
>dear mister, that's the orginal doc from de kernel source, not the
>Debianized one.
>well, with Debian there are some more files that are necessary for the
>kernel to work
>(e.g. : /boot/SystemMap)
That's nonsense. I have ne
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
strange
maybe you compiled the root fs as a module (which is not to be
done), but how would you boot?...
ah there's the answer:
> I installed the 2.0.34 kernel source package. I think I'm following
[EMAIL PROTECTED] wrote:
>
> My Hamm system is a couple weeks old, and I'm trying to roll my own kernel.
> The first few trys seemed to work, (removing PCI support, setting processor
> type to 486, etc...), but now, no matter how simple of a kernel I try to
> build, the system won't reboot. T
43 matches
Mail list logo
