do a full powercycle.
I just happened to have a cheap USB3 that fails on attempt to boot when
it is plugged into the USB2 port of my old laptop.
A variation is: not the same hub as keyboard and mouse.
grub> echo $cmdpath
(hd2,gpt1)/EFI/debian
grub> echo $fw_path
### no
g the stick into another USB port (e.g. USB2 instead of
USB3 or vice versa)? Try full power cycle, not just reboot.
All the 10 USB ports on my T5820 are specified as USB 3.1 Gen 1. I always do a
full powercycle.
To figure out what happens in your case you may try the following commands:
gru
On Tue, Dec 17, 2024 at 03:32:03PM +0100, Thomas Schmitt wrote:
Roger Price wrote:
To check for bad USB stick, I downloaded debian-12.8.0-amd64-DVD-1.iso and
built a new 12.8 USB installation stick using command
dd if=debian-12.8.0-and64-DVD-1.iso of=/dev/sdj1 bs=4M && sync
The "1" in "/dev/s
small to take a DVD ISO.
Is this the same USB stick as the one with Debian 12.7.0 netinst ?
If so, did you run a partition editor to create a new partition 1 ?
> I tried booting this and got to a GRUB command line. This time ls -l
> reports that (hd0) has "no known filesystem detected&q
On 16/12/2024 15:45, Roger Price wrote:
So I re-inserted the USB installation stick to redo the installation.
This took me to the GRUB command line.
Am I right that you have internal SSD (SATA? NVME?) and a USB stick?
Have you tried to plug the stick into another USB port (e.g. USB2
instead
On Tue, 17 Dec 2024, Thomas Schmitt wrote:
Roger Price wrote:
I got the message error: file '/install.amd/vmlinux' not found
So perhaps:
grub> set root=(hd0)
grub> linux/install.amd/vmlinuz vga=788 --- quiet
grub> initrd /install.amd/gtk/initrd.gz
grub> boot
Hi,
i proposed for booting from the now reluctant USB stick:
> > grub> linux/install.amd/vmlinuz vga=788 --- quiet
> > grub> initrd /install.amd/gtk/initrd.gz
> > grub> boot
Roger Price wrote:
> I got the message error: file '/install.amd/vmlinux'
On Mon, 16 Dec 2024, Thomas Schmitt wrote:
Does the USB stick yield the proper checksum when inspected on a running
GNU/Linux system ?
Will check.
grub> cat (hd0,msdos2)/efi/debian/grub.cfg
set prefix-($root)/boot/grub
I see "=" instead of "-" in this file when t
On Mon, 16 Dec 2024 09:45:59 +0100 (CET)
Roger Price wrote:
> But I did create a
> small FAT32 partition to be mounted on /boot/efi if one day I needed
> it.
Which option in the installer's partitioner did you use, one of the FAT
options, or the EFI one? The latter will create a partition with
On Mon, 16 Dec 2024 18:50:02 +
Joe wrote:
> So I gave up, and just installed bookworm clean. No bootable OS found.
> I'll cut it short: it wouldn't boot because a /boot/efi/EFI directory
> did not contain a Microsoft directory containing bootmgfw.efi.
> Previously, it had been happy to boot f
On 12/16/24 10:50, Joe wrote:
I would add that many modern computers are almost hardwired for
Windows. ...
So I gave up, and just installed bookworm clean. No bootable OS found.
I'll cut it short: it wouldn't boot because a /boot/efi/EFI directory
did not contain a Microsoft directory containing
On Mon, 16 Dec 2024 09:39:22 -0800
David Christensen wrote:
> On 12/16/24 00:45, Roger Price wrote:
> > I have a Dell T5820 workstation. I had already installed Debian 12
> > in a spare partition on a Transcend SSD dating from 2017 using a
> > USB memory stick. I left in place the existing Wind
On 12/16/24 00:45, Roger Price wrote:
I have a Dell T5820 workstation. I had already installed Debian 12 in a
spare partition on a Transcend SSD dating from 2017 using a USB memory
stick. I left in place the existing Windows SSD that came with the
workstation. All went well - a very smooth i
l test command does not
yield "IT MATCHES", then some change has happened to the ISO on the USB
stick. (You may check file debian-12.7.0-amd64-netinst.iso the same way
as /dev/sdc to check whether already the ISO image was altered.)
> grub> cat (hd0,msdos2)/efi/debian/grub.cfg
und."
So I re-inserted the USB installation stick to redo the installation. This took
me to the GRUB command line. I typed a few commands: (I have removed all
details of hd1, hd2... reported as No known filesystem detected, or Filesystem
cannot be accessed)
grub> ls -l
Device hd0:
On Sat 09 Nov 2024 at 17:03:53 (-0700), pe...@easthope.ca wrote:
> From: David Wright
> Date: Fri, 25 Oct 2024 21:12:21 -0500
> > So you need to boot into your bullseye system, and run
> > # grub-install /dev/sdX
> > where X is probably a, your first disk.
&g
The ThinkCentre has one blue and one black, as in the 2nd photo here.
https://en.wikipedia.org/wiki/USB#System_design
> * With the adapter labeled USB 2.0, why is plugging in USB 3 necessary
> to boot the external system?
From: David Wright
Date: Sun, 3 Nov 2024 22:43:19 -0600
Who knows
this list that USB3 connections cost more because (1) different
controller and (2) more wires to run and (3) signals to manage.
* With the adapter labeled USB 2.0, why is connection to a USB 3
socket necessary to boot the external system?
Perhaps grub only boots from USB3? I have no idea if th
peter composed on 2024-11-09 11:35 (UTC-0700):
> * Why does the ThinkCentre have differing USB sockets?
Monkey see, monkey do applies in the competitive field of motherboard
manufacturing. Most computers with 3.x USB have also 2.0 ports. 3.x has a
manufacturing cost that 1.x and 2.0 devices have
From: David Wright
Date: Fri, 25 Oct 2024 21:12:21 -0500
> So you need to boot into your bullseye system, and run
> # grub-install /dev/sdX
> where X is probably a, your first disk.
Done. Resulting menu here.
https://easthope.ca/GrubMenu1.jpg
For reference, this was the ear
nect a USB hub before dealing with the Void drive.
Noticed the USB socket where the Void drive was connected had a black
plastic contact carrier and another socket had a blue carrier. Blue is
USB 3. So plugged the USB adapter with the Void drive into the blue
socket. Voila; grub was able t
the blue socket. Voila; Grub was able to boot the Void system
reliably. Spent the better part of a day investigating when a USB plug
just needed moving. =8~/
In case anyone is interested, these topics remain.
* Why does the ThinkCentre have differing USB sockets?
* With the adapter labeled
e0n1 disk,
> or copying partitions nvme0n1p1, nvme0n1p2, etc, or just recursive
> copies of the files in each partition into new filesystems created
> on sda.
>
> That information might well yield the reason that the installation
> stick wouldn't boot correctly. After reading
sda.
That information might well yield the reason that the installation
stick wouldn't boot correctly. After reading Thomas's post about
which partition is which on the stick, I think that:
grub> set root=(hd0)
grub> linux install.amd/vmlinuz
grub> initrd install.amd/i
On Mon, Nov 4, 2024 at 12:17 PM Chris Green wrote:
>
> On Mon, Nov 04, 2024 at 08:31:41AM -0500, Felix Miata wrote:
> [...]
> > Is a BIOS update available?
> >
> Possibly, but I bet I'd need an MS-Windows system to do the update.
This situation sucks. My father has an Acer laptop like it -- the
I have found how to get it to install, I removed the other (SATA SSD)
disk drive. It now boots successfully, phew!
I've no idea why that second drive breaks things. I installed it when
I was still running xubuntu 24.04 and that OS could see the drive OK.
I actually copied the whole of my old (xu
I have found how to get it to install, I removed the other (SATA SSD)
disk drive. It now boots successfully, phew!
I've no idea why that second drive breaks things. I installed it when
I was still running xubuntu 24.04 and that OS could see the drive OK.
I actually copied the whole of my old (xu
d apple2 is because viewing
> gdisk debian-12.7.0-amd64-netinst.iso
> as a GPT partition table gives a listing with only partition 2.
debian-12.7.0-amd64-netinst.iso has three partition tables:
- A valid MBR ("msdos") partition table with unusual layout.
Partition 1 begin
Chris Green composed on 2024-11-04 14:49 (UTC):
> Felix Miata wrote:
>> You might try pre-partitioning the NVME in GPT mode with ESP partition
>> instead
>> of the current MBR mode.
You seem to have skipped addressing this directly. It appears from your Grub
shell
ls output
On Mon, Nov 04, 2024 at 11:19:50AM -0500, Stefan Monnier wrote:
> > If I boot from the USB stick (isohybrid image) in Legacy mode then it
> > all **appears** to work, installation completes, but then the system
> > won't boot.
>
> What kind of boot loader did you i
ntinues from my "Failed Debian 12 install..." thread earlier
> > > > today.
> > > >
> > > > I can't get the USB Installation stick to boot into the Debian
> > > > installation process when I load it in UEFI mode. If I boot the USB
>
> If I boot from the USB stick (isohybrid image) in Legacy mode then it
> all **appears** to work, installation completes, but then the system
> won't boot.
What kind of boot loader did you install? `grub-efi`, `grub-pc`,
something else?
Does your Debian install's boot fail
> today.
> > >
> > > I can't get the USB Installation stick to boot into the Debian
> > > installation process when I load it in UEFI mode. If I boot the USB
> > > stick in UEFI mode it just takes me to the grub prompt.
> >
> > It may help
k to boot into the Debian
> > installation process when I load it in UEFI mode. If I boot the USB
> > stick in UEFI mode it just takes me to the grub prompt.
>
> It may help to know whether that's a grub> prompt
> or a grub rescue> prompt. The latter takes a bi
t the USB
> stick in UEFI mode it just takes me to the grub prompt.
It may help to know whether that's a grub> prompt
or a grub rescue> prompt. The latter takes a bit more
work to recover from.
Whichever, does typing ls produce a listing of some sort?
Basically, you have to l
> - Always boot using UEFI.
> - Boot the install using legacy BIOS, then manually change the install
> to use grub-efi, then reboot into my EFI config to "activate" the
> right `.efi` installed into the EFI partition.
>
> I started with the first choice, and then a
the Debian
> > installation process when I load it in UEFI mode. If I boot the USB
> > stick in UEFI mode it just takes me to the grub prompt.
>
> > I suspect that this is why, when I boot from the USB stick in BIOS
> > compatibility mode the resulting installation doe
out that if the installation media is booted in "legacy BIOS"
mode, then it can't do an install that boots via UEFI.
IOW I had 3 choices:
- Always boot using legacy BIOS mode.
- Always boot using UEFI.
- Boot the install using legacy BIOS, then manually change the install
to use gr
gt; stick in UEFI mode it just takes me to the grub prompt.
> I suspect that this is why, when I boot from the USB stick in BIOS
> compatibility mode the resulting installation doesn't work.
> Any ideas what I need to do to get the USB stick to boot properly in
> USB mode?
This has
gt; stick in UEFI mode it just takes me to the grub prompt.
> I suspect that this is why, when I boot from the USB stick in BIOS
> compatibility mode the resulting installation doesn't work.
> Any ideas what I need to do to get the USB stick to boot properly in
> USB mode?
This has
connect a USB hub before dealing with the Void drive.
> Noticed the USB socket where the Void drive was connected had a black
> plastic contact carrier and another socket had a blue carrier. Blue is
> USB 3. Black isn't? So plugged the USB adapter with the Void drive
> into the b
This continues from my "Failed Debian 12 install..." thread earlier
today.
I can't get the USB Installation stick to boot into the Debian
installation process when I load it in UEFI mode. If I boot the USB
stick in UEFI mode it just takes me to the grub prompt.
I suspect that th
drive
> into the blue socket. Voila; Grub was able to boot the Void system
> reliably. Spent the better part of a day investigating when a USB plug
> just needed moving. =8~/
>
> In case anyone is interested, these topics remain.
>
> * Why does the ThinkCentre have dif
On 27/10/2024 21:56, David Wright wrote:
On Sat 26 Oct 2024 at 20:55:11 (-0700), pe...@easthope.ca wrote:
A Web search
found mention of grub command nativedisk which I added.
I don't know anything about nativedisk or the distinctions between
various types of driver.
[...]
nativ
socket where the Void drive was connected had a black
plastic contact carrier and another socket had a blue carrier. Blue is
USB 3. Black isn't? So plugged the USB adapter with the Void drive
into the blue socket. Voila; Grub was able to boot the Void system
reliably. Spent the better pa
On Thu, Oct 31, 2024 at 23:10:22 -0500, David Wright wrote:
> On Mon 28 Oct 2024 at 07:08:12 (-0400), Greg Wooledge wrote:
> > On Sun, Oct 27, 2024 at 22:42:15 -0500, David Wright wrote:
> > > type
> > > set -x
> > > before you run os-prober and
> > > set +x
> > > afterwards, and track what it
On Mon 28 Oct 2024 at 07:08:12 (-0400), Greg Wooledge wrote:
> On Sun, Oct 27, 2024 at 22:42:15 -0500, David Wright wrote:
> > type
> > set -x
> > before you run os-prober and
> > set +x
> > afterwards, and track what it does.
>
> os-prober is a script, so that won't work as written. You'd ei
] || ls
"$dir"/usr/lib*/ld*.so*) >/dev/null 2>/dev/null; then
The comments preceding it tell you why this test comes about last,
and what the difficulties are. I would hazard a guess that Void
linux fails this test.
> Where is "set"?
It's a shell built-in. Greg&
a lazy way:
> type
> set -x
> before you run os-prober and
> set +x
> afterwards, and track what it does. You'd probably want to
> capture the output as it could be voluminous; it looks for
> linux systems just about last.
You've lost me there. Which first test? W
On Sun, Oct 27, 2024 at 22:42:15 -0500, David Wright wrote:
> type
> set -x
> before you run os-prober and
> set +x
> afterwards, and track what it does.
os-prober is a script, so that won't work as written. You'd either
need to modify os-prober (change the second line from "set -e" to
"set -
On Sun 27 Oct 2024 at 11:26:12 (-0700), pe...@easthope.ca wrote:
> A search of "os-prober security" finds several pages. os-prober is
> disabled by default in Archlinux and other respected distributions.
>
> For interest, I enabled os-prober again in /etc/default/grub a
From: David Wright
Date: Sun, 27 Oct 2024 09:56:45 -0500
> That earlier installation is presumably the bookworm that
> wrote (hd0,gpt2)/boot/grub/grub.cfg with the Grub deb12u1,
> which I pointed out in my first post, but wasn't confirmed
> by your follow-up.
Yes, the
On Sat 26 Oct 2024 at 20:55:11 (-0700), pe...@easthope.ca wrote:
> Tim & all,
>
> From: Tim Woodall
> Date: Fri, 25 Oct 2024 22:35:50 +0100 (BST)
> > It's possibly not reading the grub.cfg you think it is reading. I've
> > hit this problem before
Tim & all,
From: Tim Woodall
Date: Fri, 25 Oct 2024 22:35:50 +0100 (BST)
> It's possibly not reading the grub.cfg you think it is reading. I've
> hit this problem before - IIRC grub uses the grub.cfg from the *first*
> place it finds one - this can even be a par
On Fri 25 Oct 2024 at 23:50:05 (-0400), Felix Miata wrote:
> David Wright composed on 2024-10-25 14:08 (UTC-0500):
> > On Fri 25 Oct 2024 at 13:51:06 (-0400), Felix Miata wrote:
>
> >> Manual editing of /boot/grub/grub.cfg does not persist. Every kernel
> >> addit
David Wright composed on 2024-10-25 14:08 (UTC-0500):
> On Fri 25 Oct 2024 at 13:51:06 (-0400), Felix Miata wrote:
>> Manual editing of /boot/grub/grub.cfg does not persist. Every kernel
>> addition or
>> removal causes its regeneration anew based upon the content of
On Fri 25 Oct 2024 at 13:30:25 (-0700), pe...@easthope.ca wrote:
> From: David Wright
> Date: Fri, 25 Oct 2024 14:13:50 -0500
> > You took out the tail!
>
> Appears we're at crossed purposes. You catted /etc/grub.d/40_custom.
> I posted /boot/grub/grub.cfg.
reful
monkeying.
Thanks, ... P.
It's possibly not reading the grub.cfg you think it is reading. I've
hit this problem before - IIRC grub uses the grub.cfg from the *first*
place it finds one - this can even be a partition (or in my case a LV)
t
ntries 07_custom refers to are not duplicated by
> 41_custom
> after every time whatever Grub package providing it is updated.
Do you mean that the previously inserted copies of custom.cfg are
preserved, and a new copy inserted, each time grub-mkconfig runs?
If that's not the case,
From: David Wright
Date: Fri, 25 Oct 2024 14:13:50 -0500
> You took out the tail!
Appears we're at crossed purposes. You catted /etc/grub.d/40_custom.
I posted /boot/grub/grub.cfg.
My 40_custom has the "exec tail" line as you posted and produces a
stanza in /
d/ I copy 41_custom to 07_custom. Then I empty 41_custom and
>> make it
>> immutable so that the entries 07_custom refers to are not duplicated by
>> 41_custom
>> after every time whatever Grub package providing it is updated.
> Do you mean that the previously inserted co
On Fri 25 Oct 2024 at 11:33:37 (-0700), pe...@easthope.ca wrote:
> The /boot/grub/grub.cfg created by update-grub2 is at
> https://easthope.ca/grub.cfg . My 40_custom stanza is there but not
> in the boot menu. If someone can spot an error, good, thanks.
You took out the tail!
It sh
t. Booting with BIOS rather
than EFI.
Incidentally, the Void Linux system on (hd1,gpt6) boots when directed
from the BIOS. The problem is to boot it through Grub on (hd0)
without switching in the BIOS.
If my /etc/grub.d/40_custom is problematic for update-grub2 an error
message from update-g
~# cat /etc/debian*
> 11.11
>
> > The system has booted into a bookworm Grub (deb12u1).
>
> I don't understand.
Booting is a multistage process. By means of an MBR or EFI, you
reached the Grub menu, which you photographed. At the top, it says:
GNU GRUB version 2.06-13+deb12u
n /etc/grub.d/ I copy 41_custom to 07_custom. Then I empty 41_custom and make
it
immutable so that the entries 07_custom refers to are not duplicated by
41_custom
after every time whatever Grub package providing it is updated.
Manual editing of /boot/grub/grub.cfg does not persist. Every kernel
From: Felix Miata
Date: Thu, 24 Oct 2024 16:55:37 -0400
> Instead of 40_custom, I use 41_custom, but copied to 07_custom.
You have two copies of the custom configuration. One in
/etc/grub.d/07_custom and one in /etc/grub.d/41_custom. Correct?
Are both entries in the menu? Only the on
On Fri, Oct 25, 2024 at 08:26:21 -0700, pe...@easthope.ca wrote:
> A new-to-me detail is hd0 having FAT and hd1 having GPT.
> According to this, OK for Grub2.
> https://www.gnu.org/software/grub/manual/grub/grub.html#BIOS-installation
FAT is a type of file system. The disk partition
, so hd1 may accidentally
become hd2. Grub installer may add a command to rely on filesystem UUID,
not on drive numbering:
search.fs_uuid 12345678-90ab-cdef-1234-567890abcdef root
or a variant with a hint where this partition is expected
search.fs_uuid 12345678-90ab-cdef-1234-567890abcdef root
logy.
>
> > And a 14-month old bullseye system on hd0, which is currently
> > running?
>
> Yes.
> root@imager:~# cat /etc/debian*
> 11.11
>
> > The system has booted into a bookworm Grub (deb12u1).
>
> I don't understand. To my understanding,
Yes.
root@imager:~# cat /etc/debian*
11.11
> The system has booted into a bookworm Grub (deb12u1).
I don't understand. To my understanding, booted into Debian 11 on hd0.
A new-to-me detail is hd0 having FAT and hd1 having GPT.
According to this, OK for Grub2.
https://www.gnu.org/software/gr
ies from /boot/grub/custom.cfg at runtime, placing them ahead
of
its own entries. Any changes you make to /boot/grub/custom.cfg are read without
any additional fuss next boot and beyond, until you change it again.
--
Evolution as taught in public schools is, like religion,
based on faith
On Thu 24 Oct 2024 at 12:52:59 (-0700), pe...@easthope.ca wrote:
> root@imager:~# grep PROBER /etc/default/grub
> GRUB_DISABLE_OS_PROBER=true
>
> Also,
>
> root@imager:~# cat /etc/grub.d/40*
> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add c
Hi,
root@imager:~# grep PROBER /etc/default/grub
GRUB_DISABLE_OS_PROBER=true
Also,
root@imager:~# cat /etc/grub.d/40*
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to
On Sun, 20 Oct 2024 23:09:40 +0200
paolo.dupu...@gmail.com wrote:
> Hello,
>
> I am having difficulties installing Debian 12, specifically with the
> GRUB bootloader. After installation, my system is unable to boot
> properly, and I suspect there might be an issue with the GRUB
Hello,
I am having difficulties installing Debian 12, specifically with the GRUB
bootloader. After installation, my system is unable to boot properly, and I
suspect there might be an issue with the GRUB configuration. I have tried
reinstalling GRUB, but the problem persists.
Could someone
On Thu, Sep 12, 2024 at 01:21:12AM +0200, Florent Rougon wrote:
> Hi,
>
> Le 11/09/2024, Andy Smith a écrit:
>
> > Since booting from sdb wasn't working in any case, I thought I'd
> > experiment a bit. I copied the first 446 bytes of sda to sdb. This
> >
On Tuesday 10 September 2024 08:39:59 pm Andy Smith wrote:
> This does leave me wondering however, if the boot code in the mBR of
> sdb is now set to believe that this is "the second drive", I suppose
> (hd1) in grub terms? With the implication that should sda fail or be
>
Hi,
Le 11/09/2024, Andy Smith a écrit:
> Since booting from sdb wasn't working in any case, I thought I'd
> experiment a bit. I copied the first 446 bytes of sda to sdb. This
> made matters worse! Instead of a "grub> " prompt, I just got a blank
> screen.
&
Hi,
On Wed, Sep 11, 2024 at 12:45:46AM +0200, Florent Rougon wrote:
> The partition table indeed starts at offset 446 (decimal), however I'd
> still rather run grub-install or “dpkg-reconfigure grub-pc” than copy
> the first 446 bytes from one drive to another drive. The reason is
27;d
still rather run grub-install or “dpkg-reconfigure grub-pc” than copy
the first 446 bytes from one drive to another drive. The reason is that,
AFAIUI, what GRUB writes in this area when installed is likely to
contain disc-specific info. More specifically, according to [1]:
There isn't roo
primary partitions of each drive are among
> these bytes.
Good point. I understand the bootloader is actually the first 446
bytes so maybe I should only be looking at these.
https://unix.stackexchange.com/a/254668/36243
> I'd rather 'dpkg-reconfigure grub-pc' where you can
ach drive are among
these bytes.
> I do not particularly want to run grub-install, as the MBR of sdb is
> known good at the moment. Perhaps though I could run:
>
> $ sudo grub-install /dev/sda
I believe so, although by habit I'd rather 'dpkg-reconfigure grub-pc'
where you
On Mon, Sep 09, 2024 at 07:59:58PM +, Andy Smith wrote:
> I was kind of hoping that there would be something I could run which
> would say "yes, this MBR has grub v and is set to find its
> grub.cfg on (hdX)", then I might be able to see some difference in
> what the
Hi,
I've come into possession of a machine running Debian 10 with two
drives in it; sda and sdb. These have been labelled with a DOS MBR
and partitioned. The first partition starts at sector 2048 of both
drives (512 byte sectors). It appears that GRUB has been installed
on both sda an
Hi,
Andy Smith wrote:
> Is there some advantage in me editing one of the files in the EFI
> partition as opposed to just putting the grub serial directives in
> /boot/grub/grub.cfg of the ISO?
None that i know of.
Editing /efi/debian/grub.cfg of the EFI partition filesystem would ju
Hi,
On Mon, Jul 29, 2024 at 12:42:05PM +0200, Thomas Schmitt wrote:
> Andy Smith wrote:
> > Should I just edit that into $iso_root/boot/grub/grub.cfg and repack
> > the ISO?
>
> If altering the EFI partition is not viable, then surely: Yes.
Is there some advantage in me edi
Hi,
Andy Smith wrote:
> Currently when I add the Debian 12 netinst ISO as a virtual media it
> EFI boots grub, not isolinux,
That's because Debian ISOs advertise a EFI System Partition with GRUB
initial boot equipment:
$ xorriso -indev debian-12.2.0-amd64-
ement controller that adds virtual media from ISOs, but I would
still like to see that install over the IPMI serial.
Currently when I add the Debian 12 netinst ISO as a virtual media it
EFI boots grub, not isolinux, so the output of grub only goes to the
graphical terminal (a web interface of the manag
Le 28/05/2024, Harald Dunkel a écrit:
> Full thread is on debian-boot mailing list.
I've read it now, thanks for the info, Harald!
Regards
--
Florent
Full thread is on debian-boot mailing list.
Hi,
Le 24/05/2024, Harald Dunkel a écrit:
> if I migrate from grub-pc to grub-uefi, then grub-pc.postrm
> removes /etc/default/grub on the final purge.
I confirm the behavior, have been bitten by this. IMHO, it is a nasty
bug: suppose your rely on your kernel command line to disable, sa
Hi folks,
if I migrate from grub-pc to grub-uefi, then grub-pc.postrm
removes /etc/default/grub on the final purge.
grub2 doesn't provide much information in its man pages, but
AFAICT /etc/default/grub is still processed for UEFI, so why
is it deleted?
Regards
Harri
On 01/05/2024 10:45, Richard wrote:
I'd like to increase the font size in Grub (v2.12, at least I think
that's the better alternative to just lowering the resolution) and
opted to just use a custom font as there seems to be an OTF version of
"GNU Unifont", though it s
I'd like to increase the font size in Grub (v2.12, at least I think that's
the better alternative to just lowering the resolution) and opted to just
use a custom font as there seems to be an OTF version of "GNU Unifont",
though it seems to be jagged by design, but I'
the output of any of
> >>
> >> # blkid
> >
> > Here I have them shown as UUID by blkid
> >
> > # grep root /boot/grub/grub.cfg
> > ...
> > search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2
> > --hint-efi=hd1,gpt2 --hint-bareme
> On 13 Mar 2024, at 19:00, Gareth Evans wrote:
>
> Hi Michael,
I'm sorry - Michel
On Wed 13/03/2024 at 12:50, Michel Verdier wrote:
> On 2024-03-13, Gareth Evans wrote:
>
>> That suggests perhaps something to do with an FS UUID, but it doesn't seem
>> to appear in the output of any of
>>
>> # blkid
>
> Here I have them shown as
On 2024-03-13, Gareth Evans wrote:
> That suggests perhaps something to do with an FS UUID, but it doesn't seem to
> appear in the output of any of
>
> # blkid
Here I have them shown as UUID by blkid
# grep root /boot/grub/grub.cfg
...
search --no-floppy --fs-uuid --set=roo
Does anyone know what the 16-digit hex number (truncated below to 9cbe...)
refers to in /boot/grub/grub.cfg, where it makes several appearances?
# grep 9cbe -A2 -B2 /boot/grub/grub.cfg
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
>On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>>> where you get the blank screen GRUB?
>>
>> Yeah, I probably should have opened with that. Sorry:
>>
>> ```
&
1 - 100 of 1575 matches
Mail list logo
