ChanServ changed the topic of #ubuntu-asahi to: Ubuntu-Asahi development | Github: https://github.com/UbuntuAsahi | Logs: https://oftc.irclog.whitequark.org/ubuntu-asahi
MasterDuke has joined #ubuntu-asahi
<MasterDuke> i just booted with the new kernel on my m2 13" air and my touchpad and wifi didn't work. the touchpad wasn't even found. unfortunately i forgot to save the dmesg output.
<MasterDuke> had to re-reboot into an older kernel
<tobhe[m]> ouch
<tobhe[m]> can you create an issue on github including which device that was?
<MasterDuke> sure, which repo?
<tobhe[m]> that would be the best yes
<tobhe[m]> if you have a dmesg log from the failed run that would also help
<MasterDuke> i don't currently, but i guess i can reboot and get one
<tobhe[m]> john-cabaj: ^
<tobhe[m]> maybe journalctl -b -1 to get the log from your last boot
<john-cabaj[m]> Right, first step is logs
<john-cabaj[m]> I'm still on gnome, but I'll see what I can dig up when you have more information
<MasterDuke> some logs added
<MasterDuke> while i'm here...what's this ibus panel notification i get every time i enter kde?
<tobhe[m]> Don't know about any notification but I use gnome
<john-cabaj[m]> Saw this in boot1.log
<john-cabaj[m]> `Mar 28 20:25:47 athena kernel: dockchannel-hid 24eb30000.input: Direct firmware load for apple/tpmtfw-j413.bin failed with error -2`
<tobhe[m]> that is suspicious yes
<tobhe[m]> and a few for brcmfmac too
<john-cabaj[m]> Which indicates firmware not found
<tobhe[m]> our firmware mechanism is a bit complicated
<john-cabaj[m]> Right, so it's not finding some firmware bins
<tobhe[m]> let me see if we log anything useful
<tobhe[m]> MasterDuke: have you tried more than once? just asking to make sure it wasn't some random hickup
<MasterDuke> yeah, that's why there are a couple log files
<tobhe[m]> makes sense 😄
<MasterDuke> i didn't go all the way into kde in all of them, some i just stopped at the login screen because the touchpad wasn't working their either
<john-cabaj[m]> Wonder if we can check if the firmware files are actually there in recovery mode or whichever
<tobhe[m]> yes, so two more things that would be helpful:
<tobhe[m]> 1. check if `find /lib/firmware/vendor/` and `mount | grep vendorfw` actually shows the firmware directory
<tobhe[m]> 2. if you could add `debug` to the kernel command line you should get a initramfs log in `/run/initramfs/initramfs.debug`
<tobhe[m]> oh and just to be sure: 3. which version of asahi-scripts is installed on your system
<tobhe[m]> I'll also comment on github
<tobhe[m]> it seems weird that only one kernel fails if it is an initramfs issue
<MasterDuke> the find and the mount both show stuff, i didn't have asahi-scripts installed
<tobhe[m]> so there's your issue
<tobhe[m]> install ubuntu-asahi, that should pull in asahi-scripts as dependency
<MasterDuke> i think it got removed by the kernel update or some other updates just prior
<tobhe[m]> /var/log/apt/history.log should tell you
<tobhe[m]> I hope apt doesn't just remove it silently without confirmation on dependency conflicts...
<MasterDuke> full-upgrade on the 26th. `Install: triforce-lv2:arm64 (0.2.0-1~asahi0.24.10, automatic)` and `Upgrade: tzdata:arm64 (2024b-1ubuntu2.2, 2025a-0ubuntu0.24.10), asahi-audio:arm64 (2.2-1, 3.2-1~bpo24.10.0~asahi0), m1n1:arm64 (1.4.17-1ubuntu0.1~asahi1, 1.4.21 -1ubuntu0.1~asahi1), tzdata-legacy:arm64 (2024b-1ubuntu2.2, 2025a-0ubuntu0.24.10), alsa-ucm-conf-asahi:arm64 (5-1, 7-1~bpo24.10.1)` and `Remove: asahi-scripts:arm64 (20
<tobhe[m]> and ubuntu-asahi is still there?
<MasterDuke> well, i just installed it and asahi-scripts
<tobhe[m]> I think john-cabaj also managed to end up in such a state when manually testing kernel
<tobhe[m]> s/kernel/kernels/
<tobhe[m]> we need to figure out how to prevent this I guess
<MasterDuke> i'll try rebooting into 6.13 now
MasterDuke has quit [Quit: Page closed]
<tobhe[m]> I hope it worked
<tobhe[m]> ah github says it works now 🙂
MasterDuke has joined #ubuntu-asahi
<MasterDuke> 6.13 is working. however, scrolling in firefox doesn't seem to be as smooth. and is there supposed to be a mic now?
<tobhe[m]> mic should be there yes
<tobhe[m]> unless you have a very old installation actually, I had to also update the firmware stub to get it working because mine is from 2022
<tobhe[m]> scrolling in firefox sounds like a mesa issue
<john-cabaj[m]> I noticed Firefox was a bit jittery. I enabled zswap late today and my brief interactions were better. Not sure if related.
<MasterDuke> i just installed this ubuntu in january i believe
<MasterDuke> i do have 24gb of ram, and this is just after a fresh reboot
<MasterDuke> most of the installed mesa packages are 9.0.2-1.1build1 or 25.0.0~pre20250221-1asahi2.24.10
<tobhe[m]> the default firefox snap or deb from their website?
<tobhe[m]> the snap uses a bundled version, it could be that this one stopped working with the latest kernel update
<MasterDuke> and i have zswap enabled, pool zstd/zsmalloc
<MasterDuke> `apt info firefox` shows 136.0.4+build1-0ubuntu0.24.10.1~mt1
<MasterDuke> which seems to match what help in ff shows
<tobhe[m]> ah so not the snap
<MasterDuke> i had tried to remove all snaps, but i believe some snuck back in
<tobhe[m]> you can open about:support in firefox and scroll down to Graphics. If that says something like "Mesa -- Apple M2" and not llvmpipe it should be accelerated
<tobhe[m]> or actually GPU #1 -> Description: Apple M*
<MasterDuke> oh! it is showing llvmpipe
<tobhe[m]> now that's weird. we have a pending mesa update so that might fix it
<tobhe[m]> still unexpected, my snap version seems to work (but as I said that uses a different mesa)
<MasterDuke> i have to leave and probably won't be able to return until tomorrow evening, but i'll check the irc logs if there are any further suggestions. and re the mic, it doesn't show up at all in the kde audio devices system settings
<tobhe[m]> ack, not sure if I can get the mesa update out this weekend but I hope I will
<tobhe[m]> mine had a apple_aop error in dmesg
MasterDuke has quit [Remote host closed the connection]
<tobhe[m]> before I fixed the firmware
phoenix has joined #ubuntu-asahi
<phoenix> What are the current known issues with Ubuntu asahi?
phoenix has quit []
tobhe_ has joined #ubuntu-asahi
tobhe has quit [Ping timeout: 480 seconds]
hwpplayer1 has joined #ubuntu-asahi
hwpplayer1 has quit [Remote host closed the connection]
hwpplayer1 has joined #ubuntu-asahi
hwpplayer1 has quit [Remote host closed the connection]
koubas has joined #ubuntu-asahi
<koubas> hi, a standard update of the system just got me to the state where the touch pad and wifi isn't working. apt install asahi-scripts helped, but no mic and gpu support was broken on 6.13, had to switch to 6.12. Just to clarify that MasterDuke's experience was not just a glitch and regular update is breaking things.
koubas has quit [Ping timeout: 480 seconds]
<tobhe[m]> concerning. /var/log/apt/history.log would be interesting to compare, in the previous case it broke a few days ago and the kernel upgrade yesterday just exposed it. I believe what caused it was a dependency mismatch with the packages in the ppa which lead to apt removing ubuntu-asahi
hwpplayer1 has joined #ubuntu-asahi
koubas has joined #ubuntu-asahi
hwpplayer1 has quit [Quit: sleep]
<koubas> yes, that seem like what happened to me https://gist.github.com/koubas/492ff74cd02d93598c0bf56ad906cf0b
<tobhe[m]> ah well "good" to see that it was a manual dist-upgrade
<tobhe[m]> I think at least the auto update would not remove anything
<tobhe[m]> sorry for the hassle!
<tobhe[m]> does the mic work for you after installing ubuntu-asahi again?
<koubas> Rigth, the first step to disaster was actually a dist-upgrade. No mic on 6.13, though. Graphics acceleration was also broken. I have still 6.13 installed, if you tell me where to look we might find out what's wrong
<tobhe[m]> do you see your mic at all if you open the sound settings in gnome?
<tobhe[m]> anything in dmesg maybe if you look for apple_aop
<koubas> I don't see it at all and there's no mention about apple_aop in dmesg. Maybe - do I have to install some extra package to enable the mic support or should it work out of the box?
<tobhe[m]> everything should work out of the box, you need 6.13 though
<tobhe[m]> if you have reinstalled the ubuntu-asahi package
<tobhe[m]> that should hopefully work with wifi and touchpad
<tobhe[m]> I wonder how this happens
<tobhe[m]> dpkg-deb --contents clearly shows:
<tobhe[m]> ./etc/apt/preferences.d/ubuntu-asahi.pref
<john-cabaj[m]> Probably a dumb question, but is the dot rendering that path relative?
<tobhe[m]> well it is an archiv
<tobhe[m]> s/archiv/archive/
<tobhe[m]> so relative from the root I guess
<koubas> I'm currently booted to 6.13. Reinstalling one of asahi-scripts or asahi-desktop helped with wifi and touchpad, I forgot to mention.
<tobhe[m]> don't forget to also apt install ubuntu-asahi
<tobhe[m]> that is the most important one and pulls in everything you need as dependecies
<tobhe[m]> if audio doesn't work yet the reason is probably a wrong pipewire version. The ubuntu-asahi package pins our ppa version with a higher priority than the archive version
<koubas> sorry, I meant unutu-asahi, no asahi-desktop. What can I do about Pipewire?
<tobhe[m]> depends, what version is currently installed? apt list --installed | grep pipewire
<koubas> 1.0.5-1ubuntu2.0asahi0
<tobhe[m]> that looks correct
<tobhe[m]> now that you are booted into 6.13, does sudo dmesg | grep apple_aop show any errors?
<koubas> still no mention about it at all
<tobhe[m]> weird. can you try running update-m1n1 manually and rebooting?
<tobhe[m]> this sounds like you might have booted with an old device tree for some reason, updating m1n1 should make sure it uses the latest ones
<koubas> we are talking about mic support on M2 Pro, are we? :)
<tobhe[m]> afaiu it should work on those too yes. let me double check though
<koubas> what does update-m1n1 do? Isn't it something M1 speciffic? I ran it, but didn't reboot yet :)
<tobhe[m]> m1n1 is the bootloader we use on all machines to bridge between apple's boot stuff and u-boot
<tobhe[m]> it loads the device trees which describe the hardware layout, which are then used by the kernel to determine which drivers to load etc
<tobhe[m]> that actually looks good
<tobhe[m]> do you see a mic in your audio settings?
<koubas> still no, but hey! Graphics acceleration is now fixed!
<tobhe[m]> aha, I think we might be missing a little fix to unblock your mic
<tobhe[m]> what does sudo cat /sys/firmware/devicetree/base/compatible print on your machine?
<koubas> apple,j414sapple,t6020apple,arm-platform
<koubas> I guess I can't change that without kernel recompilation
<tobhe[m]> looks like I actually might be wrong and it is still marked wip in asahi
<tobhe[m]> so we are actually up-to-date and not missing any upstream commits. must be something different
<koubas> ok, that's anticlimactic :( but thanks for your time, at least I have up to date system
<tobhe[m]> well I expect it will be fixed soon
ubuntu has joined #ubuntu-asahi
ubuntu is now known as Guest12400
Guest12400 has quit [Remote host closed the connection]
koubas has quit [Ping timeout: 480 seconds]