dockstar boot just with serial cable possible

Hi,
on my dockstar i have installed the "Linux-2.6.32.18-dockstar" kernel rescue image. On my harddisk I've installed debian. Now i have the problem that the dockstar is just booting when the serial cable is connected. It just have to be connected to the computer. It also does not boot into the recovery without the serial cable. Has anyone an idea? Anything to set with fw_printenv?
Thanks Manfred

We can't tell without seeing the contents of env... why don't you post that and maybe someone here will see the problem.
(don't forget to xx:xx:xx:xx:xx:xx out your MAC/ethaddr.)

=====================================================

• davy's Github Repo's rescue-dg

here ar my env... sorry!

ethact=egiga0
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x80000i
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.ti
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_pas
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x11000i
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800e
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usbs
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; theni
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; ret
ethaddr=xx:xx:xx:xx:xx:xx
rescue_installed=1
bootdelay=10
stdin=serial
stdout=serial
stderr=serial
arcNumber=2097

Have you tried turning on netconsole?

Also, why are you using the sheevaplug arcNumber? IIRC, Dockstar is 2998.

I don't know if that is the problem, but it might be worth trying.

=====================================================

• davy's Github Repo's rescue-dg

updated uboot to 2011.12, rescue to 2.8.1, set arcNumber to 2998...

still no change.

configured netconsole -> bootmessage "host 192.168.1.xxx is alive" but no output on the nc console.
Seems like the bootloader or something else is testing if a serial connection is possible.
The cable has just to be connected to the computer with no running minicom, and it boots.
Without cable the LED is not even going on...

any ideas?

have you tried socat instead?

some users report markedly better response/results w/ socat..

command would be something like:

socat STDIO UDP-LISTEN:6666

BTW, are you using Linux, Windows, OS X...?

Firewalls off? (that is Firewalls w/i your desktop computer)

=====================================================

• davy's Github Repo's rescue-dg

Edited 1 time(s). Last edit at 06/05/2012 07:13PM by davygravy.

I work on Ubuntu 12.04, socat shows the messages now, but when the serial cable is disconnected, there is nothing ....

Do you know if there is a check for the serial connection in the boot sequence? Could this be disabled?

I don't think there is such a check.

Do you have netconsole enabled?

Netconsole should give your the ability to see some of the things from serial the serial port, especially uboot output, while you are booting. Using netconsole, you are unlikely to see anything after booting.

Via network, you really have to use ssh to see much of what is going on.

=====================================================

• davy's Github Repo's rescue-dg

I can't see messages on the netconsole at the beginning, first i see stuff on the serial until the nc-host is checked. is it possible that the system awaits a keyboard (hit any key to stop autoboot...)?

I don't think that's likely.
It normally does a countdown and then tries to boot.

Are you sure the netconsole settings & commands are correct.?

=====================================================

• davy's Github Repo's rescue-dg