hexdump0815
misc: report a not properly booting image
in case an image does not properly boot on your device, please add a comment here. beforehand plase make sure you read the readme.md for that system - some images need extra customization for one of the supported devices by the image in order to boot properly.
I can't make this boot on the chromebook minnie, i't only beeps (another bootable usb works).
I made a a bootable USB with dd on linux.
I read the specific instructions and I should copy u-boot from partition 3 to partition 1?
From gparted i have 4 partitions on the USB-drive.
I can find a U-boot on /dev/sdb3, should I put that on /dev/sdb1 ?
I can't mount sdb1, how to put it there?
Greetings, the extra uboot options are on partition 3 in a folder called extra. In my case I used something like the below to copy the uboot that worked for my to the partition 1 of my sdcard:
mkdir /tmp/p3 mount /dev/mmcblk1p3 /tmp/p3
Now copy the image you want to try to the partition 1
dd if=/tmp/p3/extra/uboot.kpart.cbr-minnie of=/dev/mmcblk1p1
I have veyron_mighty chromebooks but I used the minnie uboot to make mine boot. And I could only get sdcard to work on my chromebooks, not usb sticks. Hope this helps.
@RagnarLodbrok79 - i'm happy to hear that it works in the end for you now - thanks to @unixabg for the quick help.
Thank you for this project!
I do have a boot issue on Asus Chromebit RK3288 (i.e. veyron-mickey) using the Debian release from 220820-01.
After dd'ing uboot.kpart.cbr-mickey from /boot/extra to /dev/sdc1 and adjusting extlinux.conf, there is console output on the attached display, but it seems to be unable to read extlinux.conf
I mentioned SDC above as I'm using a USB stick because the chromebit has no SD card slot (perhaps only SD is configured for mickey).
I tried using kpart from the other devices including speedy, minnie, and jerry, but none of those produced video output (perhaps they expected a built-in display which chromebit doesn't have)
I'll add another post with the console output:
... Model: Google Mickey Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 Switch to partitions #0, OK mmc0(part 0) is current device MMC Device 1 not found No mmc device at slot 1 Starting USB... Bus usb@ff580000: USB DWC2 Scanning bus usb@ff580000 for devices... 1 USB device(s) found Scanning usb for storage devices...0 storage device(s) found
Device (0): unknown device No ethernet found. ...
The chromebit usb2.0 port currently has an unpowered hub attached. That hub has one USB flash drive, one USB ethernet dongle, and a single USB keyboard-mouse combo dongle attached.
I tried using different USB drives and different USB ethernet dongles, but the result was unchanged.
I have this successfully booting arch linux arm. To do that though, it was necessary to use an older image from 2017. The more recent kernels would not boot successfully (I noticed you built an older 2017 version of u-boot for speedy. Perhaps a 2017 mickey kpart would fix this).
Greetings, @mattschwantes - I have veyron_mighty chromebooks and I had to use the extra/uboot.kpart.cbr-minnie to get them to boot. You might try that or the others in the extra folder. I did still use the mighty dtb and I could not get mine to boot from usb, only sdcard for some reason.
@mattschwantes - thanks for the positive feedback ... it could be that usb support is broken in some of the u-boot binaries (i had to compile different older versions as later ones were broken for some devices) ... maybe the postmarketos guys have fixed this (they fixed some u-boot issues for veyron) - i'll have to try to build a u-boot from their tree and see if it helps ... i think i even have a mickey around somewhere, but it might take some time util i get to it ... you could maybe try to dd the vmlinux.kpart (instead of the u-boot.kpart) from the boot partition (3rd) to the first partition to boot the kernel directly - maybe this works in the meantime as it works without u-boot inbetween
Thanks for your suggestion @unixabg. I tried the files for other veyron devices from the extra folder, but unfortunately those others didn't have video output.
Thank you @hexdump0815 for your suggestion! I used dd if=vmlinux.kpart-5.19.1-stb-cbr+ of=/dev/sdc1 this time and the Chromebit booted directly to XFCE with no errors. It seems to run well on veyron-mickey, other than the non-functional graphics acceleration. Please let me know if you want to test anything in particular on mickey.
@mattschwantes - thanks for testing, i have added a note to the veyron readme: https://github.com/hexdump0815/imagebuilder/commit/e29da873e4bca9b1791d31ac89ed215d7de8c3b9 ... this should be useable with the only limitation that initrd loading is not possible this way ... long term we should have a look at u-boot and in case there is no way to get this working then the pmos guys have hacked some kind of initrd support to the regular boot sequence
gpu accel is disabled by default as it is not 100% stable in all scenarios - should be easy to test by commenting out the lines in https://github.com/hexdump0815/imagebuilder/blob/main/systems/chromebook_veyron/extra-files/etc/modprobe.d/blacklist-panfrost.conf i.e. in /etc/modprobe.d/blacklist-panfrost.conf
good luck and best wishes - hexdump
I'm working with veyron-jerry at the moment, looks like it's hanging - I've also seen this problem with Arch Linux ARM, but it managed to initialize the screen and show a console during boot.
I guess this is confirmation that the CTL Chromebook J4 doesn't work? I've given it a couple tries, checked my configs, and I'm not seeing a change (even over HDMI). Just in case I'm missing something, I'm including pictures of my partition layout, and my extlinux.conf.
@starfoxdot64 - it looks like you are trying to get usb to boot and not sdcard. If you might read https://github.com/hexdump0815/imagebuilder/issues/130#issuecomment-1454021880 and in the next entry @mattschwantes confirms that it works. I can also confirm that that suggestion works on booting from usb on left side of eduGear M4 chromebook veyron_mighty.
@starfoxdot64 - it looks like you are trying to get usb to boot and not sdcard. If you might read https://github.com/hexdump0815/imagebuilder/issues/130#issuecomment-1454021880 and in the next entry @mattschwantes confirms that it works. I can also confirm that that suggestion works on booting from usb on left side of eduGear M4 chromebook veyron_mighty.
Alright, I'll have to give that a shot later. I'll admit, I didn't look over the comments in this issue thread since it's not specific to Veyron boards, but that's definitely a good pointer for testing.
I can't say i'm the most optimistic though, since the CTL Chromebook J4+ is in the untested portion of veyron-jerry models.
Hello,
I have X96Q2 TV box (H313 SoC) I tried to flash last feb build, and it's just stuck on red led, after connecting UART this shows in console:
U-Boot SPL 2021.04-18166-g647b392bf2-dirty (Jan 27 2023 - 08:09:08 +0100) DRAM:This DRAM setup is currently not supported.
Here is my stock UART console log in case it's useful: https://pastebin.com/9w0EiapP
@starfoxdot64 - i think the chances should be good to get jerry working, maybe try the different u-boot options (even the non jerry ones) until you get the u-boot menu and if you are there try all options given there ...
@xAbdaziz - maybe your box is one of the newer ones with lpddr3 (h313 is just a low quality h616)? - the only way then is to build your own u-boot based on https://oftc.irclog.whitequark.org/linux-sunxi/2023-02-27#31929559 (if that even works at all) ... for that please keep in mind that gcc should not be 11 or 12 - see: https://oftc.irclog.whitequark.org/linux-sunxi/2023-03-02#31938041 ... otherwise using the images on tv boxes is "if it works it works - otherwise its bad luck" - too little consistency across devices to put too much effort into them
good luck and best wishes - hexdump
ps: there is also some lpddr4 code which might be worth a try: https://github.com/iuncuim/u-boot/commit/2a59bd30a82396f78279a972e79a9b04b56af2c7 via: https://oftc.irclog.whitequark.org/linux-sunxi/2022-12-09#31699422
@xAbdaziz - maybe your box is one of the newer ones with lpddr3 (h313 is just a low quality h616)? - the only way then is to build your own u-boot based on https://oftc.irclog.whitequark.org/linux-sunxi/2023-02-27#31929559 (if that even works at all) ... for that please keep in mind that gcc should not be 11 or 12 - see: https://oftc.irclog.whitequark.org/linux-sunxi/2023-03-02#31938041 ... otherwise using the images on tv boxes is "if it works it works - otherwise its bad luck" - too little consistency across devices to put too much effort into them
good luck and best wishes - hexdump
ps: there is also some lpddr4 code which might be worth a try: iuncuim/u-boot@2a59bd3 via: https://oftc.irclog.whitequark.org/linux-sunxi/2022-12-09#31699422
Thanks, yes it seems that i have LPDDR3 RAM I will try compiling U-Boot from that repo and report back 👍🏻
@xAbdaziz - maybe your box is one of the newer ones with lpddr3 (h313 is just a low quality h616)? - the only way then is to build your own u-boot based on https://oftc.irclog.whitequark.org/linux-sunxi/2023-02-27#31929559 (if that even works at all) ... for that please keep in mind that gcc should not be 11 or 12 - see: https://oftc.irclog.whitequark.org/linux-sunxi/2023-03-02#31938041 ... otherwise using the images on tv boxes is "if it works it works - otherwise its bad luck" - too little consistency across devices to put too much effort into them
good luck and best wishes - hexdump
ps: there is also some lpddr4 code which might be worth a try: iuncuim/u-boot@2a59bd3 via: https://oftc.irclog.whitequark.org/linux-sunxi/2022-12-09#31699422
Looks like warpme already tried that repo and it didn't work for him :(
@xAbdaziz - as you do not seem to fear to compile your own u-boot etc., maybe just ask at the #linux--sunxi irc channel - people there are usually quite helpful and might help to debug it together if someone is willing to do the compiling and testing ...
@starfoxdot64 - i think the chances should be good to get jerry working, maybe try the different u-boot options (even the non jerry ones) until you get the u-boot menu and if you are there try all options given there ...
@hexdump0815 I got it working with the veyron-speedy uboot build, but it's not booting the bookworm image. I have uboot's shell now though, which is progress. ^^
@starfoxdot64 - do you get any error messages when it tries to boot? you boot from sd-card right?
@starfoxdot64 - do you get any error messages when it tries to boot? you boot from sd-card right?
I found that it just wasn't detecting my USB on the right port. It works on the left, but Debian doesn't boot when using Jerry or Speedy's kernel. Mighty works though - I'm still figuring this out, but so far the J4+ isn't responding well to the Jerry presets/kernel.
@starfoxdot64 - nice to see the progress ... maybe it is not really a jerry in the mainline code? also the mighty of @unixabg in https://github.com/hexdump0815/imagebuilder/issues/110 seems to be some mix of minnie and mighty on the mainline side at the end :)
lets maybe move any further discussion over to https://github.com/hexdump0815/imagebuilder/issues/81 where it fits a bit better now
is this expected to work on odroid-c1? ( as it uses the same SoC ) It doesn't boot.
Tried release 210808-04 bullseye on odroid-c1 and doesn't boot either.
@gociii - it might be worth a try, but one thing missing for sure is some boot block - you may try to steal one from some other image (via dd: reading: dd if=/dev/otherimagedevice of=boot.dd bs=512 count=32768 status=progress - writing to your written image: dd if=boot.dd of=/dev/yourwrittenimagedevice bs=512 seek=1 skip=1 count=32767) and depending on how the boot block works some adjustments of the boot scripts in /boot are most probably required as well - a dtb file for the c1 should be included i think. and there is no hdmi support.
best wishes and good luck - hexdump
Hi @hexdump0815
Is it possible to boot your debian sid image directly from NVMe on the VF2? I have updated my VF2 to the latest u-boot and firmware which supposedly allows this. If so, could you please provide instructions.
I have tried without any success to get the official StarFive Debian '69' image to boot off NVMe, I get a kernel panic when I try to boot it from NVMe:
https://forum.rvspace.org/t/nvme-boot-using-visionfive2-software-v2-11-5/2464/17
It seems you've applied a few patches to your kernel so hopefully it can boot from NVMe OK?
There is also a port of Arch to the VF2 which runs great off SD card but I've not been able to get that to boot from NVMe because I was unable to mount its BTRFS partition to adjust the fstab so please explain how to correctly mount your images BTRFS partition if I need to edit fstab.
Thanks
sorry for the deleyed response, i'm mostly offline right now - i did not add or test direct nvme boot you, but looks like you got it somehow working: http://forum.rvspace.org/t/nvme-boot-using-visionfive2-software-v2-11-5/2464/20
@hexdump0815 Kind of, but only by manually entering a few u-boot commands. This proves to me that is not a problem with your kernel, its me that doesn't know how to use u-boot properly.
