The Librem 14 running Pure OS Byzantium off a USB stick did a normal release build of ARSE 0.11.0 in 1m30s. I need to build it in Qubes OS again and make note of the time for a better comparison because I did add two new dependencies between 0.9.0 and 0.11.0.
Lots to like about this machine.
v0.11.0 of A Rust Site Engine is out, and completes my 1.0 feature roadmap items. I've not rev'd to 1.0 as there is some refactoring to be done, and I would like to get that done between now and the time I actually release 1.0.
Earlier this week my significant other, for whom ARSE was created, made her own post without any assistance from me. Now, with 0.11, interested parties can hit also consume content by RSS.
@kyle back in my racing days I used to listen to When The Levee Breaks by Led Zeppelin during every run, so when it comes on now I’m still inclined to want to nail every apex. Not even an up tempo song, but it always helped me remember slow is smooth and smooth is fast.
One more thing I've meant to give a go on my @purism Librem 14 for a while was just doing straight DP over USB-C. I've had a cable for this for a long time from when my NUC was in my office. Anyway, it works fine. Of course having left my regular charger across an ocean this means I can only do this when running on battery since I must charge over USB-C for the time being, but I'm glad it works without issue.
@dredmorbius @kyle probably for the best given the OpenPOWER of such large flames
@kyle when I compiled Buildroot in my projects qube (assigned all 12 threads) it was loud enough I could tell the job was done from another room, but that’ll happen when the whole thing is pegged for 72m!
@kyle yeah, a bit strange indeed. Not sure how much it matters this red hot second. Of course, I could back my stuff up and load clean again to see if that makes a difference. I’ve got plenty of machines available now!
@kyle interesting. It is there, it doesn’t auto load for me and modprobing it makes it show up as in your notes but no dice on showing any more objects in the sys paths. Maybe my EC is older itself?
@kyle what kernel are you on in dom0 - dkms complained about 5.4.125-1.fc25.qubes.x86_64. Looks like if I boot one of the older kernels it may work though.
@kyle excellent, thanks for sharing.
For any other Librem 14 users running Qubes, I was able to install the librem-ec-acpi-dkms package in Qubes dom0, which lets you have more control over the embedded controller including setting charge thresholds. I documented my steps here: https://source.puri.sm/-/snippets/1170
@twrightsman @kyle in Qubes not even changing manually worked for me, but the USB dongle the headphones came with worked fine and I even did a Matrix call with a friend using it after I sorted my Synapse and COTURN issues.
@twrightsman @kyle I’ve not seen an issue with it powering off with the hub plugged in so much as I’ve seen it run out of battery that way. The hub appears to drop off (dom0 and sys-usb both see it coming and going with an annoying frequency) and when that happens charging also stops. My shutdowns seem to be related to that happening while I was already low on juice and doing CPU intensive tasks that happily drained the battery dead. I’ve stopped using the hub for now.
@kyle nice! My backup imported smoothly as well. My insert key doesn’t seem to work, nor does my audio jack, but otherwise most everything is as expected save for the USB-C hub shenanigans. If I get any free time this week I plan on live booting PureOS to see if those things work there or not.
@rbrown dom0 and sys-usb both see the hub disappear and reappear so I think it may just be some module instability. Will burn a live USB of PureOS and see what happens in that environment. My old laptop is also on QubesOS, and that’s really where I do most of the things where Qubes magic is really beneficial.
The audio jack doesn’t work at all in Qubes, but that was true of my T460s too. A USB audio device sorts that, and my headset came with one. The hub has one too. Both work.
@absc@mastodon.uno @loweel most of the time my homeserver isn’t having huge problems, but when it does synapse is generally to blame. I do have much more machine, but it’s under-utilized. Still, I feel like most things ought to be able to run much lighter. I used run NAT with QoS, an MTA, and SIP on a 586 with 128MB of RAM and a 512MB disk. Shouldn’t need a quad core EPYC and 8GB of RAM to run a website and a chat service.
@loweel yeah, I was told not to run an instance on an embedded device... it’s a quad core EPYC with 8GB of RAM and NVMe block storage...
My server was created because I wanted to secure my own chat and voice with friends during my overseas assignment. When I did the same in 2005 during a combat deployment I setup Asterisk on an embedded device I hooked up to very slow (and expensive) satellite internet. That worked flawlessly. Guess this is what progress looks like 😂
I like to work with my hands. That may mean hammering out solutions to complex problems in #Python or #Rust, building things in my shop, or spinning yarn to knit something warm. You’ll likely see some of all of that here. By day (and sometimes night) I keep >13k nodes and services alive in the Electric Vehicle sector.
PGP: FCBF 31FD B34C 8555 027A D1AF 0AD2 E852 9F5D 85E1