Linux Kernel 5.4.268 Oxnas (OX820) Pogo V3 package and Debian rootfs

Can I upgrade the system to Debian Jessie just by editing sources.list or would that create problems?

nibre Wrote:
-------------------------------------------------------
> Can I upgrade the system to Debian Jessie just by
> editing sources.list or would that create
> problems?

You could. Update source list and then apt-get update, apt-get upgrade.

But usually securiy updates are lagging in Testing, comparing to Stable, so that should be considered. And please remember backup your rootfs before upgrading (it will be massive :-).

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

I just upgraded to this kernel and rootfs with the help from bodhi! Everything looks good except one thing:

oxnas:~# mount -t iso9660 -o ro,loop keiso.iso /mnt/temp
mount: Could not find any loop device. Maybe this kernel does not know
       about the loop device? (If so, recompile or `modprobe loop'.)

Here is the output from modprobe:

oxnas:~# modprobe loop
FATAL: Module loop not found.

I tried to search around but couldn't find anything. Is it a known issue?

purespin Wrote:
-------------------------------------------------------
> I just upgraded to this kernel and rootfs with the
> help from bodhi! Everything looks good except one
> thing:
>
>

> oxnas:~# mount -t iso9660 -o ro,loop keiso.iso
> /mnt/temp
> mount: Could not find any loop device. Maybe this
> kernel does not know
>        about the loop device? (If so, recompile or
> `modprobe loop'.)
>

>
> Here is the output from modprobe:
>

> oxnas:~# modprobe loop
> FATAL: Module loop not found.
>

>
> I tried to search around but couldn't find
> anything. Is it a known issue?

Unfortunately loop is not configured in this kernel. It is not completed as the Kirkwood 3.17 kernel configuration, but I don't have time to build a new kernel yet :)

# CONFIG_BLK_DEV_LOOP is not set

Next release...

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

bodhi Wrote:
-------------------------------------------------------
> Unfortunately loop is not configured in this
> kernel. It is not completed as the Kirkwood 3.17
> kernel configuration, but I don't have time to
> build a new kernel yet :)
>
>

> # CONFIG_BLK_DEV_LOOP is not set
>

>
> Next release...

Got it! Thank you for the clarification!

@Bohdi

Enabling the following in the next kernel compile should fix the issues with wireless:

Old
# CONFIG_CFG80211_WEXT is not set

New
CONFIG_CFG80211_WEXT=y


See https://github.com/raspberrypi/linux/issues/171

@nohud,

> Enabling the following in the next kernel compile
> should fix the issues with wireless:
>
> Old
> # CONFIG_CFG80211_WEXT is not set
>
> New
> CONFIG_CFG80211_WEXT=y
>
>
> See
> https://github.com/raspberrypi/linux/issues/171

Which wireless issue? with the stock wifi ?

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

Yes, this should add the support needed to the kernel so the stock wifi will work with wpa_supplicant and other wireless utilities.

CONFIG_CFG80211_WEXT=y

nohud Wrote:
-------------------------------------------------------
> Yes, this should add the support needed to the
> kernel so the stock wifi will work with
> wpa_supplicant and other wireless utilities.
>
> CONFIG_CFG80211_WEXT=y

Thanks nohud. I've missed this from the Kirkwood kernel. I will add it to the next OXNAS release.

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

can you post a picture of the wifi board?

Hello,

I own a pogoplug classic. I succesfully flashed u-boot and installed the newest rootfs.

Encrypt a directory with encryptfs-utils doesn't work. The module isn't loaded neither is it in
/lib/modules/$(uname -r)/kernel/fs.

And lsmod says there is only one module loaded (uas). Could it be enabled?

With my GoFlexNet it works perfect.

Has the pogoplug no arcNumber env-variable?

-automatux

automatux,

Do you know the modules names?

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

bodhi,

the module needed for ecryption with ecryptfs-utils is called ecryptfs.

On pogoplug-classic lsmod shows:
Module Size Used by
uas 15442 0

