You can install my kernel package to manjaro, but you’ll also need to tweak some settings for bootloader/kernel(config.txt, cmdline.txt, etc.). I’m not sure if Manjaro’s image uses u-boot like what archlinuxarm do by default, that will be a different story.
To check if bluetooth hardware is recognized, try with command rfkill and it’ll probably list all recognized wireless interfaces(including WiFi), and there should be 2(bluetooth/hci0, wlan/phy0). You might also want to try the firmware files for wireless chip provided by firmware-raspberrypi(archlinuxarm exclusive package). Also check your bluetooth.service, it should be up and running.
I don’t have that system on SD anymore, I’m just trying and trying. Either way, rfkill returned only WiFi, no BT at all, and bluetooth.service was enabled and up, but I do remember now that gave some “errors”, like 10 lines or so about unsupported mods or something like that. Sorry I can’t remember it now. I will try out the firmware you mention next time then.
Manjaro thing; trying it right now haha.
EDIT: I’ve downloaded the Manjaro ARM Sway RPI and flashed on an USB just to see.
config.txt
# See /boot/overlays/README for all available options
# Uncomment some or all of these to enable optional Hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Run in 64bit mode
arm_64bit=1
# Auto load correct initramfs files if found
auto_initramfs=1
# Run as fast as the firmware/board allows
arm_boost=1
# Disable compensation for displays with overscan
disable_overscan=1
# Enable sound
dtparam=audio=on
# Uncomment if no sound thru hdmi
#hdmi_drive=2
# Auto load overlays for detected cameras
camera_auto_detect=1
# Auto load overlays for detected DSI displays
display_auto_detect=1
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
# For pi4's and above boards uncomment next line & Comment out above line
#dtoverlay=vc4-kms-v3d,cma-512
max_framebuffers=2
# Don't have the firmware create an initial video= setting in cmdline.txt
# Use the kernel default instead
#disable_fw_kms_setup=1
# Disable rainbow screen at boot
disable_splash=1
# RPi 5B/4B/400 ONLY
# For 4k content @ 60 Hz refresh rate, uncomment hdmi_enable_4kp60=1
#hdmi_enable_4kp60=1
# If video breaks with hdmi_enable_4kp60=1 uncomment
#force_turbo=1
[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller
# This line should be remoed if the legacy DWC2 controller is required
otg_mode=1
[all]
console=serial0,115200 shouldn’t be there in your cmdline.txt. Serial0 is used to communicate with the bluetooth part, and bluetooth won’t work if you are using it for console. Remove it or change it to serial1.
Oh no sorry, that is the config and cmdline from the Manjaro ARM Sway img I downloaded, just so if you were curious about it.
I flashed again the one you built, and it doesn’t work either. In neither one had no “console=…” in cmdline, but it’s just like if the hardware had no BT at all from the SO point of view. It’s super weird, but really can’t seem to find any solution at all. I don’t remember tho if with the one yatli made which I used too before (6.1.idk) worked. I have seen on internet that for some reason RPI4 & BT & Arch don’t bechave really well.
Yep, working 100% now on your img. Have to build it again and try it. Good timing tho! I was just going to migrate from SD to internal USB to see how it works. Ty!
So, if I want to see what are the differences in one dtbo and another, can I use diff or something like that? If I open the files in any text editor just hundreds of number lines, which I guess it’s normal.
I’ll publish the code very soon. Basically it disables some gpio configurations and power for external wireless chip compared to the previous version. I think my gpio configurations for CM3 and CM4S overwrite the good default ones for CM4, causing unsuitable pins used for BT interface.
If you want to compare the blobs, you need to decompile the files using dtc and then compare the clear text.
Shout-out to @PotatoMania, my Arch on uConsole is a success!
I set up my partitions using the guide for the RPi 4 here; then the pacstrap, the custom packages, the fstab, and the configs from the scripts here; and the user account manually using arch-chroot.
I decided I don’t need gdm right away, so I didn’t enable the service. I can even simply disable NetworkManager, ModemManager, and bluetooth when I don’t need them. Assuming those, running just a vanilla console, I feel I can easily hit the exceptional battery life this device can promise.
My Bluetooth is missing as well. But I believe this matter has been fixed. And that my Git copy isn’t the latest. So I’ll just make it up as I go.
Hi~ @mterencelao Glad to hear your success! Enjoy customizing Arch for your specific need!
If I remember it right, it takes about 8 seconds for CM4 to finish booting with my configuration, and the same thing takes around 30 seconds on a CM3.
BTW I use sway and autologin instead of some DEs with gdm/sddm/lightdm etc. for a graphical interface(at the cost of a portion of security, it’s not my sensitive device anyway).
Thanks! I’m gradually building my install, as of the moment.
For some reason, GNOME Web (epiphany) recoils upon finding media in the web page. I understand, however, that the browser achieves playback through the gstreamer suite. It also has a habit of crashing. I guess I’ll limit my use of that browser and use firefox for the meantime.
4G module’s “power button" is connected to the gpios, herefore a script is required to enable the module, and that is the clockworkpi’s way to do it(read their doc). After all it’s just a USB modem with power button connected to the pi’s gpio. I sold mine BTW because I made myself a custom expansion card.
I’m pretty sure I’m among the very first ones who successfully adapted the kernel code and upgraded to 6.x, when I was on CM3. I’ve split the official patch, fixed the panel issue on 6.x kernel, and written a simple kernel driver to avoid a python script polling the state of 3.5mm jack. I just don’t have the motivation to follow every major kernel update. I think I’ve organized the code well so that if someone need it, it’s easy to pick or inspect the changes.
Firefox on pi4 and up in a wayland session features hardware accelerated rendering(but not for video decoding). See about:support and you’ll find Compositing: WebRender(if software appears after WebRender, then you may need further configuration).
For hardware video decode, you need a custom ffmpeg(rpi-ffmpeg) with necessary implementations.
In that case, I leave the maintenance development to more capable hands. I have nearly zero experience in building packages for Arch. And I don’t have the same breadth of cores to test the kernel against. Only ever fiddled with AUR and PKGBUILDS so far.
What do you mean? If you want your CPU to run at performance mode all the time, try set the cpu governor with a cmdline parameter(in cmdline.txt), or use a userspace program to change it on boot. I’ll not provide more detail. However, you can find more on Arch wiki.
