#
✕ nick:fl0_id
#asahi · 2025-04-04 09:38
fl0_id(I once used a ssd - hdd setup on a windows laptop, with the user directoy symlinked to the hdd. it was great, except for some apps (nvidia gui driver thingy) breaking because node didn't support these types of symlinks)
#asahi · 2025-04-04 09:36
fl0_idjbe didn't it always? mostly you can have apps anywhere. though some might complain, and their Application Support/Library stuff which can be caches, downloaded things etc can get quite big, which you cannot easily move i think
#asahi · 2025-04-04 09:31
fl0_idmaybe just have someone upgrade the flash chips... ;)
#asahi · 2025-04-04 09:31
fl0_idbecause of xattrs etc I think
#asahi · 2025-04-04 09:31
fl0_idmonthebiff you can prob mount it, if it's ext4, but pretty sure you don't want to store imovie there
#asahi · 2025-04-03 08:23
fl0_idthe first to me seems to me like it could be a faulty cable or connector tbh. (not a driver developer, but guesstimating)
#asahi · 2025-04-03 08:03
fl0_idtea_bag_inc for hdmi, a configuration from uni seems unlikely... that's usually mostly for networks afaik
#asahi · 2025-04-03 07:51
fl0_idtea_bag_inc I'm not sure, but you could check if m1n1 version etc is up to date.
#asahi · 2025-04-03 07:45
fl0_idtea_bag_inc which macbook pro? m3's don't work at all yet
#asahi · 2025-03-27 21:26
fl0_idmmh I think they left already
#asahi · 2025-03-27 09:54
fl0_idtbodt mobile market is the intent of the regulation for apple, as that is much more restricted. macos you can still somewhat distribute your own apps and they have much less market share
#asahi · 2025-03-26 13:51
fl0_idevil_kin1_8791 maybe just try kde audio mixer just to be sure it's not a gnome thing
#asahi · 2025-03-25 21:07
fl0_idJamesB192 sorry for being a bit short before, this seems like a suitable guide. adjust for newer kernel etc https://discussion.fedoraproject.org/t/trouble-with-installing-a-patched-vanilla-upstream-kernel/105818
#asahi · 2025-03-25 17:05
fl0_idso just google for that and you should be good
#asahi · 2025-03-25 17:05
fl0_idJamesB192 afaik it's not different from building any other kernel
#asahi · 2025-03-24 08:43
fl0_idif anyone is interested in potentially using the DMA for asahi's advantage, FSFE is holding an online workshp today on this topic https://fsfe.org/news/2025/news-20250306-01.html
#asahi · 2025-03-22 16:16
fl0_id*asahi
#asahi · 2025-03-22 16:16
fl0_idI also reached out to ppl on the fsfe legal mailing list what they think (w/o mentioning asah)
#asahi · 2025-03-22 16:15
fl0_idchaos_princess btw this is the interoperability request form https://developer.apple.com/support/ios-interoperability/
#asahi · 2025-03-22 09:47
fl0_idqed for real
#asahi · 2025-03-22 09:47
fl0_idjannau haha wow
#asahi · 2025-03-22 09:34
fl0_idand temper expectations haha
#asahi · 2025-03-22 09:34
fl0_idchaos_princess yeah I know, just wanted to provide some context
#asahi · 2025-03-22 09:17
fl0_idif there commission would be aware, I think they have an actual interest to enable things like asahi, but prob they won't go out of their way as based on size etc addon developers etc are more important
#asahi · 2025-03-22 09:16
fl0_idbut that would be a separate request, independent of the current decision
#asahi · 2025-03-22 09:15
fl0_idthere might be some way to provide feedback and ask for additional specifications, but for this order this prob only would cover ios/ipados - under the dma you could potentially ask an interoperabiltiy request separately
#asahi · 2025-03-22 09:09
fl0_id- you could try to get info that way, but not sure if that would work, as like others said, the intent is probably more to enable developers for addon devices. (and the order f.e. only covers ios and ipados)
#asahi · 2025-03-22 09:08
fl0_idafaik as this is somewhat within my day job first - the original DMA is a regulation. the linked document is more like an order or "proposed measures"
#asahi · 2025-03-21 15:02
fl0_idI think then it's not that. but still cannot hurt to try the other things
#asahi · 2025-03-21 14:58
fl0_id restarting helps)
#asahi · 2025-03-21 14:58
fl0_idtexotek I don't know if this is true for m2 macbook air, but sometimes the same model has different numbers, like j293 j294 (one of these I made up) If yours has a diff number, it would not be enabled. also make sure to have installed the mic branch (or relevant package) of https://github.com/AsahiLinux/alsa-ucm-conf-asahi/tree/mics and you could try resetting the config by removing ~/.local/state/wireplumber/ (and sometimes reloading services or
#asahi · 2025-03-21 14:51
fl0_idtexotek you could check if your model number is enabled
#asahi · 2025-03-21 14:23
fl0_idmischa85_ btw, do you think the adt is different between firmware versions? if yes, maybe I can get another one once I upgraded to 15.x just to compare...
#asahi · 2025-03-21 13:10
fl0_idchaos_princess nice. though it was super confusing to me to just type random stuff to "continue"
#asahi · 2025-03-21 12:58
fl0_iddid anyone run from inside a font yet? they are basically turing complete or at least some of the formats I think...
#asahi · 2025-03-20 12:36
fl0_id(om macos)
#asahi · 2025-03-20 12:36
fl0_idsven yes, I would prob get a caldigit one at some point. right now a cheaper anker usb-c works, other screen goes to hdmi out
#asahi · 2025-03-20 10:35
fl0_idchaos_princess ah yeah right. thanks for clarifying
#asahi · 2025-03-20 10:25
fl0_idnicolas17 this. As far as I understand the separate systems are not very flexible, and patching everything is not feasible either due to the size etc. A manufacturer with their own kernel could just do what they want to. And some things, like display port chaining, doesn't even work on macos, or only with a TB4 doc for like 300
#asahi · 2025-03-18 21:49
fl0_idoops wrong channel
#asahi · 2025-03-18 21:49
fl0_idsven well, it would look like that, because it just put the macros/constants back into midr.h / removed them from the file where the original author duplicated them. so the only remaining part of that is https://github.com/AsahiLinux/m1n1/pull/450/commits/fa3cd4b96fd6acaeb4eca7eeccb2e4ec595b7f24#diff-81896a3d888013ed9999381fea7e22d11b2de48149444a059a54bc37de4814e5
#asahi · 2025-03-18 16:55
fl0_id*what it's worth
#asahi · 2025-03-18 16:55
fl0_idI like the fingerprint scanner for what it's worse, unless it's sth that I have to operate without hands
#asahi · 2025-03-18 16:54
fl0_idmonthebiff you can still do auth via webcam, assuming the webcam works there might even be some PAM integration that does that already. It just won't be as secure as using depth info etc, though it's generally not *that* secure I think
#asahi · 2025-03-18 10:49
fl0_idjmax mmh may amilie is still off. if anyone has a t6030, feel free to try this PR https://github.com/AsahiLinux/m1n1/pull/450
#asahi · 2025-03-17 21:35
fl0_idthen reboot and it should boot into m1n1 proxy mode. to do anything then, you will need a second machine with a usb c to a cable (or I guess c to c might also work)
#asahi · 2025-03-17 21:34
fl0_idamilie oh and also the t6030 PR is nicer now. So you could get https://github.com/step21/m1n1/tree/t603x-bringup (recursive) then make, reboot to your new macos install, then shutdown, start into recovery by holding power. Then in recovery make sure you know where you m1n1 binary is and do kmutil configure-boot -c m1n1-stage1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v <path to your OS volume>
#asahi · 2025-03-17 21:30
fl0_idamilie don't think you have to apologize :) for documentation, could also be useful to reorganize things, like for me installing a second container manually, installing m1n1 from recovery, and then doing stuff with it is all in the docs, but not necessarily all easily accessible. so if you think of a better structure or a quick start for development maybe that would be cool
#asahi · 2025-03-16 09:51
fl0_idmonthebiff like iirc it would be missing because you cannot run wine on normal asahi, just inside muvm? so any changes like winetricks would have to go in there I assume and then presumably. be configured correctly
#asahi · 2025-03-15 23:47
fl0_idanyway gn8 for now

plus ›