justan0theruser has quit [Ping timeout: 264 seconds]
h0m1 has joined #nixos-aarch64
monk has left #nixos-aarch64 [#nixos-aarch64]
monk has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 272 seconds]
<noneucat>
zram is wondrous
<noneucat>
on memory constrained systems
* samueldr
still hasn't looked at and tried that
<samueldr>
lol
<samueldr>
and no, there's no need to add it to the defaults for mobile nixos... let the end-user decide... though we might want to provide a profile with good defaults to import?
<Ke>
ie. independent bmc for my honeycomb that would emulate the boot media
<clever>
if i add this code, then all functions of the usb device die
<samueldr>
clever: odd, though I'm not totally understanding how the second parameter (what comes after the dot) affects the function
<samueldr>
pretty much everything you look online has no explanation, only cargo-culting
<clever>
i think thats purely to make it uniq, so you can create multiple of the same type
<samueldr>
like the language string identifier
<clever>
i did find a table for language strings somewhere
<samueldr>
I'm not sure it's purely for identifying
<samueldr>
yeah, microsoft's doc
<clever>
and i found the official usb hid specs
<samueldr>
IIRC the usb spec didn't even cite properly where the identifiers came from
<clever>
i wrote some code for the pi400, to read any input device (the internal usb keyboard) then hid gadget repeat its msgs
cole-h has quit [Quit: Goodbye]
<clever>
> Specifying the full path really does not cost you anything and it guarantees you will get the behaviour you expect, even if the environment is different that you expect.
<{^_^}>
error: syntax error, unexpected ',', expecting ')', at (string):460:115
* clever
cries in nix
cole-h has joined #nixos-aarch64
<samueldr>
NARRATOR: they did not expect that
<clever>
samueldr: the original context was cron having the wrong $PATH by default, and the recommendation was to just always use absolute paths, even when not involving cron!
mvnetbiz_99 has joined #nixos-aarch64
cole-h has quit [Ping timeout: 260 seconds]
__gotcha has joined #nixos-aarch64
<Ke>
does nixos/u-boot somehow support booting compressed images?
<Ke>
on eg. pinephone or pbp
<LinuxHackerman>
I'm not sure we have the structure in place to generate compressed u-boot kernel images
<LinuxHackerman>
initramfs images can be compressed though, and it's become quite flexible on nixpkgs master
<Ke>
sure
<Ke>
Images are bigger still
veleiro has quit [Ping timeout: 264 seconds]
Darkmatter66 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
__gotcha has quit [Ping timeout: 272 seconds]
monk has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
monk has joined #nixos-aarch64
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
justanotheruser has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
<LinuxHackerman>
Any helios64 people here installed u-boot on the SPI flash?
<LinuxHackerman>
if so: how? :D
__gotcha has joined #nixos-aarch64
pinpox has joined #nixos-aarch64
<pinpox>
Anyone running nixos mobile as daily driver yet? I'm thinking about purchasing a pinephone, would be great to use nixos on it but I'm concerned if it will be usable at all
<LinuxHackerman>
It's definitely not suitable for daily driver use.
<LinuxHackerman>
Unless you're willing to stick in all the time to configure some desktop environment to be halfway usable on a phone.
justanotheruser has quit [Ping timeout: 264 seconds]
<LinuxHackerman>
And even then, I don't think there's much in place for configuring the modem, so if you're lucky you can get mobile data, but there's no application stuff in place for making calls etc.
<LinuxHackerman>
You should consider mobile-nixos as "normal nixos, but on a phone". Not "a phone OS".
<Ke>
I would normally compare it to other distros wrt. packaging
<Ke>
people are daily driver using eg. mobian
<pinpox>
I see. hm, I guess I'll have to wait then for a bit or get a secondary phone to play with it. My current samsung galaxy s5 is not supported yet (at least it's not in the devices list)
sorki has joined #nixos-aarch64
srk has quit [Ping timeout: 240 seconds]
sorki is now known as srk
__gotcha has quit [Ping timeout: 264 seconds]
ryantrinkle has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
<andi->
I've been trying to figure out how I can make the heat sink less warmy for a while...
<andi->
It is odd enough that the linked document writes spl to offset 0 in both u-boot & from within linux but writes u-boot to 0x40000 from within u-boot and to 0x1 from within linux.. that smells like an issue in the doc.
<samueldr>
andi-: I think most of the time people end-up underclocking it in the device tree
<samueldr>
but it'd be nice if better power management was understood
<samueldr>
andi-: seek=1 bs=256k <- seek one bs
* gchristensen
'd like to skip way more than just 1 bs
<samueldr>
(256*1024).to_s(16)
<samueldr>
=> "40000"
<gchristensen>
so much bs to skip today
<samueldr>
listen, gchristensen, we're talking about seeking bs
<gchristensen>
oh no
<andi->
samueldr: ohhh, yeah
<andi->
I can never remember if offset or seek is multiplied by bs
__gotcha has joined #nixos-aarch64
<samueldr>
pretty sure all numbers are with dd
<samueldr>
don't forget that ibs and obs can affect input and output independently!
<andi->
oh right, it isn't offset but skip and only applies for input
<andi->
and indeed it is multiplied by bs
Darkmatter66 has joined #nixos-aarch64
sarcasticadmin has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
ky0ko has joined #nixos-aarch64
<makefu>
ahey all, what is the go-to sd image for the raspi4? i tried the latest from hydra but the device is stuck at "mbox: Timeout waiting for response \n bcm2835: Could not set module 3 power state\ninitcall sequence 000000003b3d26c8 failed at call 000000000008409c"
<samueldr>
makefu: 8GB?
<samueldr>
makefu: someone reported that today on the PR adding u-boot too
<samueldr>
mines are early revisions that's for sure
<samueldr>
so I can't test and confirm issues/solutions
<samueldr>
oh
<samueldr>
makefu: is your eeprom updated?
<makefu>
ummmm .... i guess not
<samueldr>
mine hasn't been updated since an arbitrary time in the past
<samueldr>
a possibility is that either a newer update would have made this break, or older version of that firmware breaks
<makefu>
actually i've opened the box of the rpi4 just today after i bought it almost half a year ago
<samueldr>
hmm
<samueldr>
I don't know when they started shipping hw revisions
<samueldr>
I'm not even sure there are trivial ways to know
<makefu>
i will google a bit around to try to find something
<makefu>
i will first try to build some other distro to see if the hardware would work in general. it seems that you can get some info from /proc/cpuinfo about the hardware-revision. but i will report back once i know more
<samueldr>
since they never were highlighted: misuzu ^ about the pi4
<makefu>
oh oh, it seems that its a 4B and not 'vanilla' 4. that may explain some of the shenanigans
<samueldr>
uh
<makefu>
or is 4 == 4B ?
<samueldr>
there's no "vanilla" 4
<samueldr>
yeah
<makefu>
so confusing
<samueldr>
there's the 4B, and the 400 (the keyboard)
<samueldr>
B is the form factor
<makefu>
okay, that makes sense
<samueldr>
the A form factor is smaller, and less popular among pi
<makefu>
the 'old' one was A which had some weird spacing for RJ45 and the A/V connector
<makefu>
in our local hackerspace there is still the RPI1A running with nixos, however i am afraid of ever updating it again (did this 2 years ago)
<makefu>
A without ethernet
<samueldr>
the model A doesn't have ethernet at all AFAIK
<samueldr>
if it has ethernet, it's a model B
<samueldr>
initial model B for the raspberry pi 1 (or all?) had only 2 USB ports
<makefu>
ok got raspbian running via serial after manually editing config.txt and cmdline.txt
<makefu>
cat /proc/cpuinfo: Hardware : BCM2711
<makefu>
Revision : c03111
<makefu>
Serial : 10000000d42b4828
<makefu>
Model : Raspberry Pi 4 Model B Rev 1.1
<samueldr>
AFAIK 1.1 is the first public revision
<samueldr>
so this could be an EEPROM issue
<samueldr>
well, EEPROM firmware
<samueldr>
or uh... naming things is hard, firmware for the raspberry pi, found on the eeprom
<makefu>
ok let me try updating the eeprom first
<makefu>
eeprom updated, boot_uart enabled, lets see what happens with the latest nixos image
<makefu>
same issue unfortunately
<samueldr>
hm, annoyinh
<samueldr>
annoying*
<samueldr>
given I used the same image as you did, and it boots here
<samueldr>
the main difference I can see, outside hw differences, is the eeprom
<samueldr>
really, I would look into maybe first downgrading u-boot as misuzu did to confirm it helps
<samueldr>
and then maybe upgrading to see if it will help once the next stable hits