#
#asahi · 2026-10-30 01:45
monthebiffsurely the --update-kernel=ALL in
#asahi · 2026-10-30 01:45
monthebiffsystem has done that update thing where the notch display has reset.
#asahi · 2026-10-29 15:30
AnEagle[m]It's absolutely not thunderbolt, it's a 15 dollar Amazon dongle
#asahi · 2026-10-29 15:28
sven-s
#asahi · 2026-10-29 15:28
sventhat's expected, neither display port nor pcie tunnelings works yet
#asahi · 2026-10-29 15:24
AnEagle[m]Interestingly, it shows up in gnome settings, it just doesn't display anything
#asahi · 2026-10-29 15:24
AnEagle[m]And... It works ! I do however have another dock that's broken, but I honestly don't care enough, unless this is of interest to you
#asahi · 2026-10-29 13:28
jannaulook at arch/arm64/configs/asahi.config you probably need CONFIG_RESET_APPLE_CIO=m and CONFIG_USB4_APPLE_SOC=m
#asahi · 2026-10-29 13:25
AnEagle[m]Ah, that's probably it
#asahi · 2026-10-29 13:25
JamesCalligeros[m]Make sure you have enabled the new usb kconfig options
#asahi · 2026-10-29 13:24
AnEagle[m]I think I'll just rebuild lol
#asahi · 2026-10-29 13:24
AnEagle[m]Oh, the whole usb stack is broken on this kernel
#asahi · 2026-10-29 13:22
AnEagle[m]The mystery thickens. My usual dock, a random Chinese dock with a single port, worked in 7.1.9 fairydust, and is broken here (but at least usb works on it)
#asahi · 2026-10-29 13:09
yurixblasdo: NetBSD already has some M1 support (or at least I've noticed code for in the kernel)
#asahi · 2026-10-29 13:07
AnEagle[m]And yes usb works without fairydust
#asahi · 2026-10-29 13:06
AnEagle[m]Rebuilt with dracut and it works again
#asahi · 2026-10-29 13:06
jannaueasier solution might be to update the kernel. 7.2 is available since yesterday
#asahi · 2026-10-29 13:05
jannaunot directly related to initramfs but to the kernel you want to boot. running update-m1n1 is most likely not enough. the uses the DTBs in /boot/dtb (a symlink). If that still points to the new kernel it won't help
#asahi · 2026-10-29 12:59
AnEagle[m]jannau: Yeah, dracut is also failing occasionally, do I need to run update-m1n1 if I rebuild the initramfs?
#asahi · 2026-10-29 12:59
jannauthe fairydust kernel used is based on 7.2? not aware that any DTS change should affect internel keyboard though
#asahi · 2026-10-29 12:57
AnEagle[m]Can't enter my password for luks
#asahi · 2026-10-29 12:57
AnEagle[m]Now the internal keyboard doesn't initialise on 7.1
#asahi · 2026-10-29 12:51
jannaudoes USB work on a non-fairydust kernel?
#asahi · 2026-10-29 12:51
jannauit is USB 3.2 Gen2 Type-C
#asahi · 2026-10-29 12:45
AnEagle[m]Oh and USB is also failing to initialise, I'm only getting power delivery
#asahi · 2026-10-29 12:45
AnEagle[m]It's a dell WD19S
#asahi · 2026-10-29 12:44
AnEagle[m]Don't believe it is
#asahi · 2026-10-29 12:44
chaos_princessis it a thunderbolt dock
#asahi · 2026-10-29 12:32
AnEagle[m]How can I debug a dock not working in fairydust ? It's a multi-display dock, but I'm only plugging in one monitor
#asahi · 2026-10-29 11:31
blasdoGood idea
#asahi · 2026-10-29 11:30
chaos_princessand there is an asahi port of openbsd, so you can peek at their homework
#asahi · 2026-10-29 11:30
blasdoyes, it do. but I can create another port. For try
#asahi · 2026-10-29 11:30
chaos_princesshttps://wiki.netbsd.org/ports/evbarm/raspberry_pi/
#asahi · 2026-10-29 11:30
chaos_princessnetbsd already works on raspi, no?
#asahi · 2026-10-29 11:28
blasdoNetBSD, has a really good comunity in port things to other platforms. I loved see it working in my wii.
#asahi · 2026-10-29 11:27
blasdo(Of course I'll try to do the port in first case for a documented plataform, a raspi, but I would to try things in powerful computers)
#asahi · 2026-10-29 11:26
chaos_princesswhich os are you trying to port btw?
#asahi · 2026-10-29 11:26
blasdoOk. In this case speakers would be the only part that I'll not try to implement.
#asahi · 2026-10-29 11:24
chaos_princessyes, for speakers. everything else should be software-recoverable
#asahi · 2026-10-29 11:22
blasdoI'm trying to understand some things about how can I create a port to another OS to mac using some of the asahi tools and documents. Basically for fun (I want to know how can I create some things and how can I do some reverse enginering without LLM usage). The problem is that I'm not really sure of the risks. Can I damage my computer permanently trying to implement a driver?
#asahi · 2026-10-29 11:22
blasdoHello, how are you?
#asahi · 2026-10-28 08:35
jannauthat was years ago so might be worth retesting. not sure I expect changes given that kde hasn't yet switched to upower for managing the thresholds (that would get rid of the authentication for changing them)
#asahi · 2026-10-28 08:33
chadmedlmao ok now the unidentified nick works....
#asahi · 2026-10-28 08:32
chadmedMichaelReeves[m]: oh you have a list like that too
#asahi · 2026-10-28 08:32
MichaelReeves[m]I remembered one of them was ok and the other wasn't, but must have gotten it the wrong way round. that's annoying that its needed
#asahi · 2026-10-28 08:32
chadmed_MichaelReeves[m]: oh you have a list like that too
#asahi · 2026-10-28 08:31
jannaucharge_control_start_threshold is broken. it is only there since some software (iirc kde) expected charge_control_end_threshold and charge_control_start_threshold
#asahi · 2026-10-28 08:29
jannauI think charge_control_end_threshold is ABI wise ok. The driver is alloved to not support arbitrary values and is expected to round to next supported one
#asahi · 2026-10-28 08:25
MichaelReeves[m]it's something on my endless list of things I intend to get around and fix
#asahi · 2026-10-28 08:25
MichaelReeves[m]yes, I don't think the functionality should be removed but (IMO) it shouldn't use the names of things which have a defined ABI and completely not follow that and fake values etc.

plus ›