<tuxd3v>
I just run some debug, and discovered that using ubootv2020.07 is OK, but running uboot v2020.10 or uboot v2021.01 I don't have network :S
<tuxd3v>
on Orange PI one plus( H6 )
matthias_bgg has quit [Ping timeout: 276 seconds]
<apritzel>
tuxd3v: was this after reboot?
<tuxd3v>
I tried both, off and then bootup, and also reboot
<apritzel>
tuxd3v: I think there were problems when you boot in Linux, then reboot into U-Boot, with the new PHY programming
<tuxd3v>
the unique one that gave me network was 2020.07
<tuxd3v>
and I believe this was the major issue I was having
<tuxd3v>
I flashed first 2021.01
<tuxd3v>
no network on boot
<tuxd3v>
then I flashed v2020.10, no network on boot
<tuxd3v>
I suspected from the kernel..
<tuxd3v>
But later IgorPec, replied confirming he was able to build 5.10.13
<apritzel>
tuxd3v: and this is only on 5.10.13, but not on 5.10.2? Or on both, and it really depends on U-Boot?
<tuxd3v>
So I shifted my attention to uboot, and started with v2020.07
<apritzel>
and by "having network", you mean it works in the kernel, right?
<tuxd3v>
then flahed the others and was unable to get network, going back to 2020.07 and notwork OK :)
<tuxd3v>
network
<tuxd3v>
yes
<apritzel>
network notwork
<tuxd3v>
:)
<tuxd3v>
err, notwork I mean network :)
<tuxd3v>
apritzel, It really depends on Uboot
<tuxd3v>
:)
<tuxd3v>
uboot v2020.07 is the one OK!
<apritzel>
I think I booted later U-Boot on the Pine H64 a dozen of times, can't remember any network issues
<tuxd3v>
I tried even with kernels 5.8.1
<tuxd3v>
what is your uboot version?
<tuxd3v>
ho later one..
<apritzel>
compiling 5.10.13 now ...
<tuxd3v>
maybe it depends on phy-mode = "rgmii-id"; or phy-mode = "rgmii-txid"; for diferent versions of uboot?
<tuxd3v>
2020.07 works OK with phy-mode = "rgmii-id"
<apritzel>
tuxd3v: U-Boot doesn't really make a difference, for a start
<apritzel>
and then U-Boot uses its own DTB, and can only deal with non-rgmii settings since recently
<tuxd3v>
well using uboot 2020.10 or 2021.01 gave me no network in the kernel
<apritzel>
which delayed the DTB sync
<apritzel>
but you load the DTB built from the kernel repos, right?
<tuxd3v>
I load the dtb compiled in the kernel process
<smaeul>
this board has the same dual-phy-supply mess as the Orange Pi 3, right? so I'm guessing you patched ATF in your 2020.07 image to not turn on the regulator during boot, and missed the patch for newer builds
<smaeul>
or alternatively, the device tree was updated in U-Boot, and now the regulator is referenced, whereas it wasn't before
<tuxd3v>
yeah its the same mess as with orangepi 3
<apritzel>
ah, that one ...
<tuxd3v>
smaeul, it could be indeed
<tuxd3v>
the last time I updated this board was some 6 months ago
chewitt_ is now known as chewitt
Mangy_Dog has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
apritzel has quit [Ping timeout: 265 seconds]
victhor has quit [Ping timeout: 276 seconds]
ganbold has joined #linux-sunxi
gaston1980 has quit [Quit: Konversation terminated!]
JohnDoe_71Rus has joined #linux-sunxi
<ullbeking>
what is the cheapest SBC that has a real SATA interface? (I want to get proper IO speeds to 100-400 GB SSD's per SBC). 1GbE wired ethernet (pref. 2), wireless, and a SOC that won't fall over...
<ullbeking>
i'm looking for the cheapest SBC-based hyperconverged storage cluster
<ullbeking>
in my research, often a regular mitx board is far better value than an SBC
<ullbeking>
so i want to see if there's any practical use for an SBC to build something really useful (hyperconverged cluster in my case)
<ullbeking>
i had this conversation with folks here before where the focus was on the application. here i want to explore the range of SBC's.
<ullbeking>
they all seem v. expensive when you start to actually, you know, *do* things with them
ChriChri_ has joined #linux-sunxi
ChriChri has quit [Ping timeout: 240 seconds]
ChriChri_ is now known as ChriChri
<[TheBug]>
None will have it built in, best options will be rk3399 board with an m.2-> pcie x4 adapter (or similar, rockpro64 has an pcie x4 port built on and is only one I know t hat doesn't need adapter board to put card) or a RPi4 CM4 SoM w/ Carrier board
<[TheBug]>
with your own sata card
<[TheBug]>
if a lower amount of sata devices, then there are m.2 to 5 port sata controllers you can get if you wants to use an option which require m.2 without an pcie adapter
<smaeul>
or nanopi m4 with sata hat
<[TheBug]>
As per built on SATA interfaces there are only a few devices with "real" sata, A10, A20, i.MX6, ESPRESSOBin
<[TheBug]>
nanopi m4 is rk3399
<[TheBug]>
and you would probably at this point want nanopi m4v2
<[TheBug]>
with lpddr4
<[TheBug]>
ullbeking: actually only one really that has the ports built on and matches what you are asking for is the Helios64 which is rk3399 but the way the board is manufactured it has 4 sata ports built on
<[TheBug]>
There is also Helio4 which is basically a 4 port ESPRESSOBin but your not gonna get the performance you asked for from it
<[TheBug]>
nor pretty much any of the other mentioned boards with SATA built on other than Helios64
<smaeul>
helios64 also has 2 1+GbE NICs
<smaeul>
unfortunately it's unobtanium
<[TheBug]>
yep
<[TheBug]>
why I would suggest
<[TheBug]>
RockPi 4c
<[TheBug]>
w/ m.2 extender board + m.2 to pice x4 extender they offer + 16-64GB emmc + SATA card + USB 3.0 nic if you need a second nic
<[TheBug]>
currently using similar in 3x NAS deployments and its a treat
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 246 seconds]
fl_0 has quit [Ping timeout: 276 seconds]
macc24 has quit [Ping timeout: 276 seconds]
fl_0 has joined #linux-sunxi
macc24 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 240 seconds]
_whitelogger has joined #linux-sunxi
Jayx276 has joined #linux-sunxi
<Jayx276>
Could anyone advice me on how to port the ethernet on sun8i bananapizero to mainline please ?
<Jayx276>
I arrive at a segmentation fault at module load, fast Ret syscall
hlauer has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
Jayx276 has quit [Remote host closed the connection]
asdf28 has joined #linux-sunxi
Jayx276 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
netlynx has joined #linux-sunxi
cmeerw has joined #linux-sunxi
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 258 seconds]
niceplace has joined #linux-sunxi
warpme_ has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
apritzel has joined #linux-sunxi
Net147 has quit [Quit: Quit]
Net147 has joined #linux-sunxi
Jayx276 has quit [Remote host closed the connection]
Jayx276 has joined #linux-sunxi
Jayx276 has quit [Ping timeout: 260 seconds]
niceplace has quit [K-Lined]
apritzel has quit [Ping timeout: 276 seconds]
apritzel has joined #linux-sunxi
JohnDoe4 has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 240 seconds]
igraltist has quit [Remote host closed the connection]
igraltist has joined #linux-sunxi
apritzel has quit [Ping timeout: 256 seconds]
BroderTuck has quit [Quit: -]
asdf28 has quit [Ping timeout: 256 seconds]
Mangy_Dog has joined #linux-sunxi
pdp7 has quit [Quit: Connection closed for inactivity]
matthias_bgg has joined #linux-sunxi
matthias_bgg has quit [Remote host closed the connection]
asdf28 has joined #linux-sunxi
macc24 has quit [Ping timeout: 276 seconds]
macc24 has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
andy25225 has quit [Ping timeout: 264 seconds]
andy25225 has joined #linux-sunxi
jstein has joined #linux-sunxi
gediz0x539 has quit [Quit: Leaving]
gaston1980 has joined #linux-sunxi
apritzel has joined #linux-sunxi
asdf28 has quit [Ping timeout: 246 seconds]
bantu has quit [Quit: bantu]
bantu has joined #linux-sunxi
mmarc__ has joined #linux-sunxi
lurchi_ is now known as lurchi__
<mmarc__>
Hi guys! Looking for a modern Linux device tree for CherryPi PC H6, a fresh devboard by Shenzhen LC Technology Co.,Ltd. Do you know of any sources?
<mmarc__>
Practically, it's very similar to OrangePi 3, I was even able to run their Armbian image on CherryPi. It worked, but not entirely, USB clock seems to be broken.
asdf28 has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 272 seconds]
ldevulder has joined #linux-sunxi
<apritzel>
mmarc__: do you have any schematic of it?
<apritzel>
mmarc__: and not working USB is most likely not a USB clock problem (for known SoCs), but more a power issue: some regulator supplying VBUS to the device being still disabled
<mmarc__>
no, as for many others. Best what I have is a 3.10.65 dtb dumped from the stock Android firmware. Would it help?
<mmarc__>
Specifically, the clock problem reads as follows: "ac200 0-0010: Can't obtain the clock: -517"
<apritzel>
mmarc__: maybe, at least it should point to the USB regulator
<apritzel>
mmarc__: that's a red herring, -517 means EPROBEDEFER, which is basically saying the clock driver has not started YET, but will do later
<mmarc__>
yes, exactly. I'm attaching a high-speed USB3 camera to the USB-A 3.0 socket, and it stops frame grabbing shortly after, with only two messages above in dmesg.
<apritzel>
mmarc__: so it initially works? then stops doing so?
<mmarc__>
yes
<apritzel>
could that be a power issues? As in: power supply insufficient to power both the board and the camera?
<mmarc__>
I thought foreign dtb is a problem, as it's coming from OrangePi, which is similar yet quite different
<apritzel>
mmarc__: well, if the device probes, it's most likely not a DT issue
<apritzel>
is the USB-C just for power? (because the H6 only has 2 USB 2.0 ports)
victhor has joined #linux-sunxi
<mmarc__>
yes, it reports itself: "usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd"
<mmarc__>
That could be indeed worth to test. I can plug power cable to a qualcomm charger
<apritzel>
yeah, also try a different cable, if you have one
<mmarc__>
interesting, I'm going to try that, thanks!!
<apritzel>
many cables work to a certain degree, but the voltage drop gets too high at some point, if the current increases due to higher load
<mmarc__>
Yes, I remember that I have encountered sudden reboots on long/cheap cables
<apritzel>
and USB 3.0 is spec'ed to deliver up to 900mA per device, IIRC, so that can add significantly to the equirement
<mmarc__>
Also, I've been trying to get USB-otg work on this board. The gadget & UVC config is up and running, but host attachment is not observed. I've notices OrangePi DT sticks device role to host, could it be the reason?
<mmarc__>
Also, I've been trying to get USB-otg work on this board. The gadget & UVC config is up and running, but host attachment is not observed. I've notices OrangePi DT sticks device role to host, could it be the reason?
<apritzel>
well, yes, it explicitly says host only in this DT
mmarc__ has quit [Remote host closed the connection]
mmarc__ has joined #linux-sunxi
lucascastro has quit [Ping timeout: 264 seconds]
<jernej>
apritzel: is this something to worry about? "WARNING: BL31: cortex_a53: CPU workaround for 1530924 was missing!"
<apritzel>
jernej: not really, it's a rather new erratum. smaeul enabled it recently in TF-A
mmarc__ has quit [Ping timeout: 258 seconds]
<apritzel>
I don't know anyone ever hit in on an A53 (Se
<apritzel>
(speculative AT instruction)
<jernej>
hm... I have troubles to boot H5 tritium board reliably - boot log often stops after the end of SPL, befre TF-A prints anything
<smaeul>
usually for me that means it's looking for FIT at the wrong MMC sector
<smaeul>
but that would never be an intermittent problem
<apritzel>
jernej: so this definitely not related to this erratum
lurchi__ is now known as lurchi_
<jernej>
I suspect too high RAM speed
<apritzel>
jernej: can you enable DEBUG in the SPL FIT loader? I think it then prints what it loads?
<apritzel>
TF-A goes into SRAM, but the rest goes into DRAM, also IIRC the MMC driver uses DRAM itself
<jernej>
apritzel: is enabling CONFIG_SPL_FIT_PRINT enough?
<apritzel>
no clue, haven't looked at that code for a while
mmarc__ has joined #linux-sunxi
gaston1980 has quit [Quit: Konversation terminated!]