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

Thanks, bodhi! I'll try it asap!

Update:
3G seems to work (can't test it more currently):

Jan  1 01:00:41 PogoplugV3 dhclient: isc-dhclient-4.2.2
Jan  1 01:00:42 PogoplugV3 dhclient: isc-dhclient-4.2.2
Jan  1 01:03:07 PogoplugV3 pppd[2253]: pppd 2.4.5 started by root, uid 0
Jan  1 01:03:07 PogoplugV3 pppd[2253]: Using interface ppp0
Jan  1 01:03:07 PogoplugV3 pppd[2253]: Connect: ppp0 <--> /dev/ttyUSB0
Jan  1 01:03:07 PogoplugV3 pppd[2253]: CHAP authentication succeeded
Jan  1 01:03:07 PogoplugV3 pppd[2253]: CHAP authentication succeeded
Jan  1 01:03:07 PogoplugV3 kernel: [  187.820413] PPP BSD Compression module registered
Jan  1 01:03:07 PogoplugV3 kernel: [  187.839649] PPP Deflate Compression module registered
Jan  1 01:03:09 PogoplugV3 pppd[2253]: Could not determine remote IP address: defaulting to 10.64.64.64
Jan  1 01:03:09 PogoplugV3 pppd[2253]: not replacing existing default route via 192.168.xx.1
Jan  1 01:03:09 PogoplugV3 pppd[2253]: local  IP address 10.xx.217.xx
Jan  1 01:03:09 PogoplugV3 pppd[2253]: remote IP address 10.xx.64.xx
Jan  1 01:03:09 PogoplugV3 pppd[2253]: primary   DNS address 10.xx.210.xx
Jan  1 01:03:09 PogoplugV3 pppd[2253]: secondary DNS address 10.xx.210.xx

But it seems after a bit more testing that wifi didn't work at all: I can't scan nearby wifi networks with the wifi adapter attached. (Its weird that I can ping the ip address of the wireless adapter from another machine of the network; maybe it is working or the wireless address gets tunneled through wired network somehow).

It seems the adapter doesnt even support scanning:

iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

Relevant dmesg:

[   17.231682] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 detected
[   17.354355] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[   17.380776] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   17.388523] usbcore: registered new interface driver rt2800usb
[   26.355729] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   26.377172] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
[   26.798812] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Also interesting:

 iwconfig
wlan0     no wireless extensions.

EDIT: NVM Wifi scanning works with

iw wlan0 scan

The issue must be somewhere else.

EDIT2: Connection attempt:

root@PogoplugV3:~# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf -d
wpa_supplicant v1.0
random: Trying to read entropy from /dev/random
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Priority group 0
   id=0 ssid='MAINTENANCE'
WEXT: cfg80211-based driver detected
wext: interface wlan0 phy: phy0
rfkill: Cannot open RFKILL control device
WEXT: RFKILL status not available
ioctl[SIOCSIWMODE]: Operation not supported
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Operation not supported
ioctl[SIOCGIWMODE]: Operation not supported
ioctl[SIOCSIWAP]: Operation not supported
WEXT: Failed to clear BSSID selection on disconnect
ioctl[SIOCSIWESSID]: Operation not supported
WEXT: Failed to clear SSID on disconnect
netlink: Operstate: linkmode=1, operstate=5
wlan0: Own MAC address: 00:1f:1f:68:f8:a5
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Operation not supported
Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE
ioctl[SIOCSIWENCODE]: Operation not supported
wpa_driver_wext_set_countermeasures
wlan0: RSN: flushing PMKID list in the driver
wlan0: Setting scan request: 0 sec 100000 usec
WPS: Set UUID for interface wlan0
WPS: UUID based on MAC address - hexdump(len=16): xxx
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
wlan0: Added interface wlan0
random: Got 11/20 bytes from /dev/random
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
wlan0: State: DISCONNECTED -> SCANNING
wlan0: Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Operation not supported
Scan requested (ret=-1) - scan timeout 10 seconds
wlan0: Failed to initiate AP scan
wlan0: State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wlan0: Setting scan request: 1 sec 0 usec
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
wlan0: State: DISCONNECTED -> SCANNING
wlan0: Starting AP scan for wildcard SSID
ioctl[SIOCSIWSCAN]: Operation not supported
Scan requested (ret=-1) - scan timeout 10 seconds
wlan0: Failed to initiate AP scan
wlan0: State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wlan0: Setting scan request: 1 sec 0 usec
^Cwlan0: CTRL-EVENT-TERMINATING - signal 2 received
wlan0: Removing interface wlan0
wlan0: No keys have been configured - skip key clearing
wlan0: State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
wlan0: No keys have been configured - skip key clearing
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout
ioctl[SIOCGIWMODE]: Operation not supported
ioctl[SIOCSIWAP]: Operation not supported
WEXT: Failed to clear BSSID selection on disconnect
ioctl[SIOCSIWESSID]: Operation not supported
WEXT: Failed to clear SSID on disconnect
netlink: Operstate: linkmode=0, operstate=6

