I may be mixing up memories from Zaurus and dockstar. But I remember that on
one of these if one forgot to erase the flash partition where the kernel was
about to be written next boot would fail.
But I may be putting you of with this. Sorry for any inconvinience.
________________________________
Da: Jim Hammack <hamm...@gotslack.org>
A: armedslack@lists.armedslack.org
Inviato: Giovedì 9 Febbraio 2012 16:20
Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug
Davide,
I'm not sure what you mean by erasing the partition. I am
using these commands taken from INSTALL_KIRKWOOD.TXT:
setenv arcNumber 2659
setenv mainlineLinux yes
setenv ipaddr 192.168.2.1
setenv serverip 192.168.2.7
saveenv
reset
usb start
tftpboot 0x01100000 armedslack-13.37/uinitrd-kirkwood.img
tftpboot 0x00800000 armedslack-13.37/uImage-kirkwood
setenv bootargs console=ttyS0,115200 nodhcp kbd=us root=/dev/ram
rw
bootm 0x00800000 0x01100000
*** install armedslack and reboot ***
setenv bootargs_console console=ttyS0,115200
setenv bootargs_root 'root=/dev/sda3 waitforroot=10 rootfs=ext4'
setenv bootcmd 'setenv bootargs $(bootargs_console)
$(bootargs_root); run bootcmd_slk ; reset'
setenv bootcmd_slk 'usb start;ext2load usb 0:1 0x01100000
/uinitrd-kirkwood;ext2load usb 0:1 0x00800000
/uImage-kirkwood;bootm 0x00800000 0x01100000'
setenv ethaddr F0:AD:4E:00:E5:BD
setenv eth1addr F0:AD:4E:00:E5:BE
saveenv
reset
Thanks,
Jim
On 02/09/2012 02:38 AM, Davide wrote:
If you can boot the image via tftp but subsequently not from flash then maybe
it war not flashed correctly.
>Are you erasing partition before writing kernel to it ?
>
>
>
>
>________________________________
> Da: Jim Hammack <hamm...@gotslack.org>
>A: armedslack@lists.armedslack.org
>Inviato: Giovedì 9 Febbraio 2012 3:36
>Oggetto: Re: [ARMedslack] ARMedslack hangs during boot on Dreamplug
>
>
>Brennan,
>
> Thanks for the suggestion, but I downloaded the
files again and made sure they were binary
transfers, and still no luck. I also downloaded
armedslack-current (I had the original
armedslack-13.37 that I used on my sheevaplug) but
still no change. I'm confused because the kernel
boots after the initial tftpboot and I can install
software, configure the system, etc., but when I try
to reboot the system hangs.
>
> Jim
>
>On 02/06/2012 08:32 PM, Brennan Newman wrote:
>Jim,
>> I had this same issue and it was driving me crazy, it is a simple fix (at
>>least for me). Simply re-download the kernel images and make sure that you
>>are transferring it over in binary. I had used Filezilla to get my install
>>and it was set to transfer all files in ascii by default which according to
>>many people in the world today mangles binary files pretty badly. Hope this
>>helps.
>>
>>
>>Brennan
>>
>>
>>On Mon, Feb 6, 2012 at 8:27 PM, Jim Hammack <hamm...@gotslack.org> wrote:
>>
>>I've been trying to install ARMedslack on my Dreamplug (ser: 1148-XXXXXX) by
>>following Stuart's excellent instructions in INSTALL_KIRKWOOD.TXT, but have
>>been unable to get the system to boot. I believe it is due to a problem
>>with my u-boot which I scrambled earlier. I have been able to find only one
>>version of u-boot that will run on this machine (the guruplug version from
>>http://www.armedslack.org/maint_kirkwooduboot loads but hangs after a
>>'reset'). This one works:
>>>
>>>Marvell>> version
>>>
>>>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2
(Jun 15 2011 - 22:44:57)
>>>Marvell-DreamPlug
>>>armv5tel-softfloat-linux-gnueabi-gcc (Gentoo
4.4.4-r2 p1.3, pie-0.4.5) 4.4.4
>>>GNU ld (GNU Binutils) 2.20.1.20100303
>>>
>>>I am following Stuart's instructions with two
exceptions:
>>>
>>>1. I am using dream-2.6.38.4-uImage (renamed
uImage-kirkwood) from with-linux instead of
uImage-kirkwood from the distribution due to a
known problem with uImage-kirkwood on the
Dreamplug.
(http://lists.armedslack.org/2011-August/000978.html)
>>>2. I am using a fat16 boot partition rather
that the ext2 partition Stuart uses in his
documentation, so I have changed all references
to "ext2load" to "fatload" in the bootcmd
>>>
>>>The system loads uinitrd-kirkwood okay, then
loads uImage-kirkwood (which is really
dream-2.6.38.4-uImage), but hangs after:
>>>
>>>"Uncompressing Linux... done, booting the
kernel."
>>>
>>>I don't think this is the problem, but does
anyone see any problems with my u-boot
variables? Also, I've read that newer
Dreamplugs (#114 and later) have some
differences from the earlier version. Could
this be why the majority of u-boot versions I've
found do not run on this machine? Any ideas on
where I can find a suitable u-boot? I tried the
version referenced here:
>>>(http://www.newit.co.uk/forum/index.php?topic=1977.0) but that version hangs
>>>also.
>>>
>>>Any input is appreciated!
>>>
>>> Thanks,
>>> Jim
>>>
>>>printenv and boot details follow:
>>>
>>>Marvell>> printenv
>>>arcNumber=2659
>>>baudrate=115200
>>>bootargs_console=console=ttyS0,115200
>>>bootargs_root=root=/dev/sda3 waitforroot=10
rootfs=ext4
>>>bootcmd=setenv bootargs $(bootargs_console)
$(bootargs_root); run bootcmd_slk ; reset
>>>bootcmd_slk=usb start;fatload usb 0:1 0x01100000
/uinitrd-kirkwood;fatload usb 0:1 0x00800000
/uImage-kirkwood;bootm 0x00800000 0x01100000
>>>bootdelay=3
>>>eth1addr=02:50:43:ba:45:cb
>>>ethact=egiga0
>>>ethaddr=00:DE:AD:C0:FF:EE
>>>ipaddr=192.168.2.1
>>>mainlineLinux=yes
>>>serial_num=DS2-1148-000934
>>>serverip=192.168.2.7
>>>stderr=serial
>>>stdin=serial
>>>stdout=serial
>>>
>>>Environment size: 561/65532 bytes
>>>Marvell>> reset
>>>
>>>U-Boot 2011.03-00012-g1a93b51-dirty-pingtoo-v1.2
(Jun 15 2011 - 22:44:57)
>>>Marvell-DreamPlug
>>>
>>>SoC: Kirkwood 88F6281_A1
>>>DRAM: 512 MiB
>>>SF: Got idcodes
>>>00000000: c2 20 15 c2 20 . ..
>>>SF: Detected MX25L1605D with page size 256,
total 2 MiB
>>>In: serial
>>>Out: serial
>>>Err: serial
>>>Net: egiga0, egiga1
>>>88E1121 Initialized on egiga0
>>>88E1121 Initialized on egiga1
>>>Hit any key to stop autoboot: 0
>>>(Re)start USB...
>>>USB: Register 10011 NbrPorts 1
>>>USB EHCI 1.00
>>>scanning bus for devices... EHCI timed out on TD
- token=0x80008c80
>>>4 USB Device(s) found
>>> scanning bus for storage devices... Device
NOT ready
>>> Request Sense returned 02 3A 00
>>>2 Storage Device(s) found
>>>reading /uinitrd-kirkwood
>>>
>>>5755094 bytes read
>>>reading /uImage-kirkwood
>>>
>>>2033192 bytes read
>>>## Booting kernel from Legacy Image at 00800000
...
>>> Image Name: Linux-2.6.38.4-kirkwood
>>> Image Type: ARM Linux Kernel Image
(uncompressed)
>>> Data Size: 2033128 Bytes = 1.9 MiB
>>> Load Address: 00008000
>>> Entry Point: 00008000
>>> Verifying Checksum ... OK
>>>## Loading init Ramdisk from Legacy Image at
01100000 ...
>>> Image Name: Slackware ARM Initial RAM disk f
>>> Image Type: ARM Linux RAMDisk Image (gzip
compressed)
>>> Data Size: 5755030 Bytes = 5.5 MiB
>>> Load Address: 00000000
>>> Entry Point: 00000000
>>> Verifying Checksum ... OK
>>> Loading Kernel Image ... OK
>>>OK
>>>
>>>Starting kernel ...
>>>
>>>Uncompressing Linux... done, booting the kernel.
>>>
>>>
>>>_______________________________________________
>>>ARMedslack mailing list
>>>ARMedslack@lists.armedslack.org
>>>http://lists.armedslack.org/mailman/listinfo/armedslack
>>>
>>
>>
>>
>>_______________________________________________
ARMedslack mailing list ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
>_______________________________________________
>ARMedslack mailing list
>ARMedslack@lists.armedslack.org
>http://lists.armedslack.org/mailman/listinfo/armedslack
>
>
>
>
>
>_______________________________________________
ARMedslack mailing list ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
_______________________________________________
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack_______________________________________________
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack
