Pogoplug E2 - get LED right

Hi

I managed to boot into Deboian again, but I had to reset the uBoot variables. Unfortunately, I have forgotten which ones I changed.

Now everything works, but not the LEDs - the light on the Pogoplug is always orange and does not turn green, and also stays orange after a shutdown (via ssh).

I remember that I set the arcNumber and the machineID (or similar).

Now I read to set

fw_setenv arcNumber 3542

but the LED is still only orange.

What am I missing?

I am positive, that it was working befor I reset the values with my old Deian installation.

I have:

machid=dd6

And I get the green LED.

Thanks - I'll try it out tomorrow. Which arcNumber are you using?

Same as you:

arcNumber=3542

Hm - now I can't boot neither into Debian nor into the rescue System and netconsole shows me nothing either.

Any suggestions (apart from a serial console into which I am going to invest)?

ethact=egiga0
bootdelay=3
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
stdin=serial
stdout=serial
stderr=serial
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 0x800000; else run pogo_bootcmd; fi
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.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
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 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
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 $usb_custom_params
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; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:00:49:4B
rescue_installed=1
arcNumber=3542
serverip=192.168.1.2
ipaddr=192.168.1.100
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
machid=dd6

rkrug,

> Hm - now I can't boot neither into Debian nor into
> the rescue System and netconsole shows me nothing
> either.

First, should not change the envs on Pogo E02 that way if you're not absolutely sure it will work. Use netconsole to change envs with setenv, and then boot into Debian. Then use fw_setenv to set them. Changing arcNumber will cause problem with rescue system.

> Any suggestions (apart from a serial console into
> which I am going to invest)?

If those were only 2 variables that you've changed, then netconsole should still be working. Try booting and connect with netconsole again. But if you've played with other variables, then some changes might have caused problems. Also, if you've changed preboot variable, a typo in there could have bricked it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks bodhi - this sounds encouraging.

netconsole didn't show anything because I have s typo in the server ip.

What are the correct values for arcNber and machid I should use?

Rainer

Rainer,

> netconsole didn't show anything because I have s
> typo in the server ip.

You could temporarilly set this serverip=192.168.1.2 on the netconsole server box as static IP. Just to get it connect and solve this problem. And change it back to the orginal one later.

>
> What are the correct values for arcNber and machid
> I should use?
>
>

It depends on the rescue system version. Usually on this Pogo E02, you can use arcNumber 2097 and it will work for both rescue system and Debian/Arch kernel (iirc, 2.28+ or later). The LED can be manipulated somewhat to get it turn on Green, but other things might not work if it's not 3542. However, it is a good compromise so you can have rescue system running.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks - you'r a star. Got it running again.

I used arcNumber=3542 (the one which worked before I changed) and unset the machid (

setenv machid

). Now it is booting again.

Concerning netconsole: I did not get it to work with

nc -l -u -p 6666 &
nc -u 192.168.1.100 6666

but it worked how restamp suggested in this thread by using

nc -klu 6666

Additional piece of info: I am using a Mac, and I have to leave the "-p" out.

Thanks,

Rainer