raspberrypi-bootloader / raspberrypi-bootloader-x 20201016-1 in the stable branch
Another way to make it work is use the bcm2711 .dtb from the linux-rpi4-mainline (kernel 5.9) package and then use the latest raspberrypi-bootloader / raspberrypi-bootloader-x packages in the unstable branch.
Of all of my options, including continuing to use a 4GB Pi, that one I think, sounds most appealing.
I lately been keeping the kernel 5.9 .dtb in /boot and putting -sav extension on it so all I have to do is copy it over after installing the 5.10 kernel.
1 Like
they fixed usb issue, rc3 need rebuild.
Using the stable version of the device tree is working on my 8GB.
It looks lke they did. I will compile it tomorrow.
From looking at the commit it is concerning that they did not pay any attention to me when I opened an issue 2 weeks ago and wanted me to close it. I even in my last post told them where the issue was. They only did something when some one in their forum mentioned it.
Scroll down to the last post to see where I told them where the issue was:
Anyway we will see tomorrow what the new compile will do.
I have another issue with the latest linux-rpi4 released yesterday where bluetooth is not working right. I was reluctant to create an issue with it because they seem to not want to pay attention lately. What is the use of filing an issue?
1 Like
I changed my mind and it is compiling now.
can you share PKGBUILD?
I will after the kernel builds/tested/pushed. All of my devices are tied up in a distcc farm compiling.
No V3D at the moment, I have mesa-git installed, and I reinstalled it just to make sure.
$ glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
$ glxgears
Error: couldn't get an RGB, Double-buffered visual
So currently Xorg is falling back to the fb driver, I do not have fbturbo installed.
Edit: The kernel modules seem to be loaded.
$ lsmod | grep vc
bcm2835_mmal_vchiq 32768 3 bcm2835_codec,bcm2835_v4l2,bcm2835_isp
vc_sm_cma 36864 2 bcm2835_mmal_vchiq,bcm2835_isp
vc4 270336 8
cec 53248 1 vc4
drm_kms_helper 253952 3 vc4
snd_soc_core 241664 1 vc4
snd_pcm 126976 5 vc4,snd_bcm2835,snd_compress,snd_soc_core,snd_pcm_dmaengine
drm 561152 7 gpu_sched,drm_kms_helper,v3d,vc4
$ lsmod | grep v3d
v3d 81920 1
gpu_sched 45056 1 v3d
drm 561152 7 gpu_sched,drm_kms_helper,v3d,vc4Try going back to mesa.
Will do, but I bet it is due to the older dtb.
Edit: But rolling back did work, V3D is back.
The 5.10-rc3 usb issue is fixed and the new kernel/headers packaged are pushed to the unstable branch when the mirrors sync. They will have a -2 suffix.
linux-rpi4-rc 5.10.rc3-2
linux-rpi4-rc-headers 5.10.rc3-2
Projects · manjaro-arm / packages / core / linux-rpi4-rc · GitLab
1 Like
My update to rc3-2 went smoothly… thank you very much for all of the hard work. And I tried mesa-git again but it still does not work.
mesa-git is a work in progress and sometimes buggy.
No worries… I am just sort of yammering in the forum. 
But maybe it saves someone else the effort.
There are some news from the 5.9 kernel :
firmware: raspberrypi: Add support for tryonce reboot flag
Define a new mailbox (SET_REBOOT_FLAGS) which may be used to
pass optional flags to the Raspberry Pi firmware that changes
the behaviour of the bootloader and firmware during a reboot.
Currently this just defines the ‘tryboot’ flag which causes
the firmware to load tryboot.txt instead config.txt. This
alternate configuration file can be used to specify the
path of an alternate firmware and kernels allowing a fallback
mechanism to be implemented for OS upgrades.
And the 5.9.8 is out from raspberry team.
I remembered and revisted wireguard today and got it going. I also added using iptables to enable masquerading so I could connect to my home server via my phone and have internet:
[Interface]
Address = 10.0.0.1/24
ListenPort = 51820
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
PostUp = iptables -A FORWARD -o %i -j ACCEPT
PostDown = iptables -D FORWARD -o %i -j ACCEPT
[Peer]
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
AllowedIPs = 10.0.0.2/24
Then enable IP forwarding so I could test it:
sudo sysctl net.ipv4.ip_forward=1