On 25/10/15 12:27, ioan stan wrote:
Hi Jacco,
I’ve tried the dreamplug image on an SD card but the box gets stuck into
the message below. This is probably a uBoot issue.
If's a kernel issue.
6 USB Device(s) found
scanning usb for storage devices... 2 Storage Device(s) found
3665856 bytes read in 418 ms (8.4 MiB/s)
17811253 bytes read in 1726 ms (9.8 MiB/s)
## Booting kernel from Legacy Image at 06400000 ...
Image Name: 3.10.14-100.fc18.armv5tel.kirkwo
Created: 2015-09-20 16:39:00 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665792 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 07400000 ...
Image Name: initramfs
Created: 2015-09-20 16:39:00 UTC
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 17811189 Bytes = 17 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
The boot variables are
Marvell>> printenv
baudrate=115200
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootwait
bootargs_console=console=ttyS0,115200
bootcmd=usb start; ${loadImage}; ${loadInitrd} ; bootm 0x6400000 0x7400000
bootcmd_usb=usb start; ext2load usb 1:1 0x00800000 /uImage; ext2load usb
1:1 0xd
bootdelay=3
egiga0=02:50:43:ae:ae:0b
egiga1=02:50:43:34:63:dc
eth1addr=02:50:43:34:63:dc
ethact=egiga0
ethaddr=02:50:43:ae:ae:0b
loadImage=ext2load usb 1:1 0x6400000 uImage
loadInitrd=ext2load usb 1:1 0x7400000 uInitrd
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200
x_bootargs_root=root=/dev/sda2 rootdelay=10
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd_kernel=ext2load usb 1 0x6400000 uImage
x_bootcmd_usb=usb start
Environment size: 755/4092 bytes
Marvell>>
Try:
Marvell>> setenv machid=0xa63
Marvell>> saveenv
The SD card is USB 1 as shown below from uBoot.
Marvell>> ext2ls usb 1:1
<DIR> 1024 .
<DIR> 1024 ..
<DIR> 12288 lost+found
<DIR> 1024 grub
582234 initrd-plymouth.img
3665856 uImage
2 boot.scr
<DIR> 1024 dtb-3.10.14-100.fc18.armv5tel.kirkwood
17811253 uInitrd
179 .vmlinuz-3.10.14-100.fc18.armv5tel.kirkwood.hmac
1688755 System.map-3.10.14-100.fc18.armv5tel.kirkwood
125174 config-3.10.14-100.fc18.armv5tel.kirkwood
17811189 initramfs-3.10.14-100.fc18.armv5tel.kirkwood.img
3665792 vmlinuz-3.10.14-100.fc18.armv5tel.kirkwood
3665856 uImage-3.10.14-100.fc18.armv5tel.kirkwood
17811253 uInitrd-3.10.14-100.fc18.armv5tel.kirkwood
35 klist.txt
Marvell>>
And it is sdb from OS point of view.
Once you have set the GuruPlug's machid (I assume you are running
this on a DreamPlug), the kernel will boot, but it will get
stuck during the boot when it tries to load the orion_nand
driver (since this hardware isn't present on the dreamplug. You
will need to either remove the orion_nand drier (mv it out of
the way, or preferably, add
blacklist orion_nand
to /etc/modprobe.d/blacklist.conf
and do
depmod -a
but that is quite difficult if you don't have a working ARM
machine where you can mount the FS and do it in a chroot.
After that it should boot and most things should work. I'm
working on getting a rpm of 3.10.91 kernel built and tested
at the moment. I have an un-rpm-ed 3.10.90 version up and
running with zfs-fuse rootfs working on both the DreamPlug
and SheevaPlug, but I want to make sure the kernel is
packaged up properly in this case since the full mainline
support for the device is available.
uBoot version
U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 21:53:14)
Marvell-DreamPlug
Good, so you have the pretty recent u-boot. It is the same version
I have updated my *Plugs to over the weekend.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