EDIT3:
This problem seems to be related to wpa_supplicant. Connecting with

iw dev wlan0 connect

to a WEP wifi network is possible without any error.



Edited 8 time(s). Last edit at 09/01/2014 05:50PM by theliquid.

@ theliquid,

So are we good with the wireless and 3G config additions? is there anything unresolved?

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

As requested by a forum member, attached is the patch for kernel linux-oxnas-3.14-tld-5.

Note that it is almost the same as kref's patch in GitHub. The only change in this patch is the LED is set to green explicitly when the kernel has booted.

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

Dear Bodhi, first of all i would like to thank you for all your work. Your U-BOOT and your kernel gave a new life to my abandoned Pogoplug Pro. I even managed to get the my.pogoplug.com service working after updating to your latest 3.16.0 kernel!
I also tried to setup Pogoplug Pro as a surveillance system with a Logitech C310 webvcam attached along with mjpeg-streamer with no success though. The thing is that because the /media/video kernel modules aren't included with the kernel, the webcam isn't initiated and found under /dev/video0 as it should, but is rather seen only as a USB device (checked with lsusb). Referring to kernel 2.6, this guide http://armbedded.eu/node/415 points out the needed modules for the web cam to work. Could you please be kind enough to provide instructions how to compile kernel source along with our oxnas kernel patch in order to be able to compile the kernel modules?

@bodhi

Hi,

I see you did some awesome work for the pogoplug oxnas devices.

I'm running an "old" eTrayz nas (by xTreamer), which is an oxnas810 device. I have been looking into ways to upgrade the kernel as it runs an old 2.6.24.4 kernel but could not find the proper source tree containing the oxnas810 patches for building a 3.0 and up kernel version, as Oxford technology kept sources to themselves.

I'm now running debian squeeze on the device using a kernel v.2.6.24.4 I build from the original source tree, crosscompiled using emdebian toolchain and it is loaded from an usb stick not by booting because the old uboot on the device doesn't support usb, but by a kernel reload. It works!

Would it be possible to adapt the PogoV3 kernel 3.16.0 package in such a way that it would also support oxnas810 eTrayz devices or could you explain where to find a kernel v3.16.0 source tree containing support for oxnas810 (eTrayz) devices ?

I also tried to update uBoot to include usb support, but was not able to find sources for oxnas810 (eTrayz) either.

Your comments/ideas would be highly appreciated.

rgds.



Edited 2 time(s). Last edit at 09/24/2014 02:34PM by intrax.

The ox810 and plx oxnas 8720 are different enough that they are not compatible. You will need to make the necessary forward ports.

WarheadsSE Wrote:
-------------------------------------------------------
> The ox810 and plx oxnas 8720 are different enough
> that they are not compatible. You will need to
> make the necessary forward ports.

Forward ports ? Based on what... non existing sources or non-disclosed hw specs ?
Any other ideas ?

I think what WarheadsSE was trying to say is:
There ARE indeed kernel sources for OX810. They are quite old, but they exist. So your approach would be to take those sources and port them to newer kernel versions. Maybe 2.6.32 or something like that first and maybe later newer kernels.

The point is:
If there are no newer sources and nobody else is interested enough, you'll have to do the necessary work yourself.

As WarheadsSE said, you can't expect poeple who worked on OX820 sources, to automatically provide OX810 sources, too. It's not that easy.

If you absolutely cannot live with the older kernel(s), then maybe you should consider abandoning the OX810 platform. Sounds hard, but is just realistic.

And now maybe BTT?

Sorry for OT cont...
I know old oxnas810 kernel sources exist, I compiled my own kernel using them, if you read my post.
Not expecting anything but some help. There are many other devices using the oxnas810 soc and and a newer kernel from such a device maybe could be used hence my question here.

@denexo,

The patch is provided in the tarball. All you need to do is to download the 3.16 source from the kernel source tree, apply the patch and build. Or you could choose to clone kref's Git, and build.

EDIT: corrected info.

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



Edited 1 time(s). Last edit at 09/25/2014 01:56AM by bodhi.

intrax,

Among us, WarheadsSE is the expert for this SoC family.

