Ah, I am referring to linux-rc (vanilla), you are referring to linux-rpi4-rc.
1 Like
You said you’re using rpi4in a previous post? How are you using linux-rc?
Linux-rc is aarch64
Linux-rpi4 is raspberry pi4 64 bit kernel?
What the what?
Which is better?
Both kernels will boot and run. But with the vanilla kernel, currently v3d and headphones do not work. The rpi4 kernels are better all-around, but the linux-rc runs pretty well and has use cases.
2 Likes
Yah but now I tried aarch64 one and my system doesn’t boot… Staring at a blank screen… I don’t have a backup
Ah there we go. Manjaro on the sdcard to the rescue
So if I just open the config.text and mute the dtovetlay with a hashtag to disable fkms- v3d it will boot aarch64?
OK remind me again what I install to get manjaro-chroot on my xfce sdcard install?
Well linux-rc didn’t boot for me but I’ll get my desktop back in a little while I suppose. I’m using my pi4 as a desktop got general purposes I don’t need use cases of aarch64 of linux-rc
The interesting thing is that I was on 5.15 rc but never upgraded to 5.15 non rc when 5.15 went out of rc.
I update linux-rc in unstable branch, when there is either an update or a change I want to put in it. That is pretty often inj the RC cycle.
1 Like
@thesesocalledflowers The linux-rc upstream kernel will boot just fine with the pi4 but it requires some config adjustments after installing it and before rebooting.
Disable all fkms/kms overlays in config.txt. Upstream does not have V3D support or overlays. Also in config.txt specify the path to upstream’s kernel and it’s devicetree. You need to set the gpu_mem= in config.txt. Most important you will have to have xf86-video-fbdev installed if you do not.
sudo pacman -S xf86-video-fbdev
Config.txt:
gpu_mem=512
device_tree=dtbs/broadcom/bcm2711-rpi-4-b.dtb
kernel=Image
#dtoverlay=vc4-fkms-v3d,cma-512
#dtoverlay=vc4-kms-v3d,cma-512
#max_framebuffers=2
The cmdline.txt also needs to be a little different (make a backup of your original) Get the PARTUUID below from your original cmdline.txt:
[ray@pi4 ~]$ cat /boot/cmdline.txt
root=PARTUUID=your-drive-partuuid-here rw rootwait console=ttyS1,115200 console=tty0 snd_bcm2835.enable_headphones=1 usbhid.mousepoll=8 audit=0
I have not released the latest linux-rpi4-rc yet as kms/fkms is broke. You can install the latest linux-rpi4 or latest linux-rpi4 to be current. The linux-rpi4-5.15-rc7 kernel is very old in the repo. You can keep up with what is what with the latest pi kernels here:
https://forum.manjaro.org/t/raspberry-pi-kernels-2-0/84885/2
Notice the cmdline.txt I posted above (snd_bcm2835.enable_headphones=1). The headhones does not get picked up for some reason with the upstream kernel in inxi but it will be there in aplay -l and Pulse Audio Settings. It may be a little flaky hot switching back and forth but the headphones will work.
I have noticed that pulseaudio was not working in the past with the upstream kernel but uninstalling it and installing piprwire seems to be ok.
All in all everything is working including bluetooth with the upstream kernel except V3D which it does not support. Of course some pi specific proprietary add on devices will not work also.
1 Like
Thanks, I see the headphones now when booting with firmware, but still not seeing it via uefi.
When you boot into linux-rc next time, would you try running sudo i2cdetect -y 1
When booting via firmware and the linux-rc .dtb, I get this mess:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: -- -- -- -- -- -- -- -- 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77
1 Like
I get the exact same thing.
1 Like
Ah, well I guess that is both good news and bad news. It means gpio is indeed broken and not just some config issue on my end.
So no dtoverlays use at all. Not even with case fans?
Overlays work, but none are supplied with the linux-rc kernel.
1 Like
The video v3d overlays will not work as they are not supported. The upstream kernel install will remove the overlays directory so you will have to supply your own back.
This is interesting:[ray@pi4 ~]$ sudo i2cdetect -F 1
Functionalities implemented by /dev/i2c-1:
I2C yes
SMBus Quick Command yes
SMBus Send Byte yes
SMBus Receive Byte yes
SMBus Write Byte yes
SMBus Read Byte yes
SMBus Write Word yes
SMBus Read Word yes
SMBus Process Call yes
SMBus Block Write yes
SMBus Block Read no
SMBus Block Process Call no
SMBus PEC yes
I2C Block Write yes
I2C Block Read yes
1 Like
Lines 3-6 delete? Or just 3-5?
Lines 13-15 delete for sure.
Bad link
1 Like
Tyvm!!
Ah, yes… no doubt other overlays are not supported. I know i2c-rtc supplied by the rpi kernel works, and an overlay for my fan works. So I should say overlays are supported in general, but may or may not be supported on an individual basis.
#See /boot/overlays/README for all available options
#gpu_mem=64
gpu_mem=512
initramfs initramfs-linux.img followkernel
device_tree=dtbs/broadcom/bcm2711-rpi-4-b.dtb
#kernel=kernel8.img
kernel=Image
arm_64bit=1
disable_overscan=1
#enable sound
dtparam=audio=on
#hdmi_drive=2
#enable vc4
#dtoverlay=vc4-fkms-v3d
#max_framebuffers=2
disable_splash=1
#Make sure your argonone .dtbo's are in /boot/overlays/ & cross your fingers if supported by kernel
dtoverlay=argonone,hystersis=5
dtparam=fantemp0=35,fanspeed0=33
dtparam=fantemp1=40,fanspeed1=67
dtparam=fantemp2=45,fanspeed2=100
Be sure to change cmdline.txt also.
1 Like
OK I thought I did all that right but I got a kernel panic
You did not provide any info with what you did.
ls /boot would be nice also
1 Like
Double checking now for typos