<zeta_0>
samueldr: if your not busy, could you help me out for a bit, i'm having trouble building a nixos img for my raspberry pi 4, it worked last time, so it's strange that it's not working now.
<zeta_0>
samueldr: it's ok, is there someone else that can help me?
<zeta_0>
the only other thing that i did was change NIXPKGS_BRANCH to `master`, which was not on the instructions of the link that i just posted, but in the readme, it said that i need to use the upstream master for raspberry pi 4.
<Jake[m]>
I can try to help, but not sure I know enough.
<Jake[m]>
What exactly is not working right now?
<zeta_0>
Jake[m]: thanks following these instructions: https://gist.github.com/chrisanthropic/2e6d3645f20da8fd4c1f122113f89c06 , ./run.sh is not building the img, also did not uncomment `#DISABLE_ZFS_IN_INSTALLER: "y"` like it says in the instructions, so maybe that's why it's not build, (read previous messages on this channel to get the rest of the context)
<Jake[m]>
Is it giving you an error message?
<zeta_0>
Jake[m]: ./run.sh did not throw any error messages, but it told me to paste something in ~/.profile, to make sure the environment variables are set, so do i need to do that as well?
* colemickens
really wants to test 5.8 + uefi-rpi4, it might be easier to just recommend that soon
<samueldr>
colemickens: the bigger issue is more about the kernel, does mainline support the raspberry pi 4 enough yet?
<samueldr>
then the *other* issue is to test u-boot + whatever kernel, last time I tried I failed, but it might just have been me doing something wrong
<colemickens>
samueldr: yeah, supposedly in 5.8, even without the 3gb limit, that's my understanding
<samueldr>
I can't wait for the moment we can ditch the rpi4-specific image
<colemickens>
actually, I know it does, I've done it, I just didn't have a rootfs for it to finihs booting
<zeta_0>
oh i missed an error message, it must be that typo in the nix code that i had to fix last time: `#DISABLE_ZFS_IN_INSTALLER: "y"`
<colemickens>
(trying to netboot instead of just trying the happy path :P) but I definitely got the nixos kernel boot from eeprom->netboot uefi->netboot pxe kerne. even :)
<colemickens>
(I had pulled the 5.8 commit when I did that)
<zeta_0>
woops, wrong paste: `build-nixos_1 | error: The option `services.sshd.enabled' defined in `/build/config/sd-image.nix' does not exist.
<zeta_0>
`
<zeta_0>
services.sshd.enabled = true;
<zeta_0>
yup it's a typo, `enabled`, the `d` needs to be removed, i need to get a hold of the maintainer to change that, so other people do not run into that same typo.
<Jake[m]>
"zeta_0" (https://matrix.to/#/@freenode_zeta_0:matrix.org): hmm I'm not sure. I don't know a lot about docker. I think what I did to bootstrap is I burned a Ubuntu image onto an SD card which had ssh enabled by default, connected it over Ethernet, and then I installed nix on that and built a nixos image with ssh enabled. Not saying you should do that, just offering an alternative approach because I don't know anything
<Jake[m]>
about docker
<Jake[m]>
Oh nice. Good catch!
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Read error: Connection reset by peer]
<zeta_0>
Jake[m]: setting up docker for this was actually not that bad, i just needed to install docker, docker-compose in home.nix, and also i needed to setup a docker background daemon nix service(which i can't remember off the top of my head), and add `docker` to extraGroups for my user in configuration.nix.
<samueldr>
colemickens: though do note I do fully support the concept of going with a UEFI raspberry pi :)
<samueldr>
colemickens: but we'd need to build the firmware ourselves
<samueldr>
colemickens: and this circles back to making device-specific images, which *that* I don't like
<zeta_0>
Jake[m]: it looks like fixing that typo works, things are still being built, so i'm not sure how long it's going to take.
<colemickens>
samueldr: when you say we'd need to , you just mean ideally? I'm just using the project's released binaries for now because building from source seemed like it was non-trivial.
<samueldr>
in Nixpkgs, need
<colemickens>
but I do see what you mean, there's still an extra step
<samueldr>
in fact when I first got wind of that firmware I tried revamping the OVMF bits in Nixpkgs for that
<colemickens>
fingers crossed for a uefi-capable rpi5?
<samueldr>
colour me surprised if it is
<colemickens>
well, I don't know the terminology, but one with enough ROM? storage to be able to burn a community-built UEFI in?
<samueldr>
yeah, if its on-board SPI flash had the capacity for it, it would be okay
<colemickens>
I mean, apply my learning, I guess one with a (bigger?) SPI?
<samueldr>
but that's cents, if not dozen of cents more cost to the BOM!
<samueldr>
#53064
<zeta_0>
does xmonad work in nixos on a raspberry pi 4? it was throwing build errors last time.
<samueldr>
I really need to re-do the PR in the spirit of what I was trying to achieve, now that I have almost two years additional knowledge to back myself :)
<samueldr>
there's also the (grim) view I hold that they purposefully make their hardware into a half-closed ecosystem
<samueldr>
it's to their advantage if the sd image for an appliance distro only works on raspberry pi hardware
<zeta_0>
samueldr: i saw that you are one of the contributors for mobile nixos: https://github.com/NixOS/mobile-nixos , so nixos can be installed on a smartphone?
<samueldr>
on some, with caveats still, but work in progress
<zeta_0>
samueldr: wow that's cool, i've been using apple's iphone6 for the past 5 years, but i've been wanting to buy a new smartphone and table and put linux on it, so this sounds good, so does nixos work on tablets as well?
<samueldr>
for android-based tablets, they're basically big phones, often without the phone part (3/4/5G modem)
<samueldr>
for other tablet-type hardware it differs
<zeta_0>
samueldr: oh and i forgot to ask, can nixos be installed on smartwatches and amazon's kindle hardware as well?
<samueldr>
the main question to ask is: can you intall anything else than the manufacturer's provided operating systems
<samueldr>
if the answer is no, then it's a flat no
<samueldr>
if the answer is yes, it's a maybe
<samueldr>
amazon's kindle fire tablets (the android-based ones) are locked, though software and hardware bugs allowed for some to be opened
<samueldr>
amazon's e-readers, I have no idea
<samueldr>
smart watches, dependso on the watch
<samueldr>
though all of those also mean that the relevant sources be made available
<samueldr>
generally if there is an alternative ROM (e.g. LineageOS) the chances are it's possible
<samueldr>
in itself, Mobile NixOS is an incremental work of pulling the puzzle pieces together, requiring bespoke development for all devices wouldn't be feasible with the ressources available
<zeta_0>
samueldr: oh that's great, i eventually want to replace all of my devices that have proprietary os's, like apple and mac, to linux, so this mobile nixos looks good.
<zeta_0>
ok, i was able to get the nixos sd img to build for my pi, i'll come back here if i get stuck again, thanks for the help everyone.
zeta_0 has quit [Quit: rcirc on GNU Emacs 26.3]
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
<colemickens>
well, I setup an SD card, did a GPT setup on the eMMC and now it doesn't power on or respond at all. lol
<colemickens>
reset button = unblocked, weird
<samueldr>
if you power it on without an OS, it goes in rockusb mode, which unless you plug it into a computer, looks like the machine responds to nothing
<samueldr>
holding power for a real 15 seconds should ensure it's powered off
<samueldr>
the LEDs are enabled in software only
<samueldr>
(if I had designed the hw, I would have made it so the LEDs default to on, and need to be turned off in software)
<colemickens>
if I disable emmc, it goes amber (aka loads uboot frm the usb I think, but then can't load anything else since emmc is disabled)
<colemickens>
if I re-enabled emmc, it does this
<samueldr>
it can't load u-boot from USB
<samueldr>
it goes SPI, eMMC, SD only
<colemickens>
I know I dd the uboot files to the SD card
<samueldr>
did you clear the eMMC before partitioning with GPT?
<colemickens>
with emmc disabled, it seems to load uboot from the SD card because hte LED goes amber
<samueldr>
I believe you might have broken the built-in u-boot by smushing in a GPT
<samueldr>
the pre-programmed u-boot
<colemickens>
I wanted to though, to make it load from SD
<samueldr>
let me rephrase
<samueldr>
you partially corrupted it
<colemickens>
but I think maybe it has to be actually blank and skipped, which I didn't do
<samueldr>
if you didn't erase it
<samueldr>
since it might still have the valid header, but it jumps to something else
<colemickens>
samueldr: I see
<colemickens>
can I read more about that process?
<colemickens>
(is it based on a header, does it just try to load the chunk in and see whta happens, etc)?
<colemickens>
I keep getting 404 for the itneresting rock-chips.com URLs for some reason.
<samueldr>
the GPT starts at the beginning, but probably doesn't go far enough to erase the location(s) the SoC checks
<samueldr>
colemickens: ipv6?
<samueldr>
(I don't have ipv6 here)
<colemickens>
samueldr: possibly, I do have ipv6.
<colemickens>
and I while I do believe you, re: gpt/uboot headers, I find it surprising. (but of course it aligns with the directions everywhere that say to erase -_-)
<colemickens>
thank you for the extensive work in wip-pinebook-pro and the help here!
<samueldr>
your hostname won't do
<colemickens>
I'm taking suggestions! I'm having a hard time because I feel like I need to name the laptop and phone in tandem.
<colemickens>
screw count, 8/10, my father would be disappointed
<samueldr>
:|
<samueldr>
alreadu??
<samueldr>
already*??
<samueldr>
use a flashlight that you set level with the ground to find screws (and ALL the fluff) on the floor
<samueldr>
hoping it's not carpet
<colemickens>
cheap apartment carpet, so hardly counts, they were easy to find :P
<colemickens>
oddly it seems my Super+arrow controls don't work in sway? almost everything else just works
<samueldr>
updated keyboard firmware?
<colemickens>
oooh right
<samueldr>
read carefully
<samueldr>
though just in case, you do have a usb keyboard or ssh?
<colemickens>
both
<samueldr>
then you're unlikely to stay stuck in a bad place
irminsul has quit [Remote host closed the connection]
veleiro has joined #nixos-aarch64
<colemickens>
oh thats right I was going to bump up your version of it too
* colemickens
has a more functional KB now.
Darkmatter66_ has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 240 seconds]
Darkmatter66 has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 265 seconds]
cole-h has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
<samueldr>
interesting, gru-dru is acer chromebook tab 10, and druwl is the CTL tablet... the former missing from the devices list on chromium.org
<samueldr>
(though shouldn't matter as they are basically the same as dumo)
<samueldr>
and the acer model (seemingly) has the innolux display too
ryantrinkle has quit [Ping timeout: 264 seconds]
<colemickens>
lmao, ran the reset sound script, ran mpv, it started screeching until I rebooted
<colemickens>
oh no, and seems to have started again when I started sway. oh god
<colemickens>
seems like as soon as PA starts, it starts screeching, but only after I ran the reset-audio.rb
<colemickens>
alsamixer -> mute -> no screech. phew.
<samueldr>
I wonder if kernel updates changed some of the names for stuff
<samueldr>
it's a bit annoying how the default state for audio is "broken" unless you know which bits to twiddle or use whatever asound state file your distro cobbled together
<Ke>
I am also having problems in grasping, why this is not something just not provided by device tree and things would just work
<samueldr>
AFAIK it's the normal alsa stuff here, though not sure
<samueldr>
like, AFAIUI it's not an arm or aarch64 or device tree issue
<samueldr>
the same hardware on x86_64 would have the same trouble
<samueldr>
x86_64+acpi I should say, to make sure no pedant start pointing out x86_64 device tree platforms :)
<Ke>
true, but eg. alsaucm normally does not exist there etc.
<Ke>
and on typical hda device things just work with pulseaudio like you would expect
zupo has joined #nixos-aarch64
cole-h has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
veleiro` has joined #nixos-aarch64
<sphalerite>
Ke: my guess is that the "embedded" sound hardware used by a lot of these devices has a lot more knobs to twiddle and isn't "just a PC sound card", but a device that can be used in a lot of specialised use cases which require this twiddling
<sphalerite>
ok no, the applications/uses listed by the manufacturer for the sound chip used by my chromebook is are smartphones and tablets
veleiro has quit [Ping timeout: 264 seconds]
<sphalerite>
though what's connected to what does seem like something that would make sense to keep in the device tree.
<Ke>
yes, I asked about this on alsa channel, and there did not seem to be a stong reason this is not the case
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite>
so… you going to make a patch? :D
zupo has joined #nixos-aarch64
h0m1 has quit [Quit: WeeChat 2.9]
h0m1 has joined #nixos-aarch64
sarcasticadmin has quit [Ping timeout: 240 seconds]
sarcasticadmin has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
sarcasticadmin has quit [Read error: Connection reset by peer]
sarcasticadmin has joined #nixos-aarch64
zupo has quit [Ping timeout: 258 seconds]
disasm has quit [Ping timeout: 258 seconds]
davidtwco has quit [Ping timeout: 264 seconds]
jackdk has quit [Ping timeout: 244 seconds]
claudiii has quit [Ping timeout: 244 seconds]
cstrahan has quit [Ping timeout: 244 seconds]
feepo has quit [Ping timeout: 244 seconds]
chessai has quit [Ping timeout: 244 seconds]
prusnak has quit [Ping timeout: 244 seconds]
taktoa[c] has quit [Read error: Connection reset by peer]
dsal has quit [Read error: Connection reset by peer]
feepo has joined #nixos-aarch64
chessai has joined #nixos-aarch64
cstrahan has joined #nixos-aarch64
dsal has joined #nixos-aarch64
prusnak has joined #nixos-aarch64
claudiii has joined #nixos-aarch64
davidtwco has joined #nixos-aarch64
bdju has quit [Ping timeout: 260 seconds]
disasm has joined #nixos-aarch64
bdju has joined #nixos-aarch64
disasm has quit [Ping timeout: 240 seconds]
disasm has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 240 seconds]
bdju has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 258 seconds]
taktoa[c] has joined #nixos-aarch64
jackdk has joined #nixos-aarch64
veleiro`` has joined #nixos-aarch64
veleiro` has quit [Ping timeout: 258 seconds]
Thra11 has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 246 seconds]