You could save sometime by starting with my Git or kref's Git. And port the settings from the stock 2.6.24.4. The advantage is the drivers for USB and SATA might be OK unchanged. IMO, the most important thing to look at porting is the DTS. Chance is that if you can create a DTS for OX810 then you've completed a big portion of the porting effort. The kernel setup code is simpler because it can be based from the OX820 setup.

Also, ingmar has done a great job here with the Buffalo Linkstation (Kirkwood):
http://forum.doozan.com/read.php?2,15699

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

@bodhi,

thanks very much for the guidance! Will try and revert with results.

The OXNAS 8720 series uses the same SATA PHY block as the ox810 because they both use a separate piece of silicon on die, but that's about where it ends.

@bodhi,

i downloaded the 3.16 linux kernel, patched it with your patch, copied the Module.symver after installing the headers .deb, copied your config after renaming it to .config and run menuconfig. I enabled all the needed modules in Device Drivers and did a "make m=drivers/i2c" for starters. I try to insmod the module but i get the following error:

Error: could not insert module drivers/i2c/i2c-core.ko: Unknown symbol in module

When i check with dmesg i get the following info:

[83281.063731] i2c_core: Unknown symbol __i2c_board_list (err 0)
[83281.069565] i2c_core: Unknown symbol __i2c_first_dynamic_bus_num (err 0)
[83281.076367] i2c_core: Unknown symbol __i2c_board_lock (err 0)

It is important to load i2c-core.ko in order to meet the dependencies for the other needed modules. A bit of searching drove me to the openwrt forum where they state that someone has to recompile the whole kernel for i2c core to work, instead of just compiling the module after the kernel has been built. Any ideas?

@denexo,

Did you try to compile the whole thing like they did? if you'd like, post the diff of your .config and my .config and I can try compiling it.

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

bodhi, I have a similar question... I've got one of those generic C-Media USB DSPs that seem to be "all the rage" at the moment and I'm trying to get it to work with the Pogo Pro using your 3.16.0 kernel.. I've downloaded the mainline sources to 3.16, applied your patch, and did all the relevant including of sound support during "make menuconfig" but the kernel modules never seem to populate despite compiling through make/make modules/make modules_install

Is there something obvious I'm missing? I won't discount it as its been a good 15 years since I've complied a kernel and the alsa documentation for 3.x kernels seems to be painfully nonexistent.

All PFM to me..

Thanks.

bodhi Wrote:
-------------------------------------------------------
> Vince,
>
>

Quote

Newbie question: I want to use a sound
> card, but does not support, what do I do? Thank
> you!

>
> Please be a litle more detailed in your question!
> which system, kernel version, sound card model,…
> things like that. May be someone already done it.

@zer0 and others,

Would be better if you recompile the whole kernel from scratch after

make distclean

This kernel config is no where near what we have in the kirkwood kernel. I've started with kref's config so it only contains a limited set of supported devices. It does need more work to add what we already have in that kirkwood config.

I could try building the next version with all the necessary configs for devices that you guys need, in general (e.g. sound, i2c, wireless, 3G,…). But if you can post info for the devices and if you know the config names or module names then it's even better. It is difficult to troubleshoot or guess the problem with kernel compilation without trying the same thing.

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

Regarding the wifi problems: wext drivers are not enabled in this kernel. tools like iwconfig don't work. Perhaps also not old wpa_supplicant versions without nl80211 support.

