jobenvil
-
Posts
60 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jobenvil
-
-
@goldfish_paris I posted some performance results on GitHub. It looks like that since kernel 4.8 the XU4 is very stable and USB3 works fine (but let's say not with all SATA-USB3 adapters)
I got new u-boot from here as well:
upgrade firmware ================ https://github.com/c0d3z3r0/xu4-update An easier way to update the firmware of your Odroid-XU4. root@bananapi:/# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 7.4G 0 disk +-sda1 8:1 1 100M 0 part /media/boot +-sda2 8:2 1 7.3G 0 part /media/root mmcblk0 179:0 0 7.4G 0 disk +-mmcblk0p1 179:1 0 7.3G 0 part / root@bananapi:/# vi /usr/bin/xu4-update root@bananapi:/# ROOT_PATH=/media/root BOOT_PATH=/media/boot SD_DEV=/dev/sda xu4-update *** Odroid-XU4 firmware updater by c0d3z3r0 *** based on rpi-update by Hexxeh, enhanced by AndrewS and Dom *** Performing self-update *** Relaunching after update *** Odroid-XU4 firmware updater by c0d3z3r0 *** based on rpi-update by Hexxeh, enhanced by AndrewS and Dom *** We're running for the first time *** Backing up files (this will take a few minutes) *** Backing up firmware *** Backing up modules 4.6.3-sunxi *** Downloading specific firmware revision (this will take a few minutes) % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 168 0 168 0 0 118 0 --:--:-- 0:00:01 --:--:-- 118 100 25.8M 0 25.8M 0 0 1515k 0 --:--:-- 0:00:17 --:--:-- 2154k *** Updating firmware *** Updating kernel modules *** depmod 4.7.2+ *** Writing new bootloader to sd card 30+0 records in 30+0 records out 15360 bytes (15 kB, 15 KiB) copied, 0.00736964 s, 2.1 MB/s 28+1 records in 28+1 records out 14592 bytes (15 kB, 14 KiB) copied, 0.0105246 s, 1.4 MB/s 1070+1 records in 1070+1 records out 548191 bytes (548 kB, 535 KiB) copied, 0.207144 s, 2.6 MB/s 512+0 records in 512+0 records out 262144 bytes (262 kB, 256 KiB) copied, 0.272539 s, 962 kB/s *** Running ldconfig *** Storing current firmware revision *** Deleting downloaded files *** Syncing changes to disk *** If no errors appeared, your firmware was successfully updated to 8bdbdebd6f60a1212e3d7b78835e9775f89bbc6d
The foillowing example shows how to upgrade offline. I took my banana pi to upgrade the kernel offline, which it means that you insert your uSD-Card in the USB-Adapter on the Banana Pi and execute the upon described procedure. With this easy step we achieved a new kernel but the more important, the new U-Boot 2016.05-dirty
Take care because after that we have the boot.scr boot script
-
tobetter created a image based on 4.6.3. His Image will become auto upgradable since he created a odroidxu4 ppa repository. You can "watch" him on GitHub to get last comments, pull requests, etc.
I installed it yesterday (only the kernel, not image) and made some iozone tests (based on tkaiser uas wiki) to check performance. Not so good like 4.7-rc4, but not interesting to be published since I have old SATA II Hardware. I bought a Samsung EVO 850 500GB and will check again the tests. This time we could consider the results based on top components.
-
wow, you don't sleep 8-)
There is another patch for enable higher frequencies (A7@1,4GHz and A15@2,00GHz). Actually it is limited (in my case) to 1,3GHz and 1,8GHz.
Did you take the tobetter@4.6 branch?
-
@wildcat_paris we were discussing some issues here, you may check it. The topic is: unable to boot new odroidxu4-v4.6 (but mine v.4.7-rc4 is up und running ;-)
-
I was playing around (Kernel 4.7-rc4) with menuconfig and comparing with older kernels where HDMI still worked. In mainline and next releases is not working my monitor, which is not HDMI native. I will receive in the next days a UART adapter and check where it hangs. Actually I use Kernel 4.7. which works somehow better with USB3.
-
There are more changes than I expected. Here.
-
post your .config in pastebin and I will git diff. Theoretically It should not differ to much. I don't remember well which branch/repo I took. My fan runs and runs... and no way to stop it. searching for solution.
Sorry for the spoiler. I will do this next time.
-
I found something weird:
- 1. You are not using all cores:
### lscpu: Architecture: armv7l Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-3 Off-line CPU(s) list: 4-7 X! Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 X! Model name: ARMv7 Processor rev 3 (v7l)
mine:
root@hiperborea /etc/init.d # lscpu Architecture: armv7l Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 Model name: ARMv7 Processor rev 3 (v7l) CPU max MHz: 1300,0000 CPU min MHz: 200,0000
- 2. Compare your dmesg with mine:
root@hiperborea /etc/init.d # dmesg [ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 4.6.0+ (root@hiperborea) (gcc version 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1) ) #1 SMP PREEMPT Mon Jun 13 20:42:30 CEST 2016 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Hardkernel Odroid XU4 [ 0.000000] cma: Reserved 128 MiB at 0xb6800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] On node 0 totalpages: 514560 [ 0.000000] free_area_init_node: node 0, pgdat c0b38680, node_mem_map eee24000 [ 0.000000] Normal zone: 1728 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 192512 pages, LIFO batch:31 [ 0.000000] HighMem zone: 322048 pages, LIFO batch:31 [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 12 pages/cpu @eed89000 s20120 r8192 d20840 u49152 [ 0.000000] pcpu-alloc: s20120 r8192 d20840 u49152 alloc=12*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 512832 [ 0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes smsc95xx.macaddr=00:1e:06:61:7a:39 governor=ondemand hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1889208K/2058240K available (6305K kernel code, 229K rwdata, 1960K rodata, 1024K init, 266K bss, 37960K reserved, 131072K cma-reserved, 1157120K highmem) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc09126f8 (9258 kB) .init : 0xc0a00000 - 0xc0b00000 (1024 kB) .data : 0xc0b00000 - 0xc0b396a0 ( 230 kB) .bss : 0xc0b3b000 - 0xc0b7dae4 ( 267 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] Switching to timer-based delay loop, resolution 41ns [ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.001037] Console: colour dummy device 80x30 [ 0.001782] console [tty1] enabled [ 0.001827] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000) [ 0.001884] pid_max: default: 32768 minimum: 301 [ 0.002067] Security Framework initialized [ 0.002099] Yama: becoming mindful. [ 0.002150] AppArmor: AppArmor disabled by boot time parameter [ 0.002237] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.002275] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.003439] CPU: Testing write buffer coherency: ok [ 0.004233] CPU0: update cpu_capacity 448 [ 0.004276] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.004485] Setting up static identity map for 0x40100000 - 0x40100058 [ 0.005042] ARM CCI driver probed [ 0.005304] Exynos MCPM support installed [ 0.060323] CPU1: update cpu_capacity 448 [ 0.060332] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 [ 0.080298] CPU2: update cpu_capacity 448 [ 0.080306] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 [ 0.100296] CPU3: update cpu_capacity 448 [ 0.100305] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 [ 0.120344] CPU4: update cpu_capacity 1535 [ 0.120352] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.140332] CPU5: update cpu_capacity 1535 [ 0.140340] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.160332] CPU6: update cpu_capacity 1535 [ 0.160339] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.180332] CPU7: update cpu_capacity 1535 [ 0.180340] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.180500] Brought up 8 CPUs [ 0.180838] SMP: Total of 8 processors activated (384.00 BogoMIPS). [ 0.180870] CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x1a) [ 0.180913] CPU: This may indicate a broken bootloader or firmware. [ 0.182327] devtmpfs: initialized [ 0.213037] evm: security.SMACK64 [ 0.213084] evm: security.SMACK64EXEC [ 0.213111] evm: security.SMACK64TRANSMUTE [ 0.213137] evm: security.SMACK64MMAP [ 0.213162] evm: security.ima [ 0.213187] evm: security.capability [ 0.213822] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 3 [ 0.215669] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns [ 0.223374] pinctrl core: initialized pinctrl subsystem [ 0.224104] regulator-dummy: no parameters [ 0.225413] NET: Registered protocol family 16 [ 0.227752] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.239984] cpuidle: using governor menu [ 0.241432] exynos-sysmmu 10a60000.sysmmu:: hardware version: 3.2 [ 0.242028] exynos-sysmmu 10a70000.sysmmu:: hardware version: 3.2 [ 0.242636] exynos-sysmmu 14650000.sysmmu:: hardware version: 3.3 [ 0.243328] exynos-sysmmu 13e80000.sysmmu:: hardware version: 3.3 [ 0.243941] exynos-sysmmu 13e90000.sysmmu:: hardware version: 3.3 [ 0.244541] exynos-sysmmu 12880000.sysmmu:: hardware version: 3.2 [ 0.245193] exynos-sysmmu 12890000.sysmmu:: hardware version: 3.2 [ 0.245790] exynos-sysmmu 128a0000.sysmmu:: hardware version: 3.2 [ 0.246384] exynos-sysmmu 128c0000.sysmmu:: hardware version: 3.2 [ 0.246957] exynos-sysmmu 128d0000.sysmmu:: hardware version: 3.2 [ 0.247509] exynos-sysmmu 128e0000.sysmmu:: hardware version: 3.2 [ 0.248057] exynos-sysmmu 11d40000.sysmmu:: hardware version: 1.0 [ 0.248629] exynos-sysmmu 11f10000.sysmmu:: hardware version: 1.2 [ 0.249210] exynos-sysmmu 11f20000.sysmmu:: hardware version: 1.2 [ 0.249786] exynos-sysmmu 11200000.sysmmu:: hardware version: 2.1 [ 0.250426] exynos-sysmmu 11210000.sysmmu:: hardware version: 2.1 [ 0.251026] exynos-sysmmu 14640000.sysmmu:: hardware version: 3.3 [ 0.251592] exynos-sysmmu 14680000.sysmmu:: hardware version: 3.3 [ 0.260226] exynos-audss-clk 3810000.audss-clock-controller:: setup completed [ 0.260672] exynos-sysmmu 11200000.sysmmu:: Enabled [ 0.260712] exynos-sysmmu 11210000.sysmmu:: Enabled [ 0.260730] platform 11000000.codec:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6ebec000 [ 0.261036] iommu: Adding device 11000000.codec: to group 0 [ 0.265161] gpio gpiochip0: (gpy7): added GPIO chardev (254:0) [ 0.265865] gpiochip_setup_dev: registered GPIOs 0 to 7 on device: gpiochip0 (gpy7) [ 0.265912] gpio gpiochip1: (gpx0): added GPIO chardev (254:1) [ 0.266572] gpiochip_setup_dev: registered GPIOs 8 to 15 on device: gpiochip1 (gpx0) [ 0.266623] gpio gpiochip2: (gpx1): added GPIO chardev (254:2) [ 0.267152] gpiochip_setup_dev: registered GPIOs 16 to 23 on device: gpiochip2 (gpx1) [ 0.267191] gpio gpiochip3: (gpx2): added GPIO chardev (254:3) [ 0.267718] gpiochip_setup_dev: registered GPIOs 24 to 31 on device: gpiochip3 (gpx2) [ 0.267757] gpio gpiochip4: (gpx3): added GPIO chardev (254:4) [ 0.268286] gpiochip_setup_dev: registered GPIOs 32 to 39 on device: gpiochip4 (gpx3) [ 0.269729] gpio gpiochip5: (gpc0): added GPIO chardev (254:5) [ 0.270350] gpiochip_setup_dev: registered GPIOs 40 to 47 on device: gpiochip5 (gpc0) [ 0.270391] gpio gpiochip6: (gpc1): added GPIO chardev (254:6) [ 0.270937] gpiochip_setup_dev: registered GPIOs 48 to 55 on device: gpiochip6 (gpc1) [ 0.270975] gpio gpiochip7: (gpc2): added GPIO chardev (254:7) [ 0.271516] gpiochip_setup_dev: registered GPIOs 56 to 62 on device: gpiochip7 (gpc2) [ 0.271555] gpio gpiochip8: (gpc3): added GPIO chardev (254:8) [ 0.272082] gpiochip_setup_dev: registered GPIOs 63 to 66 on device: gpiochip8 (gpc3) [ 0.272120] gpio gpiochip9: (gpc4): added GPIO chardev (254:9) [ 0.272638] gpiochip_setup_dev: registered GPIOs 67 to 68 on device: gpiochip9 (gpc4) [ 0.272677] gpio gpiochip10: (gpd1): added GPIO chardev (254:10) [ 0.273177] gpiochip_setup_dev: registered GPIOs 69 to 76 on device: gpiochip10 (gpd1) [ 0.273214] gpio gpiochip11: (gpy0): added GPIO chardev (254:11) [ 0.273705] gpiochip_setup_dev: registered GPIOs 77 to 82 on device: gpiochip11 (gpy0) [ 0.273742] gpio gpiochip12: (gpy1): added GPIO chardev (254:12) [ 0.274233] gpiochip_setup_dev: registered GPIOs 83 to 86 on device: gpiochip12 (gpy1) [ 0.274271] gpio gpiochip13: (gpy2): added GPIO chardev (254:13) [ 0.274765] gpiochip_setup_dev: registered GPIOs 87 to 92 on device: gpiochip13 (gpy2) [ 0.274813] gpio gpiochip14: (gpy3): added GPIO chardev (254:14) [ 0.275373] gpiochip_setup_dev: registered GPIOs 93 to 100 on device: gpiochip14 (gpy3) [ 0.275420] gpio gpiochip15: (gpy4): added GPIO chardev (254:15) [ 0.275938] gpiochip_setup_dev: registered GPIOs 101 to 108 on device: gpiochip15 (gpy4) [ 0.275976] gpio gpiochip16: (gpy5): added GPIO chardev (254:16) [ 0.276502] gpiochip_setup_dev: registered GPIOs 109 to 116 on device: gpiochip16 (gpy5) [ 0.276540] gpio gpiochip17: (gpy6): added GPIO chardev (254:17) [ 0.277032] gpiochip_setup_dev: registered GPIOs 117 to 124 on device: gpiochip17 (gpy6) [ 0.278158] gpio gpiochip18: (gpe0): added GPIO chardev (254:18) [ 0.278687] gpiochip_setup_dev: registered GPIOs 125 to 132 on device: gpiochip18 (gpe0) [ 0.278724] gpio gpiochip19: (gpe1): added GPIO chardev (254:19) [ 0.279236] gpiochip_setup_dev: registered GPIOs 133 to 134 on device: gpiochip19 (gpe1) [ 0.279273] gpio gpiochip20: (gpf0): added GPIO chardev (254:20) [ 0.279795] gpiochip_setup_dev: registered GPIOs 135 to 140 on device: gpiochip20 (gpf0) [ 0.279834] gpio gpiochip21: (gpf1): added GPIO chardev (254:21) [ 0.280421] gpiochip_setup_dev: registered GPIOs 141 to 148 on device: gpiochip21 (gpf1) [ 0.280462] gpio gpiochip22: (gpg0): added GPIO chardev (254:22) [ 0.280977] gpiochip_setup_dev: registered GPIOs 149 to 156 on device: gpiochip22 (gpg0) [ 0.281016] gpio gpiochip23: (gpg1): added GPIO chardev (254:23) [ 0.281555] gpiochip_setup_dev: registered GPIOs 157 to 164 on device: gpiochip23 (gpg1) [ 0.281595] gpio gpiochip24: (gpg2): added GPIO chardev (254:24) [ 0.282112] gpiochip_setup_dev: registered GPIOs 165 to 166 on device: gpiochip24 (gpg2) [ 0.282151] gpio gpiochip25: (gpj4): added GPIO chardev (254:25) [ 0.282667] gpiochip_setup_dev: registered GPIOs 167 to 170 on device: gpiochip25 (gpj4) [ 0.283756] gpio gpiochip26: (gpa0): added GPIO chardev (254:26) [ 0.284311] gpiochip_setup_dev: registered GPIOs 171 to 178 on device: gpiochip26 (gpa0) [ 0.284351] gpio gpiochip27: (gpa1): added GPIO chardev (254:27) [ 0.284888] gpiochip_setup_dev: registered GPIOs 179 to 184 on device: gpiochip27 (gpa1) [ 0.284926] gpio gpiochip28: (gpa2): added GPIO chardev (254:28) [ 0.285525] gpiochip_setup_dev: registered GPIOs 185 to 192 on device: gpiochip28 (gpa2) [ 0.285578] gpio gpiochip29: (gpb0): added GPIO chardev (254:29) [ 0.286111] gpiochip_setup_dev: registered GPIOs 193 to 197 on device: gpiochip29 (gpb0) [ 0.286151] gpio gpiochip30: (gpb1): added GPIO chardev (254:30) [ 0.286703] gpiochip_setup_dev: registered GPIOs 198 to 202 on device: gpiochip30 (gpb1) [ 0.286742] gpio gpiochip31: (gpb2): added GPIO chardev (254:31) [ 0.287273] gpiochip_setup_dev: registered GPIOs 203 to 206 on device: gpiochip31 (gpb2) [ 0.287311] gpio gpiochip32: (gpb3): added GPIO chardev (254:32) [ 0.287876] gpiochip_setup_dev: registered GPIOs 207 to 214 on device: gpiochip32 (gpb3) [ 0.287916] gpio gpiochip33: (gpb4): added GPIO chardev (254:33) [ 0.288454] gpiochip_setup_dev: registered GPIOs 215 to 216 on device: gpiochip33 (gpb4) [ 0.288492] gpio gpiochip34: (gph0): added GPIO chardev (254:34) [ 0.289018] gpiochip_setup_dev: registered GPIOs 217 to 224 on device: gpiochip34 (gph0) [ 0.290225] gpio gpiochip35: (gpz): added GPIO chardev (254:35) [ 0.290803] gpiochip_setup_dev: registered GPIOs 225 to 231 on device: gpiochip35 (gpz) [ 0.300064] exynos-sysmmu 14650000.sysmmu:: Enabled [ 0.300087] platform 14450000.mixer:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e0c8000 [ 0.300354] iommu: Adding device 14450000.mixer: to group 1 [ 0.300777] exynos-sysmmu 11d40000.sysmmu:: Enabled [ 0.300796] platform 11c00000.rotator:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e074000 [ 0.301054] iommu: Adding device 11c00000.rotator: to group 2 [ 0.305044] exynos-sysmmu 13e80000.sysmmu:: Enabled [ 0.305064] platform 13e00000.video-scaler:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e0d8000 [ 0.305332] iommu: Adding device 13e00000.video-scaler: to group 3 [ 0.305724] exynos-sysmmu 13e90000.sysmmu:: Enabled [ 0.305745] platform 13e10000.video-scaler:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e0dc000 [ 0.305989] iommu: Adding device 13e10000.video-scaler: to group 4 [ 0.306376] exynos-sysmmu 11f10000.sysmmu:: Enabled [ 0.306395] platform 11f50000.jpeg:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e0e0000 [ 0.306645] iommu: Adding device 11f50000.jpeg: to group 5 [ 0.307027] exynos-sysmmu 11f20000.sysmmu:: Enabled [ 0.307046] platform 11f60000.jpeg:: exynos_iommu_attach_device: Attached IOMMU with pgtable 0x6e0e4000 [ 0.307294] iommu: Adding device 11f60000.jpeg: to group 6 [ 0.307805] EXYNOS5420 PMU initialized [ 0.314242] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.314302] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.367422] SCSI subsystem initialized [ 0.368028] usbcore: registered new interface driver usbfs [ 0.368186] usbcore: registered new interface driver hub [ 0.368414] usbcore: registered new device driver usb [ 0.369576] s3c-i2c 12c80000.i2c:: slave address 0x00 [ 0.369623] s3c-i2c 12c80000.i2c:: bus frequency set to 65 KHz [ 0.370409] s3c-i2c 12c80000.i2c:: i2c-2: S3C I2C adapter [ 0.370672] media: Linux media interface: v0.10 [ 0.370803] Linux video capture interface: v2.00 [ 0.373422] NetLabel: Initializing [ 0.373463] NetLabel: domain hash size = 128 [ 0.373490] NetLabel: protocols = UNLABELED CIPSOv4 [ 0.373583] NetLabel: unlabeled traffic allowed by default [ 0.374317] clocksource: Switched to clocksource mct-frc [ 0.374655] VFS: Disk quotas dquot_6.6.0 [ 0.374784] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.401331] NET: Registered protocol family 2 [ 0.402320] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.402487] TCP bind hash table entries: 8192 (order: 5, 163840 bytes) [ 0.402882] TCP: Hash tables configured (established 8192 bind 8192) [ 0.403076] UDP hash table entries: 512 (order: 2, 24576 bytes) [ 0.403176] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes) [ 0.403576] NET: Registered protocol family 1 [ 0.403973] Trying to unpack rootfs image as initramfs... [ 0.970606] Freeing initrd memory: 7600K (c2000000 - c276c000) [ 0.975789] futex hash table entries: 2048 (order: 5, 131072 bytes) [ 0.976076] audit: initializing netlink subsys (disabled) [ 0.976244] audit: type=2000 audit(0.970:1): initialized [ 0.977414] workingset: timestamp_bits=12 max_order=19 bucket_order=7 [ 1.001012] ntfs: driver 2.1.32 [Flags: R/W]. [ 1.001725] fuse init (API version 7.24) [ 1.003207] Key type big_key registered [ 1.005072] Key type asymmetric registered [ 1.005104] Asymmetric key parser 'x509' registered [ 1.005204] bounce: pool size: 64 pages [ 1.005604] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248) [ 1.005865] io scheduler noop registered [ 1.005896] io scheduler deadline registered [ 1.006272] io scheduler cfq registered (default) [ 1.006775] phy phy-video-phy@10040728:.0: Looking up phy-supply from device tree [ 1.006792] phy phy-video-phy@10040728:.0: Looking up phy-supply property in node /video-phy@10040728 failed [ 1.007451] phy phy-video-phy@10040714:.1: Looking up phy-supply from device tree [ 1.007467] phy phy-video-phy@10040714:.1: Looking up phy-supply property in node /video-phy@10040714 failed [ 1.007695] phy phy-video-phy@10040714:.2: Looking up phy-supply from device tree [ 1.007710] phy phy-video-phy@10040714:.2: Looking up phy-supply property in node /video-phy@10040714 failed [ 1.007923] phy phy-video-phy@10040714:.3: Looking up phy-supply from device tree [ 1.007938] phy phy-video-phy@10040714:.3: Looking up phy-supply property in node /video-phy@10040714 failed [ 1.008155] phy phy-video-phy@10040714:.4: Looking up phy-supply from device tree [ 1.008170] phy phy-video-phy@10040714:.4: Looking up phy-supply property in node /video-phy@10040714 failed [ 1.009266] samsung-usb2-phy 12130000.phy:: Looking up vbus-supply from device tree [ 1.009283] samsung-usb2-phy 12130000.phy:: Looking up vbus-supply property in node /phy@12130000 failed [ 1.009301] 12130000.phy: supply vbus not found, using dummy regulator [ 1.009511] phy phy-12130000.phy:.5: Looking up phy-supply from device tree [ 1.009526] phy phy-12130000.phy:.5: Looking up phy-supply property in node /phy@12130000 failed [ 1.009758] phy phy-12130000.phy:.6: Looking up phy-supply from device tree [ 1.009773] phy phy-12130000.phy:.6: Looking up phy-supply property in node /phy@12130000 failed [ 1.009987] phy phy-12130000.phy:.7: Looking up phy-supply from device tree [ 1.010002] phy phy-12130000.phy:.7: Looking up phy-supply property in node /phy@12130000 failed [ 1.010216] phy phy-12130000.phy:.8: Looking up phy-supply from device tree [ 1.010230] phy phy-12130000.phy:.8: Looking up phy-supply property in node /phy@12130000 failed [ 1.010951] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply from device tree [ 1.010968] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-supply property in node /phy@12100000 failed [ 1.010983] 12100000.phy: supply vbus not found, using dummy regulator [ 1.011074] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply from device tree [ 1.011089] exynos5_usb3drd_phy 12100000.phy:: Looking up vbus-boost-supply property in node /phy@12100000 failed [ 1.011104] 12100000.phy: supply vbus-boost not found, using dummy regulator [ 1.011200] phy phy-12100000.phy:.9: Looking up phy-supply from device tree [ 1.011214] phy phy-12100000.phy:.9: Looking up phy-supply property in node /phy@12100000 failed [ 1.011435] phy phy-12100000.phy:.10: Looking up phy-supply from device tree [ 1.011450] phy phy-12100000.phy:.10: Looking up phy-supply property in node /phy@12100000 failed [ 1.011792] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply from device tree [ 1.011807] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-supply property in node /phy@12500000 failed [ 1.011822] 12500000.phy: supply vbus not found, using dummy regulator [ 1.011913] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply from device tree [ 1.011928] exynos5_usb3drd_phy 12500000.phy:: Looking up vbus-boost-supply property in node /phy@12500000 failed [ 1.011942] 12500000.phy: supply vbus-boost not found, using dummy regulator [ 1.012037] phy phy-12500000.phy:.11: Looking up phy-supply from device tree [ 1.012052] phy phy-12500000.phy:.11: Looking up phy-supply property in node /phy@12500000 failed [ 1.012276] phy phy-12500000.phy:.12: Looking up phy-supply from device tree [ 1.012291] phy phy-12500000.phy:.12: Looking up phy-supply property in node /phy@12500000 failed [ 1.018082] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330 [ 1.018115] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6 [ 1.025195] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330 [ 1.025227] dma-pl330 121a0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 1.032091] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330 [ 1.032125] dma-pl330 121b0000.pdma: DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32 [ 1.034077] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330 [ 1.034109] dma-pl330 10800000.mdma: DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32 [ 1.172858] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.176350] 12c00000.serial:: ttySAC0 at MMIO 0x12c00000 (irq = 76, base_baud = 0) is a S3C6400/10 [ 1.177056] 12c10000.serial:: ttySAC1 at MMIO 0x12c10000 (irq = 77, base_baud = 0) is a S3C6400/10 [ 1.177749] 12c20000.serial:: ttySAC2 at MMIO 0x12c20000 (irq = 78, base_baud = 0) is a S3C6400/10 [ 2.044553] console [ttySAC2] enabled [ 2.049025] 12c30000.serial:: ttySAC3 at MMIO 0x12c30000 (irq = 79, base_baud = 0) is a S3C6400/10 [ 2.059083] [drm] Initialized drm 1.1.0 20060810 [ 2.091348] brd: module loaded [ 2.133971] loop: module loaded [ 2.137730] exynos-dwc3 usb@12000000:: no suspend clk specified [ 2.142245] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree [ 2.142954] exynos-dwc3 usb@12400000:: no suspend clk specified [ 2.148127] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree [ 2.148606] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 2.154638] ehci-exynos: EHCI EXYNOS driver [ 2.159066] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/usb@12110000[0]' [ 2.159369] exynos-ehci 12110000.usb:: EHCI Host Controller [ 2.164384] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 1 [ 2.172401] exynos-ehci 12110000.usb:: irq 130, io mem 0x12110000 [ 2.184414] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00 [ 2.189445] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.195846] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.203060] usb usb1: Product: EHCI Host Controller [ 2.207888] usb usb1: Manufacturer: Linux 4.6.0+ ehci_hcd [ 2.213263] usb usb1: SerialNumber: 12110000.usb: [ 2.219348] hub 1-0:1.0: USB hub found [ 2.221695] hub 1-0:1.0: 3 ports detected [ 2.227079] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 2.231875] ohci-exynos: OHCI EXYNOS driver [ 2.236504] exynos-ohci 12120000.usb:: USB Host Controller [ 2.241505] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 2 [ 2.249405] exynos-ohci 12120000.usb:: irq 130, io mem 0x12120000 [ 2.313656] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 2.319026] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.327142] usb usb2: Product: USB Host Controller [ 2.330981] usb usb2: Manufacturer: Linux 4.6.0+ ohci_hcd [ 2.336345] usb usb2: SerialNumber: 12120000.usb: [ 2.342261] hub 2-0:1.0: USB hub found [ 2.344801] hub 2-0:1.0: 3 ports detected [ 2.350628] usbcore: registered new interface driver uas [ 2.354724] usbcore: registered new interface driver usb-storage [ 2.361782] i2c /dev entries driver [ 2.369694] vdd_ldo1: 1000 mV [ 2.371059] LDO2: at 1800 mV [ 2.372868] vdd_ldo3: 1800 mV [ 2.374214] LDO4: at 1800 mV [ 2.376063] vdd_ldo5: 1800 mV [ 2.377898] vdd_ldo6: 1000 mV [ 2.379701] vdd_ldo7: 1800 mV [ 2.381510] vdd_ldo8: 1800 mV [ 2.382897] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV [ 2.390133] vdd_ldo9: 3000 mV [ 2.391964] vdd_ldo10: 1800 mV [ 2.393772] vdd_ldo11: 1000 mV [ 2.395606] vdd_ldo12: 1800 mV [ 2.396943] vdd_ldo13: Bringing 3300000uV into 2800000-2800000uV [ 2.404262] vdd_ldo13: 2800 mV [ 2.405663] LDO14: at 3000 mV [ 2.406987] vdd_ldo15: Bringing 3300000uV into 3100000-3100000uV [ 2.414274] vdd_ldo15: 3100 mV [ 2.416484] vdd_ldo16: 2200 mV [ 2.418296] tsp_avdd: 3300 mV [ 2.419648] LDO18: at 1800 mV [ 2.421031] vdd_sd: Bringing 3300000uV into 2800000-2800000uV [ 2.428091] vdd_sd: 2800 mV [ 2.429452] LDO20: at 1800 mV [ 2.430789] LDO21: at 1800 mV [ 2.432129] LDO22: at 1200 mV [ 2.433458] LDO23: at 1100 mV [ 2.435666] tsp_io: 2800 mV [ 2.437037] LDO25: at 1800 mV [ 2.439188] vdd_ldo26: 3000 mV [ 2.440616] LDO27: at 1000 mV [ 2.442023] LDO28: at 3300 mV [ 2.443366] LDO29: at 1800 mV [ 2.444690] LDO30: at 1800 mV [ 2.445958] LDO31: at 1800 mV [ 2.447236] LDO32: at 1800 mV [ 2.448493] LDO33: at 1800 mV [ 2.449863] LDO34: at 3000 mV [ 2.451183] LDO35: at 1600 mV [ 2.452506] LDO36: at 1800 mV [ 2.453807] LDO37: at 1800 mV [ 2.455184] LDO38: at 2800 mV [ 2.457443] vdd_mif: 800 <--> 1300 mV at 1100 mV [ 2.459736] vdd_arm: 800 <--> 1500 mV at 1000 mV [ 2.462025] vdd_int: 800 <--> 1400 mV at 1000 mV [ 2.464360] vdd_g3d: 800 <--> 1400 mV at 1000 mV [ 2.466633] vdd_mem: 800 <--> 1400 mV at 1200 mV [ 2.468902] vdd_kfc: 800 <--> 1500 mV at 1025 mV [ 2.471191] vdd_1.0v_ldo: 800 <--> 1500 mV at 900 mV [ 2.473475] vdd_1.8v_ldo: 800 <--> 1500 mV at 1225 mV [ 2.475843] vdd_2.8v_ldo: 3000 <--> 3750 mV at 3400 mV [ 2.477987] vdd_vmem: 2850 mV [ 2.486866] s5m-rtc s2mps14-rtc: rtc core: registered s5m-rtc as rtc0 [ 2.495535] pwm-fan pwm-fan:: Failed to configure PWM [ 2.499156] pwm-fan: probe of pwm-fan: failed with error -22 [ 2.505557] exynos-tmu 10060000.tmu:: Looking up vtmu-supply from device tree [ 2.506396] exynos-tmu 10060000.tmu:: More trip points than supported by this TMU. [ 2.512568] exynos-tmu 10060000.tmu:: 2 trip points should be configured in polling mode. [ 2.520899] exynos-tmu 10064000.tmu:: Looking up vtmu-supply from device tree [ 2.521819] exynos-tmu 10068000.tmu:: Looking up vtmu-supply from device tree [ 2.522756] exynos-tmu 1006c000.tmu:: Looking up vtmu-supply from device tree [ 2.523710] exynos-tmu 100a0000.tmu:: Looking up vtmu-supply from device tree [ 2.526188] s3c2410-wdt 101d0000.watchdog:: watchdog inactive, reset disabled, irq disabled [ 2.534149] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 2.542211] cpu cpu0: Looking up cpu-supply from device tree [ 2.543187] cpu cpu0: Looking up cpu-supply from device tree [ 2.549482] cpu cpu4: Looking up cpu-supply from device tree [ 2.555956] pwrseq_emmc pwrseq:: GPIO lookup for consumer reset [ 2.555969] pwrseq_emmc pwrseq:: using device tree for GPIO lookup [ 2.555989] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/pwrseq[0]' - status (0) [ 2.556137] sdhci: Secure Digital Host Controller Interface driver [ 2.560888] sdhci: Copyright(c) Pierre Ossman [ 2.565453] Synopsys Designware Multimedia Card Interface Driver [ 2.571948] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode. [ 2.578219] dwmmc_exynos 12200000.mmc:: Using internal DMA controller. [ 2.584619] dwmmc_exynos 12200000.mmc:: Version ID is 250a [ 2.590126] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 83,64 bit host data width,64 deep fifo [ 2.599470] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply from device tree [ 2.599482] dwmmc_exynos 12200000.mmc:: Looking up vmmc-supply property in node /mmc@12200000 failed [ 2.599550] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply from device tree [ 2.599560] dwmmc_exynos 12200000.mmc:: Looking up vqmmc-supply property in node /mmc@12200000 failed [ 2.599614] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer cd [ 2.599623] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup [ 2.599644] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/mmc@12200000[0]' - status (0) [ 2.599665] dwmmc_exynos 12200000.mmc:: Got CD GPIO [ 2.604256] dwmmc_exynos 12200000.mmc:: GPIO lookup for consumer wp [ 2.604265] dwmmc_exynos 12200000.mmc:: using device tree for GPIO lookup [ 2.604275] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12200000[0]' [ 2.604285] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12200000[0]' [ 2.604345] dwmmc_exynos 12200000.mmc:: using lookup tables for GPIO lookup [ 2.604357] dwmmc_exynos 12200000.mmc:: lookup for GPIO wp failed [ 2.604424] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq [ 2.639645] dwmmc_exynos 12200000.mmc:: 1 slots initialized [ 2.644069] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode. [ 2.650786] dwmmc_exynos 12220000.mmc:: Using internal DMA controller. [ 2.657213] dwmmc_exynos 12220000.mmc:: Version ID is 250a [ 2.662707] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 84,64 bit host data width,64 deep fifo [ 2.672054] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply from device tree [ 2.672066] dwmmc_exynos 12220000.mmc:: Looking up vmmc-supply property in node /mmc@12220000 failed [ 2.672121] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply from device tree [ 2.672132] dwmmc_exynos 12220000.mmc:: Looking up vqmmc-supply property in node /mmc@12220000 failed [ 2.672184] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer cd [ 2.672193] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup [ 2.672204] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12220000[0]' [ 2.672214] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12220000[0]' [ 2.672223] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup [ 2.672233] dwmmc_exynos 12220000.mmc:: lookup for GPIO cd failed [ 2.672244] dwmmc_exynos 12220000.mmc:: GPIO lookup for consumer wp [ 2.672252] dwmmc_exynos 12220000.mmc:: using device tree for GPIO lookup [ 2.672262] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12220000[0]' [ 2.672271] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12220000[0]' [ 2.672280] dwmmc_exynos 12220000.mmc:: using lookup tables for GPIO lookup [ 2.672289] dwmmc_exynos 12220000.mmc:: lookup for GPIO wp failed [ 2.699388] dwmmc_exynos 12220000.mmc:: 1 slots initialized [ 2.704639] s5p-secss 10830000.sss:: s5p-sss driver registered [ 2.710401] usbcore: registered new interface driver usbhid [ 2.714877] usbhid: USB HID core driver [ 2.719957] NET: Registered protocol family 17 [ 2.723109] NET: Registered protocol family 15 [ 2.728192] Registering SWP/SWPB emulation handler [ 2.733260] registered taskstats version 1 [ 2.747654] Key type encrypted registered [ 2.750248] ima: No TPM chip found, activating TPM-bypass! [ 2.755820] evm: HMAC attrs: 0x1 [ 2.764708] exynos-dwc3 usb@12000000:: no suspend clk specified [ 2.769156] exynos-dwc3 usb@12000000:: Looking up vdd33-supply from device tree [ 2.769683] exynos-dwc3 usb@12000000:: Looking up vdd10-supply from device tree [ 2.772997] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller [ 2.777096] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 3 [ 2.784932] xhci-hcd xhci-hcd.6.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010 [ 2.793354] xhci-hcd xhci-hcd.6.auto: irq 134, io mem 0x12000000 [ 2.799512] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.806058] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.813258] usb usb3: Product: xHCI Host Controller [ 2.818094] usb usb3: Manufacturer: Linux 4.6.0+ xhci-hcd [ 2.823469] usb usb3: SerialNumber: xhci-hcd.6.auto [ 2.826864] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 2.826953] mmc1: new high speed SDHC card at address aaaa [ 2.827669] mmcblk1: mmc1:aaaa SL08G 7.40 GiB [ 2.829075] mmcblk1: p1 p2 [ 2.851337] hub 3-0:1.0: USB hub found [ 2.854427] hub 3-0:1.0: 1 port detected [ 2.858728] xhci-hcd xhci-hcd.6.auto: xHCI Host Controller [ 2.863782] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 4 [ 2.871453] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.879553] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [ 2.886205] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.893403] usb usb4: Product: xHCI Host Controller [ 2.898248] usb usb4: Manufacturer: Linux 4.6.0+ xhci-hcd [ 2.903624] usb usb4: SerialNumber: xhci-hcd.6.auto [ 2.909138] hub 4-0:1.0: USB hub found [ 2.912222] hub 4-0:1.0: 1 port detected [ 2.917084] exynos-dwc3 usb@12400000:: no suspend clk specified [ 2.921996] exynos-dwc3 usb@12400000:: Looking up vdd33-supply from device tree [ 2.922525] exynos-dwc3 usb@12400000:: Looking up vdd10-supply from device tree [ 2.923798] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 2.927846] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5 [ 2.935715] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x00010010 [ 2.944151] xhci-hcd xhci-hcd.9.auto: irq 135, io mem 0x12400000 [ 2.950227] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.956918] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.964053] usb usb5: Product: xHCI Host Controller [ 2.968897] usb usb5: Manufacturer: Linux 4.6.0+ xhci-hcd [ 2.974273] usb usb5: SerialNumber: xhci-hcd.9.auto [ 2.979804] hub 5-0:1.0: USB hub found [ 2.982850] hub 5-0:1.0: 1 port detected [ 2.987197] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller [ 2.992227] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6 [ 2.999895] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.007998] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003 [ 3.014712] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.021851] usb usb6: Product: xHCI Host Controller [ 3.026702] usb usb6: Manufacturer: Linux 4.6.0+ xhci-hcd [ 3.032071] usb usb6: SerialNumber: xhci-hcd.9.auto [ 3.037577] hub 6-0:1.0: USB hub found [ 3.040669] hub 6-0:1.0: 1 port detected [ 3.045732] s3c-rtc 101e0000.rtc:: rtc disabled, re-enabling [ 3.050258] s3c-rtc 101e0000.rtc:: warning: invalid RTC value so initializing it [ 3.057995] s3c-rtc 101e0000.rtc:: rtc core: registered s3c as rtc1 [ 3.065297] Power domain power-domain@10044120 disable failed [ 3.069754] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01 00:00:06 UTC (946684806) [ 3.104477] Freeing unused kernel memory: 1024K (c0a00000 - c0b00000) [ 3.151565] random: systemd-udevd urandom read with 118 bits of entropy available [ 3.164370] usb 3-1: new high-speed USB device number 2 using xhci-hcd [ 3.224469] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.247161] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616 [ 3.252428] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.259525] usb 4-1: Product: USB3.0 Hub [ 3.263387] usb 4-1: Manufacturer: GenesysLogic [ 3.272716] hub 4-1:1.0: USB hub found [ 3.275309] hub 4-1:1.0: 2 ports detected [ 3.300524] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610 [ 3.305786] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.312890] usb 3-1: Product: USB2.0 Hub [ 3.316787] usb 3-1: Manufacturer: GenesysLogic [ 3.352138] hub 3-1:1.0: USB hub found [ 3.354750] hub 3-1:1.0: 2 ports detected [ 3.454437] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd [ 3.475326] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153 [ 3.480604] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 3.487733] usb 6-1: Product: USB 10/100/1000 LAN [ 3.492401] usb 6-1: Manufacturer: Realtek [ 3.496473] usb 6-1: SerialNumber: 000001000000 [ 3.769426] random: nonblocking pool is initialized [ 4.064350] raid6: int32x1 gen() 402 MB/s [ 4.149381] raid6: int32x1 xor() 411 MB/s [ 4.234398] raid6: int32x2 gen() 607 MB/s [ 4.319325] raid6: int32x2 xor() 540 MB/s [ 4.404319] raid6: int32x4 gen() 678 MB/s [ 4.489371] raid6: int32x4 xor() 559 MB/s [ 4.574445] raid6: int32x8 gen() 285 MB/s [ 4.659402] raid6: int32x8 xor() 191 MB/s [ 4.662199] raid6: using algorithm int32x4 gen() 678 MB/s [ 4.667596] raid6: .... xor() 559 MB/s, rmw enabled [ 4.672447] raid6: using intx1 recovery algorithm [ 4.678409] xor: measuring software checksum speed [ 4.729329] arm4regs : 1535.200 MB/sec [ 4.779356] 8regs : 1083.200 MB/sec [ 4.829343] 32regs : 2350.400 MB/sec [ 4.832058] xor: using function: 32regs (2350.400 MB/sec) [ 4.855371] Btrfs loaded, assert=on [ 7.764447] usb 4-1.2: new SuperSpeed USB device number 3 using xhci-hcd [ 7.785658] usb 4-1.2: New USB device found, idVendor=152d, idProduct=3562 [ 7.791088] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.798367] usb 4-1.2: Product: AD TO BE II [ 7.802518] usb 4-1.2: Manufacturer: ADMKIV [ 7.806679] usb 4-1.2: SerialNumber: DB123456789628 [ 7.822724] scsi host0: uas [ 7.825526] scsi 0:0:0:0: Direct-Access ADplus SuperVer 6302 PQ: 0 ANSI: 6 [ 7.865497] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 7.865505] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 7.876807] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 7.882738] sd 0:0:0:0: [sda] Write Protect is off [ 7.886778] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08 [ 7.887148] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 7.978658] sda: sda1 sda2 [ 7.982428] sd 0:0:0:0: [sda] Attached SCSI disk [ 8.426771] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null) [ 8.871821] systemd[1]: System time before build time, advancing clock. [ 8.974987] NET: Registered protocol family 10 [ 9.039104] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 9.056680] systemd[1]: Detected architecture arm. [ 9.085579] systemd[1]: Set hostname to <hiperborea>. [ 9.912138] systemd[1]: Created slice User and Session Slice. [ 9.929638] systemd[1]: Listening on LVM2 metadata daemon socket. [ 9.950250] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 9.974466] systemd[1]: Reached target Encrypted Volumes. [ 9.989617] systemd[1]: Listening on Journal Socket (/dev/log). [ 10.009735] systemd[1]: Listening on Journal Audit Socket. [ 10.024679] systemd[1]: Listening on Journal Socket. [ 10.039651] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 10.059533] systemd[1]: Listening on udev Kernel Socket. [ 10.074543] systemd[1]: Listening on LVM2 poll daemon socket. [ 10.094517] systemd[1]: Listening on Syslog Socket. [ 10.109668] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 10.129934] systemd[1]: Created slice System Slice. [ 10.145016] systemd[1]: Created slice system-systemd\x2dfsck.slice. [ 10.184634] systemd[1]: Mounting RPC Pipe File System... [ 10.200033] systemd[1]: Created slice system-getty.slice. [ 10.217366] systemd[1]: Starting Journal Service... [ 10.234492] systemd[1]: Reached target Slices. [ 10.252456] systemd[1]: Mounting Debug File System... [ 10.272606] systemd[1]: Starting Nameserver information manager... [ 10.293051] systemd[1]: Mounting POSIX Message Queue File System... [ 10.294698] RPC: Registered named UNIX socket transport module. [ 10.294703] RPC: Registered udp transport module. [ 10.294707] RPC: Registered tcp transport module. [ 10.294711] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 10.335201] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 10.354684] systemd[1]: Listening on fsck to fsckd communication Socket. [ 10.394895] systemd[1]: Starting Remount Root and Kernel File Systems... [ 10.411230] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null) [ 10.424545] systemd[1]: Reached target Swap. [ 10.441510] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 10.499945] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [ 10.528999] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 10.589916] systemd[1]: Starting Load Kernel Modules... [ 10.604688] systemd[1]: Listening on udev Control Socket. [ 10.627094] systemd[1]: Mounted RPC Pipe File System. [ 10.644635] systemd[1]: Mounted POSIX Message Queue File System. [ 10.664509] systemd[1]: Mounted Debug File System. [ 10.679805] systemd[1]: Started Journal Service. [ 11.257762] systemd-journald[1755]: Received request to flush runtime journal from PID 1 [ 12.339941] usbcore: registered new interface driver r8152 [ 12.428966] usbcore: registered new interface driver cdc_ether [ 12.523976] usb 6-1: reset SuperSpeed USB device number 2 using xhci-hcd [ 12.660714] r8152 6-1:1.0 eth0: v1.08.3 [ 26.307526] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) -
awesome!. I was trying to put statical IP, changing DNS, etc. Something with the interfaces.d/ init scripts should be the problem, but no idea, time and will.
-
stuck at first boot... no way to login as root (as usual
)with USB-UART and I don't see DHCP request (so no network). let's try keyboard and screensorry to comment this so late. I can confirm I tried already last week this: xenial + odroidxu4 = not booting properly. DHCP / Eth0 issue. I think this bug was fixed with jessie, not Xenial. I gave up trying to fix eth0.
-
-
@jobenvil
newer kernel it is better to use UUID because there is a mess on XU4 with /dev/mmc* and /dev/mmc*boot? between eMMC and SDcard
just to make sure, you have done only little changes on your "lib" (adding "next")
and done your compilation & updates directly on the XU4, haven't you? please (I have tried to follow you but got quickly lost
Normal and don't worry, mi english is "broken" :-)
1) Yes, there is a mess with device drivers. You should use UUID to uniq identification of devices. So you are save if boot search for mmc0 or mmc1
2) Yes, only "next" was added = minor change
3.1) No, I tried to compile and build an image with ARMBIAN tools changing the "next" (see point 2). This compiled well, but the produced image doesn't boot because the boot.ini and fstab needs changes. After properly modifications, the u-boot is loading.
3.2) Yes, I prefer to compile directly on XU4. This takes less than 20 minutes. You get zImage, xu4-dtb and modules. Follow the guide from Uli Middelberg.
-
yes, this was working like it is mentioned. You should care about the /etc/fstab, wait...
root@hiperborea /media/boot # cat /etc/fstab # <file system> < mount point> <type> <options> <dump> <pass> #/dev/mmcblk0p2 / ext4 noatime,barrier=0,commit=5,errors=remount-ro 0 1 UUID=e139ce78-9841-40fe-8823-96a304a09859 / ext4 defaults,noatime,nodiratime 0 1 UUID=1E66-94B1 /media/boot vfat defaults 0 0 #/dev/sda1 /media/sda ext4 defaults,noatime,nodiratime,data=writeback,commit=600,errors=remount-ro 0 2 # Seagate 500GB 7200RPM ST9500325AS #/dev/sda1 /media/sda ext4 noatime,barrier=0,errors=remount-ro 0 2 LABEL="data-7200" /media/sda ext4 defaults,noatime,nodiratime 0 2 # deleted barrier=0, para error tan largo en disco duro # Seagate 500GB 5400RPM #/dev/sdb1 /media/sdb ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev,noexec,mode=1777,size=512M 0 0 #tmpfs /var/tmp tmpfs defaults explanation: Verzeichnis /var/tmp sollte generell nicht auf diese Weise ausgelagert werden LABEL="swap-7200" none swap sw 0 0 /media/sda/album /var/www/Album none bind 0 0
UUID are mandatory
-
Actually, mi boot.ini looks like:
ODROIDXU-UBOOT-CONFIG # U-Boot Parameters setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" # Mac address configuration setenv macaddr "00:1e:06:61:7a:39" #------------------------------------------------------------------------------------------------------ # Basic Ubuntu Setup. Don't touch unless you know what you are doing. # -------------------------------- # original: setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=a4b494db-320a-4ce2-bb3a-841db943f9c0 rootwait ro" # working 4.7rc-2 and 4.6.0+ #setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes" # working armbian 3.10.101: setenv bootrootfs "console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait ro net.ifnames=0 cgroup_disable=memory,cpu,devices,cpuacct,freezer,blkio swapaccount=0 apparmor=0" # original hardkernel uInitrd: #setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x42000000 uInitrd; fatload mmc 0:1 0x44000000 exynos5422-odroidxu3.dtb; bootz 0x40008000 0x42000000 0x44000000" # working 4.7 : #setenv bootcmd "fatload mmc 0:1 0x40008000 zImage_next; fatload mmc 0:1 0x42000000 uInitrd-4.7.0-rc2-next-20160609; fatload mmc 0:1 0x44000000 exynos5422-odroidxu4_next.dtb; bootz 0x40008000 0x42000000 0x44000000" #not working 4.7.0-rc3: #setenv bootcmd "fatload mmc 0:1 0x40008000 zImage-4.7.0-rc3; fatload mmc 0:1 0x42000000 uInitrd-4.7.0-rc3-g65f0709; fatload mmc 0:1 0x44000000 exynos5422-odroidxu4-4.7.0-rc3.dtb; boot 0x40008000 0x42000000 0x44000000" # working 4.6.0+ setenv bootcmd "fatload mmc 0:1 0x40008000 zImage_4.6.0+; fatload mmc 0:1 0x42000000 uInitrd-4.6.0+; fatload mmc 0:1 0x44000000 exynos5422-odroidxu4_4.6.0+.dtb; bootz 0x40008000 0x42000000 0x44000000" # working armbian 3.10.101: setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb; bootz 0x40008000 0x44000000" # --- Screen Configuration for HDMI --- # # --------------------------------------- # Uncomment only ONE line! Leave all commented for automatic selection. # Uncomment only the setenv line! # ---------------------------------------
and /media/boot
root@hiperborea /media/boot # ll total 36766 -rwxr-xr-x 1 root root 3402084 Jun 10 21:11 zImage -rwxr-xr-x 1 root root 1891504 Jun 10 21:11 System.map-3.10.101-odroidxu4 -rwxr-xr-x 1 root root 111399 Jun 10 21:11 config-3.10.101-odroidxu4 -rwxr-xr-x 1 root root 54607 Jun 12 13:20 exynos5422-odroidxu4_next.dtb -rwxr-xr-x 1 root root 4499904 Jun 12 13:20 zImage_next -rwxr-xr-x 1 root root 105958 Jun 12 13:23 config-4.7.0-rc2-next-20160609 -rwxr-xr-x 1 root root 6245260 Jun 13 08:39 initrd.img-3.10.101-odroidxu4 -rwxr-xr-x 1 root root 5760903 Jun 13 09:02 uInitrd-4.7.0-rc2-next-20160609 -rwxr-xr-x 1 root root 47808 Jun 13 21:17 exynos5422-odroidxu4_4.6.0+.dtb -rwxr-xr-x 1 root root 4206392 Jun 13 21:19 zImage_4.6.0+ -rwxr-xr-x 1 root root 113418 Jun 13 21:20 config-4.6.0+ -rwxr-xr-x 1 root root 7782354 Jun 13 23:06 uInitrd-4.6.0+ -rwxr-xr-x 1 root root 3402084 Jun 16 11:30 vmlinuz-3.10.101-odroidxu4 -rwxr-xr-x 1 root root 9788 Jun 16 11:56 boot.ini drwxr-xr-x 2 root root 2048 Jun 16 11:58 dtb
-
@wildcat_paris
Answering your questions:
1) No, I have the original one based on HardKernel Ubuntu distro which is 2012.07
2) No idea what this is. Do you mean the tsz.bin /bl1/bl2? For what is this good or necessary?
3) Yes, /dev/mmcblk0p1 is starting at 4096.
I didn't see any new mention on ODROID Forum regarding newer U-Boot to use with mainline kernel.
I tested 4.6.X, 4.7.rc-2, rc-3. I build directly on XU4. It's quicker.
-
@wildcat_paris Trying to compile next branch (4.2.X) with Armbian tools, I want to send this pull but I realized that even the compilation doesn't break, it doesn't work the created image out of the box and unfortunately, minor tunnings in boot.ini, etc/fstab are necessary to boot the image.
-
@wildcat_paris Thanks for your update. I'm reading very interesting your link and motivated @Shuah for share her progress with the XU4 community.
Update 13. Juni: I built the Kernel 4.7.0-rc2-next following the guides from @ummidelb and @shuah
The main problem that I had is that the SD Card device numbering for mmcblk0 changed to mmcblk1 (probably NAND device is now mmclbk0?) and therefore it was necessary to use UUID in u-boot environment variables and in /etc/fstab. Moreover I had a Hardkernel Ubuntu Image wich had 3.10.84 updated by hardkernel scripts until 3.10.96 with Xenial. After that I put on the top the ARMBIAN Kernel 3.10.110. The u-boot environment variable had to be changed to the original one from Hardkernel:
setenv bootrootfs "console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes" ... ... setenv bootcmd "fatload mmc 0:1 0x40008000 zImage_next; fatload mmc 0:1 0x42000000 uInitrd-4.7.0-rc2-next-20160609; fatload mmc 0:1 0x44000000 exynos5422-odroidxu4_next.dtb; bootz 0x40008000 0x42000000 0x44000000"
But because the HDMI is broken and no serial UART available atm (german reseller has no more and I didn't want to order once again from Korea..) it was difficult to debug when it was not booting.
I enabled USB_CONFIG_UAS=y, but didn't work out the box. Probably patches are necessary, like other to fix the CPUs order, the ethernet which is attached to the USB2.0 instead of 5Gbps, etc.
-
right, he uses bzImage instead zImage and he doesn't use initramfs. let's see...
update 4.Juni 2006: Didn't work like described by @Luisbg. If you try by yourself, try in .config with UAS activated.
CONFIG_USB_UAS=y
-
@wildcats_paris are you aware of this?
http://forum.odroid.com/viewtopic.php?f=95&t=18034&start=150
-
On my Banana Pro SATA works fine with the help of some userpatches. Take a look at the end of the thread http://forum.armbian.com/index.php/topic/836-bananapro-wifi-armbian-5-kernel-tracebacks/. I have attached my userpatches there.
Banana Pro uses a different DTS file, which is not as well maintained as those for the Banana Pi. Therefore, I have made a patch for sun7i-a20-bananapro.dts which this updated and solves some problems with the power supply.
Viele Gruesse
Axel
Axel, ich bin Dir sehr dankbar! This did the trick. SATA is recogniced again and the patch considered the LEDs using Armbian_5.07 and Bananapro 4.5.2. Du solltest über die patches Igor benachrichtigen. Now I have wlan! (which I didn't use, but anyhow...) Thank you very much again!. BTW, I have short questions that you maybe could answer:
- Do you have zram in use? if yes, how much and prio/swapiness?
- Do you have tweaked rc.local? Possible to share?
- Do you have tweaked sysctl.con?
(maybe paste and bin?)
Schöne Grüße
Solution: Use the offered userpatches from Axel in earlier post to get recogniced SATA in Banana Pro; compile with them.
-
There are problems with U-boot. We fix back to 2016.01 where gmac problems are not present, but I guess we have SATA problems. I think we need to enable this patch back on:
https://github.com/igorpecovnik/lib/blob/master/patch/u-boot/u-boot-next/bananapi-enable-ldo4.patch
or move to current dev branch, which could have some other hidden bugs.
Thanks Igor. Do you mean to insert the mentioned ldo4 patch inside /userpatches/u-boot/u-boot-next/ and compile again? I have done this right now, but SATA is still not recogniced. Some other patch or idea? (I didn't cleaned last compilation, but I think it's OK)
-
I runned once again in same isssue. After compiling last image for bananapro and copying these to the sd card, the sata device not appears anymore. I changed the bananapro with the bananapi dtb file, but this doesn't help.
root@bananapipro:~# dpkg -l | grep next ii linux-dtb-next-sunxi 5.07 armhf Linux DTB, version 4.5.1-sunxi ii linux-firmware-image-next-sunxi 5.07 armhf Linux kernel firmware, version 4.5.1-sunxi ii linux-headers-next-sunxi 5.07 armhf Linux kernel headers for 4.5.1-sunxi on armhf ii linux-image-next-sunxi 5.07 armhf Linux kernel, version 4.5.1-sunxi ii linux-jessie-root-next-bananapipro 5.07 armhf Root file system tweaks for bananapipro ii linux-u-boot-bananapipro-next 5.07 armhf Uboot loader 2016.01 root@bananapipro:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 14.9G 0 disk └─mmcblk0p1 179:1 0 14.9G 0 part / root@bananapipro:~# dmesg | grep ata [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Memory: 1007252K/1046952K available (9236K kernel code, 664K rwdata, 2164K rodata, 636K init, 308K bss, 23316K reserved, 16384K cma-reserved, 244136K highmem) .data : 0xc0bca000 - 0xc0c702a4 ( 665 kB) [ 3.258555] libata version 3.00 loaded. [ 3.591733] ahci-sunxi 1c18000.sata: PHY power up failed. [ 3.591812] ahci-sunxi: probe of 1c18000.sata failed with error -5 [ 4.025162] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 4.952900] systemd[1]: Starting Increase datagram queue length... [ 5.064922] systemd[1]: Started Increase datagram queue length. [ 6.644417] EXT4-fs (mmcblk0p1): re-mounted. Opts: data=writeback,commit=600,errors=remount-ro
Do you know what to do? Ideas?
Thanks
-
https://github.com/igorpecovnik/lib/commit/6f58b4041385bf4d3e0eca6926b00132998698eb
This commit should prevent this problem on the build level.
Yes, this was what I mean in the earlier post. Thanks for the info because I thought that it was my build environment.
-
I think this could be succesfully catalogued like as solved.
Summary: Errors(1) on SD-Card which lies to read-only filesystem on first boot and as a result new user an not be created.
(1) Errors due to faulty compilation image.
SBC consumption/performance comparisons
in Reviews, Tutorials, Hardware hacks
Posted
Really appreciated that you always share your observations.