Latest posts of: diefrisur

Show Posts
Pages: [1]

1	Linux Stuff / General Linux questions / Re: problems enabling UBIFS on NAND	on: February 20, 2010, 04:20:38 PM
After updating the kernel I got UBIFS working as well. Pls see here: http://plugcomputer.org/plugforum/index.php?topic=1279.msg8411#msg8411

2	Linux Stuff / General Linux questions / Re: ubimkvol fails	on: February 20, 2010, 04:18:39 PM
Having updated the kernel to 2.6.32.8 everything is now working. I do have a plug that is running Debian from the nand with UBIFS. After I figured how to update the kernel I started with a complete new installation of Debian on USB drive following the instructions in the Wiki (http://www.plugcomputer.org/plugwiki/index.php/Installing_Debian_To_Flash) If you update the kernel before converting internal flash root partition to UBIFS I could even use Code: ubiformat /dev/mtd2 -s 512 ubiattach /dev/ubi_ctrl -m 2 ubimkvol /dev/ubi0 -N rootfs -m mount -t ubifs ubi0:rootfs /mnt without any problem. The only thing that didn't work from that manual was the setup of the boot loader. For that point I found some useful instructions at http://www.jukie.net/~bart/blog/20100215083725 The ultimate problem then was that the sheeva stopped booting after uncompressing the kernel. I solved this by reentering Code: setenv mainlineLinux yes setenv arcNumber 2097 saveenv reset Thanks for your help.

3	Linux Stuff / Kernel / Re: kernel change	on: February 20, 2010, 05:53:25 AM
Thanks very much. It now works and I have the latest kernel running. I also changed the address from 0x0800000 to 0x08000000.

4	Linux Stuff / Kernel / Re: kernel change	on: February 19, 2010, 01:41:34 AM
Ah, thanks for pointing that out. This makes sense in that I think the kernel is loaded before the error message pops up. I'll try and let you know if this caused the error. I whish I had more time to really get into things and understand the details. So it's mostly trial and error...

5	Linux Stuff / Kernel / Re: kernel change	on: February 18, 2010, 04:37:47 AM
I used the uboot settings described in one of the earlier posts, i.e. setenv bootargs_console console=ttyS0,115200 setenv bootargs_root 'rw root=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext2' setenv bootcmd_mmc 'mmcinit; ext2load mmc 0 0x800000 /boot/uImage-2.6.30-sheevaplug' setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x0800000' but modified it slightly because I renamed the file to /boot/uImage. I tried both "/boot/uImage" and "/uImage" and I also tried both "0x800000" and "0x0800000" in the bootcmd_mmc because in the last line the address seems to be 0x0800000. So currently my bootargs should be setenv bootargs_console console=ttyS0,115200 setenv bootargs_root 'rw root=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext2' setenv bootcmd_mmc 'mmcinit; ext2load mmc 0 0x0800000 /boot/uImage' setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x0800000' Your guess re the partitions is correct and I had also thought that /boot was mounted before running the README. I can't doublecheck though because it's not booting anymore... I'll probably try updating uboot from 3.4.19 to 3.4.27 next as per the link you attached.

6	Linux Stuff / Kernel / Re: kernel change	on: February 17, 2010, 02:04:49 PM
I followed the above steps and the result was the following: Code: Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver ums-datafab usbcore: registered new interface driver ums-freecom usbcore: registered new interface driver ums-jumpshot usbcore: registered new interface driver ums-sddr09 usbcore: registered new interface driver ums-sddr55 mice: PS/2 mouse device common for all mice rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 i2c /dev entries driver cpuidle: using governor ladder cpuidle: using governor menu sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman mmc0: mvsdio driver initialized, lacking card detect (fall back to polling) Registered led device: plug:green:health mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address d555 mmcblk0: mmc0:d555 SD04G 3.79 GiB mmcblk0: p1 p2 p3 < p5 > mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver oprofile: using timer interrupt. TCP cubic registered NET: Registered protocol family 17 lib80211: common routines for IEEE802.11 drivers rtc-mv rtc-mv: setting system clock to 2010-02-17 21:06:40 UTC (1266440800) Waiting 10sec before mounting root device... EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 179:1. Freeing init memory: 140K Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. [<c00307e4>] (unwind_backtrace+0x0/0xdc) from [<c04033b8>] (panic+0x48/0x11c) [<c04033b8>] (panic+0x48/0x11c) from [<c002b5f0>] (init_post+0xd4/0xfc) [<c002b5f0>] (init_post+0xd4/0xfc) from [<c0008440>] (kernel_init+0xe0/0x110) [<c0008440>] (kernel_init+0xe0/0x110) from [<c002c40c>] (kernel_thread_exit+0x0/0x8) Any idea what went wrong?

7	Linux Stuff / General Linux questions / Re: problems enabling UBIFS on NAND	on: February 17, 2010, 06:10:00 AM
I hope to update the kernel to the most recent version maybe tonight or tomorrow using http://plugcomputer.org/plugforum/index.php?topic=1316.0 and let you know if this solves the problem.

8	Linux Stuff / General Linux questions / Re: ubimkvol fails	on: February 14, 2010, 07:25:23 AM
Okay, I've now installed a new debian on a SD card and tried it all over again. Now success but I've now the complete process with kernel version, mtd-utils version and error messages. I really hope this helps in any way to find an answer. Thanks! root@JGServer:/tmp# uname -a Linux JGServer 2.6.32-trunk-kirkwood #1 Mon Jan 11 10:57:12 UTC 2010 armv5tel GNU/Linux root@JGServer:/sys/class/ubi# dpkg -l \| grep mtd-utils ii mtd-utils 20090606-1 Memory Technology Device Utilities root@JGServer:/sys/class/ubi# root@JGServer:/tmp/ubifsinst# tar -C /tmp/ubifsinst -xf /tmp/rootfs.tar.gz root@JGServer:/tmp/ubifsinst# mkfs.ubifs -v -r /tmp/ubifsinst -m 2048 -e 129024 -c 4096 -o /tmp/ubifs.img mkfs.ubifs root: /tmp/ubifsinst/ min_io_size: 2048 leb_size: 129024 max_leb_cnt: 4096 output: /tmp/ubifs.img jrn_size: 8388608 reserved: 0 compr: lzo keyhash: r5 fanout: 8 orph_lebs: 1 super lebs: 1 master lebs: 2 log_lebs: 5 lpt_lebs: 2 orph_lebs: 1 main_lebs: 608 gc lebs: 1 index lebs: 12 leb_cnt: 619 UUID: F5E19CDD-9B19-4B0C-BD66-497AA91EC32B Success! root@JGServer:/tmp/ubifsinst# root@JGServer:/tmp/ubifsinst# cat > /tmp/ubi.cfg <<_EOF_ > [rootfs-volume] > mode=ubi > image=/tmp/ubifs.img > vol_id=0 > vol_size=400MiB > vol_type=dynamic > vol_name=rootfs > vol_flags=autoresize > _EOF_ root@JGServer:/tmp/ubifsinst# root@JGServer:/tmp/ubifsinst# ubinize -v -o /tmp/ubi.img -m 2048 -p 128KiB -s 512 /tmp/ubi.cfg ubinize: LEB size: 129024 ubinize: PEB size: 131072 ubinize: min. I/O size: 2048 ubinize: sub-page size: 512 ubinize: VID offset: 512 ubinize: data offset: 2048 ubinize: loaded the ini-file "/tmp/ubi.cfg" ubinize: count of sections: 1 ubinize: parsing section "rootfs-volume" ubinize: mode=ubi, keep parsing ubinize: volume type: dynamic ubinize: volume ID: 0 ubinize: volume size: 419430400 bytes ubinize: volume name: rootfs ubinize: volume alignment: 1 ubinize: autoresize flags found ubinize: adding volume 0 ubinize: writing volume 0 ubinize: image file: /tmp/ubifs.img ubinize: writing layout volume ubinize: done root@JGServer:/tmp/ubifsinst# root@JGServer:/tmp/ubifsinst# ubiformat /dev/mtd2 -s 512 -f /tmp/ubi.img ubiformat: mtd2 (nand), size 531628032 bytes (507.0 MiB), 4056 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes libscan: scanning eraseblock 4055 -- 100 % complete ubiformat: 4056 eraseblocks have valid erase counter, mean value is 9 ubiformat: flashing eraseblock 620 -- 100 % complete ubiformat: formatting eraseblock 4055 -- 100 % complete root@JGServer:/tmp/ubifsinst# root@JGServer:/tmp/ubifsinst# ubiattach /dev/ubi_ctrl -m 2 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.219770] Internal error: Oops: 817 [#1] Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.223883] last sysfs file: /sys/class/ubi/version Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.298528] Process ubiattach (pid: 1011, stack limit = 0xdebee270) Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.304823] Stack: (0xdebefde0 to 0xdebf0000) Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.309207] fde0: 00000000 c00c8b78 00000cb3 de69f000 de69f000 ffffffe2 00000000 de6f3800 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.317429] fe00: 00000000 c0206408 df858100 c00ce7bc df858100 df81ee60 00000000 c03c3f8c Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.325652] fe20: deae2060 00000000 00000000 c02ca160 00000000 c01cf518 debefef0 00000000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.333875] fe40: 00000000 00000000 df858100 deae2060 def91400 c00ce9e0 deb29400 c00ceb5c Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.342097] fe60: 00000001 0000003e 00000008 00000000 deb29400 00000000 deae2060 ffffff9c Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.350322] fe80: def91400 c00ce9e0 df4aed00 c00c9e74 df9bf000 deb29400 debea800 df9bf000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.358544] fea0: 00020001 ffffff9c 00000024 00000000 00000000 c00ca06c 00000000 de6f3800 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.366767] fec0: 00000000 debefed0 c02b5318 40186f40 de945000 bea476a0 00000003 bea476a0 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.374989] fee0: debee000 00000000 00000000 c0206794 ffffffff 00000002 00000000 00000000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.383212] ff00: 00000000 00000000 deb29400 40186f40 bea476a0 c00d8a28 00000000 deb29400 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.391436] ff20: 00000003 c00d912c 00000000 df4a9180 df4a9180 c03aa6f0 00000000 00020001 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.399659] ff40: 00000000 deb29400 00000003 00000000 00000002 deae2060 ded969c4 df4aed00 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.407882] ff60: 00000020 df4aed00 00000000 bea476a0 40186f40 00000003 deb29400 debee000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.416104] ff80: 00000000 c00d91e4 bea479db 00000000 00000000 bea47740 00000003 00000036 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.424327] ffa0: c0027048 c0026ea0 00000000 bea47740 00000003 40186f40 bea476a0 00000003 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.432550] ffc0: 00000000 bea47740 00000003 00000036 00016008 000156b0 000156cc 00000000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.440773] ffe0: bea479db bea476a0 00009da0 400e419c 60000010 00000003 00000000 00000000 Message from syslogd@JGServer at Feb 14 15:17:04 ... kernel:[ 1874.508396] Code: e1a01000 e59f000c eb0a25b6 e3a03000 (e5833000) Segmentation fault root@JGServer:/tmp/ubifsinst#

9	Linux Stuff / General Linux questions / Re: ubimkvol fails	on: February 11, 2010, 03:05:28 AM
I had really thought I started the system from USB, in particular because I formatted the nand with ubiformat before I tried ubiattach. Sorry, I think I forgot to mention that everything worked fine including ubiformat. The error messages come up when I start ubiattach. I wanted to install a clean system on SD and try it all over again anyway either tonight or tomorrow. I then hope to transfer the console output into a file by using "> output.txt" or something similar and then get such file from the plug onto a USB drive from where I can copy the entire output. Anyway, if you have any thoughts nevertheless assuming that I bootet from USB and not from nand, that be great.

10	Linux Stuff / General Linux questions / Re: ubimkvol fails	on: February 10, 2010, 03:16:00 PM
I downloaded a rootfs.tar.gz from http://www.mediafire.com/sheeva-with-debian Then I followed exactly the steps described above,i.e. Code: unix root# mkdir /tmp/ubi-content unix root# tar -C /tmp/ubi-content -xf /path/to/your/rootfs.tar unix root# mkfs.ubifs -v -r /tmp/ubi-content -m 2048 -e 129024 -c 4096 -o /tmp/ubifs.img unix root# cat > /tmp/ubi.cfg <<_EOF_ [rootfs-volume] mode=ubi image=/tmp/ubifs.img vol_id=0 vol_size=400MiB vol_type=dynamic vol_name=rootfs vol_flags=autoresize _EOF_ unix root# ubinize -v -o /tmp/ubi.img -m 2048 -p 128KiB -s 512 /tmp/ubi.cfg unix root# ubiformat /dev/mtd2 -s 512 -f /tmp/ubi.img I'm too stupid though to get the screen output copied from my putty console to past it here. So I can only describe. The error messages are first the same as when using ubimkvol, i.e. ubi_io_write: error -5 while writing ... and loads of similar errors Then at some point it says kernel BUG at /build/buildd-linux-2.6_2.6.32-5-armel-EFZj80/linux-2.6-2.6.32/debian/build/source_armel_none/mm/slub.c:2969! At the end there are messages like Message from syslogd@JGServer1 at date kernel xyz Internal error: Oops: 817 and further messages of this style. How can I get a copy from my putty console output copied to insert it here? There are so many errors I can't possibly mention all of them here. Any idea? The above is probably not really helpful.

11	Linux Stuff / General Linux questions / Re: ubimkvol fails	on: February 09, 2010, 04:13:03 PM
I'm struggling with ubimkvol as well. The above procedure didn't work. After ubiformat finished I received a long list of messages from the kernel. I came across this link http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail According to this it might help to turn off CONFIG_MTD_NAND_VERIFY_WRITE in the kernel. Has anybody tried this before? How would I do this? I'm pretty new to Linux and therefore a bit reluctant to do such steps without a good description of the relevant steps.

Pages: [1]