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...)?by maxdock - uBoot
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?by maxdock - uBoot
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 cabby maxdock - uBoot
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 $mtdpartsby maxdock - uBoot
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_printenby maxdock - uBoot