#asahi-dev · 2026-09-04 11:00
jannauthe current fedora images are broken as well (to be replaced later today with fixed ones (hopefully)) but a dnf upgrade in fedora will install a fixed u-boot#asahi-dev · 2026-09-04 10:58
jannauno, that has no working usb on m3#asahi-dev · 2026-09-04 10:57
jannaumyria: are you trying the uefi boot option? The binary for that one still has to be fixed#asahi-dev · 2026-09-04 09:43
jannauyuka: send what's ready. the ordering argument for t603x/t8132 was only about available patches#asahi-dev · 2026-09-04 09:29
jannaushould be fine to use (a package update after configuring the system is strongly recommended) but we will update the install images tonight#asahi-dev · 2026-09-04 09:27
jannauif you want to test M3 devices you can just use `curl -L https://alx.sh/dev | sh` and enable expert mode#asahi-dev · 2026-09-04 09:26
jannaumyria: the installer itself can be built on macos (if it did not regressed) but isn't that interesting unless you want to add support for a currently unsupported device#asahi-dev · 2026-09-04 08:43
jannauI've tagged u-boot asahi-v2026.07-1 with M3* USB support#asahi-dev · 2026-09-03 18:44
jannausven: did you look into usb4net receive iommu issues? it looks like https://docs.kernel.org/7.1/networking/page_pool.html is made for this if I'm not mistaken#asahi-dev · 2026-09-03 09:28
jannauyes, works in the same way on m3 so the simple atc-phy compatible change is enough#asahi-dev · 2026-09-03 09:26
jannaupossibly (probably) caused by going through usb device mode for testing#asahi-dev · 2026-09-03 09:20
jannauseems to be an "hotplug" issue. devices are not detected at boot but if I replug them and run `usb reset` on u-boot's cmdline#asahi-dev · 2026-09-03 09:04
jannauusb is broken on t6020 as well. possibly an issue in my u-boot v2026.07 rebase, nevermind then#asahi-dev · 2026-09-03 08:57
jannauI've already copied the ATCPHY_EVT_USB2_CTL set to m1n1's usb_phy_bringup()#asahi-dev · 2026-09-03 08:56
jannaunot at all. soc device init works. I see the root hub in u-boot but no usb devices#asahi-dev · 2026-09-03 08:53
jannauany idea why usb2 host mode works in u-boot although USB2PHY_SIG_HOST does not appear to be set?#asahi-dev · 2026-09-02 20:16
jannaugood. I'll tag an installer-release#asahi-dev · 2026-09-02 20:15
jannaufirst problem was the missing "apple,t8122-atcphy" compatible. usb xhcis are now detected but devices aren't#asahi-dev · 2026-09-02 19:51
jannauvolume icons are fixed#asahi-dev · 2026-09-02 19:50
jannauplease do. I'm reasonably certain it should work but confirmation would be good#asahi-dev · 2026-09-02 19:35
jannauchaos_princess: did you had a chance to retest amkor bt firmware handling the in the dev installer? volume icons should be fixed (testing the KDE install right now)#asahi-dev · 2026-09-02 19:31
jannauusb in u-boot is broken on m3* (likely just missing compatibles)#asahi-dev · 2026-09-02 10:10
jannauthe uefi boot install was fine#asahi-dev · 2026-09-02 10:07
jannauI assumed it was safe while macos was still downloading#asahi-dev · 2026-09-02 10:06
jannaudon't update macos and do an asahi install at the same time. macos doesn't like that#asahi-dev · 2026-09-01 21:08
jannauso I guess that means I have to look at DP tunneling soon#asahi-dev · 2026-09-01 18:04
jannaumerged, we need to tag a new installer release, update the fedora package and ensure it ends up in the image#asahi-dev · 2026-09-01 17:54
jannauupdated kde and gnome images installed fine#asahi-dev · 2026-09-01 17:46
jannauhttps://github.com/AsahiLinux/asahi-installer/pull/439#asahi-dev · 2026-09-01 17:42
jannauchaos_princess: sigh, I can't read. it misses "texa-a.bin", that is very likely amkor and should be easy to fix. sorry#asahi-dev · 2026-09-01 17:09
jannauI've updated the images to today's build. at least the kde ESP volume id should be ok#asahi-dev · 2026-09-01 16:33
jannauvolume logo might be broken due to "curl -LO https://pagure.io/fedora-logos/blob/master/f/bootloader/fedora.icns"#asahi-dev · 2026-09-01 16:09
jannau"USI" for the -u suffix#asahi-dev · 2026-09-01 16:09
jannauyes, that's unhandled but use #asahi-dev · 2026-09-01 16:01
jannauhow did your previous install work? I have a faint recollection that we just renamed files#asahi-dev · 2026-09-01 15:56
jannauvolume icon is just 196 bytes on disk. probably an error during install image creation#asahi-dev · 2026-09-01 15:51
jannauno avd firmware is expected. nothing pulls it in yet, not sure if I even built it for f44 yet#asahi-dev · 2026-09-01 15:49
jannauafter fixing the EFI UUID in fstab?#asahi-dev · 2026-09-01 15:49
jannauI think so, no panel node so 100 DPI#asahi-dev · 2026-09-01 15:45
jannausame here#asahi-dev · 2026-09-01 15:41
jannaudoes it query for frimware with a different prefix than "-a" or "-u"?#asahi-dev · 2026-09-01 15:39
jannaubt firmware or just "failed to query codec capabilities"#asahi-dev · 2026-09-01 15:35
jannaugnome image works on t6030#asahi-dev · 2026-09-01 15:29
jannaukde image boots into emergency mode, might be firmware related as isp failed#asahi-dev · 2026-09-01 15:20
jannauthe custom boot partition icon seems to be broken#asahi-dev · 2026-09-01 15:11
jannauthe dev installer has now M3, M3 Pro/Max compatible Fedora-Asahi-Remix images#asahi-dev · 2026-09-01 15:11
jannauargh, you ment the no in the first message. yes that should have been now#asahi-dev · 2026-09-01 15:10
jannauI'm still at extracting root.img so the image / install might be broken (very unlikely though as my existing Fedora 44 install on the same device works and shouldn't contain non-distro packages anymore)#asahi-dev · 2026-09-01 15:03
jannaucurrently testing on j8122 so no confirmation that it works#asahi-dev · 2026-09-01 15:02
jannautest with `curl -L https://alx.sh/dev | sh` and say yes to expert mode