<patagonicus>
Ok, so turns out that the 4.14 Hardkernel is worse at rebooting on the HC2 than the upstream 5.something. Mainline reboots, but SATA doesn't work, hardkernel just hangs within the first few seconds.
<patagonicus>
But the Hardkernel ubuntu image can do it, so it's probably something outside the kernel that makes SATA work after a reboot. Sigh.
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
pinkieval has quit [Ping timeout: 240 seconds]
pinkieval has joined #nixos-aarch64
<samueldr>
or a kernel config for their downstream kernel?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
Thra11 has quit [Quit: WeeChat 2.8]
orivej has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
<Thra11>
I'm trying to run aarch32 stuff on an aarch64 machine, but I get this: "/nix/store/cvzil995dqk628n017d02s1zaa6fjh4i-bootstrap-tools/lib/ld-2.30.so: cannot execute binary file". file output: "/nix/store/cvzil995dqk628n017d02s1zaa6fjh4i-bootstrap-tools/lib/ld-2.30.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), statically linked,
<Thra11>
BuildID[sha1]=e5d5384f5a5bdf5b9e080e7d0782882a4cfd7b60, not stripped"
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
<Thra11>
CONFIG_COMPAT=y in kernel config
Thra11 has quit [Ping timeout: 246 seconds]
orivej_ has joined #nixos-aarch64
<samueldr>
does your aarch64 machine support running 32 bit?
<samueldr>
it's not a given
orivej has quit [Ping timeout: 240 seconds]
Thra11 has joined #nixos-aarch64
<gchristensen>
Thra11: 15:52 <samueldr> does your aarch64 machine support running 32 bit?
<gchristensen>
15:52 <samueldr> it's not a given
<samueldr>
oops, hi, it's me, someone who hides joins/parts
orivej_ has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
<Thra11>
samueldr: I *think* it supports running 32 bit. It's a pinebook pro.
orivej_ has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
<samueldr>
right, it should
<samueldr>
tbf, I never tried running a binary, all the times I ran 32 bit on 64 bit was a VM (with virtualization)
<samueldr>
so I don't know if it's expected to work easily
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
iwq has joined #nixos-aarch64
<iwq>
how usable is mobile NixOS? I can't find anything about wireless or phone calls. If it's not listed in ports should I assume it works?
cole-h has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
<samueldr>
to the contrary, it generally doesn't work
<samueldr>
it is still in early stage for some of the device features
<samueldr>
the big lacking features are "all comms" (wifi, mobile data, calls, sms), and useful suspends
<samueldr>
though there are exceptions, like asus-dumo being a mainline device, all that is supported by the mainline kernel works, like wifi and bluetooth
Thra11 has quit [Ping timeout: 240 seconds]
<samueldr>
same for the pinephone, and it is likely tha calls, sms, mobile data would work fine with a little bit if work
<samueldr>
older android devices *may* have working wi-fi depending on whether they use wcnss or not
orivej has quit [Quit: No Ping reply in 180 seconds.]
<samueldr>
I personally think it ends up being better in the end if I try to implement features in lock-step
<samueldr>
right now I'm on a yak shaving expedition to make it easier for me to work on wi-fi on newer qualcomm devices
<samueldr>
(which should also make it easier to work on all comms for all qualcomm devices)
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<Thra11>
iwq: samueldr: I'm curious about mobile nixos too. I don't see much mention of userspace stuff, but I'm not sure if that's because it's not done yet, or because it's relatively straightforward and just works.
FRidh has quit [Quit: Konversation terminated!]
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
<samueldr>
kind of both
<samueldr>
(1) there are no phone-specific environment packaged
<samueldr>
(2) once packaged, it's usual nixpkgs porting work
<samueldr>
I'm starting from the base first, the actual interface running is an implementation detail :)
<samueldr>
what good is an interface without wi-fi, and comms working?
<samueldr>
uh, let me rephrase
<samueldr>
(2) to package, it's the usual nixpkgs porting work*
<Thra11>
Makes sense :)
<Thra11>
What's the story with armv7l mobile devices?
<Thra11>
I'm wondering if they're theoretically supported but not the focus right now, or no intention to support them at all?
t184256 has joined #nixos-aarch64
Asmadeus has quit [Ping timeout: 246 seconds]
Asmadeus has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<Thra11>
w.r.t the 32-bit not working on aarch64, I commented out the line in lib/systems/parse.nix that says they're compatible, so it's using qemu-arm now, which appears to work.
<Thra11>
Don't know if there's a 'proper' way to override the isCompatible assumption.
<clever>
it also depends on both the cpu and kernel
<Thra11>
clever: As far as I know the cpu (RK3399) and the kernel (CONFIG_COMPAT=y) should support it. It just doesn't actually work at the moment.
<clever>
what error when you run a 32bit binary?
<Thra11>
"cannot execute binary file"
<clever>
anything in dmesg?
<Thra11>
no
<clever>
have you tried booting a 32bit kernel?
<Thra11>
No, I haven't
<clever>
how did you read CONFIG_COMPAT=y ?
<patagonicus>
samueldr: re HC2, might be a kernel config, I'll check tomorrow. But I think they just use the defconfig they added for their board and I think the Nix package also uses that. It is a slightly different patch version.