the install script has bug long time ago.
core.db failed to download
extra.db failed to download
Easy as pie with no calmares to deal with.
git clone https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer
cd manjaro-arm-installer
chmod +x manjaro-arm-installer
sudo bash ./manjaro-arm-installer (Use Default stable branch)
sudo bash ./manjaro-arm-installer arm-testing (Use testing branch)
sudo bash ./manjaro-arm-installer arm-unstable (Use unstable branch)
I just used it and had no issues making a new sdcard install here. Sounds like you need to clean out some old local files you have. I forget what directories they are, I am busy right now with kernel 6.13-rc1.
so i reckon this “scheduler” is a new addition to raspberry pi kernel which can be utilized for performance gain? But we need to install scx_scheduler to utilize it?
That is the idea. for it. I think each user needs to make up their own mind with it according to their own use case. From reading it appears that it is supposed to handle multitasking more smoother and games will have better performance. From my testing things are a little bit better but with arm and a little bit better here and there can add up overall.
The future kernels v6.12 and up will have scx-scheduler has a depend so it will get installed with the kernels. The v6.6 kernel will not be sched_ext capable.
The new kernels are on hold right now until I hear back from RPi. It will not boot into a display manager right now. I have found something wrong with the new .dtb. It boots fine with an older .dtb.
Linux jellyfin 6.13.0-rc1-1-MANJARO-RPI5 #1 SMP PREEMPT Thu Dec 5 23:03:56 UTC 2024 aarch64 GNU/Linux
● scx.service - Start scx_scheduler
Loaded: loaded (/usr/lib/systemd/system/scx.service; enabled; preset: disabled)
Active: active (running) since Fri 2024-12-06 09:06:13 CST; 2h 20min ago
Invocation: 12056b6c882f464da5e00db7eb71e833
Main PID: 897 (scx_rusty)
Tasks: 14 (limit: 9025)
CPU: 10.212s
CGroup: /system.slice/scx.service
└─897 scx_rusty
You are really working hard on maintaining this, we appreaciate your efforts. Thanks. Manjaro ARM on RPI i would say sometimes feel much more hassle-free even when compared to their official RPIOS. KDE Plasma brings a lot of ease on itself but also arch (arch wiki), the aur repos, flatpak, this is a very nice overall package for anybody.
1 Like
ok, build manjaro-arm-installer from PiOS, work.
what is wrong with my OS?
Worked ok here. I built from git posted above. I don’t believe anyone is maintaing the package in our repo.
1 Like
Do we really need the manjaro arm installer for RPI? Or why do we need it? I flashed the image i downloaded from github and has been using it for some months now. Never had any major issues. I flashed it with RPI Imager. What does the manjaro arm installer do different?
PS: I had to download one of the “developer” builds for RPI5. I think the default latest release on github (still from 2023) doesn’t have the RPI-5 bootloader support to work on it. Dev builds come in the “unstable” branch, which is OK.
sorry, we talk about sway.img and it broken.
v6.12.3 is out
got scx-scheds-git-2 rebuild updated, what is change?
you should build 1.0.7 upload instead of git-build, hard work.
Yes it also has the issue like v6.13-rc1 with it’s newer .dtb. I make it work by using an older .dtb and it boots into the desktop with no issue.
[ray@jellyfin ~]$ neofetch
██████████████████ ████████ ray@jellyfin
██████████████████ ████████ ------------
██████████████████ ████████ OS: Manjaro ARM Linux aarch64
██████████████████ ████████ Host: Raspberry Pi 5 Model B Rev 1.0
████████ ████████ Kernel: 6.12.3-1-MANJARO-RPI5
████████ ████████ ████████ Uptime: 18 mins
████████ ████████ ████████ Packages: 1686 (pacman), 6 (flatpak), 16 (snap)
████████ ████████ ████████ Shell: bash 5.2.37
████████ ████████ ████████ Resolution: 1360x768
████████ ████████ ████████ DE: Xfce 4.18
████████ ████████ ████████ WM: Xfwm4
████████ ████████ ████████ WM Theme: Default
████████ ████████ ████████ Theme: Matcha-dark-sea [GTK2], Adwaita [GTK3]
████████ ████████ ████████ Icons: Papirus-Dark-Maia [GTK2], Adwaita [GTK3]
Terminal: xfce4-terminal
Terminal Font: Monospace 12
CPU: (4) @ 2.800GHz
Memory: 2293MiB / 8038MiB
A fix for arm to stop freezing due to low default memory allocation.
Do you plan to release it anyway ? Did you raise that issue to the RPI GitHub repo?
I created an issue last night. I do not expect to hear from them until Monday. They do very little on weekends. I do not want to push to the repo but will provide a link below.
Be sure you back up /boot/*.dtb some place then install the packages. Then copy back your saved *.dtb’s to /boot before you reboot. If you switch to the other new kernel then copy back the saved .dtb’s again before rebooting.
If you forget to copy back the saved .dtb’s do a CTRL-ALT-F2 then login and copy back the saved .dtb’s then reboot.
These kernels have sched_ext enabled.
Unpack tarball and install the kernel packages:
1 Like
ok, scx-scheds-git-1.0.6.r262-2 & linux-6.12.1-2, freeze.
edit,
which kernel should backup *.dtb or both?
Back up your current .dtbs and copy them back after you install the new kernels above. Keep the backup so you can copy back after you install the second kernel also. Always copy the older .dtb’s to /boot after you install any of the new kernels above.
6.13-rc2,
*bpftool: fix potential NULL pointer dereferencing in prog_dump()
*bpf: Remove unnecessary check when updating LPM trie
*bpf: Remove unnecessary kfree(im_node) in lpm_trie_update_elem
*bpf: Handle BPF_EXIST and BPF_NOEXIST for LPM trie
*bpf: Handle in-place update for full LPM trie correctly
*bpf: Fix exact match conditions in trie_get_next_key()
*bpf: Switch to bpf mem allocator for LPM trie
*bpf: Use raw_spinlock_t for LPM trie
*selftests/bpf: Move test_lpm_map.c to map_tests
*selftests/bpf: Add more test cases for LPM trie
*selftests/bpf: Add tests for iter arg check
*bpf: Zero index arg error string for dynptr and iter
*bpf: Don’t mark STACK_INVALID as STACK_MISC in mark_stack_slot_misc
*selftests/bpf: Add test for reading from STACK_INVALID slots
*selftests/bpf: Add test for narrow spill into 64-bit spilled scalar
*bpf: Ensure reg is PTR_TO_STACK in process_iter_arg
*bpf: Fix narrow scalar spill onto 64-bit spilled scalar slots
*bpf, lsm: Remove getlsmprop hooks BTF IDs
edit,
eeprom upadte, Enable NUMA by default.
edit2,
Pi 500 is coming…
Jeff has done a few videos on it. And a online Retailer has it as $155 Australian dollars. I don’t know if I will get it yet.
*sched/numa: fix memory leak due to the overwritten vma->numab_state
*drm/v3d: Enable Performance Counters before clearing them
*dma-buf: fix dma_fence_array_signaled v4
I have built v613-rc2 and I am having the same issue here. RPi got back to me a while ago and 6by9 said it is booting ok on his PiOS and asked for some more tests. I have a suspicion the issue might be with my VIZIO tv I am using for a monitor. I have had issues like this in the past off and on. I did decompile the new and old .dtb’s and compared them in meld and it looked like @50 changes in the diff between the 2.
● scx.service - Start scx_scheduler
Loaded: loaded (/usr/lib/systemd/system/scx.service; enabled; preset: disabled)
Active: active (running) since Mon 2024-12-09 07:28:22 CST; 4min 2s ago
Invocation: ef9b5d64204a48358813ce4bbfc036a0
Main PID: 905 (scx_rusty)
Tasks: 14 (limit: 9025)
CPU: 636ms
CGroup: /system.slice/scx.service
└─905 scx_rusty
Dec 09 07:28:22 jellyfin systemd[1]: Started Start scx_scheduler.
Dec 09 07:28:22 jellyfin bash[905]: 13:28:22 [INFO] Running scx_rusty (build ID: 1.0.7-g246fad9a-dirty aarch64-unknown-linux-gnu)
Dec 09 07:28:22 jellyfin bash[905]: 13:28:22 [INFO] NODE[00] mask= f
Dec 09 07:28:22 jellyfin bash[905]: 13:28:22 [INFO] DOM[00] mask= f
Dec 09 07:28:22 jellyfin bash[905]: 13:28:22 [INFO] Rusty scheduler started! Run `scx_rusty --monitor` for metrics.
Could I get some one here to install this kernel (using it’s .dtb’s) on your pi4 and pi5 devices while I am waiting for 6by9 to get back to me using a regular computer monitor to rule out the issue being my tv monitor. I do not have another monitor to test with.
If it does not boot to the login screen do a CTRL-ALT-F2 and log in the TTY and then copy back your saved .dtb’s to /boot or just install one of the kernels in the repo and reboot.
Download the tarball and unpack and install the kernel / kernel-headers for your device in the 6.13-rc2-1 folder:
https://drive.google.com/file/d/1D5GMZDcaErB4FM9H7l5GmIRANzAaMK_y/view?usp=sharing