tilpner_ has joined #nixos-aarch64
sphalerite has quit [Ping timeout: 240 seconds]
tilpner has quit [Ping timeout: 260 seconds]
tilpner_ is now known as tilpner
sphalerite has joined #nixos-aarch64
mvnetbiz_83 has joined #nixos-aarch64
mvnetbiz_8 has quit [Ping timeout: 240 seconds]
mvnetbiz_83 is now known as mvnetbiz_8
vika_nezrimaya has quit [Remote host closed the connection]
mvnetbiz_8 has quit [Quit: Bye!]
mvnetbiz_8 has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
disasm has quit [Ping timeout: 265 seconds]
disasm has joined #nixos-aarch64
vika_nezrimaya has quit [Remote host closed the connection]
vika_nezrimaya has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
vika_nezrimaya has quit [Remote host closed the connection]
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
dustinm- has joined #nixos-aarch64
dustinm has quit [Ping timeout: 265 seconds]
fps has quit [Ping timeout: 265 seconds]
fps has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
knerten1 has joined #nixos-aarch64
knerten2 has quit [Ping timeout: 256 seconds]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Read error: Connection reset by peer]
dongcarl has joined #nixos-aarch64
* samueldr idly thinks
<samueldr> could I use something like squashfs or cromfs ( https://bisqwit.iki.fi/source/cromfs.html ) to make a "system" image which is the base nixos system, and on top of that overlayfs changes into userdata?
<samueldr> I guess the question is: what would be the best way to compress the fs for a phone
<samueldr> but at the same time, thinking just 1 minute more
<samueldr> I realise I should just LVM the partitions instead of playing dumb games
<samueldr> hm, now thinking compression could still be interesting
<samueldr> well, already I see some easy gains in limiting the systemd journal :)
<clever> samueldr: overlayfs would also offer some major recovery options like android
<samueldr> yeah
<clever> samueldr: just wipe the upper layers, and you can factory reset it!
<samueldr> I was thinking about that
<samueldr> but do you really want to manage upgrading the base layer and keeping the nix store... somewhat sane??
<clever> but incremental updates with nix and state kind of ruin things
<samueldr> exactly :)
<clever> what about 2 overlayfs's?
<samueldr> so, if you build a non-nixos with nix, yes, definitely feasible
<clever> hmmm, or just one, but
<clever> one overlayfs, for /nix, to have a compressed base, and a non-compressed incremental, wipe both whenever
<clever> and then a non overlayfs for everything else in / (all state)
<clever> then you can still have incremental changes, but you get better usage if you wipe and do a non-incremental update
<samueldr> yeah, main issue is I assumed `system` would be handled from the outside via e.g. fastboot flash
<samueldr> and system might be too small to do this
<samueldr> BUT, I guess you could have a unique ID on the system partition and wipe the incremental stuff when it differs?
<clever> yeah
<samueldr> though that's likely to break the user's system, no?
<clever> just use the root $out that your putting in the squashfs
<clever> if the user is updating the system partition, they would loose any nix-env profiles in the process
<clever> it would be reset back to just one system generation
veleiro has joined #nixos-aarch64
<samueldr> assuming no nix-env shenanigans into their desktop, it should be fine
<samueldr> but eh, quite concerning
<clever> you could also involve `nix copy --from local?root=` into the process, but it gets ugly
<clever> you would need to copy the closure of ~/.nix-profile before erasing the old system, to a safe dir
<clever> and then copy it back over the overlayfs after the reset
<clever> oh, another thing ive found (while rooting things), /system isnt true read-only
<clever> it tends to just be ext4 mounted ro
<clever> if you gain root, you can just `mount /system -o remount,rw` and do whatever you want
<samueldr> yeah
<samueldr> but you can't anymore
<samueldr> (on android btw for those confused)
<samueldr> if you do so, you'll trip dm-verity possibly
<clever> ah
<clever> my last rooted device was the kindle fire, which i think was armv6
<samueldr> armv7l pretty sure
<clever> its not the HD one
<clever> Processor : ARMv7 Processor rev 10 (v7l)
<clever> ah yeah, it is 7
<clever> Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
<samueldr> I don't think there's been much armv6 android devices
<clever> Hardware : OMAP4 Bowser4 board
<clever> its even dual-core!
<samueldr> oh, looks like I'm wrong, there's been some
<clever> <5>[ 0.000000] Linux version 3.0.8-02825-g9e39b8c (ubuntu@ip-10-166-55-151) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 SMP PREEMPT Sat Aug 3 23:03:37 PDT 2013
<samueldr> haha! we have their IP!
<clever> and damn, is the battery ever good on this bloody thing
<clever> i havent turned it on in months, and it still has 72% charge
<clever> my cellphone can barely go a single day while in standby
<clever> <5>[ 0.000000] Kernel command line: console=ttyO2,115200n8 rootdelay=2 mem=1G init=/init vmalloc=256M vram=32M omapfb.vram=0:20M androidboot.console=ttyO2 androidboot.hardware=bowser
<clever> wait, is that a serial console i see?
<samueldr> most likely
<samueldr> many end-user devices end up shipping with the serial console running
<samueldr> but the ends often hidden
<clever> i couldnt find the serial pads when i was at the last nixcon
<samueldr> they might be totally out of reach
<clever> there are several clear testpoints on the pcb, one of them i think was hard reset
<clever> but i couldnt get the bootloader into the right mode
<samueldr> though be careful!
<samueldr> 1.8V UART!!!
<clever> is that on the other side of the pcb??
<samueldr> you tell me :)
<{^_^}> error: syntax error, unexpected ')', expecting ID or OR_KW or DOLLAR_CURLY or '"', at (string):321:1
<clever> > Here is where the UART pins sits on the back of the motherboard.
<clever> yeah, it says back side, no wonder i couldnt find them
<clever> samueldr: also, that pcb doesnt look like the right one for this model
<samueldr> oh... turns out that the implementation of display suspend and double tap to wake just work on asus-z00t
<clever> my pcb is a very different aspect ratio
<samueldr> so as long as the display is off, touch is off; but a double tap is a wake
<samueldr> hm, could be another one
<samueldr> their naming scheme is terrible
<clever> 1.5" by 6"
<samueldr> 2012, could be the fire hd 7 (1st gen)
<clever> yeah, that sounds right
<clever> single camera
<clever> there are some testpoints labeled in the bottom right, rst, pwr, usb-boot
<samueldr> ah, so they have wiki pages for devices without PRs or working port :/
<clever> the wiki you linked claims 512mb of ram, but the kernel cmdline above claims 1gig
<clever> [clever@amd-nixos:~]$ adb shell busybox free -m
<clever> total used free shared buffers
<clever> Mem: 751 739 12 0 32
<samueldr> you *could* have a kindle fire (non-HD) 2012
<clever> [clever@amd-nixos:~]$ adb shell cat /proc/meminfo
<clever> MemTotal: 769872 kB
<clever> pretty sure its non-hd, one second
<samueldr> it looks like there is a non-HD (only) in 2011, one non-HD for 2012
<samueldr> OEMs: PLEASE NAME YOUR DEVICES IN SANE WAYS
<samueldr> YOU'RE NOT APPLES
<samueldr> AND YES, ASUS, YOU AND YOUR ZENFONE 5
<clever> found it, screen info, 1280x800
<clever> 56.299fps
<samueldr> https://www.gsmarena.com/res.php3?sSearch=zenfone+5 <- in 2014, the zenfone 5 was a 5" zenfone variant... in 2018 they were up to the 5th generation of zenfones!
<clever> lol
<clever> ah, the wifi you linked claims 1024x600, lower res then mine
<clever> wiki*
<clever> i remember the resolution being a bit neat, because it was the exact same resolution as my 14" laptop at the time, but on a 7" display
<clever> so i could vnc into the laptop, and it matched up pixel perfect
* clever checks google images
<samueldr> I'm slowly taking notes for a guide to port mobile nixos
<samueldr> and the first point is
<samueldr> "identify your device"
<samueldr> and currently, you're almost failing :)
<clever> i can definitely confirm, my device matches this photo
<samueldr> so you have an HD 7
<clever> maybe i'm just going senile then? lol
<clever> i did buy it some 8-ish years ago
<samueldr> or that their naming scheme sucks :D
<samueldr> KFTT KFJWI ; those kind of model names are "official" at amazon AFAIUI
<clever> the logic board is absolutely dwarfed by the battery
<clever> the "screen info" app from earlier does call it a KFTT, currently android 4.0.3
<clever> oh, that gives me an idea
<samueldr> so if you had the KF* model name it'd point to a specific model
<clever> make a mobile-nixos helper app, a normal android app
<samueldr> it might be available into system properties
<clever> it will gather info from the device, model#, screen info, dmesg, and other stuff
<clever> and then lookup the model# on a db, to see if its supported or not
<samueldr> the latter part would be harder
<samueldr> but an app to gather data is a good idea
<samueldr> since *anyway* you need to gather that data
<samueldr> it could point to the important nuggets
<samueldr> like the likely manufacturer codename
<samueldr> it might also be able to detect things like A/B and system as root
<clever> amazon crippled the android version, device->about says basically nothing
<clever> i see the amazon version# (7.5.1), serial#, mac addresses, thats it
<clever> [clever@amd-nixos:~]$ adb shell getprop | grep KF
<clever> [ro.product.model]: [KFTT]
<clever> [ro.product.cpu.abi]: [armeabi-v7a]
<clever> [ro.product.board]: [blaze_tablet]
<samueldr> KFTT is it
<clever> [ro.product.name]: [Kindle Fire]
<samueldr> >> Kindle Fire HD 7"
<clever> `getprop` works from a relatively normal android app
<samueldr> yeah
<clever> so you can easile scrape that from the app
<samueldr> it could be relatively trivial to make a basic app that gets enough *structured* information
<samueldr> from then on you have a better starting point
<clever> then dump it all into a pastebin service, and put a link to the right mobile-nixos directions at the top of the pastebin
<samueldr> e.g. here you would know it's `amazon-blaze`, model KFTT
<clever> yep
<clever> you could just shove https://mobile.nixos.com/device/${ro.product.board}/${ro.product.model} into the pastebin, as a starting point
<clever> and then let the http server deal with the rest
<samueldr> having a server-side component could be annoying (and GDPR)
<clever> what if you just named wiki pages after models?
<samueldr> better just dump a timestamped .json / .txt with the data
<samueldr> and possibly get the postmarketOS people on board
<clever> KFTT/amazon-blaze could just be a redirect in the wiki
<samueldr> shared responsibility of the app would mean we get more users and bugfixes I suppose
<samueldr> and after all, a bunch of facts are going to be shared
<clever> yeah
<clever> samueldr: what is this..... https://github.com/aosp/blaze_tablet
<samueldr> looks like a "device tree" for android builds
<samueldr> (Android.mk is a telltale sign)
<clever> but is it this board, or another blaze tablet...
<samueldr> most likely that board with a quick look
<clever> TARGET_BOOTLOADER_BOARD_NAME := blaze_tablet
<samueldr> aosp is just a random username on github
<clever> [clever@amd-nixos:~]$ adb shell su -c wpa_cli -g /dev/socket/wpa_wlan0
<clever> and boom, i can now control the wifi, heh
<clever> [clever@amd-nixos:~]$ adb shell cat /proc/product_name
<clever> Tate PVT
<clever> wut?
<clever> [clever@amd-nixos:~]$ adb shell ls -l /sys/class/net/wlan0
<clever> lrwxrwxrwx root root 2020-08-19 00:44 wlan0 -> ../../devices/platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/net/wlan0
<clever> another thing the app can scrape, the wifi is SDIO based, like the pi's
<clever> lrwxrwxrwx root root 2020-08-19 01:08 mmcblk0p13 -> ../../devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p13
<clever> and storage is just emmc on a 2nd mmc controller
<clever> dang, its just a binary kernel, no .config
<clever> neat
<clever> if you hit the power button 7 times in a row, it reboots
veleiro has quit [Ping timeout: 256 seconds]
<samueldr> clever: Tate PVT might be an ODM codename for ap latform
<samueldr> clever: amazon has kernel source code available on their site
<samueldr> at the very least people say that in fastboot mode, the tablet identifies as tate pvt 08
<clever> reboot [bootloader|recovery|sideload|sideload-auto-reboot]
<clever> bootloader i'm guessing?
<samueldr> most likely, for fastboot
<clever> Bus 004 Device 031: ID 1949:0007 Lab126, Inc. Kindle
<clever> hmmm, that just did a plain reboot
<clever> `adb shell` already works again
<clever> and its going thru the usual boot animation
<samueldr> it might not respond to that trigger
<clever> `adb reboot recovery` gives a recovery screen that doesnt identify over usb, i only have 2 options, reboot or factory reset
rajivr has joined #nixos-aarch64
<clever> i remember it having a bootloader of some kind though, possibly with fire in the name
<samueldr> clever: hit both vol up and vol down at the same time on that recovery screen
<samueldr> it might show more options
<samueldr> but nothing useful
<clever> nada, let me try the other usual keystrokes
<samueldr> I never rememebr
<samueldr> it might be power + volup or power + voldown
<samueldr> that's when you're at that recovery screen, mind
<clever> to google!
<samueldr> good luck finding your way through the generated contents farms :)
<clever> found it on a youtube vid
<clever> [clever@amd-nixos:~/apps/kindle]$ adb shell su -c "reboot bootloader"
<clever> this drops me at "fastboot kindle fire" with no animation and no UI
<clever> Bus 004 Device 036: ID 1949:0007 Lab126, Inc. Tate-PVT-08
<clever> and yep, tate now shows up in usb
<clever> [clever@amd-nixos:~/apps/kindle]$ fastboot -i 0x1949 getvar product
<clever> product: Tate-PVT-08
<samueldr> yep
<samueldr> that's fastboot
<clever> can it do a full read of the emmc? or is it write only?
<clever> i'm guessing its write only, but `fastboot boot` can run a custom stage
<samueldr> ah-ha! found the firmware files!
<samueldr> they were on a partition all that time
* samueldr wonders how to reconcile that with a mobile nixos build :/
<samueldr> a problem for another day
<clever> i think i have enough info to boot a custom kernel now, but without uart, debugging would be tricky
<clever> and if i have a .config, i could bake the initrd into the kernel, to make it even simpler
<samueldr> you might have /proc/console-ramoops
<samueldr> and if you do, might want to find a TWRP build to boot into
<clever> not on the stock kernel
<clever> definitely need to look into custom recovery stuff, but i also want to make a complete image of the emmc before i do too much
<clever> so i can undo things
cole-h has quit [Quit: Goodbye]
bennofs has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
bennofs has joined #nixos-aarch64
bennofs has quit [Client Quit]
bennofs has joined #nixos-aarch64
bennofs has quit [Client Quit]
alp has joined #nixos-aarch64
<sphalerite> samueldr: "out of device" scheme?
<sphalerite> samueldr: I'm deploying my phone with nixops, which might fit that description? And it definitely feels NixOS-like :D
zupo has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
quinn has quit [Quit: ZNC 1.8.1 - https://znc.in]
colemickens_irc has quit [Quit: Connection closed for inactivity]
alp has quit [Ping timeout: 272 seconds]
fooker has quit [Ping timeout: 240 seconds]
fooker has joined #nixos-aarch64
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
noonien has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<bennofs[m]> does anyone here successfully run linux-5.7.15 on raspi 3b+?
<bennofs[m]> the kernel isn't even getting to the earlycon output for me
bennofs has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<bennofs[m]> just wondering if I messed something up in some way or the kernel really is broken (which seems unlikely)?
alp has quit [Remote host closed the connection]
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
bennofs has joined #nixos-aarch64
lordcirth has joined #nixos-aarch64
alp has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bennofs has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
zupo has joined #nixos-aarch64
noonien has quit [Quit: Connection closed for inactivity]
bennofs has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
bennofs has joined #nixos-aarch64
<bennofs[m]> any ideas how I can debug such things? Perhaps I should buy a JTAG adapter...
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite> bennofs[m]: if you have another raspi handy, you can use that as a JTAG adapter :)
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
orivej has quit [Ping timeout: 264 seconds]
<lordcirth> Is anyone using tlp on aarch64? I tried to enable it but it's not supported. But it seems that upstream tlp has an aarch64 build.
<lordcirth> Seems I don't really need it, as networkmanager can also disable wifi powersave, but it's odd
bennofs has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
disasm has quit [Ping timeout: 246 seconds]
disasm has joined #nixos-aarch64
bennofs_ has joined #nixos-aarch64
bennofs has quit [Ping timeout: 256 seconds]
julm has quit [Ping timeout: 256 seconds]
<Thra11> I tried putting this https://nixos.wiki/wiki/Nix_on_ARM in the 2.3.7 nix source directory and building it, but I get, "configure: error: Package requirements (bdw-gc) were not met:
<Thra11> builder for '/nix/store/rwkdkakc0wxj3siw1md43n87zskyllgq-nix-tarball-2.3.7pre7029_d5ecb8d.drv' failed with exit code 1
<Thra11> I had to adjust the file slightly (e.g. s/version/.version/), so maybe it's outdated in some other way too?
<Thra11> Hmmm. Looks like boehmgc isn't in the tarballDeps or the buildDeps, it's in propagatedDeps, which isn't included in nix-tarball's buildInputs
julm has joined #nixos-aarch64
<samueldr> sphalerite: I guess the main difference is that (1) it assumes you won't be able to nixos inside the device and (2) you might not even be able to use nix (for those older kernels)
<Thra11> I'm not sure if I should update the wiki, or whether I'll just end up breaking it for people using it with more 'stable' versions of nix
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alp has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
quinn has joined #nixos-aarch64
noonien has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
veleiro has quit [Client Quit]
veleiro has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 240 seconds]
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-aarch64
lordcirth_ has joined #nixos-aarch64
lordcirth has quit [Ping timeout: 244 seconds]
cole-h has quit [Quit: Goodbye]
<DigitalKiwi> bennofs[m]: i had to use the old kernel
<DigitalKiwi> bennofs[m]: i wasted many hours trying not to, if you figure it out let me know