Hello Vince,
I have used your input to get my Odorid Xu4 to both blink and use
all 8 cores now. Thanks for the work you did to get that working.
However, unlike Andreas, my Driver r8152 still shows 480M. I am
using the latest 4.17.18-200 kernel. See my output that follows:
Last login: Tue Aug 28 10:49:22 2018
[root@myodroid-wireless ~]#
[root@myodroid-wireless ~]#
[root@myodroid-wireless ~]# uname -a
Linux myodroid-wireless 4.17.18-200.fc28.armv7hl #1 SMP Wed Aug
22 20:36:45 UTC 2018 armv7l armv7l armv7l GNU/Linux
[root@myodroid-wireless ~]#
[root@myodroid-wireless ~]# lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class,
Driver=r8152, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p,
5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p,
480M
|__ Port 2: Dev 6, If 0, Class=Hub,
Driver=hub/4p, 12M
|__ Port 4: Dev 9, If 2, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 9, If 0, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 9, If 1, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 8, If 1, Class=Wireless,
Driver=btusb, 12M
|__ Port 2: Dev 8, If 0, Class=Wireless,
Driver=btusb, 12M
|__ Port 1: Dev 7, If 2, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 7, If 0, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 7, If 1, Class=Human
Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=Vendor Specific Class,
Driver=rtl8192cu, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p,
12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p,
480M
[root@myodroid-wireless ~]#
Also, it looks that although 8 cores are now being used, the cpu
frequency is set to "ondemand" governor at 700 MHz. You can change
that to 1.3 GHz by changing the governor to "performance". But I is
not persistent between boots. Perhaps someone can provide some
assistance in how to make it persistent between boots. Anyway, here
is what I did to change the governor.
[root@myodroid-wireless ~]# cpupower frequency-info
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by
software: 0 1 2 3
maximum transition latency: 154 us
hardware limits: 200 MHz - 1.30 GHz
available frequency steps: 200 MHz, 300 MHz, 400 MHz, 500
MHz, 600 MHz, 700 MHz, 800 MHz, 900 MHz, 1000 MHz, 1.10 GHz,
1.20 GHz, 1.30 GHz
available cpufreq governors: conservative userspace powersave
ondemand performance schedutil
current policy: frequency should be within 200 MHz and 1.30
GHz.
The governor "ondemand" may decide which speed
to use
within this range.
current CPU frequency: 700 MHz (asserted by call to hardware)
[root@myodroid-wireless ~]#
[root@myodroid-wireless ~]#
[root@myodroid-wireless ~]# cpupower frequency-info --governors
analyzing CPU 0:
available cpufreq governors: conservative userspace powersave
ondemand performance schedutil
[root@myodroid-wireless ~]# cpupower frequency-set --governor
performance
Setting cpu: 0
Setting cpu: 1
Setting cpu: 2
Setting cpu: 3
Setting cpu: 4
Setting cpu: 5
Setting cpu: 6
Setting cpu: 7
[root@myodroid-wireless ~]# cpupower frequency-info
analyzing CPU 0:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by
software: 0 1 2 3
maximum transition latency: 154 us
hardware limits: 200 MHz - 1.30 GHz
available frequency steps: 200 MHz, 300 MHz, 400 MHz, 500
MHz, 600 MHz, 700 MHz, 800 MHz, 900 MHz, 1000 MHz, 1.10 GHz,
1.20 GHz, 1.30 GHz
available cpufreq governors: conservative userspace powersave
ondemand performance schedutil
current policy: frequency should be within 200 MHz and 1.30
GHz.
The governor "performance" may decide which
speed to use
within this range.
current CPU frequency: 1.30 GHz (asserted by call to hardware)
So, although we might be able to get to 1.30 GHz, the A15 Cortex
frequency is suppose to be 2.0 GHz and the A7 Cortex process 1.4
GHz.
Does anyone know if I am missing something here? I will check to
see what Ubuntu 18.04 for the Odroid XU4 and report back later.
Stewart
Am
2018-08-27 10:41, schrieb Vince Geze:
---snip---
Hello Vince,
after newest kernel update and poweroff for 1 minute:
[root@odroidh2 ~]# lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class,
Driver=r8152, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
5000M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas,
5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p,
480M
/: Bus 02.Port 1: Dev 1, Class=root_hub,
Driver=exynos-ehci/3p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub,
Driver=exynos-ohci/3p, 12M
[root@odroidh2 ~]# uname -a
Linux odroidh2.reschke.lan 4.17.17-200.fc28.armv7hl #1 SMP Mon
Aug 20
17:31:32 UTC 2018 armv7l armv7l armv7l GNU/Linux
[root@odroidh2 ~]#
Greetings
Andreas
Hi Andreas,
Thanks for the feedback, looks like both storage and Ethernet
are
connected as USB3 now.
Out of curiosity, are you running from SD or eMMC? I'm still
using SD
for testing, but once I got everything covered I'd like to
switch to
eMMC.
Best regards,
Vince
Hello Vince,
this system is running only with /boot from SD, all other
filesystems are on SSD.
I will now update my Odroid XU4, this should also work. I hope, I
can take this in the near future as my working place.
Greetings
Andreas
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
|
