I am attempting to use the linux-rc3 kernel on a fresh Arch Arm install. I don’t think that should have any affect at this point in the boot process, but maybe.
Doing a diff on the configs was my next step, but that must wait until this evening.
Is anyone aware if any of these recent developments will allow booting from MVMe m.2 drive on USB 3? Previously I was only able to boot from USB 2 ports.
I compared my list of modules of things that I had to add and they are exactly the same in linux-rc.
Then it must be something on my end, thank you for looking into it.
@Darksky I must be doing something wrong. I installed 2107 Plasma edition to an SD card and updated it to arm-unstable. I install linux-rc and linux-rc-headers. I then copy bcm2711-rpi-4-b.dtb to /boot. I then edit config.txt and point the kernel at Image and comment out the dtoverlay=vc4-fkms-v3d. I modify the mkinitcpio.conf to switch from udev to systemd. Finally remake the initramfs.
Reboot… the kernel crashes trying to sync the CPUs.
What am I missing?
Did you use the cmdline.txt I posted above. Comment out all vc4 stuff in config.txt.
I do not know if modifying the mkinitcpio.conf to switch from udev to systemd will affect things or not. I have also in the past seen issues with enabling the initrd with upstream kernel.
Ah, you did not use an initrd? I was loading one, I’ll try it this evening without one.
As for cmdline.txt, I think I just changed root=partuuid=. But I may not have removed the other parameters. I’ll try that too.
I downloaded and installed the Plasma image here and it booted just fine after installing the latest linux-rc3 kernel.
It booted ok with or with out the stock initrd. I do not know what it will do with your custom initrd.
Steps (I did not update the 2 raspberrypi-bootloader packages)
Installed the latest linux-rc/linux-rc-headers packages from unstable branch
Copied existing cmdline.txt and config.txt to cmdline.txt-manjaro and config.txt-manjaro to have for backups:
Edited cmdline.txt
cmdline.txt (I left PARTUUID= as is)
root=PARTUUID=8b919108-02 rw rootwait console=ttyS1,115200 console=tty0 usbhid.mousepoll=8 audit=0
Edited config.txt:
config.txt (You may want to increase the gpu_mem=)
#un-comment for pi4
device_tree=dtbs/broadcom/bcm2711-rpi-4-b.dtb
#un-comment for pi400
#device_tree=dtbs/broadcom/bcm2711-rpi-400.dtb
gpu_mem=64
initramfs initramfs-linux.img followkernel
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
To uninstall the linux-rc upstream kernel and go back to your previous linux-rpi kernel you were using:
sudo pacman -S linux-rpi4 linux-rpi4-headers
sudo cp /boot/cmdline.txt-manjaro /boot/cmdline.txt
sudo cp /boot/config.txt-manjaro /boot/config.txt
reboot
Edited to reflect switching kernels when installing the linux-rc upstream kernel and back to manjaro-arm kernel by installing their packages to make it easier.
Weird. I could swear that I tried exactly as you have done, but I will give it another go this afternoon/evening. It helps to see your example setup and results, thank you. Maybe it is a systemd init issue… so I will give udev another try and follow your example exactly.
In my testing all seems to work except I tried the kodi-rpi and it will not play any video. I think it will probably play the kodi X11 version in the repo (with no hardware decoding) but when I tried it the package is broke missing files so will have to wait for it to be fixed.
Systemd works fine, it was my cmdline.txt. I was using the version as supplied by the initial installation. I am not sure which parameter(s) causes the problem, I may investigate that further, but not sure if it is worth the effort. Thanks again for setting me straight.
I guess there is a typo : the first word should be Sudo
PiOS had sata drivers supported, does manjaro build support?
Thanks. Corrected.
Use their kernel config as a base so whatever they have enabled
we have enabled.
I just noticed a new overlay: vc4-fkms-v3d-pi4.dtbo. I guess we should be using it instead, if we have rpi4?
I am not sure of when it arrived… but it is included with 5.10.52 and does not seem to exist with 5.10.46.
I noticed that yesterday merging 2 trees for a kernel I maintain for satellite use. I have not find anything on it yet. I was hoping it might help with the -rc kernel booting with fkms / v3d rendering but it did not.
It is exactly the same as the vc4-fkms-v3d.dtbo except for the “compatible” line (with 5.10.52):
compatible = "brcm,bcm2835"
versus
compatible = "brcm,bcm2711"
for the rpi4.
Edit: But it appears they will be different very soon someday.
vc4-fkms-v3d
vc4-fkms-v3d-pi4
I’m not replingbto you it just takes forever to scroll all the way down so I’m using this shortcut to get to relevant posts relative to today’s date
While not specifically pertaining to the RPi, there is good news concerning a new release of Xorg. Let’s hope this work continues. While Wayland works in some situations and configurations, it does not work for all… wake me when it can.
I have been seeing disable_fw_kms_setup=1 popping up lately, and have wondered what it does. According to a small post in a bug report, it will at least result in the removal of the video=HDMI-1... entry in the kernel command line.
Not that this fixes any particular issue I have, but expect it might be helpful or at least informative to others that might be battling video issues.