Linux Mainline

[maal]

Ayufan's Ethernet patch has been commited to the mainline kernel:

https://git.kernel.org/pub/scm/linux/ker...0dc12d36e7

[decontainerized]

USB3 seems to be broken in ARM Arch Linux using 4.17.2.

[beakfire]

USB3 seems to be broken in ARM Arch Linux using 4.17.2.

There's a couple of threads on this on the forum and a fix for it over on the Arch Linux ARM forums here:

https://archlinuxarm.org/forum/viewtopic...67&t=12826

[suberimakuri]

I notice in ayufan's pre-releases (mainline kernel) there are a lot less network related modules included compared to the 4.4 releases, eg: `CONFIG_NETFILTER_XT_SET=m` is missing.
I wonder what the selection criteria or upstream source is? Is it from vanilla kernel sources plus anything specific to Rock64?

On my amd64 18.04.1 LTS laptop for example:
```
$ find /lib/modules/$(uname -r) -type f -name '*.ko' | grep xt_set
/lib/modules/4.15.0-34-generic/kernel/net/netfilter/xt_set.ko
```

UPDATE:
On the flip side, with Arch following [this guide](https://archlinuxarm.org/platforms/armv8...hip/rock64) I have 4.18.4 with above module (search for '*.ko.gz' as they are gzip'd).
Feel like I should just stick with Arch for this and update my Ansible playbooks appropriately. Or run Ubuntu cosmic minimal with 4.18 kernel as well (should have modules).
Great work finding fixes and getting them upstream Ayufan.

[belfastraven]

Aftert running successfully with the 4.19 kernel (Ayufan's) , SPI booting with  a USB3 ssd,  I found that after installing 4.20 I could no longer boot from the USB drive.  Booting from SD worked,  but none of my drives, a Samsung T1,  a sandisk Extreme stick,  or  WD passport would even be powered/recognized from any of the USB ports .  If I boot with the 4.19 dtb on the 4.20 kernel, eveything boots/is recognized again.  If I change the following lines in the rk3328-rock64.dts (from 4.20) to their 4.19 values and recompile ,  disk recognition/booting works again.


vcc_host1_5v: vcc_otg_5v: vcc-host1-5v-regulator {#############################  from 4.20,  changed A2 back to D3  to make things work
compatible = "regulator-fixed";
enable-active-high;
gpio = <&gpio0 RK_PA2 GPIO_ACTIVE_HIGH>;




usb2 {
usb20_host_drv: usb20-host-drv {
rockchip,pins = <0 RK_PA2 RK_FUNC_GPIO &pcfg_pull_none>;#################  from 4.20,  changed A2 back to D3  to make things work

My board is version 2.0

This problem did not affect other usb devices, btw,  just storage...  I tried to check the specs but didn't see find anything for vcc_host1_5v ,  vcc_otg_5v or usb20_host_drv.

I did find usb_otg_drv at A2.....

Could anyone clarify what is going on?  I'm pretty clueless about hardware.'

I did see a complaint about this on the Arch forums,  but none of the armbian people seemed to have run into it.  
'
Thanks.

[Voyt]

Aftert running successfully with the 4.19 kernel (Ayufan's) , SPI booting with  a USB3 ssd,  I found that after installing 4.20 I could no longer boot from the USB drive. ...

Hi belfastraven,

Could you please check the following:
1) Revert the Kernel sources v4.20 to the original state
2) Add this line

Code:

regulator-boot-on;

in sections vcc_host_5v: vcc-host-5v-regulator and vcc_host1_5v: vcc_otg_5v: vcc-host1-5v-regulator so both sections should look like this:

Code:

    vcc_host_5v: vcc-host-5v-regulator {
        compatible = "regulator-fixed";
        enable-active-high;
        gpio = <&gpio0 RK_PA0 GPIO_ACTIVE_HIGH>;
        pinctrl-names = "default";
        pinctrl-0 = <&usb30_host_drv>;
        regulator-name = "vcc_host_5v";
        regulator-always-on;
        regulator-boot-on;
        vin-supply = <&vcc_sys>;
    };

    vcc_host1_5v: vcc_otg_5v: vcc-host1-5v-regulator {
        compatible = "regulator-fixed";
        enable-active-high;
        gpio = <&gpio0 RK_PA2 GPIO_ACTIVE_HIGH>;
        pinctrl-names = "default";
        pinctrl-0 = <&usb20_host_drv>;
        regulator-name = "vcc_host1_5v";
        regulator-always-on;
        regulator-boot-on;
        vin-supply = <&vcc_sys>;
    };

Or just copy & paste the whole file from here: https://pastebin.com/ubwPv9TY
Please let me know if it works for you (I'd appreciate if you drop me an e-mail: voytikd [at] gmail [dot] com).

[Mentaluproar]

Why is there a performance between mainline and 4.4 patched kernels?

[kanelxake]

Aftert running successfully with the 4.19 kernel (Ayufan's) , SPI booting with  a USB3 ssd,  I found that after installing 4.20 I could no longer boot from the USB drive. ...

Hi belfastraven,

Could you please check the following:
1) Revert the Kernel sources v4.20 to the original state
2) Add this line

Code:

regulator-boot-on;

in sections vcc_host_5v: vcc-host-5v-regulator and vcc_host1_5v: vcc_otg_5v: vcc-host1-5v-regulator so both sections should look like this:

Code:

    vcc_host_5v: vcc-host-5v-regulator {
        compatible = "regulator-fixed";
        enable-active-high;
        gpio = <&gpio0 RK_PA0 GPIO_ACTIVE_HIGH>;
        pinctrl-names = "default";
        pinctrl-0 = <&usb30_host_drv>;
        regulator-name = "vcc_host_5v";
        regulator-always-on;
        regulator-boot-on;
        vin-supply = <&vcc_sys>;
    };

    vcc_host1_5v: vcc_otg_5v: vcc-host1-5v-regulator {
        compatible = "regulator-fixed";
        enable-active-high;
        gpio = <&gpio0 RK_PA2 GPIO_ACTIVE_HIGH>;
        pinctrl-names = "default";
        pinctrl-0 = <&usb20_host_drv>;
        regulator-name = "vcc_host1_5v";
        regulator-always-on;
        regulator-boot-on;
        vin-supply = <&vcc_sys>;
    };

Or just copy & paste the whole file from here: https://pastebin.com/ubwPv9TY
Please let me know if it works for you (I'd appreciate if you drop me an e-mail: voytikd [at] gmail [dot] com).

Hi,

Sorry to say, it did not help here. Reverting ef05bcb60c1a8841e38c91923ba998181117a87c works, but adding that line instead of reverting does not.

[thewonderer]

Didn't want to start a new thread, but curious what is happening with new linux and kernel builds? I'm really grateful for all the work that Ayafun has done to get the rock64 where it is, but I'm still encountering crashes with the latest builds whether stable or pre-release. Only 0.56 is stable for me.... I can see he's busy working on gitlab due to the number of commits on github, but hoping he doesn't give up making the rock64 more stable and perform a bit better.

[ElektromAn]

From my popcornhour transformer
a rock64 clone with room for a hdd drive

 

Code:

               _     __   _  _          
 _ __ ___   ___| | __/ /_ | || |
| '__/ _ \ / __| |/ / '_ \| || |_
| | | (_) | (__|   <| (_) |__   _|
|_|  \___/ \___|_|\_\\___/   |_|  
                                          
Linux rock64 4.19.0-1073-ayufan-ga6e013135a6e #1 SMP PREEMPT Tue Oct 23 09:19:54 UTC 2018 aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Jan 30 18:27:33 2019 from xxx.xxx.xxx.xxx

With v4.20 there is an USB 3.0 power issue
Also the audio (headphone) is missing

Currently I have no time to tst my changes.
Will do this next week (hopefully)