<matthewcroughan>
maybe it's that removal of "boot.loader.generic-extlinux-compatible.enable = true;"
<matthewcroughan>
ah no, that's set to true no matter wah
rajivr has joined #nixos-aarch64
<matthewcroughan>
- In `/nix/store/iw4agb8mx3qyfk3yn84v5krxih4x7zyd-source/nixos/modules/installer/cd-dvd/sd-image-armv7l-multiplatform.nix': true
justanotheruser has joined #nixos-aarch64
Church- is now known as aleph-
ryantrinkle has quit [Ping timeout: 240 seconds]
ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
dsal has quit [Ping timeout: 246 seconds]
dsal has joined #nixos-aarch64
<matthewcroughan>
hmm
<matthewcroughan>
ext4-fs.img.zst-armv7l-unknown-linux-gnueabihf> /nix/store/ilakjh4f6xcxiis1mipad03jhp2mys4d-extlinux-conf-builder.sh: line 133: cd: /nix/var/nix/profiles: No such file or directory
<matthewcroughan>
Is this more insidious than it looks?
<matthewcroughan>
Yeah.. I have an example to share now too.
<matthewcroughan>
it's pretty good, I turned samueldr's stuff into a flake, but still no dice on armv7l.
<matthewcroughan>
gotta sleep now, too tired
aminechikhaoui8 has joined #nixos-aarch64
bdju_ has joined #nixos-aarch64
Gaelan has quit [*.net *.split]
aminechikhaoui8 is now known as aminechikhaoui
Gaelan has joined #nixos-aarch64
V has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
cole-h has quit [Ping timeout: 260 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
Laa[m] has quit [Quit: Idle for 30+ days]
orivej has quit [Ping timeout: 260 seconds]
Liam[m] has quit [*.net *.split]
Raito_Bezarius has quit [*.net *.split]
cwfefifofum[m] has quit [*.net *.split]
c00w has quit [*.net *.split]
angerman has quit [*.net *.split]
KalBot has quit [*.net *.split]
hiroshi[m] has quit [*.net *.split]
zhaofeng_alt has quit [*.net *.split]
luxemboye has quit [*.net *.split]
nicoo has quit [*.net *.split]
Gaelan has quit [*.net *.split]
V has quit [*.net *.split]
aminechikhaoui has quit [*.net *.split]
ryantrinkle has quit [*.net *.split]
AmandaC has quit [*.net *.split]
ajs124 has quit [*.net *.split]
Andoriyu has quit [*.net *.split]
julm has quit [*.net *.split]
mla has quit [*.net *.split]
dotlambda has quit [*.net *.split]
patagonicus has quit [*.net *.split]
clever has quit [*.net *.split]
sigtrm has quit [*.net *.split]
noonien has quit [*.net *.split]
Mirrexagon has quit [*.net *.split]
pinpox has quit [*.net *.split]
njd has quit [*.net *.split]
delroth has quit [*.net *.split]
disasm_ has quit [*.net *.split]
justanotheruser has quit [*.net *.split]
dsal has quit [*.net *.split]
srk has quit [*.net *.split]
Irenes has quit [*.net *.split]
pbb has quit [*.net *.split]
ehmry has quit [*.net *.split]
hexa- has quit [*.net *.split]
bridge[evilred] has quit [*.net *.split]
misuzu has quit [*.net *.split]
illustris has quit [*.net *.split]
edrex has quit [*.net *.split]
Jassuko[m] has quit [*.net *.split]
l-as has quit [*.net *.split]
mvnetbiz_ has quit [*.net *.split]
zuh0 has quit [*.net *.split]
anton[m] has quit [*.net *.split]
hyperfekt has quit [*.net *.split]
kcalvinalvin has quit [*.net *.split]
matthewcroughan has quit [*.net *.split]
v0|d has quit [*.net *.split]
pie_ has quit [*.net *.split]
h0m1 has quit [*.net *.split]
leonardp has quit [*.net *.split]
cepheus has quit [*.net *.split]
tdeo has quit [*.net *.split]
lopsided98_ has quit [*.net *.split]
ServerStatsDisco has quit [*.net *.split]
n0emis[m] has quit [*.net *.split]
Danct12[m] has quit [*.net *.split]
kloenk has quit [*.net *.split]
JJJollyjim has quit [*.net *.split]
Dandellion has quit [*.net *.split]
hpfr has quit [*.net *.split]
danielrf[m] has quit [*.net *.split]
davidak[m] has quit [*.net *.split]
makefu has quit [*.net *.split]
blueberrypie has quit [*.net *.split]
thefloweringash has quit [*.net *.split]
DavHau[m] has quit [*.net *.split]
gh0st[m]1 has quit [*.net *.split]
dxb[m] has quit [*.net *.split]
mica[m] has quit [*.net *.split]
spacetato has quit [*.net *.split]
craige has quit [*.net *.split]
Ericson2314 has quit [*.net *.split]
cstrahan has quit [*.net *.split]
alunduil has quit [*.net *.split]
alexeyan has quit [*.net *.split]
artturin has quit [*.net *.split]
LinuxHackerman has quit [*.net *.split]
evils has quit [*.net *.split]
colemickens has quit [*.net *.split]
jdnixx-M1 has quit [*.net *.split]
gchristensen has quit [*.net *.split]
ejpcmac has quit [*.net *.split]
CRTified[m] has quit [*.net *.split]
railroadmanualji has quit [*.net *.split]
bennofs[m] has quit [*.net *.split]
puzzlewolf has quit [*.net *.split]
roberth has quit [*.net *.split]
siraben has quit [*.net *.split]
nyanotech has quit [*.net *.split]
ashkitten has quit [*.net *.split]
ky0ko has quit [*.net *.split]
sorear has quit [*.net *.split]
Mic92 has quit [*.net *.split]
elvishjerricco has quit [*.net *.split]
feepo has quit [*.net *.split]
rajivr has quit [*.net *.split]
fgaz has quit [*.net *.split]
manveru[m] has quit [*.net *.split]
veleiro has quit [*.net *.split]
pinkieval has quit [*.net *.split]
steveeJ has quit [*.net *.split]
Cadey has quit [*.net *.split]
qyliss has quit [*.net *.split]
cirno-999 has quit [*.net *.split]
cptchaos83 has quit [*.net *.split]
marek has quit [*.net *.split]
mschwaig has quit [*.net *.split]
monk has quit [*.net *.split]
Adluc has quit [*.net *.split]
dustinm has quit [*.net *.split]
bennofs__ has quit [*.net *.split]
bigvalen has quit [*.net *.split]
zhaofeng has quit [*.net *.split]
ekleog has quit [*.net *.split]
bdju_ has quit [*.net *.split]
adisbladis has quit [*.net *.split]
aleph- has quit [*.net *.split]
davidtwco has quit [*.net *.split]
quinn has quit [*.net *.split]
figgyc has quit [*.net *.split]
heywoodlh has quit [*.net *.split]
wrmilling has quit [*.net *.split]
samueldr has quit [*.net *.split]
luigy has quit [*.net *.split]
globin_ has quit [Ping timeout: 245 seconds]
misuzu has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
cwfefifofum[m] has joined #nixos-aarch64
craige has joined #nixos-aarch64
hyperfekt has joined #nixos-aarch64
lopsided98_ has joined #nixos-aarch64
noonien has joined #nixos-aarch64
jasom has joined #nixos-aarch64
wirew0rm2 has joined #nixos-aarch64
clever has joined #nixos-aarch64
blackriversoftwa has joined #nixos-aarch64
NekomimiScience has joined #nixos-aarch64
flokli has joined #nixos-aarch64
Mirrexagon has joined #nixos-aarch64
bpye has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
qyliss has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<matthewcroughan>
misuzu: play around with kernel versions
<matthewcroughan>
Some drivers are provided by uboot whereas others are provided via the kernel.
<matthewcroughan>
Sometimes neither has the driver, because it has not been upstreamed.
<matthewcroughan>
Eventually, things make their way into the kernel.
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
<misuzu>
matthewcroughan: networking.wireless.enable = true; did the trick
<matthewcroughan>
Ah so you could have seen the interface with `ifconfig -a`
<matthewcroughan>
You said the interface didn't exist, but it did.
<misuzu>
matthewcroughan: there was no wlan0 in `ifconfig -a`
<matthewcroughan>
Huh.
zupo_ has quit [Client Quit]
<matthewcroughan>
I don't understand this :D
<misuzu>
me too :D
Acou_Bass has joined #nixos-aarch64
superherointj has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 240 seconds]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
superherointj has quit [Quit: Leaving]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr>
I knew I had it somewhere, couldn't figure out the branch name I used
<samueldr>
so I uh... re-did it all yesterday evening
<misuzu>
:D
<veleiro>
how does the nixos images for the pi family work with /boot/config.txt? as far as i can tell, there's no config.txt in /boot, but its mounted within /run/media/user/FIRMWARE. changing boot.loader.raspberryPi.firmwareConfig in nixos config wont change anything there though. how does it boot the config.txt
<samueldr>
veleiro: there's no universal answer
<samueldr>
for the raspberry pi family of hardware, there are two paths you can go
<samueldr>
(1) generic SBC support, where the boot firmware is an opaque blob not managed by NixOS
<samueldr>
(2) vendor-specific raspberry pi "support" in NixOS
<samueldr>
what you described with the FIRMWARE partition is (1), where we use the boot chain from the vendor to boot U-Boot
<samueldr>
(1) is, in my opinion, preferrable if you don't need to interact with the "pi ecosystem of hardware"
<samueldr>
but with (1) managing config.txt is left out of band of NixOS system management
<samueldr>
basically, with (1) think of config.txt as if it was a menu in your BIOS, where you change settings
<samueldr>
does that help veleiro?
<samueldr>
I don't have much experience with (2), it exists, but I don't like that we're doing vendor-specific things
<veleiro>
oh yes
<veleiro>
so the mounted FIRMWARE partition is where i'd make changes instead?
<samueldr>
yes
<veleiro>
awesome, this makes sense
<veleiro>
i appreciate you explaining those options to me. cheers
<samueldr>
here FIRMWARE is "your BIOS" in many ways with the raspberry pi
<veleiro>
good way to put it because you're treating the nonfree blob stuff in that ecosystem as a different interface to the device, completely separate from nixos
<samueldr>
not strictly the "nonfree blob"
<samueldr>
but more of a "platform specific detail"
<samueldr>
this way we don't care about how it boots, as long as it's extlinux.conf compatible
<{^_^}>
#121226 (by zhaofengli, 1 day ago, merged): phosh: init at 0.10.2
<veleiro>
amazing
<veleiro>
the UEFI booting and phosh merge i mean
<samueldr>
yeah, saw that
<samueldr>
now waiting on the phosh example system on mobile nixos ;)
<davidak[m]>
yes, a demo with phosh would be great
<veleiro>
i'm not a fan of touch interfaces to emulate android/ios however, cant stand what they've done to the computer
<davidak[m]>
veleiro: do you know a better way of doing it? it seem to work for most people
<veleiro>
a keyboard is my preferred method
<davidak[m]>
on a smartphone? you can connect a usb keyboard, but the UI is not optimised for that
<veleiro>
i know, everything is built around touch
<veleiro>
we're cool enough not to have to be like the corporations with their interfaces, there was nothing wrong with small tangible keyboards
<samueldr>
phosh is not forced onto anyone
<samueldr>
I rather we have varied explorations of interfaces than a myopic single-minded one
<veleiro>
yep
<veleiro>
its good i said
<veleiro>
i'll be trying for wayland-something keyboard focused as my mobile driver, to be determined with more research
<davidak[m]>
veleiro: great if you found a workflow that works for you. just to provide a perspective to the topic: i see people like CLI and argue it's more efficient. i was thinking about the thesis that GUI is actually more efficient for most people since it's easier to click a button than knowing which arguments you have to type, needing reading the manual. i was even considering the idea, when people argue that clicking
<davidak[m]>
i don't have a final opinion on this and don't want to start a discussion now
<davidak[m]>
with the mouse is not efficient, maybe a touch screen on pc/notebook would be faster and more intuitive? there seem to be a trend that casual computer users seem to prefer smartphone/tablets over PCs... that seem what you criticize, but maybe we can learn from that when our goal is to create tools that are accessible to most people, not just toys for nerds
<samueldr>
I assume it's all a total workflow thing, and not a single task
<samueldr>
I assume people seem to gravitate to CLIs not because of the single CLI use being more efficient, but because they can be composed or scripted, while GUIs (on most OS) seldom can
<samueldr>
so that brings some familiarity
<samueldr>
might also be because CLIs are mostly "one dimensional"
<samueldr>
not sure how to better describe that dimensionality feeling
<davidak[m]>
the workflow of unix style cli tools in combination with pipes and scripting is very powerful, but not what most computer users are comfortable using.
<samueldr>
I also think the familiarity one gains by chaining, scripting and composing with CLI tools colours their judgement
<veleiro>
GUIs have already run into the problem of the same amount of bloat added to their interfaces, requiring a manual of operation. look at your CAD tools, any professional graphics tools. the difference is the GUI captured the publics' expectations at the right time, and its only seen exponential growth and adoption by users since then
<veleiro>
there was a time before the gui and before a standardized gui, decades of normal users using terminals for work, play etc
<davidak[m]>
i would like to argue that good GUI can be more intuitive, efficient and the users have a better experience than CLI. that does not mean that most GUI programs are like that, especially in the free software world. i need to do more research before making this argument comfortably.
<samueldr>
those discussions often end up comparing the worse to the best, rather than thinking on level terms :(
<samueldr>
the worst to*
<samueldr>
both "CLIs" and GUIs can be terrible
<samueldr>
both "CLIs" and GUIs can be good
<davidak[m]>
sure
<samueldr>
and then there's the "CLIs" I scare-quoted since some people think of TUIs as CLIs
<samueldr>
(e.g. cfdisk, cmus, ranger, even vim, emacs, they are not CLIs)
<davidak[m]>
i try to form an opinion on how we (as free software community) can make computing accessible to more people. should we really suggest to learn to use the CLI or should we create software where that is not needed for most tasks. i tend to latter
andi- has joined #nixos-aarch64
<samueldr>
personally, it depends what "make computing accessible" is as a goal
<samueldr>
and "CLI" to me shouldn't be limited to the VT100 rut we're stuck with!
<samueldr>
think about "fancy" CLIs like the browser inspector, or "maths" software
<samueldr>
in many ways, chat bots are bad CLIs
<samueldr>
(this is getting way off-topic for aarch64 :))
<samueldr>
what can be done to better marry "imperative" interfaces to user-friendliness?
<davidak[m]>
yeah, thank you
<samueldr>
I'm sure a good answer is somewhat in-between GUIs and CLIs
<samueldr>
why can't a "command" (not necessarily running an executable!) be met with an in-line choice to tap/click/select ?
<samueldr>
and thinking in "imperative interfaces" like those, where you ask/demand things, can end up making spoken interfaces work better too
<samueldr>
so CLIs vs. GUIs is probably a big false dichotomy
<qyliss>
Emacs is a bit of both
<samueldr>
yep
<samueldr>
vim in many ways dips in both categories
<samueldr>
if you want a CLI text editor, you need to use the standard text editor
<qyliss>
Ed, man! !man ed
<davidak[m]>
how to you mean that?
<samueldr>
?
<davidak[m]>
>standard text editor
<samueldr>
haha
<samueldr>
ed is "the standard text editor" according to an old meme
<samueldr>
and "?" is what ed responds on wrong commands
<samueldr>
so my "?" was mistimed by your question :) was supposed to be for qyliss' reaction
<davidak[m]>
ok, i don't know these memes
<qyliss>
understandable lol they're from the early 90s
<samueldr>
I was going to explain it once someone bit :)
<samueldr>
so yeah, the point is that CLI vs. GUI is a false dichotomy, and thinking solely on those terms is probably poison for the mind
<samueldr>
where can we harness an "explorative" interface, and where can we harness an "imperative" interface
<samueldr>
and even then, not sure "explorative" is a good term
<davidak[m]>
maybe intuitive? when i try to solve a problem and find a program that says it can do that or is recommended to me, i just want to be able to use it, without reading the manual! there are cases where this is done to the extreme with "one click optimization" tools, that are very populare by novice users, but you have no control over what the program does. i guess interface design is a hard task. Human Interface
<davidak[m]>
Guidelines (HIG) like GNOME, elementary and Apple have them can help to create a complete experience where for example all programs have the same keyboard shortcuts for the same task
<samueldr>
I think having an HIG and making apps intuitive is orthogonal to the main "quality" assigned to GUIs
<samueldr>
I think GUIs mostly are thought as laying their *everything* bare, visible for all
<samueldr>
which can be done despite or in addition of having an HIG :)
<davidak[m]>
HIG helps to have a consistent experience in an ecosystem. the users develop a feeling what to expect, which feels intuitive. you can also learn to use the CLI, but having to read manuals seem more effort than just observing how programs behave
<samueldr>
yes, orthogonal though :)
<samueldr>
HIGs are not an inherent property of GUIs
<davidak[m]>
yes
zupo has joined #nixos-aarch64
<davidak[m]>
"imperative" vs "explorative" seem to be good terms for the topic
<qyliss>
GNU has pretty extensive HIGs (although they don't call them that) for CLIs
<qyliss>
and you can see the difference they make if you give a GNU user a BSD system
<davidak[m]>
i know GNU and BSD style CLI parameters
<qyliss>
(which will have a different, but still consistent experience)
<qyliss>
yeah, I wasn't trying to introduce the concept, but to make the point about how alien it feels to use the one you're not used to
<qyliss>
which surprised me a lot
<davidak[m]>
yeah, good point
<qyliss>
I was using a BSD system the other day, and it wasn't the long vs. short options that tripped me up, it was not being able to put options after positional arguments
<qyliss>
which I'd never even thought about before
<samueldr>
whew
<qyliss>
(like, I academically knew that this was a GNU thing, but it hadn't sunk in)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<davidak[m]>
"intuitive" might mean "what the user is used to" and is kind of arbitrary. working towards (open) standards would be a way to work in that direction. but finding consensus is hard, as we know :D
<qyliss>
yeah
<qyliss>
a floppy disk icon is not innately intuitive, especially to young people
zupo has quit [Ping timeout: 252 seconds]
<samueldr>
intuitiveness is what HIGs are for, and is probably a fine term to use for user expectations among things of a same origin
<davidak[m]>
is there a better term to describe that a programs interface allows a (new) user to finish a task fast, without much effort/cognitive load and having a good experience doing it (have a positive feeling associated with it)
<samueldr>
good? :)
<samueldr>
I don't know that this is a "property" of any concept of interfaces, but more of a quality
sciamp has joined #nixos-aarch64
<davidak[m]>
maybe that can be achieved also with CLI programs. i might be biased, because i'm not good at reading and used a mac for long time (mostly clicking GUIs), so i'm used to that. i'm might not be able to see the perspective of someone who hasn't used a computer before since i use computers for as long as i can think lol
<samueldr>
yep, familiarity is one hell of a thing to get away from
<davidak[m]>
there might be different types of users. those who like to read manuals and then know exactly how it's done and those who like to just try out until the find out themselves
zupo has joined #nixos-aarch64
<davidak[m]>
so we as a community have to provide different options and users have to search for those that work for them
<samueldr>
yes, the most important value in my opinion is the freedom of choice
<samueldr>
being free to do bad choices, good choices, any choice
<samueldr>
more on-topic: #121429 updates U-Boot to 2021.04