On 3/15/06, Philipp H. Mohr <phm4-eQnPN5D1UZ61Qrn1Bg8BZw@xxxxxxxxxxxxxxxx>
wrote:
>
> Hello,
>
> dmesg is attached.
>
> > > The flashing as described in the wiki seemed to have worked, at least it
> > > said it wrote some thing ;-) But when I try to mount mtdblock3 I get the
> > > error below.
> > >
> > > root@h2200:~# mount -t jffs2 /dev/mtdblock3 /mnt/test
> > > mount: Mounting /dev/mtdblock3 on /mnt/test failed: No such device
> > >
> > > btw: /mnt/test exists
> >
> > That sounds like the kernel doesn't have the right MTD modules
> > built-in. What kernel were you running when this happened? Did
> > /dev/mtdblock3 exist?
>
> kernel 2.6.13-hh1
>
> all these mtdblock's can be found:
> /dev/mtdblock0 /dev/mtdblock1 /dev/mtdblock2 /dev/mtdblock3
Ok, dmesg shows that the flash chips are detected.
Can you try booting the kernel from the rootfs instead? You can find a
.tar.bz2 rootfs where you got my jffs2 rootfs. Use the kernel from
that rootfs.
> > > I also tried to boot into it through LAB, when I take the SD card out I
> > > get the following, which is expected:
> > >
> > >
> > >
> > > >> Booting now.
> > > >> Looking for filesystems...
> > > >> Trying "/dev/mmc/blk0/part1"... failed
> > > >> Trying "/dev/mtdblock/3"... ok, but no zImage.
> > > >> No bootable filesystems found!
> > > boot>
> >
> > So at this point you had already written the jffs2 image to flash?
>
> yes
I'd guess the problem is that there is no symlink from zImage-whatever
to /boot/zImage, or the symlink is an absolute symlink rather than a
relative one.
It also looks like you're using an older version of LAB. That version
should work fine, but while you're at it you may as well install the
newest, which you can get at
http://handhelds.org/~mreimer/zImage-LAB-20060222.htc.
> When I try to write through LAB I get the following error when I try to
> mount the CF card (same for SD):
>
> boot> hda: SanDisk SDCFB-256, CFA DISK drive
> ide0 at 0xc4980000-0xc4980007,0xc498000e on irq 30
> hda: max request size: 128KiB
> hda: 501760 sectors (256 MB) w/1KiB Cache, CHS=980/16/32
> hda: cache flushes not supported
> /dev/ide/host0/bus0/target0/lun0: p1
> ide-cs: hda: Vcc = 5.0, Vpp = 0.0
>
> boot> mount /dev/hda1 /mnt ext2
> lab: mount -t ext2 /dev/hda1 /mnt failed with errno -2
> boot>
>
> The CF is in ext2 and the GPE image is on it, just double checked.
I think I know what's going on here: older versions of LAB use the
devfs style of device naming, but the newest version of LAB uses the
more conventional naming (/dev/hda1). With the old LAB you mount from
CF something like this:
mount /dev/ide/host0/bus0/target0/lun0/part1 /mnt ext2
To mount from SD:
mount /dev/mmc/blk0/part1 /mnt ext2
But if you're using the newest LAB, you would use the more familiar
device names:
mount /dev/hda1 /mnt ext2
mount /dev/mmcblk0p1 /mnt ext2
Hope this helps.
Matt
|