I compiled my own kernel for this, which was very straightforward, before that I also flashed the new u-boot. Then I cross-compiled 3.16, for this I used https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.16.3.tar.gz with the patch and .config from here, I added some modules in menuconfig e.g. legacy wireless to make wext work, alsa drivers, and other stuff I personally need.
Then I rsynced the new modules folder to /lib (I didn't have to overwrite the old folder, cause this is 3.16.3 whereas the old one was 3.16.0.), I backed up the old kernel and copied over the new one. reboot without any problems, even u-boot's netconsole worked straight away in case something would have gone wrong...
Then all that was left was upgrading to wheezy with apt-get dist-upgrade. After this all wpa_supplicant worked with 3 different wifi sticks I tested. In the end I didn't test wpa_supplicant with wext though, I only used nl80211 which worked stable enough.

Thanks a lot for this very accessible and up-to-date patch!

Hey bodhi- tried that with the same result - nothing sound realted gets generated installed under /lib/modules/3.16.0-oxnas-tld-1/kernel - in comparison my sun4i (cubie) board has a /lib/modules/3.16.0-oxnas-tld-1/kernel/sound with the alsa modules (and I'm pretty sure raspbian has the same as c-media devices are supported in their installation).

The USB DSP de jour seems to be this guy:

http://www.amazon.com/HDE-Channel-External-Sound-Adapter/dp/B0027EMHM6/ref=sr_1_7?ie=UTF8&qid=1411826920&sr=8-7&keywords=usb+audio

...which shows up as:

Bus 001 Device 003: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter

...and is based off the CM106 chipset - there are literally hundreds of variants and clones of this device so it is pretty widely used.

Not sure what alsa module that ends up using, as alsa's documentation makes me want to kick a puppy.

Thanks!


bodhi Wrote:
-------------------------------------------------------
> @zer0 and others,
>
> Would be better if you recompile the whole kernel
> from scratch after
>

> make distclean
>

>
> This kernel config is no where near what we have
> in the
> kirk
> wood kernel. I've started with kref's config
> so it only contains a limited set of supported
> devices. It does need more work to add what we
> already have in that kirkwood config.
>
> I could try building the next version with all the
> necessary configs for devices that you guys need,
> in general (e.g. sound, i2c, wireless, 3G,…).
> But if you can post info for the devices and if
> you know the config names or module names then
> it's even better. It is difficult to troubleshoot
> or guess the problem with kernel compilation
> without trying the same thing.

@zer0 & denexo,

I'll give it a shot! will rebuild it to see if it helps.

@ nixOS,

It would be helpful if you can post the diff between my .config and your final one. It'll be easier for others who are looking for the same thing, if it is incorporated to the released kernel.

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

As requested by a forum member, attached is the patch for kernel linux-oxnas-3.12.13-tld-5.

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

Here's my config I used with 3.16.3 and the diff from bodhi's version.

I have a NON-PCI version, so I disabled PCI in here.

--Nixos

*fixed



Edited 3 time(s). Last edit at 09/28/2014 08:43AM by h1ro.

@Nixos,

Thanks. BTW, you did not have to disable PCI. Using the Pogo Classic DTB would be enough to run the box correctly.

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

@bodhi

Awesome, many thanks!

@bodhi,

I would like to thank you once again for all your efforts! I will try today to create a .diff file from your config and mine.

Stay tuned, I've rebuilt and veriffied the modules, but has not got time to upload. Will do that tonight!

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

@zer0 & denexo,


Here is kernel linux-3.16.0-oxnas-tld-3. Please test and let me know if it works for you!

Dowload at Dropbox
linux-3.16.0-oxnas-tld-3-bodhi.tar.bz2
md5:
0f3ca0717b2438676c7a7eec8f264963

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

@bodhi,

thank you very much! I am trying right now and will get back with results!

EDIT: vpn to home doesn't work at the moment.



Edited 1 time(s). Last edit at 09/30/2014 02:10AM by denexo.

@bodhi,

i still didn't manage to load the needed modules for the camera. Though i managed to surpass the error regarding the i2c. I attach the diff file from your 3.16.0-3 config and mine, after making all the configurations needed for uvc to work.
In order to make the camera work ones has to load the following modules with the exact order as written: v4l2-core/videodev.ko , v4l2-core/v4l2-common.ko, v4l2-core/videobuf2-core.ko , usb/uvc/uvcvideo.ko . First two modules are loaded ok, but as soon as i try to insmod the videobuf2-core.ko i get the following error

Error: could not insert module drivers/media/v4l2-core/videobuf2-core.ko: Unknown symbol in module

and this is what dmesg shows

[ 5032.813504] videobuf2_core: Unknown symbol dma_buf_get (err 0)
[ 5032.819333] videobuf2_core: Unknown symbol dma_buf_put (err 0)
[ 5032.825200] videobuf2_core: Unknown symbol dma_buf_fd (err 0)

During the build of the v4l modules, i also got the following warnings which are related to the above error message

WARNING: "dma_buf_vmap" [drivers/media/v4l2-core/videobuf2-vmalloc.ko] undefined!
WARNING: "dma_buf_vunmap" [drivers/media/v4l2-core/videobuf2-vmalloc.ko] undefined!
WARNING: "dma_buf_fd" [drivers/media/v4l2-core/videobuf2-core.ko] undefined!
WARNING: "dma_buf_get" [drivers/media/v4l2-core/videobuf2-core.ko] undefined!
WARNING: "dma_buf_put" [drivers/media/v4l2-core/videobuf2-core.ko] undefined!

I am out of ideas. I don't know if the change at CONFIG_DMA_SHARED_BUFFER from unset to y (automatically changed from menuconfg) cause the errors.