#
#asahi-alt · 2025-02-01 15:21
chaos_princess> implying uk is not a failed state
#asahi-alt · 2025-02-01 15:20
chadmedi kinda resent that ezpz has become anglosphere vernacular because z is 'zed' not 'zee' in states that have not failed
#asahi-alt · 2025-02-01 10:44
mpsj`ey: ah. thanks
#asahi-alt · 2025-02-01 10:24
j`eyeasy peasy
#asahi-alt · 2025-02-01 10:21
mps chadmed: what means 'ezpz'?
#asahi-alt · 2025-02-01 09:28
chadmedoh it has ezpz
#asahi-alt · 2025-02-01 09:28
chadmedunless the gentoo mirror hasnt picked it up yet
#asahi-alt · 2025-02-01 09:28
chadmedi've replaced m1n1 1.4.19 with 1.4.21 in the gentoo overlay so it should be safe for ~arm64 folks to upgrade now
#asahi-alt · 2025-02-01 01:32
HalianI haven't had freeze-after-sleep issues after reinstalling Asahi ALARM, this time the GNOME version (yet, knock on wood).
#asahi-alt · 2025-01-29 19:58
HalianOop, nevermind, it just takes even longer to enter the GUI after failing to wait for the network to be configured, which is still infuriating :(
#asahi-alt · 2025-01-29 19:58
HalianThe first boot went peachy keen, but a system update broke it ;-;
#asahi-alt · 2025-01-29 19:57
HalianOn a freshly installed copy of Asahi ALARM GNOME, not only am I getting the -52 wireless error and the long wait for it to fail to configure the network, but it doesn't enter the GUI afterward
#asahi-alt · 2025-01-29 19:57
Halianfacedesk
#asahi-alt · 2025-01-28 17:35
n3phIIRC 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..
#asahi-alt · 2025-01-28 14:21
Halian|Jardingrumble grumble, looks like (for other reasons) he's gonna have to reinstall AGAIN :|
#asahi-alt · 2025-01-28 14:05
Halian|Jardin._.
#asahi-alt · 2025-01-28 13:46
Halian|JardinIt didn't start at installation, but when the system froze after returning from sleep and I had to hard reset it
#asahi-alt · 2025-01-28 13:46
Halian|Jardinn3ph: ieee80211 phy0: brcmf_dongle_roam: WLC_SET_ROAM_DELTA error (-52)
#asahi-alt · 2025-01-28 13:45
Halian|JardinBack; I forgot that Asahi ALARM currently hangs when returning from sleep
#asahi-alt · 2025-01-28 10:38
n3ph_zerdox: source: https://github.com/chadmed/asahi-overlay/tree/main/sys-kernel/asahi-kernel
#asahi-alt · 2025-01-28 10:38
n3ph_You may use the FAR one: https://asahi.jannau.net/cgit/@asahi/kernel/kernel.git/plain/kernel-aarch64-16k-fedora.config?id=0f8f1fbbbace045751fa63ffbe6e3024bb5f195e
#asahi-alt · 2025-01-28 10:35
zerdoxhi everyone, where could i find a kernel config? my old one stopped working for some reason
#asahi-alt · 2025-01-28 10:28
n3ph_Halian|Jardin: `journalctl -b -1 | wgetpaste`
#asahi-alt · 2025-01-28 10:23
Halian|JardinBRB
#asahi-alt · 2025-01-28 10:23
Halian|JardinNot sure where to find it. I'm really sorry ;-;
#asahi-alt · 2025-01-28 10:23
Halian|Jardinn3ph_: not without rebooting, plus I need to BRB anyway
#asahi-alt · 2025-01-28 10:23
n3ph_Do you have more logging to share?
#asahi-alt · 2025-01-28 10:22
Halian|JardinNo, I do, but it's one of those stupid new cable Internet ones that has crippled management through the cable company's app :(
#asahi-alt · 2025-01-28 10:22
n3ph_Can you elaborate on the error -56?
#asahi-alt · 2025-01-28 10:22
Halian|JardinOh, sorry
#asahi-alt · 2025-01-28 10:22
n3ph_Sorry, I mean administrational access..
#asahi-alt · 2025-01-28 10:22
Halian|Jardinn3ph_: no, I do; else, I wouldn't be able to chat with y'all right now. :P
#asahi-alt · 2025-01-28 10:22
Halian|JardinI 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.
#asahi-alt · 2025-01-28 10:21
n3ph_Halian|Jardin: So you don't have access to the Access Point?
#asahi-alt · 2025-01-28 10:21
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?
#asahi-alt · 2025-01-28 10:21
Halian|JardinNot to hand; I'm not sure where to get them .w.
#asahi-alt · 2025-01-28 10:20
n3ph_Do you have logs from the AP?
#asahi-alt · 2025-01-28 10:20
Halian|JardinDefinitely
#asahi-alt · 2025-01-28 10:20
n3ph_Still, there must be something going on within the unit starting up that it takes so much time
#asahi-alt · 2025-01-28 10:20
n3ph_FMPOV network units shouldn't be dependencies for the graphical session, but that's a configuration issue
#asahi-alt · 2025-01-28 10:19
Halian|JardinAt least a minute; I didn't time it.
#asahi-alt · 2025-01-28 10:19
Halian|JardinWireless. It says it fails the "wait for network to start" step, but Wi-Fi works just fine.
#asahi-alt · 2025-01-28 10:19
n3ph_Halian|Jardin: How log does KDE take to startup after you passed your credentials?
#asahi-alt · 2025-01-28 10:19
n3ph_And is it a wired connection it is waiting for, or wireless? Does it simply timeout or is the network connection established afterwards?
#asahi-alt · 2025-01-28 10:19
Halian|JardinSorry for not mentioning that up front >.<;
#asahi-alt · 2025-01-28 10:18
Halian|JardinKDE's
#asahi-alt · 2025-01-28 10:18
n3ph_Halian|Jardin: Which login screen are you referring to?
#asahi-alt · 2025-01-28 10:18
Halian|Jardinn3ph_: the default systemd
#asahi-alt · 2025-01-28 10:17
n3ph_*init
#asahi-alt · 2025-01-28 10:17
n3ph_Halian|Jardin: which iit system are you using?

plus ›