#
…

2025-09-15

00:16lynndotpy has quit [Quit: bye bye]
00:17lynndotpy has joined #asahi-alt
00:19lynndotpy has quit []
00:20lynndotpy has joined #asahi-alt
01:56n3ph has quit [Ping timeout: 480 seconds]
02:05tobhe has joined #asahi-alt
02:11tobhe_ has quit [Ping timeout: 480 seconds]
03:04tobhe_ has joined #asahi-alt
03:07cylm has quit [Quit: WeeChat 4.7.1]
03:08tobhe has quit [Ping timeout: 480 seconds]
04:45craftyguyis it 'normal' for udisks to complain about "No transport address for 'apple-nvme'" (the nvme cli tool also complains about this)
06:43mpscraftyguy: you managed to install and run pmOS?
06:46mpscraftyguy: nvme-cli doesn't work on alpine with apple nvme in last year or two. earlier it worked but only for some command. I guess this is because there is no apple plugin in it
06:55nst has quit [Ping timeout: 480 seconds]
07:01sventhat sounds like a bug tbh
07:06nst has joined #asahi-alt
08:05chadmed has quit [Quit: Konversation terminated!]
08:08pjakobsson has quit [Remote host closed the connection]
08:10pjakobsson has joined #asahi-alt
08:27n3ph has joined #asahi-alt
08:38mpssven: bug in nvme-cli or kernel?
08:38svenno idea, could be either
08:38svensomeone needs to figure out where that error message comes from
08:39svenit’s probably some place in nvme-cli but it might just be an error propagated from the kernel
08:40mpsI will look at nvme-cli
08:40chaos_princesswhether a bug or not, it always did that
08:41n3ph has quit [Ping timeout: 480 seconds]
08:41svenit sounds like it’s trying to use some fabric code path
08:44svenI guess they might hardcode a check for pcie somewhere and assume it’s NVMe over network otherwise
09:03maettu1025 has joined #asahi-alt
09:10maettu102 has quit [Ping timeout: 480 seconds]
09:10maettu1025 is now known as maettu102
11:42n3ph has joined #asahi-alt
13:40n3ph has quit [Ping timeout: 480 seconds]
13:43n3ph has joined #asahi-alt
14:36n3ph has quit [Ping timeout: 480 seconds]
14:39craftyguymps: yeah I've been booting pmOS from external storage. I'm working on adding support to our installer for the macbook, the installer uses udisks to enumerate target storage devices and udisks not finding nvme (because of that transport error) is a problem :P
14:48john-cabaj has joined #asahi-alt
14:54svenprobably needs an additional strncmp(transport, "nvme-apple", 10) there
14:54n3ph has joined #asahi-alt
14:54svenand then possibly at other places too since it might just fail for the same reason later on then
14:55craftyguyOoooh ok I'll see if I can hack my way through it. I haven't had a chance to poke around yet
15:03kode545 has joined #asahi-alt
15:03kode54 has quit [Read error: Connection reset by peer]
15:07mpscraftyguy: I didn't used udisks so idk what is the solution
15:10opticron has quit [Read error: Connection reset by peer]
15:10opticron has joined #asahi-alt
15:11svenfix libnvme :D
15:11sveneverything that uses libnvme right now won't work with the apple controller
15:12svenbecause it assumes that it needs an address (think nvme over ethernet) for anything that's not pcie
15:17* craftyguyworking on fixing libnvme
15:17craftyguyOr, at least trying 🙃
15:17svenwant me to write you the patch?
15:17svenit's really just adding strncmp(transport, "nvme-apple", 10) to that if clause above
15:18craftyguyI already did that, and nvme list now works
15:18svennice, should be fine then
15:18craftyguyI was trying to understand the rest of libnvme to see if I need to also patch something else 🤷‍♂️
15:18svenideally create a PR on that project so that it's fixed for everyone :)
15:18craftyguyYeah of course :)
15:18sveni quickly read through the code, i think that's the only place required
15:18svenit's just trying to guard against later errors from the kernel from what i can tell
15:20mpsis BTI kernel config work on apple silicon
15:22mpscraftyguy: when you finish patch please post url, I want to add it to alpine
15:23craftyguythanks, that was going to be my next move 😛
15:24mpscraftyguy: thanks. iiuc you will add it to alpine?
15:25craftyguyAmazing, now udisks finds the local nvme 🥳
15:25svenprobably needs a singed-off-by and maybe an explanation why that changes fixes it
15:25craftyguymps: ya I was going to
15:26craftyguysven: I don't fully understand why it it shows as "apple-nvme", because apple silicon doesn't use pcie or ?
15:27svenit's a platform device there with a separate driver called "apple-nvme"
15:27n3ph has quit [Ping timeout: 480 seconds]
15:28craftyguyOk I'll attempt to explain that heh
15:32craftyguyK, done. Thanks for the help Sven :)
15:33craftyguymps: I'll send the patch to Alpine after I have some breakfast
15:33mpscraftyguy: please create MR for it
15:35craftyguyOf course 😛
15:38n3ph has joined #asahi-alt
15:39noisycoil[mds]sven: is the driver responsible for that already in the upstream kernel?
15:40svenyes, for a long time
15:45chadmed has joined #asahi-alt
15:51noisycoil[mds]Works for me on Debian too
16:04vimprovedheads up, mesa-asahi-flatpak is triggering lib protection on the update to libxml2 2.14.6: https://paste.gentoo.zip/qBJIwqCZ
16:06jannautime to purge it with fire?
16:08seb_ has quit [Quit: Konversation terminated!]
16:11chadmedim not sure how we would force portage to remove it automatically
16:11chadmedi think ill just write a news file
16:14mpscraftyguy: nice, now nvme-cli works on alpine
16:14jannauwe can't mask packages from the overlay?
16:15vimprovedchadmed: yeah no idea either
16:15chadmedi think if we mask it portage will just quit and tell you that you have installed masked packages right
16:16vimprovedportage wont quit in that case, it will just ignore the package and keep going
16:16vimprovedbut if you mask the package and remove it as a dependency from asahi-meta, then it'll just depclean
16:16vimproveder, it will get removed with a depclean
16:18vimprovedmy bad, it's not a dependency of asahi-meta in the first place
16:19vimprovedbut if you mask it will just show the user they have masked packages installed with the mask reason, and continue on
16:19vimprovedwon't actually prevent portage from working
16:23chadmedokay cool yeah like what md4sum just did last week
16:47seb_ has joined #asahi-alt
17:07seb_ has quit [Read error: Network is unreachable]
17:39craftyguyso... uh... Do I need a macbook with apple silicon to do the dfu recovery thing on an M2?
17:44jannauyou need an snapshot of idevicerestore though
17:45jannauthe latest release is (or was) too old to support apple silicon macs
17:45craftyguyahh ok. thanks for the pointer, I was starting to ask around for a friend with a macbook 😅
17:46jannaupartitioning mishap?
17:55mpsthere is idevicerestore 1.0.0 on alpine. don't know if it works
17:55craftyguyyeah that version is 5years old. I'm building it from git now
18:01chadmed1.0.0 is too ol
18:01chadmedeven the latest release on gh is too old, just build from main
18:02craftyguyya that's what I meant by "from git", building from main :)
18:02jannau1.0.0 is the latest release on github
18:25n3ph has quit [Ping timeout: 480 seconds]
18:26n3ph has joined #asahi-alt
18:38craftyguyk it picked up the macbook and seems to be downloading 15.6.1 for it
18:46chadmedits actually a pretty good bit of kit. i used it to back up my phone before coming to britain
18:46chadmedjust wish they actually did releases and such :p
18:48craftyguyis there some stated reason why they don't?
18:49chadmednot that i have seen
19:03craftyguydang, seems to just get stuck at 'Waiting for device to enter restore mode...' after it downloads, verifies, and sends some stuff(?) to it
19:04jannauare you sure the device is the the correct mode? is the display black?
19:05craftyguyit was in DFU mode when I started the tool, then while the tool was running the laptop rebooted(?) and showed an apple with an empty status bar under it for a bit. and just now it rebooted to the "support.apple.com/mac/restore" screen and the tool is still stuck on that message ^^
19:06craftyguyah it just now failed with "Device failed to enter restore mode."
19:12jannaumight be an issue with usbmuxd, not sure if that would fail earlier
19:14craftyguyhmm ok. The tool does see the macbook and recognize the type and that it's in DFU mode when it first runs
19:22jannauis usbmux running when you connect the macbook in dfu mode (and no other apple devices connected). I'm not sure if the DFU usb product id activates it
19:22jannauis usbmuxd running now?
19:24tpw_rulesyou can manually run usbmuxd with like sudo usbmuxd &
19:24tpw_rulesaccording to my notes your problem indeed sounds like usbmuxd is not running right
19:28craftyguyoh gosh, usbmuxd wasn't even installed. packaging fail. installed it and started it, and now it seems to be getting further
19:45kode545 is now known as kode54
19:59kit_ty_kate has quit [Remote host closed the connection]
19:59kit_ty_kate has joined #asahi-alt
20:05craftyguyrestore successful, thanks for the help y'all :)
20:18kit_ty_kate has quit [Remote host closed the connection]
20:18kit_ty_kate has joined #asahi-alt
20:21craftyguywas the UEFI-only image updated to have a recent m1n1 binary in it?
20:37craftyguyIf not, is there a patch I could send somewhere to do that? :)
20:42craftyguyoh yeah I guess it's still installing an old one, "os_package: uefi-only-20231220-1.zip"
20:42WoC has quit [Remote host closed the connection]
20:42WoC has joined #asahi-alt
20:52n3ph has quit [Ping timeout: 480 seconds]
21:21n3ph has joined #asahi-alt
22:08john-cabaj has quit [Ping timeout: 480 seconds]
22:27nela5 has joined #asahi-alt
22:33nela has quit [Ping timeout: 480 seconds]
22:33nela5 is now known as nela
…