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
rosefromthedead has quit [Ping timeout: 480 seconds]
hightower2 has quit [Ping timeout: 480 seconds]
balrog has quit [Read error: No route to host]
balrog has joined #asahi
<winter>
> Keep in mind that since the UAPI changed (a lot), apps will probably stop launching or will launch with software rendering until you reboot.
<winter>
Would en/disabling Mesa also cause this? As in, requiring a reboot to get GPU stuff working. How would I see if it's the UAPI change causing this? (Why is it causing issues anyways, wouldn't the new versions of the libraries be loaded? Or are we going off of cached libraries?)
<Retr0id>
I think the new libraries being loaded is the problem
<Retr0id>
since until you reboot, your kernel is the old one
<psykose>
the uapi comes from the kernel so the new mesa uses the new kernel apis but until you reboot it's only the old kernel
possiblemeatball has joined #asahi
<mort_>
after the latest round of mesa/kernel updates, the system feels way more snappy -- I'm guessing that's the async stuff Lina talked about in the blog post
<Retr0id>
A small issue I've been having since updating is that in firefox, my text caret disappears sometimes, haven't figured out how to reproduce it yet
hightower2 has joined #asahi
wintp has joined #asahi
<winter>
Retr0id, psykose: Sorry, to clarify: I'm running into the above quirk with the edge kernel loaded, just en/disabling Mesa using weird symlink RPATH... stuff... unsure how that'd be cached until reboot, though (nscd?).
<Retr0id>
I'm confused, are you implying that you've loaded the edge kernel without rebooting?
<psykose>
it wouldn't be and nscd has no relation to it
<Retr0id>
ohhhh
zopieux has quit [Read error: Connection reset by peer]
zopieux has joined #asahi
<rory_be>
nevermind... figured out I need to plug into a thunderbolt port via an adapter since it is a USB 2.0 keyboard.
<rory_be>
USB-A ports not backwards compatible (3.0 -> 2.0)before linux takes over...
unicordion has joined #asahi
brad_ has quit [Ping timeout: 480 seconds]
artemist has joined #asahi
linuxgemini1 has quit []
linuxgemini1 has joined #asahi
amarioguy has quit [Remote host closed the connection]
___nick___ has quit []
___nick___ has joined #asahi
Brainium has quit [Quit: Konversation terminated!]
___nick___ has quit []
___nick___ has joined #asahi
wintp has quit [Quit: Connection closed for inactivity]
ioldoortileotm^ has quit [Remote host closed the connection]
jmsunseri has joined #asahi
jmsunseri has quit []
Zopolis4 has quit []
bisko has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Zopolis4 has joined #asahi
unicordion has quit [Ping timeout: 480 seconds]
yc has quit [Remote host closed the connection]
<marcan>
I'm running fstests and one of the problems was btrfs-convert not working... because it has a solib dependency on reiserfsprogs but not a package dependency
<marcan>
seriously, it's just... so, so many of these things.
guillaume_g has joined #asahi
bisko has joined #asahi
mkurz has joined #asahi
c10l has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
giskard has joined #asahi
mohit88 has joined #asahi
mohit8 has quit [Read error: Connection reset by peer]
mohit88 is now known as mohit8
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi
bisko has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<mkurz>
When upgrading packages I get following error: "error: failed to commit transaction (conflicting files)
<mkurz>
ruby-bump: /usr/bin/bump exists in filesystem (owned by mesa-demos)"
<mkurz>
Anyone know why that happens?
<_jannau_>
ruby-bump and mesa-demos are both installing /usr/bin/bump
<mkurz>
yes I removed mesa-demos now
<mkurz>
don't need the demos myself...
afroboy has joined #asahi
rosefromthedead has joined #asahi
baozich has joined #asahi
nyilas has joined #asahi
leitao has joined #asahi
antonio__ has joined #asahi
baozich has quit [Ping timeout: 480 seconds]
nyilas has quit [Ping timeout: 480 seconds]
baozich has joined #asahi
<Retr0id>
ayke_ thanks, I did get everything working with virt-manager in the end, the only tricks are that I needed to install the edk2-aarch64 package from upstream, and remember to add spice graphics, virtio keyboard, and virtio tablet devices (there's some broken DPI scaling in windowed mode but full-screen works perfectly). llvmpipe graphics work nicely
<Retr0id>
in the guest, I did try enabling gl passthrough but that didn't work
<Retr0id>
and I've now forgotten why I wanted to boot up a VM in the first place
<j`ey_>
Retr0id: :D
baozich has quit [Ping timeout: 480 seconds]
hightower2 has quit [Read error: Connection reset by peer]
baozich has joined #asahi
rosefromthedead has quit [Ping timeout: 480 seconds]
bisko has joined #asahi
<kujeger>
how's the story with FEX vs box64 when it comes to strictly x64 binaries? Last I checked FEX isn't quite runnable on asahi/m1 yet due to page size stuff but I've already gamed a bit through box64
<chadmed>
box64 will probably work fine for well-behaved purely 64 bit binaries
<chadmed>
i have had trouble getting wine64 to work at all in a debian chroot even building it from source but any native linux binaries should be fine
<kujeger>
as I understood it emulating/running/whatever x86 stuff would require running a 4k page kernel anywat, which I'm guessing is what Lina's stream tomorrow about FEX and gaming is going to involve
<chadmed>
yeah not sure how box64 gets around the page size thing other than just hope and pray that the program doesnt make any assumptions about page size :P
<chadmed>
there was some discussion around adding page size emulation to fex a while ago but the main devs seemed rather cold to the idea
<winter>
<Retr0id> I'm confused, are you implying that you've loaded the edge kernel without rebooting? <-- No, I'm running the edge kernel, but en/disabling the same version of Mesa each time causes things to be weird until a reboot. But how Mesa is en/disabled is pretty nonstandard (yanking the binary out of the RPATH of the binary who needs it, and then
<winter>
just restarting all of them).
<marcan>
the vast, vast majority of apps don't care about page size and on windows the default granularity is 64K anyway
<marcan>
the only problem that gets in the way upfront is ELF section alignment, which can be worked around by tweaking how mmap works
<marcan>
I assume that's what box64 does
<marcan>
I still don't understand why FEX refuses to try doing the same thing
mofux has joined #asahi
<chadmed>
did they end up just flatly refusing? last time i checked in it was on their planner board to investigate and implement at some point
<chadmed>
but that was a few months ago now
<mofux>
First: Thanks to everyone involved in the newest updates! Fantastic progress! Is there any way yet to enable hardware acceleration for firefox / chromium with the latest mesa drivers (mesa-asahi-edge)?
Brainium has joined #asahi
<piroko>
oh. should the headphone jack work on the m1 pro macbook pro?
<piroko>
the feature matrix seems to suggest that it should but kde doesn't even see a soundcard
<kujeger>
piroko: I used it on my m1 pro a couple of days ago, and it worked fine
<marcan>
the sound card shows up when you actually plug in something
<marcan>
(or rather the output device, which is not the same thing)
<marcan>
(the card is there, it just has no profile until you plug in)
<piroko>
oh. apparently "off" was selected in kde's audio system settings
<piroko>
w00t it's working now
mofux has quit [Read error: Connection reset by peer]
mofux_ has joined #asahi
mofux_ is now known as mofux
nyilas has joined #asahi
antonio__ has quit [Ping timeout: 480 seconds]
delsol has joined #asahi
Zopolis4 has quit []
beeblebrox has joined #asahi
bcrumb has joined #asahi
possiblemeatball has joined #asahi
bcrumb has quit []
giskard has quit [Read error: Connection reset by peer]
unicordion has joined #asahi
<ayke_>
I have a one second delay when I click the Bluetooth button in the KDE panel, but only on Wayland (it's fast on X11). It's quite annoying. Does anyone have the same issue?
bisko has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<piroko>
yeah; same with the first time I open the "start" menu or the volume panel
<as400>
ayke: strange, for me everything is blazingly fast after last update
<piroko>
actually bluetooth is fine. volume is the one that delays
<d4ve>
Is it expected that wired headphones have audio output working but not input? M1 Pro, headphones are bose 700. On latest edge kernel.
<d4ve>
fwiw, the same headphones work on an x86 arch machine, with pipewire
<ar>
d4ve: wired as in analog jack?
bisko has joined #asahi
<d4ve>
yes
baozich has quit [Ping timeout: 480 seconds]
<ayke_>
as400: are you on the edge kernel?
<ayke_>
Just checked, and it doesn't happen on the edge kernel
<ayke_>
Time for a bug report, I guess
<ayke_>
Err, I mean it doesn't happen on the non-edge kernel (it's fast there)
rosefromthedead has joined #asahi
Nezteb has joined #asahi
<mps>
d4ve: do you mean mic on jack doesn't work?
<mps>
on my m1pro headphone mic works though I use alpine linux and not asahi alarm
unicordion has quit [Quit: Konversation terminated!]
unicordion has joined #asahi
<d4ve>
mps: correct, the mic on jack doesn't work for me.
<mps>
d4ve: maybe try with alsamixer and select hardware device (not pipewire) to set controls
<d4ve>
mps: yeah I'll try to fiddle around with that. I guess that means disabling pipewire first and then trying alsamixer?
<mps>
d4ve: maybe you don't need to disable pipewire, just select hardware device in alsamixer
<mps>
idk how pipewire works, never used it
<mps>
just wanted to say that mic works
<_jannau_>
headset mic works with pipewire as well but might be very quiet. there are two 'jack adc ... gain' controls which are probably at zero. try to raise those with `alsamixer -c 0`
mofux has quit [Quit: mofux]
possiblemeatball has quit [Quit: Quit]
bcrumb has joined #asahi
birdjj has quit [Ping timeout: 480 seconds]
bcrumb has quit []
birdjj has joined #asahi
qwe has joined #asahi
c10l has joined #asahi
<as400>
ayke: yes
possiblemeatball has joined #asahi
beeblebrox has quit [Ping timeout: 480 seconds]
bisko has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
beeblebrox has joined #asahi
Brainium has quit [Quit: Konversation terminated!]
afroboy has quit [Remote host closed the connection]
<d4ve>
_jannau_: so in zoom via firefox I get a constant beep, no matter what settings I apply to the Jack ADC controls. In pavucontrol there's no sound, and it says the headset microphone is unplugged.
rosefromthedead has quit []
<Retr0id>
related to webrtc being disabled perhaps?
<_jannau_>
d4ve: is there a 'cs42l84 .* Detected mic' message in the kernel log when plugging the headset in?
gladiac has quit [Quit: k thx bye]
<d4ve>
_jannau_: just tested another one, also does not work. it says [19920.755289] cs42l84 1-004b: Detected bare headphone (no mic)
<_jannau_>
that explains why it's not working. are the headset working in macos?
<d4ve>
_jannau_: Rebooting to check, but I'm reasoably sure they did.
<d4ve>
_jannau_: welp, good hunch. I seem to have been using the internal mics all this time without noticing, the mic also does not show up in macOS. Sorry for the noise!
<d4ve>
Seems to be a broken jack though, as the mics do work (and show up as such) on a different machine
<waldi>
d4ve: bose 700 is primarily a wireless headphone. internet suggests that it does not even support microphone in wired mode
<_jannau_>
cable on the low resolution image looks also if it has just a single ring, i.e. 3 connectors for stereo audio
<waldi>
let's look on mine: yep, it is a single ring, so mic can never work
<waldi>
and another case of: start at the basics
bisko has joined #asahi
bcrumb has joined #asahi
<the_CLA>
I was wondering: Is there some approximate time frame when Asahi might switch to another base distro? Or has that idea been scrapped?
bcrumb has quit [Quit: WeeChat 3.8]
<jn>
the_CLA: i'm curious because i don't know the full history - has the idea been in the position where it could be scrapped, i.e. proposed and accepted?
<jn>
on a more practical side of things: there are a few sister projects of Asahi which run non-Arch distros on M1 etc. hardware
<jn>
they are discussed in the #asahi-alt channel
<the_CLA>
jn: No idea. I'm just curious, because of a toot, 2 weeks ago, I think.
<jn>
i haven't seen the toot, sorry
janrinze has quit [Remote host closed the connection]
<ayke_>
as400: hmm, odd. Do you have any Bluetooth devices configured? I have about five.
mofux has joined #asahi
<the_CLA>
mps: I'm not looking for an alternative distro. I installed Asahi some time ago, but didn't do much with it, yet. Also quite some time since I last used Arch. So just not sure I should dig in with the current Asahi, or if I might wait until it possibly switches.
<the_CLA>
mps: But I'd like to stay with the official Distro, in case of some bug reporting.
<mps>
the_CLA: ok. posted url in case you didn't saw it earlier
<the_CLA>
thx, anyways. :)
darkwater4213 has joined #asahi
dax has joined #asahi
<mps>
personally I don't see any reason to switch to another distro but I'm not one who have any influence on this because I'm not using official distro from 'day one' (and I'm using m1 as daily driver for more than 15 months)
<darkwater4213>
Hey, I know there's a cURL script for installing Asahi, but is there an ISO for trying it out without modifying the disk?
mofux has quit [Quit: mofux]
<ChaosPrincess>
not really, you must install the bootloader to the internal ssd
<darkwater4213>
So, that's a no? Shame. I was really hoping it would be... idk, easier? I'm not used to MacOS yet XD
<ChaosPrincess>
aside from one step where you need to pay attention, the process is quite easy
<ChaosPrincess>
try it via the curl script, its easy
<darkwater4213>
I've used Linux for a long time, mostly with Xfce as my frontend. I don't like how... _cumbersome_ launching a terminal is in MacOS.
<ChaosPrincess>
launchpad -> type t e r m -> enter
<darkwater4213>
It has nothing to do with the installer. I just don't like MacOS all that much. It's like GNOME but even more opinionated and less free.
<darkwater4213>
Whereas on most Ubuntu and Xfce distros, its Ctrl+Alt+T
<darkwater4213>
quarter of a second. I don't like having to go through a menu, that's more time.
<darkwater4213>
I ditched mice a while ago, if you can't tell XD
<mps>
darkwater4213: also I never used macos. only used it to install linux on m1
<bcrumb>
did anyone experience without update their screen going black and desktop blinking?
<bcrumb>
Basically, I didn't really do anything, except that I went from the screen, and the screensaver started (meaning black screen)
<bcrumb>
But as I came back, and tried to unlock it, the screen wouldn't turn back on
<bcrumb>
So I had to shut it down manually by button, and now plasmashell crashes when booting
<bcrumb>
There was lots of different errors, I will get a journalctl log if I turn my machine off for longer (I guess it was like 10-15 seconds?) and if it doesn't boot
<bcrumb>
I'll also try downgrading plasma i suppose, or something else
<bcrumb>
This thing with the black screen did happen once before - a couple of days ago, but it didn't lead to unbootability or anything - so it's weird
<bcrumb>
And yeah, the sscreen is blinking, if I didn't mention it
<bcrumb>
Oh, there was kernel updates yesterday, let me check that out
<bcrumb>
Might have installed by chance or something
bcrumb has quit [Quit: Page closed]
Brainium has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bcrumb has joined #asahi
bcrumb_ has joined #asahi
<bcrumb_>
Heart attack: over. Updating to the latest packages seems to have fixed it.
<bcrumb_>
In fact, this time around it was not _that_ of a heart attack, those former experiences toughened this bread crumb up
<bcrumb_>
In any case, I will drop the habit and advise anyone else to I guess possibly wait if there haven't been kernel updates for a while? I don't know what the Omnissiah has to say on this but I guess it makes sense. I will post the journalctl for reference later - need to redact it first
<bcrumb_>
(drop the habit of updating other packages if there haven't been kernel updates for a while)
<bcrumb_>
here some key words for anyone searching => black screen blinking
bcrumb_ has quit []
bcrumb has quit [Ping timeout: 480 seconds]
unicordion has quit [Ping timeout: 480 seconds]
unicordion has joined #asahi
unicordion has quit [Remote host closed the connection]
Zopolis4 has joined #asahi
unicordion has joined #asahi
unicordion has quit [Remote host closed the connection]
delsol has quit [Remote host closed the connection]
<mort_>
hmm there's something up with the shader cache, linking some shaders into a program gave me the error "vertex shader lacks `main'", then after deleting the mesa shader cache it now gives me a sensible error about GLSL version support
chadmed has quit [Read error: Connection reset by peer]
jess has joined #asahi
bcrumb has joined #asahi
___nick___ has quit [Ping timeout: 480 seconds]
icmroortideotm^ has joined #asahi
jtolio has quit [Quit: Connection closed for inactivity]
mkurz has quit [Ping timeout: 480 seconds]
mkurz has joined #asahi
rayanamukami38 has joined #asahi
rayanamukami3 has quit [Read error: Connection reset by peer]
rayanamukami38 is now known as rayanamukami3
thinkofher has quit []
coderobe has quit [Quit: Ping timeout (120 seconds)]
thinkofher has joined #asahi
coderobe has joined #asahi
nyilas has quit [Remote host closed the connection]
bcrumb has quit [Quit: WeeChat 3.8]
<mkurz>
Just a couple of minutes ago I was not able to log back in again after looking the screen a couple of hours ago.
<mkurz>
kwin_wayland_drm: Failed to create gamma blob! Invalid argument