@N0rbert - thanks for the positive feedback … i took a note of that link, but i prefer to simply put the latest u-boot+sbi onto the next image, so that it can boot from sd card alone using that and i hope the latest firmware mentioned by you fixes those memory detection problems
its quite funny: with the first update of the firmware files my 4gb vf2 detected its memory as 8gb and of course crashed when it tried to use it later - so the problem was the other way around that i had to add an mem=4000k to my cmdline
I rebased the StarFive kernel (latest commit at time of writing) onto upstream Linux 5.15.98: GitHub - MichaIng/linux
Only trivial conflict resolving was required. Find affected commits with:
Most were even just internal commit inconsistencies, respectively when a commit which caused a conflict was later reverted.
When this builds and boots/works fine, next I’ll have a look at your patches. Will also keep rebasing it on upstream (5.15.99 was just released) and merging StarFive commits as they are coming.
If anyone was wondering, this image DOES NOT work when flashed to and booted from the eMMC (whereas StarFive’s “Debian Image 202302” does boot from eMMC).
Flashing this Experimental Debian Sid Image to SD card now. I will report back.
please be aware that it does not work with the latest sbi/u-boot firmware as that changed the expected partition setup - i plan to update it accordingly for it but did not get to it yet
We have a missing green channel when starting an X session, which is resolved by re-applying resolution settings. I was hoping that this gets solved by one of the patches out there.
@MichaIng - sorry i cannot say for sure what those patches are doing and how well they are (not?) working … i was just looking quickly at them and i thought that they maybe are usefull to bring in as well as i know icenowy as a very good and reliable developer from around allwinner socs - maybe just ask icenowy directly?
Okay makes sense, also to assure that those patches/commits apply for the VisionFive 2 the same way they apply for Star64. Same SoC but not same PCB components, of course.
i finally found the time to build a new experimental debian sid image using the same kernel version, boot blocks and partition schema as the starfive 202302 debian image … the kernel was built and the image assembled on my vf2 running a system based on my last image … this new image contains sbi/u-boot in its boot blocks (taken from the 202302 starfive debian image) so that the sd card can boot directly if the dip switches are set to “sd” boot, otherwise (default spi boot) the latest firmware will have to be installed to boot this image properly
the v5.15 kernel used is based on VF2_v2.10.4 of the starfive visionfive2 kernel tree and some patches from the icenowy star64 kernel tree
framebuffer console added (part of the patches mentioned above)
a v5.15 backport of mglru added (multigen lru mm patches, which were merged into v6.1 mainline and improve performance especially in low memory situations)
has some features typical for the images here: btrfs rootfs with zstd compression, zswap with zstd compression, mgrlu enabled by default
please switch the dip switches on the board to “sd”, i.e. upper one (marked rgpio_1) to 0 (marked ON on the dip switch, i.e. default setting) and lower one (marked rgpio_0) to 1 (marked 2 on the dip switch, i.e. oposite to the default setting) to boot directly from the sd card as this image has sbi/u-boot included in its boot blocks (taken from the 202302 starfive debian image)
small erratum: a leftover /debootstrap directory which can be deleted
username/password is as usual linux/changeme
see also the first post of this thread for some more information about this image
Is there a way to tell the kernel I’ve a 8GB version? Setting `mem=8000M’ in the kernel command line appears not to do anything. Still end up with 4GB RAM.
Thanks for the reference. Due to naming differences, the dtc compile line ends up as: dtc -I dts -O dtb -o /boot/dtb-5.15.0-vf2-104+/starfive/jh7110-visionfive-v2.dtb vf2.dts
Then one ends up with 8GB on capable HW. Excellent.
@hexdump0815
Hello dear friends…
I have acer chromebook tab 10 - (gru-scarlet).
I want to convert it to android os.
can any one help me and I will pay for that.
The device originally supported Android by default, so www.acer.com, log a support ticket with Acer. But it is also 5 years old so the very last update would have been sometime in 2023.
You could bang your head against a lot of brick walls and compile your own android OS developer.android.com and applications. Installing it on the device would prove to be the most difficult part of the entire process (trusted boot - Google/Acer decides what OS can run on “your” hardware). And because you compiled your own OS you have the ability to remove or disable the default google spyware, so your device would not be granted access to the “google play store” for applications. You could probably point it to F-Droid for some open source applications. If you are a embedded systems software developer, LineageOS might be a better choice (It will not work by default for most hardware).
Another problem with installing your own custom Android OS would be all the binary blobs for your hardware not existing for a newer Android kernel, so you might loose the ability to use some hardware inside your device (e.g. WiFi, Bluetooth, speakers, microphone, touchscreen, MEMS accelerometers, camera, USB, battery, lcd, …).
You need to find somewhere on the internet where there is a high concentration of knowledge about your particular hardware and the Android OS or one of it’s forks. Here is opposite of where you need to look (On a site about RISC-V you are unlikely to find optimal support for ARM based hardware).
P.S. Kidnapping a preexisting thread that has nothing to do with your problem is seen as bad (it is basic netiquette to make a new thread for an unrelated subject). Re-purposing a thread that has not been posted to in ten months is something that a spam bot would do, it makes information harder to find. If you read the subject “Expermental debian sid image”, would you assume that was anything to help you with your problem.