Re: Redboot won't load initrd.gz via ymodem

[mark@jumpingbean.co.za]

Hi Loïc,

Thanks for the help. I have an intel S44000E. I will give screen a go. I
think I may have bricked the device when I did a
"fis init". According to everything I read though I should be able to get
a new image installed with ymodem.

The networking doesn't appear to work anymore :( Even though ip_address
shows the ip address it would use. I have no rammode,ramdisk or zImage
when I do "fis list" it only shows the redboot image and the redboot
config image.

I will give your suggestion a try and let you know.

thanks

Mark


> On Wed, Dec 30, 2009, mark@jumpingbean.co.za wrote:
>> I would dot he same with the zImage as well if I can get this to work.
>> The
>> problem is that the initrd.gz image wont download via ymodem. I am using
>> minicom. I wait for a "C" to show then do the c-A S thing to send the
>> file
>> but it just times out. First time using minicom so maybe I don't know
>> how
>> to use it properly.
>
>  I suggest you use screen as your terminal and "sb" (from lrzsz) to send
>  the initrd with xmodem or ymodem.  e.g.:
>     load -v -m ymodem -b 0xsomeaddress -r
>
>  from screen type ^A and « : » then:
>     exec !!.| sb --ymodem /some/file
>
>  Another good option with the Thecus (you have a Thecus, right?) is
>  http:
>     load -r -v -b 0x01d00000 -h 192.168.0.12 -m http /kernel
>     load -r -v -b 0x01000000 -h 192.168.0.12 -m http /initrd
>
>  That's much faster too.
>
> --
> Loïc Minier
>
>
> --
> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>