Hi Steffen,
> Steffen wrote:
> Mh, I only find "jh7100-starfive-visionfive-v1.dtb" therein. Looks like
> another SoC is mentioned, no "2" for the board and the version also does
> not seem to match - if they are all supposed to match exactly.
root@fluffy:/home/scott/projects/starfive/dtb-package/share# find . | grep -i
starfive
/dtb/riscv/starfive
/dtb/riscv/starfive/jh7110-milkv-mars.dtb
/dtb/riscv/starfive/jh7110-pine64-star64.dtb
/dtb/riscv/starfive/jh7110-deepcomputing-fml13v01.dtb
v-- visionfive v2 rev 1.2A
/dtb/riscv/starfive/jh7110-starfive-visionfive-2-v1.2a.dtb
v-- visionfive v2 rev 1.3B, which I have
/dtb/riscv/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb
/dtb/riscv/starfive/jh7100-beaglev-starlight.dtb
v-- the visionfive v1 dtb you found
/dtb/riscv/starfive/jh7100-starfive-visionfive-v1.dtb
> Have you tried the steps described in
> https://gist.github.com/csgordon/74658096f7838382b40bd64e11f6983e and my
> comment to the post.
One thing different between that and what I've done is that
installs to eMMC. It also drops the dtb in the root directory
of the EFI partition instead of a vendor/ etc directory as
https://ftp.openbsd.org/pub/OpenBSD/7.7/riscv64/INSTALL.riscv64
suggests.
The eMMC interface on this seems to be two rows of contacts that a
board snaps on to. Searching for eMMC storage, I see solder on things
with a very different pinout, or else cards. What keywords are needed
to find the correct type of eMMC storage for these? Or where could you
order one? Because I'm now realizing that without work (as in that
gist and another post in misc) that booting nvme will take some more
work (may mess with that later tho). U-Boot just doesn't know how to
talk it by default.
I was flailing on doing an install at all. I eventually installed to a
second SD card in a USB-SD adapter. Pulling out the install image and
trying to do a network install, the ISP was resetting connections and
it just got stuck with transfes showing stalled "Stalled". That was
after installing to NVMe (I'm not clear why that suddenly started
working other than maybe a bad contact that one attempt at reseating
didn't fix but being handled did? Or did movin the dtb image to the
root of the EFI partition somehow fix that?) and realizing I couldn't
boot it.
> > cpu0: regulator not implemented
> I don't see such a message.
This went away went I finally booted the installed bsd.mp.
The "real" kernel doesn't do that but the installer
kernel does, I'm pretty sure.
Searching for that text, it also comes up in a lot of boot
messages for different devices. I'd spent enough time
thrashing around with dtbs that I just assumed it was a
missing device, but that doesn't seem to be the case.
I'll read the fantastic source later.
> What temperatures do you observe? Is the fan running?
I don't have a fan hooked up.
> # sysctl | grep 'sensors' | grep temp
> hw.sensors.stftemp0.temp0=59.52 degC
> hw.sensors.nvme0.temp0=53.00 degC, O
I was also assuming that the install kernel is the same kernel that
gets installed but that was only a guess and it seems wrong but didn't
check that either. The installer kernel doesn't have that:
# sysctl | grep 'sensors' | grep temp
# sysctl | grep sensors
# sysctl
kern.osrelease=7.7
hw.machine=riscv64
hw.model=rv64imafdc_zba_zbb
hw.product=StarFive VisionFive 2 v1.3B
hw.disknames=sd0:2bc370bf9cdd3878,rd0:cf6ce3c5e24f767e,sd1:b206a06eaa814b03,sd2:e247c56f18424f05
hw.ncpufound=4
machdep.compatible=starfive,visionfive-2-v1.3b
The installed system does:
# sysctl | grep 'sensors' | grep temp
hw.sensors.stftemp0.temp0=55.17 degC
hw.sensors.nvme0.temp0=51.00 degC, OK
This may be a U-Boot thing. Thermal camera was saying 59C
which isn't horrible but isn't good for idling at a proompt and
not doing anything. I may have just been spending enough time
in U-Boot, if U-Boot is to blame, that I made the thing hot.
Or maybe booting over and over was a lot of work. idk.
> > 202409/sd/starfive-jh7110-202409-SD-minimal-desktop-wayland.img.bz2
> Which temperatures do you observe with this DTB?
Bouncing around 45C in that Debian install, booted in to whatever
GUI, idle. (Frequency scaling? Tickless?)
I think this thing runs a bit hot. I'm inclined to glue some
heatsyncs on.
> An answer to that question would be of interest for me as well.
Another question from me...
I tried adding the "load mmc" commands to startup.nsh, but
that doesn't seem to be working or I did something wrong.
Any tips or examples for doing that? It does continue on
to boot OpenBSD automatically, just without any devices
probed.
> Not sure if the DTB is available somewhere else officially.
https://github.com/starfive-tech/ , but
https://marc.info/?l=openbsd-misc&m=169107663830666&w=2 suggests
that getting the correct ones is part of the trick, with changes
causing chaos. That comments on where they're built from.
I'm a bit unclear on this. It seems like they would have to
match the board and be readable by U-Boot and OpenBSD, and
then beyond that I don't know what other considerations there
are.
That post has some strongly worded language about that situation.
So, at this point, what should be expected to work seems to be
working.
The intall docs could cover a lot more of this stuff and seem
to be wrong about automatically loading the dtb "files" from
certain directories but glad someone this up (that gist).
* What kind of eMMC do I need to buy?
* How does one script loading the needed dbd on startup?
* Install docs seem to be broken and could be more helpful
Again, appreciate the reply. It's nice to get a sanity check
after beating my head against this for many hours.
-scott
