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
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 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
ion or
> >> removal causes its regeneration anew based upon the content of
> >> /etc/default/grub
> >> and the regeneration script(s), same as running grub-mkconfig.
>
> > FTR, editing the Grub menu itself is, of course, totally ephemeral.
> > Type what
>> /etc/default/grub
>> and the regeneration script(s), same as running grub-mkconfig.
> FTR, editing the Grub menu itself is, of course, totally ephemeral.
> Type whatever you like, boot from it, and the edits are gone for good.
> But editing /boot/grub/grub.cfg does persist as lo
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
hat is not used anywhere on any system.
So the first thing to check is whether there's a grub.cfg on any other
partition.
One thing you can try is changing something innocuous in what you think
is the live stanza, and then checking whether it's visible when you go
to edit the commands in th
'Load initial ramdisk /initrd.img …'
initrd /initrd.img
}
> 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 the regeneration script(
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
~# 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
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
>
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 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/
gt; So far, good, but when booting the Void entry is absent.
> https://easthope.ca/GrubMenu.jpg
>
> Ideas?
The system has booted into a bookworm Grub (deb12u1). It would appear
that your MBR/UEFI has booted into a grub.cfg that isn't the one
created above, ie on the other disk. After all, that Grub menu looks
as if it was created on a system that (a) isn't bullseye, and (b) ran
os-prober to produce its bullseye lines 3 and 4.
Cheers,
David.
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 11 Jul 2021 at 11:31:09 (-0500), David Wright wrote:
> On Sat 10 Jul 2021 at 11:13:31 (+0200), Stella Ashburne wrote:
> > My LUKS-encrypted partition consists of / and swap area. I assume the /
> > contains /home, /var, /usr, etc...
>
> It would be nice to give you a set of Grub commands
ated grub.cfg
> > in the ESP on the SSD.
> >
>
> I suspected it too because when I installed Debian Testing, I didn't delete
> both the ESP and /boot partitions that were created by Debian Buster. As a
> result, after installing Debian Testing successfully and reboo
tem.map and initrd.img- in grub is of the
older Debian Buster.
Do you think the problem of the missing GRUB menu can be fixed if the older
version of config-, vmlinuz- System.map and initrd.img- can replaced with those
of Debian Testing? What do you think?
Best regards
Hello David
I didn't expect a rather lengthy reply from you.
> Sent: Tuesday, July 06, 2021 at 9:29 AM
> From: "David"
> To: "debian-user mailing list"
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
>
> grub> echo &qu
Hi David
> Sent: Monday, July 05, 2021 at 4:52 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
>
> I find the Grub installation prompts in the d-i very confusing.
>
On Mon, 5 Jul 2021 at 02:46, Stella Ashburne wrote:
> > Sent: Sunday, July 04, 2021 at 12:01 PM
> > From: "David"
> > As I mentioned, I do not know GPT and UEFI systems.
> It's off-topic; I am curious why you do not use GPT/UEFI/Secure Boot?
> Secure Boot has been supported since Debian Buster.
. Booting with the USB stick inserted: something else appears,
a blue Grub menu, or a Debian installer splash screen,
or even Windows.
Of course, the second scenario can only work if the USB's UUID
hasn't been recreated by further uses.
¹ With encrypted systems, you have to
Hi
> Sent: Sunday, July 04, 2021 at 12:01 PM
> From: "David"
> To: "debian-user mailing list"
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
>
> As I mentioned, I do not know GPT and UEFI systems.
It's off-topic; I am c
Hi
> Sent: Sunday, July 04, 2021 at 2:42 PM
> From: "deloptes"
> To: debian-user@lists.debian.org
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
>
> I had similar issue on some of the machines. Try with the bios boot from
> devi
Stella Ashburne wrote:
> I discovered that reinstalling GRUB and then ran update-grub didn't help
> at all. The issue still persists. With my limited technical knowledge, the
> only way for me to get back the GRUB menu with the blue background is to
> reinstall Debian.
I had
On Sun, 4 Jul 2021 at 18:54, Stella Ashburne wrote:
> > Sent: Friday, July 02, 2021 at 10:49 AM
> > From: "David"
> > On Thu, 1 Jul 2021 at 23:20, Stella Ashburne wrote:
> > I suggest to boot as you describe above (your step #8) until you reach
> > the 'grub>' prompt. This is actually a very us
Hi David
> Sent: Friday, July 02, 2021 at 10:49 AM
> From: "David"
> To: "Stella Ashburne"
> Cc: "debian-user mailing list"
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
> I see that you've not had any repl
Hi
> Sent: Friday, July 02, 2021 at 8:58 AM
> From: "deloptes"
> To: debian-user@lists.debian.org
> Subject: Re: How do I get back the GRUB menu with the blue background?
>
>
> As this is a fresh installation, why don't you just wipe everything linux
> p
Stella Ashburne wrote:
> 7. Debian Testing was installed on the 100GB partition. Installation was
> successful.
>
> 8. However, I am now unable to boot into the GRUB menu with the blue
> background. Instead all I have is a black screen with the word grub> _
> (The under
(automatically created by Microsoft Windows'
> installer)
> 100GB Microsoft Windows 10
> 1. Debian Buster's 64bit installer (version 10.10) was used to create the EFI
> System Partition (ESP), the /boot partition and the encrypted logical
> volumes. Installation was successfu
tition and the encrypted logical volumes.
Installation was successful and I was able to boot into the GRUB menu with a
blue background. It had an entry named Debian GNU/Linux.
2. Next I installed Microsoft Windows 10 and the installation was successful.
3. I rebooted into Debian and used sudo os
you may need to change where the root is in the script below
using the file /etc/grub.d/40_custom replace it with:
=
#!/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
By the way and for the record, this bug report is an exact instance of the
problem I had and the proposed workaround fixed the delayed boot process
for me too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950175.
Hey folks,
I’ve been trying to install Debian testing on an Asus x205ta laptop which
has a 32-bit UEFI. The i386 architecture installs flawlessly but I am
trying to install the amd64 architecture using the Debian Installer alpha 2
multi-arch image (I tried the daily images but they consistently fa
On 10/18/2016 8:51 AM, Richard Owlett wrote:
With GRUB2 on Jessie, how do I increase the menu's font _size_ .
A Google search wandered around my problem without addressing it.
I did discover that that GRUB was using a resolution that matched
my monitor's settings.
[When menu comes up go to comma
On Wed 19 Oct 2016 at 12:44:16 -0500, Richard Owlett wrote:
> On 10/19/2016 11:17 AM, Brian wrote:
> >
> >Do you really want to overwrite the system's unicode.pf2?
>
> I my specific use case, I think so. It illustrates why I do not consider my
> original post to not quite be a 'XY Problem'. I'm w
On Wed 19 Oct 2016 at 12:51:32 -0500, Richard Owlett wrote:
> On 10/19/2016 11:33 AM, Jonathan Dowland wrote:
> >On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
> >>It's not _quite_ an 'XY Problem'. The OP hath declared.
> >>It may be its first cousin. There is a not explicitly st
Richard Owlett composed on 2016-10-19 12:51 (UTC-0500):
Jonathan Dowland wrote:
On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
It's not _quite_ an 'XY Problem'. The OP hath declared. It may
be its first cousin. There is a not explicitly stated solution
constraint. In my c
On 10/19/2016 11:33 AM, Jonathan Dowland wrote:
On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
It's not _quite_ an 'XY Problem'. The OP hath declared.
It may be its first cousin. There is a not explicitly stated solution
constraint.
In my case I wish to use default resolution o
On 10/19/2016 11:17 AM, Brian wrote:
On Wed 19 Oct 2016 at 09:22:00 -0500, Richard Owlett wrote:
It's not _quite_ an 'XY Problem'. The OP hath declared.
It may be its first cousin. There is a not explicitly stated solution
constraint.
In my case I wish to use default resolution of current driv
On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
> It's not _quite_ an 'XY Problem'. The OP hath declared.
> It may be its first cousin. There is a not explicitly stated solution
> constraint.
> In my case I wish to use default resolution of current driver/monitor
> combination.
> I
On Wed 19 Oct 2016 at 09:22:00 -0500, Richard Owlett wrote:
> It's not _quite_ an 'XY Problem'. The OP hath declared.
> It may be its first cousin. There is a not explicitly stated solution
> constraint.
> In my case I wish to use default resolution of current driver/monitor
> combination.
> I in
Hi,
to change the resolution at boot makes EVERYTHING bigger: the picture, the
fonts and so on.
Isn't the font not beeing created by the file /boot/grub/fonts/unicode.pf2?
I believe, to exchange this against another file might increase the font.
However, I do still not know, which format this f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 19, 2016 at 09:22:00AM -0500, Richard Owlett wrote:
> On 10/19/2016 6:08 AM, to...@tuxteam.de wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Wed, Oct 19, 2016 at 11:37:08AM +0100, Brian wrote:
> >>On Tue 18 Oct 2016 at
On 10/19/2016 6:08 AM, to...@tuxteam.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 19, 2016 at 11:37:08AM +0100, Brian wrote:
On Tue 18 Oct 2016 at 10:22:24 -0500, Richard Owlett wrote:
On 10/18/2016 9:20 AM, Darac Marjal wrote:
On Tue, Oct 18, 2016 at 08:51:00AM -0500,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Oct 19, 2016 at 11:37:08AM +0100, Brian wrote:
> On Tue 18 Oct 2016 at 10:22:24 -0500, Richard Owlett wrote:
>
> > On 10/18/2016 9:20 AM, Darac Marjal wrote:
> > >On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
> > >>With GRUB2
On Tue 18 Oct 2016 at 10:22:24 -0500, Richard Owlett wrote:
> On 10/18/2016 9:20 AM, Darac Marjal wrote:
> >On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
> >>With GRUB2 on Jessie, how do I increase the menu's font _size_ .
> >>A Google search wandered around my problem without ad
It's been a while since I saw it, but I swear I once had a graphical
tool for editing various Grub parameters, including the splash screen
image, font, font size, and the grub menu, but I can't find it now.
On 10/18/2016 11:22 AM, Richard Owlett wrote:
On 10/18/2016 9:20 AM, Da
On Tue, Oct 18, 2016 at 10:22:24AM -0500, Richard Owlett wrote:
On 10/18/2016 9:20 AM, Darac Marjal wrote:
On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
With GRUB2 on Jessie, how do I increase the menu's font _size_ .
A Google search wandered around my problem without addressi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Oct 18, 2016 at 10:22:24AM -0500, Richard Owlett wrote:
> On 10/18/2016 9:20 AM, Darac Marjal wrote:
[...]
> >You will need to convert a font of your choice to GRUB's pf2 format:
[...]
> I'm confused. We may be using the term "font" differe
On 10/18/2016 9:20 AM, Darac Marjal wrote:
On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
With GRUB2 on Jessie, how do I increase the menu's font _size_ .
A Google search wandered around my problem without addressing it.
I did discover that that GRUB was using a resolution that
On Tue, Oct 18, 2016 at 08:51:00AM -0500, Richard Owlett wrote:
With GRUB2 on Jessie, how do I increase the menu's font _size_ .
A Google search wandered around my problem without addressing it.
I did discover that that GRUB was using a resolution that matched my
monitor's settings.
[When menu
With GRUB2 on Jessie, how do I increase the menu's font _size_ .
A Google search wandered around my problem without addressing it.
I did discover that that GRUB was using a resolution that matched
my monitor's settings.
[When menu comes up go to command mode by typing 'c'. Then enter
'vbeinfo'
Scott Ferguson wrote:
> Muntasim-Ul-Haque wrote:
> > I dual-booted Debian with Windows. I reinstalled my Windows and now the
> > GRUB menu does not appear. How can I fix this without reinstalling
> > Debian again?
> > With thanks,
> > Muntasim-Ul-Haque
On 29/12/13 01:50, Muntasim-Ul-Haque wrote:
> Hi,
> I dual-booted Debian with Windows. I reinstalled my Windows and now the
> GRUB menu does not appear. How can I fix this without reinstalling
> Debian again?
> With thanks,
> Muntasim-Ul-Haque
Use the rescue option on the i
Hi,
I dual-booted Debian with Windows. I reinstalled my Windows and now the
GRUB menu does not appear. How can I fix this without reinstalling
Debian again?
With thanks,
Muntasim-Ul-Haque
I think you want to modificate the content of the boot menu
for grub you can give fix values here
/boot/*grub*/menu.lst
On Tue, Jan 13, 2009 at 12:58 PM, Umarzuki Mochlis wrote:
> perhaps if you'd be a bit more verbose on what do you mean by "item
> under c", what you're trying to avoid and why
perhaps if you'd be a bit more verbose on what do you mean by "item
under c", what you're trying to avoid and why do you need to stop the
server.
2009/1/13 Leniy Tsan :
> When boot into grub, how can I change the default item under 'c' command
> line?
> I don't want to boot another system for a mo
When boot into grub, how can I change the default item under 'c' command
line?
I don't want to boot another system for a modification,it's difficult to
stop a server.
thank you.
On Mon, 24 Sep 2007 20:19:32 -0500, Nate Bargmann <[EMAIL PROTECTED]> said:
> * Andrew Sackville-West <[EMAIL PROTECTED]> [2007 Sep 24
> 20:13 -0500]:
>> looks like update-grub is picking up initrd.img and vmlinux symlinks
>> that must exist in /boot. You could maybe delete these symlinks, as I
* Andrew Sackville-West <[EMAIL PROTECTED]> [2007 Sep 24 20:13 -0500]:
> looks like update-grub is picking up initrd.img and vmlinux symlinks
> that must exist in /boot. You could maybe delete these symlinks, as I
> think theyre supposed to be in / anyway.
>
> That would get you down to 2 stanz
On Mon, Sep 24, 2007 at 07:13:40PM -0500, Nate Bargmann wrote:
> This one has been driving me batty and I've not figured out the cause
> of this one yet. On this desktop with Sid installed and grub as the
> bootloader, for some time (months) update-grub has been adding a
> "Default" entry and then
This one has been driving me batty and I've not figured out the cause
of this one yet. On this desktop with Sid installed and grub as the
bootloader, for some time (months) update-grub has been adding a
"Default" entry and then repeats the entries again:
title Debian GNU/Linux, kernel 2
Hi,
Grub's menu uses 80x25 character sizes on its menu.
I would like to change that to something smaller.
Trying 'terminal --lines=50' does nothing.
Anybody gotten grub to put smaller characters on its menu?
Hugo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
; One issue: I can't find the GRUB menu list file in this
> installation. Where is it? It would be much easier to make some
> multiple disk multiboot changes if I could directly edit it rather
> than do it indirectly through GRUB.
>
It should be in /boot/grub/menu.lst,
pair odocs <[EMAIL PROTECTED]> writes:
> I am a new user who just installed debian 3.1r1 with the 2.6 kernel with GRUB
> in the mbr.
>
> Much went well for a 'desktop' install...later we could talk printer and
> video codecs.
>
> One issue: I c
pair odocs wrote:
> I am a new user who just installed debian 3.1r1 with the 2.6 kernel with GRUB
> in the mbr.
>
Welcome to Debian .. and debian-user
> Much went well for a 'desktop' install...later we could talk printer and
> video codecs.
>
> On
I am a new user who just installed debian 3.1r1 with the 2.6 kernel with GRUB in the mbr. Much went well for a 'desktop' install...later we could talk printer and video codecs. One issue: I can't find the GRUB menu list file in this installation. Where is it? It would be
92 matches
Mail list logo
