monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
apache8080 has quit [Ping timeout: 245 seconds]
apache8080 has joined #nixos-aarch64
<andoriyu> hmm, overlay applies, module loads, but the device doesn't show up. All hits on google are raspberian specific.
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<andoriyu> i think it's becayse i2c1 and i2c0 aren't in device tree for some reason.
apache8080 has quit [Ping timeout: 245 seconds]
apache8080 has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 276 seconds]
ajs124 has quit [Quit: Bridge terminating on SIGTERM]
ajs124 has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
apache8080 has quit [Ping timeout: 265 seconds]
heywoodlh_ has joined #nixos-aarch64
heywoodlh has quit [Ping timeout: 260 seconds]
<Ke> does someone here know, how would one create protective partition for rockchip boolaoder
<Ke> the problem is that it's before sector 2048
<samueldr> last time I checked it just wasn't possible
<samueldr> oh
<samueldr> uh
* samueldr thinks
<samueldr> allwinner is trivial
<samueldr> then amlogic is *definite* impossible
<samueldr> I think rockchip is
* samueldr checks again
<samueldr> putting it *in* the GPT is not possible though, as it is with allwinner IIRC
<samueldr> what has to be done is to reduce the GPT size
<Ke> 34 sectors for gpt
<Ke> 64 is bootloader
* samueldr is confused
<samueldr> I guess I was mixing this up with another target
<Ke> rockchip i mean
<samueldr> yeah, I was confusing myself
<samueldr> right, so I was looking at it
<samueldr> and I was confused by your assertion about 2048th sector
<samueldr> I'm still confused by it, but not by you
<samueldr> I guess I need to look at the spec
<samueldr> but you *can* make partitions start starting at LBA34
<samueldr> I'm confused though, as cgdisk definitely tries hard to make you use 2048
<samueldr> I had to make one at 2048, *then* it let me do one at 0x34
<samueldr> oops 34(decimal)
<samueldr> or 64, if I choose 64
<samueldr> >> I've managed to recover it using fdisk -c=dos to be able to create partition from sector 63, without troubles.
<samueldr> ang cgpt was able to, too
<samueldr> cgpt add -b 64 -s 2048 -l u-boot -t reserved ./test.disk
<samueldr> in my experience, cgpt is the best tool to actually do what you want with GPT
<samueldr> its main fault, barely, is that it does not create a PMBR by default, which can confuse some software
<samueldr> for allwinner you cannot do this, but there are other tricks https://github.com/samueldr/holey
<samueldr> the main difference is that it does not create a tangible partition
evils has joined #nixos-aarch64
<Ke> hmm for me cgpt refuses
<Ke> also fdisk
<Ke> maybe I'll try cgdisk
<samueldr> note that I tested using a file
<samueldr> maybe they do things differently on a block device?
<Ke> perhaps
<samueldr> cgpt refused how? (what was the error?)
<Ke> I got nadias u-boot booting itself, but it hangd on starting kernel
<Ke> I think it was something like illegal value
<Ke> fdisk was definitely value out of range
<samueldr> odd, I don't see how that's related to cgpt refusing?
<samueldr> ah
<samueldr> sorry
<samueldr> I understand
<samueldr> the two sentences were unrelated
<samueldr> as far as hanging at "starting kernel...", it may be because of that patch that is required for Linux (if it is still required)
<samueldr> though hanging at "starting kernel..." can be a lot of issues
<samueldr> it's basically the last thing u-boot says before booting something
<samueldr> I could look into that... but really for the PBP I don't see any use because I much rather write u-boot to the SPI flash
<samueldr> and AFAIK most RK3399 platforms have an SPI Flash (yay!)
<samueldr> really with the PBP there's not much difference in recovering a bad SPI flash and bad eMMC flash in my experience
<samueldr> the exact thing you need to do differs (short SPI chip vs. disable eMMC), but they both require the same annoying process of dismantling the PBP
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
cole-h has quit [Ping timeout: 245 seconds]
justanotheruser has quit [Ping timeout: 240 seconds]
cript0nauta has quit [Ping timeout: 245 seconds]
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nicoo has quit [Remote host closed the connection]
nicoo has joined #nixos-aarch64
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-aarch64
nicoo has quit [Remote host closed the connection]
nicoo has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
<Ke> btw. sway works on nixos on linux-5.11.2 for me on amdgpu
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
dev_mohe has joined #nixos-aarch64
dev_mohe has quit [Client Quit]
cole-h has joined #nixos-aarch64
_linker_ has joined #nixos-aarch64
cole-h has quit [Ping timeout: 245 seconds]
<Ke> can't make nadia's u-boot boot anything
<Ke> could obviously try extracting it from arch images
<Ke> sway works for me on linux-5.11.2 also on pbp
<ar> u-can't-boot? ;)
<ar> i'll see myself out
<Ke> Yeeaaahh!!
<Ke> nadia's build unexplainably works
<Ke> maybe it's the config that's different or then it's the build env
rajivr has quit [Quit: Connection closed for inactivity]
<adamzivcak> colemickens: I've tried to build it one more time from your repo using flakes. It creates a new generation, but it fails to boot into it. It fails with message ERROR: RD image overlaps OS image. Photo with booting process log: https://imgur.com/a/zVT8JhJ . I found, that you have also experienced this in December 2020. But I am not able to find a solution.
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 276 seconds]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
cript0nauta has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dev_mohe has joined #nixos-aarch64
heywoodlh_ has quit [Quit: ZNC 1.8.2 - https://znc.in]
heywoodlh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
dev_mohe has quit [Quit: dev_mohe]
evils has quit [Ping timeout: 276 seconds]
adamzivcak1 has joined #nixos-aarch64
<colemickens> adamzivcak: the other suggestion I have is to check the version of firmware you have flashed on it.
<colemickens> adamzivcak1: otherwise if you're using my `nixpkgs` and my config, I can't really explain why it wouldn't be working (unless you have a different SKU and its related to that)
adamzivcak has quit [Ping timeout: 260 seconds]
<colemickens> I'll probably bump to 2021-02-16 release that was marked stable soon though.
<adamzivcak1> Oh, that should be the thing. I have 2020-09-03.
<colemickens> also, if you want, you can just drop all of my u-boot stuff and use the regular boring rpi bootloader method and use the rpi4 kernel, there's probably less hoops involved.
jumper149 has joined #nixos-aarch64
adamzivcak1 has left #nixos-aarch64 [#nixos-aarch64]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cole-h has joined #nixos-aarch64
hexa- has quit [Quit: WeeChat 2.9]
hexa- has joined #nixos-aarch64