Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1130571 > unrolled thread

Bug#1016963: Help with testing u-boot!

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 00:30 +0100
    Bug#1016963: Please test u-boot for rpi_3 rpi_3_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:10 +0100
    Bug#1016963: Please test u-boot for rpi_4 rpi_4_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:20 +0100
    Bug#1016963: Please test u-boot for rpi_4 bananapi_m2_berry rpi_4_32b Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:20 +0100
    Bug#1016963: Please test u-boot for orangepi_one_plus Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:30 +0100
    Bug#1016963: Please test u-boot for colibri_imx6 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
      Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Ian Campbell <ijc@debian.org> - 2022-12-29 13:30 +0100
        Bug#1016963: Please test u-boot for dreamplug Vagrant Cascadian <vagrant@debian.org> - 2023-01-21 21:20 +0100
          Bug#1016963: Please test u-boot for dreamplug Ian Campbell <ijc@debian.org> - 2023-01-22 10:00 +0100
      Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck Ian Campbell <ijc@debian.org> - 2022-12-29 18:10 +0100
    Bug#1016963: Please test u-boot for dh_imx6 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for sheevaplug mx6cuboxi Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:40 +0100
    Bug#1016963: Please test u-boot for am335x_boneblack am335x_evm Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for nitrogen6q sifive_unleashed Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for mx53loco wandboard igep00x0 omap3_beagle omap4_panda Cubietruck Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 01:50 +0100
    Bug#1016963: Please test u-boot for Linksprite_pcDuino Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for A20-OLinuXino_MICRO-eMMC Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Mini-X Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
      Bug#1016963: Please test u-boot for Mini-X Jochen Sprickerhof <jspricke@debian.org> - 2023-01-04 23:40 +0100
        Bug#1016963: Please test u-boot for Mini-X Jochen Sprickerhof <jspricke@debian.org> - 2023-01-06 18:10 +0100
    Bug#1016963: Please test u-boot for A20-OLinuXino-Lime2-eMMC Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Linksprite_pcDuino3 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for Bananapi_M2_Ultra Sinovoip_BPI_M3 Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:00 +0100
    Bug#1016963: Please test u-boot for orangepi_zero Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:10 +0100
    Bug#1016963: Please test u-boot for nanopi_neo_air Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 02:10 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:00 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:30 +0100
      Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2023-01-06 01:10 +0100
    Bug#1016963: Help with testing u-boot! "Rick Thomas" <rick.thomas@pobox.com> - 2022-12-29 04:40 +0100
    Bug#1016963: Help with testing u-boot! Reco <bugs@enotuniq.net> - 2022-12-29 07:40 +0100
    Bug#1016963: Help with testing u-boot! Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 11:20 +0100
    Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Walter Lozano <walter.lozano@collabora.com> - 2023-01-03 13:20 +0100
    Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Christopher Obbard <chris.obbard@collabora.com> - 2023-01-05 16:20 +0100
      Bug#1016963: Please test u-boot for rock-pi-4-rk3399 Christopher Obbard <chris.obbard@collabora.com> - 2023-01-05 17:40 +0100

Page 2 of 2 — ← Prev page 1 [2]

#1132010 — Bug#1016963: Please test u-boot for Mini-X

[Multipart message — attachments visible in raw view] — view raw

* Vagrant Cascadian <vagrant@debian.org> [2023-01-05 12:29]:
>On 2023-01-04, Jochen Sprickerhof wrote:
>> * Vagrant Cascadian <vagrant@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 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.
>>>
>>>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

[toc] | [prev] | [next] | [standalone]

#1130592 — Bug#1016963: Please test u-boot for A20-OLinuXino-Lime2-eMMC

[Multipart message — attachments visible in raw view] — view raw

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

A20-OLinuXino-Lime2-eMMC

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#1130593 — Bug#1016963: Please test u-boot for Linksprite_pcDuino3

[Multipart message — attachments visible in raw view] — view raw

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

Linksprite_pcDuino3

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#1130594 — Bug#1016963: Please test u-boot for Bananapi_M2_Ultra Sinovoip_BPI_M3

[Multipart message — attachments visible in raw view] — view raw

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

Bananapi_M2_Ultra
Sinovoip_BPI_M3

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#1130595 — Bug#1016963: Please test u-boot for orangepi_zero

[Multipart message — attachments visible in raw view] — view raw

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

orangepi_zero

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#1130597 — Bug#1016963: Please test u-boot for nanopi_neo_air

[Multipart message — attachments visible in raw view] — view raw

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

nanopi_neo_air

live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#1130611

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

[toc] | [prev] | [next] | [standalone]

#1130612

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

[toc] | [prev] | [next] | [standalone]

#1131889

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#1130613

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 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

[toc] | [prev] | [next] | [standalone]

#1130619

	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

[toc] | [prev] | [next] | [standalone]

#1130639

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#1131421 — Bug#1016963: Please test u-boot for rock-pi-4-rk3399

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 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.
> 
> rock-pi-4-rk3399
> 


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

Regards,

-- 
Walter Lozano
Collabora Ltd.

[toc] | [prev] | [next] | [standalone]

#1131813 — Bug#1016963: Please test u-boot for rock-pi-4-rk3399

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

[toc] | [prev] | [next] | [standalone]

#1131825 — Bug#1016963: Please test u-boot for rock-pi-4-rk3399

On Thu, 2023-01-05 at 13:21 -0300, Walter Lozano wrote:
> Hi Christopher and Vagrant
> 
> On 1/5/23 12:10, Christopher Obbard wrote:
> > 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 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.
> > > 
> > > 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
> > 
> 
> 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
> 

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.bugs.dist

csiph-web