Pink Pogo (v2) E02 - What arcNumber?

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Pink Pogo (v2) E02 - What arcNumber?

Postby LavaChild » Wed Apr 11, 2012 2:36 pm

Just followed the PogoPlug v2 instructions and changed UBoot. The script output:

Setting arcNumber to 2097 (SheevaPlug)
Note: if you have a kernel that supports your platform, you should use the proper arcNumber.
You can set the correct arcNumber by running the following command:
/usr/sbin/fw_setenv arcNumber 2998


However, I read the following thread on this forum: viewtopic.php?f=18&t=2101

This suggests 3542. So, do I go with 2097, 2998 or 3542? Obviously there has to be Kernel support... Is there Kernel support for all of these arcNumbers, such that if I were to reboot without the USB ALARM drive the Pogo OS would boot fine?

Thanks!
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby kmihelich » Wed Apr 11, 2012 3:25 pm

There is kernel support for all of them in our latest kernels. The only difference you will see is NAND partitioning (which will be a problem if you're using that for anything) and whether or not LEDs work or are addressed properly.

2097 = Sheeva, 2998 = Dockstar, 3542 = Pogo v2.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby moonman » Wed Apr 11, 2012 3:25 pm

3542 is the one you need. The only difference is that LED will be proper color now.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3367
Joined: Sat Jan 15, 2011 3:36 am

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby LavaChild » Wed Apr 11, 2012 3:38 pm

Thank you for your prompt replies! :)
LavaChild
 
Posts: 46
Joined: Wed Mar 21, 2012 12:39 pm

Re: Pink Pogo (v2) E02 - What arcNumber and which colors?

Postby PogoDancer » Sun Dec 16, 2012 6:08 pm

moonman wrote:3542 is the one you need. The only difference is that LED will be proper color now.
Could you define "proper", i.e. which color it ought to show in which state?
While the original POGO-E02 firmware is using a green LED (on black "pinkpogos" sold off mislabelled as P24s lately), following
Code: Select all
/usr/sbin/fw_setenv arcNumber 3542
as per this thread (on Linux alarm 3.1.10-13-ARCH these days) rather than
install_uboot_mtd0.sh wrote:set the correct arcNumber by running the following command:
/usr/sbin/fw_setenv arcNumber 2998
the LED now blinks amber during boot, then stays lit this way, even after "shutdown -h now" which this Pogoplug never seems to complete.
PogoDancer
 
Posts: 14
Joined: Sun Dec 16, 2012 2:00 pm

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby agillis » Tue Dec 18, 2012 5:55 am

If you add this to /etc/rc.local the LED should turn green after boot.

Code: Select all
echo none > /sys/class/leds/status\:blue\:health/trigger
echo default-on > /sys/class/leds/status\:green\:health/trigger


If your really clever you could add some if condition to this script to make sure the system is really working before you turn the LED green.
agillis
 
Posts: 3
Joined: Fri Dec 14, 2012 8:02 pm

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby moonman » Tue Dec 18, 2012 8:05 am

Good find, although rc.local won't work with systemd.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3367
Joined: Sat Jan 15, 2011 3:36 am

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby WarheadsSE » Tue Dec 18, 2012 2:34 pm

Not without adding the needed bits, but it can be done.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pink Pogo (v2) E02 - What arcNumber?

Postby byteme » Sat Feb 23, 2013 3:49 pm

agillis wrote:If you add this to /etc/rc.local the LED should turn green after boot.

Code: Select all
#!/bin/sh
echo none > /sys/class/leds/status\:blue\:health/trigger
echo default-on > /sys/class/leds/status\:green\:health/trigger


If your really clever you could add some if condition to this script to make sure the system is really working before you turn the LED green.


Put that in a script (I used /usr/local/bin/ledboot.sh) and make a service file for systemd

Code: Select all
nano /usr/lib/systemd/system/ledboot.service


PASTE THIS:
Code: Select all
[Unit]
Description=LED Turn Off
After=syslog.target

[Service]
Type=oneshot
ExecStart=/usr/local/bin/ledboot.sh &

[Install]
WantedBy=multi-user.target

then:
Code: Select all
systemctl enable ledboot

reboot and enjoy :P

As a side note, I like my lights off.
Code: Select all
#!/bin/sh
echo "none" > /sys/class/leds/status\:blue\:health/trigger
echo "none" > /sys/class/leds/status\:green\:health/trigger


And this will make the LED blink on hard drive access. iostat will accept specific partitions. check the man page. You can use vnstat and do the same for network (use a little math to set a threshold), blink on web server access, etc. You can use each led for a different function.
Code: Select all
echo "timer" > /sys/class/leds/status\:blue\:health/trigger
iostat -z -d 1 | sed -u -e '1d' -e 's/Device.*/0/' -e 's/sd.*/100/' -e '/^$/d' > /sys/class/leds/status\:blue\:health/delay_on &
byteme
 
Posts: 3
Joined: Fri Feb 15, 2013 9:34 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 2 guests