#
#asahi-alt · 2025-04-11 06:50
flokliHm, it is 3.3 and 8, so that might not be it
#asahi-alt · 2025-04-11 06:45
chadmedand it should be version 8
#asahi-alt · 2025-04-11 06:45
chadmedsorry not asahi-audio, alsa-ucm-conf-asahi
#asahi-alt · 2025-04-11 06:45
chadmedasahi-audio should be version 3.2 at least (3.3 ideal) but apart from that the rest of UCM is just standard pipewire/alsa functionality and shouldnt be affected by package versions
#asahi-alt · 2025-04-11 06:43
floklichadmed: I'm trying to figure out which part is still missing / outdated from the NixOS packaging. ucm not being applied might be the right hint, I'll dig into that. Thanks!
#asahi-alt · 2025-04-11 06:41
chadmedleio, sam_: the mesa driver will be enabled upstream for 25.1 which is why we can do that. might leave it until the kernel uapi changes flow through to linux-asahi though
#asahi-alt · 2025-04-11 06:38
chadmedplease do not try re-engineering the matching scheme. what exists is correct and your system is what is incorrect
#asahi-alt · 2025-04-11 06:38
chadmedtheyre not. the UCM profile is not being applied
#asahi-alt · 2025-04-11 06:36
flokliBut I'm not sure if the devices I'm seeing are actually the correct ones or not
#asahi-alt · 2025-04-11 06:36
floklichadmed: I was thinking about trying to match on alsa.id or something similar, which seems to be more reliable
#asahi-alt · 2025-04-11 06:34
chadmedi need more hardware :(
#asahi-alt · 2025-04-11 06:34
chadmedsomeone else reported a similar failure mode and i could not for the life of me work it out
#asahi-alt · 2025-04-11 06:33
chadmedflokli: im not terribly sure tbh. the ucm files are correct and working so i dont know why they wouldnt be getting picked up.
#asahi-alt · 2025-04-11 06:04
floklichadmed: what's deciding about these names, how do I debug this?
#asahi-alt · 2025-04-10 20:48
chadmedflokli: if the api alsa path is hw:0 and not J314HPAI then something is wrong
#asahi-alt · 2025-04-10 20:43
n3phI am currently compiling non-stop and have a look on `powertop` in parallel. Why do I see so much idle state, or might it be inaccurate? https://pastebin.com/rExjX6MY
#asahi-alt · 2025-04-10 16:47
jannausam_: it's merged https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33984
#asahi-alt · 2025-04-10 16:44
flokliis there multiple api.alsa.path that can be matched on, and if so, how do I see which ones exist?
#asahi-alt · 2025-04-10 16:42
flokliwpctl inspect says alsa.card_name = "MacBook Air J413" and api.alsa.path = "hw:0"
#asahi-alt · 2025-04-10 16:42
sam_chadmed: he may be open to a draft PR to discuss stuff
#asahi-alt · 2025-04-10 16:42
sam_chadmed: as long as it's upstream -- I wouldn't expect Matt to necessarily merge it if it's not yet
#asahi-alt · 2025-04-10 16:42
floklichadmed: hmmh, I'm trying to debug why asahi-audio doesn't seem to properly do the microphone thing on my NixOS machine (J413). I poked around at `wpctl status` and `wpctl inspect`, as well as running pipewire/wireplumber with more debug being enabled, and it looks like api.alsa.path is not hw:AppleJ314,1 or hw:AppleJ314HPAI,0 (or I'm looking in the wrong place).
#asahi-alt · 2025-04-10 16:42
sam_chadmed: sounds good
#asahi-alt · 2025-04-10 16:33
mrvictorywinAnother question: how can I get the count of tweeters / woofers on either linux or macos? This repo: https://github.com/davidjo/snd_hda_macbookpro supports setting up 4 channels for 2 tweeters & 2 woofers but idk if I need a 4 channel setup as my mac has a different audio device (cs4208)
#asahi-alt · 2025-04-10 13:51
jannauleio: asahi-wip but not tags for a while
#asahi-alt · 2025-04-10 13:50
leio(to test)
#asahi-alt · 2025-04-10 13:49
leiochadmed: probably, if you beat me to it ;) but I don't know what kernel bits I need to match uapi
#asahi-alt · 2025-04-10 12:17
chadmedsorry that wasnt particularly clear, i mean mesa asahi (incl. honeykrisp)
#asahi-alt · 2025-04-10 12:16
chadmedwill i just make a PR against the live ebuild with what we're currently doing in the overlay?
#asahi-alt · 2025-04-10 12:16
chadmedsooooo sam_ and/or leio re getting asahi enabled upstream
#asahi-alt · 2025-04-10 10:51
chadmedmrvictorywin: in case you read the logs, you cant turn off the dsp on macos'
#asahi-alt · 2025-04-10 10:43
cy8aermrvictorywin: ah I see.
#asahi-alt · 2025-04-10 10:37
mrvictorywincy8aer: my goal by disabling DSP is to understand if it fixes the issues ie. buzzing I have on Linux. I basically want to see if I turn off DSP on macOS whether the audio output becomes similar to Linux. If it does then I can rule out driver problems.
#asahi-alt · 2025-04-10 08:30
cy8aerComponents involved implement the sound in asahi: asahi-scripts, alsa-ucm-conf-asahi, speakersafetyd, bankstown (lv2). For the speakers (we have three mics and beam forming is needed) there is another lv2 plugin triforce. These components are heavily using pipewire and wireplumber. More infos at https://github.com/AsahiLinux/asahi-audio
#asahi-alt · 2025-04-10 08:01
cy8aer... damages. Sound on linux laptops is a general problem and may be adapted from the asahi solution for other laptops. Since the macOS DSP has nothing to do with the asahi DSP, there is unfortunately nothing you can do for the Linux sound on the macOS side. And the DSPs are software, no hardware!
#asahi-alt · 2025-04-10 08:01
cy8aermrvictorywin: Asahi linux uses a DSP like macOS not _the_ DSP of macOS. Apple laptops have 2 or more speakers which have their own digital analogue converters. The DSP provides the crossovers like in old HIFI speakers. They also adjust the frequency spectra of the loudspeakers (Asahi as straight a frequency response as possible, macOS with more boom). Asahi also uses psychoacoustic effects to boost the bass and there is a limiter to avoid speaker...
#asahi-alt · 2025-04-10 05:40
mrvictorywinHow can I disable or modify the default DSP (digital sound processing) on macOS? The asahi-audio github page mentions macOS uses DSP to improve sound quality and Linux should also use DSP to match macOS. I have an Intel Mac (MB Air early 2015 running Arch) and audio quality on Linux is worse than macOS. I'm trying to find if the cause is lack of DSP or sth else ie. HDA commands.
#asahi-alt · 2025-04-06 20:27
chaos_princessyes, its broken
#asahi-alt · 2025-04-06 20:15
kaazooDid anybody else try the new FEX release yet?
#asahi-alt · 2025-04-06 20:15
kaazooHi, I updated FEX to version 2504 (released 2 days ago) and got this error: https://github.com/FEX-Emu/FEX/issues/4483
#asahi-alt · 2025-04-06 19:00
floklithat's a 2.4ghz only set of hotel wifi aps, if someone tries to reproduce.
#asahi-alt · 2025-04-06 19:00
flokliThere's a single "ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_DELTA error (-52)", and another later "ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -52", but it seems wifi overall ~works
#asahi-alt · 2025-04-06 18:59
flokliok, iwd seems to not make it be that unhappy
#asahi-alt · 2025-04-06 18:49
floklitrying to switch it to iwd and reboot, hoping this will make things better. Though it smells more like an issue with the kernel, or how wpa_supplicant is talking to it
#asahi-alt · 2025-04-06 18:43
flokliThat's 6.13.8-asahi, with NetworkManager (and wpa_supplicant)
#asahi-alt · 2025-04-06 18:42
floklias well as then after some time "brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring"
#asahi-alt · 2025-04-06 18:41
floklihmmh, getting loots of "brcmf_cfg80211_query_dcmd: Timeout on response for query command" and "brcmf_cfg80211_dump_station: BRCMF_C_GET_ASSOCLIST failed, err=-12/-5"
#asahi-alt · 2025-04-06 00:08
ece314378925355451680698427415Test
#asahi-alt · 2025-04-03 09:04
steevat the end of the day, it's your hardware, use it however you like as long as it suits your needs.
#asahi-alt · 2025-04-03 09:03
steevchaos_princess: offensively, sure, but we also have defensive tools

plus ›