On 05/02/2024 17:40, Dmitry wrote:
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during
Linux installation.
That advice may be standard for distributions that do not provide signed
shim and grub. Likely it is applicable for Arch
On Mon, 2024-02-05 at 17:40 +0700, Dmitry wrote:
>
> But secure boot is usually turned off. It is a standard advice during
> Linux
> installation.
>
Will probably be increasingly common though, I've got a Microsoft
Surface Laptop that works fine with Debian, but if you switch off
secure boot,
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during Linux
installation.
sudo -i
Thank you!
I am unsure what UUID you mean.
At Manjaro:
grubx64.efi is at the sdb1 - EFI vfat /dev/sdb1
grub.cfg is at the sdb2 - crypto_LUKS /dev/sdb2
grubx64.efi contains data UUID=""a8...b7" of /dev/sdb2 which is
TYPE="crypto_LUKS".
`blkid` output:
/dev/sdb2: UUID="a8...b7"
On 03/02/2024 22:32, Dmitry wrote:
2. sudo bash
sudo -i
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
I am unsure what UUID you mean.
Summary: GRUB installation not only involves configuration of text
files, but
also it
Tim Woodall composed on 2024-02-03 21:25 (UTC):
> Max Nikulin wrote:
>> It seems secure boot is disabled in your case, so I am wondering why you do
>> not boot xen.efi directly.
> Because the NVRAM is extremely tempremental.
Not in my experience. I recognized long ago that WRT non-removable
On Sat, 3 Feb 2024, Max Nikulin wrote:
It seems secure boot is disabled in your case, so I am wondering why you do
not boot xen.efi directly.
Because the NVRAM is extremely tempremental. Most updates fail, or
worse, corrupt it to the point it's hard to get anything to boot.
Additionally,
Main question is resolved.
GRUB knows how to reach grub.cfg because grubx64.efi binary has the UUID and
path to grub configurations.
1. sudo blkid;
2. sudo bash
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
Summary: GRUB
On 03/02/2024 02:15, Tim Woodall wrote:
$ cat /boot/efi/EFI/XEN/xen.cfg
[...]
I'd be interested if there's a way to tell grubx64.efi to look for a
particular partition UUID.
An example of such grub.cfg from EFI/debian has been posted already in
this thread
On 03/02/2024 02:51, Thomas Schmitt wrote:
Max Nikulin wrote:
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi)
to the ESP partition on the USB stick.
The /EFI/boot directory of a bootable Debian ISO usually does not contain
the full GRUB equipment for EFI. Important parts of
On 02/02/24 at 15:12, Dmitry wrote:
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
Nope, maybe you gave a quick read, the release notes of the current
release ยน are exhaustive. If
Hi,
Dmitry wrote:
> Yep. `dd` copy partitions table. Amazing.
Not so amazing after you realize that a partition table is just data on
the storage medium and not some special property of the storage device.
dd copies data. If these data contain a partition table and get copied to
the right place
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
$ cat /boot/efi/EFI/XEN/xen.cfg
[global]
default=debian
[debian]
options=console=vga smt=true
kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
ramdisk=initrd.img
menuentry "Xen EFI NVME" {
On Sat, Feb 03, 2024 at 01:17:05AM +0700, Dmitry wrote:
> > Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
> ESP partition on the USB stick.
>
> As I understand right now `dd` command applied to a device will copy all
> information including partitions table. Thus:
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Yep. `dd` copy partitions table. Amazing.
```
dd will simply recreate the old partition scheme, as it is a bitwise copy &
applies no 'intelligence' to the operation.
```
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
As I understand right now `dd` command applied to a device will copy all
information including partitions table. Thus:
dd if=debian-xx.iso of=/dev/sdb bs=4M status=progress; sync
Would
On Fri 02 Feb 2024 at 21:12:30 (+0700), Dmitry wrote:
> Going to read carefully.
>
> https://www.debian.org/releases/buster/amd64/ch04s03.en.html
>
> Interesting that Buster has more documentation than current release.
It appears the balance has now been spun off into a wiki page, at
On 02/02/2024 21:06, Dmitry wrote:
Need additional research what to do with a FlashStick with several
partitions to make a LiveCD from it.
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
> Do you want to install the OS on it?
Eventually no, I do not want OS on the Flash Stick.
The Flash Stick is only a testing place. I want OS at the SSD.
Now I am wondering how to prepare the Flash Stick to write LiveImage on it.
Because I already created a GPT table on that Flash and use
Am 02.02.2024 schrieb Dmitry :
> I want OS at the SSD.
Then the ESP should be on that SSD too.
Max Nikulin schrieb:
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot without modification of boot entries in NVRAM.
Yes, UEFI can (and must be able) to boot from a device without a boot
entry in the UEFI.
On 02/02/2024 01:46, Dmitry wrote:
3. Now I want to boot using that Flash.
1. ESP is a partition that stores GRUB Binary. /boot/EFI/Name/grub64.eif
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
> $ cat /boot/efi/EFI/XEN/xen.cfg
> [global]
> default=debian
>
> [debian]
> options=console=vga smt=true
> kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
> ramdisk=initrd.img
>
>
> menuentry "Xen EFI NVME" {
> insmod part_gpt
>
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat
On Fri, 2 Feb 2024, Dmitry wrote:
Hi Tim. The community is so kind.
So.
I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks like a caught
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
> 2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat /boot/efi/EFI/debian/grub.cfg
search.fs_uuid 5b8b669d-xyz root
Hi Tim. The community is so kind.
So.
> I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks like a caught the thread.
1. ESP is a partition
Am 02.02.2024 um 00:09:56 Uhr schrieb Dmitry:
> I made experiments with a FlashDrive, and create GPT there,
> if I want to use standard Debian Image how I should partition that
> flash drive (MBR, GPT)?
Do you want to install the OS on it?
For the partition table, I recommend GPT.
Do you want
Huge thanks.
Your message starts the understanding.
And as well give a plenty of texts to read.
> EFI/debian/grub.cfg on the EFI System Partition contains filesystem UUID
where grub files reside.
All parts are simple But when compounding them together become messy.
In the Manjaro:
On Thu, 1 Feb 2024, Dmitry wrote:
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to
> Why don't you use the normal setup?
Spend a lot of time on research, it would be nice to finish.
I made experiments with a FlashDrive, and create GPT there,
if I want to use standard Debian Image how I should partition that
flash drive (MBR, GPT)?
> Do you need a special configuration here
On 01/02/2024 22:54, Marco Moock wrote:
Am 01.02.2024 schrieb Dmitry:
Use gdisk for that.
You can create an EFI partition there.
Choose Type EFI (EF00), 100MB.
Format it with FAT32.
550MiB is recommended in "Preparing your ESP"
http://www.rodsbooks.com/linux-uefi/#installing
see also
Am 01.02.2024 schrieb Dmitry :
Why don't you use the normal setup?
It does many tasks for you.
> After:
> 1. Creating GPT table and GPT partition with fdisk.
Use gdisk for that.
You can create an EFI partition there.
Choose Type EFI (EF00), 100MB.
Format it with FAT32.
> And at the point two
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to start booting.
And at the point
35 matches
Mail list logo
