Repacking initrd as initrd.lz is a working workaround on d05. By using
initrd.lz, I could not reproduce this issue on d05-4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900773
Title:
thunderx
My apologies. The comment#9 https://bugs.launchpad.net/ubuntu/+source
/livecd-rootfs/+bug/1900773/comments/9 used the grubnetaa64.efi from
focal http://ports.ubuntu.com/ubuntu-
ports/dists/focal/main/uefi/grub2-arm64/current/grubnetaa64.efi.signed
If d05 (d05-4) uses the groovy grub, it COULD
More infomation. I can not reproduce with grubnetaa64.efi from focal.
This is the focal grub I download, which can not reproduce
http://ports.ubuntu.com/ubuntu-
ports/dists/focal/main/uefi/grub2-arm64/current/grubnetaa64.efi.signed
This is the groovy grub, which is able to reproduce
** Also affects: ubuntu-release-notes
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/1900773
Title:
thunderx CRB systems tftp timeout downloading initrd
** Also affects: grub2 (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/1900773
Title:
thunderx CRB systems tftp timeout downloading initrd
To
Since technically GRUB is requesting the initrd file, I tried to rule it
out as a possible cause by seeing if the initial payload that UEFI
downloads directly would time out if it was the same size. I did this by
padding my grubnetaa64.efi binary to be the same size as the installer
initrd.
mv
I tried 20201021 Groovy daily live with Hisilicon d05 via PXE, and I did
NOT reproduce this issue.
[Post-installation Information]
ubuntu@d05-4-20-10-rc-102021-pxe-tai-1:~$ cat /var/log/installer/media-info ;
echo ; uname -a; lsb_release -a
Ubuntu-Server 20.10 "Groovy Gorilla" - Release arm64
90771321 initrd
44620048 initrd.lzma
Yes. recompress with `lzma -9` and I can finish the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900773
Title:
thunderx CRB systems tftp
On Wed, Oct 21, 2020, 03:20 Ike Panhc <1900...@bugs.launchpad.net>
wrote:
> I hit this issue on Hisilicon d06 when PXE groovy subiquity. System
> boots without initrd and hang on no rootfs.
>
>
> error: timeout reading `/casper/initrd'.
>
> Press any key to continue...
>
Interesting, does
I hit this issue on Hisilicon d06 when PXE groovy subiquity. System
boots without initrd and hang on no rootfs.
error: timeout reading `/casper/initrd'.
Press any key to continue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, Oct 20, 2020 at 5:30 PM Steve Langasek
<1900...@bugs.launchpad.net> wrote:
>
> And is there something intrinsic to this hardware that leads to the
> timeout?
I wonder if there might be a firmware bug. Here's what I see on the
wire:
52120 56.958016 10.229.50.135 10.229.50.84 TFTP 78 Read
On Tue, Oct 20, 2020 at 5:30 PM Steve Langasek
<1900...@bugs.launchpad.net> wrote:
>
> Just to confirm, are you using the initrd as extracted from the .iso?
I am.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to confirm, are you using the initrd as extracted from the .iso?
** Project changed: ubuntu-cdimage => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900773
Title:
And is there something intrinsic to this hardware that leads to the
timeout? Or would this perhaps work if the machine had a faster network
link to the tftp server?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
14 matches
Mail list logo
