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
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
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
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.
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
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
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
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
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
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
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
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-
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
>
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 and ran
> grub-install /de
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
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
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
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
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
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
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
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
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
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
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
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
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
>
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
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
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
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
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/
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
35 matches
Mail list logo
