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
xcpy00 has quit [Quit: Ping timeout (120 seconds)]
xcpy00 has joined #asahi-alt
clandmeter has quit [Quit: Ping timeout (120 seconds)]
clandmeter has joined #asahi-alt
john-cabaj has joined #asahi-alt
john-cabaj has quit [Ping timeout: 480 seconds]
KxCORP5 has quit [Quit: Bye!]
KxCORP5 has joined #asahi-alt
jeisom has quit [Ping timeout: 480 seconds]
utsweetyfish has joined #asahi-alt
kidplayer666 has quit [Quit: Connection closed for inactivity]
KxCORP5 has quit [Quit: Bye!]
KxCORP5 has joined #asahi-alt
JayBeeFOSS has quit [Ping timeout: 480 seconds]
JayBeeFOSS has joined #asahi-alt
VeeBop has quit [Quit: buh bye]
VeeBop has joined #asahi-alt
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi-alt
chadmed has quit []
chadmed has joined #asahi-alt
chadmed has quit []
chadmed has joined #asahi-alt
chadmed has quit []
chadmed has joined #asahi-alt
Guest3898 has quit [Quit: Bridge terminating on SIGTERM]
rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
Jamie has joined #asahi-alt
Jamie is now known as Guest4042
rhysmdnz has joined #asahi-alt
nyaomixyz has joined #asahi-alt
<nyaomixyz>
hello
<nyaomixyz>
did anyone notice that bluetooth headphone playback is stuttery?
<nyaomixyz>
trying with sony wh-1000xm4 on my gentoo install
<nyaomixyz>
wondering if there's something to do with the speaker stuff or not
<nyaomixyz>
s/there's/this has/
<leio>
are you using 2.4GHz wifi?
<nyaomixyz>
5ghz iirc
<nyaomixyz>
yup 5 ghz, checked
<leio>
ok, good, though occasional SSID scans to the 2.4GHz network might affect things
<nyaomixyz>
it's persistent though, it's not a one off
<nyaomixyz>
i could try with wifi disabled
<leio>
yeah, give it a try to rule it out
<leio>
bluetooth works in the 2.4GHz range too and it's for some reason more disturbing things on asahi than elsewhere
<stintel>
2.4GHz is hit-or-miss, if you live in a house with no close neighbors, it can work very well, if you live in an area with apartment buildings ... good luck! I scan > 100 2.4 SSIDs, I've had times where toggling a zigbee light took ~10s
<nyaomixyz>
so, i live in a decently isolated house and there aren't many wifi networks here
<nyaomixyz>
mostly because i am the only one with wifi and the others are elder people still using landline phones
<nyaomixyz>
but no, with wifi disabled the issue still occurs
<chadmed>
years ago before 802.11n on 5ghz i had to stop using my microwave rice cooker thing and go back to the absorption method on the stove because the 2.4ghz would utterly tank any wifi or bluetooth in the house
<nyaomixyz>
it seems like it recovers and breaks in intervals
<nyaomixyz>
tried sbc codec, it's the sam
<nyaomixyz>
so it's not like the codec affects it
<nyaomixyz>
pipewire has -11 niceness level so it shouldn't be pw related
<stintel>
maybe try completely unloading the brcmfmac* modules too
<nyaomixyz>
there's reason to try as it periodically is fine
<stintel>
I've use my m2 air on a plane once or twice with B&W PX7 and afair it worked fine, but that was ~3 months ago, so might be a regression somewhere
<stintel>
used*
<stintel>
haha, testing it now and it is completely unusable
<nyaomixyz>
yeah unloaded the modules and it is still completely fried
<stintel>
which kernel version you on?
<nyaomixyz>
asahi-kernel r3 with fedora config
nyaomixyz has quit [Remote host closed the connection]
<stintel>
6.8.0 here is completely unusable, built from asahi-wip-6.8 342f90828c4167c94ee184ca05eeacb22255ac9b
<stintel>
booted into 6.6.4 (asahi-6.6-14 + linux-stable/v6.6.4) works like charm
<stintel>
I'll make sure to keep this kernel around for when I'm traveling lol
<stintel>
"completely unusable" --> bluetooth audio is completely unusable, to be clear
<stintel>
I've been running it fine without other issues for ~2 weeks
<stintel>
right, that means I should hold off on reinstall with bcachefs rootfs until this is sorted, as I won't be able to boot that with 6.6
nyaomixyz has joined #asahi-alt
<nyaomixyz>
stintel: here i have 6.6.0_p15-r3 (gentoo)
<nyaomixyz>
also what's this hype for bcachefs?
<stintel>
I've been using it since 2018, and now that it's finally in mainline I plan to move all my non-embedded Linux machines (physical and virtual) to bcachefs rootfs
<stintel>
been bitten too often by btrfs bugs
<stintel>
and I consider any other fs without checksumming and snapshots not a proper fs for this age
<stintel>
so there's not many options :)
possiblemeatball has joined #asahi-alt
<nyaomixyz>
idk, i've been bitten by smart errors more than btrfs bugs and it's hard to know if they were caused by the filesystem in the first place
<nyaomixyz>
right now i'm using btrfs around my house (not in the mac tho)
<nyaomixyz>
for the mac i am using the old ext4
tobhe has joined #asahi-alt
tobhe_ has quit [Ping timeout: 480 seconds]
tobhe_ has joined #asahi-alt
akda5id has quit [Quit: Ping timeout (120 seconds)]
akda5id has joined #asahi-alt
TellowKrinkle has quit [Remote host closed the connection]
TellowKrinkle has joined #asahi-alt
tobhe has quit [Ping timeout: 480 seconds]
jeisom has joined #asahi-alt
kidplayer666 has joined #asahi-alt
<cy8aer>
My btrfs on the mac does not make any problems for two years now... but bcachfs is interesting anyways
<nyaomixyz>
yeah
<nyaomixyz>
as long as it won't eat our data
<nyaomixyz>
but i'm more interested in what happens if something goes wrong
<nyaomixyz>
like in btrfs you got nothing, in bcachefs tooling seems to be premature
<nyaomixyz>
so when looked that way... at least in btrfs you can scrub data
<stintel>
tooling and repairability is actually already quite good in bcachefs
<nyaomixyz>
saw their website and saw plans for that, not actual shipped products
<nyaomixyz>
did it deliver scrub?
<nyaomixyz>
s/it/they/
<nyaomixyz>
which is probably the thing i run the most on my btrfs systems just because i am paranoid
<stintel>
scrub is missing, but fsck is there, and can repair lots of things
<nyaomixyz>
so we're counting on fsck to pick up and fix corrupted files
<nyaomixyz>
or at least metadata?
<stintel>
I guess it depends on how corrupt things are :)
<nyaomixyz>
fair call
<nyaomixyz>
right now i'd want bt audio to not be corrupt lol
<nyaomixyz>
you mentioned kernel 6.6.4 - are you compiling yourself? are you on fedora?
<stintel>
Gentoo
<stintel>
like I said, asahi-6.6-14 + linux-stable/v6.6.4
<nyaomixyz>
oh
<nyaomixyz>
so there's probably a couple fixes you pulled in that way
<nyaomixyz>
if asahi-wip is broken
<stintel>
those are two tags, so you should be able to exactly replicate that
<nyaomixyz>
there should be 6.6-15 now tho
<stintel>
what I usually do is: git checkout asahi-6.6-14; git checkout -b build-6.6.x; git merge linux-stable/v6.6.x
<stintel>
I switched to 6.8 before 6.6-15 came out, iirc
<stintel>
v6.6.5 no longer merged cleanly and conflicts were too many so that's why I stuck with 6.6.4
<stintel>
that's actually how I ran bcachefs.git for years :)
<nyaomixyz>
oh understood
<nyaomixyz>
it makes sense, also I saw there's a 6.6-16 now
<nyaomixyz>
i should've tested bt audio with fedora prior to formatting...meh
jcajka has joined #asahi-alt
<stintel>
changes between 14 and 16 seem mostly drm related, so I'd say unlikely this would introduce a regression in bt
zerdox has joined #asahi-alt
<chadmed>
ive tried merging genpatches in the past but they dont merge
<chadmed>
or cause build failures
<chadmed>
so i just gave up
<stintel>
:)
<nyaomixyz>
btw chadmed does your setup have broken bt audio?
<nyaomixyz>
just so we are all on the same page - again
<stintel>
nyaomixyz: what hardware are you on?
<stintel>
15" air m2 here
<stintel>
01:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4387 802.11ax Dual Band Wireless LAN Controller (rev 07)
<stintel>
01:00.1 Network controller: Broadcom Inc. and subsidiaries BRCM4387 Bluetooth Controller (rev 07)
<nyaomixyz>
14" m1 pro macbook pro
<chadmed>
i used my airpods once a while ago and they were fine
<chadmed>
i dont really use bt audio day to day though
<stintel>
yeah me neither
<nyaomixyz>
i should test with other bluetooth stuff just to be sure it's not a compatibility problem with my headphones specifically
<nyaomixyz>
but yeah i get your point
<stintel>
going to reboot in 6.8 and try again to see what it does in a hopefully clean state
<stintel>
nope. 6.8 is definitely busted
demon_in_a_jar has joined #asahi-alt
kidplayer666 has quit [Quit: Connection closed for inactivity]
MichaelLong has quit [Ping timeout: 480 seconds]
MichaelLong has joined #asahi-alt
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #asahi-alt
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #asahi-alt
hightower2 has quit [Read error: Connection reset by peer]