Re: Bug#1016963: Help with testing u-boot!
A Cubox-i running Debian bullseye (11.6). According to <aptitude versions> It has "u-boot-tools" (version 2021.01+dfsg-5) installed, but none of the u-boot-<arch> packages installed.
If I reboot it and watch the serial console, I see it showing "U-boot 2021.01-dfsg-5" so that version must have gotten into the firmware somehow without telling Linux about it... <shrug?>
Other info that might be helpful that shows with the reboot is
CPU: Freescale i.MX6Q rev 1.3
Board: MX6 Cubox-i
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 1016963@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
Reply to: