Hi,
I’m trying to =
develop a
Linux-based system on a Disk On Chip (8Mb).
I’ve got several
problems, and although I’ve read your mailing list archive, I
didn’t find a great solution.
I’m using =
PeeWeeLinux 0.61.0 =
distribution.
I build my file system =
(with
DOC driver included as module or as static in the kernel : both =
don’t
work) and put it on the DiskOnChip (by replacing lilo with doc-lilo in =
the
pwl-target-load script).
I manage to boot on =
the DOC,
but the system is then bloked while trying to mount the root =
partition.
It says something =
like: VFS
unable to mount root partition on device =
03:02.
Do you know the =
problem or at
least could you answer to the following =
questions:
1)
Is
it possible to put all the file system directly on the Disk On Chip =
target ?
2)
Is
it necessary to use doc-lilo (and a special lilo.conf file) instead of =
lilo in
the pwl_target_load script ?
3)
In
the mailing list archive, some say it is necessary to first put =
everything on
ide partition and then put everything on DOC =
?
4)
On
the web site, it is written: “ Currently the loading of target devices =
directly
attached to the development system are supported. These include floppy =
drives,
IDE hard drives, scsi hard drives, M-Systems Disk-On-Chip and =
CompactFlash
devices.”.
So what’s the best method to load the file system on the
DiskOnChip target ?
Thanks very much for your answer !
---<=
o:p>
Guil=
laume
SISTERON
COM
One
------=_NextPart_000_0027_01C129CC.6CDD8A90--
---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at http://peeweelinux.com
---------------------------------------------------
From peeweelinux@adis.on.ca Tue Aug 21 08:21:38 2001
From: peeweelinux@adis.on.ca (Tim Westbrook)
Date: Tue, 21 Aug 2001 00:21:38 -0700 (PDT)
Subject: DiskOnChip Problem
In-Reply-To: <002601c129bb$a954ba90$a016fea9@guigui>
Message-ID: <20010821072138.87587.qmail@web13502.mail.yahoo.com>
Hello Guillaume,
Oddly enough, I found myself in your exact same
situation tonight. I am using a doc system as well,
with the target being an uncompressed ext2 partion on
ramdisk.
I was able to get around your particular problem
by creating an msys subdirectory in my
/project/minimal/mnt/dev directory.
It seems that the portion of the script that
creates the boot device directory structure does not
create multi-level /dev entries. So you may be seeing
cp error messages when your run "load target"
You may be able to do this with the custom files
option I did it by editing the script file that
creates these directory entries.
Also make sure that the doc driver is loaded, i am
using a modular driver so i had to modify the linuxrc
in the initrd to load the driver before attempting to
mount the root partition.
I myself am having trouble with finding init. My
root partition seems to boot fine , but i get
"Kernel Panic: No INIT found" I suppose for some
reason, the system can't read my root partition.
A curious item, I noticed that for uncompressed
ext2 partitions booting from lilo, the linuxrc script
in the initrd copies the root partition from the
source partion on the flash to /dev/ram2, but the
fstab entry created points / to /dev/ram0. I don't
think this is my problem , but it seems sort of odd.
- Tim
--- Guillaume Sisteron