vika_nezrimaya has quit [Ping timeout: 265 seconds]
Acou_Bass has quit [Ping timeout: 265 seconds]
Acou_Bass has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
Acou_Bass has quit [Ping timeout: 265 seconds]
Acou_Bass has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 265 seconds]
zupo has joined #nixos-aarch64
<cornu>
hey, still trying to boot with efiboot and the aarch64 nixos img. But uboot needs a dtb, which is not in the img. Is there some other img or some way to build the imgage with the device tree in the boot directory?
FRidh has quit [Quit: Konversation terminated!]
tilpner_ is now known as tilpner
vika_nezrimaya has joined #nixos-aarch64
vika_nezrimaya has quit [Ping timeout: 265 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
ryantrinkle has joined #nixos-aarch64
<clever>
samueldr: how large is a typical dtb file?
<samueldr>
>> it will be possible to upgrade existing Pinebooks to Pro-esque versions
<samueldr>
considering device trees are used to do everything to identify the hardware, I wonder how it'll work to identify the older keyboard/touchpad and screns
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ryantrinkle has quit [Ping timeout: 240 seconds]
orivej_ has quit [Ping timeout: 268 seconds]
ryantrinkle has joined #nixos-aarch64
<tilpner>
samueldr: Where is that quote from?
<tilpner>
Oh, uhh, definitely not the URL directly before it
<samueldr>
tilpner definitely from the URL directly before it :)
<samueldr>
though, in reality what you end up doing is removing most of the computer and replacing with another one :)
<tilpner>
Mine's too broken to deserve an upgrade :(
<samueldr>
how come?
<tilpner>
They shipped it with a bad display
<samueldr>
uh... oh...
<samueldr>
that's not great
<tilpner>
And the replacement display has the magnets oriented the wrong way
<samueldr>
the pinebook a64's keyboard is so bad to me that I probably will never end up really using it :(
<tilpner>
Any attempts at peacefully removing the magnets below the touchpad has ended in failure
<tilpner>
But now the case is cracked as well
<samueldr>
oof
<tilpner>
NixOS runs on it, but without zfs, but slowly and without any video decoding capabilities (so no remote desktop)
<tilpner>
The last two points are mostly expected
<samueldr>
yeah
<tilpner>
Is your PBP setup with NixOS yet?
<samueldr>
if the keyboard had been fine (not completely butchered) the pinebook a64 would have been quite acceptable, almost nice
<tilpner>
Yeah, that too, it's not the greatest
<simpson>
Oh! Is "PBP" maybe a PandaBoard of some sort?
<samueldr>
not started yet, tried u-boot mainline, had issues, out of my reach
<samueldr>
pinebook pro
<samueldr>
RK3399 based laptop
<simpson>
Aha, rad.
<tilpner>
Though TBF my main laptop has a broken keyboard too, so it's not that much of downgrade
thequux[m] has joined #nixos-aarch64
<samueldr>
:)
<samueldr>
and then I lacked time to continue
<samueldr>
I really want to not rely on any bits from the EXTREMELY SPOOKY default software
<samueldr>
I hate being so cynical and negative about it
<samueldr>
but it's amateur hour
<tilpner>
Nah, it's deserved
<samueldr>
it paints the pinebook pro project in a bad light to let mrfixit do the software
<tilpner>
samueldr: Did you tell tllim?
<thequux[m]>
haha, I just dropped in here to ask about whether anybody had gotten nixos running on the Pinebook Pro
<samueldr>
no
<samueldr>
hi!
<samueldr>
I think Thra11 has tried more than I did
<tilpner>
thequux[m]: I approve of your naming strategies
<samueldr>
though I've been busy with work and couldn't do much more than *try* and get u-boot mainline working :)
<thequux[m]>
I have an interest in working on it, but I probably won't have much time over the next week.
<samueldr>
I think u-boot mainline is extremely close to work (without gfx init), and likely still close to work with gfx init
<samueldr>
and anarsoul is going to work on that, and he did receive the PBP recently
<thequux[m]>
Though it seems that having an aarch64 build machine is pretty important
<samueldr>
it will help
<tilpner>
You *can* use qemu
<tilpner>
It's just going to be slow
<samueldr>
you probably shouldn't use qemu
<samueldr>
though I'll look in ensuring one can bootstrap oneself's with true cross-compilation
<tilpner>
I used qemu for installing NixOS on the pinebook
<tilpner>
But I mixed cross-compilation with qemu-native-compilation
<samueldr>
it'll require a rebuild on-device of the bits not in the cache (most likely kernel)
<thequux[m]>
What do I need to do to get access to the community builder?
<samueldr>
recognition, mostly, and then ask
<tilpner>
Cross compile everything that allows it, qemu-native compile the rest
zupo has joined #nixos-aarch64
<samueldr>
tilpner: a full sd_image can be cross-compiled by fiddling with 4 (or is it 3 yet?) options
<samueldr>
tilpner: so it's possible to bootstrap oneself from a trusted environment :)
<samueldr>
and I figure it was possible earlier than this summer
<tilpner>
I trust-ish qemu
<samueldr>
yeah, that was compared to the aarch64 community builder
<samueldr>
qemu is trusted, but might be fiddly or tarnish builds in unexpected ways
<samueldr>
especially for armv6
<samueldr>
(though I think it got better since last time I tried)
<tilpner>
Hmm, neat!
FRidh has quit [Quit: Konversation terminated!]
<samueldr>
something else about the PBP I need to investigate
<samueldr>
can the mainline u-boot be flashed to SPI?
<samueldr>
if so, then everything will be amazing
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 276 seconds]
ris has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 265 seconds]
Thra11 has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 276 seconds]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Thra11>
samueldr thequux[m] : Just tried a NixOS image built using the tsys's Manjaro sources (5.4.0-rc6 + 4 commits). It boots, backlight + display work. Keyboard input doesn't seem to work at the moment. Still using old u-boot
<samueldr>
great, weird that the keyboard doesn't
<samueldr>
I thought it was only usb
<samueldr>
(when USB broke on 4.4 for some godawful type-c reasons, I was left without the keyboard working)
<Thra11>
samueldr: Yeah. Very weird. I can't see any sign of a keyboard enumerating in the boot logs, only the hubs.
<thequux[m]>
FYI, the rock64 u-boot seemed to work for me, but it couldn't boot because the standard image was missing a DTB for the pinebook pro
<thequux[m]>
Do you have a link for the config you used?
<samueldr>
for me, mainline u-boot was failing in weird ways, like really weird, so couldn't say