PINE64

Did anyone tried usbip? Not sure if it needs extra modules for that. I'm gonna test it later tonight.

(02-14-2016, 03:00 AM)longsleep Wrote: [ -> ]**3.10.101-1-pine64-longsleep-41 (20160516)**
- Tagged as 3.10.101-1-pine64
- Enable XFS, FS2FS and HFS+ as module
- Fix sunxi-ss ahash registration and disable SHA-224
- Enable BLK_DEV_BSG for better udev compatibility

**3.10.101-2-pine64-longsleep-48 (20160521)**
- Tagged as 3.10.101-2-pine64
- Enable various netfilter and namespace features to make LXD happy
- Disable XFS module (not compatible with user namespaces in Kernel 3.10)
- Backported apparmor3
- Enable/changed various additional features to for complete secure container support

First of all, big THANKS! for all your work on this. And now to my question -- is there a chance to get the XFS module back? Maybe if I disable user namespaces? Not sure where user namespaces are used, but if it's only containers stuff, I'd gladly sacrifice it for XFS support.

Yes just rebuild with xfs if you do not need secure containers.

I just pushed a new awesome Kernel release. It brings a security fix, ip multicast support and A64 camera driver changes. For details, see the first post of this thread.

Get 3.10.104-1-pine64-longsleep-103 from https://www.stdin.xyz/downloads/people/l...ges/linux/

Thanks Simon, you rock !

(10-12-2016, 10:01 AM)longsleep Wrote: [ -> ]Yes just rebuild with xfs if you do not need secure containers.

Just for the record and for people with similar use case: I built the kernel with the XFS module and no namespaces and everything works great. Except for new(ish) XFS file system created which cause crash in the XFS module when being mounted. Older XFS file systems work just fine.

I just released a new Kernel build line "pine64gmac" which has a possible fix for the Ethernet Gigabit issue which happens on some boards. The fix is based on a patch provided by tllim (thanks!).

For now consider this a test release and you can switch to the pine64gmac Kernel line easily with


You can switch back to the normal Kernel line with
(assume the Network still works with the gmac Kernel ).

To see what changed:
https://github.com/longsleep/linux-pine6...gmactxonly


If feedback is good, this fix will go into the default Kernel. So let me know how it goes.

To check if the fix is applied on boot:

(10-29-2016, 07:09 AM)longsleep Wrote: [ -> ]I just released a new Kernel build line "pine64gmac" which has a possible fix for the Ethernet Gigabit issue which happens on some boards. The fix is based on a patch provided by tllim (thanks!).

This is super cool! Thanks!

(10-29-2016, 07:09 AM)longsleep Wrote: [ -> ]I just released a new Kernel build line "pine64gmac" which has a possible fix for the Ethernet Gigabit issue which happens on some boards. The fix is based on a patch provided by tllim (thanks!).

For now consider this a test release and you can switch to the pine64gmac Kernel line easily with

Code:

bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh) latest gmac

You can switch back to the normal Kernel line with

Code:

bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh) latest default

(assume the Network still works with the gmac Kernel ).

To see what changed:
https://github.com/longsleep/linux-pine6...gmactxonly


If feedback is good, this fix will go into the default Kernel. So let me know how it goes.

To check if the fix is applied on boot:

Code:

root@pine64:~# dmesg|grep 'init ephy'
[   16.070919] init ephy for pine64

Thanks.