hello,
I'm trying to mount root filesystem on cramfs (2.6.11,
compiled with mtd and CRAMFS support), however I get
following well known error message:
VFS: Cannot open root device "mtdblock1" or
unknown-block(31,1)
Please append a correct "root=" boot option
Kernel
On Wed, 23 Feb 2005 16:25:39 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > Could someone try this?
>
> Let's turn that into a real patch.
>
> --- 25/drivers/ide/ide-probe.c~ide_init_disk-fixWed Feb 23 16:24:44
> 2005
> +++ 25-akpm/driv
elect.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root de
elect.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root de
On Wed, 23 Feb 2005 16:25:39 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > Could someone try this?
>
> Let's turn that into a real patch.
>
> --- 25/drivers/ide/ide-probe.c~ide_init_disk-fixWed Feb 23 16:24:44
> 2005
> +++ 25-akpm/driv
On Thu, Feb 24, 2005 at 03:03:33AM +0100, Benoit Boissinot wrote:
> On Wed, 23 Feb 2005 16:41:59 -0800, Matt Mackall <[EMAIL PROTECTED]> wrote:
> > On Wed, Feb 23, 2005 at 04:16:53PM -0800, Andrew Morton wrote:
> > > Steven Cole <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Yes, that worked. 2.6.11
On Wed, 23 Feb 2005 16:41:59 -0800, Matt Mackall <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 23, 2005 at 04:16:53PM -0800, Andrew Morton wrote:
> > Steven Cole <[EMAIL PROTECTED]> wrote:
> > >
> > > > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > > > missing.
> >
> > Looking
On Wed, Feb 23, 2005 at 03:10:38PM -0700, Steven Cole wrote:
> Andrew Morton wrote:
> >Steven Cole <[EMAIL PROTECTED]> wrote:
>
> >>I am having trouble getting recent -mm kernels to boot on my test box.
> >>For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the follo
Steven Cole <[EMAIL PROTECTED]> wrote:
>
> Andrew Morton wrote:
> > Steven Cole <[EMAIL PROTECTED]> wrote:
>
> >> I am having trouble getting recent -mm kernels to boot on my test box.
> >> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
&g
On Wed, Feb 23, 2005 at 04:16:53PM -0800, Andrew Morton wrote:
> Steven Cole <[EMAIL PROTECTED]> wrote:
> >
> > > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > > missing.
>
> Looking at the IDE update in rc4-mm1:
>
> +void ide_init_disk(struct gendisk *disk, ide_drive_
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> Could someone try this?
Let's turn that into a real patch.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fixWed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unr
Steven Cole <[EMAIL PROTECTED]> wrote:
>
> > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > missing.
Looking at the IDE update in rc4-mm1:
+void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
+{
+ ide_hwif_t *hwif = drive->hwif;
+ unsigned int unit
t on my test box.
> > >> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
> > >>
> > >> VFS: Cannot open root device "301" or unknown-block(3,1)
> > >> Please append a correct "root=" boot option
> > >&g
Steven Cole wrote:
Andrew Morton wrote:
Steven Cole <[EMAIL PROTECTED]> wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append
On Wed, Feb 23, 2005 at 09:37:53AM -0700, Steven Cole wrote:
> I copied a working .config from an earlier kernel(-rc3), and ran make
> oldconfig, answering most of the new questions 'n'.
Then you get into trouble with stuff under CONFIG_EMBEDDED. Answering
'n' turns off stock functionality. Thoug
Andrew Morton wrote:
Steven Cole <[EMAIL PROTECTED]> wrote:
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root
; > down a bit.
> >
>
> I am having trouble getting recent -mm kernels to boot on my test box.
> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
>
> VFS: Cannot open root device "301" or unknown-block(3,1)
> Please append a correct &qu
2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
2.6.11-rc2-mm1 boots fine, and so do plain -rc3 and -rc4.
I copi
Peter Samuelson wrote:
> [Jeremy Jackson]
> > try command 'man mkinitrd' under redhat for hints about initial
> > ramdisk.
>
> I have been puzzled about this for quite some time. Why exactly does
> everyone always recommend using 'mkinitrd' on Red Hat systems? It
> seems to me that if you are c
[Jeremy Jackson]
> try command 'man mkinitrd' under redhat for hints about initial
> ramdisk.
I have been puzzled about this for quite some time. Why exactly does
everyone always recommend using 'mkinitrd' on Red Hat systems? It
seems to me that if you are compiling a kernel for a specific ser
ckage.
try command 'man mkinitrd' under redhat
for hints about initial ramdisk.
>
>
> Then some standard lines Then:
>
> NET 4: Unix domain sockets 1.0/SMP for Linux NET 4.0
> request_module[block-major-104]: Root FS not mounted
> VFS: Cannot open root device "6802
following message.
request_module[scsi_host_adapter]: Root FS not mounted
request_module[scsi_host_adapter]: Root FS not mounted
Then some standard lines Then:
NET 4: Unix domain sockets 1.0/SMP for Linux NET 4.0
request_module[block-major-104]: Root FS not mounted
VFS: Cannot open root device
22 matches
Mail list logo
