#asahi · 2026-02-06 21:04
jannauif we get the debugusb uart to work it'll much easier. I think the server image has cockpit installed but you still need to get through the terminal based initial setup to set a root password#asahi · 2026-02-05 21:28
jannau15 minutes for sci-electronics/kicad-9.0.2-r1 on a m1 max#asahi · 2026-02-05 20:23
jannauare you using the fedora/redhat make commands to build the rpms? Does the config has CONFIG_GPIO_MACSMC=m?#asahi · 2026-02-05 20:22
jannauit has not. still waiting for libkrun/libkrunfw compatible with 6.18 to land#asahi · 2026-02-04 20:12
jannauyuka: disconnect command in https://github.com/AsahiLinux/tuxvdmtool/tree/port-disconnect will simulate a port disconnect. pushed as branch since I think this is better suited for the kernel driver#asahi · 2026-02-01 10:59
jannaubart: The issue looked resolved according to the comments. just because you have similar symptoms does not mean it is the same issue#asahi · 2026-02-01 10:58
jannauother possiblilty is using the hypervisor, see https://asahilinux.org/docs/sw/tethered-boot/#asahi · 2026-02-01 10:58
jannaudeadbeef: in the case you read logs. The easiest way would be to using the serial port. either from macos on the m4 via macvdmtool. Setup is annoying on macos side (but there might have been a change in macos 26 (I could be mixing that up or haven't paid enough attention))#asahi · 2026-01-31 23:17
jannauwhen does it freeze? during the execution in the initramfs?? before? after?#asahi · 2026-01-31 23:14
jannauis there anything prior in the log? filming it in slow motion might be helpful (usually only to decipher the actual issue and not to spot that there is something wrong)#asahi · 2026-01-31 22:57
jannauplease try with "nomodeset module_blacklist=tps6598x". the latter will disable both ports. that should confirm if the assumption that it's related to the type-c port#asahi · 2026-01-31 22:38
jannautry with nomodeset#asahi · 2026-01-31 22:36
jannauwhen it freezes the display stays on with kernel messages?#asahi · 2026-01-31 22:36
jannaucan you try to boot with nomodeset in the kernel command line? it's possible that loading the display driver hides crucual messages#asahi · 2026-01-31 22:34
jannauno, boot.bin needs to be refreshed after updating the kernel (or m1n1 or u-boot)#asahi · 2026-01-31 22:32
jannauwhen do they freeze? during boot? with dmesg you mean the kernel log during boot?#asahi · 2026-01-31 22:31
jannauhas you the secret os you're using a mechanism to update the embedded device tree in $ESP/m1n1/boot.bin? i.e. runs update-m1n1 I don't see how this could cause issue beyond non working usb-c ports#asahi · 2026-01-31 22:29
jannauif there is nothing in dmesg how did you conclude that the second port is responsible for the completely different looking issue#asahi · 2026-01-31 22:27
jannauwith now you mean with a 6.18.x kernel? That is not yet available for fedora#asahi · 2026-01-31 22:20
jannauis there anything special to report on the device? i.e. was it serviced?#asahi · 2026-01-31 22:17
jannauis this a normal fedora-linux-remix install?#asahi · 2026-01-31 22:17
jannauany indication what goes wrong?#asahi · 2026-01-31 22:09
jannauah#asahi · 2026-01-31 21:56
jannauI still do not understand the error. also can you just not put the charger into the other port#asahi · 2026-01-31 12:55
jannaua usb-c displayport adapter or cable would work#asahi · 2026-01-31 12:55
jannaubennofs: probably not. Apple's firmware on the USB Type-C port controller will negotiate thunderbolt mode if the partner is thunderbolt capable without a way to override it. fairydust support only DP altmode#asahi · 2026-01-28 21:42
jannauyou can step beck yourself with `journalctl -k -b-N` with N bein n-th last boot#asahi · 2026-01-28 21:37
jannauthere should be a section "## Kernel log (last boot)"#asahi · 2026-01-28 21:30
jannauthe timestamps at the beginning are most likely wrong because the real time clock driver isn't loaded yet#asahi · 2026-01-28 21:08
jannauviolette: using linux.py with --u-boot? see https://github.com/AsahiLinux/m1n1/pull/537 and https://github.com/AsahiLinux/u-boot/commit/4411224f218ee67526f74d10cd3b3a7cd70ff2ad#asahi · 2026-01-26 19:44
jannauthe fragile is probably still justified because it doesn't see much use/testing#asahi · 2026-01-26 19:40
jannauat least for multi-channel audio#asahi · 2026-01-26 19:40
jannauI think I improved it to make at least "very" unjustified. it's mostly just not a priority. the architecture is weird/annoying and it iirc requires some user space bits#asahi · 2026-01-26 18:35
jannauthere should be MTD device with label "m1n1_stage2.log" which contains what the name suggests#asahi · 2026-01-26 18:34
jannauNekoCWD: enable CONFIG_MTD_PHRAM#asahi · 2026-01-26 18:24
jannauprobably missing devicetree changes for audio. I'll take a brief look in the next days#asahi · 2026-01-26 17:25
jannauI think dcp audio should work if enabled#asahi · 2026-01-24 21:14
jannauare you booting with the dtb from 6.18 kernel? This is better discussed in #asahi-alt #asahi · 2026-01-24 21:08
jannaudoes the issue go away if you plug the usb hdd after the kernel has booted (with a long rootwait)?#asahi · 2026-01-24 21:07
jannaunote that there is no official asahi-6.18.* build yet#asahi · 2026-01-23 16:22
jannaumonthebiff: I think it's kdeconnectd#asahi · 2026-01-23 16:21
jannauif nobody else will I guess I'll start looking into the high prio socket optoion and vendor hci commands for audio streams#asahi · 2026-01-21 11:41
jannaupoints towards code added in asahi-6.18*#asahi · 2026-01-21 11:18
jannaudoesn't make sense for battery powered devices though#asahi · 2026-01-21 11:18
jannauyes#asahi · 2026-01-21 11:18
jannauI use that for my mac mini testing machine so that I don't have to press the power buttom because it's inconvenient#asahi · 2026-01-21 11:17
jannauthe devices has to be powered on when you cut power. otherwhise it remains powered down#asahi · 2026-01-21 11:15
jannauthat's how apple designed this feature#asahi · 2026-01-21 11:14
jannauyou have to cycle power externally#asahi · 2026-01-21 11:14
jannauyes