• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  General Category / General Discussion / Re: UBIFS mount fails due to unknown filesystem on: January 27, 2010, 06:04:11 AM
I think you need ubi0:root, Not ubi2:root.
Thanks, you've got a point, but still I had no success.
mount -t ubifs ubi0:root /mnt/ubi
mount: ismeretlen fájlrendszertípus: "ubifs"
Meanwhile, I have discovered that dmesg contains some useful(?) information on the error:
UBIFS error (pid 1874): ubifs_get_sb: cannot open "ubi0:root", error -19
Some googling suggests that I may got the volume name wrong, I will look into that.

Update: I figured it out!
The missing step was an
ubimkvol /dev/ubi0 -m -N rootfs
before mounting.
2  Linux Stuff / Kernel / Re: new release on: January 27, 2010, 05:52:49 AM
I am curious which subdirectory in sheeva.with-linux.com? I can not find it.
3  General Category / General Discussion / UBIFS mount fails due to unknown filesystem on: January 26, 2010, 05:01:48 AM
I am trying to put ubifs on the nand, currently to no avail. Here is what I got:
  • I formatted mtd2 as a clean ubifs.
    ubiformat /dev/mtd2
  • I attached mtd2 as ubi0:
    ubiattach /dev/ubi_ctrl -m 2
    UBI device number 0, total 4041 LEBs (521385984 bytes, 497.2 MiB), available 3997 LEBs (515708928 bytes, 491.8 MiB), LEB size 129024 bytes (126.0 KiB)
  • Tried to mount the result:
    mount -t ubifs ubi2:root /mnt/ubi
    mount: ismeretlen fájlrendszertípus: "ubifs"
    (unknown filesystem type: "ubifs")
  • checked /proc/filesystems:
    cat /proc/filesystems |grep ubi
    nodev   ubifs

Does anyone have a suggestion what I did wrong?
I am using the kernel and debian lenny, except for the mtd-utils package, which is from squeeze and has version 20090606-1.
4  Linux Stuff / Kernel / Re: new release on: January 26, 2010, 03:28:42 AM
I read somewhere in this forums the 0x400000 is not a good place to load kernel, I recommend use 0x02000000 for kernel and 0x01100000 fro initrd/initramfs.
Thanks for the recommendation, now loading the kernel into memory works. However, the bootm 0x02000000 0x01100000  command does have difficulties:
## Booting image at 02000000 ...
   Image Name:   Linux-
   Created:      2010-01-18  22:56:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861348 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading Ramdisk Image at 01100000 ...
Bad Magic Number�
(And it reboots after that...) It seems that the problem is with the initrd, as the kernel boots if I only specify bootm 0x02000000. This is all right for me, as I do not use an encrypted or remote root file system currently.
However, I may want to do that later, so if anyone has experience with debian initrd creation on the sheeva plug, please don't hold yourself back to share it with me.
5  Linux Stuff / Kernel / Re: new release on: January 26, 2010, 03:09:05 AM
Where did sheeva- come from?

I use:
ext2load mmc 0:1 0x800000 /uImage; bootm 0x800000
and always hard link uImage to the latest kernel, so I don't need to change anything under uboot.  Copy in files, boot from slogin.  Never need serial console.
Well, that is okay if your boot process does not hang... Smiley
6  Linux Stuff / Kernel / Re: new release on: January 22, 2010, 07:16:37 AM
I tried tried to use this kernel image, to no avail. If I type the following in uboot prompt:
ext2load mmc 0 0x0800000 /sheeva-
ext2load mmc 0 0x400000 /sheeva-
I simply hangs there, I can't run the bootm command, I have to hard reset.
Does anyone have any idea what the problem could be?
Maybe the kernel is too big, and overwrites something (the uboot itself, maybe)?
Did anyone have a similar problem?

Ps: I generated the initrd with debian's standard tools, but even without loading it, the ex2load for the uimage hangs. However, it loads fine with the old kernel (kirkwood's 2.6.30-2).
Ps2: U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19
7  General Category / General Discussion / Re: Getting serial console working, on ubuntu karmic on: December 15, 2009, 06:33:06 AM
My problem was that although /dev/ttyUSB0 appears, /dev/ttyUSB1 does not appear, and I can't connect to /dev/ttyUSB0 with any terminal program.
It does not matter if I let udev do the module loading or I load ftdi_sio manually.

Finally!  I forget what led me to this document but it was the final piece I needed to get my kernel to recognize the serial usb console for the plug in Linux.

I've read the above document, and it gave a tip about removing the brltty package, which I did.
After that, there was still no /dev/ttyUSB1, but I could connect to /dev/ttyUSB0 with gtkterm. Hoorray!

Someone should put this info into the wiki, as it is really useful for ubuntu users...

Pages: [1]