Bug#1016963: u-boot: delay migration to testing to test more platforms

[Vagrant Cascadian]

Source: u-boot
Version: 2022.07+dfsg-1
Severity: serious
X-Debbugs-Cc: Vagrant Cascadian <vag...@debian.org>

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

live well,
vagrant

[Vagrant Cascadian]

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
>

> Well, this turned out to be pretty troublesome. The pinebook-pro-rk3399
> u-boot boots, but causes issues loading the rootfs from nvme or microsd.

Pushed a fix for the pinebook-pro-rk3399 to the debian/sid branch by
pulling a patch from upstream:

https://salsa.debian.org/debian/u-boot/-/commit/2557bb1b4be611fb1d8f96d7de79914ca21fa2b6

This fix landed in upstream in 2023.01-rc4.


> the odroid-c2 crashes as soon as it tries to switch to the kernel.

Still need to dig out the odroid-c2 and possibly troubleshoot if there
is something in the flashing process that has changed, or ... bisect
upstream git.


live well,
vagrant

[Vagrant Cascadian]

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 101...@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

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

rpi_3
rpi_3_32b

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

rpi_4
bananapi_m2_berry
rpi_4_32b

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

rpi_4
rpi_4_32b

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

orangepi_one_plus

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

dreamplug
jetson-tk1
Bananapi
Cubieboard2
Cubietruck

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

colibri_imx6

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

dh_imx6

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

sheevaplug
mx6cuboxi

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

nitrogen6q
sifive_unleashed

I'm able to test sifive_unmatched myself, but more people testing the
better.

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

mx53loco
wandboard
igep00x0
omap3_beagle
omap4_panda
Cubietruck

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

am335x_boneblack
am335x_evm

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

Linksprite_pcDuino

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

A20-OLinuXino-Lime2-eMMC

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

Linksprite_pcDuino3

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

A20-OLinuXino_MICRO-eMMC

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

Mini-X

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

Bananapi_M2_Ultra
Sinovoip_BPI_M3

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

nanopi_neo_air

live well,
vagrant

[Vagrant Cascadian]

On 2022-12-28, 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 101...@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.

orangepi_zero

live well,
vagrant

[Rick Thomas]

Raspberry Pi 4B (8GB) running bullseye, but does not seem to have any version of u-boot installed. Weird?
Running <aptitude versions '?name(u-boot)'> tells me that the following (among lots of others) versions are available. Should I install one of them and see what happens?

Package u-boot-rpi:
p 2021.01+dfsg-5 stable 500

Package u-boot-rpi:armhf:
p 2021.01+dfsg-5 stable 500

HTH
Rick

[Rick Thomas]

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

> Attachments:
> * signature.asc

[Rick Thomas]

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:

> Attachments:
> * signature.asc

[Reco]

Hi.

On Wed, Dec 28, 2022 at 03:21:05PM -0800, 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!

That Ordoid N2 board that I had was damaged about year ago.
I have not procured a replacement to it since then.

So I cannot test u-boot on Odroid N2 in the foreseeable future.

Reco

[Jonas Smedegaard]

Quoting Vagrant Cascadian (2022-12-29 01:27:29)

> On 2022-12-28, 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 101...@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.
>

> teres_i

Unfortunately both my TERES I laptops are dead (voltage regulator
circuit let out their blue smoke), so I can no longer test U-boot for
that platform :-(


- Jonas

--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
* Sponsorship: https://ko-fi.com/drjones

[x] quote me freely [ ] ask before reusing [ ] keep private

[Vagrant Cascadian]

On 2022-12-29, Diederik de Haas wrote:

> On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote:
>> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*)
>> and experimental (2023.01-rc*)
>>

>> # arm64
>> ...
>> rock64-rk3328
>
> I don't recall ever having issues with u-boot on my Rock64's, so for me
> 2022.04 - 2022.10 surely work. I'll try the experimental version soon.

I have been testing that one, but thanks for the extra testing!


> I generate my own images for Rock64 and that uses 'dd ... seek=' of
> idbloader.img and u-boot.itb from the u-boot-rockchip package.
> I have been doing that since 2021-03, so it's very likely that I haven't seen
> an issue since then.

u-boot-rockchip also includes a u-boot-install-rockchip script which
might simplify the process for you. :)


live well,
vagrant

[Ian Campbell]

booting u-boot and Debian both from external mmc

testing: 2022.04+dfsg-2+b1 "FDT and ATAGS support not compiled in" then resets and loops doing that
unstable: 2022.10+dfsg-2 ok
exp: 2023.01~rc4+dfsg-1 ok