On Goflex:
Module Size Used by
ecb 1711 1
ipv6 300163 28
ecryptfs 67780 0
orion_wdt 3834 0
hmac 2441 0
sha1_generic 1712 0
sha1_arm 3330 0
mv_cesa 10637 0
ext4 449247 1
jbd2 85140 1 ext4
mbcache 8316 1 ext4
sg 20651 0
sd_mod 35160 2
sr_mod 13883 0
cdrom 32818 1 sr_mod
crc_t10dif 1032 1 sd_mod
crct10dif_common 1126 1 crc_t10dif
uas 15570 0
usb_storage 37762 2 uas
sata_mv 24761 0
libata 146773 1 sata_mv
scsi_mod 160362 6 sg,uas,usb_storage,libata,sd_mod,sr_mod

Thanks bodhi, I appreciate your help

automatux,

I'll build the next version and include it.

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

bodhi,

Thanks, I am looking forward.

It seems the PLX 7820 700MHz has hardware encryption. It could help if you include also the mv_cesa module. And maybe also the ext4, ecb, sha1_*.

mv_cesa is kirkwood. This is Oxnas! So no hardware encryption as far as I know.

A websearch for PLX 7820/1 shows hardware encryption support. But, yeah, probably the pogoplug hasn't hardware encryption.

I think perhaps it's time to do a serious merge from Kirkwood config to OXNAS config. Ingmar has not said so yet again, but I can read mind :))

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

Hehe. :-D
Actually, I am so busy at work right now that I would not have thought of that.

BUT, it's still a good idea. The debian default kirkwood config was always a quite good start point.

I have come back to Pogoplug Pro hacking from a long time away.

I have a previously hacked Pogoplug Pro (Oxnas CPU, internal SATA port and internal Wifi) and working access to the internal serial port. It boots correctly to a system that I can SSH into with the correct, carefully crafted USB memory stick attached. It hangs and does nothing useful with no or a random USB memory stick attached. I would like to get the system back into use doing something useful, but I can't remember what I did! I'm pretty sure the internal NAND flash memory has been changed at some point.

From the serial terminal I get the following pertinent information (heavily edited!) -
Stage-1 Bootloader XCE_STAGE1: 1.1: Tue Feb 8 01:40:26 PST 2011
.......
U-Boot 1.1.2 (Jul 29 2010 - 19:36:07)
.......
Loading from device 0: 128MiB 3,3V 8-bit (offset 0x500000)
-- Using 1bit ECC style encoding
Image Name: Linux-2.6.31.6_SMP_820
Image Type: ARM Linux Kernel Image (uncompressed)
..........
[ 0.000000] Linux version 2.6.31.6_SMP_820 (root@hunchback) (gcc version 4.7.0 20120505 (prerelease) (GCC) ) #7 SMP Thu Jun 14 20:31:06 CDT 2012
...........
[ 6.500000] hub 1-1:1.0: USB hub found
[ 6.510000] hub 1-1:1.0: 4 ports detected
At this point the Pogoplug hangs if there is no USB memory stick connected. If a carefully crafted USB memory stick is installed, then the Pogoplug gets to a useful login via ssh after about a minute or so.

If it is going to be worth the effort, I would like to update this Pogoplug Pro to a currently stable operating system, but I appreciate that it will not be simple because of the apparently altered internal NAND flash memory. I intend to use the system as a simple filestore/NAS. In the future I would like to use the internal SATA port, however I appreciate that this will will not be trivial and I would be better making it work correctly with USB attached filesystems in the first instance. Can a helpful person point me in the direction of appropriate advice/instructions/tutorial.

Thank you

Peter

Peter,

It's quite easy. Because what you've installed was Arch kernel in NAND. And you can leave that untouched if you install new u-boot and kernel and boot with USB or SATA.

u-boot:
http://forum.doozan.com/read.php?3,16017

debian kernel & rootfs (this thread):
http://forum.doozan.com/read.php?2,16044

Note: if you want to run Arch then you need to compile the kernel. Debian kernel and rootfs were already done in the above thread.

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



Edited 1 time(s). Last edit at 12/29/2014 12:40PM by bodhi.

Thank you for your helpful reply. I'll stick with debian because I'm more familiar with it. I'll go away and play...

Thanks

Peter

First of, THANK YOU Bodhi.... thanks to all your valuable information here in the forums, I have successfully managed to install Wheezy on my Pogo Pro.... running the new uboot....

That being said, I'm running into a problem, which honestly, I'm not sure if its a hardware issue, or just something not enabled in the kernel.... and not sure if I'm entirely comfortable compiling a new kernel for anything but x86 hardware...

