Re: Grub menu entry for a system on a second drive.

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. > > Done. Resulting menu here

Re: [solved, more] Re: Grub menu entry for a system on a second drive.

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

Re: [solved] Re: Grub menu entry for a system on a second drive.

On 11/9/24 13:04, pe...@easthope.ca wrote: A new factor in the original problem. Therefore a new thread. I can respond to the original thread when there's time. In case anyone is interested, these topics remain. * Why does the ThinkCentre have differing USB sockets? I've read on this list th

Re: Grub menu entry for a system on a second drive.

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 earlier menu.

Re: [solved] Re: Grub menu entry for a system on a second drive.

A new factor in the original problem. Therefore a new thread. I can reply to the original thread later. From: pe...@easthope.ca Date: 27 Oct 2024 11:26:12 -0700 > Rather than spend more time investigating, will put the HDD in the > target machine and work there. Happened to connect a

Re: [solved] Re: Grub menu entry for a system on a second drive.

A new factor in the original problem. Therefore a new thread. I can respond to the original thread when there's time. From: pe...@easthope.ca Date: 27 Oct 2024 11:26:12 -0700 > Rather than spend more time investigating, will put the HDD in the > target machine and work there. Happened

Re: [solved, more] Re: Grub menu entry for a system on a second drive.

On Nov 02, 2024, pe...@easthope.ca wrote: > From: pe...@easthope.ca > Date: 27 Oct 2024 11:26:12 -0700 > > Rather than spend more time investigating, will put the HDD in the > > target machine and work there. Remove some of the complications. > > Happened to connect a USB hub before deal

Re: [solved, more] Re: Grub menu entry for a system on a second drive.

On Sat 02 Nov 2024 at 07:46:33 (-0700), pe...@easthope.ca wrote: > From: pe...@easthope.ca > Date: 27 Oct 2024 11:26:12 -0700 > > Rather than spend more time investigating, will put the HDD in the > > target machine and work there. Remove some of the complications. > > Happened to connec

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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. [...] nativedisk se

Re: [solved, more] Re: Grub menu entry for a system on a second drive.

From: pe...@easthope.ca Date: 27 Oct 2024 11:26:12 -0700 > Rather than spend more time investigating, will put the HDD in the > target machine and work there. Remove some of the complications. Happened to connect a USB hub before dealing with the Void drive. Noticed the USB socket wher

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

On Mon 28 Oct 2024 at 09:07:42 (-0700), pe...@easthope.ca wrote: > From: David Wright > Date: Sun, 27 Oct 2024 22:42:15 -0500 > > Well, it could be because Void apparently isn't a glibc OS. > > Thanks. Haven't thought about that. > > > You could check /usr/lib/os-probes/mounted/90linux-

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

From: David Wright Date: Sun, 27 Oct 2024 22:42:15 -0500 > Well, it could be because Void apparently isn't a glibc OS. Thanks. Haven't thought about that. > You could check /usr/lib/os-probes/mounted/90linux-distro > to see whether the first test would succeed. Or a lazy way: > type >

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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 -

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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 and ran > grub-install /de

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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 multiple details hav

Re: [solved, partly] Re: Grub menu entry for a system on a second drive.

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 - IIRC grub uses the grub.cfg from the *f