comparing the config of 2022.04+dfsg-2+b1 vs 2022.10+dfsg-2 I see:

-# CONFIG_SUPPORT_PASSING_ATAGS is not set
+# CONFIG_ARCH_GXP is not set
+CONFIG_SUPPORT_PASSING_ATAGS=y
+CONFIG_SETUP_MEMORY_TAGS=y
+CONFIG_CMDLINE_TAG=y
+CONFIG_INITRD_TAG=y

which I suspect explains the failure in 2022.04+dfsg-2+b1.

> jetson-tk1
> Bananapi
> Cubieboard2     

I have these somewhere, I think in a box in the loft, I have to go up
there later anyway so will see if I can find any of them.

> Cubietruck

u-boot on mmc + Debian on sata:

testing: 2022.04+dfsg-2+b1 ok
unstable: 2022.10+dfsg-2 ok
exp: 2023.01~rc4+dfsg-1 ok

I've updated the wiki with the 5 successes, I didn't update the
dreamplug testing entry nor file a bug, I assume 2022.10+dfsg-2 will
eventually be allowed to migrate to fix that issue.


Ian.

[rod...@tjader.xyz]

On 2022-12-28 21:12, Vagrant Cascadian wrote:
> On 2022-12-28, 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 101...@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.
>

> a64-olinuxino

Sadly my a64-olinuxino board has died and I'm no longer able to test it.

[Ian Campbell]

On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:

> jetson-tk1

testing: 2022.04+dfsg-2+b1  ok
unstable: 2022.10+dfsg-2 ok
exp: 2023.01~rc4+dfsg-1 ok

> Bananapi

I don't seem to have a working setup for this any more, sorry.

> Cubieboard2     

testing: 2022.04+dfsg-2+b1 ok
unstable: 2022.10+dfsg-2 ok
exp: 2023.01~rc4+dfsg-1 ok

I mentioned those successes on the wiki.

[Philip Rinn]

On 29.12.22 at 01:14, Vagrant Cascadian wrote:
>> 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 101...@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.
>

> a64-olinuxino-emmc

I tested all four versions and they work on my A64-Olinuxino-eMMC board. [Tested
from and updated unstable installation.]

Best,
Philip

[Walter Lozano]

On 12/28/22 20:53, Vagrant Cascadian wrote:
> On 2022-12-28, 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 101...@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.
>

> rock-pi-4-rk3399
>


Sorry for the late reply, let me run some tests and confirm the status.

Regards,

--
Walter Lozano
Collabora Ltd.

[Frédéric Danis]

Hi Vagrant,

On 29/12/2022 00:57, Vagrant Cascadian wrote:
> On 2022-12-28, 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 101...@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.

> orangepi_zero_plus2

U-boto works fine for all versions on Orange Pi Zero Plus 2 H5 board.
I updated the wiki page.

Regards,

Fred

--
Frédéric Danis
Senior Software Engineer

Collabora Ltd.
Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, United Kingdom
Registered in England & Wales, no. 5513718

[Jochen Sprickerhof]

Hi Vagrant,

* Vagrant Cascadian <vag...@debian.org> [2022-12-28 16:56]:

>>>>> 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 101...@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.
>
>Mini-X

Works fine with unstable, I've updated the wiki page.

Cheers Jochen

[Christopher Obbard]

On Wed, 2022-12-28 at 15:53 -0800, Vagrant Cascadian wrote:
> On 2022-12-28, 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 101...@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.
>

> rock-pi-4-rk3399

Hi Walter, Hi Vagrant,


I tested this board and updated the wiki. All looks fine to me.

- rock-pi-4-rk3399, on rock-pi-4b, 2023.01-rc4+dfsg-1 from experimental
- SD boot: works
- MAC address: correctly derived from serial number


- rock-pi-4-rk3399, on rock-pi-4b, 2022.10+dfsg-2 from unstable
- SD boot: works
- MAC address: correctly derived from serial number

[Christopher Obbard]

On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote:
> Hi Christopher and Vagrant

> Thank you for your help here! I also did some testing, and everything
> looks OK. The only thing to mention is that the the script
> u-boot-install-rockchip  does not auto detect my board.
>
> The case statement is
> ```
>                 "Radxa ROCK Pi 4")
>                         TARGET="/usr/lib/u-boot/rock-pi-4-rk3399"
> ```

Ah, good catch!

