marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
ydalton has quit [Ping timeout: 480 seconds]
thelounge986 has quit [Quit: Ping timeout (120 seconds)]
thelounge986 has joined #asahi
kidplayer666 has quit [Quit: Connection closed for inactivity]
baozich has joined #asahi
matteo has joined #asahi
<psanford_>
I seem to have corrupted my EFI partition. When booting into asahi I see the asahi logo but never make it to u-boot. running `ls` from macOS in that volume gives a `ls: fts_read: Input/output error`. I still get a directory listing though. Any suggestions on how I might repair this partition?
timokrgr has quit [Quit: User left the chat]
timokrgr has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
eiln has quit [Ping timeout: 480 seconds]
eiln has joined #asahi
thelounge986 has quit [Quit: Ping timeout (120 seconds)]
thelounge986 has joined #asahi
baozich1 has joined #asahi
baozich has quit [Read error: Connection reset by peer]
baozich1 is now known as baozich
hd73 has joined #asahi
<tpw_rules>
psanford_: are you on nixos?
Brainium has quit [Quit: Konversation terminated!]
<psanford_>
yes. i ran fsck_msdos to repair the partition. my boot.bin was then empty. i replaced that file and now can reach u-boot again. I should be able to repair the rest of the files now
<tpw_rules>
psanford_: okay. if you simply blow away the EFI partition and macOS stub then rerun the asahi installer and redo the UEFI install, then there are further repair instructions in the guide to rebuild everything
<tpw_rules>
this might also be in your best interests as it's the only way to get HDMI support currently as the macOS stub needs to be more recent than this August or so
ryec has quit [Ping timeout: 480 seconds]
john-cabaj has quit [Ping timeout: 480 seconds]
<psanford_>
good to know. this is on an m2-air so no hdmi port
ryec__ has joined #asahi
hd73 has quit [Read error: Connection reset by peer]
hd73 has joined #asahi
dylanchapell has quit [Read error: Connection reset by peer]
Raito_Bezarius has quit [Ping timeout: 480 seconds]
Luj has quit [Ping timeout: 480 seconds]
dylanchapell has joined #asahi
Raito_Bezarius has joined #asahi
Luj has joined #asahi
matteo has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
marvin24 has joined #asahi
hd73 has quit [Quit: leaving]
ciara has quit [Ping timeout: 480 seconds]
marvin24_ has quit [Ping timeout: 480 seconds]
EdLin has joined #asahi
millenialhacker has joined #asahi
timokrgr has quit [Quit: User left the chat]
timokrgr has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
jeisom has quit [Ping timeout: 480 seconds]
greguu has joined #asahi
possiblemeatball has quit [Quit: Quit]
ryec__ has quit [Ping timeout: 480 seconds]
ryec has joined #asahi
kidplayer666 has joined #asahi
matteo has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
matteo has joined #asahi
ryec has quit [Ping timeout: 480 seconds]
matteo has quit [Ping timeout: 480 seconds]
ryec_ has joined #asahi
EdLin has quit [Ping timeout: 480 seconds]
EdLin has joined #asahi
capta1nt0ad has joined #asahi
ryec_ has quit [Ping timeout: 480 seconds]
<capta1nt0ad>
Hello! I'm really grateful for the work that the Asahi team is doing on the Fedora Remix as well as the attempted collaboration with the ALARM maintainers. I currently do not have the time to migrate to the Fedora Asahi Remix (I have too many packages both from the ALARM repos and the AUR that I would need to reinstall and reconfigure), and I have read and understand this (https://social.treehouse.systems/@AsahiLinux/
<j`ey>
capta1nt0ad: think your message got cut off
<capta1nt0ad>
111607864744814408) reply which states that an lsp-plugins fix could be available as soon as January. I was wondering if there is anything specific that is also preventing other new features from being included, such as the new Touch Bar interface. Thank you for your time in answering my question.
capta1nt0ad has quit [Remote host closed the connection]
<Retr0id>
One side of my headphones permanently stopped working while I was using the 3.5mm jack, on asahi on my 14" 2021 MBP. I got my multimeter out to investigate, and it's not the cable (as one might expect) but the driver itself that's gone open-circuit, almost as if it got overdriven and blew out. like I said, probably just a random hardware failure,
<Retr0id>
but I figured I'd ask anyway - has anyone else had something like this happen?
i509vcb has quit [Quit: Connection closed for inactivity]
<Retr0id>
before it totally broke, it would work for a bit if I unplugged it and re-plugged it again, which is a pretty weird behaviour, and at the time I was convinced it must've just been a software bug - but the headphones are definitely toast now (at least, on one side)
EdLin has joined #asahi
ciara has joined #asahi
WindowPa- has joined #asahi
crabbedhaloablut has quit [Read error: Connection reset by peer]
capta1nt0ad has quit [Remote host closed the connection]
ryec has quit [Ping timeout: 480 seconds]
matteo has joined #asahi
ryec_ has joined #asahi
kidplayer666 has quit [Quit: Connection closed for inactivity]
ryec_ has quit [Ping timeout: 480 seconds]
tpz has joined #asahi
ryec_ has joined #asahi
tpz has quit []
ryec_ has quit [Ping timeout: 480 seconds]
baozich1 has joined #asahi
holiday has joined #asahi
baozich has quit [Ping timeout: 480 seconds]
baozich1 is now known as baozich
<mort_>
Is there detailed info somewhere on how the audio stuff works from a system integration perspective? I'm using sway on asahi fedora, and while I can see the "Built-in Audio Speakers" device, I can't hear any sound; I'm guessing maybe speakersafetyd isn't running since I'm not using the standard gnome/kde session
<j`ey>
mort_: speakersafetyd is started by udev
<j`ey>
is it actually running? systemctl status speakersafetyd
<PaulFertser>
mort_: without speakersafetyd the kernel will limit the volume but not to 0.
<PaulFertser>
I suggest you check alsamixer for the real device (switch to it with F6 if needed).
<mort_>
ah speakersafetyd isn't even installed
<mort_>
I assumed it was in some meta package and would get installed automatically
<PaulFertser>
And that should be the case, yes.
<PaulFertser>
You also need the correct lsp-plugins etc.
<j`ey>
mort_: oh, do you not have the metapackage?
<j`ey>
asahi-platform-metapackage
<mort_>
from what I can tell from `dnf info asahi-platform-metapackage` it's installed
<mort_>
anyway sound works after manually installing and starting speakersafetyd!
millenialhacker has joined #asahi
<Namidairo>
at least it's not making the bass clip all over the place like it was for me yesterday
delroth has quit [Remote host closed the connection]
delroth has joined #asahi
<Namidairo>
not too sure about the profile check in asahi-diagnose though, given the macaudio profile is listed as 'none' for me
millenialhacker has quit [Ping timeout: 480 seconds]
ryec has joined #asahi
fugi has quit [Quit: Ping timeout (120 seconds)]
ryec has quit [Ping timeout: 480 seconds]
EdLin has quit [Quit: leaving]
fossdd has quit [Read error: Connection reset by peer]
fugi has joined #asahi
slewsys has joined #asahi
<mort_>
I checked into meta package stuff, asahi-platform-metapackage is installed and depends on asahi-platform-metapackage-audio which is installed and depends on speakersafetyd, so it's odd
<mort_>
but all of these meta packages seem to have multiple versions installed? Like this is `dnf info asahi-platform-metapackage`: https://p.mort.coffee/5Ac
<psykose>
info --installed i think
<psykose>
just info lists available too
<psykose>
or maybe list --installed etc
<janneg>
the info output has headers "Installed" and "Available" packages
<psykose>
means none were installed then
fossdd has joined #asahi
<janneg>
mort_: yes, that suggest none is installed. I didn't looked at the output before
roxfan has joined #asahi
ryec__ has joined #asahi
<PaulFertser>
marcan: I'm here if you want me to test anything extra with this AP6255 broadcrap module.
crabbedhaloablut has quit []
ryec__ has quit [Ping timeout: 480 seconds]
crabbedhaloablut has joined #asahi
kidplayer666 has joined #asahi
roxfan2 has joined #asahi
<PaulFertser>
marcan: what I missed to mentioned is that it was 6.4.7 kernel driver. I hope it's not hard for you to tell if there were any changes that could have affected WPA3 since then.
roxfan has quit [Ping timeout: 480 seconds]
<PaulFertser>
Why Arend isn't even trying to test it himself is beyond my understanding :/
holiday has quit [Ping timeout: 480 seconds]
<sven>
broadcrap unfortunately is the answer to that :(
<sven>
he mentioned that he almost gets no time allocated by them for upstream work
<chadmed>
that whole thread today actually shit me off to the point of getting a headache
<PaulFertser>
Then he should just remove himself from MAINTAINERS, clear and easy as that.
<chadmed>
legit just fuck off if youre going to be like that
<PaulFertser>
Somehow his idea of keeping this codepath seems to be correct in this particular case though.
<chadmed>
just the absolute opposite of helpful every single time
<chadmed>
sad to see him rage quit like that but sadly its also the only way this driver is going to move forward
<PaulFertser>
I'd say that's fair enough. And in the past Arend seemed to be a reasonably nice fellow. Why is he acting this way now I can't explain, given he retains access to company documentation and can ask internally if he's really willing to help.
<chadmed>
thats probably the issue
<j`ey>
willing to help.. but no time it seems really
<chadmed>
he might _want_ to be more helpful and is being prevented from doing so by broadcom management who are notorious for doing exactly this
<sven>
depending on how siloed the company is he might not be able to ask for documentation if his work isn’t directly related to some chipset :(
<chadmed>
if that is the case though he probably just shouldve said something to that effect and bowed out long ago
<chadmed>
instead of holding things up and going "uhh well yeah idk
<sven>
and to be fair, I wouldn’t want to maintain that Broadcom driver either with all the messy hw and fw variants out there
<PaulFertser>
Though in this particular case he prevented a regression it seems.
<sven>
I’m kinda happy the Bluetooth driver is only used for Apple machines so far and even there we might already have a t2 regression (probably due to core changes though)
<sven>
I think the best solution would’ve been something like Arend + someone from rpi + markan or d berlin
<PaulFertser>
Nobody from rpi wants to do anything at all regarding wifi.
<chadmed>
rpi will never step up
<chadmed>
as far as im concerned upstream would be better off pretending that company and their products dont exist
<sven>
I did say best and not realistic ;) maybe I should’ve said „in a perfect world“ instead
<ndo>
hey folks, whats the recommended way to get the arch distro on a fresh install? I see the installer data.json file still has an entry for arch arm, but it says "not recommended"
ndo is now known as ndom91
<j`ey>
ndom91: that is how you do it
<j`ey>
(setting EXPERT=1 first)
<ndom91>
Okay thanks, and why is it tagged with "not recommended" exactly? It just doesn't ship wtih a desktop environment or something?
<ndom91>
setting EXPERT=1 where?
<j`ey>
it's not as well maintained as Fedora is
<eiln>
alarm is broken and we don't have the bandwidth to look at alarm issues too
<ndom91>
Gotcha
delsol has joined #asahi
<j`ey>
ndom91: I would suggest Fedora, unless you really want alarm
<j`ey>
alarm in general has less maintainers (pretty much one person)
<j`ey>
and in the terminal: export EXPERT=1, before running curl
<ndom91>
Ah as env var for the installer, gotcha
kidplayer666 has joined #asahi
<ndom91>
What about folks who already have alarm installed? Is there an easy way to migrate to the fedora version? Or any sort of offical guide?
<j`ey>
alarm doesnt have speakers or hdmi currently
<ndom91>
Like the original alarm install from before the fedora switch
<j`ey>
no guide, backup and wipe and reinstall is the way to do it
<ndom91>
Okay gotcha, thanks
<j`ey>
(there is the partitoning cheat sheet onthe wiki that will help after backups have been done)
<ndom91>
Thanks for the hint, thats exactly what I need for the wipe / reinstall operation ;)
<ydalton>
janneg: shouldn't it direct the user to https://alx.sh?
<j`ey>
ydalton: because fedora wanted their hosted one to be on the main docs
rvalue has quit [Remote host closed the connection]
rvalue has joined #asahi
al3xtjames has quit [Read error: Connection reset by peer]
ryec__ has quit [Ping timeout: 480 seconds]
ryec_ has joined #asahi
ryec_ has quit [Ping timeout: 480 seconds]
ryec has joined #asahi
Brainium has quit [Quit: Konversation terminated!]
millenialhacker has joined #asahi
possiblemeatball has joined #asahi
roxfan2 has quit [Remote host closed the connection]
roxfan has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
Murray_B has joined #asahi
<Murray_B>
Hi! Time for a nice christmas holiday project: Linux on my M2 mini. I am a bit confused by the Asahi distribution. Does the modified version of Arch on ARM still exist or do I have to use the fedora version now?
<j`ey>
Murray_B: it's suggested to use Fedora, it is maintained better
<novaandromeda>
ALARM still exists and you can use it, but the fedora one is recommended
<Murray_B>
And are there any information which software is in this distribution? Does it just link to the Arch on Arm repositories?
<j`ey>
yes it uses the ALARM repos + some extra asahi specific packages
<j`ey>
(ALARM is pretty much maintained by one person)
<Murray_B>
I see, a rather big project ;-)
<j`ey>
Fedora is the same way, all the normal fedora stuff + a few asahi specific packages
<Murray_B>
I normally use arch and prefer a rolling distribution, I guess the fedora is non rolling, right?
<j`ey>
yeah
<j`ey>
there is a rolling version (rawhide) but it's more for testing
<j`ey>
(and planning the next release)
<Murray_B>
Okay, I see. And I guess with Fedora I get a full blast of supported software. Do I get Updates from Asahi with Fedora or do I need to reinstall every time?
<j`ey>
yes you get updates
<Murray_B>
One last question: Which works better on Mac, KDE or Gnome. AFAIR Gnome has older support for wayland.
<j`ey>
KDE is the 'flagship' DE
<j`ey>
so if you dont really mind, pick that!
<Murray_B>
j`ey: Thanks a lot for your help!
<ydalton>
GNOME has terrible support for fractional scaling
<ydalton>
if you use any Xwayland applications, they will be blurry
<ydalton>
KDE does not have this problem, it scales the programs properly
delsol has quit [Remote host closed the connection]
<ar>
kde has two options for scaling legacy apps. one that gives xwayland hints about scaling and apps that support scaling will look good, but those that don't won't scale at all, and another option for just scaling everything
<ar>
but then even apps that do support scaling get blurry
holiday has joined #asahi
matteo has quit [Remote host closed the connection]
<ydalton>
and some super legacy apps, such as xclock will appear very tiny
shiggitay has joined #asahi
AnuthaDev has joined #asahi
<kit_ty_kate>
is it expected for speakersafetyd to not be enabled by default with the new kernel/release on fedora?
<ydalton>
as a systemd unit?
<kit_ty_kate>
yeah
<ydalton>
is it running?
<kit_ty_kate>
it is now but it wasn't before
<ydalton>
udev should start it up usually
<ydalton>
for me it's not enabled by default
<j`ey>
kit_ty_kate: wasnt before when?
<j`ey>
kit_ty_kate: you started it manually or?
<kit_ty_kate>
ah, mmh, let me reboot and make sure i'm not saying something wrong
Murray_B has quit [Quit: Leaving]
<kit_ty_kate>
ok nevermind it was started on boot even though the systemd unit is disabled, i somehow didn't see it in the list of processes at the time
<kit_ty_kate>
my bad, sorry for the noise
<ydalton>
no problem
matteo has joined #asahi
shiggitay has quit [Ping timeout: 480 seconds]
<joshheyse>
Just updated fedora packages on my j416 and jumped when slack notification played through the speakers! Thank you all so much for your hard work!!
<kit_ty_kate>
is https://github.com/AsahiLinux/asahi-audio the best place to open issues about the default eq/weird vibrations sounds when playing some music on j316 ?
sekalol15 has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
<kit_ty_kate>
and extra tanjantially related question: is there a way to change the EQ to see what makes it sound better/fix the issue i'm having?
<sekalol15>
I recently had to reinstall asahi fedora on my macbook air(M1), and i can't reinstall anymore. RecoveryOS always kernel panics in step 2, and MacOS shows the error "your pc was restarted because of a problem" after booting back into MacOS,(sonoma 14.2.1), I tried a few times and also on sonoma 14.0 before updating if I remember correctly(which had already sucessfully installed asahi fedora with before) and the problem persists
millenialhacker has quit [Ping timeout: 480 seconds]
<unixpoet>
should I be able to upgrade to fedora 39? I see that it's available to install but I'm not seeing it as available to install via the Discover program. I've tried refreshing and rebooting and it's still not available
<unixpoet>
I'm also curious about speakers; I just updated my packages, rebooted, and I can adjust volume, but there's no actual output, on an M2 Air. it's listed as supported on the support matrix but there's no actual detail on what I need to do to make it happen
<ydalton>
are you on fedora 38?
<unixpoet>
I am, yes
<ydalton>
do you know how to upgrade to fedora 39?
<unixpoet>
I just did an upgrade from 38->39 on x86_64 with the Discover app so I figured it'd be the same process
<Fridtjof>
(warning, 10s in there's a dramatic increase in volume lol)
<unixpoet>
okay, removed a bunch of font packages and it seems the download part is happy atleast
Brainium has joined #asahi
i509vcb has joined #asahi
<janneg>
Fridtjof: I think only by editing the graph files (for example /usr/share/asahi-audio/j314/graph-j414.json) and restarting wireplumber. I suppose setting "bypass" to 1 in the bankstown node disables it
<chadmed>
it does
<chadmed>
Fridtjof: which model do you have
<Fridtjof>
oh
<Fridtjof>
thanks for asking, i went as far as to restart my laptop because i thought it didn't apply right
<Fridtjof>
turns out i just mindlessly went with j314, when this is j316
<Fridtjof>
chadmed: so i'd go with j316/graph-j416.json then, right?
<Fridtjof>
yeah, interesting. the harmonics are indeed from bankstown
WindowPa- has quit [Ping timeout: 480 seconds]
<Fridtjof>
don't think i've played that song on speakers with macos before, i wonder if it's a thing there as well
<chadmed>
please try for us
<chadmed>
it will help us fine tune bankstown
matteo has quit [Ping timeout: 480 seconds]
<Fridtjof>
alright, i quickly rebooted to check
<Fridtjof>
it doesn't exhibit any out of place harmonics like with bankstown, at least not that i could hear as clearly
matteo has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
matteo has joined #asahi
<chaos_princess>
is the sound with speakers supposed to be much quieter than on macos? i need to set volume to 50-ish percent to to have similar volume as i get from just one bar of sound (5%? 10%? idk) on macos
<ydalton>
is speakersafetyd running?
<chaos_princess>
ofc
john-cabaj has joined #asahi
<kidplayer666>
Maybe a different curve? How does max volume compare, what model
john-cabaj has quit [Ping timeout: 480 seconds]
<chaos_princess>
the model is j314, max on linux is roughly 54 db using a very unscientific test, i get the same on macos by only having the volume a bit below the half way mark (dont want to turn macos to full blast cause we live in a society)
delsol has quit [Remote host closed the connection]
<leio>
this leads me to ask - can I get the audio on linux to be 100% on what it is at 30% or so right now? I always have to run it below 30% or so for headset and it doesn't leave much room for precise volume changes - each step changes a lot unless doing the precise volume stepping with holding shift while hitting volume up/down keys
<mort_>
are cores 0 and 1 the E cores on the M1 Pro models?
<bluetail>
idk. maybe try running lstopo
<j`ey>
mort_: yeah
<mort_>
In that case, it kinda looks like a lot of work which should have been done on P cores ends up on E cores... the other cores aren't really affected by doing things in Firefox
matteo has quit [Ping timeout: 480 seconds]
<mort_>
ah yeah I used taskset to prevent firefox from using 0 and 1 and it's actually more responsive, and cores 0 and 1 aren't the ones getting used when I do stuff in firefox anymore
<mort_>
this seems like a kinda bad scheduler issue, I wonder if it's tweakable somehow?
matteo has joined #asahi
greguu has quit [Ping timeout: 480 seconds]
greguu has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
matteo has joined #asahi
matteo has quit [Ping timeout: 480 seconds]
ydalton has quit [Remote host closed the connection]