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

Please see this post:
http://forum.doozan.com/read.php?2,12096,21196#msg-21196

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

Kernel linux-4.0.0-oxnas-tld-1 package was uploaded. Please see 1st post for download link.

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

@bodhi,

You are da man! I will never stop thanking you for all your efforts! Your are a brilliant example of community giver.

denexo,

You're welcome! please post if bluetooth working/not-working in the new kernel, especially if you're using 4.0 mode.

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

schnee Wrote:
-------------------------------------------------------
> denexo Wrote:
> --------------------------------------------------
> -----
> > @bodhi,
> >
> > thanks once again for your effort!
> > I installed patched kernel but i get same
> > result...i get no image on mjpg_streamer when
> > using the input_uvcvideo.so . I really hope i
> am
> > not doing something wrong. Could someone else
> > please check also?
>
>
> mjpg-streamer from repo does not work on 3.18 -
> service running, but no video output. Fixed
> version of mjp-streamer can be found here:
> https
> ://github.com/oliv3r/mjpg-streamer
>
> After compilation it works fine. I tested with
> running 3 cameras parallel and it worked like
> charm

@schnee,

i verify that with the provided git, mjpg-streamer works fine! I wish i had more than one camera to test it. Thanks very much for the info!

bodhi Wrote:
-------------------------------------------------------
> Kernel linux-4.0.0-oxnas-tld-1 package was
> uploaded. Please see 1st post for download link.

Is this normal?

root@debian:/boot# dpkg -i linux-image-4*
Selecting previously unselected package linux-image-4.0.0-oxnas-tld-1.
(Reading database ... 50501 files and directories currently installed.)
Unpacking linux-image-4.0.0-oxnas-tld-1 (from linux-image-4.0.0-oxnas-tld-1_1.0_armel.deb) ...
Examining /etc/kernel/preinst.d/
Done.
Setting up linux-image-4.0.0-oxnas-tld-1 (1.0) ...

 Hmm. There is a symbolic link /lib/modules/4.0.0-oxnas-tld-1/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/4.0.0-oxnas-tld-1/build


 Hmm. The package shipped with a symbolic link /lib/modules/4.0.0-oxnas-tld-1/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/4.0.0-oxnas-tld-1/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 4.0.0-oxnas-tld-1 /boot/vmlinuz-4.0.0-oxnas-tld-1
Error! Could not locate dkms.conf file.
File:  does not exist.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.0.0-oxnas-tld-1 /boot/vmlinuz-4.0.0-oxnas-tld-1
update-initramfs: Generating /boot/initrd.img-4.0.0-oxnas-tld-1
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 4.0.0-oxnas-tld-1 /boot/vmlinuz-4.0.0-oxnas-tld-1

Regarding bluetooth, I was able to get a USB BT adapter working but unfortunately the bluetooth module on my Atheros model AR5B225 combo wifi / bluetooth card is not enabling. The modules load - Ath3k, btusb, etc but when I do a hcitool dev it does not indicate a device. I also tried an Intel Centrino 300M Wireless-N 2230 combo wifi/bt card and had the same result. From research, these types of cards require some special blacklisting and other firmware tweaks to initialize the BT side and those are beyond my skillset so what I am saying is that it may work but I haven't figured out how yet. Thankful though that you were able to get conventional bluetooth adapters to work wth Oxnas now :)



Edited 3 time(s). Last edit at 04/17/2015 03:49PM by LeggoMyEggo.

LeggoMyEggo,

> Hmm. There is a symbolic link
> /lib/modules/4.0.0-oxnas-tld-1/build
> However, I can not read it: No such file or
> directory
> Therefore, I am deleting
> /lib/modules/4.0.0-oxnas-tld-1/build
>
>
> Hmm. The package shipped with a symbolic link
> /lib/modules/4.0.0-oxnas-tld-1/source
> However, I can not read the target: No such file
> or directory
> Therefore, I am deleting
> /lib/modules/4.0.0-oxnas-tld-1/source
>

Yes, it is normal. I've switched back to building kernel with Debian make-kpkg. This is just a warning about it can't find the some symbolic link to build directories, which does not apply when we install kernel.

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



Edited 1 time(s). Last edit at 04/18/2015 02:06AM by bodhi.

LeggoMyEggo,

> Regarding bluetooth, I was able to get a USB BT
> adapter working but unfortunately the bluetooth
> module on my Atheros model AR5B225 combo wifi /
> bluetooth card is not enabling. The modules load
> - Ath3k, btusb, etc but when I do a hcitool dev it
> does not indicate a device. I also tried an Intel
> Centrino 300M Wireless-N 2230 combo wifi/bt card
> and had the same result.

Thanks for reporting your finding! Since I am at building the Pogo V3 kernel to include pNFS, I've found some other kernel configs that we are lacking comparing to the Kirkwood kernel. I will update it and release a 4.0.0-tld-2 version :) so if you can find out if the PCIe card BT issue needs kernel config tweak, please let me know.

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

bodhi Wrote:
-------------------------------------------------------
> I will update it and release a 4.0.0-tld-2 version :) so
> if you can find out if the PCIe card BT issue
> needs kernel config tweak, please let me know.

