On 8/28/07, Richard Thompson <[EMAIL PROTECTED]> wrote:
>
> I don't get why your building you own intird?, if your using the kernel
> provided it already has it's own initrd and if your building the kernel
> yourself why are you using initrd at all?
Good question. I am building my own kernel (usin
On 8/27/07, Francois Duranleau <[EMAIL PROTECTED]> wrote:
> On 8/24/07, Bert Schulze <[EMAIL PROTECTED]> wrote:
> > Hi
> >
> > I took a look at your config and menu.lst
> > So whats missing seems to be an initrd image which holds all the
> > modules your kernel needs. Your config uses some of em. Y
On 8/27/07, Jeff D <[EMAIL PROTECTED]> wrote:
>
> One thing that kinda stands out to me in the 2.6 config are:
> CONFIG_IDE_GENERIC=m
> CONFIG_BLK_DEV_VIA82CXXX=m
>
> I'd change those to be compiled in rather than modules.
Yes. There were set as modules for some experiments regarding
CRC errors (s
On 8/24/07, Bert Schulze <[EMAIL PROTECTED]> wrote:
> Hi
>
> I took a look at your config and menu.lst
> So whats missing seems to be an initrd image which holds all the
> modules your kernel needs. Your config uses some of em. You should
> build the initrd
> mkinitramfs -o /boot/initrd.img-2.6.1
On Mon, 27 Aug 2007, Francois Duranleau wrote:
On 8/25/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
Francois
Just looked at the config file you listed for the 2.1.18 kernel.
It looks different then mine in the Block Device section.
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not
On 8/25/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> Francois
>
> Just looked at the config file you listed for the 2.1.18 kernel.
> It looks different then mine in the Block Device section.
>
> # Block devices
> #
> CONFIG_BLK_DEV_FD=m
> # CONFIG_BLK_DEV_XD is not set
> # CONFIG_PARIDE is not set
>
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> On 8/24/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> > Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> [snip]
> > > It's an old system: AMD Athlon Thunderbird 1.1GHz with 1.25GB RAM and
> > > an 80GB Western Digital
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> On 8/24/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> > Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> [snip]
> > > It's an old system: AMD Athlon Thunderbird 1.1GHz with 1.25GB RAM and
> > > an 80GB Western Digital
On 8/24/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
> Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
[snip]
> > It's an old system: AMD Athlon Thunderbird 1.1GHz with 1.25GB RAM and
> > an 80GB Western Digital drive, for sur not SATA, I bought this
> > computer in december 2000. The
Francois Duranleau([EMAIL PROTECTED]) is reported to have said:
> On 8/24/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote:
> > On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
> > >
<>
> > Is the disk really a PATA or is it SATA? 2.4 kernels will see them as
> > /dev/hd* wher
On 8/24/07, Douglas A. Tutty <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
> >
> > Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
> > boot my system with 2.6, I get the following error:
> >
On Thu, Aug 23, 2007 at 09:49:52PM -0400, Francois Duranleau wrote:
>
> Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
> boot my system with 2.6, I get the following error:
>
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> P
On 24 Aug., 04:00, "Francois Duranleau" <[EMAIL PROTECTED]>
wrote:
> Hi!
>
> Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
> boot my system with 2.6, I get the following error:
>
> VFS: Cannot open root device "hda1" or unknow
Hi!
Trying to upgrade to kernel 2.6 (actually, 2.6.18) from 2.4.27, when I
boot my system with 2.6, I get the following error:
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to moun
Marty wrote:
Gayle Lee Fairless wrote:
Although the Gateway 500 does have an
internal modem that Windows 98SE can use, Linux appears to be able to
use only the Hayes external modem.
Then can you try a PCI modem instead? This is a critical troubleshooting step.
Possibly off-topic, but doe
Gayle Lee Fairless wrote:
Although the Gateway 500 does have an
internal modem that Windows 98SE can use, Linux appears to be able to
use only the Hayes external modem.
Then can you try a PCI modem instead? This is a critical troubleshooting step.
Possibly off-topic, but does a custom kern
Gayle's current wvdial problem:
After I fixed the lilo.conf with the initrd=/initrd.img, I got the
2.6.8 kernel to run but ran into what appeared to be Bug #276020 filed
against that kernel so I went to unstable and got the 2.6.11 kernel.
It seems to manifest the same bug with wvdial.
Subject:
Re: [Fwd: Re: VFS: Cannot open root device 2141 ... Kernelpanic: VFS:
Unable to mount root fs on unk-blk(33,65)]
From:
Marty <[EMAIL PROTECTED]>
Date:
Sat, 25 Jun 2005 16:06:29 -0400
To:
debian-user@lists.debian.org
Gayle Lee Fairless wrote:
line 'initrd=/initrd.img
Gayle Lee Fairless wrote:
line 'initrd=/initrd.img' after the read-only line in the Linux label
stanza. Now the 2.6 kernel (you guessed or read correctly) boots. It
appears to be a little fussier than the bf2.4 kernel which still works
fine. I kept it under the LinuxOld label where the pack
On Fri, 24 Jun 2005, Debian User Leonard Chatagnier wrote:
> Gayle Lee Fairless wrote:
>
> >
> >
> > Original Message
> > Subject: Re: VFS: Cannot open root device 2141 ... Kernelpanic:
> > VFS: Unable to mount root fs on unk-blk(33,65)
Gayle Lee Fairless wrote:
Original Message
Subject: Re: VFS: Cannot open root device 2141 ... Kernelpanic:
VFS: Unable to mount root fs on unk-blk(33,65)
Date: Thu, 23 Jun 2005 22:26:08 -0500 (CDT)
From: Gayle Lee Fairless <[EMAIL PROTECTED]>
To:
Original Message
Subject: Re: VFS: Cannot open root device 2141 ... Kernelpanic: VFS:
Unable to mount root fs on unk-blk(33,65)
Date: Thu, 23 Jun 2005 22:26:08 -0500 (CDT)
From: Gayle Lee Fairless <[EMAIL PROTECTED]>
To: Edward Dunagin <[EMAIL PROTE
following panic:
VFS: Cannot open root device 2141 or unknown-block(33,65)
Please append a correct "root=" boot option
Kernelpanic: VFS: Unable to mount root fs on unknown-block(33,65)
The computer is a Gateway 500 with a Pentium III at 500 MHZ. I
looked through the man pages for
s me the following panic:
> >
> > VFS: Cannot open root device 2141 or unknown-block(33,65)
> > Please append a correct "root=" boot option
> >
> > Kernelpanic: VFS: Unable to mount root fs on unknown-block(33,65)
> >
> >The computer is a Gateway
Interesting that I think I might have found the real source of my build
problem.
I was able to retain a config file from a working 2.6.8 kernel build,
and used it as the basis of my further builds by loading that config
file while in "make config" mode. I then recompiled a new kernel,
adding onl
Ok. This is now starting to seriously irritate me. I can no longer
build kernels anymore. Even blowing away the source tree directory and
re-expanding the tarball gets me nowhere. Thankfully I retained a
"safe" kernel which boots (but doesn't give me the functionality I'm
after, namely Macinto
Andrea, Alvin, and Reiner (and the rest of Debian-User):
Thank you for your assistance. It turns out that there was something
scrod in my source tree. After multiple attempts (including a "make
mrproper") I finally blew away the source directory and re-extracted
from the tarball.
My builds hav
work and the other one doesn't
> ( in old scsi hardware
>
> make sure you're booting the kernel you compiled ..
>
> > Beyond this problem with HFS,
>
> your boot problems is NOT related to hfs ...
>
> > > > I recently recompiled m
On Thu, 30 Dec 2004 00:01:15 -0800, Eric N. Valor <[EMAIL PROTECTED]> wrote:
>
> I don't know because I'm not using the Debian image (I like to compile
> my own kernels, and have only started running into these problems using
> 2.6.x kernels). Does the Debian 2.6.8 binary image contain support fo
27;re booting the kernel you compiled ..
> Beyond this problem with HFS,
your boot problems is NOT related to hfs ...
> > > I recently recompiled my 2.6.8 kernel. Now I can no longer boot my
> > > system. It fails with the message "cannot open root device "801" or
Hi,
Am Mittwoch, den 29.12.2004, 12:45 -0800 schrieb Eric N. Valor:
> The only change I
> made was to enable HFS filesystem (so I can play with my new iPod).
This is no solution for your problem, but maybe a useful workaround:
I work for a company that uses Macs, and we all got an iPod for
chris
or <[EMAIL PROTECTED]> wrote:
> >
> > Hello.
> >
> > I recently recompiled my 2.6.8 kernel. Now I can no longer boot my
> > system. It fails with the message "cannot open root device "801" or
> > unknown-block(8,1)".
> >
&
On Wed, 29 Dec 2004 12:45:27 -0800, Eric N. Valor <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> I recently recompiled my 2.6.8 kernel. Now I can no longer boot my
> system. It fails with the message "cannot open root device "801" or
> unknown-block(8,1)".
Hello.
I recently recompiled my 2.6.8 kernel. Now I can no longer boot my
system. It fails with the message "cannot open root device "801" or
unknown-block(8,1)".
I am using a Symbios SCSI card without any IDE devices (save the CDROM)
in my system. My lilo.conf properly
I am having somewhat the same problem mentioned in this trail. The bin
2.6.3 deb works fine (etcept for alsa which is what started the whole
thing)
When I recompile I cannot get the root file system to come up.
I copied over the /boot/config file, ran make config, checked that ext3
is compiles in,
On Sun, Apr 11, 2004 at 11:31:32AM +0200, Markus LindstrÃm wrote:
| Derrick 'dman' Hudson wrote:
| >
| >Don't forget to include "PC BIOS (MSDOS partition tables) support"
| >(CONFIG_MSDOS_PARTITION) in the kernel's configuration. If you leave
| >it out, then the kernel can't read the partition tab
Derrick 'dman' Hudson wrote:
Don't forget to include "PC BIOS (MSDOS partition tables) support"
(CONFIG_MSDOS_PARTITION) in the kernel's configuration. If you leave
it out, then the kernel can't read the partition table and thus can't
find the filesystem.
GREAT! That was the missing link! It boots
blem comes at boot time, where I can the following message:
|
|
| VFS: Cannot open root device "341" or hdb1
| Please append a correct "root=" boot option
| Kernel panic: VFS: Unable to mount root fs on hdb1
Don't forget to include "PC BIOS (MSDOS partition tables) su
Ok, it really depends on your config.
Do you have a USB mouse or keyboard, what's you sound card, network card...?
When you run make {x,g,menu}config there is a short description for each
option.
The better way is to look at the kernel how-to
(http://www.tldp.org/HOWTO/Kernel-HOWTO/).
I hope my
Hello
Markus Lindström (<[EMAIL PROTECTED]>) wrote:
> In fact I've been trying to compile 2.6.4 and
> 2.6.4-ck2. The compilation itself doesn't encounter any problems, so
> that's clear.
>
> The problem comes at boot time, where I can the following message:
Yes, module-init-tools isn't in stable packages, try to download (you'll
find a .deb here:
http://www.backports.org/debian/dists/stable/module-init-tools/binary-i386/)
and install it, you should use modules.
Retry making a make-kpkg clean before compiling and choose the default
answers and th
6 kernel (which I've heard many good
things about). In fact I've been trying to compile 2.6.4 and 2.6.4-ck2.
The compilation itself doesn't encounter any problems, so that's clear.
The problem comes at boot time, where I can the following message:
VFS: Cannot open root devi
Hello
JAMES MERRITT (<[EMAIL PROTECTED]>) wrote:
> I tried typing linux root=/dev/hdb1 at the lilo prompt and it says
> something about that not being one of the choices.
Try "Linux root=/dev/hdb1" (note the capital letter).
> The lilo menu I see is:
> Linux WinNT (hda1)
> WinNT or DOS (hdb6) <
: Fri, 23 Jan 2004 17:18:14 -0600
To: [EMAIL PROTECTED]
Subject: Re: Cannot Open Root Device - Was: Unidentified subject!
> JAMES MERRITT wrote:
>
>
> >I am having a little problem with my Debian Woody. The other day when I tried to
> >boot into Woody,
> >it started
Hello
JAMES MERRITT (<[EMAIL PROTECTED]>) wrote:
> Also to Andreas, I am sorry I responded to your response and my email
> package uses the poster, not the newsgroup, as it's TO: address. I
> try never to respond directly unless the poster requests it. Also, by
> responding back to the newsgrou
message:
VFS: Cannot open root device "346" or 03:47.
Please append a correct "root=" boot option.
Kernel Panic: VFS: Unable to mount root fs on 03:46.
As far as I know my disk configuration has not changed and I have not added any new hard drives. I remember doing somethi
PROTECTED]
Subject: Cannot Open Root Device - Was: Unidentified subject!
> JAMES MERRITT wrote:
>
> >Hi everyone,
> >
> >I am having a little problem with my Debian Woody. The other day when I tried to
> >boot into Woody,
> >it started the normal text boot
gave this message:
VFS: Cannot open root device "346" or 03:47.
Please append a correct "root=" boot option.
Kernel Panic: VFS: Unable to mount root fs on 03:46.
What does all of this mean, what is going on and what can I do to correct this?
I am lost at this point.
Let
ald Becker
http://www.scyld.com/network/via-rhine.html
Partition check:
hda: [PTBL] [823/32/63] hda1 hda2
apm: BIOS version 1.1 Flags 0x03 (Driver version 1.13)
apm : disabled on user request
VFS: Cannot open root device 00:00
Kernel panic: VFS: Unable to mount root fs on 00:00
I
Petteri Heinonen wrote:
> I've compiled kernel (2.2.15), succesfully. But when I try to boot with it,
> I get message during boot:
>
> VFS: cannot open root device 03:02
> Kernel Panic: VFS: Unable to mount root fs on 03:02
Do run 'lilo' after installing the new kernel?
Rüdiger
I've compiled kernel (2.2.15), succesfully. But when I try to boot with it,
I get message during boot:
VFS: cannot open root device 03:02
Kernel Panic: VFS: Unable to mount root fs on 03:02
With old (but big and clumsy) kernel I've no problems. My lilo.conf is like
that:
lba32
boot=/de
51 matches
Mail list logo
