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
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
KxCORP5894 has quit [Quit: Bye!]
KxCORP5894 has joined #asahi
Brainium has quit [Remote host closed the connection]
opticron has quit [Ping timeout: 480 seconds]
cylm has joined #asahi
Szadek5925420419 has joined #asahi
Szadek592542041 has quit [Ping timeout: 480 seconds]
<mkurz>
tramtrist: pretty sure this is not asahi related
<LarstiQ>
fwiw my bluetooth headset (not airpods) works fine with M1 Pro Asahi, so yeah I'm inclined to agree with mkurz
maxmatteo has joined #asahi
<mkurz>
LarstiQ: This is just about the microphone, my Pixel Buds Pro and AFAIK also the airpods pro also basically work, like you can listen music with the a2dp sink (aac), but on some models the microphone does not work. For my this is fixed with current pipewire main branch, so upcoming v1.2 makes everyting work out of the box for me and I guess maybe also the mic on the airpods pro
<mkurz>
LarstiQ: Also from comments I read on the pipewire issue is that not all models are affected with broken mic, just some
<LarstiQ>
mkurz: yeah I use the HSP microphone in meetings, the laptop mic doesn't work
<LarstiQ>
right
<mkurz>
LarstiQ: Not talking about the laptop mic but I always talk(ed) about the bluetooth headset mic, in my case pixel buds pro
<cy8aer>
6.8.9-10 - the messages like "pipehandler lock not acked, this type-c port is probably dead until the next reboot." do come from the usb stuff to be come or is this a real problem?
<cy8aer>
I get them on booting and when plugging in something to usb ports
<jannau>
real problem, usb3 should be broken. I missed that usb changes landed in v6.8.10
<cy8aer>
As long as it is known everything is good.
maxmatteo has quit [Ping timeout: 480 seconds]
<jannau>
do you mean asahi-6.8.10-1? it wasn't known that it's broken there. it's fixed in my 6.9 branch (should be pushed in my repo, I don't think I pushed anything 6.9 to AsahiLinux)
<cy8aer>
sorry I meant 6.8.10-1, sorry
<cy8aer>
The numbering drives me as crazy as the public holidays in May in Germany (you never know what day of the week it is)
pb17 has quit [Ping timeout: 480 seconds]
<jannau>
should be fixed in asahi-6.8.10-2
KDDLB has joined #asahi
joske has joined #asahi
<joske>
jannau: is 6.8.10-2 ok to update to in the PKGBUILD?
maxmatteo has joined #asahi
maxmatteo has quit [Remote host closed the connection]
maxmatteo has joined #asahi
pb17 has joined #asahi
shiggitay has joined #asahi
shiggitay has quit [Remote host closed the connection]
shiggitay has joined #asahi
maxmatteo has quit [Ping timeout: 480 seconds]
istdaa^ has joined #asahi
istdaa^ has quit [Remote host closed the connection]
Whistler_ has quit []
Whistler_ has joined #asahi
axboe has quit [Remote host closed the connection]
axboe has joined #asahi
<dontdieych>
joske: thanks for your PKGBUILDs. I got MBA + Arch. All systems operational
<PaulFertser>
bluetail: have you tried it with uas disabled btw?
<PaulFertser>
Your old log was with uas not disabled.
<bluetail>
PaulFertser there are some indications that my issue was unrelated
shiggitay has quit [Ping timeout: 480 seconds]
<PaulFertser>
And the iommu errors... It all makes sense now.
<bluetail>
Marcan said this exists for months
<sven>
yes, but it's a bug that's not easily triggered
<PaulFertser>
bluetail: so what indications? So far everything I see matches your story.
<bluetail>
I just don't wanna feel bad, okay?
<bluetail>
I have already build the server :X
<sven>
it may have well existed for years but only started happening for you today because the enclosure finally triggered an error that went down that buggy code path
<bluetail>
I bought a new case, a hba, a psu... everything
<bluetail>
even new fans
<PaulFertser>
bluetail: doesn't mean you'll never find the use for your old one
<bluetail>
well it was fully refunded
<PaulFertser>
It's is so uplifting to see markan fix xhci bugs! This whole story with Intel maintainership for xhci specifically is nothing new. It was all bug-ridden right from the beginning, with new odd issues appearing all the time. But Sarah Sharp became famous /not/ for the outstanding quality of the code she contributed and maintained over those years.
<bluetail>
PaulFertser what usually happens is that those kind of issues only present for me, and theres no fix whatsoever
<bluetail>
or rather, thats what it feels like
<bluetail>
for instance, I would buy a head mounted display, just to find out the USB disconnects every 5 minutes
<PaulFertser>
bluetail: you can see in the comment thread that one was happening for many people, just probably you invested in a bit more elaborate setup for it to become critical.
<bluetail>
pico neo 3 link for instance
<PaulFertser>
BTW, disabling uas is kinda standard way to try to troubleshoot/workaround USB storage issues, now that I think about it that's odd I didn't suggest you try it back then.
<PaulFertser>
(and nobody else either)
<bluetail>
ok... so I just calculated it. It set me back 2300 eur
<PaulFertser>
I wonder if there's a single thing from Intel with regard to software that people are happy with? Probably mac80211?
<mini_>
oh, this is good to see, I invested in external SAS because of how many weird USB3 bugs I've hit
<bluetail>
just for ref, my new system is cpu i3-9100, 2x32GB DDR4 rDIMM Micron (ECC), 9305-24i HBA (IT MODE), Supermicro X11SCH-F Motherboard, 3xNoctua A12 PWM, 2x Noctua A8 PWM, case: Silverstone RM43-320-RS 20 bay, PSU: Corsair HX1000i
<bluetail>
Oh and a Noctua NH D12-L cpu cooler
<Namidairo>
would I be right to assume that all the fans cost a magnitude more than the cpu itself
<bluetail>
yes
<bluetail>
150 EUR
<bluetail>
I got the cpu used for 50 bucks
<bluetail>
the standard fans that were included in the case were too noisy!
<Namidairo>
lol
<bluetail>
Thats not the only drawback
<bluetail>
It takes quite a bit more wattage than over USB and a mac mini m1
<bluetail>
But the new setup has so advantages
<bluetail>
Mounting a borg repo and browsing it doesnt take ages anymore
<bluetail>
I got IPMI now, I can run x86 applications now without headache
<mini_>
do you still get enough airflow with replacing the fans? those standard fans are usually crazy high RPM with very high static pressure figures
<bluetail>
mini_ People keep saying USB is not robust at all.
<bluetail>
I will see today
<bluetail>
I did temporarily use a fan controller + a low noise adapter and it was nearly silent enough, and my disks were still below 50C
<bluetail>
of course, while in use and writing stuff to i
<bluetail>
t
<bluetail>
Another side-effect this had was me ordering a cheaper electricity contract that allows me to use 5000 kWh a month for less money. Cause I was already close to 3800 kWh a year, not now assumedly I was at 4500 kWh a year with the change.
<bluetail>
140 EUR/month => 113 EUR a month
<bluetail>
PaulFertser 😔
<leio>
silence is why I got a Mac Studio :)
<mini_>
bluetail: what's your backup strat for that machine? :)
<mini_>
I ended up with a mix of online backup using borg for important things + external SAS for backup drives I can turn off and walk away with easily
<bluetail>
It changed from btrfs raid1c3 ( 3x20TB pairs ) to 2 coldbackups via borgbackup to single disks having borgbackup after the usb bug started appearing
<bluetail>
since I could not even remake the btrfs raid1c3 without it failing just in 5 minutes or so
<bluetail>
I was happy I had backups
<bluetail>
Now with ECC / registered dimm in the new machine, I think am less likely to write faulty stuff
<bluetail>
But does it warrant to no more use raid1c3? I don't know. I will make tar archives and check crc and send them into the borg backup repo!
<mini_>
this is probably more for -offtopic, but still :)
<bluetail>
mini_ also I do always mount via /dev/disk/by-id rather than UUID
<mini_>
yeah - I do ZFS and do via /dev/disk/by-id, it makes it easier to identify a failing disk quickly
* leio
points out #asahi-offtopic exists
<bluetail>
its recommended to not rely on one file system!
<bluetail>
ZFS had breaking bugs with corruption, so had others. You should have your backups on differently formatted disks
<bluetail>
and even your live data
<bluetail>
I got 2 cold backups foreach disk I use in prod
pb17 has quit [Ping timeout: 480 seconds]
<bluetail>
leio at this point I don't care. I need now some aftercare emotionally because I feel bad about myself. Cause this month I will be just ... slightly in minus :S And this was avoidable.
<bluetail>
Maybe a pizza? idk.
<j`ey>
don't feel bad, it was only avoidable with hindsight
<j`ey>
(and even then we don't even know if markan's fix would have been the same)
<mini_>
I've had enough strange USB3 issues for a decade, so I just don't trust it for anything that isn't ephemeral
jadesoturi_ has quit [Ping timeout: 480 seconds]
hellstabber_ has quit [Quit: Connection closed for inactivity]
jadesoturi has joined #asahi
r1k0 has joined #asahi
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi
pb17 has joined #asahi
r1k0 has quit [Remote host closed the connection]
r1k0 has joined #asahi
r1k0 has quit [Read error: Connection reset by peer]