jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<jaeger> So, neither of the slackware images is really useful, at least not the latest ones... the 6.0.2 locks up frequently and the 5.19.whatever just gives a black screen after boot. I might try one of the older releases tomorrow
<jaeger> On the subject of the phone being a decent mobile device with a dock setup, the steamdeck is pretty good for that as well :)
guido_rokepo has quit [Quit: guido_rokepo]
guido_rokepo has joined #crux-arm
<beerman> the steamdeck can also be utilized for gaming, i wouldn't dare to try this on the pine 😛
<beerman> the pi finished llvm, compiler-rt, clang, lld, rust, nodejs so far
<pitillo> jaeger: same fault as our old images which hadn't wpa_supplicant nor linux-firmware on the release.
<pitillo> about the version, I believe 5.15 is a good one which has full support (there is a matrix overthere explaining what is supported in all different kernel versions)
<pitillo> I'm currenrly building modules... when it ends, I'll give a try
<pitillo> the steamdeck seems a very nice toy btw... for gaming and for "playing" with distro development, the problem os price (a bit expensive)
<beerman> i think you get more than you pay for with the steam deck
<beerman> but it is expensive
<beerman> i wouldn't buy one myself, i am not gaming that much lately
<pitillo> very good new beerman, it seems to run smoothly with all those beasts, thanks for sharing results, they are promising
<beerman> but: i love that the device exists. its pushing the market boundaries a lot which is great
<beerman> pitillo: you are welcome, of course. It ran fine on the 32bit build i have been running almost the past 2 years too already
<pitillo> yeah, me too. I'd like it for both, gaming and playing... but not enought time for any of them (I have the kid currently chasing me to tickle him xD
<beerman> haha the game of life
<beerman> thats just next level stuff 😄
<pitillo> nice to know that too, but to get all its power, 64b is needed and your tests are really promising to get a rock solid device (my rpi3 with the 64b release was a beast too)
<pitillo> true... more than next level... it's another league xD
<beerman> haha
<beerman> anyway, going to do christmas grocery shopping now. got a few cookies to bake and dishes to prepare.
<beerman> i'll see if i can get sway up and running in the meantime. first thing i'd like to setup is mail and some basics
<pitillo> great
pitiIIo has quit [Quit: leaving]
<pitillo> the kernel is creating a lot of modules... most of them are not needed for this device... so I think it won't be a good one
<pitillo> 5.16 doesn't boot neither... not many time to debug it over serial
<beerman> foot compiled with lto and pgo, neat
<beerman> not too big of a task, but so nice that it does
genpaku has quit [Read error: Connection reset by peer]
guido_rokepo has quit [Remote host closed the connection]
genpaku has joined #crux-arm
guido_rokepo has joined #crux-arm
<pitillo> niiiice
guido_rokepo has quit [Quit: guido_rokepo]
sajcho has joined #crux-arm
<sajcho> Guys just for info. How long does rust take to compile on rpi4.
<beerman> didn't look at the time
<beerman> i'd say between 6 to 9 hours, roughly. i guess it strongly varies on the setup as well
<sajcho> Thank you. That's not bad. Good luck with your next job.
<jaeger> rebuilding the toolchain did not fix the prt-get issue, I kinda expected that it would
sajcho has quit [Quit: Client closed]
<pitillo> interesting jaeger, I thought it may be will fix it... but like I said, the mix between arches (32b on 64b) and specific sub arches (armv7 vs armv5) didn't allow me to be very optimistic
<pitillo> good luck with your next job? what does that mean?
<beerman> build job, hopefully
<beerman> 😛
<pitillo> xD
<pitillo> jaeger: I've tested 3.6 on the cubieboard (jailed) and it's working fine, so there is no mix between armv5 and armv7 (all devices are arv7*)
<pitillo> I believe the problems comes from the container
<pitillo> not sure if --platform docker option can help, because I think it's autodetected (linux/arm/v7 and linux/arm/v6)
<pitillo> may be forcing it to be v6 can help, but this is far from my knowledge
<jaeger> I'm going to rebuild core as well to see if that matters... if that doesn't fix it I will assume the container is doing something stupid
<pitillo> ok
<pitillo> let's see if manufacturers start building this kind of laptops....
<pitillo> here I'm on the way with the cubieboard2 building the generic release 32b.... I want to see how goes stage0 binutils bump... that's the cretical point atm
sajcho has joined #crux-arm
<sajcho> Good. I'll write it differently. Good luck in whatever you want to achieve. (y)
<beerman> no worries, thanks a lot
<beerman> 👍️
sajcho has quit [Client Quit]
<pitillo> jjajajajaja
<pitillo> he's a bit strange or it's me?
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-xorg-arm64 ]: mesa: update to 22.3.1
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> i dunno 😄 i think i understand correctly
<beerman> so i've built flatpak and seahorse but haven't tried sway yet
<pitillo> me too, I hope he doesn't take anything wrong, but it seems strange for me the connections and disconnections (and following the log I believe). May be restricted connection or to don't waste quote...
<beerman> oh, i haven't noticed that. i don't even see quits or joins
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: libtiff: remove overlay, not needed anymore
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> pitillo: /etc/pam/.d/common-session is missing the dumb runtime dir module
<beerman> but sway seems to run fine
<beerman> the dbus package is referencing old /var/run/dbus directory, the rc scripts also doesn't create the correct one in /run
<pitillo> let me check beerman
<pitillo> beerman: do you care abput creating an issue for it?
<pitillo> I mean in girhub.... your contribution here is a present for the project, but if I fix it, your report isn't shown
<pitillo> girhub xD
<pitillo> if you prefer to be innthe shadow, I can understand, but I'd like to see your work where it should be
<pitillo> I hope this doesn't sound bad
<beerman> ah, don't worry, i don't need my report to be shown 🙂
<beerman> i can of course do it
<beerman> ah, need a kernel with unpriviledged user namespace for ungoogled-chromium flatpak, maybe not tonight anymore
<pitillo> beerman: whatever you want, your choice. May be I'll take a look when wife goes to bed or maybe I'll do it tomorrow...
<jaeger> I think I have found the slowest uSD card there is, heh
<pitillo> xD
<beerman> pitillo: why is dbus in core anyway? 😄
<beerman> it should be in the opt overlay
<pitillo> if we want to provide wpa_supplicant in the release, we must move some to core and maintain them there
<pitillo> thank you!
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-core-arm64 ] fix rc.dbus (#4)
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-core-arm64 ] dbus: update .signature
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> ah, ok
<beerman> gotcha
<beerman> sure
<beerman> good idea to use github, imo 🙂 enables that kind of pr easily
<pitillo> I haven't used github until sepen pointed out and it's a good enviroment for a project like this one (there are pros and cons of course)
<beerman> i mean, mostly pros, really. there is some nifty features and we are not writing precious code to be harvested on
<beerman> you would need a sign action to sign the pull request, you already have the REPO bump 😄