** Changed in: u-boot (Ubuntu Hirsute)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notificati
This bug was fixed in the package u-boot-menu - 4.0.2ubuntu5~20.04.1
---
u-boot-menu (4.0.2ubuntu5~20.04.1) focal; urgency=medium
* SRU changes from hirsute to enable booting on the HiFive Unmatched
LP: #1925267 LP: #1923162
u-boot-menu (4.0.2ubuntu5) hirsute; urgency=medium
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu0~20.04.1
---
u-boot (2021.01+dfsg-3ubuntu0~20.04.1) focal; urgency=medium
* SRU of 2021.01+dfsg-3 from hirsute to enable booting on HiFive Unmatched
LP: #1934791, LP: #1925267, LP: #1923162
[ Dimitri John Ledkov
The changes in ubuntu9.1 did make it into impish in ubuntu10.
https://launchpadlibrarian.net/538731561/u-boot_2021.01+dfsg-3ubuntu9_2021.01+dfsg-3ubuntu10.diff.gz
However, it looks like they were later removed from impish.
https://launchpadlibrarian.net/539465636/u-boot_2021.01+dfsg-3ubuntu10_20
On Tue, 27 Jul 2021, 05:45 Brian Murray, <1923...@bugs.launchpad.net>
wrote:
> I'm sorry to be a bother here but I don't understand how u-boot failed
> verification for hirsute but passed for focal when what are presumably
> the same patches exist in both versions of the package. How could this
>
I'm sorry to be a bother here but I don't understand how u-boot failed
verification for hirsute but passed for focal when what are presumably
the same patches exist in both versions of the package. How could this
happen?
--
You received this bug notification because you are a member of Ubuntu
Bug
sil2100 sorry for the delayed response. I originally thought that the
verification-failed-hirsute tag was left over from a previous regression
we had in this package. I will investigate what is needed in hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Per my discussion with Dimitri on IRC, I'm switching the tag to
verification-failed for hirsute again and then proceeding with dropping
the hirsute-proposed u-boot package.
** Tags removed: verification-needed-hirsute
** Tags added: verification-failed-hirsute
--
You received this bug notificati
Hey William! Any reason why the verification-failed-hirsute tag has been
removed? Did you discuss with Dimitri and all is good already, or is the
update still incorrect for hirsute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The verification passed for focal. The daily images are building with
u-boot-menu-4.0.2ubuntu5~20.04.1. I have successfully booted these daily
images in qemu and Unmatched hardware.
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-29-generic riscv64)
* Documentation: https://help.ubuntu.com
* Ma
Oh https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu9.1
is an orphan, as it did not make it into impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fa
Impish is not affected, as it still skips fdtdir under qemu completely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications abou
Trying to see if impish u-boot is also broken at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug
$ dpkg-query -W u-boot-qemu
u-boot-qemu 2021.01+dfsg-3ubuntu9.1
$ qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
device,netdev=eth0 -netdev user,id
Hello Dimitri, or anyone else affected,
Accepted u-boot into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
re: u-boot-menu backport, imho the debian/changelog should be merged and
focal entries should not be lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in
@jawn-smith https://paste.ubuntu.com/p/hjqFz46frm/ is what i'm
sponsoring, after fix ups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage
Re: u-boot-menu backport, imho debian/changelog should have documented
that debhelper-compat version is lowered from 13 to 12, to make it build
on focal. But also it is self-explanatory (i did try to get debhelper 13
into focal before it released, but that upload got rejected).
Otherwise no change
@sil2100 sorry - that's my fault for skimming this (and the breaks: bit
too -- that's actually not necessary as the backport re-instates the
postinst installing the binaries to the boot partition; the breaks was
there as later releases ditched the postinst and passed the
responsibility for copying
Ok, leaving a trace here as well, regarding the u-boot upload in the focal
Unapproved queue, other than direct messages: currently in the .changes file
there are 3 bugs attached, 2 of which do not have SRU templates, so we'd need
that + since this is a backport, I feel a bit sad that there's no
** Changed in: u-boot-menu (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage noti
This patch backports the changes from hirsute in u-boot-menu to focal.
** Changed in: u-boot-menu (Ubuntu Focal)
Status: Invalid => In Progress
** Changed in: u-boot-menu (Ubuntu Focal)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Patch added: "lp1923162_focal_u-boot-menu
Hello Dimitri, or anyone else affected,
Accepted u-boot into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-
3ubuntu9.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu10
---
u-boot (2021.01+dfsg-3ubuntu10) impish; urgency=medium
* Revert "Skip processing fdtdir on qemu-riscv64_smode target, as it crashes
the
riscv qemu VM."
* Apply upstreamed patch "cmd: pxe_utils: sysboot: fix
** Description changed:
- When booting v5.11 based riscv unmatched image in qemu with uboot, it
- fails to boot.
+ [Impact]
- When booting v5.11 based riscv unmatched kernel+initrd directly, it
- boots fine.
+ * u-boot may crash when attempting to boot extlinux.conf which
+ specifies fdtdir; t
** Changed in: u-boot (Ubuntu)
Status: Fix Released => New
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => Triaged
** Changed in: u-boot (Ubuntu Hirsute)
Status: Triaged => New
** Changed in: u-boot (Ubuntu)
Importance: Critical => Undecided
** Also affect
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu8
---
u-boot (2021.01+dfsg-3ubuntu8) hirsute; urgency=medium
* Skip processing fdtdir on qemu-riscv64_smode target, as it crashes the
riscv qemu VM. LP: #1925267 LP: #1923162
-- Dimitri John Ledkov Wed, 21 Apr 20
** Tags removed: block-proposed block-proposed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~xnox/ubuntu/+source/u-boot/+git/u-boot/+merge/401545
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boo
** Tags added: block-proposed block-proposed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
h
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications ab
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu6
---
u-boot (2021.01+dfsg-3ubuntu6) hirsute; urgency=medium
* Set USE_PREBOOT on unmatched board too (just like unleashed & qemu),
otherwise u-boot's fdtfile from itb is not used (i.e. when
extlinux.conf does no
** Changed in: u-boot (Ubuntu)
Status: Confirmed => In Progress
** Also affects: u-boot (Ubuntu Hirsute)
Importance: Critical
Status: In Progress
** Also affects: u-boot-menu (Ubuntu Hirsute)
Importance: Critical
Status: Fix Released
** Also affects: linux-riscv (Ubunt
So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.
Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but n
This bug was fixed in the package u-boot-menu - 4.0.2ubuntu4
---
u-boot-menu (4.0.2ubuntu4) hirsute; urgency=medium
* Revert "Add support for ubuntu kernels location of device trees." as
it breaks booting riscv64 images with qemu, as the qemu in-ram dtb
should be used not th
** Tags added: fr-1282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
It appears that although fdtdir option from u-boot-menu works on bare
metal, it breaks qemu booting.
Thus revert it from now, seeking more details from u-boot upstream.
** Also affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: u-boot-menu (Ubuntu)
St
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifica
** Attachment added: "direct-qemu-riscv.txt"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1923162/+attachment/5485930/+files/direct-qemu-riscv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This is reproducible with any uboot from focal/groovy/hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bu
** Attachment added: "uboot-qemu-riscv.txt"
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1923162/+attachment/5485929/+files/uboot-qemu-riscv.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
41 matches
Mail list logo
