<craige_>
That's the path I'd go down. Perhaps even an multi-ethernet port SBC and just sideline the WDR4300 will be the best first step.
<hexa->
I have a setup with WPA3 (SAE) at home and one with WPA2-EAP at our local hackerspace
<hexa->
if you want a ubiquiti dishes, probably for it's ceiling mount capability, look at aruba instant on ap11 instead
<hexa->
s/want a/want some/
<hexa->
it needs a custom usb cable to flash, but they're equally priced to the ac lite, but they're 2x2 ac wave2
<hexa->
an ipq4029 (armv7, 4x717 Mhz)
<craige_>
Thanks.
<angerman>
craige_: tbqh I have the ISPs modem connected to a Ubiquiti Edgerouter, which connects to the cabling in the wall, and then there are two Ubiqiti AP's at the far ends of the apt. No nix involved 🤷
<hexa->
if edgerouters where somewhat better supported than openwrt they would be fine :p
<hexa->
even community support for openwrt is better than the ubnt customer service story
<craige_>
My WDR4300 with OpenWRT is a great success story for OpenWRT - as long as you get the initail hardware correct, I spent some time doing that with that router.
<samueldr>
my two routers are openwrt based, the second one only bought to get a gigabit interfaced router
<samueldr>
I want to see nixwrt (by telent / dan//_b`) get better :)
<clever>
> Status of Raspberry Pi 4 in Mainline
<{^_^}>
error: syntax error, unexpected IN, expecting ')', at (string):315:26
<hexa->
samueldr: he focuses too much on tiny devices :<
<samueldr>
hm?
<samueldr>
isn't it the point?
<hexa->
tiny = < 8 MB Flash & <= 32 MB RAM
<samueldr>
yes
<hexa->
devices even openwrt considers a dead-end
<clever>
hexa-: *looks*
<samueldr>
>> An experiment, currently, to see if Nixpkgs is a good way to build an OS for a domestic wifi router or IoT device, of the kind that OpenWRT or DD-WRT or Tomato run on.
<clever>
hexa-: this compiles down to a 2mb executable
<samueldr>
I know that it is a dead-end technologically speaking, compared to good hardware
<hexa->
> DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version (18.06 or later) onto it! See 4/32 warning for details.
<clever>
add in the kernel, and that could fit in an 8mb flash
<{^_^}>
error: syntax error, unexpected IF, expecting ')', at (string):315:46
<delroth>
hi there, probably more likely to get an answer here than on #nixos... anyone using nixos on an aarch64 machine with 64KB pages? seems like patchelf breaks binaries by aligning segments to 4K regardless of max architectural support
<delroth>
wondering if I'm doing anything wrong, if it's a known problem, or just something nobody has encountered before
<simpson>
Is 64KiB an uncommon page size? I don't know what normally happens on ARM.
<simpson>
Ah, interesting. patchelf can take custom page sizes.
<delroth>
I don't think it's that rare, but Linux defaults to 4K still
<delroth>
this is to run on some hardware with a fairly rare SoC and some driver code that has likely only been tested with 64K pages based on how it's configured in production units
<delroth>
so I wanted to minimize the risks of breakage and keep 64K pages, but I'm getting binaries in my initrd that Linux cannot load
<delroth>
(bin/busybox: error while loading shared libraries: bin/busybox: ELF load command alignment not page-aligned)
<delroth>
seems like it defaults to whatever the builder is configured to use right now
<delroth>
that's an interesting "leak" :)
<delroth>
and I'm going to guess that whatever builds hydra packages is 4K pagesize...
<simpson>
Mm, yes, interesting r13y concern. The GNU way would be to alter the system's triple name, and use the triple to ensure that "arm7lwchonkypages" or whatever is treated differently.
<simpson>
But maybe it'd be possible to parameterize stdenv instead? Or
<delroth>
I don't think GNU has different triples for this specifically though, it defaults to align to the highest page size supported by the platform
<simpson>
*Or maybe even just override patchelf alone.
<delroth>
which seems like a sane default, and it seems like people have suggested doing that in patchelf in 2016 but the PR is still pending :(
<{^_^}>
#89317 (by delroth, 11 seconds ago, open): patchelf: increase the page size alignment on Aarch64 to support 64K pages
FRidh has quit [Ping timeout: 240 seconds]
<simpson>
+1 to the idea, but I too lack the hardware diversity to test.
FRidh has joined #nixos-aarch64
<delroth>
I mean, making sure it doesn't break the world on 4K pages is likely enough
<delroth>
I can confirm it unbreaks my 64K pages system :)
<delroth>
given that currently busybox in the initrd is patchelf'd, it should be fairly easy to notice breakages.
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
<cole-h>
Notice: The community box will be redeployed (there was a failure in the earlier weekly redeploy due to -- presumably -- Packet maintenance) in ~10 minutes.
zupo has joined #nixos-aarch64
bqy has quit [*.net *.split]
puzzlewolf has quit [*.net *.split]
zupo_ has quit [Ping timeout: 260 seconds]
danielrf[m] has quit [Ping timeout: 240 seconds]
Ericson2314 has quit [Ping timeout: 240 seconds]
edrex has quit [Ping timeout: 252 seconds]
NickHu has quit [Ping timeout: 260 seconds]
hsngrmpf[m] has quit [Ping timeout: 246 seconds]
loyon has quit [Ping timeout: 252 seconds]
vika_nezrimaya[m has quit [Ping timeout: 252 seconds]
thefloweringash has quit [Ping timeout: 256 seconds]
Irenes[m] has quit [Ping timeout: 256 seconds]
hpfr[m] has quit [Ping timeout: 256 seconds]
alj[m] has quit [Ping timeout: 252 seconds]
kai_w has quit [Ping timeout: 246 seconds]
Smith[m] has quit [Ping timeout: 244 seconds]
cornu has quit [Ping timeout: 244 seconds]
colemickens has quit [Ping timeout: 244 seconds]
comrandroxaos[m] has quit [Ping timeout: 244 seconds]
goibhniu has quit [Ping timeout: 244 seconds]
Ox4A6F has quit [Ping timeout: 240 seconds]
JJJollyjim has quit [Ping timeout: 252 seconds]
Danct12[m] has quit [Ping timeout: 260 seconds]
matthewbauer has quit [Ping timeout: 260 seconds]
bennofs[m] has quit [Ping timeout: 260 seconds]
la-s has quit [Ping timeout: 256 seconds]
puzzlewolf has joined #nixos-aarch64
bqy has joined #nixos-aarch64
quinn has joined #nixos-aarch64
puzzlewolf has quit [Ping timeout: 244 seconds]
bqy has quit [Ping timeout: 244 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr>
I don't think that notification is required, but thanks
<cole-h>
It's not, but I feel like it's nice for people to know what's going on. Related note: deploy failed again; Packet maintenance wasn't the problem. Waiting on help from benevolent overlord.
Thra11 has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
goibhniu has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
tilpner has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
cornu has joined #nixos-aarch64
bennofs[m] has joined #nixos-aarch64
Irenes[m] has joined #nixos-aarch64
kai_w has joined #nixos-aarch64
Ericson2314 has joined #nixos-aarch64
la-s has joined #nixos-aarch64
vika_nezrimaya[m has joined #nixos-aarch64
NickHu has joined #nixos-aarch64
Danct12[m] has joined #nixos-aarch64
danielrf[m] has joined #nixos-aarch64
comrandroxaos[m] has joined #nixos-aarch64
bqy has joined #nixos-aarch64
thefloweringash has joined #nixos-aarch64
hsngrmpf[m] has joined #nixos-aarch64
loyon has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
hpfr[m] has joined #nixos-aarch64
JJJollyjim has joined #nixos-aarch64
dtz has joined #nixos-aarch64
puzzlewolf has joined #nixos-aarch64
edrex has joined #nixos-aarch64
alj[m] has joined #nixos-aarch64
matthewbauer has joined #nixos-aarch64
Smith[m]1 has joined #nixos-aarch64
colemickens has joined #nixos-aarch64
andi- has quit [Remote host closed the connection]