All PLX based chips - Important Upgrade Note [updated]

This forum is for all other ARMv5 devices

Re: All PLX based chips - Important Upgrade Note [updated]

Postby greenfly » Wed Oct 10, 2012 7:41 pm

just a quick update:
I had success by following the reinstall howto. Now everything is back to normal :)
greenfly
 
Posts: 14
Joined: Thu Dec 01, 2011 7:26 pm

Re: All PLX based chips - Important Upgrade Note [updated]

Postby shv » Tue Dec 25, 2012 7:20 pm

Can you please be so kind and provide me the kernel configuration file you have used to build the kernel? What compiler options (CFLAGS) must be set to build the kernel? I want to compile the kernel and the wifi driver.
Debian @ Pogoplug Pro (actively used)
Debian @ Pogoplug E02
shv
 
Posts: 38
Joined: Fri Dec 21, 2012 6:35 am

Re: All PLX based chips - Important Upgrade Note [updated]

Postby WarheadsSE » Wed Dec 26, 2012 12:18 am

My configuration matches that which I have on github. Other than that, it also matches the configuration in makepkg.conf. See the PKGBUILD for core/linux-ox820.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6730
Joined: Mon Oct 18, 2010 2:12 pm

Re: All PLX based chips - Important Upgrade Note [updated]

Postby shv » Wed Dec 26, 2012 9:59 am

I had no success with PKGBUILD from git:

Code: Select all
makepkg --asroot --skipinteg
==> Making package: linux-ox820 2.6.31-0 (Wed Dec 26 03:53:40 CST 2012)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
  -> Downloading linux.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   175  100   175    0     0    193      0 --:--:-- --:--:-- --:--:--   249
100 76.2M  100 76.2M    0     0   475k      0  0:02:44  0:02:44 --:--:--  610k
==> ERROR: Failure while downloading linux.tar.gz
    Aborting...
Debian @ Pogoplug Pro (actively used)
Debian @ Pogoplug E02
shv
 
Posts: 38
Joined: Fri Dec 21, 2012 6:35 am

Re: All PLX based chips - Important Upgrade Note [updated]

Postby shv » Wed Dec 26, 2012 4:05 pm

I got the kernel source code directly from git. Afterwards I rolled back to the commit of August. So I got access to the .config.old configuration file form the 14th of June. It contains already a PCI configuration. I comipled everything under Debian on the PogoplugPro. At the end I comipled the wireless driver and it works. It fits to the kernel which is provided in this thread.
Debian @ Pogoplug Pro (actively used)
Debian @ Pogoplug E02
shv
 
Posts: 38
Joined: Fri Dec 21, 2012 6:35 am

Re: All PLX based chips - Important Upgrade Note [updated]

Postby croldham » Mon Jan 28, 2013 4:08 am

I have a working oxnas-based PogoPlug but would like to switch to systemd. I didn't understand until recently that it would need a different kernel--though I successfully installed systemd via pacman, attempting to execute it generates

Trying to run as user instance, but the system has not been booted with systemd.

Is there an existing kernel that I can use? Where can I find it?
croldham
 
Posts: 1
Joined: Mon Jan 28, 2013 4:04 am

Re: All PLX based chips - Important Upgrade Note [updated]

Postby WarheadsSE » Mon Jan 28, 2013 4:21 am

There isn't a currently known to me, stable kernel with all the needs of systemd
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6730
Joined: Mon Oct 18, 2010 2:12 pm

Re: All PLX based chips - Important Upgrade Note [updated]

Postby darkside401 » Sat Feb 02, 2013 5:27 pm

Could it be that from more and more packages the old init scripts get removed?
Not only from the Samba package but also for instance from the Sabnzbd package.

Is there anyway to stop that? Because when you do a pacman -Syu on a Oxnas device nowaday you likely get left behind with a not properly working system?

Wasn't there an attempt to port a newer 3-Series Kernel to that Oxnas devices, which could lead us to using Systemd instest of SysVinit?
darkside401
 
Posts: 14
Joined: Fri Jan 11, 2013 10:18 am

PCI vs. NoPCI - Pogo Bricked?

Postby alfred1 » Sun Feb 17, 2013 12:36 am

Hi,

i ran the update from the second post on my black Pogoplug Pro.
But i did'nt read exactly and so i patched the NO-PCI-Script on my PCI-Pogoplug.
Before i did a partially system update with "pacman -Syu", but i had some trouble with some
packages, but i think that should not block the upgrade, because reboots after updating
the packages worked without problems.

Update log from SSH:
Code: Select all
# Oxnas kernel update, WarheadsSE 06/05/12
# Adds devtmpfs to kernel, and many modules
# NOTE: I DO NOT HAVE THE DEVICES TO TEST
# THEM ALL. Sorry.

