Welcome to the new monthly unstable branch thread.
Recent News
Kernel 5.4 is now EOL
5.4.302 is the last maintenance release of the 5.4 kernel series. This kernel is now marked ‘End Of Life’ (EOL). It is recommend to switch to a newer LTS series like 5.10 or 5.15.
Kernel 6.17 is now EOL
6.17.13 is the last maintenance release of the 6.17 kernel series. This kernel is now marked ‘End Of Life’ (EOL). It is recommend to switch to the newer linux618 series:
sudo mhwd-kernel -i linux618
[DRAFT] NVIDIA 590 driver drops Pascal support
With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) GPUs or older.
Impact: Updating the NVIDIA packages on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment.
Intervention required for Pascal/older users: Users with GTX 10xx series and older cards must switch to a legacy driver to maintain support:
Install the official linuxXXX-nvidia-575xx, linuxXXX-nvidia-570xx, or related DKMS packages.
Notable Package Changes
Known Issues
.NET packages may require manual intervention
2025-12-11 - George Rawlinson
The following packages may require manual intervention due to the upgrade from 9.0 to 10.0:
aspnet-runtime
aspnet-targeting-pack
dotnet-runtime
dotnet-sdk
dotnet-source-built-artifacts
dotnet-targeting-pack
pacman may display the following error failed to prepare transaction (could not satisfy dependencies) for the affected packages.
If you are affected by this and require the 9.0 packages, the following commands will update e.g. aspnet-runtime to aspnet-runtime-9.0:
pacman -Syu aspnet-runtime-9.0
pacman -Rs aspnet-runtime
– Arch Linux - News: .NET packages may require manual intervention
Additional Info
Info about AUR packages
AUR (Arch User Repository ) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in Support > AUR and a helpful volunteer may be able to assist you.
Get our latest daily developer images now from Github: Plasma , GNOME , XFCE . You can get the latest stable releases of Manjaro from CDN77 .
Check if your mirror has already synced:
2025-12-12T23:00:00Z
freerdp2 moved to AUR
$ pamac search freerdp
libpam-freerdp2 2.0.0-1 AUR
Arctica Greeter: Remote logon support for freerdp (PAM module)
krdc-xfreerdp 23.08.5-3 AUR
Remote Desktop Client(old version with xfreerdp)
freerdp2 2.11.7-5 [Installed]
Free implementation of the Remote Desktop Protocol (RDP)
freerdp-sdl3 1:3.17.2-1 AUR
Free implementation of the Remote Desktop Protocol (RDP) (SDL3 only)
freerdp-git 3.12.0.r53.g11e980a-1 AUR
Free implementation of the Remote Desktop Protocol (RDP)
1 Like
Aragorn
Split this topic
1 December 2025 19:31
2
A post was split to a new topic: Kernel config option — backlight
Noticed that the 6.18 kernel is available in unstable and testing. Will there be a linux618-zfs package soon or are zfs-dkms and zfs-utils sufficient voor using zfs on these manjaro branches ?
philm
7 December 2025 08:51
4
There is no stable version of zfs yet. 6.17 series is the highest supported one, for now.
opened 07:16AM - 16 Sep 25 UTC
closed 09:47AM - 16 Sep 25 UTC
Type: Defect
According to a Phoronix article `write_cache_pages` will be removed from the ke… rnel.
https://www.phoronix.com/news/Linux-6.18-write-cache-pages
The corresponding kernel patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9c5518f1bacf98b20c3ad0fa5873b4da92122ced
How will that affect openzfs?
master ← robn:linux-6.18-compat
opened 01:36AM - 13 Oct 25 UTC
_[Love using OpenZFS on the latest Linux kernel? [Sponsor me!](https://despairla… bs.com/sponsor/)]_
### Motivation and Context
> You're so afraid of losing it
> But you're more afraid of showing it
> No good manners, no social skills
> Just vanity and overkill
>
> -- No Big Deal, Sahara Hotnights, 2001.
[6.18-rc1](https://lore.kernel.org/lkml/CAHk-=whPJTtX5u1m47fPUD2g2Dc=Did_6OqCVj6OQPKFgfKn9g@mail.gmail.com/) was tagged a few hours ago, and we should try to accommodate it.
### Description
All but one of the changes are simple API renames, moves or adjustments, which means only a few lines to detect and adjust for them. Refer to the commits for details, but the quick summary of things:
- `nth_page()` macro removed
- `ida_simple_*()` wrappers removed
- `block_device_operations->getgeo()` prototype changed
- `*_namespace->ops->type` moved to `*_namespace->ns_type`
- `generic_drop_inode()` and `generic_delete_inode()` renamed
- `sha256_*` and `sha512_*` exposed with conflicting prototypes
The remaining change is replacing `write_cache_pages()`, which has been removed from the kernel. This is fairly straightfoward: we already have a wrapper for this in `zpl_write_cache_pages()` to assist with page vs folio availability, so this is just a more involved implementation of that function that simply grabs all the dirty pages in the mapping, loops over them and calls `zpl_putpage()`->`zfs_putpage()` for them. No other changes are required, as the semantics of page/folio management are unchanged.
### How Has This Been Tested?
Full ZTS succeeded on: 6.18.0-rc1, -rc2 (will rerun and update for each -rc as they appear).
Compile checked against: 4.19.325, 5.4.296, 5.10.240, 5.15.189, 6.1.147, 6.6.101, 6.12.41, 6.16.4, 6.17.0.
I am both cautious and optimistic about the `zpl_write_cache_pages()` update. Cautious, because the `mmap` test tag failed a lot during its development, optimistic, because once I understood everything it also passed a lot.
### Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Performance enhancement (non-breaking change which improves efficiency)
- [x] Code cleanup (non-breaking change which makes code smaller or more readable)
- [x] Quality assurance (non-breaking change which makes the code more robust against bugs)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Library ABI change (libzfs, libzfs\_core, libnvpair, libuutil and libzfsbootenv)
- [ ] Documentation (a change to man pages or other documentation)
### Checklist:
- [x] My code follows the OpenZFS [code style requirements](https://github.com/openzfs/zfs/blob/master/.github/CONTRIBUTING.md#coding-conventions).
- [ ] I have updated the documentation accordingly.
- [x] I have read the [**contributing** document](https://github.com/openzfs/zfs/blob/master/.github/CONTRIBUTING.md).
- [ ] I have added [tests](https://github.com/openzfs/zfs/tree/master/tests) to cover my changes.
- [x] I have run the ZFS Test Suite with this change applied.
- [x] All commit messages are properly formatted and contain [`Signed-off-by`](https://github.com/openzfs/zfs/blob/master/.github/CONTRIBUTING.md#signed-off-by).
2 Likes
thats new
Dez 07 20:16:15 kernel: warn_alloc: 1 callbacks suppressed
Dez 07 20:16:15 kernel: python3: page allocation failure: order:0, mode:0xc0de0(GFP_KERNEL|__GFP_HIGH|__GFP_ZERO|__GFP_COMP|__GFP_NOMEMALLOC), nodemask=(null),cpuset=/,mems_allowed=0
Dez 07 20:16:15 kernel: CPU: 31 UID: 1000 PID: 27019 Comm: python3 Tainted: G OE 6.18.0-1-MANJARO #1 PREEMPT(full) 963af16d2cfb6ee5a80c987405d35211ffd33d09
Dez 07 20:16:15 kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Dez 07 20:16:15 kernel: Hardware name: ASUS System Product Name/ROG MAXIMUS Z790 HERO, BIOS 3001 04/25/2025
Dez 07 20:16:15 kernel: Call Trace:
Dez 07 20:16:15 kernel: <TASK>
Dez 07 20:16:15 kernel: dump_stack_lvl+0x5d/0x80
Dez 07 20:16:15 kernel: warn_alloc+0x163/0x190
Dez 07 20:16:15 kernel: __alloc_pages_slowpath.constprop.0+0x587/0xe00
Dez 07 20:16:15 kernel: __alloc_frozen_pages_noprof+0x334/0x350
Dez 07 20:16:15 kernel: alloc_pages_mpol+0x86/0x170
Dez 07 20:16:15 kernel: folio_alloc_noprof+0x5b/0xb0
Dez 07 20:16:15 kernel: isolate_lock_cluster.isra.0+0x112/0x1d0
Dez 07 20:16:15 kernel: cluster_alloc_swap_entry+0x142/0x360
Dez 07 20:16:15 kernel: folio_alloc_swap+0x194/0x450
Dez 07 20:16:15 kernel: shrink_folio_list+0xa53/0xf10
Dez 07 20:16:15 kernel: evict_folios+0x2cd/0x790
Dez 07 20:16:15 kernel: try_to_shrink_lruvec+0x173/0x250
Dez 07 20:16:15 kernel: shrink_one+0x108/0x1f0
Dez 07 20:16:15 kernel: shrink_node+0xac2/0xc60
Dez 07 20:16:15 kernel: do_try_to_free_pages+0xb3/0x550
Dez 07 20:16:15 kernel: try_to_free_pages+0xde/0x200
Dez 07 20:16:15 kernel: __alloc_pages_slowpath.constprop.0+0x34f/0xe00
Dez 07 20:16:15 kernel: __alloc_frozen_pages_noprof+0x334/0x350
Dez 07 20:16:15 kernel: alloc_pages_mpol+0x86/0x170
Dez 07 20:16:15 kernel: ? mod_memcg_lruvec_state+0xc5/0x1f0
Dez 07 20:16:15 kernel: vma_alloc_folio_noprof+0x6e/0xd0
Dez 07 20:16:15 kernel: do_anonymous_page+0x31a/0x8a0
Dez 07 20:16:15 kernel: ? ___pte_offset_map+0x1b/0x160
Dez 07 20:16:15 kernel: __handle_mm_fault+0xa60/0xf10
Dez 07 20:16:15 kernel: handle_mm_fault+0xe7/0x2d0
Dez 07 20:16:15 kernel: do_user_addr_fault+0x21a/0x690
Dez 07 20:16:15 kernel: exc_page_fault+0x7e/0x1a0
Dez 07 20:16:15 kernel: asm_exc_page_fault+0x26/0x30
Dez 07 20:16:15 kernel: RIP: 0033:0x7f7caeba94c9
Dez 07 20:16:15 kernel: Code: 8e ab 03 00 00 48 8b 5c 24 d0 4d 8d 51 20 c4 c1 f9 7e db 48 89 f7 49 29 f3 49 29 f2 48 01 f3 66 90 c5 fc 59 4f 20 c5 fc 59 17 <c4> c1 7c 11 14 3b c4 c1 7c 11 0c 3a 48 83 c7 40 48 39 df 75 e2 48
Dez 07 20:16:15 kernel: RSP: 002b:00007f7a9dffac20 EFLAGS: 00010287
Dez 07 20:16:15 kernel: RAX: 0000000000120000 RBX: 00007f748b74e040 RCX: 00007f7ac0828180
Dez 07 20:16:15 kernel: RDX: 00007f7a9dffacf0 RSI: 00007f748b2ce040 RDI: 00007f748b3f0000
Dez 07 20:16:15 kernel: RBP: 00007f7a9dffac50 R08: 0000000000000001 R09: 00007f74846cd040
Dez 07 20:16:15 kernel: R10: fffffffff93ff020 R11: fffffffff93ff000 R12: 00007f7a9dffacf0
Dez 07 20:16:15 kernel: R13: 00000000017a0000 R14: 0000000000000000 R15: 00000000018c0000
Dez 07 20:16:15 kernel: </TASK>
Dez 07 20:16:15 kernel: Mem-Info:
Dez 07 20:16:15 kernel: active_anon:3042855 inactive_anon:1111600 isolated_anon:0
active_file:9759380 inactive_file:151672 isolated_file:0
unevictable:0 dirty:521 writeback:0
slab_reclaimable:109694 slab_unreclaimable:103836
mapped:6123368 shmem:107862 pagetables:34729
sec_pagetables:268 bounce:0
kernel_misc_reclaimable:0
free:73042 free_pcp:53769 free_cma:0
Dez 07 20:16:15 kernel: Node 0 active_anon:12171420kB inactive_anon:4446400kB active_file:39037520kB inactive_file:606688kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:24493472kB dirty:2084kB writeback:0kB shmem:431448kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:9865216kB kernel_stack:23312kB pagetables:138916kB sec_pagetables:1072kB all_unreclaimable? no Balloon:0kB
Dez 07 20:16:15 kernel: Node 0 DMA free:11260kB boost:0kB min:12kB low:24kB high:36kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB zspages:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Dez 07 20:16:15 kernel: lowmem_reserve[]: 0 636 63962 63962 63962
Dez 07 20:16:15 kernel: Node 0 DMA32 free:247820kB boost:0kB min:552kB low:1088kB high:1624kB reserved_highatomic:0KB free_highatomic:0KB active_anon:247852kB inactive_anon:90196kB active_file:41808kB inactive_file:12kB unevictable:0kB writepending:0kB zspages:17304kB present:717276kB managed:651304kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Dez 07 20:16:15 kernel: lowmem_reserve[]: 0 0 63326 63326 63326
Dez 07 20:16:15 kernel: Node 0 Normal free:35508kB boost:157696kB min:224708kB low:289544kB high:354380kB reserved_highatomic:0KB free_highatomic:0KB active_anon:11923568kB inactive_anon:4356204kB active_file:38995712kB inactive_file:606676kB unevictable:0kB writepending:2080kB zspages:6784268kB present:66052096kB managed:64846208kB mlocked:0kB bounce:0kB free_pcp:212504kB local_pcp:15776kB free_cma:0kB
Dez 07 20:16:15 kernel: lowmem_reserve[]: 0 0 0 0 0
Dez 07 20:16:15 kernel: Node 0 DMA: 1*4kB (U) 1*8kB (U) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 1*2048kB (M) 2*4096kB (M) = 11260kB
Dez 07 20:16:15 kernel: Node 0 DMA32: 649*4kB (UME) 683*8kB (UME) 587*16kB (UME) 583*32kB (UME) 354*64kB (UME) 193*128kB (UME) 92*256kB (UME) 47*512kB (UME) 20*1024kB (UME) 11*2048kB (UME) 18*4096kB (UM) = 247820kB
Dez 07 20:16:15 kernel: Node 0 Normal: 250*4kB (UM) 8*8kB (UM) 440*16kB (U) 1*32kB (M) 98*64kB (UME) 95*128kB (UME) 12*256kB (UME) 13*512kB (UM) 0*1024kB 0*2048kB 0*4096kB = 36296kB
Dez 07 20:16:15 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Dez 07 20:16:15 kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Dez 07 20:16:15 kernel: 10182726 total pagecache pages
Dez 07 20:16:15 kernel: 211281 pages in swap cache
Dez 07 20:16:15 kernel: Free swap = 64110296kB
Dez 07 20:16:15 kernel: Total swap = 75497468kB
Dez 07 20:16:15 kernel: 16696341 pages RAM
Dez 07 20:16:15 kernel: 0 pages HighMem/MovableOnly
Dez 07 20:16:15 kernel: 318123 pages reserved
Dez 07 20:16:15 kernel: 0 pages cma reserved
Dez 07 20:16:15 kernel: 0 pages hwpoisoned
knows why that is ?
Edit:
This is a issue of SwarmUI and not Manjaro
With latest NVidia drivers 580.119.02 my screen started to blinking. This is especially noticeable when I launch Steam. The games don’t blinking themselves, but Steam window and my desktop environment (Xfce) do. I reverted to stable branch with 580.105.08 drivers and everything is ok. I found nothing about this problem, so I report you about it.
My GPU is NVidia RTX 2060 SUPER.
Kernel version is 6.18
i can confirm this point even with a terminal & text blinking ( Xfce & X11)
1 Like
@Rinaldus @stephane
Have you Test this ?
options nvidia.NVreg_EnableGpuFirmware=0
I switched back to unstable branch again to test it, but unfortunately the screen is blinking even with this parameter. I’ll be on a stable branch until this is fixed, I hope it will be soon.
The ability to switch branch when the problem occurs is the biggest Manjaro advantage in comparision with Arch.
i still confirm this point even with a terminal & text blinking ( Xfce & X11 )
1 Like
Just FYI, as far as I read, that does nothing for nvidia-open / nvidia-open-dkms. It’s only applicable for nvidia / nvidia-dkms.
philm
15 December 2025 04:30
12
Did anyone actually reported the issue properly to Nvidia yet?
List of issues that still affect the newest 580 driver: Random black screens when playing intensive games, sometimes resulting in a partial GPU driver crash. It is sometimes possible to switch to a TTY, but attempting to switch back to a...
version 580.119 is a very bad one for Xfce & X11 ( blink on text and also icon / text in menu bar )
Interesing … on my nvidia system 580.119 works … with my 2070mobile 580.119 it brought back the suspend functionality that was gone with the previous version of the 580 with Gnome … with the previous version I needed to session-quit-gnome to be able to suspend, now this works again while being logged in…
Yochanan
Split this topic
16 December 2025 00:09
15
4 posts were split to a new topic: Missing required signature
philm
16 December 2025 01:29
16
Focus of Nvidia is on wayland, GNOME and Plasma issues, not legacy software…
nvidia offers nvidia-open for wayland , why in this case change nvidia legacy ?
nvidia-open has problems with video memory, such as increased consumption. for me 580.119.02 close module and nvidia-beta work fine but I haven’t tested X11
change under X11 for login session wayland (labwc ) , and nvidia5.80 119 is working ( not for 590 coming )
philm
19 December 2025 09:52
20
Those who have issues with Nvidia 580xx series may want to switch to unstable branch and test 590.48.01 …
590.44.01 (x86_64 / aarch64) Raised the minimum supported Wayland version to 1.20. Fixed a bug that prevented the PowerMizer preferred mode dropdown menu in the nvidia-settings control panel from functioning correctly on Wayland. Raised the...
Reading time: 28 mins 🕑
Likes: 80 ❤