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


Groups > linux.debian.kernel > #68846

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

From Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel
Date 2020-12-13 21:40 +0100
Message-ID <BlGjU-3fI-13@gated-at.bofh.it> (permalink)
References <BkNGN-3td-1@gated-at.bofh.it> <BlCSZ-13N-5@gated-at.bofh.it> <BkNGN-3td-1@gated-at.bofh.it> <BlCSZ-13N-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


> The rpi flavour doesn't have those constraints, though.  What would be
> the benefit of booting it in UEFI mode?

Thank you for paying your attention!
I considered extending autopkgtest-virt-qemu to armel (and other archs) testbeds at
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100#note_205984

To boot a qemu disk image by qemu-system-*, a booting firmware seems
indispensable, as the autopkgtest maintainer does not like giving -kernel=something
qemu option as
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/97#note_205357

A booting firmware for an armel Debian disk image seems only
the qemu-efi-arm Debian package (is there anything else??).
So I resorted to the UEFI booting.
Currently I proposes to use linux-image-armmp-lpae for armel testbed.

Best regards, Ryutaroh

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-11 11:20 +0100
  Processed: Re: Bug#977126: linux: No armel kernel can be booted  by grub-efi-arm:armel "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-12-13 18:00 +0100
  Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ben Hutchings <ben@decadent.org.uk> - 2020-12-13 18:00 +0100
    Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-13 21:40 +0100
      Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ben Hutchings <ben@decadent.org.uk> - 2020-12-13 21:50 +0100
        Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-14 02:30 +0100
          Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ben Hutchings <ben@decadent.org.uk> - 2020-12-14 03:10 +0100
            Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-14 03:30 +0100
              Bug#977126: linux-image-rpi does not boot by qemu-system-arm -machine raspi0 Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-14 10:10 +0100
                Bug#977126: panic log attached Re: linux-image-rpi does not boot by qemu-system-arm -machine raspi0 Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-14 22:30 +0100
                Bug#977126: panic log attached Re: linux-image-rpi does not boot by qemu-system-arm -machine raspi0 Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp> - 2020-12-15 08:50 +0100
  Processed: Re: panic log attached Re: linux-image-rpi does not  boot by qemu-system-arm -machine raspi0 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-12-15 08:50 +0100

csiph-web