new kernel killing NIC on PogoPlug Pink

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

new kernel killing NIC on PogoPlug Pink

Postby kurter » Tue Apr 21, 2015 3:02 pm

Everyone....I found a good solution until they can sort out the issues with the 4.0 kernel.

This assumes that you haven't already upgraded and lost your remote SSH access (I have serial console access and could tell right away what was happening). I ultimately had to eject my USB stick I boot from on that plug and reload Kirkwood Linux on another machine by formatting, downloading and expanding the tarball.... but this will prevent this from happing on my secondary and tertiary servers I use for development and production. (and will fix my rebuilt server too from breaking)

change your /etc/pacman.conf file to add this line
nano /etc/pacman.conf
IgnorePkg = linux-kirkwood linux-api-headers libsystemd systemd systemd-sysvcompat

then you can issue "pacman -Syu" and you will not get the kernel updates... 8-)

generates
:: Starting full system upgrade...
warning: libsystemd: ignoring package upgrade (218-2 => 219-5)
warning: linux-kirkwood: ignoring package upgrade (3.19.3-1 => 4.0-1)
warning: systemd: ignoring package upgrade (218-2 => 219-5)
warning: systemd-sysvcompat: ignoring package upgrade (218-2 => 219-5)

This will at least leave you with a functioning system.

Enjoy
kurter
 
Posts: 11
Joined: Wed Mar 09, 2011 8:57 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby jacgl » Tue Apr 21, 2015 6:33 pm

Hi, the same happened to my Pogo v4. No connectivity on ethernet, no ssh.
Unfortunately, no tarball as well :oops:
Not good time for testing anything.... Firstly -no USB3 after update to 4.0, and now no connection at all.
So, start from the scratch once again.....
I am considering if anyone tests what is in repository???
jacgl
 
Posts: 4
Joined: Fri Apr 17, 2015 10:45 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby kurter » Tue Apr 21, 2015 8:35 pm

FYI.

Just starting from scratch and issuing a "pacman -Syu" will break it - again... even clean... ouch.

You must make the exclusions..
To get this documented, I had to wipe and reinstall about 4 times today.
kurter
 
Posts: 11
Joined: Wed Mar 09, 2011 8:57 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby moonman » Wed Apr 22, 2015 4:50 am

Are you sure it was the kernel? My devices work fine. The problem is with pcie (and by extension anything connected to it, be it usb3 controller or a second NIC), nothong else.
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: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: new kernel killing NIC on PogoPlug Pink

Postby WarheadsSE » Wed Apr 22, 2015 2:28 pm

We have identified a commit in systemd that seems to cause unexpected behavior on Kirkwoods with linux-* 4.0, and work on a resolution.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby kurter » Mon Apr 27, 2015 11:47 am

First,
Yes, the on board NIC is an issue with Systemd not the newer kernel.

Second,
In order for me to get a 2nd network port operational I had to stay on the 3.x kernel.

So,
To resolve BOTH of my issues, this is what I had to do. :)
kurter
 
Posts: 11
Joined: Wed Mar 09, 2011 8:57 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby Holzhaus » Mon Apr 27, 2015 3:05 pm

$this->bbcode_second_pass_quote('kurter', 'T')o get this documented, I had to wipe and reinstall about 4 times today.


Just in case that happens again and you have another computer running ArchLinux, you could also try using this script: https://gist.github.com/Holzhaus/94d3a4c73892e67f3ff0

Plug the USB stick into your computer, edit the MOUNTED_ROOT variable and supply the -U argument to downgrade the kernel from your desktop PC.

Packages for downgrading are available in your /var/cache/pacman/pkg folder or at http://rollback.archlinuxarm.org/.
Holzhaus
 
Posts: 62
Joined: Wed Jan 21, 2015 12:40 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby nathanh » Mon Apr 27, 2015 9:28 pm

Without using the script solution, you can just as easily: a) power down your device, b) remove the usb with Arch arm on it, and c) plug it into another computer running Arch arm and then following the steps detailed well here (https://wiki.archlinux.org/index.php/Change_root) to mount and chroot into your system. Those steps are (where /dev/sdx1 is your usb device detected):
$this->bbcode_second_pass_code('', '# mount /dev/sdx1 mnt/YOUR_MOUNT_DIR
# arch-chroot /mnt/YOUR_MOUNT_DIR')
After you have successfully chrooted into your USB drive alarm system, you can then just do the downgrade for packages systemd and/or the kernel as necessary. In my case, on a PogoPlug v4 I needed to downgrade the kernel as well back to 3.19 as the 4.0 kernel is noted as introducing a regression that affects USB 3.0 (which pogoplug v4 has)--and which messed up access to mounted drives. So in my case I ran these commands:
$this->bbcode_second_pass_code('', '# cd /var/cache/pacman/pkg/
# pacman -U linux-kirkwood-3.19.3-1-arm.pkg.tar.xz linux-kirkwood-headers-3.19.3-1-arm.pkg.tar.xz systemd-218-2-arm.pkg.tar.xz systemd-sysvcompat-218-2-arm.pkg.tar.xz')
In the case where older versions of systemd systemd-sysvcompat don't exist you can grab them from these URLs (and then try pacman -U .... to downgrade again):
$this->bbcode_second_pass_code('', 'wget http://rollback.archlinuxarm.org/packages/s/systemd-sysvcompat/systemd-sysvcompat-218-2-arm.pkg.tar.xz
wget http://rollback.archlinuxarm.org/packages/s/systemd/systemd-218-2-arm.pkg.tar.xz
')

Finally, you can make the change that @kurter noted:
$this->bbcode_second_pass_quote('', 'c')hange your /etc/pacman.conf file to add this line
nano /etc/pacman.conf
IgnorePkg = linux-kirkwood linux-api-headers libsystemd systemd systemd-sysvcompat

Note* (I believe there is one typo in @kurter's original post.... the second ignored package should be linux-kirkwood-headers not linux-api-headers). Like so:
$this->bbcode_second_pass_code('', ' IgnorePkg = linux-kirkwood linux-kirkwood-headers libsystemd systemd systemd-sysvcompat ')

You should then be able to umount the usb drive and exit the chroot, plug the usb drive back into your original device, and then boot back up. Basically, there is no reason to have to do a full re-install from scratch and lose all your settings or files incase your backup methods are not very adequate. If you have a latest backup image you just want to easily restore instead...great. If not, doing this fix should take 15 minutes or less and get you back up and running as you were before the updates that ruined your day :D .

Hope it helps someone who upgraded and inadvertently lost network ability and also usb 3.0 proper usage!
nathanh
 
Posts: 5
Joined: Mon Apr 27, 2015 8:51 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby Holzhaus » Tue Apr 28, 2015 2:00 pm

The script solution is for cases when you don't have another ArchLinuxARM device. It also works with the x86/x86_64 ArchLinux installation on your Desktop computer.
Holzhaus
 
Posts: 62
Joined: Wed Jan 21, 2015 12:40 pm

Re: new kernel killing NIC on PogoPlug Pink

Postby WarheadsSE » Tue Apr 28, 2015 2:23 pm

Just to re-iterate AGAIN:
It is not the KERNEL that is "killing" the NIC, it is an issue within systemd-219, for which we've applied a patch in attempt to resolve.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 37 guests

cron