Trying to get mainline kernel working on N1

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 09, 2019 5:14 pm

I'm planning to use my N1 as a nas, replacing my XU4, and since I'm using XFS as a filesystem, I'd like to use the newest available kernel on it (there can be problems if you mount a XFS system with an older kernel).
So, this is what I tried so far (inspired from http://opensource.rock-chips.com/wiki_Upstream_Kernel) - currently kernel 5.0.0 rc1:

Code: Select all

git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
cd linux-rockchip/
make rockchip_linux_defconfig
scripts/kconfig/merge_config.sh .config config-4.4.114
make menuconfig
#added the odroid lirc blaster driver from xu4 branch because I'll need it
#copied over the extra edid from the old 4.4.114 kernel
cp -ar ../../linux/firmware/edid/*.bin firmware/edid/
make -j 6 Image dtbs modules
sudo cp arch/arm64/boot/Image /media/boot/Image.mainline
#there was no dtb for N1, so I didn't copy any to /media/boot
sudo make modules_install
sudo make firmware_install
kver=`make kernelrelease`
sudo cp .config /boot/config-${kver}
cd /boot
sudo update-initramfs -c -k ${kver}
sudo mkimage -A arm64 -O linux -T ramdisk -a 0x0 -e 0x0 -n initrd.img-${kver} -d initrd.img-${kver} uInitrd-${kver}
sudo cp uInitrd-${kver} /media/boot/uInitrd.mainline
I'm using this kernel config: http://paste.ubuntu.com/p/SNwqGmPjnb/

I'm using this boot.ini:

Code: Select all

ODROIDN1-UBOOT-CONFIG

# U-Boot configuration
setenv kernel_addr "0x02000000"
setenv fdt_addr "0x01f00000"
setenv initrd_addr "0x04000000"

# Enable/Disable ODROID-VU7 Touchsreen
setenv disable_vu7 "false" # false

# Kernel cmdline rootfs and misc
setenv bootrootfs "swiotlb=1 console=ttyFIQ0,115200n8 root=UUID=a130ca78-0841-400a-8823-06a304a00850 rootwait rw"

# Load kernel, uInitrd and dtb
load mmc ${bootdev} ${kernel_addr} Image.mainline
load mmc ${bootdev} ${initrd_addr} uInitrd.mainline
load mmc ${bootdev} ${fdt_addr} rk3399-odroidn1-linux.dtb

# Set the kernel bootargs
setenv bootargs "${bootrootfs} disable_vu7=${disable_vu7}"

# Boot the board
booti ${kernel_addr} ${initrd_addr} ${fdt_addr}

When I try to boot the kernel it remains at:

Code: Select all

U-Boot 2017.07-g12f5cec5fe (Apr 17 2018 - 16:04:19 +0300)

Model: Hardkernel ODROID-N1
DRAM:  3.9 GiB
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
U-Boot 2017.07-g12f5cec5fe (Apr 17 2018 - 16:04:19 +0300)

Model: Hardkernel ODROID-N1
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot:  0
reading boot.ini
707 bytes read in 11 ms (62.5 KiB/s)
cfgload: applying boot.ini...
cfgload: setenv kernel_addr "0x02000000"
cfgload: setenv fdt_addr "0x01f00000"
cfgload: setenv initrd_addr "0x04000000"
cfgload: setenv disable_vu7 "false" # false
cfgload: setenv bootrootfs "swiotlb=1 console=ttyFIQ0,115200n8 root=UUID=a130ca78-0841-400a-8823-06a304a00850 rootwait rw"
cfgload: load mmc ${bootdev} ${kernel_addr} Image.mainline
reading Image.mainline
21864456 bytes read in 2299 ms (9.1 MiB/s)
cfgload: load mmc ${bootdev} ${initrd_addr} uInitrd.mainline
reading uInitrd.mainline
9729827 bytes read in 1033 ms (9 MiB/s)
cfgload: load mmc ${bootdev} ${fdt_addr} rk3399-odroidn1-linux.dtb
reading rk3399-odroidn1-linux.dtb
72899 bytes read in 29 ms (2.4 MiB/s)
cfgload: setenv bootargs "${bootrootfs} disable_vu7=${disable_vu7}"
cfgload: booti ${kernel_addr} ${initrd_addr} ${fdt_addr}
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   initrd.img-5.0.0-rc1-ubuntu-06-g
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    9729763 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f55dc000, end f5f236e3 ... OK
   Loading Device Tree to 00000000f55c7000, end 00000000f55dbcc2 ... OK

Starting kernel ...

I'll be looking into running with a different dtb (which one?), and I'll also double check kernel size and the offset it gets written to, so that the kernel and initrd don't overwrite eachother.

joy
Posts: 911
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 20 times
Been thanked: 52 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by joy » Wed Jan 09, 2019 5:39 pm

Nice topic!

User avatar
rooted
Posts: 6921
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 278 times
Been thanked: 71 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by rooted » Wed Jan 09, 2019 5:47 pm

Maybe you need to use mainline u-boot?

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Wed Jan 09, 2019 5:53 pm

I was planning to wait for rockchip video decoder to make it into mainline, and then make it work, since I use my N1 as my main media station.
I think this should be pretty easy, only the .dtb part is need to be properly ported, and this one is what prevents your kernel from booting I guess. .dts description changed significantly between 4.4 and 4.20 - 5.0

BTW I still maintain the latest 4.4 kernel for N1 and it works flawlessly, especially with libreelec patches (another branch): https://github.com/Owersun/linux-hardkernel/

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 09, 2019 6:23 pm

Should I try a generic rk3399 dtb, or it wouldn't help anyway? The branch I'm trying has experimental vpu support, if I'm not mistaking, though I won't be using it...

User avatar
meveric
Posts: 10575
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go, H2 (N4100), N2, H2 (J4105)
Has thanked: 21 times
Been thanked: 167 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by meveric » Wed Jan 09, 2019 7:13 pm

OverSun wrote:
Wed Jan 09, 2019 5:53 pm
BTW I still maintain the latest 4.4 kernel for N1 and it works flawlessly, especially with libreelec patches (another branch): https://github.com/Owersun/linux-hardkernel/
Thanks that is really nice of you to share! :)
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 09, 2019 8:19 pm

@Owersun: a bit offtopic, but, would you be interested in integrating the patches from my branch to yours, so that I don't have to maintain mine? Your branch seems more advanced anyway:
https://github.com/hardkernel/linux/com ... idn1-4.4.y

I can export them as patch files if you want to. The important changes are adding kexec support (for petitboot), spi flash support and ir blaster via gpio (tested, it works).

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Thu Jan 10, 2019 2:04 am

generic rk3399 should be able to at least boot, while providing almost no devices in the system. thing is that there is no such thing as generic rk3399, there is a base .dtsi, but that's an "include" file, this is where "i" comes in the end. by default everything is disabled in that file, all the devices are status = "disabled", and all the board vendors create their board .dts'es, for rk3399 sometimes they contain barely few required regulators description and bunch of settings to set devices to status = "ok". so this is what needs to be created for N1 - .dts describing regulators (which are going to be identical probably to what there already is), plus list of devices that N1 has and should be enabled.

sure thing, no prob I can take you changes into the branch.
can you just remove the "ignoring compile warnings", seems pretty hectic practice for me, and create pull request?

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Thu Jan 10, 2019 3:30 am

I will try. To do this I need to fork your repo and add the patches, right? I think I have some instructions written somewhere.

User avatar
rooted
Posts: 6921
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 278 times
Been thanked: 71 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by rooted » Thu Jan 10, 2019 4:30 am

mad_ady wrote:I will try. To do this I need to fork your repo and add the patches, right? I think I have some instructions written somewhere.
Correct. Fork his repo, add your changes, push, create pull request.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Fri Jan 11, 2019 10:03 pm

I'm knee deep in the process to push my changes to Owersun's repo, and some of those changes turn on some features in the defconfig. It seems that the kernel can't build and the build process exists with:

Code: Select all

...
  LD      fs/built-in.o
  LINK    vmlinux
  LD      vmlinux.o
  MODPOST vmlinux.o
  GEN     .version
  CHK     include/generated/compile.h
  UPD     include/generated/compile.h
  CC      init/version.o
  LD      init/built-in.o
drivers/built-in.o: In function `iep_iommu_info_create':
odroid-sysfs.c:(.text+0x532d8): undefined reference to `iep_iommu_ion_set_ops'
odroid-sysfs.c:(.text+0x532d8): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `iep_iommu_ion_set_ops'
Makefile:1034: recipe for target 'vmlinux' failed
make: *** [vmlinux] Error 1
I haven't touched odroid-sysfs or iep_iommu*. @Owersun - any idea what's going on?

I will continue with the PR, but I wanted to test things before pushing changes.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Mon Jan 14, 2019 7:29 pm

Ok, I get the same error on Owersun's unmodified branch, so it wasn't me :)

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Mon Jan 14, 2019 8:21 pm

You need to disable "CONFIG_ION" (and have CONFIG_DRM enabled)

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Mon Jan 14, 2019 10:44 pm

Yup, I disabled ION and now it built and ran fine. Thank you!

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Thu Jan 17, 2019 2:59 am

mad_ady wrote:
Wed Jan 09, 2019 5:14 pm
...Starting kernel ...
OverSun wrote:
Wed Jan 09, 2019 5:53 pm
...only the .dtb part is need to be properly ported...
How would one debug a dts that compiles but produces no useful uart output?

same results for
- Adding "initcall_debug loglevel=15 earlycon=rk3399-uart,ff180000" to the bootargs
- tinyconfig.
- other rk3399 dtd s.
- 4.4 mainline
Maybe some hints from memeka here.

There are 13 examples to work from in mainline (arch/arm64/boot/dts/rockchip/rk3399*.dts), but rk3399-gru-kevin.dts (google chromebook) is the only one with a thermal_zone...
Last edited by elatllat on Tue Jan 22, 2019 7:22 am, edited 1 time in total.

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Tue Jan 22, 2019 7:20 am

I'm out of ideas, but would appreciate if anyone could demonstrate how to get debug output from a badly configured dts/kernel.
Last edited by elatllat on Wed Jan 23, 2019 5:32 pm, edited 1 time in total.

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Wed Jan 23, 2019 8:04 am

Code: Select all

root@n1:~# uname -a
Linux n1.local 5.0.0-rc3-dirty #1 SMP Tue Jan 22 23:09:36 CET 2019 aarch64 aarch64 aarch64 GNU/Linux
from the first try, if someone is still interested.

Code: Select all

root@n1:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.0.0-rc3-dirty (root@n1.local) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #1 SMP Tue Jan 22 23:09:36 CET 2019
[    0.000000] Machine model: Hardkernel ODROID-N1
[    0.000000] On node 0 totalpages: 1015296
[    0.000000]   DMA32 zone: 15864 pages used for memmap
[    0.000000]   DMA32 zone: 0 pages reserved
[    0.000000]   DMA32 zone: 1015296 pages, LIFO batch:63
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.0
[    0.000000] random: get_random_bytes called from start_kernel+0x94/0x3cc with crng_init=0
[    0.000000] percpu: Embedded 21 pages/cpu @(____ptrval____) s46424 r8192 d31400 u86016
[    0.000000] pcpu-alloc: s46424 r8192 d31400 u86016 alloc=21*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: kernel page table isolation forced OFF by command line option
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 999432
[    0.000000] Kernel command line: earlyprintk swiotlb=1 kpti=0 console=ttyFIQ0,115200n8 consoleblank=0 root=/dev/mmcblk1p1 rootwait ro video=HDMI-A-1:1920x1080@60
[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Memory: 3968632K/4061184K available (7230K kernel code, 562K rwdata, 2248K rodata, 576K init, 433K bss, 92552K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=6.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000
[    0.000000] ITS [mem 0xfee20000-0xfee3ffff]
[    0.000000] ITS@0x00000000fee20000: allocated 65536 Devices @280000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x0000000000240000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000000250000
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000008] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.001479] Console: colour dummy device 80x25
[    0.001526] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=24000)
[    0.001546] pid_max: default: 32768 minimum: 301
[    0.001804] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.001849] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.004037] ASID allocator initialised with 32768 entries
[    0.004185] rcu: Hierarchical SRCU implementation.
[    0.004537] Platform MSI: interrupt-controller@fee20000 domain created
[    0.004999] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created
[    0.005949] smp: Bringing up secondary CPUs ...
[    0.006644] Detected VIPT I-cache on CPU1
[    0.006694] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000
[    0.006711] GICv3: CPU1: using allocated LPI pending table @0x0000000000260000
[    0.006761] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.007572] Detected VIPT I-cache on CPU2
[    0.007611] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000
[    0.007627] GICv3: CPU2: using allocated LPI pending table @0x0000000000270000
[    0.007665] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.008459] Detected VIPT I-cache on CPU3
[    0.008497] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000
[    0.008512] GICv3: CPU3: using allocated LPI pending table @0x0000000000300000
[    0.008549] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.011933] CPU features: detected: EL2 vector hardening
[    0.012376] Detected PIPT I-cache on CPU4
[    0.013575] GICv3: CPU4: found redistributor 100 region 0:0x00000000fef80000
[    0.014023] GICv3: CPU4: using allocated LPI pending table @0x0000000000310000
[    0.015153] CPU4: Booted secondary processor 0x0000000100 [0x410fd082]
[    0.023449] Detected PIPT I-cache on CPU5
[    0.024616] GICv3: CPU5: found redistributor 101 region 0:0x00000000fefa0000
[    0.025020] GICv3: CPU5: using allocated LPI pending table @0x0000000000320000
[    0.026004] CPU5: Booted secondary processor 0x0000000101 [0x410fd082]
[    0.031187] smp: Brought up 1 node, 6 CPUs
[    0.031315] SMP: Total of 6 processors activated.
[    0.031337] CPU features: detected: GIC system register CPU interface
[    0.031355] CPU features: detected: 32-bit EL0 Support
[    0.031378] CPU features: detected: CRC32 instructions
[    0.032465] CPU: All CPU(s) started at EL2
[    0.033476] alternatives: patching kernel code
[    0.047336] devtmpfs: initialized
[    0.071642] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.071825] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.072971] pinctrl core: initialized pinctrl subsystem
[    0.073275] regulator-dummy: no parameters
[    0.074520] NET: Registered protocol family 16
[    0.079907] cpuidle: using governor ladder
[    0.080145] cpuidle: using governor menu
[    0.080539] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval____))
[    0.080684] DMA: preallocated 256 KiB pool for atomic allocations
[    0.145459] cryptd: max_cpu_qlen set to 1000
[    0.146916] dc_12v: 12000 mV
[    0.147152] reg-fixed-voltage dc-12v: dc_12v supplying 12000000uV
[    0.147364] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.147377] vcc1v8_s3: unable to resolve supply
[    0.147389] vcc1v8_s3: 1800 mV
[    0.147550] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.147561] vcc1v8_s3: unable to resolve supply
[    0.147575] reg-fixed-voltage vcc1v8-s3: vcc1v8_s3 supplying 1800000uV
[    0.147755] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.147767] vcc3v3_sys: unable to resolve supply
[    0.147778] vcc3v3_sys: 3300 mV
[    0.148005] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.148018] vcc1v8_s3: unable to resolve supply
[    0.148029] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.148040] vcc3v3_sys: unable to resolve supply
[    0.148053] reg-fixed-voltage vcc3v3-sys: vcc3v3_sys supplying 3300000uV
[    0.148456] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.148469] vcc5v0_host: unable to resolve supply
[    0.148504] vcc5v0_host: no parameters
[    0.148675] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.148687] vcc1v8_s3: unable to resolve supply
[    0.148699] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.148709] vcc3v3_sys: unable to resolve supply
[    0.148721] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.148731] vcc5v0_host: unable to resolve supply
[    0.148744] reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV
[    0.149077] vcc5v0_host31: no parameters
[    0.149248] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.149261] vcc1v8_s3: unable to resolve supply
[    0.149273] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.149284] vcc3v3_sys: unable to resolve supply
[    0.149296] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.149307] vcc5v0_host: unable to resolve supply
[    0.149321] reg-fixed-voltage vcc5v0-host31-regulator: vcc5v0_host31 supplying 0uV
[    0.149591] vcc5v0_host32: no parameters
[    0.149762] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.149776] vcc1v8_s3: unable to resolve supply
[    0.149788] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.149799] vcc3v3_sys: unable to resolve supply
[    0.149810] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.149822] vcc5v0_host: unable to resolve supply
[    0.149836] reg-fixed-voltage vcc5v0-host32-regulator: vcc5v0_host32 supplying 0uV
[    0.150051] reg-fixed-voltage vcc-sys: Looking up vin-supply from device tree
[    0.150064] vcc_sys: supplied by dc_12v
[    0.150086] dc_12v: could not add device link regulator.7 err -2
[    0.150103] vcc_sys: 5000 mV
[    0.150271] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.150285] vcc1v8_s3: unable to resolve supply
[    0.150296] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.150309] vcc3v3_sys: unable to resolve supply
[    0.150321] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.150333] vcc5v0_host: unable to resolve supply
[    0.150348] reg-fixed-voltage vcc-sys: vcc_sys supplying 5000000uV
[    0.156001] vgaarb: loaded
[    0.156544] usbcore: registered new interface driver usbfs
[    0.156624] usbcore: registered new interface driver hub
[    0.157077] usbcore: registered new device driver usb
[    0.157214] media: Linux media interface: v0.10
[    0.157291] videodev: Linux video capture interface: v2.00
[    0.157434] pps_core: LinuxPPS API ver. 1 registered
[    0.157445] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.157482] PTP clock support registered
[    0.159987] Advanced Linux Sound Architecture Driver Initialized.
[    0.162973] clocksource: Switched to clocksource arch_sys_counter
[    0.163822] VFS: Disk quotas dquot_6.6.0
[    0.163929] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.318115] NET: Registered protocol family 2
[    0.319717] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes)
[    0.319860] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[    0.320608] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[    0.321833] TCP: Hash tables configured (established 32768 bind 32768)
[    0.322304] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[    0.322597] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[    0.323145] NET: Registered protocol family 1
[    0.323197] PCI: CLS 0 bytes, default 64
[    0.346159] Initialise system trusted keyrings
[    0.346543] workingset: timestamp_bits=62 max_order=20 bucket_order=0
[    0.374872] NET: Registered protocol family 38
[    0.374988] Key type asymmetric registered
[    0.375003] Asymmetric key parser 'x509' registered
[    0.375297] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.375315] io scheduler mq-deadline registered
[    0.375326] io scheduler kyber registered
[    0.378700] phy phy-ff770000.syscon:phy@f780.0: Looking up phy-supply from device tree
[    0.378755] phy phy-ff770000.syscon:phy@f780.0: Looking up phy-supply property in node /syscon@ff770000/phy@f780 failed
[    0.380653] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up phy-supply from device tree
[    0.380681] reg-fixed-voltage vcc5v0-host-regulator: Looking up vin-supply from device tree
[    0.380706] vcc5v0_host: supplied by vcc_sys
[    0.380766] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e450.1 err -2
[    0.380783] phy phy-ff770000.syscon:usb2-phy@e450.1: Linked as a consumer to regulator.4
[    0.382108] phy phy-ff770000.syscon:usb2-phy@e450.2: Looking up phy-supply from device tree
[    0.382139] vcc5v0_host31: could not add device link phy-ff770000.syscon:usb2-phy@e450.2 err -2
[    0.382154] phy phy-ff770000.syscon:usb2-phy@e450.2: Linked as a consumer to regulator.5
[    0.383597] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up phy-supply from device tree
[    0.383624] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e460.3 err -2
[    0.383639] phy phy-ff770000.syscon:usb2-phy@e460.3: Linked as a consumer to regulator.4
[    0.384422] phy phy-ff770000.syscon:usb2-phy@e460.4: Looking up phy-supply from device tree
[    0.384447] vcc5v0_host32: could not add device link phy-ff770000.syscon:usb2-phy@e460.4 err -2
[    0.384463] phy phy-ff770000.syscon:usb2-phy@e460.4: Linked as a consumer to regulator.6
[    0.385299] phy phy-ff770000.syscon:pcie-phy.5: Looking up phy-supply from device tree
[    0.385321] phy phy-ff770000.syscon:pcie-phy.5: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
[    0.385532] phy phy-ff770000.syscon:pcie-phy.6: Looking up phy-supply from device tree
[    0.385550] phy phy-ff770000.syscon:pcie-phy.6: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
[    0.385695] phy phy-ff770000.syscon:pcie-phy.7: Looking up phy-supply from device tree
[    0.385712] phy phy-ff770000.syscon:pcie-phy.7: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
[    0.385846] phy phy-ff770000.syscon:pcie-phy.8: Looking up phy-supply from device tree
[    0.385862] phy phy-ff770000.syscon:pcie-phy.8: Looking up phy-supply property in node /syscon@ff770000/pcie-phy failed
[    0.386931] phy phy-ff7c0000.phy.9: Looking up phy-supply from device tree
[    0.386952] phy phy-ff7c0000.phy.9: Looking up phy-supply property in node /phy@ff7c0000/dp-port failed
[    0.387177] phy phy-ff7c0000.phy.10: Looking up phy-supply from device tree
[    0.387193] phy phy-ff7c0000.phy.10: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
[    0.388485] phy phy-ff800000.phy.11: Looking up phy-supply from device tree
[    0.388503] phy phy-ff800000.phy.11: Looking up phy-supply property in node /phy@ff800000/dp-port failed
[    0.388701] phy phy-ff800000.phy.12: Looking up phy-supply from device tree
[    0.388718] phy phy-ff800000.phy.12: Looking up phy-supply property in node /phy@ff800000/usb3-port failed
[    0.394810] rockchip-pcie f8000000.pcie: Looking up vpcie12v-supply from device tree
[    0.394860] rockchip-pcie f8000000.pcie: Looking up vpcie12v-supply property in node /pcie@f8000000 failed
[    0.394881] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[    0.394904] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    0.394922] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
[    0.394938] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    0.394955] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    0.394972] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[    0.394988] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    0.395005] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    0.395022] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[    0.395037] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    0.443809] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    0.443856] rockchip-pcie f8000000.pcie:   MEM 0xfa000000..0xfbdfffff -> 0xfa000000
[    0.443885] rockchip-pcie f8000000.pcie:    IO 0xfbe00000..0xfbefffff -> 0xfbe00000
[    0.444401] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    0.444429] pci_bus 0000:00: root bus resource [bus 00-1f]
[    0.444447] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    0.444468] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    0.444530] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    0.444652] pci 0000:00:00.0: supports D1
[    0.444664] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.453424] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.453763] pci 0000:01:00.0: [1b21:0611] type 00 class 0x010185
[    0.453864] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[    0.453883] pci 0000:01:00.0: reg 0x10: [io  size 0x0008]
[    0.453922] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[    0.453938] pci 0000:01:00.0: reg 0x14: [io  size 0x0004]
[    0.453979] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[    0.453995] pci 0000:01:00.0: reg 0x18: [io  size 0x0008]
[    0.454033] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[    0.454050] pci 0000:01:00.0: reg 0x1c: [io  size 0x0004]
[    0.454088] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[    0.454104] pci 0000:01:00.0: reg 0x20: [io  size 0x0010]
[    0.454143] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[    0.454183] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    0.454232] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512)
[    0.465721] pci_bus 0000:01: busn_res: [bus 01-1f] end is updated to 01
[    0.465791] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
[    0.465832] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref]
[    0.465853] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]
[    0.465882] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0010]
[    0.465899] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0010]
[    0.465916] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0008]
[    0.465933] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0008]
[    0.465950] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0008]
[    0.465966] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0008]
[    0.465983] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0004]
[    0.466000] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0004]
[    0.466016] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0004]
[    0.466033] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0004]
[    0.466051] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.466073] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    0.466669] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    0.470569] dma-pl330 ff6d0000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.470602] dma-pl330 ff6d0000.dma-controller: 	DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12
[    0.473663] dma-pl330 ff6e0000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.473685] dma-pl330 ff6e0000.dma-controller: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
[    0.474333] pwm-regulator vdd-log: Looking up pwm-supply from device tree
[    0.474352] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed
[    0.474452] pwm-regulator: supplied by regulator-dummy
[    0.474472] regulator-dummy: could not add device link regulator.8 err -2
[    0.474511] vdd_log: 800 <--> 1400 mV at 1118 mV
[    0.474707] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    0.474724] vcc1v8_s3: unable to resolve supply
[    0.474736] reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree
[    0.474751] vcc3v3_sys: supplied by vcc_sys
[    0.477618] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled
[    0.494575] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 36, base_baud = 1500000) is a 16550A
[    0.502880] iommu: Adding device ff8f0000.vop to group 2
[    0.503080] rockchip-vop ff8f0000.vop: Linked as a consumer to ff8f3f00.iommu
[    0.504057] iommu: Adding device ff900000.vop to group 3
[    0.504251] rockchip-vop ff900000.vop: Linked as a consumer to ff903f00.iommu
[    0.507339] rockchip-drm display-subsystem: Linked as a consumer to ff8f0000.vop
[    0.507455] rockchip-drm display-subsystem: Linked as a consumer to ff900000.vop
[    0.507870] rockchip-drm display-subsystem: Linked as a consumer to ff940000.hdmi
[    0.511564] rockchip-drm display-subsystem: bound ff8f0000.vop (ops 0xffffff80107eb4f0)
[    0.513776] rockchip-drm display-subsystem: bound ff900000.vop (ops 0xffffff80107eb4f0)
[    0.513959] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    0.515866] dwhdmi-rockchip ff940000.hdmi: registered DesignWare HDMI I2C bus driver
[    0.516331] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffff80107edaf0)
[    0.516358] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.516433] [drm] No driver support for vblank timestamp query.
[    0.624041] random: fast init done
[    0.772369] Console: switching to colour frame buffer device 240x67
[    2.386323] rockchip-drm display-subsystem: fb0:  frame buffer device
[    2.401214] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    2.409637] rc_core: Couldn't load IR keymap rc-cec
[    2.409701] Registered IR keymap rc-empty
[    2.410070] rc rc0: dw_hdmi as /devices/platform/ff940000.hdmi/rc/rc0
[    2.411179] input: dw_hdmi as /devices/platform/ff940000.hdmi/rc/rc0/input0
[    2.414057] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.417962] brd: module loaded
[    2.439870] loop: module loaded
[    2.446958] libphy: Fixed MDIO Bus: probed
[    2.448238] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
[    2.448301] rk_gmac-dwmac fe300000.ethernet: Looking up phy-supply from device tree
[    2.448328] rk_gmac-dwmac fe300000.ethernet: phy regulator is not available yet, deferred probing
[    2.451709] dwc3 fe800000.dwc3: Failed to get clk 'ref': -2
[    2.458305] dwc3 fe900000.dwc3: Failed to get clk 'ref': -2
[    2.467428] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.467457] ehci-pci: EHCI PCI platform driver
[    2.467558] ehci-platform: EHCI generic platform driver
[    2.470181] ehci-platform fe380000.usb: EHCI Host Controller
[    2.472423] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1
[    2.472743] ehci-platform fe380000.usb: irq 30, io mem 0xfe380000
[    2.479648] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
[    2.479959] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    2.479978] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.479994] usb usb1: Product: EHCI Host Controller
[    2.480010] usb usb1: Manufacturer: Linux 5.0.0-rc3-dirty ehci_hcd
[    2.480025] usb usb1: SerialNumber: fe380000.usb
[    2.485752] hub 1-0:1.0: USB hub found
[    2.485808] hub 1-0:1.0: 1 port detected
[    2.489038] ehci-platform fe3c0000.usb: EHCI Host Controller
[    2.491352] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2
[    2.491631] ehci-platform fe3c0000.usb: irq 32, io mem 0xfe3c0000
[    2.498469] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00
[    2.498771] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    2.498791] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.498807] usb usb2: Product: EHCI Host Controller
[    2.498822] usb usb2: Manufacturer: Linux 5.0.0-rc3-dirty ehci_hcd
[    2.498837] usb usb2: SerialNumber: fe3c0000.usb
[    2.503743] hub 2-0:1.0: USB hub found
[    2.503800] hub 2-0:1.0: 1 port detected
[    2.504943] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.504955] ohci-platform: OHCI generic platform driver
[    2.505298] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
[    2.508567] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3
[    2.508736] ohci-platform fe3a0000.usb: irq 31, io mem 0xfe3a0000
[    2.564705] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[    2.564725] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.564741] usb usb3: Product: Generic Platform OHCI controller
[    2.564757] usb usb3: Manufacturer: Linux 5.0.0-rc3-dirty ohci_hcd
[    2.564772] usb usb3: SerialNumber: fe3a0000.usb
[    2.569682] hub 3-0:1.0: USB hub found
[    2.569740] hub 3-0:1.0: 1 port detected
[    2.570660] ohci-platform fe3e0000.usb: Generic Platform OHCI controller
[    2.572621] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4
[    2.572764] ohci-platform fe3e0000.usb: irq 33, io mem 0xfe3e0000
[    2.628642] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[    2.628662] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.628678] usb usb4: Product: Generic Platform OHCI controller
[    2.628693] usb usb4: Manufacturer: Linux 5.0.0-rc3-dirty ohci_hcd
[    2.628708] usb usb4: SerialNumber: fe3e0000.usb
[    2.634636] hub 4-0:1.0: USB hub found
[    2.634690] hub 4-0:1.0: 1 port detected
[    2.636890] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[    2.638594] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 5
[    2.638883] xhci-hcd xhci-hcd.3.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[    2.639034] xhci-hcd xhci-hcd.3.auto: irq 224, io mem 0xfe800000
[    2.639302] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    2.639325] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.639341] usb usb5: Product: xHCI Host Controller
[    2.639356] usb usb5: Manufacturer: Linux 5.0.0-rc3-dirty xhci-hcd
[    2.639451] usb usb5: SerialNumber: xhci-hcd.3.auto
[    2.644660] hub 5-0:1.0: USB hub found
[    2.644720] hub 5-0:1.0: 1 port detected
[    2.645490] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
[    2.647572] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 6
[    2.647603] xhci-hcd xhci-hcd.3.auto: Host supports USB 3.0  SuperSpeed
[    2.647716] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.647900] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[    2.647919] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.647935] usb usb6: Product: xHCI Host Controller
[    2.647950] usb usb6: Manufacturer: Linux 5.0.0-rc3-dirty xhci-hcd
[    2.647966] usb usb6: SerialNumber: xhci-hcd.3.auto
[    2.652729] hub 6-0:1.0: USB hub found
[    2.652786] hub 6-0:1.0: 1 port detected
[    2.653711] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[    2.655631] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 7
[    2.655890] xhci-hcd xhci-hcd.4.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[    2.656005] xhci-hcd xhci-hcd.4.auto: irq 225, io mem 0xfe900000
[    2.656282] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    2.656302] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.656318] usb usb7: Product: xHCI Host Controller
[    2.656333] usb usb7: Manufacturer: Linux 5.0.0-rc3-dirty xhci-hcd
[    2.656348] usb usb7: SerialNumber: xhci-hcd.4.auto
[    2.661595] hub 7-0:1.0: USB hub found
[    2.661652] hub 7-0:1.0: 1 port detected
[    2.662247] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[    2.664440] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 8
[    2.664474] xhci-hcd xhci-hcd.4.auto: Host supports USB 3.0  SuperSpeed
[    2.664594] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.664762] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[    2.664781] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.664797] usb usb8: Product: xHCI Host Controller
[    2.664812] usb usb8: Manufacturer: Linux 5.0.0-rc3-dirty xhci-hcd
[    2.664827] usb usb8: SerialNumber: xhci-hcd.4.auto
[    2.669750] hub 8-0:1.0: USB hub found
[    2.669802] hub 8-0:1.0: 1 port detected
[    2.670746] usbcore: registered new interface driver cdc_acm
[    2.670758] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.670839] usbcore: registered new interface driver cdc_wdm
[    2.671017] usbcore: registered new interface driver usbserial_generic
[    2.671071] usbserial: USB Serial support registered for generic
[    2.671145] usbcore: registered new interface driver cp210x
[    2.671192] usbserial: USB Serial support registered for cp210x
[    2.671406] usbcore: registered new interface driver ftdi_sio
[    2.671456] usbserial: USB Serial support registered for FTDI USB Serial Device
[    2.672022] usbcore: registered new interface driver keyspan
[    2.672072] usbserial: USB Serial support registered for Keyspan - (without firmware)
[    2.672120] usbserial: USB Serial support registered for Keyspan 1 port adapter
[    2.672168] usbserial: USB Serial support registered for Keyspan 2 port adapter
[    2.672226] usbserial: USB Serial support registered for Keyspan 4 port adapter
[    2.672315] usbcore: registered new interface driver option
[    2.672538] usbserial: USB Serial support registered for GSM modem (1-port)
[    2.673347] usbcore: registered new interface driver oti6858
[    2.673421] usbserial: USB Serial support registered for oti6858
[    2.673500] usbcore: registered new interface driver pl2303
[    2.673547] usbserial: USB Serial support registered for pl2303
[    2.673664] usbcore: registered new interface driver qcserial
[    2.673712] usbserial: USB Serial support registered for Qualcomm USB modem
[    2.673869] usbcore: registered new interface driver sierra
[    2.673917] usbserial: USB Serial support registered for Sierra USB modem
[    2.680728] ads7846 spi0.1: Looking up vcc-supply from device tree
[    2.680768] ads7846 spi0.1: unable to get regulator: -517
[    2.681165] usbcore: registered new interface driver usbtouchscreen
[    2.683579] i2c /dev entries driver
[    2.693355] rk808 0-001b: chip id: 0x0
[    2.699240] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    2.699330] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    2.699463] rk808 0-001b: Looking up vcc1-supply from device tree
[    2.699493] DCDC_REG1: supplied by vcc3v3_sys
[    2.699513] vcc3v3_sys: could not add device link regulator.9 err -2
[    2.700261] vdd_center: 750 <--> 1350 mV at 900 mV
[    2.700574] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.700593] vcc1v8_s3: unable to resolve supply
[    2.700687] rk808 0-001b: Looking up vcc2-supply from device tree
[    2.700701] DCDC_REG2: supplied by vcc3v3_sys
[    2.700718] vcc3v3_sys: could not add device link regulator.10 err -2
[    2.701131] vdd_cpu_l: 750 <--> 1350 mV at 900 mV
[    2.701330] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.701346] vcc1v8_s3: unable to resolve supply
[    2.701449] rk808 0-001b: Looking up vcc3-supply from device tree
[    2.701463] DCDC_REG3: supplied by vcc3v3_sys
[    2.701481] vcc3v3_sys: could not add device link regulator.11 err -2
[    2.701505] vcc_ddr: at 3300 mV
[    2.701673] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.701689] vcc1v8_s3: unable to resolve supply
[    2.701770] rk808 0-001b: Looking up vcc4-supply from device tree
[    2.701783] DCDC_REG4: supplied by vcc3v3_sys
[    2.701801] vcc3v3_sys: could not add device link regulator.12 err -2
[    2.702122] vcc_1v8: 1800 mV
[    2.702314] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.702331] vcc1v8_s3: unable to resolve supply
[    2.702454] rk808 0-001b: Looking up vcc6-supply from device tree
[    2.702468] LDO_REG1: supplied by vcc3v3_sys
[    2.702485] vcc3v3_sys: could not add device link regulator.13 err -2
[    2.703623] vcc1v8_dvp: 1800 mV
[    2.703817] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.703834] vcc1v8_s3: unable to resolve supply
[    2.703922] rk808 0-001b: Looking up vcc6-supply from device tree
[    2.703935] LDO_REG2: supplied by vcc3v3_sys
[    2.703952] vcc3v3_sys: could not add device link regulator.14 err -2
[    2.704772] vcc3v0_tp: 3000 mV
[    2.704971] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.704988] vcc1v8_s3: unable to resolve supply
[    2.705103] rk808 0-001b: Looking up vcc7-supply from device tree
[    2.705117] LDO_REG3: supplied by vcc3v3_sys
[    2.705135] vcc3v3_sys: could not add device link regulator.15 err -2
[    2.706101] vcc1v8_pmu: 1800 mV
[    2.706350] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.706401] vcc1v8_s3: unable to resolve supply
[    2.706496] rk808 0-001b: Looking up vcc9-supply from device tree
[    2.706510] LDO_REG4: supplied by vcc3v3_sys
[    2.706528] vcc3v3_sys: could not add device link regulator.16 err -2
[    2.707500] vcc_sdio: 1800 <--> 3300 mV at 3000 mV
[    2.707692] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.707709] vcc1v8_s3: unable to resolve supply
[    2.707802] rk808 0-001b: Looking up vcc9-supply from device tree
[    2.707816] LDO_REG5: supplied by vcc3v3_sys
[    2.707833] vcc3v3_sys: could not add device link regulator.17 err -2
[    2.708652] vcca3v0_codec: 3000 mV
[    2.708844] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.708862] vcc1v8_s3: unable to resolve supply
[    2.709005] rk808 0-001b: Looking up vcc10-supply from device tree
[    2.709019] LDO_REG6: supplied by vcc3v3_sys
[    2.709036] vcc3v3_sys: could not add device link regulator.18 err -2
[    2.709996] vcc_1v5: 1500 mV
[    2.710189] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.710206] vcc1v8_s3: unable to resolve supply
[    2.710314] rk808 0-001b: Looking up vcc7-supply from device tree
[    2.710327] LDO_REG7: supplied by vcc3v3_sys
[    2.710344] vcc3v3_sys: could not add device link regulator.19 err -2
[    2.711188] vcca1v8_codec: 1800 mV
[    2.711412] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.711430] vcc1v8_s3: unable to resolve supply
[    2.711535] rk808 0-001b: Looking up vcc11-supply from device tree
[    2.711549] LDO_REG8: supplied by vcc3v3_sys
[    2.711566] vcc3v3_sys: could not add device link regulator.20 err -2
[    2.712527] vcc_3v0: 3000 mV
[    2.712721] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.712738] vcc1v8_s3: unable to resolve supply
[    2.712835] rk808 0-001b: Looking up vcc8-supply from device tree
[    2.712849] SWITCH_REG1: supplied by vcc3v3_sys
[    2.712866] vcc3v3_sys: could not add device link regulator.21 err -2
[    2.713011] vcc3v3_s3: at 3300 mV
[    2.713180] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.713197] vcc1v8_s3: unable to resolve supply
[    2.713292] rk808 0-001b: Looking up vcc12-supply from device tree
[    2.713306] SWITCH_REG2: supplied by vcc3v3_sys
[    2.713325] vcc3v3_sys: could not add device link regulator.22 err -2
[    2.713473] vcc3v3_s0: at 3300 mV
[    2.713643] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.713660] vcc1v8_s3: unable to resolve supply
[    2.720212] rk808-rtc rk808-rtc: registered as rtc0
[    2.721104] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
[    2.721135] fan53555-regulator 0-0040: Looking up vin-supply from device tree
[    2.721150] fan53555-reg: supplied by vcc3v3_sys
[    2.721167] vcc3v3_sys: could not add device link regulator.23 err -2
[    2.722025] vdd_cpu_b: 712 <--> 1500 mV at 1000 mV
[    2.722413] reg-fixed-voltage vcc1v8-s3: Looking up vin-supply from device tree
[    2.722431] vcc1v8_s3: supplied by vcc_1v8
[    2.723146] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!
[    2.723180] fan53555-regulator 0-0041: Looking up vin-supply from device tree
[    2.723195] fan53555-reg: supplied by vcc3v3_sys
[    2.723212] vcc3v3_sys: could not add device link regulator.24 err -2
[    2.724204] vdd_gpu: 712 <--> 1500 mV at 1000 mV
[    2.729950] rockchip-rga ff680000.rga: HW Version: 0x03.02
[    2.732596] rockchip-rga ff680000.rga: Registered rockchip-rga as /dev/video0
[    2.733539] rockchip-iodomain ff320000.syscon:io-domains: Looking up pmu1830-supply from device tree
[    2.733610] rockchip-iodomain ff320000.syscon:io-domains: Linked as a consumer to regulator.20
[    2.733888] rockchip-iodomain ff770000.syscon:io-domains: Looking up bt656-supply from device tree
[    2.733942] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.13
[    2.733973] rockchip-iodomain ff770000.syscon:io-domains: Looking up audio-supply from device tree
[    2.734019] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.19
[    2.734048] rockchip-iodomain ff770000.syscon:io-domains: Looking up sdmmc-supply from device tree
[    2.734090] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.16
[    2.734118] rockchip-iodomain ff770000.syscon:io-domains: Looking up gpio1830-supply from device tree
[    2.734161] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.20
[    2.743992] cpu cpu0: Looking up cpu-supply from device tree
[    2.744095] cpu cpu0: Linked as a consumer to regulator.10
[    2.744137] cpu cpu0: Dropping the link to regulator.10
[    2.744704] cpu cpu0: Looking up cpu-supply from device tree
[    2.744745] cpu cpu0: Linked as a consumer to regulator.10
[    2.745052] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 400000 KHz
[    2.745486] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 408000 KHz
[    2.746529] cpu cpu4: Looking up cpu-supply from device tree
[    2.746694] cpu cpu4: Linked as a consumer to regulator.23
[    2.746795] cpufreq: cpufreq_online: CPU4: Running at unlisted freq: 12000 KHz
[    2.747668] cpufreq: cpufreq_online: CPU4: Unlisted initial frequency changed to: 408000 KHz
[    2.749261] sdhci: Secure Digital Host Controller Interface driver
[    2.749264] sdhci: Copyright(c) Pierre Ossman
[    2.749267] Synopsys Designware Multimedia Card Interface Driver
[    2.749940] dwmmc_rockchip fe320000.dwmmc: IDMAC supports 32-bit address mode.
[    2.749977] dwmmc_rockchip fe320000.dwmmc: Using internal DMA controller.
[    2.749985] dwmmc_rockchip fe320000.dwmmc: Version ID is 270a
[    2.750020] dwmmc_rockchip fe320000.dwmmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo
[    2.750039] dwmmc_rockchip fe320000.dwmmc: Looking up vmmc-supply from device tree
[    2.750046] dwmmc_rockchip fe320000.dwmmc: Looking up vmmc-supply property in node /dwmmc@fe320000 failed
[    2.750068] dwmmc_rockchip fe320000.dwmmc: Looking up vqmmc-supply from device tree
[    2.750094] dwmmc_rockchip fe320000.dwmmc: Linked as a consumer to regulator.16
[    2.750412] vcc_sdio: ramp_delay not set
[    2.763039] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    2.773877] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.774476] sdhci-arasan fe330000.sdhci: Looking up vmmc-supply from device tree
[    2.774483] sdhci-arasan fe330000.sdhci: Looking up vmmc-supply property in node /sdhci@fe330000 failed
[    2.774507] sdhci-arasan fe330000.sdhci: Looking up vqmmc-supply from device tree
[    2.774511] sdhci-arasan fe330000.sdhci: Looking up vqmmc-supply property in node /sdhci@fe330000 failed
[    2.774583] mmc1: CQHCI version 5.10
[    2.800222] mmc1: SDHCI controller on fe330000.sdhci [fe330000.sdhci] using ADMA
[    2.801333] ledtrig-cpu: registered to indicate activity on CPUs
[    2.801388] hidraw: raw HID events driver (C) Jiri Kosina
[    2.801560] usbcore: registered new interface driver usbhid
[    2.801563] usbhid: USB HID core driver
[    2.801826] rockchip-saradc ff100000.saradc: Looking up vref-supply from device tree
[    2.801848] rockchip-saradc ff100000.saradc: Linked as a consumer to regulator.2
[    2.804534] Initializing XFRM netlink socket
[    2.804879] NET: Registered protocol family 10
[    2.805351] Segment Routing with IPv6
[    2.805400] NET: Registered protocol family 17
[    2.805412] NET: Registered protocol family 15
[    2.805430] Key type dns_resolver registered
[    2.805757] registered taskstats version 1
[    2.805761] Loading compiled-in X.509 certificates
[    2.806343] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
[    2.806375] rk_gmac-dwmac fe300000.ethernet: Looking up phy-supply from device tree
[    2.806409] rk_gmac-dwmac fe300000.ethernet: Linked as a consumer to regulator.21
[    2.806416] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input).
[    2.806422] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28).
[    2.806427] rk_gmac-dwmac fe300000.ethernet: RX delay(0x11).
[    2.806434] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no).
[    2.806457] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[    2.806460] rk_gmac-dwmac fe300000.ethernet: clock input from PHY
[    2.811471] rk_gmac-dwmac fe300000.ethernet: init for RGMII
[    2.811829] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[    2.811836] rk_gmac-dwmac fe300000.ethernet: 	DWMAC1000
[    2.811841] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported
[    2.811846] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported
[    2.811850] rk_gmac-dwmac fe300000.ethernet: COE Type 2
[    2.811854] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported
[    2.811859] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported
[    2.811881] rk_gmac-dwmac fe300000.ethernet: Normal descriptors
[    2.811886] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled
[    2.811890] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.847645] mmc1: Command Queue Engine enabled
[    2.847667] mmc1: new HS400 Enhanced strobe MMC card at address 0001
[    2.847978] mmcblk1: mmc1:0001 AJNB4R 14.6 GiB
[    2.848108] mmcblk1boot0: mmc1:0001 AJNB4R partition 1 4.00 MiB
[    2.848234] mmcblk1boot1: mmc1:0001 AJNB4R partition 2 4.00 MiB
[    2.848659] mmcblk1rpmb: mmc1:0001 AJNB4R partition 3 4.00 MiB, chardev (242:0)
[    2.850231]  mmcblk1: p1
[    2.882900] libphy: stmmac: probed
[    2.882915] mdio_bus stmmac-0:00: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    2.882921] mdio_bus stmmac-0:01: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[    2.883446] ads7846 spi0.1: Looking up vcc-supply from device tree
[    2.883476] ads7846 spi0.1: Linked as a consumer to regulator.14
[    2.883624] ads7846 spi0.1: touchscreen, irq 94
[    2.884031] input: ADS7846 Touchscreen as /devices/platform/ff1d0000.spi/spi_master/spi0/spi0.1/input/input2
[    2.884621] asoc-simple-card hdmi-sound: i2s-hifi <-> ff8a0000.i2s mapping ok
[    2.885481] input: gpio-keys as /devices/platform/gpio-keys/input/input3
[    2.886654] rk808-rtc rk808-rtc: setting system clock to 2019-01-22T23:01:36 UTC (1548198096)
[    2.887392] ALSA device list:
[    2.887397]   #0: hdmi-sound
[    2.887429] Warning: unable to open an initial console.
[    2.891595] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[    2.891622] VFS: Mounted root (ext4 filesystem) readonly on device 179:1.
[    2.894397] devtmpfs: mounted
[    2.894545] Freeing unused kernel memory: 576K
[    2.897471] Run /sbin/init as init process
[    3.039581] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    3.039999] systemd[1]: Detected architecture arm64.
[    3.046210] systemd[1]: Set hostname to <n1.local>.
[    3.258705] random: systemd: uninitialized urandom read (16 bytes read)
[    3.259110] systemd[1]: Listening on Journal Socket.
[    3.262951] random: systemd: uninitialized urandom read (16 bytes read)
[    3.264922] systemd[1]: Starting Load Kernel Modules...
[    3.265009] random: systemd: uninitialized urandom read (16 bytes read)
[    3.265301] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.265852] systemd[1]: Listening on udev Kernel Socket.
[    3.270229] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    3.270741] systemd[1]: Listening on udev Control Socket.
[    3.272734] systemd[1]: Starting udev Coldplug all Devices...
[    3.351035] EXT4-fs (mmcblk1p1): re-mounted. Opts: errors=remount-ro,discard
[    3.410210] systemd-journald[203]: Received request to flush runtime journal from PID 1
[    3.450131] synth uevent: /devices/platform/ff940000.hdmi/rc/rc0/input0: failed to send uevent
[    3.450138] input input0: uevent: failed to send synthetic uevent
[    3.884194] rk_gmac-dwmac fe300000.ethernet eth0: device MAC address 66:27:7e:c9:45:16
[    3.884769] Generic PHY stmmac-0:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    3.895399] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[    3.895415] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[    3.895674] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.022463] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   10.022517] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   20.513742] random: crng init done
[   20.513757] random: 7 urandom warning(s) missed due to ratelimiting

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Wed Jan 23, 2019 8:59 am

OverSun wrote:
Wed Jan 23, 2019 8:04 am
...first try...
Yes please share the steps to reproduce your success.
Last edited by elatllat on Wed Jan 23, 2019 5:33 pm, edited 1 time in total.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 23, 2019 2:12 pm

Teach us, master! :)

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Wed Jan 23, 2019 4:13 pm

I'll fixup the .dtb a little, because you obviously can see there are many regulators warnings, and create a repo.
There are really few changes, only .dtb and a line in Makefile to include it in the build.
Give me couple of days.
And obviously don't expect everything to be working out of the box. When the board booted the screen was flickering, there is going to be no hardware decoding and probably no sound at first. But network worked, and usb. Didn't test pcie though. So there are things to work on after it boots. Just give me a day or two. Most probably this weekend. I have really hectic days at work nowdays.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 23, 2019 4:17 pm

Take your time, and thanks!
I'm curious about GPIO support, apart from the obvious network/storage requirements.

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Thu Jan 24, 2019 4:52 am

elatllat wrote:
Wed Jan 23, 2019 8:59 am
Yes please share the steps to reproduce your success.
I also got mainline (5.0-rc3) to boot (but crash). The main issue I encountered is that the kernel is very fat! This causes the uInitrd to load over it in memory with the current uboot settings. Omitting the uInitrd is my current workaround:

Code: Select all

load mmc 1 0x02000000 Image
load mmc 1 0x01f00000 rk3399-odroidn1-linux.dtb
booti 0x02000000 - 0x01f00000

Code: Select all

U-Boot 2017.07-gf788668 (Feb 07 2018 - 02:16:39 -0200)

Model: Hardkernel ODROID-N1
DRAM:  3.9 GiB
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
Card did not respond to voltage select!
mmc_init: -95, time 24
*** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
U-Boot 2017.07-gf788668 (Feb 07 2018 - 02:16:39 -0200)

Model: Hardkernel ODROID-N1
MMC: block number 0x4001 exceeds max(0x0)
scan boot: block read fail
Writing to MMC(0)... done
Net:   
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot:  0                                                
# load mmc 1 0x02000000 Image                                                   
reading Image                                                                   
19862016 bytes read in 2316 ms (8.2 MiB/s)                                      
# load mmc 1 0x01f00000 rk3399-odroidn1-linux.dtb                               
reading rk3399-odroidn1-linux.dtb                                               
56175 bytes read in 14 ms (3.8 MiB/s)                                           
# booti 0x02000000 - 0x01f00000                                                 
## Flattened Device Tree blob at 01f00000                                       
   Booting using the fdt blob at 0x1f00000                                      
   Loading Device Tree to 00000000f5f15000, end 00000000f5f25b6e ... OK         
                                                                                
Starting kernel ...                                                             
                                                                                
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]          
[    0.000000] Linux version 5.0.0-rc3-dirty (redacted@h2) (gcc version 7.3.0 (Ubu9
[    0.000000] Machine model: Firefly-RK3399 Board                              
[    0.000000] efi: Getting EFI parameters from FDT:                            
[    0.000000] efi: UEFI not found.                                             
[    0.000000] cma: Reserved 32 MiB at 0x00000000f6000000                       
[    0.000000] NUMA: No NUMA configuration found                                
[    0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000f7fffff]
[    0.000000] NUMA: NODE_DATA [mem 0xf57e0840-0xf57e1fff]                      
[    0.000000] Zone ranges:                                                     
[    0.000000]   DMA32    [mem 0x0000000000200000-0x00000000f7ffffff]           
[    0.000000]   Normal   empty                                                 
[    0.000000] Movable zone start for each node                                 
[    0.000000] Early memory node ranges                                         
[    0.000000]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]          
[    0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000000f7ffffff] 
[    0.000000] psci: probing for conduit method from DT.                        
[    0.000000] psci: PSCIv1.0 detected in firmware.                             
[    0.000000] psci: Using standard PSCI v0.2 function IDs                      
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.                           
[    0.000000] psci: SMC Calling Convention v1.0                                
[    0.000000] random: get_random_bytes called from start_kernel+0xa8/0x408 wit0
[    0.000000] percpu: Embedded 23 pages/cpu @(____ptrval____) s55960 r8192 d308
[    0.000000] Detected VIPT I-cache on CPU0                                    
[    0.000000] CPU features: detected: ARM erratum 845719                       
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 999432    
[    0.000000] Policy zone: DMA32                                               
[    0.000000] Kernel command line:                                             
[    0.000000] Memory: 3934064K/4061184K available (11004K kernel code, 1604K r)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1       
[    0.000000] rcu: Preemptible hierarchical RCU implementation.                
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=6.   
[    0.000000]  Tasks RCU enabled.                                              
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 ji.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6     
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0                   
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode                      
[    0.000000] GICv3: Distributor has no Range Selector support                 
[    0.000000] GICv3: no VLPI support, no direct LPI support                    
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000   
[    0.000000] ITS [mem 0xfee20000-0xfee3ffff]                                  
[    0.000000] ITS@0x00000000fee20000: allocated 65536 Devices @f1080000 (flat,)
[    0.000000] ITS: using cache flushing for cmd queue                          
[    0.000000] GICv3: using LPI property table @0x00000000f1040000              
[    0.000000] GIC: using cache flushing for LPI property table                 
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000f105000
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0}
[    0.000000] GICv3: GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@1}
[    0.000000] rockchip_mmc_get_phase: invalid clk rate                         
[    0.000000] rockchip_mmc_get_phase: invalid clk rate                         
[    0.000000] rockchip_mmc_get_phase: invalid clk rate                         
[    0.000000] rockchip_mmc_get_phase: invalid clk rate                         
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).            
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycless
[    0.000009] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398s
[    0.003258] Console: colour dummy device 80x25                               
[    0.004509] printk: console [tty0] enabled                                   
[    0.004666] Calibrating delay loop (skipped), value calculated using timer f)
[    0.004722] pid_max: default: 32768 minimum: 301                             
[    0.004915] LSM: Security Framework initializing                             
[    0.008030] Dentry cache hash table entries: 524288 (order: 10, 4194304 byte)
[    0.009592] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) 
[    0.009722] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)     
[    0.009806] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.035778] ASID allocator initialised with 32768 entries                    
[    0.043778] rcu: Hierarchical SRCU implementation.                           
[    0.051960] Platform MSI: interrupt-controller@fee20000 domain created       
[    0.052522] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@feed
[    0.060939] EFI services will not be available.                              
[    0.065614] smp: Bringing up secondary CPUs ...                              
[    0.097901] Detected VIPT I-cache on CPU1                                    
[    0.097951] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000   
[    0.097971] GICv3: CPU1: using allocated LPI pending table @0x00000000f106000
[    0.098023] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]       
[    0.130024] Detected VIPT I-cache on CPU2                                    
[    0.130065] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000   
[    0.130082] GICv3: CPU2: using allocated LPI pending table @0x00000000f107000
[    0.130124] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]       
[    0.162176] Detected VIPT I-cache on CPU3                                    
[    0.162216] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000   
[    0.162232] GICv3: CPU3: using allocated LPI pending table @0x00000000f110000
[    0.162271] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]       
[    0.196934] CPU features: detected: EL2 vector hardening                     
[    0.197457] Detected PIPT I-cache on CPU4                                    
[    0.198700] GICv3: CPU4: found redistributor 100 region 0:0x00000000fef80000 
[    0.199167] GICv3: CPU4: using allocated LPI pending table @0x00000000f111000
[    0.200327] CPU4: Booted secondary processor 0x0000000100 [0x410fd082]       
[    0.236532] Detected PIPT I-cache on CPU5                                    
[    0.237721] GICv3: CPU5: found redistributor 101 region 0:0x00000000fefa0000 
[    0.238154] GICv3: CPU5: using allocated LPI pending table @0x00000000f112000
[    0.239212] CPU5: Booted secondary processor 0x0000000101 [0x410fd082]       
[    0.244227] smp: Brought up 1 node, 6 CPUs                                   
[    0.244790] SMP: Total of 6 processors activated.                            
[    0.244830] CPU features: detected: GIC system register CPU interface        
[    0.244869] CPU features: detected: 32-bit EL0 Support                       
[    0.244906] CPU features: detected: CRC32 instructions                       
[    0.254568] CPU: All CPU(s) started at EL2                                   
[    0.255365] alternatives: patching kernel code                               
[    0.261147] devtmpfs: initialized                                            
[    0.284851] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ms
[    0.285081] futex hash table entries: 2048 (order: 5, 131072 bytes)          
[    0.288626] pinctrl core: initialized pinctrl subsystem                      
[    0.294404] DMI not present or invalid.                                      
[    0.296957] NET: Registered protocol family 16                               
[    0.301706] audit: initializing netlink subsys (disabled)                    
[    0.302220] audit: type=2000 audit(0.296:1): state=initialized audit_enabled1
[    0.307928] cpuidle: using governor menu                                     
[    0.309958] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval__)
[    0.310060] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.    
[    0.324135] DMA: preallocated 256 KiB pool for atomic allocations            
[    0.331026] Serial: AMBA PL011 UART driver                                   
[    0.474720] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages     
[    0.474869] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages     
[    0.474905] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages     
[    0.474940] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages     
[    0.480144] cryptd: max_cpu_qlen set to 1000                                 
[    0.484669] ACPI: Interpreter disabled.                                      
[    0.491677] vcc3v3_pcie: supplied by dc_12v                                  
[    0.494227] vcc_sys: supplied by dc_12v                                      
[    0.502774] vgaarb: loaded                                                   
[    0.503901] SCSI subsystem initialized                                       
[    0.505940] usbcore: registered new interface driver usbfs                   
[    0.506126] usbcore: registered new interface driver hub                     
[    0.507378] usbcore: registered new device driver usb                        
[    0.511933] pps_core: LinuxPPS API ver. 1 registered                         
[    0.512043] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giom>
[    0.512139] PTP clock support registered                                     
[    0.512782] EDAC MC: Ver: 3.0.0                                              
[    0.520115] Advanced Linux Sound Architecture Driver Initialized.            
[    0.525385] clocksource: Switched to clocksource arch_sys_counter            
[    0.526219] VFS: Disk quotas dquot_6.6.0                                     
[    0.526363] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)   
[    0.526965] pnp: PnP ACPI: disabled                                          
[    0.552842] NET: Registered protocol family 2                                
[    0.557161] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 327)
[    0.557785] TCP established hash table entries: 32768 (order: 6, 262144 byte)
[    0.558659] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)      
[    0.559794] TCP: Hash tables configured (established 32768 bind 32768)       
[    0.560386] UDP hash table entries: 2048 (order: 4, 65536 bytes)             
[    0.560664] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)        
[    0.561644] NET: Registered protocol family 1                                
[    0.564698] RPC: Registered named UNIX socket transport module.              
[    0.564734] RPC: Registered udp transport module.                            
[    0.564761] RPC: Registered tcp transport module.                            
[    0.564787] RPC: Registered tcp NFSv4.1 backchannel transport module.        
[    0.572910] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counte
[    0.576275] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counte
[    0.577927] kvm [1]: 8-bit VMID                                              
[    0.577970] kvm [1]: IPA Size Limit: 40bits                                  
[    0.579867] kvm [1]: vgic-v2@fff20000                                        
[    0.580286] kvm [1]: GIC system register CPU interface enabled               
[    0.584335] kvm [1]: vgic interrupt IRQ10                                    
[    0.587602] kvm [1]: Hyp mode initialized successfully                       
[    0.609940] Initialise system trusted keyrings                               
[    0.610643] workingset: timestamp_bits=44 max_order=20 bucket_order=0        
[    0.633498] squashfs: version 4.0 (2009/01/31) Phillip Lougher               
[    0.636068] NFS: Registering the id_resolver key type                        
[    0.636254] Key type id_resolver registered                                  
[    0.636280] Key type id_legacy registered                                    
[    0.636319] nfs4filelayout_init: NFSv4 File Layout Driver Registering...     
[    0.637500] 9p: Installing v9fs 9p2000 file system support                   
[    0.759544] Key type asymmetric registered                                   
[    0.759647] Asymmetric key parser 'x509' registered                          
[    0.760081] Block layer SCSI generic (bsg) driver version 0.4 loaded (major )
[    0.760125] io scheduler mq-deadline registered                              
[    0.760153] io scheduler kyber registered                                    
[    0.776421] vcc5v0_host: supplied by vcc_sys                                 
[    0.777526] phy phy-ff770000.syscon:usb2-phy@e450.1: Linked as a consumer to5
[    0.782210] phy phy-ff770000.syscon:usb2-phy@e460.3: Linked as a consumer to5
[    0.821758] EINJ: ACPI disabled.                                             
[    0.854870] dma-pl330 ff6d0000.dma-controller: Loaded driver for PL330 DMAC-0
[    0.854991] dma-pl330 ff6d0000.dma-controller:       DBUFF-32x8bytes Num_Cha2
[    0.862615] dma-pl330 ff6e0000.dma-controller: Loaded driver for PL330 DMAC-0
[    0.862787] dma-pl330 ff6e0000.dma-controller:       DBUFF-128x8bytes Num_Ch6
[    0.879149] pwm-regulator: supplied by regulator-dummy                       
[    0.880035] vcc3v3_sys: supplied by vcc_sys                                  
[    0.897817] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled          
[    0.905538] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 38, base_baud =A
[    0.908676] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 39, base_baud =A
[    2.082891] printk: console [ttyS2] enabled                                  
[    2.093487] SuperH (H)SCI(F) driver initialized                              
[    2.100655] msm_serial: driver initialized                                   
[    2.109327] cacheinfo: Unable to detect cache hierarchy for CPU 0            
[    2.137870] loop: module loaded                                              
[    2.162320] libphy: Fixed MDIO Bus: probed                                   
[    2.170313] tun: Universal TUN/TAP device driver, 1.6                        
[    2.180179] thunder_xcv, ver 1.0                                             
[    2.184074] thunder_bgx, ver 1.0                                             
[    2.187969] nicpf, ver 1.0                                                   
[    2.193212] hclge is initializing                                            
[    2.196949] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - versin
[    2.205194] hns3: Copyright (c) 2017 Huawei Corporation.                     
[    2.211418] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k               
[    2.217988] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.              
[    2.224838] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k  
[    2.232680] igb: Copyright (c) 2007-2014 Intel Corporation.                  
[    2.239098] igbvf: Intel(R) Gigabit Virtual Function Network Driver - versiok
[    2.247914] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.              
[    2.256069] sky2: driver version 1.30                                        
[    2.263424] VFIO - User Level meta-driver version: 0.3                       
[    2.275456] dwc3 fe800000.dwc3: Failed to get clk 'ref': -2                  
[    2.292084] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/t
[    2.308758] dwc3 fe900000.dwc3: Failed to get clk 'ref': -2                  
[    2.327672] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver       
[    2.335153] ehci-pci: EHCI PCI platform driver                               
[    2.340340] ehci-platform: EHCI generic platform driver                      
[    2.348830] ehci-platform fe380000.usb: EHCI Host Controller                 
[    2.355362] ehci-platform fe380000.usb: new USB bus registered, assigned bus1
[    2.366957] ehci-platform fe380000.usb: irq 31, io mem 0xfe380000            
[    2.389056] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00           
[    2.398111] hub 1-0:1.0: USB hub found                                       
[    2.402486] hub 1-0:1.0: 1 port detected                                     
[    2.410213] ehci-platform fe3c0000.usb: EHCI Host Controller                 
[    2.416656] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus2
[    2.427307] ehci-platform fe3c0000.usb: irq 33, io mem 0xfe3c0000            
[    2.449162] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00           
[    2.457968] hub 2-0:1.0: USB hub found                                       
[    2.462351] hub 2-0:1.0: 1 port detected                                     
[    2.468276] ehci-orion: EHCI orion driver                                    
[    2.473515] ehci-exynos: EHCI EXYNOS driver                                  
[    2.478664] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver           
[    2.485712] ohci-pci: OHCI PCI platform driver                               
[    2.490910] ohci-platform: OHCI generic platform driver                      
[    2.497397] ohci-platform fe3a0000.usb: Generic Platform OHCI controller     
[    2.505047] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus3
[    2.515847] ohci-platform fe3a0000.usb: irq 32, io mem 0xfe3a0000            
[    2.586681] hub 3-0:1.0: USB hub found                                       
[    2.591029] hub 3-0:1.0: 1 port detected                                     
[    2.596701] ohci-platform fe3e0000.usb: Generic Platform OHCI controller     
[    2.604319] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus4
[    2.614798] ohci-platform fe3e0000.usb: irq 34, io mem 0xfe3e0000            
[    2.686668] hub 4-0:1.0: USB hub found                                       
[    2.691020] hub 4-0:1.0: 1 port detected                                     
[    2.696889] ohci-exynos: OHCI EXYNOS driver                                  
[    2.703983] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller                   
[    2.710294] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus n5
[    2.721731] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110
[    2.732472] xhci-hcd xhci-hcd.0.auto: irq 222, io mem 0xfe800000             
[    2.741517] hub 5-0:1.0: USB hub found                                       
[    2.745859] hub 5-0:1.0: 1 port detected                                     
[    2.751073] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller                   
[    2.757295] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus n6
[    2.765950] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0  SuperSpeed      
[    2.773530] usb usb6: We don't know the algorithms for LPM for this host, di.
[    2.784050] hub 6-0:1.0: USB hub found                                       
[    2.788434] hub 6-0:1.0: 1 port detected                                     
[    2.794131] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller                   
[    2.800406] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus n7
[    2.812054] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe64 hci version 0x110
[    2.822919] xhci-hcd xhci-hcd.1.auto: irq 223, io mem 0xfe900000             
[    2.831951] hub 7-0:1.0: USB hub found                                       
[    2.836360] hub 7-0:1.0: 1 port detected                                     
[    2.841619] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller                   
[    2.847839] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus n8
[    2.856505] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0  SuperSpeed      
[    2.864103] usb usb8: We don't know the algorithms for LPM for this host, di.
[    2.874539] hub 8-0:1.0: USB hub found                                       
[    2.878896] hub 8-0:1.0: 1 port detected                                     
[    2.885679] usbcore: registered new interface driver usb-storage             
[    2.907137] i2c /dev entries driver                                          
[    2.922540] rk808 0-001b: chip id: 0x0                                       
[    2.934783] rk808-regulator rk808-regulator: there is no dvs0 gpio           
[    2.941919] rk808-regulator rk808-regulator: there is no dvs1 gpio           
[    2.949067] DCDC_REG1: supplied by vcc_sys                                   
[    2.955302] DCDC_REG2: supplied by vcc_sys                                   
[    2.960943] DCDC_REG3: supplied by vcc_sys                                   
[    2.966148] DCDC_REG4: supplied by vcc_sys                                   
[    2.971641] LDO_REG1: supplied by vcc_sys                                    
[    2.977863] LDO_REG2: supplied by vcc_sys                                    
[    2.982697] vcc2v8_dvp: Bringing 3000000uV into 2800000-2800000uV            
[    2.990882] LDO_REG3: supplied by vcc_sys                                    
[    2.996930] LDO_REG4: supplied by vcc_sys                                    
[    3.003013] LDO_REG5: supplied by vcc_sys                                    
[    3.009023] LDO_REG6: supplied by vcc_sys                                    
[    3.015049] LDO_REG7: supplied by vcc_sys                                    
[    3.021153] LDO_REG8: supplied by vcc_sys                                    
[    3.027334] SWITCH_REG1: supplied by vcc3v3_sys                              
[    3.033240] SWITCH_REG2: supplied by vcc3v3_sys                              
[    3.041994] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!   
[    3.049906] fan53555-reg: supplied by vcc_sys                                
[    3.056496] vcc1v8_s3: supplied by vcc_1v8                                   
[    3.062484] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!   
[    3.070347] fan53555-reg: supplied by vcc_sys                                
[    3.085970] rockchip-iodomain ff320000.syscon:io-domains: Linked as a consum9
[    3.096349] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consum2
[    3.106222] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consum8
[    3.116068] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consum5
[    3.125924] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consum9
[    3.148258] cpu cpu0: Linked as a consumer to regulator.9                    
[    3.154725] cpu cpu0: Dropping the link to regulator.9                       
[    3.161041] cpu cpu0: Linked as a consumer to regulator.9                    
[    3.168613] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 400000 z
[    3.177389] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changez
[    3.188149] cpu cpu4: Linked as a consumer to regulator.22                   
[    3.195103] cpufreq: cpufreq_online: CPU4: Running at unlisted freq: 12000 Kz
[    3.204064] random: fast init done                                           
[    3.208195] cpufreq: cpufreq_online: CPU4: Unlisted initial frequency changez
[    3.220488] sdhci: Secure Digital Host Controller Interface driver           
[    3.227421] sdhci: Copyright(c) Pierre Ossman                                
[    3.232853] Synopsys Designware Multimedia Card Interface Driver             
[    3.240690] dwmmc_rockchip fe310000.dwmmc: IDMAC supports 32-bit address mod.
[    3.249064] dwmmc_rockchip fe310000.dwmmc: Using internal DMA controller.    
[    3.256661] dwmmc_rockchip fe310000.dwmmc: Version ID is 270a                
[    3.263145] dwmmc_rockchip fe310000.dwmmc: DW MMC controller at irq 28,32 bio
[    3.274262] dwmmc_rockchip fe310000.dwmmc: allocated mmc-pwrseq              
[    3.280891] mmc_host mmc0: card is non-removable.                            
[    3.299398] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz,)
[    3.323330] dwmmc_rockchip fe320000.dwmmc: IDMAC supports 32-bit address mod.
[    3.331655] dwmmc_rockchip fe320000.dwmmc: Using internal DMA controller.    
[    3.339275] dwmmc_rockchip fe320000.dwmmc: Version ID is 270a                
[    3.345761] dwmmc_rockchip fe320000.dwmmc: DW MMC controller at irq 29,32 bio
[    3.356775] dwmmc_rockchip fe320000.dwmmc: Got CD GPIO                       
[    3.373196] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz,)
[    3.396348] mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz,)
[    3.398573] sdhci-pltfm: SDHCI platform and OF driver helper                 
[    3.414373] mmc2: CQHCI version 5.10                                         
[    3.440995] mmc2: SDHCI controller on fe330000.sdhci [fe330000.sdhci] using A
[    3.449122] mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz,)
[    3.460094] ledtrig-cpu: registered to indicate activity on CPUs             
[    3.466913] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 5000000)
[    3.468105] usbcore: registered new interface driver usbhid                  
[    3.484154] usbhid: USB HID core driver                                      
[    3.484169] mmc1: new high speed SDHC card at address 0007                   
[    3.492364] NET: Registered protocol family 17                               
[    3.495252] mmcblk1: mmc1:0007 SD08G 7.42 GiB                                
[    3.499749] 9pnet: Installing 9P2000 support                                 
[    3.509514] Key type dns_resolver registered                                 
[    3.510174]  mmcblk1: p1 p2                                                  
[    3.514998] registered taskstats version 1                                   
[    3.522048] Loading compiled-in X.509 certificates                           
[    3.537253] mmc_host mmc0: Bus speed (slot 0) = 100000Hz (slot req 100000Hz,)
[    3.538054] input: gpio-keys as /devices/platform/gpio-keys/input/input0     
[    3.555291] hctosys: unable to open rtc device (rtc0)                        
[    3.561489] ALSA device list:                                                
[    3.564800]   No soundcards found.                                           
[    3.568781] ttyS2 - failed to request DMA                                    
[    3.573378] VFS: Cannot open root device "(null)" or unknown-block(0,0): err6
[    3.581744] Please append a correct "root=" boot option; here are the availa:
[    3.591114] b300         7782400 mmcblk1                                     
[    3.591117]  driver: mmcblk                                                  
[    3.598770]   b301          131071 mmcblk1p1 630bb630-01                     
[    3.598772]                                                                  
[    3.606452]   b302         7633920 mmcblk1p2 630bb630-02                     
[    3.606453]                                                                  
[    3.614129] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn)
[    3.623373] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.0.0-rc3-dirty #2     
[    3.630862] Hardware name: Firefly-RK3399 Board (DT)                         
[    3.636407] Call trace:                                                      
[    3.637006] dwmmc_rockchip fe310000.dwmmc: Unexpected interrupt latency      
[    3.639146]  dump_backtrace+0x0/0x178                                        
[    3.650616]  show_stack+0x14/0x20                                            
[    3.654320]  dump_stack+0x90/0xb4                                            
[    3.658023]  panic+0x13c/0x2ec                                               
[    3.661435]  mount_block_root+0x1a0/0x284                                    
[    3.665912]  mount_root+0x140/0x174                                          
[    3.669807]  prepare_namespace+0x138/0x180                                   
[    3.674383]  kernel_init_freeable+0x220/0x240                                
[    3.679251]  kernel_init+0x10/0x108                                          
[    3.683146]  ret_from_fork+0x10/0x18                                         
[    3.687142] SMP: stopping secondary CPUs                                     
[    3.691608] Kernel Offset: disabled                                          
[    3.695503] CPU features: 0x002,2100600c                                     
[    3.699882] Memory Limit: none                                               
[    3.703296] ---[ end Kernel panic - not syncing: VFS: Unable to mount root f-

[edit]
Adding kernel parameters allows the system to boot (using SD card):

Code: Select all

load mmc 1 0x02000000 Image
load mmc 1 0x01f00000 rk3399-odroidn1-linux.dtb
setenv bootargs "earlyprintk swiotlb=1 root=/dev/mmcblk1p2 rw"
booti 0x02000000 - 0x01f00000

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Thu Jan 24, 2019 5:05 am

Which dts did you use crashoverride?

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Thu Jan 24, 2019 5:09 am

I used the Firefly dts:

Code: Select all

[    0.000000] Machine model: Firefly-RK3399 Board 
I also set uart2 status to "okay" in rk3399.dtsi

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Thu Jan 24, 2019 5:23 am

Modern kernels if you build them with debug install all modules unstripped, which makes initrd be super huge, like 100Mb or something.
try
INSTALL_MOD_STRIP=1 make modules_install
this will make kernel strip modules when installing. This way resulting initrd is much smaller. I had this problem on other machine, I don't use initrd on N1 at all, so maybe it's just fat by itself.

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Thu Jan 24, 2019 5:26 am

I pushed my version here https://github.com/Owersun/linux-hardke ... idn1-5.0.y
Didn't make much changes to the one that I've booted yesterday, so it is still very work in progress. Feel free to correct things if you know where and what to do.

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Thu Jan 24, 2019 6:05 am

i think i forgot to commit /firmware/edid directory, you can just copy it from 4.4 directory

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Thu Jan 24, 2019 11:23 am

Apparently it was something wrong with my bootargs the whole time I was thinking I had a bad dt.
Thanks for sharing.

brad
Posts: 983
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 39 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by brad » Tue Jan 29, 2019 10:28 am

Thanks for your efforts here guys, I attempted to get mainline working some time back. Is there any luck getting GPU working in mainline?

Also what else is likely missing?

Thanks,
Brad.

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Tue Jan 29, 2019 11:46 am

brad wrote:
Tue Jan 29, 2019 10:28 am
Is there any luck getting GPU working in mainline?
There is still (5.0-rc4) no Mali driver support in mainline at all.
brad wrote:
Tue Jan 29, 2019 10:28 am
Also what else is likely missing?
I have an issue with the PCIe driver. It works fine as a module, but it causes a kernel lockup when built in. I am not sure what causes this issue. It is reproducible across any kernel version released, so it may be a bug that only shows up with the toolchain I am using (gcc-arm64 cross compile from x86-64 Ubuntu 18.04).

brad
Posts: 983
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 39 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by brad » Tue Jan 29, 2019 5:20 pm

crashoverride wrote:
Tue Jan 29, 2019 11:46 am
I have an issue with the PCIe driver. It works fine as a module, but it causes a kernel lockup when built in. I am not sure what causes this issue. It is reproducible across any kernel version released, so it may be a bug that only shows up with the toolchain I am using (gcc-arm64 cross compile from x86-64 Ubuntu 18.04).
I have been burnt many times building in a non-default kernel feature because dependencies for build in are not selected by default. You can maybe try to in include any clock, phy or maybe efuse modules which the pci depends on as built in also. Also anything else in the PCI menu that is a module that you may need when PCI is initialised.

Also thanks for the update with gpu and pci, I want to try a mainline build shortly.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Tue Jan 29, 2019 6:02 pm

I managed to get the kernel to boot as well (with owersun's odroidn1.dtb). However, networking seems not to be working. RX works (I can see the packets), but TX doesn't seem to produce valid packets. Maybe something is wrong with checksumming?

This is a tcpdump from the N1. It sees the traffic, replies to ARP, but the reply doesn't reach the destination.

Code: Select all

09:52:10.106150 ARP, Request who-has 192.168.228.15 tell 192.168.228.1, length 46
09:52:10.106267 ARP, Reply 192.168.228.15 is-at 3e:2e:aa:3e:20:b4, length 28
I've tried it with and without this: /sbin/ethtool -K eth0 rx off tx off

dmesg:

Code: Select all

[   24.736496] rk_gmac-dwmac fe300000.ethernet: PTP uses main clock
[   24.747722] rk_gmac-dwmac fe300000.ethernet: Looking up phy-supply from device tree
r.22
[   24.760652] rk_gmac-dwmac fe300000.ethernet: clock input or output? (input).
[   24.773093] rk_gmac-dwmac fe300000.ethernet: TX delay(0x28).
[   24.783994] rk_gmac-dwmac fe300000.ethernet: RX delay(0x11).
[   24.794896] rk_gmac-dwmac fe300000.ethernet: integrated PHY? (no).
[   24.806432] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[   24.818824] rk_gmac-dwmac fe300000.ethernet: clock input from PHY
[   24.835329] rk_gmac-dwmac fe300000.ethernet: init for RGMII
[   24.846387] rk_gmac-dwmac fe300000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[   24.858949] rk_gmac-dwmac fe300000.ethernet:         DWMAC1000
[   24.869308] rk_gmac-dwmac fe300000.ethernet: DMA HW capability register supported
[   24.882231] rk_gmac-dwmac fe300000.ethernet: RX Checksum Offload Engine supported
[   24.895109] rk_gmac-dwmac fe300000.ethernet: COE Type 2
[   24.905409] rk_gmac-dwmac fe300000.ethernet: TX Checksum insertion supported
[   24.917757] rk_gmac-dwmac fe300000.ethernet: Wake-Up On Lan supported
[   24.929437] rk_gmac-dwmac fe300000.ethernet: Normal descriptors
[   24.940434] rk_gmac-dwmac fe300000.ethernet: Ring mode enabled
[   24.951341] rk_gmac-dwmac fe300000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[   25.036227] libphy: stmmac: probed
[   25.059875] mdio_bus stmmac-0:01: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[   26.532906] rk_gmac-dwmac fe300000.ethernet eth0: device MAC address 0a:28:6e:bf:a1:6e
[   26.556498] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[   26.556515] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[   28.593181] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx

I think the root of the problem might be related to the MAC address that changes on each boot:

Code: Select all

3e:2e:aa:3e:20:b4
96:e7:80:91:c2:99
0a:28:6e:bf:a1:6e

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Tue Jan 29, 2019 6:07 pm

brad wrote:
Tue Jan 29, 2019 5:20 pm
You can maybe try to in include any clock, phy or maybe efuse modules which the pci depends on as built in also. Also anything else in the PCI menu that is a module that you may need when PCI is initialised.
I started from the driver source code and worked backwards to device tree. Everything that needs to be there is indeed there. This is confirmed by the driver working correctly when compiled as a module.

I also eliminated the possibility of a dependency issue (which I also thought was the case) by not having any kernel modules available while manually "insmod" the pcie driver. Again, it works as it should.

Using the official RK4.4 kernel shed a little more light since I got a backtrace. It indicates the driver accessing a 'poisoned' pointer when trying to read a PCIe configuration register.

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Tue Jan 29, 2019 6:10 pm

mad_ady wrote:
Tue Jan 29, 2019 6:02 pm
However, networking seems not to be working.
I encountered that issue too. The fix is to use the tx/rx delay settings from the N1 official device tree instead of the defaults mainline uses:
https://github.com/hardkernel/linux/blo ... #L373-L374

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Tue Jan 29, 2019 8:52 pm

Thanks @crashoverride. This did the trick: fdtput -t x /media/boot/rk3399-odroidn1-mainline.dtb /ethernet@fe300000 tx_delay 0x100

Iperf performance is not bad either:

Code: Select all

[  4] 60.0-70.0 sec   956 MBytes   802 Mbits/sec
[  5] 60.0-70.0 sec  1.09 GBytes   932 Mbits/sec
Will test stability and features that I need now that it boots! Thanks everyone!

Edit: Ok, basic GPIOs seem to work, but I have no clue what the mapping between gpio and pin number is. I have an IR led connected to the former GPIO33/1033, but I can't enable it. I can enable gpio65 for example, but don't know what it is.
I could try to do it the hard way and itterate through all of them and see when the light flashes, but I was thinking there might be a better way to find the mapping and I might learn something new!

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Tue Jan 29, 2019 10:12 pm

Hmm, my mainline kernel crashes under load. I was trying to recompile the kernel and it crashed a few minutes into the compilation - without any traces on the console. No fan activity - possibly overheat?

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Tue Jan 29, 2019 10:56 pm

... now I understand why we're running with an initrd - a few crashes later and my ext filesystem got corrupted and needed manual fixing. I don't know why it doesn't boot with the initrd I created - it's not particularly big (kernel ~11M, initrd ~9M).

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Wed Jan 30, 2019 1:54 pm

I tried using the official GCC/Linaro toolchain from Rockchip. There was no change and PCIe is still broken. I did notice that I get PCIe messages at the end that were not seen in OverSun's post:

Code: Select all

[    1.405161] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found         
[    1.411566] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found         
[    1.417956] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found         
[    1.424326] rockchip-pcie f8000000.pcie: missing "memory-region" property    
[    1.431134] PCI host bridge /pcie@f8000000 ranges:                           
[    1.435958]   MEM 0xfa000000..0xfbdfffff -> 0xfa000000                       
[    1.441126]    IO 0xfbe00000..0xfbefffff -> 0xfbe00000                       
[    1.504208] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00      
[    1.510858] pci_bus 0000:00: root bus resource [bus 00-1f]                   
[    1.516364] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]   
[    1.523259] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus add)
[    1.533224] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reg
[    1.541465] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid 
[    1.548553] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid 
[    1.555639] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid 
[    1.562724] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid 
[    1.569810] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid 
[    1.577176] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]    
[    1.583996] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pre]
[    1.591249] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]    
[    1.598059] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0010]          
[    1.604344] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0010]      
[    1.610979] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0008]          
[    1.617263] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0008]      
[    1.623897] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0008]          
[    1.630182] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0008]      
[    1.636821] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0004]          
[    1.643107] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0004]      
[    1.649742] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0004]          
[    1.656027] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0004]      
[    1.662664] pci 0000:00:00.0: PCI bridge to [bus 01]                         
[    1.667650] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]    
[    1.674504] pcieport 0000:00:00.0: enabling device (0000 -> 0002)            
[    1.680845] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt  
[    1.687825] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
My next guess is that the issue is related to order of items in the device tree.

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Wed Jan 30, 2019 9:56 pm

mad_ady wrote:
Tue Jan 29, 2019 10:12 pm
Hmm, my mainline kernel crashes under load. I was trying to recompile the kernel and it crashed a few minutes into the compilation - without any traces on the console. No fan activity - possibly overheat?
Disabling the kernel watchdog might be worth a try.
(given similar issue on XU4, and 4.4 boot issues on the N1)

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Wed Jan 30, 2019 10:44 pm

Is it the same as hardware watchdog? Or something else?

elatllat
Posts: 1590
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 25 times
Been thanked: 75 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by elatllat » Wed Jan 30, 2019 10:55 pm

Yes try the hardware watchdog ... there are 3 of them according to page 9 http://opensource.rock-chips.com/images ... 160920.pdf

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Thu Jan 31, 2019 2:56 pm

Following up ...
I tried moving PCIe to the end of the device tree. It made no difference.

I then cloned OverSun's repo and compiled it using stock gcc-arm64 on Ubuntu 18.04. The PCIe driver does load. However, after changing libata for the SATA controller from module to built-in, it experiences the same issue.

These experiments eliminate the device-tree and compiler from the possible causes. This leaves the driver/configuration as the issue and ends my adventures with RK3399 mainline.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Thu Jan 31, 2019 4:16 pm

Why do you want it built-in and don't settle for the module?

crashoverride
Posts: 4552
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 82 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by crashoverride » Thu Jan 31, 2019 4:37 pm

The PCIe hardware is fixed. The kernel should include the drivers for all always-present hardware.

I intend to use a rootfs on SATA so the PCIe and AHCI driver need to be available before the rootfs can be used. Using a uInitrd means extra maintenance since it has to be regenerated each time the kernel is updates. On a PC this would be the equivalent to having to reflash the BIOS each time the kernel is updated (my uInitrd would similarly be in flash).

brad
Posts: 983
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 39 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by brad » Thu Jan 31, 2019 4:51 pm

crashoverride wrote:
Thu Jan 31, 2019 2:56 pm
These experiments eliminate the device-tree and compiler from the possible causes. This leaves the driver/configuration as the issue and ends my adventures with RK3399 mainline.
Hi crashoverride,
Appreciate you doing the detailed testing, from you observations I see the only remaining 2 possibilities a bug or an issue with memory allocation in uboot which is mismatched with linux. Maybe we need to look at which memory regions are being allocated in the uboot PCI driver and then can either reserve in linux device tree so linux cannot touch or line them up with Linux if it can take over.

I am going to try a mainline kernel N1 compile shortly and planning on using a stock gcc on aarch64 as native compile (C2 or N1). I will try as soon as I can.

Thanks,
Brad.

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Thu Jan 31, 2019 5:51 pm

I would really like to participate, except that N1 is so good, that I use it as a main mediacenter and it is doing really perfect in this regard.
So every time I want to tinker with it I have to disconnect everything and deal with no movies, youtube and music home. =D Which is really annoying and get's me bored after few hours. =D
So I guess I'll be able to really dig into that when some next board that can do mediacenter better than N1 is going to become available...

brad
Posts: 983
Joined: Tue Mar 29, 2016 1:22 pm
languages_spoken: english
ODROIDs: C2 N1 N2 H2 (64 bit ftw)
Location: Australia
Has thanked: 16 times
Been thanked: 39 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by brad » Thu Jan 31, 2019 6:28 pm

OverSun wrote:
Thu Jan 31, 2019 5:51 pm
I would really like to participate, except that N1 is so good, that I use it as a main mediacenter and it is doing really perfect in this regard.
So every time I want to tinker with it I have to disconnect everything and deal with no movies, youtube and music home. =D Which is really annoying and get's me bored after few hours. =D
So I guess I'll be able to really dig into that when some next board that can do mediacenter better than N1 is going to become available...
My story is a bit ironic for slightly different reasons the N1 in use. Mine is currently some what of a NAS with USB attached HDD storage (no pci yet). It shares multiple NFS and samba shares to various devices and does it reliably. Even use it as a previous versions repositories for one of my windows machines. I sometime use the sdcard slot to image some of my C2's sdcard images (only time it gets rebooted is to insert new sd card) and have also run some crypto currency mining algorithms on both cpu and GPU for testing. Its hard to switch off :( I have a spare sdcard so I will deal with it and make a mainline image on there.

I want to see if -rt works on it also, not sure if we can yet mix big/little cpu's for realtime? Maybe only the bigs or littles at one time (not sure speculation or cache is so useful in this case only the operating frequency)

User avatar
rooted
Posts: 6921
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 278 times
Been thanked: 71 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by rooted » Thu Jan 31, 2019 8:49 pm

OverSun wrote:I would really like to participate, except that N1 is so good, that I use it as a main mediacenter and it is doing really perfect in this regard.
So every time I want to tinker with it I have to disconnect everything and deal with no movies, youtube and music home. =D Which is really annoying and get's me bored after few hours. =D
So I guess I'll be able to really dig into that when some next board that can do mediacenter better than N1 is going to become available...
I wish I could get my N1 to be my media center, I had a deal breaker issue last time I tried but I can't remember what it was.

Think you could share an image?

User avatar
OverSun
Posts: 1491
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 18 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by OverSun » Fri Feb 01, 2019 4:17 pm

Ahm... There is really nothing special, even Kodi image is pure vanilla 18.0. Everything that was needed was added to Kodi.
So it's pure mpp from rockchip, without changes, pure ffmpeg 4.1 with rkmpp support and pure Kodi on top. Works insanely reliable, best CEC and playback support I had.
The only thing that's custom probably is the kernel that's available from my repo, I use the other branch that include patches taken from LibreELEC, they have some supporting stuff that make reboots more reliable, but nothing really crucial.

User avatar
mad_ady
Posts: 6888
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2
Location: Bucharest, Romania
Has thanked: 248 times
Been thanked: 181 times
Contact:

Re: Trying to get mainline kernel working on N1

Unread post by mad_ady » Fri Feb 01, 2019 5:01 pm

@rooted: you can try my ubuntu 18.04 image - it should contain most of what OverSun mentioned. But there may be bugs lurking around... (last time kodi would not react to mouse/keyboard input, but it worked with hardware decoding).

Post Reply

Return to “Projects”

Who is online

Users browsing this forum: No registered users and 2 guests