My workaround was to restore pre-notch behaviour by picking a resolution from the "show all resolutions" list that is conveniently+ exactly screen res height minus notch height.
I theoretically "lose" that much height but gain a) zero notch b) non-rounded top corners and c) a traditionally heighted menubar instead of the giant one that is so big only to cater for the notch.
+ I thought this was thanks to BetterDisplay but it turns out no third party tool is needed and it's all first party probably because someone at Apple is as annoyed by the notch as I was and so that's their solution.
I think it is because they want to send to apps resolution list that includes or excludes the notch area to choose from for full screen modes (eg in games). Selecting "show all resolutions" basically shows this list.
Definitely better now with their new "opensource" driver.
I still ran in a few snags:
- DKMS can break, e.g I had a kernel bump to 6.18 or 6.19 and the nvidia driver wasn't ready yet so the build failed. A mainline driver will always win this one.
- Suspend almost always works, but sometimes fails on lid close which is of course when you can't see it fail and my laptop battery dies unexpectedly. You'd say use hybrid sleep but that reliably always fails with the nvidia driver too. Both work flawlessly with Nouveau.
Since I don't need the extra perf on this laptop I just use Nouveau to drive the the dGPU + the AMD iGPU most of the time which is powerful enough for my non-desk needs.
Agree on both counts. I use debian unstable and is usually 50/50 on whether the machine will reboot on a working display after a kernel upgrade. Very easy to fix if you have a bit of knowledge, but certainly not ready for the general public.
I don't have a laptop with an nvidia card, but I often suspend the linux gaming machine on my living room, and sometimes it doesn't come back from sleep, while my steam deck never failed to.
> The first one seems to indeed be a real RCE in vim.
Barely, since there is little restriction as to what options modelines can set they should be largely considered equivalent to eval (if unintentionally). And generally they are which is why distros typically disable them by default.
IMHO in this day and age securemodelines should just be the default.
I don't know much about vim, but from the report it sounds like part of the issue was that disabling modelines would not prevent it:
> tabpanel is missing P_MLE
Unlike statusline and tabline, tabpanel is not marked with the P_MLE flag. This allows a modeline to inject %{...} expressions even when modelineexpr is disabled.
Edit: Upon re-reading the above I guess disabling modelineexpr is not the same as disabling modelines, and disabling modelines altogether might indeed prevent the issue.
This, although it's not merely "easier/cheaper", it's "impossible" (unless you sacrifice a ton of performance)
Same reason as a) GDDR on dGPUs (I think I read somewhere that GDDR is very much like regular DDR, just with much tighter paths and thus soldered in) and b) Framework Desktop (performance would reportedly halve if RAM were not soldered)
SSD reasons I seem to recall are architectural for security: some parts (controller?) that usually sit on a NVMe SSD are embedded in the SoC next to (or inside?) the secure enclave processor or whatever the equivalent of the T2 thing is in Mx chips, so what you'd swap would be a bank of raw storage chips which don't match the controller.
Fun fact: "chambrer le vin" i.e getting (usually red) wine from storage temperature to "room temperature" comes from a time where said room temperature was well below 20 degC (more like 13-15 degC), not the comfortable 20+ degC that people like to enjoy these days.
A sommelier friend of mine says that the best way to taste wine is the one you enjoy; if you want to have a glass of chilled powerful Haut-Médoc with some delicate fish, have at it.
I theoretically "lose" that much height but gain a) zero notch b) non-rounded top corners and c) a traditionally heighted menubar instead of the giant one that is so big only to cater for the notch.
+ I thought this was thanks to BetterDisplay but it turns out no third party tool is needed and it's all first party probably because someone at Apple is as annoyed by the notch as I was and so that's their solution.
reply