390 is EOL, there was no release. 
I realized that after clicking the links and reading more closely.
But I hope this will be included in the linux driver shorty. How long does that usually take btw?
extra/linux65-nvidia 535.113.01-10
Or are the versions not following the same structure on the linux drivers?
Huh? I pushed 545.29.02 (unstable), 535.129.03 (testing & stable) 470.223.02 (all branches) yesterday. Maybe your mirror(s) haven’t caught up yet.
1 Like
I was probably too fast, I ran an update right after it was posted. Let me sync up again, haven’t run an update today.
But I just learned that sudo pacman -Ss nvidia does not show the latest version available but rather the installed one.
But syncing gives me: linux65-nvidia-545.29.02-1
And we are up to date.
Sorry about that. <3
Not quite: it does show the version from the repositories as known from your last sync (which in your case happend to be the installed one).
Something in the new Nvidia drivers and kwin-x11 don’t wanna play along. My frame rate frequently drops to half of my monitor’s refresh rate, from 144 fps to 72. All I need to do it open any application window in the desktop, or it goes up and down in games.
With which kernel? Have you tried another?
I’m pretty new to Linux and kernel stuff, still learning every day, but can we install 6.6 mainline already? Also, with the latest Nvidia NFB driver? Or should you wait until they’re provided with the regular package updates?
By “can” I mean: Are there any possible potholes or is it just like 6.5.X “it’ll just work”? 
You tell us.
I’m still using 6.5 at the moment as there’s a regression in 6.6 with battery charging thresholds on my System76 Gazelle 17. Usually after the first point release or three things like that are ironed out.
Haha I see! I’m just curious about if it will work so I’ll guess I’ll just go with it And I’ll report if my PC goes up in smoke 
I have no idea what this is. Sounds like the world-saving code in a Tom Cruise movie 
LINUX66 HERE WE GO! xD
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
resolving dependencies...
looking for conflicting packages...
Packages (3) linux66-6.6.0-2 linux66-headers-6.6.0-2 linux66-nvidia-545.29.02-1
Total Download Size: 215,24 MiB
Total Installed Size: 306,90 MiB
:: Proceed with installation? [Y/n] y
Edit
Nope, didn’t explode, and my nvidia seems fine, booted up cities: skylines 2 and it worked, as well as it does… xD
1 Like
6.5.9, and good point, I have not 
I’ve installed 6.6 as well without any major issues. The only thing that is a bit annoying is, that with 6.6 some of my mouses’ hardware buttons have stopped working I don’t know why or how I’ll be able to use them again, but yeah, just a small price to pay for running the mainline kernel (I guess )
Kernel6.6.0-2
To compensate, Manjaro now detects more sensors on my B550 board
Incoming changes in JDK / JRE 21 packages may require manual intervention
2023-11-02 - Frederik Schwan
We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21.
To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work.
This will (potentially) require a manual user action during upgrade:
- If you have both JDK and JRE installed you can manually install the JDK with
pacman -Syu jdk-openjdkand this removes the JRE related packages.- If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
- If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.
At the moment this is only valid for the upcoming JDK 21 release.
5 Likes
I like that! I have a newer gigabyte and used the same “tricks” as for B550 mentioned in the arch wiki to get lm_sensors to play nice, install aur driver and other things I’m not a huge fan of doing.
Kinda gave up and let my mb handle the fans instead.
But this tells me it’s time to look into it again. 
I downgraded to 6.5.9 again to see if the problems are caused by 6.6. My buttons work again on 6.5.9, on 6.6 they don’t.
What would be the best place to report this?
I just tried 6.10.60, same frame rate drops occur.
I just had amd crash on me while using google earth in firefox.
Kernel 66
I just killed the plasma process. It keep trying to make new over and over, a kill and switch back and forth between tty got me back. plasma seems bugged still though, my “start” menu is bugged so need to reboot but its probably fine.
Nov 02 23:03:09 bednaManjaro kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=626089, emitted seq=626091
Nov 02 23:03:09 bednaManjaro kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 1720 thread firefox:cs0 pid 1724
Nov 02 23:03:10 bednaManjaro kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 02 23:06:51 bednaManjaro kernel: Out of memory: Killed process 1247 (kwin_x11) total-vm:2216572kB, anon-rss:330596kB, file-rss:0kB, shmem-rss:16kB, UID:1000 pgtables:1688kB oom_score_adj:200