<leah2>
i thoguht i can run strings on /dev/mtd? but it's nontrivial
Nixkernal has joined #riscv
MaxGanzII has joined #riscv
valdemaras has quit [Quit: valdemaras]
<leah2>
ok, new firmware boots from nvme ++
valdemaras has joined #riscv
jacklsw has quit [Ping timeout: 255 seconds]
Tenkawa has joined #riscv
<Tenkawa>
Esmil: first round of tests didn't see the nvme drive on boot.. it did start the kernel but no nvme detected.
<Tenkawa>
Nothing obvious showed up as to why though
<Esmil>
Tenkawa: the config option probably changed name with Minda's latest patches
<Tenkawa>
oh?
<Esmil>
i have CONFIG_PCIE_STARFIVE_HOST=m
<Tenkawa>
let me check that
<Tenkawa>
(this is where the multi boot really helps)
<Esmil>
You'll alse need the new clock drivers: CONFIG_CLK_STARFIVE_JH7110_PLL=y CONFIG_CLK_STARFIVE_JH7110_SYS=y CONFIG_CLK_STARFIVE_JH7110_AON=m CONFIG_CLK_STARFIVE_JH7110_STG=m CONFIG_CLK_STARFIVE_JH7110_ISP=m CONFIG_CLK_STARFIVE_JH7110_VOUT=m
<Tenkawa>
ok the first one is set.. let me check those others
<Esmil>
CONFIG_RESET_STARFIVE_JH7110=y
<Esmil>
..and the pcie phy CONFIG_PHY_STARFIVE_JH7110_PCIE=m
<Tenkawa>
all set
<Tenkawa>
it boots fine
<Tenkawa>
just doesn't see the nvme
<Tenkawa>
to mount root
<Tenkawa>
once the initram handoff occurs
<Esmil>
also make sure that those drivers are actually in your initramfs
<Tenkawa>
they are hardcoded into the kernel.. would that matter?
<Esmil>
No, but something in your end prevents them from initializing pci/nvme
<Tenkawa>
yeah I was suspicious pci might the problem
<Esmil>
another thing could be if you didn't load the device tree that was built from the same source
<Tenkawa>
Yeah thats "very" possible
<Tenkawa>
I'm still questioning the load mechanism
<Tenkawa>
let me go try to ensure I have a forced load
<Tenkawa>
dtb
<Tenkawa>
fixed
<Tenkawa>
was copied in the wrong spot
<Tenkawa>
the install routine missed the second path
<Tenkawa>
Linux vf2 6.5.0-rc7-vf2+ #2 SMP Fri Aug 25 21:32:51 EDT 2023 riscv64 GNU/Linux
<Tenkawa>
Timing O_DIRECT disk reads: 1006 MB in 3.00 seconds = 334.78 MB/sec
<Tenkawa>
not bad
<Tenkawa>
No IO errors so far
<Tenkawa>
I'm not even using the updated IO tuning boot params
<Tenkawa>
I took them out as a test
<Esmil>
interesting. i still get the 'nvme0: I/O 640 QID 5 timeout, completion polled' even with v3.4.5
<mwette>
maybe trolling, but do you know about nvme-cli (I found via web search)
<mwette>
^userspace command line interface to nvme
<Tenkawa>
mwette: thats great if you want to change "disk" settings.. not kernel settings
<mwette>
got it
<Tenkawa>
These are settings for how the nvme kernel driver communicates/operates
<mps>
Tenkawa: ok, will add and check
<Tenkawa>
mwette: I used nvme-cli to change blocksize but changed it back after I learned a "unfortunate" side effect
<Tenkawa>
It may slightly help perf but after you get certain sized drives by certain vendors... their part tables are a mess to work wiith
<Tenkawa>
And since none of these socs can support x4 speeds yet.. its not really worth changing the mode
<mps>
I use nvme-cli only as information tool
<Tenkawa>
ooh.. up to 41.8C
<Tenkawa>
lol
<Tenkawa>
I recommend this cooler if anyone needs one (waveshare's VF2 cooler)
<mps>
Tenkawa: with your cmdline params I've got "bootarg overflow 284+0+0+1 > 256" from u-boot
<mps>
have to look at u-boot where to increase this
<Tenkawa>
then you need to go increase your u-boot max string length
<Tenkawa>
yeah
<mps>
Tenkawa: didn't help with your cmdline params
<Tenkawa>
mps: not sure what to tell you then... the only variable really is mainline u-boot from anyone else so far I've seen doing testing here.
<mps>
Tenkawa: did you tested it with mainline u-boot
<Tenkawa>
No
<Tenkawa>
I don't have the source url.. I can try building another drive with it.. problem is soon as I use that u-boot it can't be used on this image without risking this staging so I'll need to replicate the drive
MaxGanzII_ has joined #riscv
MaxGanzII has quit [Remote host closed the connection]
Stat_headcrabed has quit [Quit: Stat_headcrabed]
<Tenkawa>
Well things were going good until apt just scrambled my initrams
<Tenkawa>
I won't be able to fi those until I get home
<Tenkawa>
er fix
BootLayer has quit [Quit: Leaving]
valdemaras has joined #riscv
Nixkernal has joined #riscv
davidlt has quit [Ping timeout: 244 seconds]
Andre_Z has quit [Ping timeout: 246 seconds]
Tenkawa has quit [Quit: Was I really ever here?]
<mps>
Esmil: with your last patches kernel boots very fine from nvme and mainline u-boot - U-Boot 2023.10-rc3-dirty (Aug 26 2023 - 17:40:26 +0000)
<Esmil>
mps: cool. for some reason i still get the 'nvme0: I/O 640 QID 5 timeout, completion polled' errors. even with their latest u-boot release and the 6A powersupply that came with my vf2
<mps>
Esmil: latest fixes for u-boot are few days old and there is one patch not yet applied