#
✕ nick:PaulFertser
#asahi · 2024-12-04 22:46
PaulFertsercy8aer: ah yes, those artifacts. But they are short in duration and anyway with speakersafetyd no artifacts should be able to damage anything, right?
#asahi · 2024-12-04 22:43
PaulFertserIIRC at no point in time there was a possibility to run with speakersafetyd not doing its job. The interlocking mechanism in the kernel was ensuring the speakers get no sound unless the daemon is running and working.
#asahi · 2024-12-04 22:40
PaulFertserfl0_id: do you mean Asahi Linux ever shipped with code dangerous for the speakers? I seem to remember there was a related bug but even that was not really dangerous (unless one was doing specific kind of stress-testing). Can't remember more and the relevant fediverse content is still not searchable...
#asahi · 2024-12-04 20:13
PaulFertserOr do I misremember and macOS is safe on all models with all possible inputs?
#asahi · 2024-12-04 20:06
PaulFertserI think you can still break the speakers with macOS if you let it play "I won the loudness war" for long enough though?
#asahi · 2024-11-17 12:05
PaulFertserThere're reports of weird unexplained OOMs with the kernel trying to allocate memory and failing even though there should be plenty.
#asahi · 2024-11-17 12:02
PaulFertserrunxiyu_: have you checked dmesg for OOM?
#asahi · 2024-11-13 11:56
PaulFertserrunxiyu_: when you boot another distro live that doesn't have selinux enabled or when you use init=/bin/sh trick and create a file then it doesn't get any additional xattr attributes required by selinux in strict mode.
#asahi · 2024-11-12 21:42
PaulFertserquaff: so just creating /.autorelabel from live system should help.
#asahi · 2024-11-12 21:41
PaulFertser"A third way to fixing your issue can be to switch selinux into permissive mode using kernel boot options by adding the option enforcing=0"
#asahi · 2024-11-12 21:38
PaulFertserIndeed it talks about needing to do "touch /.autorelabel"
#asahi · 2024-11-12 21:38
PaulFertserquaff: https://docs.fedoraproject.org/en-US/quick-docs/reset-root-password/
#asahi · 2024-11-12 21:29
PaulFertserHm, what could have gone wrong doing that from inside chroot? Probably some selinux trick?
#asahi · 2024-11-12 21:18
PaulFertserquaff: if you could edit files on target partition though you could just manually edit /etc/group and add your user to all the groups you need.
#asahi · 2024-11-12 20:39
PaulFertserFor the reference, in RHEL I had to use "rdinit=/bin/sh" to make any change, but that also means one needs to manually mount rootfs from the shell.
#asahi · 2024-11-12 20:33
PaulFertserDoes that make Fedora run regular init names from initramfs and then the script or whatever is there would honour that kernel option? Or is Asahi Linux not normally using initramfs?
#asahi · 2024-10-17 09:44
PaulFertserariejan: you can try using "wev" to see what events happen when you press those buttons.
#asahi · 2024-10-15 22:13
PaulFertserSo no errors and it's unlikely partitioning might have affected this strange OOM anyhow.
#asahi · 2024-10-15 21:37
PaulFertserI made a typo, s/channels/channel/
#asahi · 2024-10-15 21:37
PaulFertserYes
#asahi · 2024-10-15 21:34
PaulFertserAnd I suggest you stay on channels, there're some real developers who have 100x more clue than me so they might have much better ideas.
#asahi · 2024-10-15 21:34
PaulFertsermbeavitt: no problem, just do not ask to ask :)
#asahi · 2024-10-15 21:33
PaulFertsermbeavitt: dmesg or it should be present in your system log too, so "journalctl -xe" and you can check prior boots too.
#asahi · 2024-10-15 21:30
PaulFertsermbeavitt: don't trust people who do not show dmesg ;)
#asahi · 2024-10-15 21:30
PaulFertserDo you have any other backtraces reported by other parts of the kernel sometimes?
#asahi · 2024-10-15 21:29
PaulFertsermbeavitt: well, imagine how many M1 users are out there using Firefox to watch youtube. I'd say a lot. So there's a chance something weird is happening on your machine due to some of your custom settings.
#asahi · 2024-10-15 21:28
PaulFertserFirefox gets killed just because it's the biggest process, it's the kernel needing memory there, not userspace.
#asahi · 2024-10-15 21:26
PaulFertsermbeavitt: haha interesting.
#asahi · 2024-10-15 21:26
PaulFertsermbeavitt: I notice unlike the majority of Asahi Linux users you run GNOME and not KDE Plasma.
#asahi · 2024-10-15 21:24
PaulFertsermbeavitt: it's a different case though. In yours it's GFP_KERNEL_ACCOUNT allocation and somehow a unix socket was involved, so the kernel itself needed more memory to handle something being sent somewhere locally (AF_UNIX socket family), I wonder what it is on your system.
#asahi · 2024-10-15 21:14
PaulFertsermbeavitt: might be related: https://social.treehouse.systems/@marcan/113255100055208143
#asahi · 2024-10-15 21:12
PaulFertserI do not see anything dangerous in that especially if you do not run anything custom. But it gives a chance to smart devs look and give an educated suggestion.
#asahi · 2024-10-15 21:09
PaulFertsermbeavitt: do you know you can watch youtube with mpv by just passing it a video URL?
#asahi · 2024-10-15 21:07
PaulFertsermbeavitt: oh btw, it's normal to have physical RAM near full during normal usage because the free space is used for disk cache automatically. It's freed under pressure automatically too, so nothing to worry about.
#asahi · 2024-10-15 21:06
PaulFertsermbeavitt: where's the text paste of the OOM kernel log part?
#asahi · 2024-10-15 20:58
PaulFertserProcessing of sysctl conf files is nothing Asahi-specific.
#asahi · 2024-10-15 20:58
PaulFertsermbeavitt: and you didn't mention what distro you're using yet.
#asahi · 2024-10-15 20:56
PaulFertserAs to the sysctl.conf , it's process by whatever your distro runs ono startup to process it.
#asahi · 2024-10-15 20:56
PaulFertserHave you tried inspecting OOM report closely?
#asahi · 2024-10-15 20:55
PaulFertserIn my experience with low RAM targets no matter what swappiness is the kernel OOM killer won't do anything till the swap is ~full.
#asahi · 2024-10-15 20:51
PaulFertserWell, this name is arch-specific in a way.
#asahi · 2024-10-15 20:49
PaulFertsermbeavitt: and BTW, Asahi Linux is not just about Linux, the kernel, there're essential userpace parts and tweaks and fixes too.
#asahi · 2024-10-15 20:48
PaulFertsermbeavitt: there's also a very active Reddit community but, again, full question is needed there. And if it's Fedora-specific, there's a Fedora web discussion forum.
#asahi · 2024-10-15 20:46
PaulFertsermbeavitt: asking your real question first might help to get more answers
#asahi · 2024-10-04 20:40
PaulFertserCalandracas: good to know. Where can people buy it and what's maximum resolution? :)
#asahi · 2024-10-04 20:40
PaulFertserCalandracas: no sound glitches during cursor movement?
#asahi · 2024-09-27 19:11
PaulFertserThey're using Rock Pi 4 (RK3399) for the USB SS connection though, not raspberry pi.
#asahi · 2024-09-27 19:07
PaulFertserAnd people here were often asking about ways to connect external displays and probably this is a good and fast way to try it ("everybody has raspberrypi around") to see if it's probably OK for the anticipated usecases.
#asahi · 2024-09-27 19:06
PaulFertserar: well, of course, that's why I linked specifically to performance page. But unlike displaylink the driver is all free software and upstream.
#asahi · 2024-09-27 18:41
PaulFertserHave you folks heard of https://github.com/notro/gud/wiki/Performance ? It's supposed to allow attaching additional displays via USB with RPi or other SBCs. There's a DRM driver in upstream.

plus ›