This will flash non-PCI kernel only
Pacman'ing needs: mtd-utils & libaccept4
:: Synchronizing package databases...
 core is up to date                    0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 extra is up to date                   0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 community is up to date               0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 aur is up to date                     0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 archlinuxfr is up to date
 alarm is up to date                   0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 alarm is up to date                   0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 alarm is up to date                   0.0   B  0.00B/s 00:00 [---------------------------------]   0%
 alarm is up to date                   0.0   B  0.00B/s 00:00 [---------------------------------]   0%
warning: mtd-utils-1.5.0-1 is up to date -- reinstalling
warning: libaccept4-0.1.0-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (2): libaccept4-0.1.0-2  mtd-utils-1.5.0-1

Total Installed Size:   0.77 MiB
Net Upgrade Size:       0.00 MiB

Proceed with installation? [Y/n] Y
(2/2) checking package integrity                              [#################################] 100%
(2/2) loading package files                                   [#################################] 100%
(2/2) checking for file conflicts                             [#################################] 100%
(1/2) upgrading mtd-utils                                     [#################################] 100%
(2/2) upgrading libaccept4                                    [#################################] 100%
Copying if necessary...
mv: cannot move ‘/lib/modules/2.6.31.6_SMP_820’ to ‘/lib/modules/oxnas-save/2.6.31.6_SMP_820’: Directory not empty
Placing updates...
Depmod...
WARNING: could not open /usr/lib/modules/2.6.31.6_SMP_820/modules.builtin: No such file or directory
Flashing Kernel to slot A...
Erasing 128 Kibyte @ 760000 -- 100 % complete
Writing data to block 40 at offset 0x500000
Writing data to block 41 at offset 0x520000
Writing data to block 42 at offset 0x540000
Writing data to block 43 at offset 0x560000
Writing data to block 44 at offset 0x580000
Writing data to block 45 at offset 0x5a0000
Writing data to block 46 at offset 0x5c0000
Writing data to block 47 at offset 0x5e0000
Writing data to block 48 at offset 0x600000
Writing data to block 49 at offset 0x620000
Writing data to block 50 at offset 0x640000
Writing data to block 51 at offset 0x660000
Writing data to block 52 at offset 0x680000
Writing data to block 53 at offset 0x6a0000
Writing data to block 54 at offset 0x6c0000
Writing data to block 55 at offset 0x6e0000
Writing data to block 56 at offset 0x700000
Writing data to block 57 at offset 0x720000

After successful upgrade i rebooted.
The device is starting up correctly, but i cannot access it via ethernet nor via wifi. (eth0 is static ip defined in rc.conf)
The LED is not blinking after full boot and the color is green - all looks normally.

Could it be, that the upgrade blocks the ethernet controller?
How can i flash the correct kernel?

I've done a full backup with "dd" of my USB device before i applied these updates,
so i could switch back if there is no other way.

Ok, one thing i found out:
in /boot/ is a file uImage (2.7MB), uImage.nopci (2.3MB), uImage.nopci.org (2.3MB), uImage.pci (2.3MB),
uImage.pci.org (2.3MB).
Could it be, that there the image "uImage" is getting loaded?
The last modication of this file was on 25. Sep 2011.

I also tried to move all files from /lib/modules/* to /usr/lib/modules/.

When i rename the file /var/local/mac_addr to "mac_addr_org" the Pogoplug boots up and halts with an orange LED (not blinking).


Do you have some ideas to finish the update successfully?
I love my Pogoplug, it runs Python, Perl, Lighttpd with PHP, sqlite, samba, dhcp, ddclient, pyload, owncloud and some other services without any greater problems for more than 2 years under archlinux.
It would be great to get it running again for 2 more years :-)

Also i am interested how to get the serial cable connected - is there a tutorial or anything like that?
I have no idea where to connect a serial cable, there are only ethernet, usb and power connectors on the black box.
Or do i have to open it?

Thank u in advance and have a nice weekend!

alfred.
alfred1
 
Posts: 10
Joined: Sat Jul 21, 2012 1:20 pm

Re: All PLX based chips - Important Upgrade Note [updated]

Postby alfred1 » Sun Feb 17, 2013 3:29 pm

Ok. I think i found out something:
I moved all files from /var/log to /var/log/old_logs and attached the usb stick again on the pogo to find out,
which logs getting created on boot.
The only logfile that is created is dmesg.log and that contains only binary bullshit, nothing human readble.
So i think there is something crashed...do you have some ideas?

Should i go back to my backup or do you have any ideas?
alfred1
 
Posts: 10
Joined: Sat Jul 21, 2012 1:20 pm

PreviousNext

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 2 guests