#asahi · 2026-09-09 08:39
barusuIs that something I can help with?#asahi · 2026-09-09 08:25
barusuI can get it to detect the audio device, but no audio is sent to them even when media plays. I don't know what stars aligned yesterday that made it work after switching between audio devices using wiremix#asahi · 2026-09-09 08:07
barusuon mbp m1#asahi · 2026-09-09 08:07
barusuSo, on fairydust, hdmi audio does not seem to work after sleep/hotplug. don't know which.#asahi · 2026-09-08 21:33
barusuNiklasReimer[m]: there were recent fixes indeed. I updated to fairydust v7.1.12 and it works!#asahi · 2026-09-08 20:16
barusuAm I missing something here? Currently running fairydust v7.1.6#asahi · 2026-09-08 20:15
barusuI passed the appledrm.hdmi_audio=1 arg to my fairydust kernel and I can confirm it got applied through `cat /sys/module/appledrm/parameters/hdmi_audio` which returns `Y`. However, no audio device is shown on KDE for the external display#asahi · 2026-09-08 15:07
barusuJamesCalligeros[m]: thanks, any known caveats with enabling it? #asahi · 2026-09-08 07:31
barusuDoes fairydust not support audio at the moment?#asahi · 2026-08-07 10:14
barususicktriple[m]: yeah, I can relate. I do that all the time #asahi · 2026-08-06 20:25
barususilly mistake, wasn't pulling the right repo. I was pulling the parent repo that had the asahi kernel as a submodule :/#asahi · 2026-08-06 17:10
barusuCan I rebase fairydust changes on top of 7.1.6?#asahi · 2026-08-04 18:53
barusuThanks for letting me know!#asahi · 2026-08-04 18:20
barusuis the battery life on MBP M1 Pro expected to be worse than the base MBP M1? KDE estimates show 7hrs remaining at 65% for MBP M1 but only 6:25 hours at 100% on MBP M1 Pro.#asahi · 2026-08-03 20:35
barusuelisaado: thanks! any drawbacks doing this? #asahi · 2026-08-03 20:06
barusuhow do I enable display notches on 14 inch m1 pro? #asahi · 2026-08-01 21:49
barusuwhen I click suspend in the start menu, the screen turns off and turns back on in 2 seconds with the login screen#asahi · 2026-08-01 21:48
barusuWhat would be a good way to report bugs with suspend issues on fairydust? #asahi · 2026-08-01 15:37
barusufl0_id: I guess you're right. I was under the assumption the mic was still exposed after the lid close#asahi · 2026-08-01 15:12
barusuOh, I see. I wished they didn't do it :(#asahi · 2026-08-01 14:00
barusuIs this for all the MBPs?#asahi · 2026-08-01 13:59
barusuAh, that's unfortunate. Thanks for letting me know.#asahi · 2026-08-01 13:57
barusuIs there any way to use the internal mic with the lid closed when an external monitor is hooked up#asahi · 2026-07-31 15:41
barusu7.1.5. Suspend seems to be misbehaving. My laptop wakes up immediately after clicking suspend. This doesn't happen on the official non-fairydust builds of 7.1.5#asahi · 2026-07-31 15:40
barusuI checked out and built fairydust couple of days back (7#asahi · 2026-07-30 06:41
barusuLarstiQ: thanks#asahi · 2026-07-30 06:23
barusumuvm seems to crash on linux 7.1.5 when launching steam#asahi · 2026-07-27 11:26
barusuguys, I have a GMK67 wireless mechanical keyboard which also seems to present itself as an Apple Keyboard. I currently use the swap fn and opt kernel module paramters for the hid_apple module. It does what I expect for the internal keyboard, but my external GMK67 gets it's keys wrongly swapped. Is there something I can do that only applies the kernel options for the internal keyboard?#asahi · 2026-07-25 11:11
barusu[ERROR tuxvdmtool] vdmtool: ControllerTimeout#asahi · 2026-07-25 11:11
barusu[INFO tuxvdmtool::cd321x] Busy Check Failed with VAL = 1934443606#asahi · 2026-07-25 11:11
barusu[INFO tuxvdmtool::cd321x] Busy Check Failed with VAL = 1934443606#asahi · 2026-07-25 11:11
barusu[INFO tuxvdmtool::cd321x] Rebooting target into DFU mode...#asahi · 2026-07-25 11:11
barusu[INFO tuxvdmtool::i2c] Safely opening failed ==> Forcefully opening device...#asahi · 2026-07-25 11:11
barusu[INFO tuxvdmtool] Using I2C bus:/dev/i2c-0 address:0x38#asahi · 2026-07-25 11:11
barusu sudo ./target/release/tuxvdmtool dfu#asahi · 2026-07-25 11:11
barusuOne difference though is something is affecting the internal state of the logic board though. Because tuxvdmtool dfu fails to enter dfu mode after the idevicerestore does its thing:#asahi · 2026-07-25 11:10
barusuthe same with the 13.5 ipsw#asahi · 2026-07-25 11:08
barusuOkay, just for info, building idevicerestore from master doesn't change anything. still the same error. usbmuxd does log some errors about libusb "ignoring udev action unbind". I will try the older ipsw now #asahi · 2026-07-25 11:01
barusuroger#asahi · 2026-07-25 11:00
barusuThis is for the iMac though. I verified with the board number that I have the A2442 logic board#asahi · 2026-07-25 10:57
barusu13.5 you mean the OS?#asahi · 2026-07-25 10:57
barusuon it#asahi · 2026-07-25 10:55
barusunot yet, it's from the nix-channel which builds the master from around 26.05#asahi · 2026-07-25 10:54
barusuYep#asahi · 2026-07-25 10:51
barusu14 inch#asahi · 2026-07-25 10:51
barusuUniversalMac_26.5.2_25F84_Restore.ipsw; this one. It was for MBP M1 Pro 2021#asahi · 2026-07-25 10:49
barususo i just get the error: "Device did not reconnect in DFU or recovery mode. Possibly invalid iBSS. Reset device and try again. Unable to place device into recovery mode from DFU mode"#asahi · 2026-07-25 10:48
barusuOkay, so an update. idevicerestore (I was just missing sudo before) now sends the iBSS to it but the device does not reconnect in recovery mode at all.#asahi · 2026-07-25 10:39
barusuI can put the board into debugusb and the corresponding device shows up for me in lsusb#asahi · 2026-07-25 10:37
barusuOh. But doesn't apple expose any interface for debugging bootup sequence on the logic board