ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
<liv>
chadmed: I installed mesa::asahi, how do I build it into the kernel?
<liv>
I'm sorry for my many questions, but I hope to end up with a working system and to be able to do this myself :P
VeeBop8 has joined #asahi-alt
lynndotpy9 has joined #asahi-alt
lynndotpy has quit [Read error: Connection reset by peer]
lynndotpy9 is now known as lynndotpy
zzywysm has quit [Ping timeout: 480 seconds]
VeeBop has quit [Ping timeout: 480 seconds]
VeeBop8 is now known as VeeBop
<liv>
I am hesitant to try and replace my kernel in /boot because I don't trust myself :P
<j`ey>
liv: install a second one
<j`ey>
as in, dont overwrite that one
kidplayer666 has quit [Quit: Connection closed for inactivity]
<liv>
Can I just run `doas make install -j10`?
john-cabaj has quit [Remote host closed the connection]
john-cabaj has joined #asahi-alt
<liv>
Also, is there a Matrix-bridge to this room?
<liv>
I am currently in a tmux window SSH'd into a server that has a tmux window running in the background running irssi
<liv>
I'd like to have a browser to be able to open links when needed :P
<liv>
if not, curl is also okay-ish for that...
zerdox has joined #asahi-alt
<zerdox>
janneg, chadmed: i found that both of available 6.6 kernels break speakers volume control for me. it was and still working on 6.5. compiling both using same config, just updated some rust things because kernel required to upgrade them. do you have any ideas? i sent a strace of alsactl above
<liv>
I'll continue tomorrow, good night people :)
<liv>
1:35 am here :P
<j`ey>
liv: no bridge
chadmed_ has joined #asahi-alt
<chadmed_>
liv: you dont build mesa into the kernel. mesa is the userspace component of the graphics stack.
<chadmed_>
once you install rust aand bindgen, you need to rebuild the kernel with RUST=y and DRM_ASAHI=m
<chadmed_>
(then reinstall with the usual procedure)
<chadmed_>
zerdox: refer to above. speakersafetyd locks the kcontrols. there is no way around this and we will not be providing facilities for them to be unlocked. use pipewire.
<zerdox>
chadmed_: i do use pipewire, volume control just works on 6.5 but doesn't on 6.6. i use pavucontrol or pwctl to change volume
<chadmed_>
do you have asahi-audio installed?
<zerdox>
also as i mentioned before i can change volume of my right speaker, that's strange and i am sure it is not intended behavior
<zerdox>
yes i do
<zerdox>
latest one
<chadmed_>
which DE are you using
<zerdox>
none
<zerdox>
wayland and hyprland
<chadmed_>
please clear out /etc/wireplumber/ and /etc/pipewire/ if they exist and reinstall asahi-audio, wireplumber and pipewire
<chadmed_>
then reboot
<zerdox>
sure, i'll try now
<zerdox>
yay, that worked
<zerdox>
chadmed_: thank you :)
<zerdox>
ohj
<zerdox>
ohjj
<zerdox>
no, now i only got dummy output
<chadmed_>
i might need to push a release of asahi-audio to the overlay
<chadmed_>
what machine do you have?
<zerdox>
air 2020
<chadmed_>
run `echo -n "J313" | sudo tee /sys/class/sound/card0/id` and then log out and log back in
zerdox has quit [Read error: No route to host]
eiln has joined #asahi-alt
jeisom has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Quit: Quit]
chadmed_ has quit [Quit: Page closed]
kidplayer666 has joined #asahi-alt
<marcan>
< yuka> also when I unload and load the snd_soc_macaudio again my system sometimes locks up <- unloading modules is basically completely untested and expected to be broken in all sorts of ways :p
<marcan>
< yuka> I updated to kernel asahi-6.6-9, speakersafetyd 0.1.7, asahi-audio e1ccf5f. With a freshly booted system the speakers are unlocked, then once I start playing something they immediately become "Speaker volumes locked: Lock timeout" <- IIRC this happens when the routing is configured wrong, which means PW/ALSA UCM didn't do its job.
<marcan>
note that with bare ALSA it's expected not to work out of the box right now, you need to manually poke the routing settings in alsamixer first (UCM does this when using PW)
<marcan>
I need to figure out what to do about the alt routing modes, but honestly I'm tempted to just remove all that, it just makes everything more complicated once speakersafetyd is in the mix
kidplayer666 has quit [Quit: Connection closed for inactivity]
kujeger has quit [Ping timeout: 480 seconds]
<liv>
chadmed: Is that `CONFIG_HAVE_RUST=y`?
<liv>
DRM_ASAHI does not exist in my kernel's .config file (took the one from you)
<mps>
liv: it is auto if rust installed and run `make {menu,n}config}`
<liv>
wdym?
<mps>
it is set by make config if rust is intalled on machine
<mps>
I have bitten few times with this when I don't rust in kernel and have it installed
<mps>
don't need*
<liv>
after running `doas make {menu,n}config` I did not get anything matching `ASAHI` inside the document
<ChaosPrincess>
did you enable config_rust
<liv>
`CONFIG_HAVE_RUST=y`
<ChaosPrincess>
no, specifically config_rust
<liv>
That's not there
<liv>
Wait I'll upload my kernel config
<mps>
liv: '{menu,n}' means one of this
<ChaosPrincess>
don't bother
<ChaosPrincess>
can you run make menuconfig and search for "RUSt"
<mps>
so 'make menuconfig' or 'make nconfig'
<ChaosPrincess>
and say which options matched
<liv>
https:/0x0.st/PYPV.txt
<liv>
I did that
<liv>
and none appeared
<ChaosPrincess>
run `make rustavailable`
<liv>
Rust compiler `rustc` is too new. This may or may not work.
<ChaosPrincess>
anything else?
<liv>
Rust bindings generator `bindgen` is too new. This may or may not work.
<liv>
then it fails with error 1/error 2
<liv>
Wait I'll get on my desktop so I can ssh in and copy/paste
<j`ey>
basically overriding the mesa/asahi driver to change the supported version
matteo has quit [Remote host closed the connection]
millenialhacker has quit [Quit: Konversation terminated!]
millenialhacker has joined #asahi-alt
<yuka>
I just got the speakers working correctly(?) for the first time on my MacBook Pro (14-inch, M1 Pro, 2021) on NixOS. The issues was indeed the Alsa UCM config not being visible to pipewire/wireplumber correctly. This sounds amazing!
<liv>
j`ey: github issue thingy didn't work, going to try the reddit solution now
millenialhacker has quit [Remote host closed the connection]
jacksonchen666 has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-alt
millenialhacker has quit [Remote host closed the connection]
millenialhacker has joined #asahi-alt
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi-alt
millenialhacker has quit [Remote host closed the connection]
millenialhacker has joined #asahi-alt
<liv>
firefox too :)
<j`ey>
wee
<sam_>
leio: let's talk tomorrow about how to handle ffmpeg, but no news on the gcc side
millenialhacker has quit [Read error: No route to host]
millenialhacker has joined #asahi-alt
millenialhacker has quit [Remote host closed the connection]
millenialhacker has joined #asahi-alt
tpz has joined #asahi-alt
DevEthann has joined #asahi-alt
DevEthann has quit []
DevEthann has joined #asahi-alt
DevEthann has quit []
DevEthann has joined #asahi-alt
DevEthann has quit [Remote host closed the connection]
DevEthann has joined #asahi-alt
DevEthann has quit []
<liv>
How does sleep work exactly? Is that a command, can I create a rule that makes my laptop sleep when I close the lid? Does it automatically resume when I open the lid? etc
rino has joined #asahi-alt
<j`ey>
it does it in a 'normal' linux way. systemd can automatically handle that
<j`ey>
I dont exactly know how systemd works it out, but there's SW_LID event that it listens for