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

Re: Debian lenny on the QNAP TS-209 II



On Saturday 27 September 2008, you wrote:
> I guess us, less fortunate ones, who used the broken image will need to
> hook up a serial port though?

Hmm. Yes, as the broken image has been flashed and you can thus not boot
the original OS anymore I'm afraid that is true.

If you do get the serial console, you can "fix" the issue without the
need to reflash by following these steps:

- break off the automatic boot process
  After that the uboot prompt should be displayed.
- add the boot parameter 'BOOT_DEBUG=3' to the uboot variable bootargs
  (first and last command are just for verification; there's no need to
  save the change to flash using 'setenv'):

Marvell>> printenv fsargs
fsargs=setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw initrd=0x800000,0x3fffff
Marvell>> setenv fsargs 'setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw initrd=0x800000,0x3fffff BOOT_DEBUG=3'
Marvell>> printenv fsargs
fsargs=setenv bootargs console=ttyS0,115200n8 root=/dev/ram rw initrd=0x800000,0x3fffff BOOT_DEBUG=3

- type 'run bootcmd'
  The installer should now boot into a debug shell.
- at the debug shell prompt type 'echo >>/var/lib/dpkg/status'
  This adds a single newline to the status file which should be enough to
  avoid the bug.
- 'exit' the debug shell (twice)
  The installer should now continue to load and start normally.

Cheers,
FJP

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: