#asahi · 2025-06-26 22:16
oxbarhi.. i know the default distro is fedora.. what de does it install and if it installs gnome or another one can i replace it with xfce ?#asahi · 2025-06-26 13:01
jannauthe preferred mode is based on dcp's scoring. m1n1's mode selection is limited though because the iboot protocol doesn't tell us which modes are real (there are virtual modes) and supported by the display#asahi · 2025-06-26 12:57
chadmedoh yeah i forgot we had that from ages ago #asahi · 2025-06-26 12:52
jannauselecting larger modes might be buggy (not well tested) since it requires fb reallocation#asahi · 2025-06-26 12:51
jannauchadmed: yes. m1n1 allows even mode selection via the "display" variable: https://github.com/AsahiLinux/m1n1/blob/main/m1n1.conf.example#L17#asahi · 2025-06-26 12:13
allmazz_oh, sry, missclick#asahi · 2025-06-26 12:13
allmazz_ }#asahi · 2025-06-26 12:13
allmazz_ return util.error(ctx.error.message, ctx.error.type);#asahi · 2025-06-26 12:13
allmazz_ if (ctx.error?.message) {#asahi · 2025-06-26 12:12
allmazz_the_eye: sometimes I have the same, but never made an attention, it does not impact anything on my system#asahi · 2025-06-26 12:04
chadmedissue seems to be drm and iboot disagreeing on what mode the monitor should be in. on my high refresh monitors drm thinks 60 hz is the preferred mode#asahi · 2025-06-26 12:01
chadmeddoes the iboot protocol let us select a mode or does dcp just pick the preferred mode based on edid#asahi · 2025-06-26 10:55
jannauthat sounds like it's the switch from simpledrm (boot framebuffer) to dcp (full display driver)#asahi · 2025-06-26 10:08
the_eye(the question was less about debugging and more about "is everyone else seeing this too") ok thanks, will try that#asahi · 2025-06-26 10:07
chaos_princessprobably. Can't psychically debug that one, if you are running plymouth, there is probably several things doing password requests via it, or some other nonsesne. Hit esc, see what it is doing.#asahi · 2025-06-26 10:05
the_eyesomething about my setup weird?#asahi · 2025-06-26 10:05
the_eyechaos_princess: I have fde too and there is one weird thing that I also wanted to ask about: after u-boot, the computer throws up a screen that looks like the one where I can enter my fde password, but it is unresponsive. After about 1-2 seconds the screen flashes subtly (kinda like a refresh?) and _then_ the password input responds to my keypresses. Does this happen for everyone or is#asahi · 2025-06-26 10:05
leiomy fde adventures need to wait till ya'll get M4 going :)#asahi · 2025-06-26 10:00
leio(no, I'm not proud of it, just still a tech debt from initial install I haven't dealt with)#asahi · 2025-06-26 10:00
chaos_princessi also ran an initramfs-less setup, but i have fde enabled now :P#asahi · 2025-06-26 10:00
leiochaos_princess: I don't use an initramfs, so it's not everyone that uses one :)#asahi · 2025-06-26 08:00
fl0_idregarding updates - there is no guarantee which is the latest, esp as there are ofc also flatpaks/snaps (and rpms) by the 3rd parties. which might be because they want newer packages or for whatever reason#asahi · 2025-06-26 06:57
chadmedsnaps can just go in the bin theyre shit at everything #asahi · 2025-06-26 06:57
chadmedflatpaks are good for sandboxing permissions and getting the vanilla sources as the upstream devs intended (note that this is NOT always a good thing), however you trade off runtime performance and having to basically have a whole second userspace image on your system#asahi · 2025-06-26 06:56
twbDoes each separate installed snap turn into a separate mountpoint in /proc/1/mountinfo? Cos I found out recently that if you have 1000+ mounts in there, you can break systemd#asahi · 2025-06-26 06:55
chadmedthe_eye: it depends on what youre trying to achieve. in terms of runtime speed, storage bloat, and getting the best fedora experience yes rpms are your best bet #asahi · 2025-06-26 06:54
twbI presume it was done for Ubuntu Core. I think I saw them doing it on normal desktops as well but now I say that I'm not 100% sure. https://documentation.ubuntu.com/core/how-to-guides/image-creation/build-a-kernel-snap/#asahi · 2025-06-26 06:53
the_eyetwb: they are what now??#asahi · 2025-06-26 06:53
twbAlso the way ubuntu kernels are now inside snap is... weird and brain-hurt#asahi · 2025-06-26 06:53
the_eyetwb: well yeah, definitely. OTOH, I am coming from ARCH where usually packages get updated quite quickly.. so I'm sitting here going "come _on_ fedora! Version 5.2.0 of darktable was released FOUR days ago! Like .. in prehistory!"#asahi · 2025-06-26 06:52
jbeI would assume that at least the fedora flatpak repo is updated at the same pace as their rpm repo is.#asahi · 2025-06-26 06:46
twbSo I prefer to run e.g. firefox from Debian rather than edge from https://packages.microsoft.com/debian/12/prod/dists/ -- and the fact that they're both .deb is irrelevant#asahi · 2025-06-26 06:46
twbSpeaking as a Debian weenie my priority is generally to minimize the number of principals I have to trust#asahi · 2025-06-26 06:44
the_eyeto the first question my gut feeling is "see, this is why it's better to use distro packages". To the second OTOH it might be "see, these new methods are better".#asahi · 2025-06-26 06:42
twbDo all three get the same kinds of local access control constraints? e.g. I *think* flatpak packages typically (always?) run inside bwrap and can't e.g. just read ~/.netrc or ~/.mozilla/default/passwords.db#asahi · 2025-06-26 06:41
twbDo all three get updated with the same cadence? If it's a snap of (say) inkscape, and includes an embedded copy of potrace, and potrace gets a security update, does the inkscape snap get automatically updated promptly?#asahi · 2025-06-26 06:39
the_eyequestion regarding software sources: as a matter of .. I dunno, felt principle, if some software is available via snap AND flatpak AND asahi fedora repositories, I choose the rpm variant. But is this also always the best choice in a technical sense?#asahi · 2025-06-26 06:30
the_eyechaos_princess: thanks again, that nvram setting did exactly what I wanted#asahi · 2025-06-26 00:15
twbOne of those things I simply hadn't thought about :-)#asahi · 2025-06-26 00:15
twbCool#asahi · 2025-06-26 00:13
chaos_princesslinux does the right thing mostly. We also have some extra fancy tricks like marking the DSP stack as being light enough so it can be scheduled on on e-cores only#asahi · 2025-06-26 00:08
twbHey so dumb question: apple's arm64 are AMP (performance/BIG + efficiency/little cores), and macos saves battery by sticking to efficiency cores where reasonable. Does that Just Work on linux, too? Or does linux treat it more like SMP?#asahi · 2025-06-25 21:04
the_eyeooooh many thanks#asahi · 2025-06-25 21:04
chaos_princesshttps://support.apple.com/en-us/120622#asahi · 2025-06-25 21:03
chaos_princessthere is a nvram variable you can set to make it not turn on from any lightest provocation#asahi · 2025-06-25 21:03
the_eyeso it drains rather quickly, probably#asahi · 2025-06-25 21:03
the_eyeI presume at this point no power saving functions are active as no plasma is running#asahi · 2025-06-25 21:03
the_eyeas far as I can surmise: plugging it in turns it on. It then boots until it gets to the screen where I need to input my disk encryption password#asahi · 2025-06-25 21:02
chaos_princessit turned on#asahi · 2025-06-25 21:02
the_eyeoh, here's another hardware-related (I think?) question. Scenario: My MacBook Pro (M2) is shut down, powered off. I think "oh, tomorrow I'll be going on a railway trip so best fully charge it first" so I plug the magsafe plug in. I unplug it in the morning. a few hours later I finally board the train, open the laptop and find the battery completely empty.