pitillo changed the topic of #crux-arm to: CRUX-ARM 3.8 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-8 | Logs: https://libera.irclog.whitequark.org/crux-arm/
_whitelogger has joined #crux-arm
darfo has joined #crux-arm
darfo has quit [Ping timeout: 245 seconds]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm/3.8 ]: prt-get: add -D_FILE_OFFSET_BITS=64 flag to build
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm/3.7 ]: prt-get: add -D_FILE_OFFSET_BITS=64 flag to build
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm/3.8 ]: filesystem: fix release, bump to release 3
crux-arm-bot has left #crux-arm [#crux-arm]
darfo has joined #crux-arm
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ opt-arm/3.8 ]: nspr: update to 4.37
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ opt-arm/3.8 ]: nss: update to 3.114
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ core-arm64/3.8 ]: filesystem: fix release, bump to release 3
crux-arm-bot has left #crux-arm [#crux-arm]
<r0ni> anyone know what would cause networkmanager to show me avail wifi but never accept my password? (it IS correct)
<r0ni> actually now that i think about it, maybe it's wpa_supplicant after all, I know I patched it for rpi5 and it did work on 3.7, but I need to reevaluate the situation. I'll have to try 2.10 and see if it connects properly then so i know if it wpa_supplicant or not
<beerman> there might be a problem with networkmanager? I got a problem with 802.1x wired auth too
<beerman> or is this with kde? my problem is on the kde system
<r0ni> well i have a realtek usb wifi that when i plug it in, it works right away, so its def just the rpi5 broadcom wifi, (which i know does work) but either wpa_supp patches are messed or the raspi firmware I'm using is bad (tho that should be trumped by the linux-firmware port)
<r0ni> but nah this is just 'nmtui'
<r0ni> i've not gotten as far as putting a DE in place yet, I'd tried using reg wpa_supplicant before and it wasn't working as-is either so i tried netman next... but now I have to wait cuz for some odd reason it decided to build llvm
<r0ni> I don't recall that being in my sysup list, so something must have needed it as a dep
<r0ni> tis ok, i need to just keep track of all my issues so i fix the rpi5 repo accordingly
<cruxbridge> <pitillo (@pitillo:crux.nu)> LLVM is taken from mesa… not sure if you have it installed
<cruxbridge> <pitillo (@pitillo:crux.nu)> The wifi stuff smells to firmware or wpa_supplicant… I’d go for manual test of wpa_supplicant to get some clues about the problem, but I don’t really know if network manager relays on it….
<r0ni> me either TBH, i know it uses dhcpcd or can use an internal dhcp client, neither of those changed anything... I'll look into wpa_supp later tho, that will give me answers no doubt
dlcusa has quit [Read error: Connection reset by peer]
dlcusa has joined #crux-arm