thelounge7571340 has quit [Remote host closed the connection]
danielnechtan has joined #asahi
Brill has joined #asahi
Brill has quit []
mindw0rk1 has quit [Ping timeout: 480 seconds]
danielnechtan has quit [Quit: WeeChat 3.4.1]
<derzahl>
Xesxen: just remove /etc/pipewire? I dont have any user config. I also created a new test user before to make sure it wasnt isolted to mine
<derzahl>
i havent messed with audio settings much since early alsa days
danielnechtan has joined #asahi
<Xesxen>
derzahl: my bash history is apparently gone from that time, but iirc I purged $HOME/.local/state/wireplumber/ and $HOME/.local/state/pipewire/media-session.d/
mindw0rk1 has joined #asahi
<Xesxen>
I think I installed wireplumber after running into that, but it's also part of the pipewire system /shrug
<derzahl>
ok, had $HOME/.local/state/wireplumber/
<derzahl>
removeed /etc/alsa and /etc/pipewire too. gonna just reinstall all the packages for good measure
<derzahl>
i couldve sworn that pipewire wasnt installed at all on asahi originally. i remember just pulse. then did a system update that pulled all the pipewire stuff in and then nothing worked
<derzahl>
but i looked and apparently pipewire has been default on arch for a couple years i think?
<derzahl>
ok, lets see. just gonna reboot
derzahl has quit [Remote host closed the connection]
derzahl has joined #asahi
<derzahl>
was worth a try, but no change :(
<derzahl>
this line seems odd to me though: cs42l42 2-0048: CS42L42 Device ID (42A83). Expected 42A42
danielnechtan has quit [Quit: WeeChat 3.4.1]
danielnechtan has joined #asahi
danielnechtan has quit []
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
ifthenelse has quit [Quit: Ping timeout (120 seconds)]
thelounge7571340 has quit [Remote host closed the connection]
amarioguy has quit [Quit: Leaving]
amarioguy has joined #asahi
adryzz has joined #asahi
Core2080 has quit [Read error: Connection reset by peer]
bestouff has quit [Read error: Connection reset by peer]
bestouff has joined #asahi
q3k has joined #asahi
LinuxM1 has quit [Ping timeout: 480 seconds]
amarioguy has quit [Ping timeout: 480 seconds]
amarioguy has joined #asahi
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
mindw0rk1 has quit [Ping timeout: 480 seconds]
mindw0rk1 has joined #asahi
mindw0rk has left #asahi [#asahi]
mindw0rk has joined #asahi
vx has quit [Quit: G-line: User has been permanently banned from this network.]
vx has joined #asahi
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
amarioguy has quit [Ping timeout: 480 seconds]
seb4nihel has quit [Ping timeout: 480 seconds]
amarioguy has joined #asahi
Stroller has joined #asahi
mindw0rk has quit [Read error: Connection reset by peer]
mewra has joined #asahi
blazra has quit [Remote host closed the connection]
blazra has joined #asahi
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
<derzahl>
jannau: yes, I am currently. Ill try the regular asahi kernel. previously i was using my own kernel compiled from asahi-linux git with a patched dts to enable sound. That stopped working after a non-kernel update
<derzahl>
ok, my kernel config doesnt have CS42L83. thanks, i will try adding that
amateurece has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
<derzahl>
anyone try that asahilina branch of the kernel? is there actually usable gpu acceleration?
<povik>
i hope we won't find out she's been pulling our leg
<povik>
she got me pretty excited
<derzahl>
i looked at the omgitworks branch and didnt notice any gpu code added but i maybe i missed it
<povik>
:D
<povik>
you probably missed it
<derzahl>
just saw rust driver framework stuff added in the commits
<derzahl>
could be that its hidding in there
<povik>
ah... some foreign script
<povik>
hopefully someone can decipher
<derzahl>
ill check it out again once i get my sound working
<povik>
the CS42L83 in config should do it ;)
<amateurece>
Hey, all! Do 3.5mm headphones work on m1pro models? Dmesg says "cs42l84 2-004b: Detected line-in" when I plug in my headphones, but there's no sound when I try to use aplay or speaker-test. Only a brief "pop". Wondering if I've got it set up wrong.
<derzahl>
hope so. used to have sound working perfectly and then it stopped. it was months ago though so i dont remember details. just that i booted back into a known previously working kernel at the time and still nothing
<mps>
amateurece: yes, it works fine for months
<povik>
amateurece: they do with the right kernel. which going by your message you have. you need to turn up 'Jack DAC' in alsamixer before we sort something out and ship the right configuration for userspace
<mps>
ofc, if you use proper kernel
<povik>
you wouldn't get "cs42l84 2-004b: Detected line-in" if you didn't have one
<jannau>
derzahl: yes, it works if you use the right subset of software. you either missed the GPU code or you're expecting the wrong kind of gpu driver
<amateurece>
povik: ah, yep. I figured it was just something like that. Works now, thanks very much!
<povik>
happy to be of help!
<jannau>
the opengl es parts are all in mesa / userspace
<povik>
jannau: i think derzahl just can't read rust :p
<jannau>
amateurece: it's currently not supported in the asahi distro but it will be soon
<jannau>
also I think it would be much harder to fake the working gpu driver than implementing it with the live streams
<derzahl>
i was just looking for added Kconfig options, but no, I cant read rust either:)
<marcan>
pretty sure those kconfig options won't show up until you have Rust support enabled, which requires the proper toolchain to be installed in the first place
<derzahl>
so the kernel just needs the rust hooks and then mesa needs to be recompiled?
<marcan>
no, there is an actual driver in the kernel
<marcan>
which you clearly missed :p
<jannau>
mps: please remember that this is the asahi distro support channel, please do not claim that things are supported which are not yet in the distro kernel
<derzahl>
awesome. cant wait to try it out
<jannau>
and I working for months is a little bit of a stretch for the cs42l84
<jannau>
-I
<marcan>
drivers/gpu/drm/asahi
<mps>
jannau: ahm yes, you are right
<marcan>
not exactly hard to find
<mps>
maybe I should leave this channel
<povik>
it's up to you but i think you shouldn't
<povik>
there's more than distro talk going on
<mps>
(I'm just trying to help people but sometimes I make mistakes, I know)
<derzahl>
probably my fault since i started talking about unsupported sound stuff in here. i can use asahi-dev in the future. i just didnt want to clutter up the channel since I myself am not an asahi-dev. just a tinkerer
<povik>
actually no, you were talking about a regression in asahi-dev compared to the 'stable' reference distro channel (as much as it can be called that)
<povik>
also #asahi-dev isn't for asahi-dev as in the testing set of packages in the reference distro
<marcan>
it's fine to talk about unsupported asahi-dev stuff, just don't say it's supported
<marcan>
it's upcoming
<povik>
i guess ^ that's the point here
<marcan>
the goal is to not confuse users, and also to not mindlessly encourage people to use asahi-dev because it is broken more often than not
<marcan>
(like right now)
<jannau>
mps: I don't think you should leave but please keep in mind that what's working on your system with your effort is not equal to the state of the asahi distro
<tpw_rules>
semi-related thought: would it be possible to in the future tag the PKGBUILDS repo with what's in the official asahi repositories?
<derzahl>
ok, thanks for clarifying. i was keep yapping in this channel then
amateurece has left #asahi [#asahi]
<marcan>
tpw_rules: yeah, I've been thinking of keeping two branches for that purpose
<jannau>
also the audio on devices with cs42l83 is not unsupported. it was previously working with a modified cs42l42 driver
<mps>
jannau: sorry, I had impression that the official asahi distro have current working kernel with all needed things enabled
<mps>
jannau: I didn't had 'my' kernel in mind when answered above question
<derzahl>
hm, was macbook air display backlight dimmer always broke using F1/F2 buttons or did i do that myself?
<ChaosPrincess>
under linux? i think its just unsupported
<derzahl>
yes
<derzahl>
ok, i vaguely recall it working when i first installed asahi. but wanted to double check
<derzahl>
for me F1 just turns the screen off and F2 turns it back on. no incremental adjustments
<ChaosPrincess>
yea, thats how its supposed to be rn
<jannau>
derzahl: yes, we currently only control the gpio to turn the backlight off and on
<derzahl>
any hacks to get the screen brighter?
<j`ey>
reboot into macos/recovery and turn it up
<derzahl>
its a bit dim for me
<derzahl>
oh ok, so whatever level was set last in OSX stays when booted into linux?
<derzahl>
ok, rebooting into my kernel with CS42L83 enabled and will try turning up brightness in recovery first
derzahl has quit [Remote host closed the connection]
derzahl has joined #asahi
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
<derzahl>
well i have headphone jack now at least! not sure why my modified t8103-j313.dts isnt working for full sound anymore
<derzahl>
arch/arm64/boot/dts/apple/t8103-j313.dts line #126, "status" = "okay";
<derzahl>
is something else needed now?
<j`ey>
there's a new macaudio.please_blow_up_my_speakers=true kernel option
<j`ey>
I mean, kernel command line option
<derzahl>
oh, great. thank you
<j`ey>
hm it might be 'snd-soc-macaudio.' not just 'macaudio'
<derzahl>
ill try both:)
<mps>
'snd-soc-macaudio.please_blow_up_my_speakers=1' works for me
<derzahl>
i wasnt able to adjust the display brightness in recovery and my osx install has long been boned
<derzahl>
is the backlight section of the dts tunable?
<jannau>
raw value was for me 0x008c0000 (m2 macbook pro 13"). 35840 and 9175040 both are way to high for raw nits
<derzahl>
still only shows headphones for output:(
<derzahl>
jannau: can i dump nvram from linux?
<jannau>
358.40 (divided by 100) could be correct
<jannau>
derzahl: no, at least not easily. you can read and mofy it from recovery though with the nvram command
<derzahl>
so yours was 0x008c0000 at full brightness?
amarioguy has quit [Ping timeout: 480 seconds]
<jannau>
no, at whatever brightness It was used at macos. ~70% could be correct. I changed it to 0x006c0000 and haven't noticed much of difference on the next boot
<tpw_rules>
it definitely behaves pretty strangely. mine is currently 0x0032b1f0
<tpw_rules>
max was 0x012c0000 but it didn't change for the top few pegs in the macos hud
<tpw_rules>
slightly above middle is 0x00a425aa
<derzahl>
cool, i will try playing with that after i can blow up my speakers
<derzahl>
any idea what im missing there?
<derzahl>
getting lots of error msgs
<derzahl>
apple-mca 238400000.i2s: ASoC: error at snd_soc_dai_hw_params on mca-pcm-1: -22
<derzahl>
repeated over and over
<jannau>
not sure it does anything at all for me and it certainly doesn't keep the macos brightness for me on the (m2 macbook pro)
<jannau>
I shut macos with brightness at barely readable and that did not stick
<jannau>
13" macbook pro might be a special case since the touchbar doesn't work in recovery, i.e. there is no way the user can correct a too low brightness
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
<derzahl>
povik: thanks! can i just restart gnome then?
<derzahl>
eh, ill just reboot. its fast enough
<povik>
logout/login should do the trick. you need to restart the userspace sound stack
derzahl has quit [Remote host closed the connection]
derzahl has joined #asahi
<derzahl>
hm, i used the PKGBUILD. still no speakers, just headphone. and new errors:
<derzahl>
apple-mca 238400000.i2s: ASoC: error at snd_soc_dai_hw_params on mca-pcm-1: -22
<derzahl>
[ 33.774926] Secondary: ASoC: error at __soc_pcm_hw_params on Secondary: -22
<derzahl>
[ 33.774927] Secondary: ASoC: error at dpcm_fe_dai_hw_params on Secondary: -22
<derzahl>
this is a macbook air m1 btw
<povik>
i don't think you edited the DT right
<povik>
since if you did edit the DT to enable speakers, the driver won't probe unless you pass snd-soc-macaudio.please_blow_up_my_speakers=1
<povik>
but it did probe for you to have headphones
<derzahl>
hm, i changed line 126 to "status" = "okay";
<derzahl>
i can triple check when i get back though
<derzahl>
what about using "dtb=" from kernal cmdline? I should have that functionality compiled into my kernel
tobhe has joined #asahi
ciggi_ has quit [Ping timeout: 480 seconds]
<mps>
is there 'dtb' option for kernel cmdline
<mps>
derzahl: to have new dtbs used you need to recreate new second stage m1n1+dtbs+u-boot
<mps>
idk how it works for asahi distro but iirc there is update script somewhere
<derzahl>
ive never tried using it. but there is a kernel option to enable "dtb=". i added it because, meh, why not. i usually use devicetree= from grub on my other arm laptop
<derzahl>
i thought it was an initcpio hook that added the dtb to m1n1 but im not finding it now
<mps>
interesting, never saw 'dtb' option in Documentation/admin-guide/kernel-parameters.txt
<derzahl>
ok, really leaving for now
amarioguy has quit [Ping timeout: 480 seconds]
seb4nihel has joined #asahi
<sven>
the dtb has to be modified by m1n1, specifying it using any other way (uboot,grub, kernel, whatever) will break
dgb has joined #asahi
gladiac has quit [Quit: k thx bye]
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
<ayke_>
jannau: I found that when the brightness changes due to automatic brightness changes in MacOS, it doesn't always stay at a reboot. But when I change it manually, the brightness appears to stick.
amarioguy has joined #asahi
___nick___ has quit [Ping timeout: 480 seconds]
compassion has quit [Read error: No route to host]
compassion has joined #asahi
Stroller has quit [Ping timeout: 480 seconds]
compassion has quit [Read error: No route to host]
compassion has joined #asahi
compassion9 has joined #asahi
compassion has quit [Ping timeout: 480 seconds]
compassion9 is now known as compassion
confusomu has quit [Quit: leaving]
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]
compassion3 has joined #asahi
compassion has quit [Ping timeout: 480 seconds]
compassion3 is now known as compassion
Stroller has joined #asahi
opticron has quit [Ping timeout: 480 seconds]
chipxxx has joined #asahi
kensan has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
SSJ_GZ has quit [Ping timeout: 480 seconds]
seb4nihel has quit [Quit: Leaving]
kensan_ has joined #asahi
amarioguy has joined #asahi
opticron has joined #asahi
kensan has quit [Ping timeout: 480 seconds]
thelounge7571340 has joined #asahi
thelounge7571340 has quit [Remote host closed the connection]