sirn has quit [Read error: Connection reset by peer]
sirn has joined #asahi
jakebot6 has quit [Quit: Ping timeout (120 seconds)]
jakebot6 has joined #asahi
kov has joined #asahi
chadmed has quit [Quit: Konversation terminated!]
eroux has joined #asahi
millenialhacker has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi
the_lanetly_052 has quit [Ping timeout: 480 seconds]
Zaprit has quit [Remote host closed the connection]
Zaprit has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
Zaprit has quit [Ping timeout: 480 seconds]
Zaprit has joined #asahi
oi_wtf has joined #asahi
Felix[m]123 has joined #asahi
millenialhacker has joined #asahi
MajorBiscuit has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
<bocekcombatbow[m]>
Hi,
<bocekcombatbow[m]>
I want to know how updates are handled when on the fedora fork. Is the experience similar to official Asahi alpha release? Or am I likely to have extra update installation steps or more likely to encounter issues?
<bocekcombatbow[m]>
I want to try and run fedora on the macbook air m1. There is (at least) one tutotial on thr Asahi github about installation process (made by a third party and not Asahi officially).
millenialhacker has joined #asahi
<tpw_rules>
as another unofficial distro maintainer, definitely the latter
Gaspare has joined #asahi
walid has quit [Ping timeout: 480 seconds]
<tpw_rules>
i don't remember who did that one but it would be entirely on them to handle any updates in a nice way for users
millenialhacker has quit [Ping timeout: 480 seconds]
<mps>
tpw_rules: as another distro maintainer I would say it is not much too problematic/complicated
<mps>
(if I had more time to upgrade kernel/m1n1/u-boot regularly)
MajorBiscuit has quit [Quit: WeeChat 3.5]
Gaspare has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi
mps has quit [Remote host closed the connection]
mps has joined #asahi
<tpw_rules>
no it's not hard, it's just that they have to atually do it
mps_ has joined #asahi
thevar1able has quit [Read error: Connection reset by peer]
thevar1able1 has joined #asahi
mps has quit [Ping timeout: 480 seconds]
thevar1able has joined #asahi
thevar1able1 has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi
zzywysm_ has joined #asahi
Gaspare has joined #asahi
zzywysm has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
handlerug has left #asahi [#asahi]
zzywysm_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<bocekcombatbow[m]>
And if I am not satisfied with the distro, I can just uninstall (such that I only have macos again and no dual boot) and then install the official asahi release?
marvin24 has joined #asahi
<tpw_rules>
sure
<bocekcombatbow[m]>
How are updates actually handled? How do I get the updates? Does it fetch them automatically?
marvin24_ has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi
<tpw_rules>
i don't know, i've never used fedora on m1 or otherwise
<bocekcombatbow[m]>
And in the feature support page, does the status "asahi-linux" indicate something that is completely implemented and fully working but not yet upstreamed?
<bocekcombatbow[m]>
Just trying to understand the difference between "asahi-linux" and "WIP"
sirn has joined #asahi
Zaprit has quit [Remote host closed the connection]
Zaprit has joined #asahi
<sven>
WIP usually means there’s some branch somewhere that more or less works
<sven>
asahi-linux means it’s in our downstream fork and will hopefully be upstreamed soon-ish
Gaspare has quit [Quit: Gaspare]
zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
millenialhacker has quit [Read error: Connection timed out]
amarioguy has quit [Ping timeout: 480 seconds]
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
zzywysm has joined #asahi
millenialhacker has joined #asahi
Gaspare has joined #asahi
pent1ckel has quit [Remote host closed the connection]
millenialhacker has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi
pent1ckel has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
Zaprit has quit [Ping timeout: 480 seconds]
Catyre has joined #asahi
Zaprit has joined #asahi
Catyre has quit [Remote host closed the connection]
Catyre has joined #asahi
Catyre has quit [Remote host closed the connection]
Zaprit has quit [Remote host closed the connection]
Zaprit has joined #asahi
doggkruse has joined #asahi
doggkruse has quit [Ping timeout: 480 seconds]
wookey[m] has joined #asahi
Zaprit has quit [Ping timeout: 480 seconds]
<wookey[m]>
HI. I tried installing debian on my Macbook Air, following the 'asahi installer' instructions here: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/, and the scripts reported that my machine appears to be an x86mac. It's defo an M1, and 'arch' reports arm64, but the command in the script 'arch -arm64 ls' says 'unrecognised CPU type in executable, so I can see why it's grumbling. I know absolutely nothing about macOS. I presume I've
<wookey[m]>
booted into some kind of recoveryOS mini-linux, whic his obviously working. Why might 'arch' report the right thing, but arch -arm64 ls is not happy? Coul my ls really be for the wrong arch. I know apple has some kid of translation tech but I presume that wouldn't be functional down in the recovery shell?
<wookey[m]>
s/whic/which/, s/his/is/
<wookey[m]>
* HI. I tried installing debian on my Macbook Air, following the 'asahi installer' instructions here: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/, and the scripts reported that my machine appears to be an x86mac. It's defo an M1, and 'arch' reports arm64, but the command in the script 'arch -arm64 ls' says 'unrecognised CPU type in executable, so I can see why it's grumbling. I know absolutely nothing about macOS. I presume I've
<wookey[m]>
booted into some kind of recoveryOS mini-linux, which is obviously working. Why might 'arch' report the right thing, but arch -arm64 ls is not happy? Could my ls really be for the wrong arch? I know apple has some kid of translation tech but I presume that wouldn't be functional down in the recovery shell?
millenialhacker has joined #asahi
millenialhacker has quit [Ping timeout: 480 seconds]
<jannau>
wookey[m]: what reported that the ssytem is a "x86 mac"? did you install anything on mac os?
<wookey[m]>
The asahi install script complained that 'this appears to be an intel mac', because it ran 'arch -arm64 ls' as a test
<dottedmag>
wookey[m]: Do you have some non-macOS ls early in $PATH by any chance?
<wookey[m]>
The only thing I have installed on this machine is brew and firefox. IIRC brew installs something on the PATH.
<wookey[m]>
I don;t have the machine here right now, so I should probably come back to this conversation when I am in the same room as it :-)
<wookey[m]>
Then I can test stuff.
<wookey[m]>
So booting into 'options' actually boots into the normal MacOS?
<dottedmag>
a chopped down version of it, and it definitely does not contain brew
<jannau>
wookey[m]: did you install x86_64 or arm64 homebrew? probably x86_64 and that's the reason why it doesn't work
<wookey[m]>
That sounds plausible. How would I check? Is it easy to uninstall? I don't even know where apps get put in macOS. My world is 'dpkg or it doesn't exist'. Apparently uninstall is yet another terrifying bash -c 'curl <foo>'.
<wookey[m]>
This sort of thing makes me very nervous
<tpw_rules>
bocekcombatbow[m]: not at all
<tpw_rules>
did you even look at the script?
<bocekcombatbow[m]>
No
<bocekcombatbow[m]>
I am new to this
<bocekcombatbow[m]>
My goal is to use the fedora distro on an m1 macbook air soon. I want to know how to update the downstream kernel changes from asahi
<bocekcombatbow[m]>
To update fedora, I type sudo dnf upgrade, but how do I get asahi updates?
<bocekcombatbow[m]>
On the official alpha the command is: pacman -Syu.
<bocekcombatbow[m]>
What do I type on fedora?
<bocekcombatbow[m]>
Alternatively, can I install gnome instead of KDE on asahi alpha?
<probie_>
Yes
<tpw_rules>
there's nothing you can just type on fedora
<tpw_rules>
you have to compile the kernel yourself, however fedora prefers to do that
<nicolas17>
bocekcombatbow[m]: I think you have to wait for fedora to pakcage the updated kernel
<bocekcombatbow[m]>
Altermatively, I install gnome on asahi linux and grab the flatpacks of all default fedora apps
<dottedmag>
bocekcombatbow[m]: The state of Asahi at the moment is "some assembly required". marcan creates installer with Arch, but everything else is basically "you'd better very well know how to build a kernel in your distro".
Gaspare has quit [Quit: Gaspare]
<jannau>
openbsd install cd image works with the uefi install option
<nicolas17>
not sure about M1 specifically, but I remember stuff like "8.4 (except it's missing feature X, and also has feature Y which is technically in the 8.5 spec)" in other Apple SoCs