#asahi · 2024-02-29 18:59
PaulFertserj`ey: I'm surprised there's any need to estimate consumption by looking at how state of charge changes over time instead of just looking at the immediate current.#asahi · 2024-02-29 18:33
PaulFertserIs asahi battery driver not providing CURRENT_NOW attribute?#asahi · 2024-02-27 11:58
PaulFertserThanks everybody for clarifications!#asahi · 2024-02-27 11:47
PaulFertserAnd CTM is not really a substitute because it's linear by definition while gamma is non-linear. But better than nothing indeed.#asahi · 2024-02-27 11:46
PaulFertserSo basically the driver announces support for color management so that CTM could be used but everything else is ignored for now, right?#asahi · 2024-02-27 11:43
PaulFertserIs any kind of regular gamma adjustment supported though?#asahi · 2024-02-27 11:41
PaulFertserSo it looks there's no need to really depend on KDE and one can read https://elixir.bootlin.com/linux/latest/source/include/uapi/drm/drm_mode.h#L838 and compose and apply that matrix by other means.#asahi · 2024-02-27 11:27
PaulFertserhttps://github.com/AsahiLinux/linux/pull/119/commits/a3902903597bb120319d83bc6eabd157b4ca6c74 so basically it just uploads the matrix as supplied to DCP?#asahi · 2024-02-27 11:25
PaulFertserhttps://github.com/AsahiLinux/linux/issues/91#asahi · 2024-02-27 11:23
PaulFertserhttps://www.reddit.com/r/AsahiLinux/comments/13jtm4h/how_to_customize_color_profilecalibration_on/ suggests there should be at least some way to adjust colour temperature though#asahi · 2024-02-27 11:15
PaulFertserInteresting, here people report profiles without Gamma Table do not do anything https://forums.linuxmint.com/viewtopic.php?t=281685#asahi · 2024-02-27 11:15
PaulFertserIt's not supposed to flicker when changing colours.#asahi · 2024-02-27 11:12
PaulFertserSo did it actually change anything?#asahi · 2024-02-27 11:11
PaulFertserWeird, https://github.com/udifuchs/icc-brightness/issues/1 also talks about needing to run several times sometimes.#asahi · 2024-02-27 11:09
PaulFertserkidplayer666: is that after running device-add-profile ?#asahi · 2024-02-26 19:45
PaulFertserNoScript helps a lot to manage web browser tabs RAM consumption#asahi · 2024-02-26 16:05
PaulFertsernicolas17: might be but that doesn't really answer my question :(#asahi · 2024-02-26 15:38
PaulFertserkidplayer666: ok, and what happens if you try to assign the colour profile with that tool?#asahi · 2024-02-26 15:24
PaulFertserkidplayer666: have you tried using "colormgr" to see some probably more detailed informaton?#asahi · 2024-02-26 15:04
PaulFertserj`ey: (cpu onlining) is it related to not using PSCI as designed and is it likely to change any time soon?#asahi · 2024-02-26 14:54
PaulFertsereldondev: OpenWrt enables watchdog by default#asahi · 2024-02-26 14:53
PaulFertserAsahi Fedora might be enabling more dependencies automatically, like it does for speakersafetyd#asahi · 2024-02-26 14:50
PaulFertserBTW, how does the watchdog work here, is it inside the SoC an generates a pulse on RESET line and that line is also connected to all the essential peripherals?#asahi · 2024-02-26 14:48
PaulFertserj`ey: I'm unfamiliar with Fedora hence asking#asahi · 2024-02-26 14:46
PaulFertserI mean like /dev/watchdog created and userspace feeding it by default#asahi · 2024-02-26 14:45
PaulFertserIs it used ever?#asahi · 2024-02-26 14:43
PaulFertserI remember that it can't fully kexec because so many aux hardware can't be properly fully re-inited. But is it true even for the PCIe controller to access NVMe? It's not like anything else is needed to save the crash info is it?#asahi · 2024-02-26 14:42
PaulFertserFor this argument to be less meaningful and at least somewhat educational, can someone please tell if Asahi has a hardware watchdog that reboots on kernel panic and whether it's activated by default in Fedora? Another question is whether Fedora automatically kexecs a kernel to collect crash dump and save it for later analysis prior to automatic reboot like RHEL does?#asahi · 2024-02-26 14:36
PaulFertserEither way sospi isn't here to clarify and guessing what was meant is moot.#asahi · 2024-02-26 14:34
PaulFertsereldondev: we were discussing sospi's report where it's clear the RAM usage was monitored by operator.#asahi · 2024-02-26 14:33
PaulFertserMost PMU ICs will not reboot when someone hold power button no matter for how long. Holding power button usually turns the host fully off eventually but doesn't power it back unless you release and press again.#asahi · 2024-02-26 14:32
PaulFertserIf you observe "swap thrashing" scenario and you want to give it a chance to recover yes, you'd wait.#asahi · 2024-02-26 14:31
PaulFertserI think it does a lot because if you wait you'll probably have much of your essential runtime data intact.#asahi · 2024-02-26 14:30
PaulFertserCrash is called "panic" in Linux terminology and in that case a distro can often use some machinery to save a crash dump and then reboot (enabled by default in RHEL). Another kind of crash I can imagine is when hardware watchdog forces reboot. Freezing for minutes (and sometimes hours) due to low RAM and then coninuing to run normally is by no sane definition a crash, I'm pretty sure.#asahi · 2024-02-26 14:26
PaulFertserSure, freezing for minutes (and hours) can happen especially when there's swap space enabled. But it's not a crash.#asahi · 2024-02-26 14:25
PaulFertserkidplayer666: issues meaning the kernel paniced or watchdog triggered or what?#asahi · 2024-02-26 14:00
PaulFertserI would say discussing memory pressure issues makes little sense without seeing /proc/meminfo .#asahi · 2024-02-26 13:58
PaulFertserj`ey: yes, having oom killer do its job is no joy but no system crash either.#asahi · 2024-02-26 13:53
PaulFertsersospi: with default settings Linux always uses free mem for caching access to storage. The cache is dropped when more memory is needed. You should provide more info about your situation. Also Linux doesn't crash when it's low on RAM, it runs an oom-killer to terminate the most suitable process to free up memory.#asahi · 2024-02-25 18:09
PaulFertserBut is it likely the required macOS version is likely to change in the future?#asahi · 2024-02-25 18:08
PaulFertsereldondev: normal Linux strategies assume firmware is redistributable and can be added to linux-firmware at git.kernel.org ...#asahi · 2024-02-25 18:02
PaulFertsereldondev: you can use a "test" device and then package everything needed yourself for your own use. That's how Apple wants it I'm afraid.#asahi · 2024-02-25 17:59
PaulFertsereldondev: in general the idea is that mac hardware has plenty of additional CPUs each running their own firmware and Asahi needs binaries for those additional CPUs, and the regular way to to get those binaries is copying from existing macOS system to the EFI partition that's accessible later to Linux.#asahi · 2024-02-25 17:57
PaulFertsereldondev: why are you not upgrading directly via the Internet?#asahi · 2024-02-11 20:51
PaulFertserOr read-only? strace -f is usually good at shedding light in cases like that.#asahi · 2024-02-10 14:17
PaulFertserWhat legacy apps are you talking about anyway. Like Xfig?#asahi · 2024-02-10 14:16
PaulFertserMake them not need external scaling.#asahi · 2024-02-10 14:16
PaulFertserYou can fix legacy apps to behave.#asahi · 2024-02-10 14:14
PaulFertserSame as how proper semantic markup lets web pages be displayed according to your needs and not just have a fixed "design" like a paper booklet.#asahi · 2024-02-10 14:11
PaulFertserBut you do want that flexibility inside every app. Compare old dialog windows with all fixed pixel sizes with modern "layouts" where window elements are scaled automatically based on the app logic and your own preferences and size and shape of displays etc.