Fair point, hadn't thought of that!

I have a lot to learn about the RISC-V ISA still. ^^' But I have a feeling it will become relevant in the future.

Iunno if I will get a response here, but it's worth a shot.

https://github.com/starfive-tech/linux/issues/135

There is a forum on rvspace, so I will try this after a few days too. That said, I can at least narrow it down to my kernel being the issue, which makes finding the issue at least a little bit easier. And, i am off to order that UART cable now. xD Before I totally forget to do it...

Why wouldn't it be?

asmJIT seems to do exactly that for a few ISAs o.o

https://github.com/asmjit/asmjit

For now, at least. Google *is* working on RISC-V in Android.

So once that lands, there is a bit of an attack vector, thus I wouldn't be surprised about malware in the future.

But untill then? Smooth sailing =)

I mean... uh... why not? XD

https://github.com/riscv-software-src/riscv-angel

I too had thought of using RISC-V as an alternative to WebAssembly... because why tf not. o.o Would be funny to see that in action though; but things like networking, device access and the likes would probably be quite hard. Oh well, fun thought regardless.

... I think, I found out why my kernel wouldn't boot. XD

There are a few modules that need to be marked, as they are experimental (as in, not in upstream yet). Timers and two other things, methinks. So of course, if I don't check them, I can't use them! Thus, the board can't boot. xD

Owell... this'll take a while. Hopefuly the kernel can do incremental compiles, because waiting for a full rebuild would kinda suck -v-

https://void.cat/d/LWxd4K4tN9LEE28YEGdMv.webp

forking around with bootloaders do be feeling like this, yes. Thanks, youtube.

#tunestr https://www.youtube.com/watch?v=e8gDxNxb2aw

Without a uart cable, I won't be able to figure it out... But at this point, the only thing that seems to work is to reset the extlinux config. Chances are, that my kernel is misconfigured, which would be very weird o.o

Oh well - at least I know where the problem is, all in that spectacular partition 3. xD Bah. -.-

That moment when you accidentially slip your microSD through a slightly unaligned case and it falls inside and you have to unscrew it to get it out... fuuuuuuuuuck :|

So I went to youtube to listen to vids meanwhile, just got done with WAN Show and whadya know - #Venjent is at it again :D

#tunestr https://www.youtube.com/watch?v=iCphn3iA0tA

(If nostr creator stuff works out, heck, might try to pill the dude for the lulz.)

I doctor'd around on my boot partitions so much... And, it boots!

My knowledge of GPT (the partition scheme) and boot process really saved me right then and there. But also, this is fucking amazing. I CAN do that. I CAN build my own kernel, slap my settings on it, change the boot stuff and be good. Yes, I had to tinker with the settings and now I have to learn more about u-boot and extlinux, but the fact that this works is AMAZING. <3

ARM can do most of that too - somewhat, sometimes, by chance.

I found what MIGHT have caused my issues.

... Debian, in it's infinite wisdom, while updating my extlinux/uboot config, FORGOT HALF THE KERNEL CMDLINE!!!

Oh. My. God. No WONDER stuff didn't work!

Here is the cmdline that VF2's "default" image takes: root=/dev/mmcblk1p4 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0 single

There is also a mention of dtbs too.

I am so, so annoyed. XD This explains so much. Aaaaaaaargh, I will fix this later. >.< Rebuilding my microSD right now.

VisionFive2

Grabbed the longest usb, ethernet and power cables. i cant be bothered to always get up to fumble the microSD into the visionfive2 xD

I want a desk...

Noice :D

Will check it out, once I fix my boot. ^^

After just literally falling asleep (laid down, tried to listen to LTT WAN Show and /IMMEDIATELY/ passed out), I am looking at my boot problem again. Apparently, I need to fit a .flt image into the boot partition now - and it's *big.*

The great thing is, I can "think" in the EFI way; most of the boot process is right on my microSD card and it behaves much like an EFI boot; just... smaller. OpenSBI (/dev/mmcblk0p1) -> u-boot (/dev/mmcblk0p2) -> u-boot uEnv + extlinux config + kernel + vmlinz (/dev/mmcblk0p3) -> OS (/dev/mmcblk04)

It's neat. ^^

Honestly, just having *a device* I can break and brick and still totally repair because it's literally built in, is soooooooo much fun.

So much to learn, too!

Yep... I now know why this DiskStation 413j was sold at the flea market for 10 € xD

I need to buy a new UART cable.

So, installing the new kernel did work - but i very likely fucked up my initrd's xD And chances are that OpenSBI is giving me useful error messages on the console, but i can't see them, because StarFive2's bootcode shows a splashscreen.

Basically, the bootcode is half of a bios, it passes control to OpenSBI which does the *actual* BIOSing and passes an initialized state to u-boot, which acts as the bootloader for the OS.

Problem is, all the nice and neat output, is on the console, and not on the screen. Aaaaaaaaaaaaaaaaargh X.x

So, shopping I go. I need this thing. Hopefuly I can find a 40pin Pi-Hat that just converts to a nice cable because plugging smol connectors on smoller pins is a biiiiiiit of a problem for me x.x;

This is so slow... x.x How did I even accumulate all that storage?

I need to move everything from Bunker into that vol1.

And that at SATA-II speeds... good thing screen and rsync are a thing, because this is literally going to take days. xD

Faster than IBD tho, lol.

Meanwhile: p a i n .

https://void.cat/d/JbHsQKeCdjiCpkxtVrUtjD.webp