Here's my problem.... Since this device has a SATA interface, I'm trying to connect a eSATA hard drive... I've got everything connected up properly, but no love... dmesg is indicating the following relative to the SATA interface...

[ 1.529482] ata1: SATA max UDMA/133 irq 50
[ 1.915778] ata1: SATA link down (SStatus 0 SControl 300)
[ 41.177789] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen
[ 41.185000] ata1: SError: { PHYInt }
[ 41.188579] ata1: hard resetting link
[ 41.981985] ata1: SATA link down (SStatus 0 SControl 300)
[ 41.987389] ata1: EH complete

Any suggestions?

John Tetreault,

Not all eSata enclosures are supported by the kernel. If you have the right cable, like this one, you could try to plug the HDD in directly using SATA cable, and get power from USB to see if it was the enclosure problem.

Which enclosure are you using?

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



Edited 1 time(s). Last edit at 01/17/2015 06:31AM by bodhi.

Posting this here so that others may benefit from my frustration (and avoid said frustration)... It starts out explaining what I did, what my problem was, and how I found my solution.

Hello, I recently installed the 2013.10 uboot and your 3.17 wheezy fs on my Pogoplug Pro, and it was booting perfectly... Of course, not being one to leave well enough alone, and a firm subscriber to the "if it ain't broke, fix it until it is" school of thought, I had to tinker....

. I am booting off of a USB flash drive, and also using an eSATA drive on the device, so I made some changes to uboot to find the rootfs by the drive label.... and that's where my troubles started.

I've got nc running, so here's what happens when I boot now.

U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1
Storage Device(s) found
4102704 bytes read in 495 ms (7.9 MiB/s)
1953812 bytes read in 326 ms (5.7 MiB/s)
7029 bytes read in 227 ms (29.3 KiB/s)
## Booting kernel from Legacy Image at 60500000...
Image Name: Linux-3.17.0-oxnas-tld-1
Image Type: ARM Linux Kernel Image
(uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000


Starting kernel ...

And that's where the boot would hang... nothing. Now, my rootfs is ext4, and is specified as such in /etc/fstab... so here are what my uboot env variables are.

autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext4load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext4load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext4load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:25:31:01:05:52
if_netconsole=ping $serverip
ipaddr=10.0.0.3
led_error=orange blinking
led_exit=green on
led_init=green blinking
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
ncip=10.0.0.6
preboot=run preboot_nc
preboot_nc=run if_netconsole start_netconsole
serverip=10.0.0.6
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=nc
stdin=nc
stdout=nc
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_root=LABEL=rootfs
usb_root_label=rootfs
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=$usb_root_label rootdelay=10

So everything SEEMS like this should work... why isn't it.... So a search through the forums seems to lead me to a hang at "Starting kernel..." is likely caused by a problem in the bootargs

Well just smack me upside the head.... forgot to specify rootfstype

changed usb_set_bootargs to this

usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=$usb_root_label rootfstype=ext4 rootdelay=10

Yup... that did the trick.... booting again.....

One thing you might not have known is that when monitoring with nc, the last thing you will ever see is:

Starting kernel ...

even during a normal bootup with everything working.

Yes, I did note that... problem was after the Starting kernel.... the system became, and remained unpingable... do definitely the kernel was crashing at that point.

Thanks to Jeff's 3.17 kernel I've now got two PP Biz's (apparently the bastard step child of Pogoplug'dem) up and running. They are working great. Had some issues with both getting my setenv's correct but finally got them straightened away. One plug is running Squeezelite using a cheapo CM108 usb adapter for sound and booting off an old 2.5" IDE drive in a usb enclosure strapped to the side. The other plug is booting off of a 2.5" sata drive and is running Squeezebox Media Server. Combo works great and either one can be built for less than $25. The only thing that would get me to Nirvana is to figure out how to get the stock on board wifi working but after several hours of pulling out my hair, I think I am going to throw in the towel and order some Atheros 300N mpci-e adapters for less than $5 each.

Thanks again for you work bodhi and to the others that have also contributed to the effort.

A small correction: kernel 3.17 for Oxnas was not come from Jeff. It's my kernel build which is a derivative of kref's kernel build!

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

bodhi Wrote:
-------------------------------------------------------
> A small correction: kernel 3.17 for Oxnas was not
> come from Jeff. It's my kernel build which is a
> derivative of kref's kernel build!


Hehe I thought your name was Jeff. Sorry :(