[Unstable Update] November 2024 Edition – Unstable Updates
Welcome to the new monthly unstable branch thread.
Recent News
Notable Package Changes
Known Issues
NVIDIA 565 Driver
- Displays connected via DVI may not function on certain graphics cards.
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 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:
1 Like
I hope it’s appropriate to comment here: Last month Phil made the following comment regards the then 560 Nvidia drivers:
I applaud the goal of not requiring user administration to perform the update and it’s great to hear that you see a direction on how to get there. I’m sure that this is why many of us are here.
With the present update to the 565 beta drivers, it’d be great to hear what the plan is. Your comment on the driver assistant made it sound as though the aforementioned homework was not being done. Hopefully, this update provides an opportunity to communicate your vision. I for one would certainly be more patient and understanding if there was a plan or criteria for the stable drivers that follow to be in the stable branch.
1 Like
nvidia-drivers 565 are still broken for kernel 6.12-rc5. Any news about it?
2 Likes
Kernel extra modules sometimes not build for RC Kernels see:
I see. However, I switched to kernel 6.12 since rc2 and there weren’t problems with nvidia drivers before.
All the extra modules seem to be there, except for a couple, according to pamac gui.
1 Like
Try linux612-nvidia
565.57.01-0.2 or nvidia-dkms
565.57.01-2 coming along shortly.
1 Like
Hi,
@Yochanan Still the same with linux612-nvidia
565.57.01-0.2 → lightdm.service could not start. Only CLI tty are working.
No problems with other kernels, working as expected.
EDIT 1 2 (20241102): Regarding the tests I’ve done, 565 performances are better than 550 NVIDIA drivers and 560 (performance drop with this one). NVIDIA have started to speak about the 570 drivers apparently for the next stable release to come.
EDIT 2 (20241106): linux612-nvidia
565.57.01-0.4 work as expected. Performances are good as other kernels.
Wish You well
1 Like
I updated, but it’s still broken.
1 Like
@JimmyK ,
You may find the reason why NVIDIA 565 drivers are in the unstable
branch here at the end of the thread:
https://forum.manjaro.org/t/unstable-update-october-2024-edition/168715/119
Wish You well
I saw that. I’m not asking for a reason.
Sorry, linux612-nvidia
565.57.01-0.4 and nvidia-dkms
565.57.01-3 should be fixed.
3 Likes
I just tried Linux 6.12.0-rc6-1 with headers and virtualbox-host-modules. Upon trying to launch a Virtualbox VM, Virtualbox (7.1.4-1) wouldn’t launch the VM and gave a cryptic message about some parameter when compiling the kernel. I didn’t take note of the exact message.
Upon further looking into this I found:
“In [Linux] kernel 6.12, KVM initializes virtualization on module
loading by default. This prevents VirtualBox VMs from starting,”
said the devs. “In order to avoid this, either add
“kvm.enable_virt_at_load=0″ parameter
into kernel command line or unload the
corresponding kvm_XXX module.”
I added the kernel command parameter to GRUB and the issue was resolved. Going forward will I have to continue using the kernel command parameter in GRUB or will this issue be resolved when the final 6.12 LTS kernel is released?
2 Likes
Hi,
nvidia-open-dkms
565.57.01-2 is broken for
linux612
Other kernels working as expected with nvidia-open-dkms
565.57.01-2
EDIT1: linux612
now work as expected with nvidia-open-dkms
565.57.01-4
Wish You well
nvidia–dkms 565.57.01-3 is now out which is supposed to be fixed
Hi @robin0800,
There’s no nvidia-open-dkms
565.57.01-3 yet as You may see here:
https://manjaristas.org/branch_compare?q=nvidia-open-dkms
Wish You well
1 Like
Hello, while updating I got the following message:
Error! acpi_call/1.2.1: Missing the module source directory or the symbolic link pointing to it.
Manual intervention is required!
What does it mean and what should I do?
In what context?
I didnt get any such error.
Does this mean you use some acpi_call package?