| 30 Nov 2023 |
Arch | Prior to swapping to AMD https://git.gmem.ca/arch/infra/src/commit/1810a2e40e25ae09a52d0d142fc4e2be1a0e3656/nix/london/configuration.nix#L160-L175 | 11:54:27 |
@atemu12:matrix.org | And you didn't update Nixpkgs on that change? | 11:55:33 |
Arch | Hm thinking about it I probably did do a flake update | 11:56:06 |
@atemu12:matrix.org | Please try it using the same Nixpkgs version | 11:56:45 |
Arch | I'll have to try and remember what rev that was 😅 | 12:01:15 |
@atemu12:matrix.org | Check yout flake.lock? You could also just switch to the old generation; while unnecessary, the nvidia driver also doesn't interfere when there is no nvidia hardware present | 12:02:28 |
@atemu12:matrix.org | * Check your flake.lock? You could also just switch to the old generation; while unnecessary, the nvidia driver also doesn't interfere when there is no nvidia hardware present | 12:02:35 |
Arch | Hm good shout | 12:03:04 |
Arch | In reply to@atemu12:matrix.org Check your flake.lock? You could also just switch to the old generation; while unnecessary, the nvidia driver also doesn't interfere when there is no nvidia hardware present Okay! That worked - checked out (well, reset) my flake.lock and rebuilt. Seems to be all good now. _Interesting_ | 12:09:17 |
Arch | Guess that will teach me to change more than one variable lol | 12:11:01 |
@atemu12:matrix.org | Arch: Could you do a first-parent bisect between those two revisions of Nixpkgs? | 15:53:36 |
Arch | In reply to@atemu12:matrix.org Arch: Could you do a first-parent bisect between those two revisions of Nixpkgs? I can do later tonight! :) | 16:42:59 |
| pentane joined the room. | 18:06:42 |
| coru joined the room. | 18:52:51 |
@r522:matrix.org | is the tcmalloc issue is https://github.com/ValveSoftware/Source-1-Games/issues/5043 ? | 21:35:38 |
K900 | Smells like it | 21:37:17 |
| 1 Dec 2023 |
| zentharen joined the room. | 00:29:24 |
Charles ⚡️ | so i have the g95nc now, it is very, very big | 07:27:41 |
Charles ⚡️ | but unfortunately, i can't get it to do 240Hz at 7680x2160 over DP 2.1, swaymsg -t get_outputs shows a max of 60Hz at that resolution | 07:28:19 |
Charles ⚡️ | any ideas for things to try? | 07:28:24 |
Charles ⚡️ | i'm using the cable that came in the box, which i would hope supports DP 2.1... | 07:28:39 |
Charles ⚡️ | (side note: the monitor does support ddc/ci, or at least ddcutil works to control the brightness) | 07:29:55 |
Charles ⚡️ | oh and i do have a 7900 XTX, so DP 2.1 should be supported by the GPU, cable, and monitor | 07:30:43 |
Charles ⚡️ | i see a max of 60Hz in windows 11 too | 07:37:37 |
Charles ⚡️ | i suspect bad cable | 07:37:50 |
Charles ⚡️ | okay, turning off my second monitor in windows 11 let it do 240Hz | 08:22:29 |
Charles ⚡️ | this made no difference in nixos though | 08:22:39 |
coru | I am no expert, but you shouldnt be able to get that high of a refresh rate on 7680x2160, no idea how it meshes, but DP80 (the cable spec you'll need for high bandwidth) is only said to support 4k at 300 fps, if it scales linearly, your resolution should get 150 fps max.
So it seems you have a DP40 cable.
I'd be interested to see if you can achieve that high refresh rate with such a high resolution! | 08:55:34 |
coru | In reply to @charles:computer.surgery this made no difference in nixos though oh wow, ok i take everything back. interesting! | 08:56:19 |
Charles ⚡️ | the plot thickens | 08:58:07 |