I can't find it in the documentation:
https://www.gnu.org/software/grub/manual/grub/grub.html
https://www.mail-archive.com/search?l=help-grub%40gnu.org=architecture+amd64
you could deduce via dmidecode if a machine is 32- or 64-bit, and,
say, in Debian Linux, after boot up you can get
On 17/12/2023 at 09:43, Albretch Mueller wrote:
you could deduce via dmidecode if a machine is 32- or 64-bit, and,
say, in Debian Linux, after boot up you can get the processor type
from the OS by running:
$ dpkg --print-architecture
amd64
This is Debian-specific and returns the system
a amd64+i386 multi-arch image which was able to boot with PC
BIOS (with ISOLinux, 32-bit x86 UEFI and 64-bit x86 UEFI (with GRUB).
will GRUB2 automatically
detect the architecture and pick the file?
Let's assume you you create such an ISO image for UEFI boot only. It
must contain an EFI
t; I can't find it in the documentation:
>
> https://www.gnu.org/software/grub/manual/grub/grub.html
>
>
> https://www.mail-archive.com/search?l=help-grub%40gnu.org=architecture+amd64
>
> you could deduce via dmidecode if a machine is 32- or 64-bit, and,
> say, in Debian Linux, after boot u
: bootarm64.efi (built for ARM64), bootx64.efi (built for
AMD64/x86_64) and bootriscv64.efi (built for RISC-V64). The UEFI
firmware will seek the matching EFI image, and the GRUB image will
report the architecture in $grub_cpu and $grub_platform.
Note: bootxxx.efi may be a GRUB image or a shim
El 17/12/23 a les 9:43, Albretch Mueller ha escrit:
I can't find it in the documentation:
https://www.gnu.org/software/grub/manual/grub/grub.html
https://www.mail-archive.com/search?l=help-grub%40gnu.org=architecture+amd64
you could deduce via dmidecode if a machine is 32- or 64-bit
understand you.
Say I burn a DVD with the debian bootable iso (the live DVD) for
amd64, arm64 and 64-bit risc-v processors, will GRUB2 automatically
detect the architecture and pick the file?, or, as I suspect, you will
have to cook some configuration file?
Now explain, how grub compiled for rsic-v
ou you create such an ISO image for UEFI boot only. It
> must contain an EFI partition with EFI images for each firmware
> architecture : bootarm64.efi (built for ARM64), bootx64.efi
(built for
> AMD64/x86_64) and bootriscv64.efi (built for RISC-V64). The UEFI
> fi
ingle kernel flavour for the amd64 architecture,
and two flavours for i386: 686 (without PAE) and 686-pae. So this script
should do the trick:
if [ $grub_cpu = x86_64 ]; then
set arch=amd64
elif [ $grub_cpu = i386 ]; then
if cpuid -l ; then
set arch=amd64
On 17.12.2023 23:50, Pascal Hambourg wrote:
...
Note 2: there have been a few lightweight PC with 32-bit UEFI firmware
and 64-bit x86 CPU around. To boot on these you need to install an x86
32-bit EFI image as bootia32.efi. It can boot i386 and amd64 kernels.
...
if [ $grub_cpu = x86_64
El 17/12/23 a les 16:56, Andrei Borzenkov ha escrit:
On 17.12.2023 18:00, Narcis Garcia wrote:
What about selecting between vmlinuz-...-amd64 and vmlinuz-...-i386 on
non EFI firmware?
If you describe what condition you are going to use to decide which
kernel to load someone may have
ally understand you.
Say I burn a DVD with the debian bootable iso (the live DVD) for
amd64, arm64 and 64-bit risc-v processors, will GRUB2 automatically
detect the architecture and pick the file?, or, as I suspect, you will
have to cook some configuration file?
Any examples or leading information
>
> > Debian does not provide any such multi-arch ISO image. Until
> bookworm it
> > provided a amd64+i386 multi-arch image which was able to boot
> with PC
> > BIOS (with ISOLinux, 32-bit x86 UEFI and 64-bit x86 UEFI
On 17.12.2023 18:00, Narcis Garcia wrote:
What about selecting between vmlinuz-...-amd64 and vmlinuz-...-i386 on
non EFI firmware?
If you describe what condition you are going to use to decide which
kernel to load someone may have an idea how to implement it in grub.
grub itself just
h EFI images for each firmware
> architecture : bootarm64.efi (built for ARM64), bootx64.efi (built for
> AMD64/x86_64) and bootriscv64.efi (built for RISC-V64). The UEFI
> firmware will seek the matching EFI image, and the GRUB image will
> report the architecture in $grub_cpu and $grub_plat
On 17/12/2023 at 17:24, Albretch Mueller wrote:
On 12/17/23, Pascal Hambourg wrote:
Let's assume you you create such an ISO image for UEFI boot only. It
must contain an EFI partition with EFI images for each firmware
architecture : bootarm64.efi (built for ARM64), bootx64.efi (built for
AMD64
d 64-bit x86 CPU around. To boot on these you need to install an x86
> >> 32-bit EFI image as bootia32.efi. It can boot i386 and amd64 kernels.
> >>
> > ...
> >>
> >> if [ $grub_cpu = x86_64 ]; then
> >> # instructions to boot with am
and amd64 kernels.
...
if [ $grub_cpu = x86_64 ]; then
# instructions to boot with amd64 kernel
elif [ $grub_cpu = i386 ]; then
# instructions to boot with i386 kernel
This obviously will not work for such systems as you mentioned earlier.
64-bit CPUs can run 32-bit kernels, so
On Mon, Dec 18, 2023 at 12:22 PM Narcis Garcia wrote:
>
> El 17/12/23 a les 16:56, Andrei Borzenkov ha escrit:
> > On 17.12.2023 18:00, Narcis Garcia wrote:
> >>
> >> What about selecting between vmlinuz-...-amd64 and vmlinuz-...-i386 on
> >> non EFI firm
finish anyway. At that point, I think Grub was installed into the MBR,
but indeed, there was no entry for Linux.
Sometime during this installation I realized that this laptop used the
AMD64 architecture, which is presumably why no kernel was found from the
x86 installer. This time, I downloaded
finish anyway. At that point, I think Grub was installed into the MBR,
but indeed, there was no entry for Linux.
Sometime during this installation I realized that this laptop used the
AMD64 architecture, which is presumably why no kernel was found from the
x86 installer. This time, I downloaded
Hello there --
I have a Debian squeeze workstation which uses grub2 as its bootloader. The
system has 2 hard drives: the root partition is a software RAID-1 array
configured with mdadm; the boot partition is non-RAID (ext3). It also has a
DVD drive. The underlying architecture is AMD64
On 17.12.2023 19:24, Albretch Mueller wrote:
On 12/17/23, Andrei Borzenkov wrote:
Now explain, how grub compiled for rsic-v is going to run on amd64 to
decide anything.
This is not what I have in mind. What I mean is that as part of the
sequence the boot process goes through, GRUB2 should
to be version 1.98+20100 in testing, so it should work:
yun:~# apt-cache show grub2
Package: grub2
Priority: extra
Section: admin
Installed-Size: 344
Maintainer: GRUB Maintainers pkg-grub-de...@lists.alioth.debian.org
Architecture: amd64
Version: 1.98+20100804-4
Yet I've no good idea what to put
; the boot partition is non-RAID (ext3). It also has a
DVD drive. The underlying architecture is AMD64, the CPU and mobo are
Intel.
Ordinarily, booting via grub2 with the configuration above works fine.
However, when I connect an external hard drive via a back-panel USB port, I
can't boot
Le 13/12/2018 à 21:53, David Collier a écrit :
On Thu, Dec 13, 2018 at 11:52 AM Pascal Hambourg
wrote:
Le 13/12/2018 à 07:49, David Collier a écrit :
You must install GRUB EFI for the architecture matching your UEFI
firmware (32 or 64 bits, most likely 64 bits - NOT the CPU
architecture
ot used to
identify the root or swap device.
Here is DMESG for this boot of this machine with Debian 9.5 SD.
It is a little long. I hope that is OK.
[0.00] Linux version 4.9.0-7-amd64 (debian-ker...@lists.debian.org)
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian
4.9.1
27 matches
Mail list logo