I'll see what I can find out. I'm not too bummed because from my reading I know people have issues with these cards on mainline distributions on Intel platforms and if that is the case then supporting on something that is a sideline to the mainline is bound to be more problematic. Like tearing down a wall, it's sometimes one brick at a time.

LeggoMyEggo Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > I will update it and release a 4.0.0-tld-2
> version :) so
> > if you can find out if the PCIe card BT issue
> > needs kernel config tweak, please let me know.
>
> I'll see what I can find out. I'm not too bummed
> because from my reading I know people have issues
> with these cards on mainline distributions on
> Intel platforms and if that is the case then
> supporting on something that is a sideline to the
> mainline is bound to be more problematic. Like
> tearing down a wall, it's sometimes one brick at a
> time.

Looks like there are changes in many RT devices drivers in this kernel, too! affected: Kirkwood iConnect wifi (rt2x00). So I would not be surprised to find Atheros to have new regression either.

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

@all
My bluetooth - cheapo noname brand works ok.

Q. did keyboard support get added to this version?

Gravelrash Wrote:
-------------------------------------------------------
> @all
> My bluetooth - cheapo noname brand works ok.
>
> Q. did keyboard support get added to this version?

Yes, it was added.

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

@LeggoMyEggo,


Could you post the dmesg part where your PCIe card got initialized? Looks like the Pogo V3 is immuned to the bug, since we are using the OXNAS patch, which is different from mainline :)

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

bodhi Wrote:
-------------------------------------------------------
> @LeggoMyEggo,
>
>
> Could you post the dmesg part where your PCIe card
> got initialized? Looks like the Pogo V3 is immuned
> to the bug, since we are using the OXNAS patch,
> which is different from mainline :)

Here it is: http://pastebin.com/AHxpwVmU

LeggoMyEggo,

Thanks. Indeed, the device was detected and eeprom was read OK. So you BT problem is not related.

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

@bodhi,

i didn't have much time to test the bluetooth much during the weekend. I am using a USB Beewi Bluetooth adapter. The device seems to get initialized (since the led indicator blinks) and the

hciconfig -a

command produces the following output

hci0:   Type: BR/EDR  Bus: USB
        BD Address: xx:xx:xx:xx:xx:xx  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:1401 acl:0 sco:0 events:65 errors:0
        TX bytes:1494 acl:0 sco:0 commands:64 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'pogoplug-0'
        Class: 0x4e0100
        Service Classes: Networking, Rendering, Capturing, Telephony
        Device Class: Computer, Uncategorized
        HCI Version: 2.1 (0x4)  Revision: 0x149c
        LMP Version: 2.1 (0x4)  Subversion: 0x149c
        Manufacturer: Cambridge Silicon Radio (10)

which seems promising. I will try to follow this guide here https://www.raspberrypi.org/forums/viewtopic.php?t=68779 and see how it goes! Will keep you posted.

denexo,

Excellent! Looks like we'all got the USB Bluetooth working. My Iogear BT dongle is also working fine..

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

Hi, Bodhi - Thanks so much for your work on Pogoplugs! I got a BIZ02 from Adorama about a week ago and it turned out to be what I think is a P01. It's definitely a V3 Oxnas with WiFi. I upgraded the U-Boot and installed 4.0 kernel per your instructions. I think I somewhat honked up the original firmware (had to direct connect SATA drive to get it sorted) - maybe I'll look into that more later. The Pogoplug works great, including the WiFi!

My main question is re: Codepage 437. I have an older MyBook that has a VFAT partition. It mounts fine on my other Debian boxes, but I can't get it to mount on the Pogoplug. Do I need to recompile the kernel, or can I just add a module? I understand that I should use the "config" file in your tarball, but I need to download the kernel sources directly - is that correct?

Best regards!
Gregg G.

gregg_a_g,

> The Pogoplug works great,
> including the WiFi!

Glad to hear this! If you could, please post your wifi setup. i..e. content of /etc/network/interfaces, or anything that you did to use the stock wifi card on this box here. It would help others to clarify whether stock wifi is working on this rootfs, and see how it can be done.

> My main question is re: Codepage 437. I have
> an older MyBook that has a VFAT partition. It
> mounts fine on my other Debian boxes, but I can't
> get it to mount on the Pogoplug. Do I need to
> recompile the kernel, or can I just add a module?
> I understand that I should use the "config" file
> in your tarball, but I need to download the kernel
> sources directly - is that correct?

You don't need to compile. I'll will include it all the code pages in the next release, but in the mean time I will post this module so you can try.

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

Thanks, Bodhi!

Perhaps I was fortunate, but the wifi was no trouble with a "fresh install" per your Page 1 directions.

Here is my /etc/network/interfaces:

