Here's another Cubox-i. This one's running Bookworm. <aptitude versions '?name(u-boot)'> shows a surprising number of u-boot-<arch> packages installed, (<arch> = exynos, imx, omap, sunxi) as well as plain "u-boot". All of them are version 2022.04+dfsg-2+b1.
Rebooting while watching the serial console output says "U-Boot SPL 2016.05-rc2+dfsg0~20160423~1-1 (Apr 24 2016 - 04:24:21)" So the firmware does not correspond to what aptitude says. <hmmm...> Should I try installing the "22.04" version in the firmware? If so, are there directions for doing that available somewhere? HTH Rick On Wed, Dec 28, 2022, at 3:21 PM, Vagrant Cascadian wrote: > On 2022-12-22, Vagrant Cascadian wrote: >> On 2022-08-20, Vagrant Cascadian wrote: >>> On 2022-08-10, Vagrant Cascadian wrote: >>>> This bug is just to delay migration to testing while more platforms get >>>> tested. If you have a relevent board, please consider testing and >>>> reporting the status: >>>> >>>> https://wiki.debian.org/U-boot/Status > > I have not received many test results for current or even remotely > recent u-boot platforms in Debian, and u-boot has been blocked from > migration to testing partly because of this. > > As the bookworm freeze approaches, this is getting to be... worrysome! > > If you have access to any of these boards, please consider testing > u-boot versions as packaged in debian for versions from debian stable > (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental > (2023.01-rc*) and updating the wiki page if successful and/or replying > to 1016...@bugs.debian.org with a positive confirmation... > > ...and if not successful, filing bugs against the relevent u-boot-* > packages and marking them as blocking 1016963. > > # arm64 > khadas-vim > khadas-vim2 > libretech-cc > nanopi-k2 > odroid-c2 > odroid-n2 > mvebu_espressobin-88f3720 > dragonboard410c > dragonboard820c > firefly-rk3399 > nanopc-t4-rk3399 > nanopi-neo4-rk3399 > pinebook-pro-rk3399 > puma-rk3399 > roc-pc-rk3399 > rock-pi-4-rk3399 > rock-pi-e-rk3328 > rock64-rk3328 > rockpro64-rk3399 > rpi_3 > rpi_4 > rpi_arm64 > a64-olinuxino > a64-olinuxino-emmc > nanopi_neo2 > nanopi_neo_plus2 > orangepi_one_plus > orangepi_zero_plus2 > pine64-lts > pine64_plus > pinebook > pinephone > pinetab > sopine_baseboard > teres_i > p2371-2180 > > # armel > dockstar > dreamplug > guruplug > sheevaplug > rpi > rpi_0_w > > # armhf > arndale > odroid > odroid-xu3 > colibri_imx6 > dh_imx6 > mx53loco > mx6cuboxi > mx6qsabrelite > nitrogen6q > novena > novena-rawsd > udoo > usbarmory > wandboard > am335x_boneblack > am335x_evm > am57xx_evm > dra7xx_evm > igep00x0 > nokia_rx51 > omap3_beagle > omap4_panda > firefly-rk3288 > rpi_2 > rpi_3_32b > rpi_4_32b > stm32mp157c-dk2 > A10-OLinuXino-Lime > A10s-OLinuXino-M > A20-OLinuXino-Lime > A20-OLinuXino-Lime2 > A20-OLinuXino-Lime2-eMMC > A20-OLinuXino_MICRO > A20-OLinuXino_MICRO-eMMC > A20-Olimex-SOM-EVB > Bananapi > Bananapi_M2_Ultra > Bananapro > CHIP > Cubieboard > Cubieboard2 > Cubieboard4 > Cubietruck > Cubietruck_plus > Lamobo_R1 > Linksprite_pcDuino > Linksprite_pcDuino3 > Mini-X > Sinovoip_BPI_M3 > bananapi_m2_berry > nanopi_neo > nanopi_neo_air > orangepi_plus > orangepi_zero > jetson-tk1 > > > Thanks! > > > live well, > vagrant > > Attachments: > * signature.asc