[solved, partly] Re: Grub menu entry for a system on a second drive.

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 partition (or in my case a LV

Re: Grub menu entry for a system on a second drive.

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 > >> addition or > >> removal causes its re

Re: Grub menu entry for a system on a second drive.

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 >> /etc/default/grub >> and

Re: Grub menu entry for a system on a second drive.

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. > > My 40_custom has the "ex

Re: Grub menu entry for a system on a second drive.

On Fri 25 Oct 2024 at 13:51:06 (-0400), Felix Miata wrote: > My actual custom stanzas are in /boot/grub2/custom.cfg, because I use only one > bootloader per PC, no matter how many installations it contains, which > averages in > excess of 20, and I use whatever version of Grub2 that Tumbleweed pro

Re: Grub menu entry for a system on a second drive.

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 /boot/grub/grub.cfg appeari

Re: Grub menu entry for a system on a second drive.

David Wright composed on 2024-10-25 14:08 (UTC-0500): > On Fri 25 Oct 2024 at 13:51:06 (-0400), Felix Miata wrote: >> My actual custom stanzas are in /boot/grub2/custom.cfg, because I use only >> one >> bootloader per PC, no matter how many installations it contains, which >> averages in >> exc

Re: Grub menu entry for a system on a second drive.

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 should look

Re: Grub menu entry for a system on a second drive.

Joe & all, From: Joe Date: Fri, 25 Oct 2024 17:06:21 +0100 > Modern drives use GPT partitioning, and modern computers generally have > UEFI firmware rather than BIOS. The machine here is ThinkCentre 1S3237C13MJTVBGW. Older than machines commonplace now. It has UEFI but I couldn't

Re: Grub menu entry for a system on a second drive.

On Fri 25 Oct 2024 at 08:26:21 (-0700), pe...@easthope.ca wrote: > From: David Wright > Date: Thu, 24 Oct 2024 22:22:19 -0500 > > So you've got a stable/testing/unstable system on hd1? > > hd1 has Void Linux. They don't use the stable/testing/unstable terminology. I'm looking at your sy

Re: Grub menu entry for a system on a second drive.

peter composed on 2024-10-25 09:23 (UTC-0700): > 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 one from 07_custom? > The immediate puzzle here is the custom menu entry in >

Re: Grub menu entry for a system on a second drive.

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 partitioning table type

Re: Grub menu entry for a system on a second drive.

On 25/10/2024 23:06, Joe wrote: On 25 Oct 2024 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. [...] Modern drives use GPT partitioning, and modern computers generally have UEFI firmware rather than BIOS. The EF

Re: Grub menu entry for a system on a second drive.

On 25 Oct 2024 08:26:21 -0700 pe...@easthope.ca wrote: > From: David Wright > Date: Thu, 24 Oct 2024 22:22:19 -0500 > > So you've got a stable/testing/unstable system on hd1? > > hd1 has Void Linux. They don't use the stable/testing/unstable > terminology. > > > And a 14-month old bu

Re: Grub menu entry for a system on a second drive.

From: David Wright Date: Thu, 24 Oct 2024 22:22:19 -0500 > So you've got a stable/testing/unstable system on hd1? hd1 has Void Linux. They don't use the stable/testing/unstable terminology. > And a 14-month old bullseye system on hd0, which is currently running? Yes. root@imager:~# cat

Re: Grub menu entry for a system on a second drive.

pe...@easthope.ca composed on 2024-10-24 12:52 (UTC-0700): > So far, good, but when booting the Void entry is absent. > https://easthope.ca/GrubMenu.jpg > Ideas? Why I don't know, but: Instead of 40_custom, I use 41_custom, but copied to 07_custom. Grub.cfg then reads custom entries from /boot/

Re: Grub menu entry for a system on a second drive.

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 custom menu entries. Simply ty

Re: grub requirements for fonts

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 seems to be jagged by desig

Re: Re: GRUB lost graphical terminal mode

>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: >>  >> ``` >> # If you change this file, run 'update-grub' af

Re: GRUB lost graphical terminal mode

On Tue, 20 Feb 2024 08:04:47 + Michael Kjörling <2695bd53d...@ewoof.net> wrote: > 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

Re: GRUB lost graphical terminal mode

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: > > ``` > # If you change this file, run 'update-grub' afterwards

Re: Re: GRUB lost graphical terminal mode

> On 18 Feb 2024 21:28 +0100, from borde...@tutanota.com (Borden): > > what the default is when neither of those are set (which doesn't > > work). Is this another "undocumented feature" of GRUB? > > Would you be willing to post your /boot/grub/grub.cfg for a setup where you > get the blank screen

Re: GRUB lost graphical terminal mode

On 18 Feb 2024 21:28 +0100, from borde...@tutanota.com (Borden): > what the default is when neither of those are set (which doesn't > work). Is this another "undocumented feature" of GRUB? Would you be willing to post your /boot/grub/grub.cfg for a setup where you get the blank screen GRUB? -- M

Re: Re: GRUB lost graphical terminal mode

> Or perhaps you have all colors set to blank. > Try add something like > GRUB_COLOR_NORMAL="light-blue/black" > GRUB_COLOR_HIGHLIGHT="light-cyan/blue" Unfortunately, that didn't work. Still a blank screen. I'm curious that if GRUB_TERMINAL=gfxterm works and GRUB_TERMINAL=console works, what the

Re: GRUB lost graphical terminal mode

On 2024-02-16, Borden wrote: > For a couple weeks now, I can't use graphical terminal in my GRUB > configuration. Setting `GRUB_TERMINAL=console` works fine. With that line > commented out, (thus using default settings), I get a blank screen on boot, 5 > second timeout, then normal boot. > > Curio

Re: GRUB lost graphical terminal mode

Thank you for the tip! So `GRUB_TERMINAL=gfxterm` works, `GRUB_TERMINAL=console` works, but whatever the default is supposed to be does not. Does this imply that "the platform's native terminal output" is broken?

Re: GRUB lost graphical terminal mode

On 16/02/2024 17:27, Borden wrote: For a couple weeks now, I can't use graphical terminal in my GRUB configuration. Setting `GRUB_TERMINAL=console` works fine. With that line commented out, (thus using default settings), I get a blank screen on boot, 5 second timeout, then normal boot. Curio

Re: grub-pc error when upgrading from buster to bullseye

On 2024-02-12 15:14, Greg Wooledge wrote: According to it uses debconf's database. That page includes instructions for viewing the device and changing it. I had just star

Re: grub-pc error when upgrading from buster to bullseye

On Mon, Feb 12, 2024 at 09:04:01PM +0100, Thomas Schmitt wrote: > Hi, > > John Boxall wrote: > > I am aware that the label and uuid (drive and partition) are replicated on > > the cloned drive, but I can't find the model number (in text format) stored > > anywhere on the drive. > > Maybe the grub

Re: grub-pc error when upgrading from buster to bullseye

Hi, John Boxall wrote: > I am aware that the label and uuid (drive and partition) are replicated on > the cloned drive, but I can't find the model number (in text format) stored > anywhere on the drive. Maybe the grub-pc package takes its configuration from a different drive which is attached to

Re: grub-pc error when upgrading from buster to bullseye

On 2024-02-12 09:34, Thomas Schmitt wrote: The disk/by-id file names are made up from hardware properties. I believe to see in the name at least: Manufacturer, Model, Serial Number. So you will have to find the configuration file which knows that /dev/disk/by-id address and change it either to

Re: grub-pc error when upgrading from buster to bullseye

Hi, John Boxall wrote: > Setting up grub-pc (2.06-3~deb11u6) ... > /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not > exist, so cannot grub-install to it! > What is confusing to me is that the error indicates the source SDD even > though I have updated the boot

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri 22 Dec 2023 at 11:24:22 (+), Mark Fletcher wrote: > On Fri, 22 Dec 2023 at 01:21, David Wright wrote: > > > > What sort of mess? I would have thought Grub would ignore excess > > kernels dropped into /boot. > [ … ] > It saw a Debian kernel (6.1.something) on / and > a LFS kernel (6.4.12

Re: grub-efi install on multiple ESPs.

Ram Ramesh (12023-12-23): >   I have debian bookworm installed on a raid1 made from /dev/nvme0n1p3  and  > /dev/nvme1n1p3.  Here are the partitions on the two nvme. > > /dev/nvme0n1p1 = /dev/nvme1n1p1  = 7mb ef02 > /dev/nvme0n1p2 = /dev/nvme1n1p2  = 7mb ef00 (Two distinct ESPs on two > different n

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher composed on 2023-12-22 06:43 (UTC): > I have just discovered that I > had a typo in my custom.cfg file, and when I fixed it, it worked. :-D > Thanks all for your help with this. :-D -- Evolution as taught in public schools is, like religion, based on faith, not based on s

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 10:54, Mark Fletcher wrote: > > On Fri, 22 Dec 2023 at 07:41, Anssi Saari > wrote: > > > > Mark Fletcher writes > > > > > The question is, what values are config_directory and prefix set to? > > > > Grub sets config_directory to point to the directory where it's reading >

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 01:21, David Wright wrote: > > What sort of mess? I would have thought Grub would ignore excess > kernels dropped into /boot. I have a laptop here that has two > bookworm netinst ISOs (release candidates) and a kernel and initrd > (hd-media) for booting the ISOs, and they've

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Fri, 22 Dec 2023 at 07:41, Anssi Saari wrote: > > Mark Fletcher writes > > > The question is, what values are config_directory and prefix set to? > > Grub sets config_directory to point to the directory where it's reading > it's config from. In other words, /boot. > > But why not just use 40_c

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher writes > The question is, what values are config_directory and prefix set to? Grub sets config_directory to point to the directory where it's reading it's config from. In other words, /boot. But why not just use 40_custom? It copies whatever is in the file (after the header) to yo

Re: GRUB -- Debian overrides? (but on original thread topic, not so much)

On Thu 21 Dec 2023 at 22:19:47 (-0500), Felix Miata wrote: > David Wright composed on 2023-12-21 19:20 (UTC-0600): > > On Thu 21 Dec 2023 at 21:38:46 (+), Mark Fletcher wrote: > > >> My very first attempt involved using Debian's > >> /boot partition as the /boot partition for LFS as well, so i

Re: GRUB -- Debian overrides? (but on original thread topic, not so much)

David Wright composed on 2023-12-21 19:20 (UTC-0600): > On Thu 21 Dec 2023 at 21:38:46 (+), Mark Fletcher wrote: >> My very first attempt involved using Debian's >> /boot partition as the /boot partition for LFS as well, so installing >> LFS's kernel (6.4.12 IIRC) alongside Debian's, but I qu

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Thu 21 Dec 2023 at 21:38:46 (+), Mark Fletcher wrote: > On Wed, 20 Dec 2023 at 06:01, David Wright wrote: > > > > I can't see anywhere where the OP claims to have set up LFS for > > booting itself, as opposed to being booted from a Debian Grub. > > It only says "I have been able to get a gr

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Thu, Dec 21, 2023 at 07:33:13PM -0500, Felix Miata wrote: > >From one PC here currently booted: > # grep vmlinuz /boot/grub2/custom.cfg | wc -l > 21 > # grep root= /boot/grub2/custom.cfg | wc -l > 21 > # grep root=LABEL /boot/grub2/custom.cfg | wc -l > 21 Just for the record, grep -c (count mat

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher composed on 2023-12-21 21:30 (UTC): > Felix Miata wrote: >> I suspect few if any regulars here spend much time with Slackware. > I am genuinely confused about how Slackware came into the picture > here... my foreign OS is LFS, nothing to do with slackware as far as I > know... Pur

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Mon, 18 Dec 2023 at 22:15, Felix Miata wrote: > > I can't answer why Grub scripts to what the do, because I don't really use > them, > and don't need to understand much about them. Grub config files in > /boot/grub/ are > akin to scripts, but they are really simple, mainly just command script

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Thu, 21 Dec 2023 at 21:38, Mark Fletcher wrote: > > > So I rebuilt my LFS (was happy to do so, this is a learning exercise) > with its own /boot partition, which gets me closer to the solution I > want which is one Grub, Debian's grub, with Debian as the first and > default boot choice, but LFS

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Wed, 20 Dec 2023 at 06:01, David Wright wrote: > > > I can't see anywhere where the OP claims to have set up LFS for > booting itself, as opposed to being booted from a Debian Grub. > It only says "I have been able to get a grub.cfg including the > LFS system …", which seems to imply LFS has on

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Wed, 20 Dec 2023 at 02:40, Felix Miata wrote: > > Mark Fletcher composed on 2023-12-20 00:28 (UTC): > > > I am curious to know from Debian > > GRUBbers (as it were) if the behaviour I am describing in this thread > > is expected... > > I suspect few if any regulars here spend much time with Sla

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Tuesday 19 December 2023 09:40:19 pm Felix Miata wrote: > I suspect few if any regulars here spend much time with Slackware. I, for one, have been running Slackware since 1999. It's what's running in this virtualbox where I do my email, and it's also what's running on my file server...

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

David Wright composed on 2023-12-20 00:00 (UTC-0600): > In case it's not clear, "generically symlinked" means that > /vmlinuz is a symlink pointing to the most recent linux-image. > (Similarly for initrd.) I added the following to > /etc/grub.d/07_custom: > menuentry 'My bullseye' $menuentry_i

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Tue 19 Dec 2023 at 21:40:19 (-0500), Felix Miata wrote: > Mark Fletcher composed on 2023-12-20 00:28 (UTC): > > > I am curious to know from Debian > > GRUBbers (as it were) if the behaviour I am describing in this thread > > is expected... > > I suspect few if any regulars here spend much time

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher composed on 2023-12-20 00:28 (UTC): > I am curious to know from Debian > GRUBbers (as it were) if the behaviour I am describing in this thread > is expected... I suspect few if any regulars here spend much time with Slackware. I think a more conventional approach would be to reconf

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

On Mon, 18 Dec 2023 at 22:15, Felix Miata wrote: > > Thus, you, as admin, construct working stanzas however you like, with or > without > UUIDS, with or without device names, with or without volume LABELS, however > you > like boot to go, and they don't get changed, except by the admin - you. Th

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

Mark Fletcher composed on 2023-12-18 20:36 (UTC): > Can anyone explain why, and how I can fix this in a way that will > still work the next time the bookworm kernel gets an update? I can't answer why Grub scripts to what the do, because I don't really use them, and don't need to understand much a

Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...

It's not ideal, but what I did when I had two disks and two operating systems was I installed two grubs, one for each OS, one on each MBR. I then used the BIOS menu to choose which disk to boot. This means each OS updates its own grub instance.

Re: Grub Error

Thank you for your reply.  Fortunately, I was able to fix the problem with the help of another respondent to my plea. Help from folks like you and your colleagues on the 'net  has kept my Computational Chemistry research  going  has since the early days of Slackware On 08/20/2023 10:30 AM,

Re: Grub Error

On 20 Aug 2023 14:30 +, from 2695bd53d...@ewoof.net (Michael Kjörling): > On 20 Aug 2023 08:14 -0400, from s.mol...@sbcglobal.net: >> error: no such device; 1d937ccf-2b57-4dcd-97d9-83522d7s04f1. >> >> error: unknown filesystem. >> >> grub fescue> > > Quite often this type of error is caused

Re: Grub Error

On 20 Aug 2023 08:14 -0400, from s.mol...@sbcglobal.net: > error: no such device; 1d937ccf-2b57-4dcd-97d9-83522d7s04f1. > > error: unknown filesystem. > > grub fescue> Quite often this type of error is caused by grub.cfg being either corrupted or out of sync with the reality of your system's sto

Re: Grub Error

On 8/20/23 08:15, s.mol...@sbcglobal.net wrote: My primary computer is an AMD FM-8320 8-Core Processor.. This morning, when I booted the system I got this result: Grub loading Welcome to GFUB! error: no such device; 1d937ccf-2b57-4dcd-97d9-83522d7s04f1. error: unknown filesystem. grub fescu

Re: Grub bug on Debian 11

On Tue 14 Mar 2023 at 23:16:29 (+0100), Mario Marietto wrote: > No problem. But without offence,what you are suggesting to me is not to > make something to understand what's the real problem and why it's > happening,but you are suggesting to change something in my configuration to > skip the genera

Re: Grub bug on Debian 11

On Tue, 14 Mar 2023 Mario Marietto wrote: No problem. But without offence,what you are suggesting to me is not to make something to understand what's the real problem and why it's happening, I believe that the locution above --"make something to understand"-- paraphrases "diagnose". but you a

Re: Grub bug on Debian 11

On Tue, 14 Mar 2023 Mario Marietto wrote in reply to Andrew Cater: --> *Which* Debian .iso did you install with ? debian-live-11.5.0-amd64-xfce.iso. Is there a way to upgrade this to the version that you have suggested ? I prefer to learn how to upgrade it than to make a fresh installation. I w

Re: Grub bug on Debian 11

On Tue, Mar 14, 2023 at 11:16:29PM +0100, Mario Marietto wrote: > No problem. But without offence,what you are suggesting to me is not to > make something to understand what's the real problem and why it's > happening,but you are suggesting to change something in my configuration to > skip the gene

Re: Grub bug on Debian 11

No problem. But without offence,what you are suggesting to me is not to make something to understand what's the real problem and why it's happening,but you are suggesting to change something in my configuration to skip the generation of the error. Do you confirm that you are following this approach

Re: Grub bug on Debian 11

Andrew M.A. Cater composed on 2023-03-14 22:02 (UTC): > I would suggest that you try with the netinst for the main Debian installer. > Other larger media are also available. > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0+nonfree/amd64/ > has iso-cd and iso-d

Re: Grub bug on Debian 11

On Tue, Mar 14, 2023 at 09:23:32PM +0100, Mario Marietto wrote: > --> *Which* Debian .iso did you install with ? > > debian-live-11.5.0-amd64-xfce.iso. Is there a way to upgrade this to the > version that you have suggested ? I prefer to learn how to upgrade it than > to make a fresh installation

Re: Grub bug on Debian 11

--> *Which* Debian .iso did you install with ? debian-live-11.5.0-amd64-xfce.iso. Is there a way to upgrade this to the version that you have suggested ? I prefer to learn how to upgrade it than to make a fresh installation. I would like to learn how to add "separately" what's missing on the 11.5

Re: Grub bug on Debian 11

[Copying to the list - private replies are discouraged On Tue, Mar 14, 2023 at 07:57:35PM +0100, Mario Marietto wrote: > Hello to everyone. > > I'm trying to understand why I'm getting an error message the second time > that I boot Debian 11 (the first time after the reinstallation it works). > W

Re: Grub bug on Debian 11

Hello to everyone. I'm trying to understand why I'm getting an error message the second time that I boot Debian 11 (the first time after the reinstallation it works). What do I do to produce the error ? Nothing special. I have just re-installed Debian 11 as normal,using qemu/kvm and virt-manager u

Re: Grub bug on Debian 11

On Mon, 13 Mar 2023 Mario Marietto wrote: Hello to every Debian user. [elided: Mario Marietto's apology for posting the following question off-topic in another thread] "I've just installed Debian 11 and I see that it is affected by the bug explained here : https://bugs.launchpad.net/oem-prior

Re: Grub issue

On Tue 29 Nov 2022 at 14:36:16 (+), Andrew Wood wrote: > On 28/11/2022 23:52, David wrote: > > > > Can you confirm that you are entering commands at the prompt that looks > > like: > > > >grub rescue> > > > > That identifies the GRUB rescue shell, which is different to the normal > > GRU

Re: Grub issue

On Wed, 30 Nov 2022 at 11:00, Andrew Wood wrote: > On 29/11/2022 20:48, David wrote: > > On Wed, 30 Nov 2022 at 01:36, Andrew Wood wrote: > > Disclaimer: I have never done this with RAID, so using a GRUB > > device looking like (md/x) is unknown territory for me. > > > >> ls (md/1)/boot shows th

Re: Grub issue

On Tue, Nov 29, 2022 at 7:00 PM Andrew Wood wrote: > ... > Thanks David &Tim > > Unfortunately insmod normal is still giving file not found > > ls (md/1)/boot/grub/i386-pc shows its not there. > > When I try to run linux /boot/vmlinuz... > > and initd /boot/initrd.img > > it says Unknown comma

Re: Grub issue

On 29/11/2022 20:48, David wrote: On Wed, 30 Nov 2022 at 01:36, Andrew Wood wrote: Disclaimer: I have never done this with RAID, so using a GRUB device looking like (md/x) is unknown territory for me. ls (md/1)/boot shows the kernels and initrd images Ok, based on that, if you still need h

Re: Grub issue

On Wed, 30 Nov 2022 at 01:36, Andrew Wood wrote: Disclaimer: I have never done this with RAID, so using a GRUB device looking like (md/x) is unknown territory for me. > ls (md/1)/boot shows the kernels and initrd images Ok, based on that, if you still need help to boot the machine, then you cou

Re: Grub issue

On 28/11/2022 23:52, David wrote: Can you confirm that you are entering commands at the prompt that looks like: grub rescue> That identifies the GRUB rescue shell, which is different to the normal GRUB shell. The first command that I would use is a bare 'set' with no arguments. grub

Re: Grub issue

On Tue, 29 Nov 2022 at 05:12, Andrew Wood wrote: > Hi Can someone help me with a Grub problem please. > > I have 2 disks in a RAID1 mirrror with 2 partitions. sda1 & sdb1 = md0 > swap parition and sda2 & sdb2 = md1 root parition. The disks are MBR > style partitiions. > > For some reason Grub has

Re: Grub issue

On Mon, 28 Nov 2022, Andrew Wood wrote: Hi Can someone help me with a Grub problem please. I have 2 disks in a RAID1 mirrror with 2 partitions. sda1 & sdb1 = md0 swap parition and sda2 & sdb2 = md1 root parition. The disks are MBR style partitiions. For some reason Grub has got corrupted on

Re: grub-xen-host in bullseye-proposed-updates

On 2022-09-22 11:43, Steve McIntyre wrote: Tim wrote: Quick followup for those here who like me might have pinned grub, the fixed version is in bullseye-proposed-updates for those who prefer not to leave pins lying around forgotten... I haven't rebooted the host yet but I can confirm that my gu

Re: grub-xen-host in bullseye-proposed-updates

Tim wrote: >Quick followup for those here who like me might have pinned grub, the >fixed version is in bullseye-proposed-updates for those who prefer not >to leave pins lying around forgotten... > >I haven't rebooted the host yet but I can confirm that my guests start >ok. > >Thanks Steve for getti

Re: Grub Problem

On 06/25/2022 09:37 AM, Stephen P. Molnar wrote: I have four hard drives ion my Bullseye platform; Three SSD's and one HDD. My current copy of Bullseye is on /dev/sdd1. I have installed a pristine copy of Bullsye on /dev/sda. The installer found the copy of Bullseye on /dev/ssd1 and I instal

Re: Grub Problem

"Stephen P. Molnar" writes: > Assistanc will be mucn appeciated. You didn't really specify what you want assistance with but I guess you want to boot the new Bullseye too? I don't really see the point of having two copies of the same OS installed though. Assuming a BIOS system and os-prober pac

  1   2   3   4   5   6   7   8   9   10   >