[SOLVED] Pogoplug v2 not reachable after kernel upgrade

[pm4888]

I do have the latest uboot but unable to reach ssh port of v2 after kernel upgrade from kirkwood 3.10.7 to 3.10.9.
ALARM is installed on a single usb ext hdd.

Is there any troubleshooting guide? What is my option next?

$this->bbcode_second_pass_quote('', '[')root@pogoplug ~]# pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (6): gnupg-2.0.21-1 libwbclient-4.0.9-1 linux-headers-kirkwood-3.10.9-1 linux-kirkwood-3.10.9-1 samba-4.0.9-1
smbclient-4.0.9-1

Total Download Size: 31.66 MiB
Total Installed Size: 109.02 MiB
Net Upgrade Size: 0.05 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages ...
gnupg-2.0.21-1-arm 1356.7 KiB 743K/s 00:02 [#############################################] 100%
linux-headers-kirkwood-3.10.9-1-arm 5.9 MiB 1469K/s 00:04 [#############################################] 100%
linux-kirkwood-3.10.9-1-arm 16.3 MiB 1968K/s 00:08 [#############################################] 100%
libwbclient-4.0.9-1-arm 25.2 KiB 138K/s 00:00 [#############################################] 100%
smbclient-4.0.9-1-arm 4.2 MiB 1995K/s 00:02 [#############################################] 100%
samba-4.0.9-1-arm 3.9 MiB 1970K/s 00:02 [#############################################] 100%
(6/6) checking keys in keyring [#############################################] 100%
(6/6) checking package integrity [#############################################] 100%
(6/6) loading package files [#############################################] 100%
(6/6) checking for file conflicts [#############################################] 100%
(6/6) checking available disk space [#############################################] 100%
(1/6) upgrading gnupg [#############################################] 100%
(2/6) upgrading libwbclient [#############################################] 100%
(3/6) upgrading linux-headers-kirkwood [#############################################] 100%
(4/6) upgrading linux-kirkwood [#############################################] 100%
>>> Updating module dependencies. Please wait ...
**********************************************************************
WARNING! This kernel requires a newer U-Boot than many devices such as
the Dockstar and Pogoplug v2 originally came with. If you do
not have an updated version, your system WILL NOT BOOT.
**********************************************************************
(5/6) upgrading smbclient [#############################################] 100%
(6/6) upgrading samba [#############################################] 100%
[root@pogoplug ~]# uname -a
Linux pogoplug 3.10.7-1-ARCH #1 PREEMPT Fri Aug 16 18:05:39 CDT 2013 armv5tel GNU/Linux
[root@pogoplug ~]# reboot

[moonman]

There was a bug in BFQ scheduler revealed in >3.10.8. It is fixed already.

You will need to create another bootable stick, and use pacman --root to downgrade the kernel from pacman cache (/var/cache/pacman/pkg)

Then when it boots update again.

[grayman4hire]

$this->bbcode_second_pass_quote('moonman', 'T')here was a bug in BFQ scheduler revealed in >3.10.8. It is fixed already.

[moonman]

3.10.9-2 which is in the repo now does not have this problems and boots fine. Another way to fix is to add/change elevator=cfq in uboot environment temporarely. That's for those who know what they are doing.

[grayman4hire]

Thanks moonman for the clarification.

Sounds like this is (or was) causing lots of issues for new users/installation.

I recall a recent post where the user mentioned skipping the kernel upgrade because it was causing him issues.

[moonman]

Bfq? This is the first time afaik

$this->bbcode_second_pass_quote('', 'T')here was a bug in BFQ scheduler revealed in >3.10.8. It is fixed already.

You will need to create another bootable stick, and use pacman --root to downgrade the kernel from pacman cache (/var/cache/pacman/pkg)

Then when it boots update again.

[moonman]

Create another bootable stick (new installation). Use the link in my signature for reinstalling from scratch and use ext3 for filesystem.
Boot from that stick.
Insert the the one that doesn't boot.
Mount it on, say, /mnt
$this->bbcode_second_pass_code('', 'wget http://us.mirror.archlinuxarm.org/arm/core/linux-kirkwood-3.10.9-2-arm.pkg.tar.xz')
Then run
$this->bbcode_second_pass_code('', 'pacman --root /mnt/ -U linux-kirkwood-3.10.9-2-arm.pkg.tar.xz')

or if you have archlinux on one of your PCs you can run
$this->bbcode_second_pass_code('', 'pacman --root /mnt/ --arch arm -U linux-kirkwood-3.10.9-2-arm.pkg.tar.xz')


You can also try to extract uImage from the http://us.mirror.archlinuxarm.org/arm/c ... pkg.tar.xz and put it in /boot on the stick replacing the old one (Use ubuntu or whatever you like on your pc). Then when it boots just run pacman -Suy to get everything updated. I would try this method first actually.

[pm4888]

That's a good idea. Painlessly fixed the boot issue.

Appreciate your help.

[cownamedpuppy]

I think I just got hit by this too (but in a worse way).

I updated the kernel and my Pogov2 wouldn't boot anymore.
Worse, the front LED doesn't even come on even if I remove the USB drive containing alarm.

The other thing I was trying to do before the reboot was to update the arch and machid using these commands.
fw_setenv arcNumber 3542
fw_setenv machid dd6

I saw some CRC errors but I just reinstalled uboot-env and they went away.

So it is either the kernel update or my uBoot is really messed up.
Unfortunately, I don't have netboot installed either.

What could I do to bring my pogov2 back to life?