public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: initrd and 2.6.0-test8
@ 2003-10-18 16:27 Walt H
  2003-10-18 17:52 ` viro
  0 siblings, 1 reply; 19+ messages in thread
From: Walt H @ 2003-10-18 16:27 UTC (permalink / raw)
  To: arekm; +Cc: linux-kernel


> Hi,
> 
> Seems that something changed between test7 and test8 regarding initrd or romfs 
> support. I'm using highly modularized 2.6.0 kernel which has all filesystems 
> beside romfs compiled as modules (romfs is compiled inside of kernel).
> 
> Modules for my rootfs are loaded from initrd (which is image with romfs as 
> filesystem) but starting from test8 kernel is not able to mount initrd 
> filesystem - stops with typical message about not being able to mount rootfs.
> 
> cset test7 from 20031012_0407 is known to be ok so something was changed later


I noticed this happened in 2.6.0-test6-mm4. Backing out this patch fixes
it in the short-term.

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test6/2.6.0-test6-mm4/broken-out/RD0-initrd-B6.patch


-Walt



^ permalink raw reply	[flat|nested] 19+ messages in thread
* initrd and 2.6.0-test8
@ 2003-10-18 19:10 Svetoslav Slavtchev
  2003-10-18 19:25 ` viro
  0 siblings, 1 reply; 19+ messages in thread
From: Svetoslav Slavtchev @ 2003-10-18 19:10 UTC (permalink / raw)
  To: linux-kernel

me had  the same problems,
with devfs enabled

could it be this (from Documentation/initrd)

Note that changing the root directory does not involve unmounting it.
    the "normal" root file system is mounted. initrd data can be read
  root=/dev/ram0   (without devfs)
  root=/dev/rd/0   (with devfs)
    initrd is mounted as root, and the normal boot procedure is followed,
    with the RAM disk still mounted as root.

the patch doesn't mention anything about /dev/rd/0 , but does for /dev/ram0

svetljo

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++


^ permalink raw reply	[flat|nested] 19+ messages in thread
* Re: initrd and 2.6.0-test8
@ 2003-10-18 18:02 Witold Krecicki
  2003-10-18 19:41 ` Valdis.Kletnieks
  0 siblings, 1 reply; 19+ messages in thread
From: Witold Krecicki @ 2003-10-18 18:02 UTC (permalink / raw)
  To: Linux Kernel Mailing List

> On Sat, Oct 18, 2003 at 09:27:56AM -0700, Walt H wrote:
> > > Hi,
> > >
> > > Seems that something changed between test7 and test8 regarding initrd
> > > or romfs support. I'm using highly modularized 2.6.0 kernel which has
> > > all filesystems beside romfs compiled as modules (romfs is compiled
> > > inside of kernel).
> > >
> > > Modules for my rootfs are loaded from initrd (which is image with romfs
> > > as filesystem) but starting from test8 kernel is not able to mount
> > > initrd filesystem - stops with typical message about not being able to
> > > mount rootfs.
> > >
> > > cset test7 from 20031012_0407 is known to be ok so something was
> > > changed later
> >
> > I noticed this happened in 2.6.0-test6-mm4. Backing out this patch fixes
> > it in the short-term.
>
> Even better would be to report the bug ;-/
>
> I can't reproduce it here.  2.6.0-test8 vanilla, so far (last 15 minutes)
> tried with
> 	* compressed initrd image
> 	* plain ext2
> and I'll try romfs as soon as I hunt down mkfs for that animal.  All
> appears to be working...
>
> What did it say before the "typical message"?  Specifically, were there
> any lines starting with RAMDISK:?
>
> .config would be also useful.

But do you have HDD-controller parts as modules or built-in? According to the
changelog message, if initrd is detected as 'usual initrd' (e.g. not
initramfs), then it's copied to /dev/initrd on rootfs. But as I understand,
there is no such thing as rootfs as long as it isn't mounted (ide/scsi
modules are not loaded
--
Witold Kręcicki (adasi) adasi [at] culm.net
GPG key: 7AE20871
http://www.culm.net

^ permalink raw reply	[flat|nested] 19+ messages in thread
* initrd and 2.6.0-test8
@ 2003-10-18 13:05 Arkadiusz Miskiewicz
  0 siblings, 0 replies; 19+ messages in thread
From: Arkadiusz Miskiewicz @ 2003-10-18 13:05 UTC (permalink / raw)
  To: linux-kernel

Hi,

Seems that something changed between test7 and test8 regarding initrd or romfs 
support. I'm using highly modularized 2.6.0 kernel which has all filesystems 
beside romfs compiled as modules (romfs is compiled inside of kernel).

Modules for my rootfs are loaded from initrd (which is image with romfs as 
filesystem) but starting from test8 kernel is not able to mount initrd 
filesystem - stops with typical message about not being able to mount rootfs.

cset test7 from 20031012_0407 is known to be ok so something was changed later
-- 
Arkadiusz Miśkiewicz    CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux


^ permalink raw reply	[flat|nested] 19+ messages in thread

end of thread, other threads:[~2003-10-18 23:12 UTC | newest]

Thread overview: 19+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-10-18 16:27 initrd and 2.6.0-test8 Walt H
2003-10-18 17:52 ` viro
2003-10-18 18:22   ` viro
2003-10-18 18:33   ` Christophe Saout
2003-10-18 19:41     ` [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8) viro
2003-10-18 21:56       ` Arkadiusz Miskiewicz
2003-10-18 22:11         ` viro
2003-10-18 22:46           ` Arkadiusz Miskiewicz
2003-10-18 23:07       ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2003-10-18 19:10 initrd and 2.6.0-test8 Svetoslav Slavtchev
2003-10-18 19:25 ` viro
2003-10-18 19:33   ` Svetoslav Slavtchev
2003-10-18 20:32   ` Witold Krecicki
2003-10-18 20:43     ` viro
2003-10-18 22:25   ` Svetoslav Slavtchev
2003-10-18 18:02 Witold Krecicki
2003-10-18 19:41 ` Valdis.Kletnieks
2003-10-18 19:57   ` viro
2003-10-18 13:05 Arkadiusz Miskiewicz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox