Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1130170 > unrolled thread
| Started by | Jochen Sprickerhof <jspricke@debian.org> |
|---|---|
| First post | 2022-12-25 20:00 +0100 |
| Last post | 2022-12-29 08:10 +0100 |
| Articles | 3 — 2 participants |
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.
Bug#1012269: u-boot-exynos on Odroid XU4 searches for exynos5422-smdk5420xu4.dtb instead of exynos5422-odroidxu4.dtb Jochen Sprickerhof <jspricke@debian.org> - 2022-12-25 20:00 +0100
Bug#1012269: u-boot-exynos on Odroid XU4 searches for exynos5422-smdk5420xu4.dtb instead of exynos5422-odroidxu4.dtb Vagrant Cascadian <vagrant@debian.org> - 2022-12-29 03:10 +0100
Bug#1012269: u-boot-exynos on Odroid XU4 searches for exynos5422-smdk5420xu4.dtb instead of exynos5422-odroidxu4.dtb Jochen Sprickerhof <jspricke@debian.org> - 2022-12-29 08:10 +0100
| From | Jochen Sprickerhof <jspricke@debian.org> |
|---|---|
| Date | 2022-12-25 20:00 +0100 |
| Subject | Bug#1012269: u-boot-exynos on Odroid XU4 searches for exynos5422-smdk5420xu4.dtb instead of exynos5422-odroidxu4.dtb |
| Message-ID | <FGEo1-dcoC-15@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi Vagrant,
* Vagrant Cascadian <vagrant@debian.org> [2022-11-04 14:22]:
>On 2022-06-02, Jochen Sprickerhof wrote:
>> with the latest u-boot-exynos in unstable it tries to load
>> exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
>> contains exynos5422-odroidxu4.dtb. This was not the case with 2022.01+dfsg-2:
>>
>> U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +0000) for ODROID-XU3/XU4/HC1/HC2
>> [..]
>> Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb
>> ** File not found /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb **
>>
>> U-Boot 2022.01+dfsg-2 (Jan 26 2022 - 19:58:27 +0000) for ODROID-XU3/XU4/HC1/HC2
>> [..]
>> Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-odroidxu4.dtb
>
>Thanks for bringing this up in IRC.
>
>My guess is this was broken in 2022.04, and fixed in 2022.07-rc5 with
>this commit:
>
[..]
>
>Could you test 2022.10 from unstable and/or pull 2022.07 from
>snapshots.debian.org and test it?
I finally found time to test, sorry for the delay. Still the same
problem:
U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +0000) for ODROID-XU3/XU4/HC1/HC2
CPU: Exynos5422 @ 800 MHz
DRAM: 2 GiB
Core: 73 devices, 12 uclasses, devicetree: separate
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Odroid XU3/XU4/HC1/HC2 based on Exynos5422
Type: xu4
Boot device: MMC(0)
Net: No ethernet found.
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
MMC Device 1 not found
no mmc device at slot 1
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1: Debian GNU/Linux bookworm/sid 6.0.0-6-armmp
2: Debian GNU/Linux bookworm/sid 6.0.0-6-armmp (rescue target)
3: Debian GNU/Linux bookworm/sid 5.18.0-2-armmp
4: Debian GNU/Linux bookworm/sid 5.18.0-2-armmp (rescue target)
Enter choice: 1: Debian GNU/Linux bookworm/sid 6.0.0-6-armmp
Retrieving file: /boot/initrd.img-6.0.0-6-armmp
Retrieving file: /boot/vmlinuz-6.0.0-6-armmp
append: root=LABEL=mmcroot rw quiet mitigations=off
Retrieving file: /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb
** File not found /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb **
Kernel image @ 0x42000000 [ 0x000000 - 0x4f3200 ]
## Flattened Device Tree blob at b99684d0
Booting using the fdt blob at 0xb99684d0
Loading Ramdisk to 4f3a5000, end 4fffff7f ... OK
Loading Device Tree to 4f39e000, end 4f3a49a7 ... OK
Starting kernel ...
The workaround with:
ln -s exynos5422-odroidxu4.dtb exynos5422-smdk5420xu4.dtb
works.
Cheers Jochen
[toc] | [next] | [standalone]
| From | Vagrant Cascadian <vagrant@debian.org> |
|---|---|
| Date | 2022-12-29 03:10 +0100 |
| Message-ID | <FHQwN-dZXD-1@gated-at.bofh.it> |
| In reply to | #1130170 |
[Multipart message — attachments visible in raw view] — view raw
On 2022-12-25, Jochen Sprickerhof wrote:
> * Vagrant Cascadian <vagrant@debian.org> [2022-11-04 14:22]:
>>On 2022-06-02, Jochen Sprickerhof wrote:
>>> with the latest u-boot-exynos in unstable it tries to load
>>> exynos5422-smdk5420xu4.dtb whereas linux-image-5.17.0-3-armmp only
>>> contains exynos5422-odroidxu4.dtb. This was not the case with 2022.01+dfsg-2:
>>>
>>> U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +0000) for ODROID-XU3/XU4/HC1/HC2
>>> [..]
>>> Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb
>>> ** File not found /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-smdk5420xu4.dtb **
>>>
>>> U-Boot 2022.01+dfsg-2 (Jan 26 2022 - 19:58:27 +0000) for ODROID-XU3/XU4/HC1/HC2
>>> [..]
>>> Retrieving file: /usr/lib/linux-image-5.17.0-3-armmp/exynos5422-odroidxu4.dtb
...
>>My guess is this was broken in 2022.04, and fixed in 2022.07-rc5 with
>>this commit:
...
>>Could you test 2022.10 from unstable and/or pull 2022.07 from
>>snapshots.debian.org and test it?
>
> I finally found time to test, sorry for the delay. Still the same
> problem:
>
> U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +0000) for ODROID-XU3/XU4/HC1/HC2
>
> CPU: Exynos5422 @ 800 MHz
> DRAM: 2 GiB
> Core: 73 devices, 12 uclasses, devicetree: separate
> MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
> Loading Environment from MMC... *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Model: Odroid XU3/XU4/HC1/HC2 based on Exynos5422
> Type: xu4
> Boot device: MMC(0)
...
> Retrieving file: /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb
> ** File not found /usr/lib/linux-image-6.0.0-6-armmp/exynos5422-smdk5420xu4.dtb **
...
> The workaround with:
>
> ln -s exynos5422-odroidxu4.dtb exynos5422-smdk5420xu4.dtb
Hrm. This suggests the fix might not have been effective, which should
have been included in 2022.07... CCing upstream...
commit e744bf3a4ba442a0e9ee1c509c70e1452e3a15d0
Author: Tom Rini <trini@konsulko.com>
Date: Wed Jun 8 14:30:14 2022 -0400
odroid_xu3: Fix board environment variable
When migrating CONFIG_CONS_INDEX to Kconfig, on this platform we changed
what "board" evaluated to in the environment. This in turn meant that
we would no longer try and find the correct fdtfile via the normal
distro boot logic. Fix this by overriding board in the default
environment, as done on other platforms where CONFIG_SYS_BOARD is not
what we want to be in the board environment variable.
Fixes: f76750d11133 ("Convert CONFIG_CONS_INDEX et al to Kconfig")
Reported-by: Gabriel Hojda <ghojda@yo2urs.ro>
Tested-by: Gabriel Hojda <ghojda@yo2urs.ro>
Signed-off-by: Tom Rini <trini@konsulko.com>
Alternately... did you at any point run saveenv? This might have stored
the incorrect value... and then it might not probe for the correct
value.
live well,
vagrant
[toc] | [prev] | [next] | [standalone]
| From | Jochen Sprickerhof <jspricke@debian.org> |
|---|---|
| Date | 2022-12-29 08:10 +0100 |
| Message-ID | <FHVd7-e331-1@gated-at.bofh.it> |
| In reply to | #1130609 |
[Multipart message — attachments visible in raw view] — view raw
* Vagrant Cascadian <vagrant@debian.org> [2022-12-28 18:00]:
>Hrm. This suggests the fix might not have been effective, which should
>have been included in 2022.07... CCing upstream...
>
>commit e744bf3a4ba442a0e9ee1c509c70e1452e3a15d0
>Author: Tom Rini <trini@konsulko.com>
>Date: Wed Jun 8 14:30:14 2022 -0400
>
> odroid_xu3: Fix board environment variable
>
> When migrating CONFIG_CONS_INDEX to Kconfig, on this platform we changed
> what "board" evaluated to in the environment. This in turn meant that
> we would no longer try and find the correct fdtfile via the normal
> distro boot logic. Fix this by overriding board in the default
> environment, as done on other platforms where CONFIG_SYS_BOARD is not
> what we want to be in the board environment variable.
>
> Fixes: f76750d11133 ("Convert CONFIG_CONS_INDEX et al to Kconfig")
> Reported-by: Gabriel Hojda <ghojda@yo2urs.ro>
> Tested-by: Gabriel Hojda <ghojda@yo2urs.ro>
> Signed-off-by: Tom Rini <trini@konsulko.com>
>
>
>Alternately... did you at any point run saveenv? This might have stored
>the incorrect value... and then it might not probe for the correct
>value.
I'm sure I never did that. Out of interest, where would it save the
environment? Afaik there is no persistent memory on the Odroid XU4
besids the emmc/sd card and my system uses a simple extlinux.conf
generated by u-boot-menu.
Cheers Jochen
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web