<scelestic>
I'm playing around with a rk3399 device (nanopc-t4) using mainline kernel. There wasn't an official dts for the device so I'm using one from the Armbian project. as far as i can see most appears to be working fine i'm just curious about many regulator errors (could not add device link regulator.?? err -2)
xerpi has joined #linux-rockchip
<scelestic>
since it's 1.8v, 3.3v and 5v supplies i wonder if it's something to worry about, I've put up a full dmesg log here https://pastebin.com/zhUx5HdZ
LargePrime has quit [Quit: Leaving]
scelestic has quit [Quit: leaving]
anarsoul has quit [Remote host closed the connection]
scelestic has joined #linux-rockchip
<jmbsvicetto>
scelestic: Hi. Can you share the dts / link to it? I'm trying to install Gentoo on a nanopc-t4
xerpi has quit [Remote host closed the connection]
<scelestic>
jmbsvicetto: sure, even though it mentions nanopi4, rev00 seems to be nanopc t4
scelestic has quit [Remote host closed the connection]
scelestic has joined #linux-rockchip
<Kelsar>
hmm the nvme is not detected...
stdint has quit [Ping timeout: 252 seconds]
stdint has joined #linux-rockchip
LargePrime has joined #linux-rockchip
default__ has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 272 seconds]
ldevulder_ has joined #linux-rockchip
default__ has quit [Ping timeout: 252 seconds]
return0e has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
<jmbsvicetto>
Kelsar: sorry, I was out
<jmbsvicetto>
Kelsar: Yes, I was able to use the upgrade_tool on my laptop to flash through usb-c the nanopc-t4
<jmbsvicetto>
Kelsar: are you sure you got the nanopc-t4 in the correct mode? IIRC, I had to start it pressing the reset and boot buttons for a few seconds
adjtm has joined #linux-rockchip
<Kelsar>
jmbsvicetto: i got it working, right now i can't see the nvme :(
<jmbsvicetto>
Kelsar: What do you mean? I had some initial issues with the nvme but got it working
<jmbsvicetto>
nvme ssd disk*
<Kelsar>
installed the ubuntu image, i can't see the nvme, but it is late so i went to bed ;)
<jmbsvicetto>
Kelsar: The nanopc-t4 is enforcing the same partitioning on nvme that it has on the mmc, so I had to use nvmen1p7 to get a large partition on it
<jmbsvicetto>
Kelsar: hehe
<jmbsvicetto>
BTW, is there any way to convince the kernel that I want to use my own partitioning on the nvme? I'm able to use fdisk and parted to create a different partitioning scheme, but the kernel refuses to accept it
<jmbsvicetto>
Kelsar: sorry, I believe it's nvme0n1p7 - I have to power it up to confirm
<Kelsar>
i don't have any nvme device
<jmbsvicetto>
Were you able to use the screw for the disk? It took me a while to understand the hole had a plastic cover that I had to remove before being able to use the screw
<jmbsvicetto>
Kelsar: It wasn't obvious to me
<Kelsar>
i had to use adapter to make my ssd large enough... so yeah, the screw wasn't an issue
<jmbsvicetto>
ok
<jmbsvicetto>
could it be related to the adapter? I'm using a samsung 970 evo on my nanopc-t4
<Kelsar>
no, it just a nechanical extension to the screw, not the socket side