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
ChaiTRex has joined #asahi
jeisom has joined #asahi
docelalt^ has joined #asahi
hdbngr has joined #asahi
hdbngr has quit [Ping timeout: 480 seconds]
hdbngr has joined #asahi
alexdelorenzo has quit [Remote host closed the connection]
alexdelorenzo has joined #asahi
KxCORP589 has quit [Quit: Bye!]
alexdelorenzo has quit [Read error: Connection reset by peer]
mintakka has quit [Remote host closed the connection]
hdbngr has joined #asahi
lxdr74 has quit [Remote host closed the connection]
lxdr74 has joined #asahi
hdbngr has quit [Ping timeout: 480 seconds]
jeisom has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Harriet has joined #asahi
<Harriet>
I've removed my Arch Linux ARM installation so I could install the new Fedora release. For various networking related issues, I always get TLS errors or connection resets when downloading fedora-39-kde-202312191235.zip. I am able to download it separately. Where should I put it? I'm suspecting /tmp/asahi-install/os but I'm slightly confused while reading the code (not sure what
<Harriet>
templates and urlcaches and zips mean)
edg-l has quit [Ping timeout: 480 seconds]
edg-l has joined #asahi
nicolas17 has quit [Read error: Connection reset by peer]
possiblemeatball has quit [Ping timeout: 480 seconds]
hdbngr has joined #asahi
nicolas17 has joined #asahi
hdbngr has quit [Ping timeout: 480 seconds]
mintakka has joined #asahi
mintakka has quit [Remote host closed the connection]
<Harriet>
I ended up modifying installer_data.json to point to a local HTTP server which worked
pb17 has quit [Ping timeout: 480 seconds]
hdbngr has joined #asahi
pb17 has joined #asahi
ChaiTRex has quit [Remote host closed the connection]
<Graypup_>
hi! I work on NixOS and I've found a wickedly haunted issue (which may be our fault but it doesn't seem shaped like it would be?), where, of six build attempts of the mesa drivers on Apple hardware, two were full of zero bytes (and not page aligned! the first bad zeros were at 0x1012a8, more or less at the start of the GNU_HASH section)
<Graypup_>
I unfortunately have an utterly useless bug report here, and I know it, but it has hit two separate users on the mesa drivers specifically (unsure if this is all builds being haunted on the platform or just the mesa drivers being haunted). I don't have hardware details at hand but can get them later.
<Graypup_>
specifically the file apple_dri.so was full of zeros. I do have the bad files, if they are useful, but I will have to prod a bit to get the build plans. If/when I get build plans I'll try running them on an Ampere machine and see if it reproduces.
shiggitay has joined #asahi
<Graypup_>
the other bit of haunting here is that our mesa build plan normally bit-reproduces, and *did for one of the users who hit this when he forced a rebuild, on the second and third tries*
<Graypup_>
(like, the bug only happened the first time, not the second and third times)
jadesoturi has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
jadesoturi has joined #asahi
<LarstiQ>
dunno if this should be #asahi-alt or not. But, Graypup_ I assume nothing special was done to build, just nixos-rebuild (maybe after a nix-channel --update)?
leah2 has joined #asahi
<Graypup_>
yes, i mean, more spooky commands regarding rebuilding it in the succeeding times for the one person, and running `builtins.filterSource` to force rebuilds that way for the other person who hit it. but yes. approximately
<Graypup_>
the reason I am bringing it up here is that it seems like haunting in the binutils in a way that seems to only affect asahi code, even though it is a different distro.
<LarstiQ>
how do you notice those bad zeros?
<Graypup_>
in both instances, dumping core
<Graypup_>
because like, a substantial part of the executable (one is compressed to 750kb, the other 3mb), is missing
<Graypup_>
i can offer that one of them was mesa 24.1.0, but unsure about the other one (sadly i only have a stack trace from that, core dump and executable are since departed)
<Graypup_>
we are reasonably confident that the disk didn't corrupt them, because the hashes that nix took after the build match the files on disk [not that this matches disk corruption imo at this point]
<LarstiQ>
Graypup_: I can only say I haven't run into that myself using https://github.com/tpwrules/nixos-apple-silicon , but maybe a developer would have some insight into why/when that might happen with mesa
<Graypup_>
yeah and I hope you don't run into it! it seems very spooky
<iyes>
Is there anyone working on laptop microphone support?
stsmwg_ has joined #asahi
stsmwg_ has quit []
hdbngr has joined #asahi
hdbngr has quit [Ping timeout: 480 seconds]
possiblemeatball has joined #asahi
rvalue has joined #asahi
alice has quit [Remote host closed the connection]
alice has joined #asahi
hdbngr has joined #asahi
rvalue- has quit [Ping timeout: 480 seconds]
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
mintakka has joined #asahi
mintakka has quit [Remote host closed the connection]
pb17 has joined #asahi
nightstrike has quit [Quit: Connection closed for inactivity]
pb17 has quit [Ping timeout: 480 seconds]
jeisom has joined #asahi
<opticron>
iyes, iirc, it's WIP, but I don't know that there's been progress on it recently
f_ has joined #asahi
pb17 has joined #asahi
donaldh has quit [Ping timeout: 480 seconds]
JayBeeFOSS has quit [Ping timeout: 480 seconds]
JayBeeFOSS has joined #asahi
delsol has joined #asahi
SalimTerryLi has quit [Ping timeout: 480 seconds]
alarm_ has joined #asahi
<alarm_>
Okay, today's the day I'm going to install openbsd on a macbook, but last time I messed with partitions I bricked my macbook. can anyone tell me what I need to do so that I can be sure I won't obliterate everything?
alarm_ is now known as spuos_
<spuos_>
I know I could probably do it fine but I need reassurance because I can't un-brick this thing myself
opotin65 has joined #asahi
opotin65 has quit []
opotin65 has joined #asahi
delroth has quit [Ping timeout: 480 seconds]
<iyes>
opticron: is there anywhere where i can find the WIP state? i am curious to see what has been done (and who knows maybe i might get nerdsniped into taking it further if i find i can do something useful and nobody is currently working on it)
spuos_ has quit [Remote host closed the connection]
<iyes>
laptop mic support is important to me, and (possibly very naive of me to say this) doesn't seem like it should be too crazy/hard?
spuos_ has joined #asahi
delroth has joined #asahi
<opticron>
iyes, I don't know of anything other than the feature support pages, there just hasn't been any chatter about it. As far as hardness, if you find that no one is doing it and it's important to you, feel free to jump in and see if you can get it working
<opticron>
I'd expect any details to be on the wiki as well
<opticron>
I could swear someone was poking at it and had at least some basic docs on the interface
<j`ey>
eiln
hdbngr has quit [Quit: Lost terminal]
<j`ey>
on github
<iyes>
i need a few pointers before i can jump in. i have never done any macos/asahi RE before. if someone can at least give me a few keywords about what tools/frameworks can be used for this, i could then go and see if i can figure it out.
<iyes>
i am guessing on the linux side this needs a kernel driver, so i should go study the existing alsa drivers for reference.
malfunction54 has quit [Remote host closed the connection]
delsol has quit [Remote host closed the connection]
possiblemeatball has quit [Ping timeout: 480 seconds]
spuos_ has quit [Remote host closed the connection]
spuos_ has joined #asahi
SalimTerryLi has joined #asahi
julio7359 has joined #asahi
iyes has quit [Remote host closed the connection]
iyes has joined #asahi
spuos_ has quit [Remote host closed the connection]
spuos_ has joined #asahi
millefy has joined #asahi
Brainium has joined #asahi
spuos_ has quit [Remote host closed the connection]
spuos_ has joined #asahi
pb17 has joined #asahi
iyes has quit [Ping timeout: 480 seconds]
SalimTer- has joined #asahi
billak has quit [Quit: Konversation terminated!]
SalimTerryLi has quit [Ping timeout: 480 seconds]
iyes has joined #asahi
spuos_ has quit [Quit: Leaving]
f_ has quit [Ping timeout: 480 seconds]
alexdelorenzo has joined #asahi
<fooxi>
Do we have a release date for asahi fedora remix 40?
<fooxi>
Or is it released automatically when regular fedora 40 is released (ie, was released today) ?
<fooxi>
Just wondering if I should just install fedora 39 instead, since the choppiness was not fixed by updating today.
alexdelorenzo has quit [Ping timeout: 480 seconds]
<jannau>
it's not released but will be in the coming days, it will probably not contain a fix for the choppiness though
<fooxi>
I assume the choppiness is upstream in kwin and is just more noticeable on a laptop screen with 60Hz?
<fooxi>
Or is it specific to asahi?
<jannau>
it's upstream changes in kwin but it's unclear why that results in the poor behavior on asahi systems. The changes caused issues on other systems as well but I believe those are resolved
delsol has joined #asahi
<fooxi>
jannau: Thanks for the information! Appreciated.
f_ has joined #asahi
<fooxi>
I will downgrade to F39 (fresh reinstall). It's a new system anyway so not a big hassle really.
<fooxi>
brb.
<fooxi>
jannau: I had some issues with variable refresh rate on my x86 rig causing similar issues. When I locked it to 144 it was fine. Not sure if you do some variable stuff in asahi but just figured I'd tell you in case it's relevant.
<fooxi>
Dont even think the displays allow it.
bpye has quit [Quit: Ping timeout (120 seconds)]
bpye has joined #asahi
alexdelorenzo has joined #asahi
<fooxi>
That's better.
alexdelorenzo has quit [Read error: No route to host]
alexdelorenzo has joined #asahi
alexdelorenzo has quit [Ping timeout: 480 seconds]
alexdelorenzo has quit [Ping timeout: 480 seconds]
docelalt^ has quit [Remote host closed the connection]
alexdelorenzo has joined #asahi
possiblemeatball has joined #asahi
slowlydev has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
iyes has quit [Ping timeout: 480 seconds]
mohit81582263 has quit [Quit: mohit81582263]
mohit81582263 has joined #asahi
slowlydev has quit [Remote host closed the connection]
ChaiTRex has joined #asahi
iyes has joined #asahi
alexdelorenzo has quit [Remote host closed the connection]
alexdelorenzo has joined #asahi
iyes has quit [Ping timeout: 480 seconds]
iyes has joined #asahi
xal has quit []
pb17 has quit [Ping timeout: 480 seconds]
xal has joined #asahi
delsol has quit [Remote host closed the connection]
delsol has joined #asahi
m5zs7k has quit [Read error: Connection reset by peer]
m5zs7k has joined #asahi
sawyer has joined #asahi
<sawyer>
Working on cross-compiling the kernel, kernel itself I'm all set on but the initramfs is tripping me up. Should I be trying to get dracut to do it or should I be cannibalizing the existing asahi provided initramfs and repacking into a new one? I'm working on setting up the tethered boot but a bunch of modules seem broken even after flipping them all to =y
<sawyer>
If this is an asahi-dev question instead sorry about that, I figured here was the less spammy option
chadmed_ has joined #asahi
<chadmed_>
sawyer: in the AsahiLinux/asahi-scripts repo there are a few dracut config files you will need to copy to your host system or mimic with dracut command line switches for the initramfs to work properly
<sawyer>
chadmed_: oh, neat! And that'll work fine for cross-compile?
<chadmed_>
probably not
<chadmed_>
it will pull in your host arch binaries
<chadmed_>
if youre going tethered you should just disable module loading and run everything built in until youve bootstrapped a rootfs
<chadmed_>
and then use that for building "real" kernels
<sawyer>
This is all relatively new to me so sorry for the confusion--do I need to fully bootstrap this? I have asahi already installed on the machine. I tried doing an "allyesconfig"-type-deal and that fell over horribly
darkapex2 has quit [Remote host closed the connection]
darkapex2 has joined #asahi
<sawyer>
basically s/=m/=y/g
pb17 has joined #asahi
<sawyer>
For a little bit I've just been marking all of the asahi-specific configs I could find and making those `=y`, and throwing the initramfs that came from the repos at the end of my tethered boot command but that seems subtly broken (speakersafetyd can't lock the right woofer so ends in a fail loop, graphics is broken but I haven't picked that apart yet)
iyes has quit [Ping timeout: 480 seconds]
<chadmed_>
if you already have asahi installed why are you cross compiling? seems like youre just asking for trouble there with no particularly good reason