[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: server people.debian.org down



http://forum.doozan.com/read.php?3,7852

--

Sent from a mobile device

Tim Fletcher

On 10 Jun 2012, at 12:53, kqt4at5v@gmail.com wrote:

> On Sun, 10 Jun 2012, Tim Fletcher wrote:
> 
>> On 10/06/12 00:28, kqt4at5v@gmail.com wrote:
>>> On Sat, 9 Jun 2012, Martin Michlmayr wrote:
>>>> * kqt4at5v@gmail.com <kqt4at5v@gmail.com> [2012-06-09 16:17]:
>>>>> I am attempting to install Debian on a Guruplug and I need to update
>>>>> u-boot. It seems that people.debian.org is down or is it just me. I
>>>>> need to get
>>>>> http://people.debian.org/~tbm/u-boot/2011.12-3/guruplug/u-boot.kwb
>>>>> Is there a mirror?
>>>> Use this in the meantime:
>>>> http://www.cyrius.com/tmp/u-boot/guruplug/u-boot.kwb
>>> I spoke too soon. Now I am in real trouble. I installed the u-boot update and it will now respond at all.
>>> Marvell>> ext2load usb 0:1 0x0800000 u-boot.kwb
>>> Loading file "u-boot.kwb" from usb device 0:1 (usbda1)
>>> 227200 bytes read
>>> Marvell>> nand erase 0x0 0x60000
>>> NAND erase: device 0 offset 0x0, size 0x60000
>>> Erasing at 0x40000 -- 100% complete.
>>> OK
>>> Marvell>> nand write 0x0800000 0x0 0x60000
>>> NAND write: device 0 offset 0x0, size 0x60000
>>> 393216 bytes written: OK
>>> Marvell>> reset
>>> resetting ...
>>> Even after a power reset, nothing.
>>> How do I recover this?
>> 
>> You can load a new uboot over serial during the early boot process, if you use the tool kwboot.
>> 
>> sudo ./kwboot -b u-boot.kwb -p /dev/ttyUSB0
>> 
>> Assuming you have either a backup of the original uboot or a known good uboot this should allow you to get back into the plug and update uboot.
> 
> Where can I find kwboot?
> 
> Richard
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] alpine.DEB.2.00.1206100653080.4809@tehzcl2.tehzcl-arg">http://lists.debian.org/[🔎] alpine.DEB.2.00.1206100653080.4809@tehzcl2.tehzcl-arg
> 


Reply to: