I am extremely happy that after far too long fighting build systems, I have managed to make #nixwrt compile the 80211 subsystem and ralink wifi drivers from linux 5.8.something via the linux-backports project, and the resulting modules do actually load into the 5.4.64 kernel on the target device

I resorted to turning config options on and off randomly at a few points - there is plenty of cleanup yet to do before this can be merged into main


Upgrade to kernel v5.4 by telent · Pull Request #12 · telent/nixwrt

WIP: I am rearranging the kernel significantly. The plan is split...


Daniel Barlow boosted

Dear fediverse

My next-door neighbour has erected a flagpole with a St George's flag on it, while engaged in a long rant about "lefties" and "communist fascists" and "they can't tell me what to do".

We're about as white middle class English as it's possible to get, so not threatened. Just disappointed, I guess.

Wasted many (well, small single digit number, but still too many) hours trying to figure out why my derivation worked perfectly in nix-shell but failed to find python in nix-build. Turns out it's not failing to find python, it's failing to find /usr/bin/env.

Something something assumptions something something

Daniel Barlow boosted

Daniel Barlow boosted

self reply

I may have hit on a really good (and much simpler) reason that I can't build a gl-mt300n image that runs on this hardware. This hardware is not a gl-mt300n, it's a gl-mt300a.

There's probably some kind of life lesson here about remote development. Or about validating assumptions, or maybe just about not being an idiot

Linux version 5.4.64 (nixbld@nixwrt.builder) (gcc version 9.3.0 (GCC)) <a href="https://terse.telent.net/tags/1" class="mention hashtag" rel="tag">#<span>1</span></a> Tue Sep 15 13:33:49 UTC 2020

Pausing here for a brief "woohoo!"

It doesn't mount the root fs yet, maybe (it suddenly occurs to me literally as I write this toot) because I forgot to build the phram target. And then the next big task is to build wireless modules from linux-backports. And maybe, y'know, actually commit some stuff to git?

#nixwrt #mips #nixpkgs #WhoSaysSentencesCantStartWithConjunctions

Was not expecting that use of the linux backports project would involve building an OCaml app, but hey, apparently it does

Typical of the Linux kernel that the ability to build a stable kernel with newer drivers is contingent on using a version of coccinelle newer than the newest stable release

(Though, the backports project does itself appear to be some kind of magic, so honestly I'm not really criticising, just grousing)

TFW you spend an evening fighting acme/file permissions to add an SSL cert to your XMPP server, then realise afterwards you don't know anyone with an XMPP account anyway

(The time is not wasted, in that I want XMPP so my server can alert me when bad things[*] happen to it, I'm just thinking that it could be nontrivial to test that it works )

[*] the particular set of bad things I have in mind necessarily excludes "help, I lost network connectivity to the xmpp server", yes

Turns out that # is not the best keybinding for "report as spam" in notmuch-search mode, because it's bound to "Print message" in notmuch-show mode. Well, that explains why my emails are coming out of the printer at random times.

The weirdest thing is I can't even remember spending the four and a half hours I believed it would take to make this flakey wifi printer work on a Linux box in the first place, so was exceedingly surprised to have anything coming out of the printer at random or indeed any times