bodhi Wrote: > So the HDD rootfs is new, not the same one you run > on USB. Yes. They both use the same 'source' tarball, indeed. > Can you backup (tar) the USB rootfs, and "untar" > it to the HDD (using a different Linux box)? I will try. But i don't understand how can be correlated... the CRC error are about the kernel, that is a file...by marcogaio - Debian
bodhi Wrote: > Last question: were you the root user when you tar > the rootfs to the HDD? and being root the whole ti > me after that? Do you mean 'untar' i suppose... yes, i was root. Effectively, i've boot into the USB key and then partition, format and untar your rootfs tarball into the HD. All done as root.by marcogaio - Debian
I've had tried 'sata' with no luck, so i think SCSI was the correct option. Sorry. Anyway, same result: Marvell>> setenv usb_make_boot_args 'setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_si ze)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),32m@0x0(flash) root=LABby marcogaio - Debian
I was sure i've done the right things, anyway i've redone all the stuff. I'm using exactly the same kernel/initrd that boot on the USB key; i've copied them on the HD and i've double checked it (the USB key is mounted as /mnt, of course): root@debian:/boot# md5sum uI* /mnt/boot/uI* 408fd043a0e53507adead04e1080b270 uImage 74cec6beff390144c60de3f2ecb0e725 uImageby marcogaio - Debian
Ahem... some hint/feedback on how the same kernel boot from USB and return 'CRC error' on sata? Thanks.by marcogaio - Debian
I'm having trouble booting from HDD, i catch CRC errors. I'm using the same rootfs of the my USB key, that work flawlessy. Same Kernel, Same Initrd. The only different things is the partiton setup: i've created a little (1GB) /dev/sda1 partition with /boot. I'm using to boot this environment: Marvell>> setenv usb_make_boot_args 'setenv bootargs console=ttby marcogaio - Debian
> Precisely, uInitrd is old. And that is no good. As stated, i've installed some package (mdadm, lvm2) that trigger an initrd rebuild, but i've not put / (root) filesystem on software raid or LVM, so i've not re mkimage-ed it. > And furthermore, even you did not see newer > mainline kernel files afer apt-get dist-upgrade > this time, it does not mean that you wby marcogaio - Debian
> ls -lart /mnt/boot/ > There is an important reason to always see the > files listing in reversed chronological order. > You'll be abe to check mistake easily that way. Ok, sure, but still i don't see the point: root@albus:~# ls -lart /mnt/boot/ totale 66968 drwxr-xr-x 21 root root 4096 feb 17 2015 .. -rw-r--r-- 1 root root 140949 gen 26 2016 config-4.4by marcogaio - Debian
> > Clearly, i've double checked the package > > installed/upgraded, doing the dist-upgrade, and > > none was added. > That's why I want to see the /boot directory. I > want to doublecheck what kernel uImage and uInitrd > files are being used. Ok, as you want... root@albus:~# ls -la /mnt/boot/ totale 66968 drwxr-xr-x 4 root root 4096 dic 9 1by marcogaio - Debian
> That's not "stock" rootfs :) it's my Debian build. Ahem sorry... i mean 'stock' as 'non upgraded kernel (and DTS). Your last rootfs! > dist-upgrade is not recommended. dist-upgrade will > install mainline Debian kernel. Clearly, i've double checked the package installed/upgraded, doing the dist-upgrade, and none was added. And i'by marcogaio - Debian
> Now, some more experimenting... Ok, the new kernel see all the 4 disks in bays. Installing 'mdadm' and 'lvm2' i was able to bind and mount the disks. Good. There's some things i can do for the project? Dump something? A little strange thing: root@debian:~# fw_printenv Cannot read bad block mark: Invalid argument Next thing to do, i suppose, is upgradeby marcogaio - Debian
> You can find how to set up to boot the ix4-200d > with stock u-boot using USB rootfs here: > http://forum.doozan.com/read.php?3,25120 Bingo! I was able to boot stock rootfs, after fiddling a bit with correct cut&paste of setenv row into minicom... But after that, i've upgrade the kernel to the latest 4.8.3 (and really, done a 'apt-get update && apt-get disby marcogaio - Debian
> You can find how to set up to boot the ix4-200d > with stock u-boot using USB rootfs here: > http://forum.doozan.com/read.php?3,25120 Sorry, i've quickly read this forum, but i've found (for me, at least ;) relevant info on booting from MTD, not USB. You have pasted wrong link or i'm really dumb? Sorry... In rootfs and kernel download topic i've found: &gby marcogaio - Debian
Sorry, i came back after loong time. I've finally setup my USB key with rootfs, as explained in http://forum.doozan.com/read.php?2,12096 , but i've not understood how to boot from it. Seems to me that i've to modify my environment, but i've not understood how. My current environment is: Marvell>> printenv bootdelay=1 baudrate=115200 loads_echo=0 ipaddr=10by marcogaio - Debian
bodhi Wrote: > entire serial bootlog. Attached. > > d) if a modification of uboot environment is > > mandatory, or not > Yes. See previous posts in this thread. OK. There's some way to ''save'' the current uboot environment? > Follow the instruction and create th Debian 4.4 > rootfs on a single ext3 partition on USB: > httpby marcogaio - Debian
First post here, sorry me if i say some dumb thing. I'm a rather log linux/debian user, but i've a little experience on ARM, mostly OpenWRT. Someone gift me a ix4-200d. The machine was in decent shape, who land me say that was retired because ''does not work'' (generically). After receiving id, and googling a bit, i've found a way to reset to default state aby marcogaio - Debian