******************************************

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
#
auto wlan0
iface wlan0 inet dhcp
wpa-ssid "mywifi"
wpa-psk "mywifipassword" (don't worry, not my real password!)

**********************************************

The WiFi module is the AzureWave with RT3090 chip ( I had to look when I opened the box to SATA boot).
I'm attaching output from "dmesg" in case it's useful for someone else to look at for troubleshooting.

I'll look forward to seeing the nls module when you have time to post it!

Best regards,
Gregg G.

@Gregg G.,

Thanks! great to see that was that easy.

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

@Gregg G,

Here is the nls_cp437 code page module. It should be extracted and placed in this directory (if nls does not exist, create it as root user):

/lib/modules/4.0.0-oxnas-tld-1/kernel/fs/nls/

You can try it out first by modprobe it at command line.

Once it is verified to work, and you should add the module to the list of extra load action. This might not be needed but won't hurt.

/etc/initramfs-tools/modules

And regenerate initrd image and uInitrd

cd /boot
cp -a uInitrd uInitrd.bak
cp -a initrd.img-4.0.0-oxnas-tld-1 initrd.img-4.0.0-oxnas-tld-1.bak
update-initramfs -u
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-4.0.0-oxnas-tld-1  -d initrd.img-4.0.0-oxnas-tld-1 uInitrd

And reboot. See how it goes!

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

Hi, Bodhi -

As "root" I made the directory /lib/modules/4.0.0-oxnas-tld-1/kernel/fs/nls, copied the tar file and extracted nls_cp437.ko to the directory. Then I did:

modprobe -v ./nls_cp437.ko

output was: builtin ./nls_cp437.ko (as if the module was builtin to the kernel)!

lsmod output is:

Module Size Used by
uas 11930 0

I plugged in the MyBook USB drive, and I still got the following:

[ 1985.120913] usb 1-1.3: new high-speed USB device number 5 using oxnas-ehci
[ 1985.232153] usb 1-1.3: New USB device found, idVendor=1058, idProduct=1100
[ 1985.239006] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1985.246353] usb 1-1.3: Product: My Book
[ 1985.250982] usb 1-1.3: Manufacturer: Western Digital
[ 1985.256012] usb 1-1.3: SerialNumber: 57442D574D41535530313333323333
[ 1985.266170] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 1985.272957] scsi host3: usb-storage 1-1.3:1.0
[ 1986.271513] scsi 3:0:0:0: Direct-Access WD 3200AAC External 1.65 PQ: 0 ANSI: 0
[ 1986.283532] sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 1986.294456] sd 3:0:0:0: [sdb] Write Protect is off
[ 1986.299261] sd 3:0:0:0: [sdb] Mode Sense: 00 00 00 00
[ 1986.306127] sd 3:0:0:0: [sdb] Asking for cache data failed
[ 1986.311808] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 1986.325754] sdb: sdb1 sdb2
[ 1986.335191] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 1987.200908] EXT4-fs (sdb2): recovery complete
[ 1987.205306] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
[ 1992.212459] FAT-fs (sdb1): codepage cp437 not found

I have 2 partitions on the drive, the first is the VFAT partition, and the second is an EXT-4 partition.

As before, mount /dev/sdb1 /media/storage/gdisk-3 returns:

mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Also, I tried:
modprobe -v ./nls_cp437.ko --first-time (which returned)

modprobe: FATAL: Module ./nls_cp437.ko already in kernel (builtin).


Perhaps there is a companion module that needs to be loaded as well?

Kind regards,
Gregg G.

Hi Gregg,

I don't think it needs anything else, VFAT was compiled into the kernel.

This indicated that the load was not successful:

lsmod output is: 

Module Size Used by 
uas 11930 0

Have you tried this to make sure the path is correct?

cd /
modprobe -v nls_cp437

If it still doesnot work. Try putting the module name in

echo nls_cp437 >> /etc/initramfs-tools/modules

And then regenerate initrd image and uInitrd as I mentioned above and reboot. Make sure you backup these 2 files first (If it does not work you can restore them back).

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



Edited 2 time(s). Last edit at 05/05/2015 07:49PM by bodhi.

Ah, it just occured to me that I need to:

depmod -a (no?)

Now I do the following:

cd /
modprobe -v nls_cp437
insmod /lib/modules/4.0.0-oxnas-tld-1/kernel/fs/nls/nls_cp437.ko
modprobe: ERROR: could not insert 'nls_cp437': Exec format error

So I think I'm getting a little farther!

I also tried --force (evidently to skip module version and magic number checking) and still got the same error.

I'll try the last step you suggested if you think it's safe:

echo nls_cp437 >> /etc/initramfs-tools/modules


And then regenerate initrd image and uInitrd as I mentioned above and reboot. Make sure you backup these 2 files first (If it does not work you can restore them back).

Thanks again,
Gregg G.

Ah! I see. That error is usally a mismatched kernel. So it migh not work any way in initramfs. No need to try.

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

Perhaps it's best that you wait a few days. I will release another kernel vesion for Oxnas.

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

Cool, Bodhi - I have plenty to keep me busy! I ordered parts for the serial cable connection on e-Bay...

Kind regards,
Gregg G.

Kernel linux-4.0.0-oxnas-tld-2 package was uploaded. Please see 1st post for download link.

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

Hi, Bodhi -

Thanks very much for creating a new 4.0 kernel with cp437. It works like a champ and my VFAT partition mounted at boot!

Kind regards,
Gregg G.