Hi Vagrant,
Sorry for the late reply. I've been testing u-boot on the Odroid U3
the last couple of days. Turns out that u-boot doesn't work in stable
(again, sorry!). I've bisected the problem to commit
4963f63fe61f15329d77472a762b1d8bf754d24b (u-boot repo, somewhere
between v2020.10 and v2021.01). Reverting this commit in v2021.01
fixes the problem.
I noticed the following change in u-boot's output. Before said commit:
Kernel image @ 0x4100 [ 0x00 - 0x3fd200 ]
## Flattened Device Tree blob at 4080
Booting using the fdt blob at 0x4080
Loading Ramdisk to 4ece6000, end 49f5 ... OK
Loading Device Tree to 4ecd6000, end 4ece5f41 ... OK
After the commit:
Kernel image @ 0x4100 [ 0x00 - 0x3fd200 ]
## Flattened Device Tree blob at 4080
Booting using the fdt blob at 0x4080
Loading Ramdisk to b9b6, end bae799f5 ... OK
Loading Device Tree to b9b5, end b9b5ff41 ... OK
I've browsed through the source code and found that you can control
the position of the initrd using environment variable `initrd_high`.
Setting this to `0x5000` solves the problem as well in v2021.01
without reverting 4963f63f. Also `0x` works, which according
to u-boot's README disables the relocation of the initrd. The position
of the device tree doesn't seem to matter.
I'm not sure how to proceed with this and any guidance is appreciated,
but given that you're busy with finishing bookworm, I completely
understand that you don't have time for this.
Best, Joost
Op do 29 dec. 2022 om 01:39 schreef 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 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.
>
> odroid
>
> live well,
> vagrant
