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
chrisl has quit [Ping timeout: 480 seconds]
john-cabaj has joined #asahi-alt
john-cabaj has quit [Ping timeout: 480 seconds]
n3ph_ has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
john-cabaj has joined #asahi-alt
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #asahi-alt
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
Halian has quit [Quit: Going offline, see ya! (www.adiirc.com)]
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
john-cabaj has quit [Ping timeout: 480 seconds]
sudtho has joined #asahi-alt
sudtho has quit [Quit: sudtho]
sudtho has joined #asahi-alt
ciara has quit [Remote host closed the connection]
zerdox has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
zerdox has joined #asahi-alt
n3ph_ has joined #asahi-alt
n3ph has quit [Ping timeout: 480 seconds]
sudtho has joined #asahi-alt
Halian|Jardin has joined #asahi-alt
<Halian|Jardin>
Hrmrmrmrmrmr. Asahi ALARM is doing the "wait a while at boot for the network" thing, as well as waiting a long time after I enter my password on the login screen for a reason yet inscrutable. Is there a way to fix these without reïnstalling? and if so how?
<n3ph_>
Probably by debugging the initrd and init processes, I guess.
<Halian|Jardin>
Hooray, that's above my pay grade ;w;
aleph-complex8 has joined #asahi-alt
aleph-complex has quit [Ping timeout: 480 seconds]
aleph-complex8 is now known as aleph-complex
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
<n3ph_>
Halian|Jardin: which iit system are you using?
<n3ph_>
*init
sudtho has quit [Read error: Connection timed out]
<Halian|Jardin>
n3ph_: the default systemd
<n3ph_>
Halian|Jardin: Which login screen are you referring to?
<Halian|Jardin>
KDE's
<Halian|Jardin>
Sorry for not mentioning that up front >.<;
<n3ph_>
And is it a wired connection it is waiting for, or wireless? Does it simply timeout or is the network connection established afterwards?
<n3ph_>
Halian|Jardin: How log does KDE take to startup after you passed your credentials?
<Halian|Jardin>
Wireless. It says it fails the "wait for network to start" step, but Wi-Fi works just fine.
<Halian|Jardin>
At least a minute; I didn't time it.
<n3ph_>
FMPOV network units shouldn't be dependencies for the graphical session, but that's a configuration issue
<n3ph_>
Still, there must be something going on within the unit starting up that it takes so much time
<Halian|Jardin>
Definitely
<n3ph_>
Do you have logs from the AP?
sudtho has joined #asahi-alt
<Halian|Jardin>
Not to hand; I'm not sure where to get them .w.
<n3ph_>
Can you relate timing? Is the assoc working instantly, or does it take as much as time as the unit to finish starting up?
<n3ph_>
Halian|Jardin: So you don't have access to the Access Point?
<Halian|Jardin>
I don't know. It immediately throws error -56, but then sits on the textual boot screen for a minute before "wait for network to start" fails and it loads the GUI.
<Halian|Jardin>
n3ph_: no, I do; else, I wouldn't be able to chat with y'all right now. :P
<n3ph_>
Sorry, I mean administrational access..
<Halian|Jardin>
Oh, sorry
<n3ph_>
Can you elaborate on the error -56?
<Halian|Jardin>
No, I do, but it's one of those stupid new cable Internet ones that has crippled management through the cable company's app :(
<n3ph_>
Do you have more logging to share?
<Halian|Jardin>
n3ph_: not without rebooting, plus I need to BRB anyway
<Halian|Jardin>
Not sure where to find it. I'm really sorry ;-;
<Halian|Jardin>
It didn't start at installation, but when the system froze after returning from sleep and I had to hard reset it
<Halian|Jardin>
._.
john-cabaj has joined #asahi-alt
* Halian|Jardin
grumble grumble, looks like (for other reasons) he's gonna have to reinstall AGAIN :|
Halian|Jardin has quit [Quit: I'll be back.]
Halian|Jardin has joined #asahi-alt
Halian|Jardin has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Halian|Jardin has joined #asahi-alt
chrisl has joined #asahi-alt
Halian|Jardin has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
Halian|Jardin has joined #asahi-alt
Halian|Jardin has quit [Read error: Connection reset by peer]
chrisl has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
Halian|Jardin has joined #asahi-alt
chrisl has joined #asahi-alt
n3ph_ has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
Seti__ is now known as Seti_
Halian|Jardin has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
n3ph has joined #asahi-alt
<n3ph>
IIRC ALARM is Arch-based. Arch kicked out all AUR packages which are aarch64-only. Also there are only a few working on Arch-based Asahi. Don't have the link to the repo at hand ATM..