For compatiblity with mainline (debian) kernel, that line should
probably be updated to:

"Radxa ROCK Pi 4A"|"Radxa ROCK Pi 4A+"|"Radxa ROCK Pi
4B"|"Radxa ROCK Pi 4B+")


The Radxa kernel[1] 4.14 branches use "ROCK PI 4A" and "ROCK PI 4B", we
could add those in if we really wanted to. The 5.10 based kernels use
devicetrees based on mainline, so are unaffected.


Thanks!

Chris

[1]:
https://github.com/radxa/kernel/blob/stable-4.4-rockpi4/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4a.dts
>

> fails since the string in my case is only "ROCK Pi 4". Of course, by
> setting TARGET variable I can upgrade it without problems. I don't
> consider this an issue and it is probably related to the kernel I am
> using, since I have used as starting point the images from Radxa [1].
>
> Regards,
>
> Walter
>
> [1] https://wiki.radxa.com/Rockpi4/downloads
>

[Vagrant Cascadian]

On 2022-12-28, Rick Thomas wrote:
> 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?>

Installing the packge does not install u-boot to the boot media, it is a
manual process, as it can be board-specific.

> Other info that might be helpful that shows with the reboot is
> CPU: Freescale i.MX6Q rev 1.3
> Board: MX6 Cubox-i

For Cubox-i install u-boot-imx and see
/usr/share/doc/u-boot-imx/README.Debian for instructions on how to
actually install the boot firmware onto microSD.


live well,
vagrant

[Bernhard]

Hello Vagrant

I tested the following versions successfully at the BananaPi M3:
- bookworm/testing: 2022.04+dfsg-2+b1
- sid/unstable: 2022.10+dfsg-2
- experimental: 2023.01~rc4+dfsg-1
I also updated the Wiki page.

Best regards
Bernhard

[Jochen Sprickerhof]

* Vagrant Cascadian <vag...@debian.org> [2023-01-05 12:29]:

>On 2023-01-04, Jochen Sprickerhof wrote:
>> * Vagrant Cascadian <vag...@debian.org> [2022-12-28 16:56]:

>>>> 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 101...@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.
>>>
>>>Mini-X
>>
>> Works fine with unstable, I've updated the wiki page.
>

>Thanks! Any chance you could also test 2023.01-rc* from experimental? At
>this point 2023.01 is the version I am most likely to try to push to
>bookworm.

2023.01~rc4+dfsg-2 from unstable also works fine (updated the wiki
page).

Cheers Jochen

[Jonas Smedegaard]

Quoting Jens Thiele (2023-01-08 12:03:22)

> Jonas Smedegaard <d...@jones.dk> writes:
>
> > Unfortunately both my TERES I laptops are dead (voltage regulator
> > circuit let out their blue smoke), so I can no longer test U-boot for
> > that platform :-(
>

> a little bit off-topic but:
> Is this a known hardware bug? is olimex aware of the problem?
> I also have a broken TERES I, I thought maybe the power adapter is the
> problem, but I don't know.

Excellent question!

(yeah, strictly speaking off-topic for the issue raised, but on-topic
for the relevancy of TERES-I as Debian laptop (not just OSHW-compliant
paperweight)

I have not yet contacted Olimex about my issue, but intended to do so.

My experience, for both laptops - using same power supply but happening
several months apart - was that the area around the power plug got so
hot that the surface plastic underneath melted, and then the system
turned off: There was a strong smell of melted plastic afterwards.

Did you experience the exact same, or something else that might have a
different cause?

[Arne Ploese]

I was successfully able to install the SD image for stable and unstable
(daily with u-boot from 2023-01-18.

Then I upgraded stable to testing und updated u-boot to 2023.01+dfsg1.

Arne

[Vagrant Cascadian]

On 2022-12-29, Ian Campbell wrote:
> On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote:
>> dreamplug
>
> booting u-boot and Debian both from external mmc
>
> testing: 2022.04+dfsg-2+b1 "FDT and ATAGS support not compiled in" then resets and loops doing that
> unstable: 2022.10+dfsg-2 ok
> exp: 2023.01~rc4+dfsg-1 ok

Any chance you could test 2023.01+dfsg-1 and/or 2023.01+dfsg-2 on the
dreamplug? Someone had problems with sheevaplug, which I think is a
fairly similar platform.

live well,
vagrant

[Ian Campbell]

Done, both versions worked fine on dreamplug.

I also think dreamplug is a fairly similar platform to sheevaplug, but
I have no personal experience of the latter.

Ian.