Now added a release to the repository. It has 2 pre-build images for try-out.
1 Like
Hello, I’ve tried SD and EMMC images and in both no wifi interfaces:
‘iw dev’ or ‘ip link show’ shows nothing like wlan0 or wlp3s0b1 …
also, the same with image ‘debian buster with new bootchain and linux 5.10’…
but image ‘Ubuntu 18.04 with kernel 5.4.0’ works.
also ‘dmesg |grep mt76’ shows no errors
That is really strange that in both images, from buildR64ubuntu and in the 5.10 debian image, it doesn’t work.
I have only tested the images with nothing in the pcie slots and with wifi of the board itself only 1 antenna on the WF0 connector.
What version of the board do you have?
Btw, buildR64ubuntu needs a fix still to load eeprom settings from file. The wifi therefore isn’t fully initiated correctly. But anyway, wlan0 should be there and works with limited range.
I’m not sure i have included firmware in the new image
the new R64 with mt7615 module, from this May.
I like these smooth and quick images. also it would be good to decrease idle tempreachar for easy passive cooling.
Could be firmware files are missing in my images as well. The script once in a while skipped them on error. Need to update the script there… Need to check if the files are on the image later…
What is it you like to change about the temperature? There is a separate topic in this forum for that issue…
in all images there is a problem, a high idle cpu temperature. and even higher temp on MT7531 switch that ends up with serial minicom hangs.
Latest changes:
Firmware is downloaded in a more robust way.
Wifi eeprom is now loaded. Wifi range has improved a lot.
Changes are in the script only for now. There will not be a new release image at every change. If you like to use the buildR64ubuntu project, I suggest using the script. It will also help applying future changes to existing installations.
1 Like
how much is your idle temp?
for serial problem you can try this:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
I can’t monitor sensors because this is ubuntu-18.04.3-bpi-r64-5.4 I touch heat-sink that become a lot hotter then CPU. Thank you for reference.
Does this also not work?
# cat /sys/class/thermal/thermal_zone0/temp
Have you tried using another kernel e.g. 5.10 from my repo?
ubuntu-18.04.3-bpi-r64-5.4 idle temps:
[root@r64 ~]# cat /sys/class/thermal/thermal_zone0/temp
58300
58100
and stay at this level
On this ubontu I didn’t experiment with kernels but this is good idea, thanks
Have you looked if your system is really idle on both cpu?
connected to serial, no wifi or ssh.
after 15min:
[root@r64 ~]# cat /sys/class/thermal/thermal_zone0/temp
55100
all the time this ps:
[root@r64 ~]# ps ax -o pid,rss,pcpu,comm --sort -pcpu|less
PID RSS %CPU COMMAND
1 8004 0.3 systemd
1380 5380 0.2 bash
1758 0 0.2 kworker/1:3-eve
16 0 0.1 kworker/1:0-eve
1588 0 0.1 kworker/1:1-eve
1712 0 0.1 kworker/0:3-eve
2 0 0.0 kthreadd
3 0 0.0 rcu_gp
4 0 0.0 rcu_par_gp
6 0 0.0 kworker/0:0H-mm
7 0 0.0 kworker/u4:0-ev
8 0 0.0 mm_percpu_wq
9 0 0.0 ksoftirqd/0
10 0 0.0 rcu_preempt
11 0 0.0 migration/0
12 0 0.0 cpuhp/0
13 0 0.0 cpuhp/1
14 0 0.0 migration/1
15 0 0.0 ksoftirqd/1
18 0 0.0 kdevtmpfs
19 0 0.0 netns
20 0 0.0 rcu_tasks_kthre
Maybe you can use the script of which this topic is about and move on to kernel 5.12. many issues were solved, so a good chance this issue is solved as well. You could at least try the image and compare idle temperature after 15 minutes.
Major update 31-08-2021
- Able to install Arch-Linux, it is also now the default. Guess the repo needs a name change.
- Using systemd’s dhcp server.
- Using systemd-resolved
- Many other small changes
As the image uses the newest kernels, I wanted to use the newest systemd and iproute2. With Arch-Linux it is easier to keep these up to date to a very new version. Arch-Linux uses rolling updates… I like it so much, it is now the default.
ATF mtksoc branch was fixed in a squashed commit, so I never saw it had a new commit which fixed the rebooting issue. Default branch is now the newest mtksoc branch of ATF.
U-Boot has a bug since 2021-04-rc1 in clk-uclass.c with log_ret(). Applied a patch so now the newest U-Boot is used.
So both issues are fixed? Are my repos affected (do i need to update/patch it)?
Atf you can just use the mtksoc branch, the fix is in that repo.
U-boot (mainline) needs a fix.
Mtksoc from my repo is fixed? I took it sometime from vendor repo,so i do not know if it’s last version
For uboot it is this patch? Imho it should be fixed upstream.could you send a patch to ML?