On 27/11/22 15:25, Stephen Morris wrote:
On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot me
On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
m
On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
m
On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
m
On 23/11/22 18:22, Samuel Sieb wrote:
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
m
On 24/11/22 05:35, Lester M Petrie wrote:
On 11/23/22 02:24, Samuel Sieb wrote:
On 11/21/22 14:12, Stephen Morris wrote: F37 the grub-gfxmode
statement in /etc/default/grub that worked fine in F36 does not work
in F37 even though the associated statements are added to grub.cfg,
they seem to
On 23/11/22 18:24, Samuel Sieb wrote:
On 11/21/22 14:12, Stephen Morris wrote:
These issues seem to be tied to the fact that F37 is now booting with
Grub and not with what F36 was booting with (possibly systemd?), and in
It has been grub for a very long time.
I know the boot menus have been g
On 11/23/22 02:24, Samuel Sieb wrote:
On 11/21/22 14:12, Stephen Morris wrote: F37 the grub-gfxmode
statement in /etc/default/grub that worked fine in F36 does not work
in F37 even though the associated statements are added to grub.cfg,
they seem to be being ignored (I'm thinking about raising
On 11/21/22 14:12, Stephen Morris wrote:
These issues seem to be tied to the fact that F37 is now booting with
Grub and not with what F36 was booting with (possibly systemd?), and in
It has been grub for a very long time.
F37 the grub-gfxmode statement in /etc/default/grub that worked fine in
On 11/22/22 22:45, Stephen Morris wrote:
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
means and why it is occurring in F37 whe
On 23/11/22 12:04, Samuel Sieb wrote:
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
means and why it is occurring in F37 when it was never produced in
F36, and what
On 11/20/22 23:54, Stephen Morris wrote:
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this means
and why it is occurring in F37 when it was never produced in F36, and
what I need to do to rectify it?
On Tue, 22 Nov 2022 09:12:00 +1100
Stephen Morris wrote:
> > On Mon, 21 Nov 2022 18:54:49 +1100
> > Stephen Morris wrote:
> >
> >> Hi,
> >> I am getting the following error message displayed before the
> >> display of the grub boot menu, can someone explain to me what this
> >> means and
On 22/11/22 02:25, stan via users wrote:
On Mon, 21 Nov 2022 18:54:49 +1100
Stephen Morris wrote:
Hi,
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this
means and why it is occurring in F37 when it was never pr
On Mon, 21 Nov 2022 18:54:49 +1100
Stephen Morris wrote:
> Hi,
> I am getting the following error message displayed before the
> display of the grub boot menu, can someone explain to me what this
> means and why it is occurring in F37 when it was never produced in
> F36, and what I need to
Hi,
I am getting the following error message displayed before the
display of the grub boot menu, can someone explain to me what this means
and why it is occurring in F37 when it was never produced in F36, and
what I need to do to rectify it?
error: ../../grub-core/kern/efi
On 5/8/22 16:15, Scott Beamer wrote:
On 8/4/22 7:28 PM, Chris Murphy wrote:
On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
Greetings,
After a recent Fedora 36 update, I'm getting an error message when
selecting "Windows Boot Manager" from the GRUB menu. Instead of
b
On 8/5/22 02:15, Scott Beamer wrote:
On 8/4/22 7:28 PM, Chris Murphy wrote:
On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
Greetings,
After a recent Fedora 36 update, I'm getting an error message when
selecting "Windows Boot Manager" from the GRUB menu. Instead of
b
On 8/4/22 7:28 PM, Chris Murphy wrote:
On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
Greetings,
After a recent Fedora 36 update, I'm getting an error message when
selecting "Windows Boot Manager" from the GRUB menu. Instead of booting
like it had previously, it giv
On Thu, Aug 4, 2022, at 6:39 PM, Scott Beamer wrote:
> Greetings,
>
> After a recent Fedora 36 update, I'm getting an error message when
> selecting "Windows Boot Manager" from the GRUB menu. Instead of booting
> like it had previously, it gives me an almost blan
On 8/4/22 15:39, Scott Beamer wrote:
After a recent Fedora 36 update, I'm getting an error message when
selecting "Windows Boot Manager" from the GRUB menu. Instead of booting
like it had previously, it gives me an almost blank screen with the
following text in
Greetings,
After a recent Fedora 36 update, I'm getting an error message when
selecting "Windows Boot Manager" from the GRUB menu. Instead of booting
like it had previously, it gives me an almost blank screen with the
following text in the upper left:
/EndEntire
And
t sequence continues for some time using VGA mode, so the driver shouldn't
> come into play at that
> point in the boot process.
>
> Booting with the 1030, the USB keyboard turns off after a selection is made
> from the grub menu, but
> it comes back on in about a second. I
to play at that
point in the boot process.
Booting with the 1030, the USB keyboard turns off after a selection is made
from the grub menu, but
it comes back on in about a second. I saw one hint regarding the 1650 related
to secure boot, since
disabled to no avail. I'm not having much l
Aha. I see now. Thank you Stan and Thank you Samuel.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-
64aa5
> rhgb quiet" GRUB_DISABLE_RECOVERY="true"
If you edit this line, and add the options you want at the end of the
line, separated by a space, and then run grub2-mkconfig, they will be
set on all your installed kernels.
> GRUB_ENABLE_BLSCFG=true
>
> But I want to
On 2021-08-31 9:44 a.m., Gueven Bay via users wrote:
Am Di., 31. Aug. 2021 um 16:28 Uhr schrieb stan via users
:
I think that by F33, the actual stanzas for each kernel had been moved
to /boot/loader/entries
But I want to change the "linux" and "initrd" lines in the grub
Some minutes ago I have rebooted to be able to write down the Fedora
33 grub menu entry:
load video
set gfxpayload=keep
insmod gzio
linux ($root)/boot/vmlinuz-5.13.12-100.fc33.x86_64 root=UUID=... ro
resume=UUID=... rhgb quiet
initrd ($root)/boot/initramfs-5.13.12-100.fc33.x86_64.img
(The ... are
ue
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=UUID=583baa2f-645c-4a12-99a1-f595ef664aa5 rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
But I want to change the "linux" and "initrd" lines in the grub menu
entry! I do no
On Tue, 31 Aug 2021 12:59:56 +0200
Gueven Bay via users wrote:
> Where do I find and edit my grub menu (of course, if I do not want to
> edit the menu manually at every boot time on the grub command line,
> which is what I do _not_ want)?
>
> (The side problem is: In the Quick
under
/etc/grub.d !?
(I looked in 40_custom, 41_custom, 10_linux)
I also looked in /etc/default/grub. The grub menu entries for both
OSes are also not in this file.
Where do I find and edit my grub menu (of course, if I do not want to
edit the menu manually at every boot time on the grub command line
ope. complete 'radio silence'. not a peep after selecting the grub menu entry
after a soft-reboot.
then something
must be broken really early which would likely make it a firmware
issue.
likely. tho, i'm not entirely clear on what could be getting borked in a
soft-reboot c
x27;s up & running without issue.
>
> But,
>
> on SOFT reboot -- via either `shutdown -r now` or `systemctl start
> reboot.target`,
> the system DOES start the reboot.
> UEFI boot passes to grub menu as usual, latest kernel is selected, and then
> ...
> ... nothing.
>
-- via either `shutdown -r now` or `systemctl start
reboot.target`,
the system DOES start the reboot.
UEFI boot passes to grub menu as usual, latest kernel is selected, and then ...
... nothing.
Just sits there. No further error logging, or progress -- even at serial
console with kernel/systemd
I just tried 'dnf kernel downgrade'. This pulls in a 4.x kernel but does not
remove the latest 5.x
/boot/grub.cfg was not touched but I do see the newly installed kernel in the
boot menu ( it is NOT the default ).
Not surprisingly 'dnf kernel update' now reports "nothing to do ".
dnf remo
I'm glad to see I'm not the only one with this problem.
I have not had this problem before since I use /etc/dnf/dnf.conf to block
kernel updates to prevent spamming /boot with every minor update. Until
yesterday my running kernel was 5.0.7-200.fc29.x86_64
I intended to upgrade from Fed29 to Fe
Hi Chris, Tim,
Sorry for the late response.
Thanks for the explanations.
On Sat, Jul 06, 2019 at 03:18:59PM -0600, Chris Murphy wrote:
> On Sat, Jul 6, 2019 at 1:18 PM Suvayu Ali wrote:
>
> Making things worse, many manufacturers treat their customers like
> children, and have decided to refer
On Sun, 2019-07-07 at 00:47 +0530, Suvayu Ali wrote:
> I have never quite understood how UEFI worked. Initially I stayed
> away from it because of secure boot issues. Do you think I should
> put in the effort to move to UEFI?
UEFI is the very basic operating system loaded into your motherboard,
On Sat, Jul 6, 2019 at 1:18 PM Suvayu Ali wrote:
>
> I have never quite understood how UEFI worked. Initially I stayed away from
> it because of secure boot issues. Do you think I should put in the effort to
> move to UEFI? If so, would you be able to point me where to start?
>
BIOS vs UEFI
Hi Chris,
On Fri, Jul 05, 2019 at 02:53:08PM -0600, Chris Murphy wrote:
>
> Post the contents of the following files somewhere (I'm not sure
> they'll attach to the list but you can give it a shot if you want)
>
> /boot/grub2/grub.cfg
This evening I went through this carefully, and spotted a fe
On Thu, Jul 4, 2019 at 2:56 PM Sergio Cipolla wrote:
>
> I've had trouble too is a new Fedora install with grub on the partition (not
> MBR), I even eventually re-installed because I tried to revert to
> grubby-deprecated and then couldn't get the system to boot to
> graphical.target because of
On Tue, Jul 2, 2019 at 8:03 AM Suvayu Ali wrote:
>
> Hi,
>
> For a while now kernel updates doesn't update the grub menu on my system.
> However I could always manually update using `grub2-mkconfig -o
> /boot/grub/grub2.cfg`. But lately I can't even do that! I h
Hi Sergio,
On Thu, Jul 4, 2019 at 9:44 PM Sergio Cipolla wrote:
>
> I've had trouble too is a new Fedora install with grub on the partition (not
> MBR), I even eventually re-installed because I tried to revert to
> grubby-deprecated and then couldn't get the system to boot to
> graphical.targe
I've had trouble too is a new Fedora install with grub on the partition (not
MBR), I even eventually re-installed because I tried to revert to
grubby-deprecated and then couldn't get the system to boot to graphical.target
because of the entries needed for nvidia drivers, even after reverting to
Hi,
>
> For a while now kernel updates doesn't update the grub menu on my system.
> However I could always manually update using `grub2-mkconfig -o
> /boot/grub/grub2.cfg`. But lately I can't even do that! I have already
> tried running `grub2-switch-to-blscfg`, but I do
Hi,
For a while now kernel updates doesn't update the grub menu on my system.
However I could always manually update using `grub2-mkconfig -o
/boot/grub/grub2.cfg`. But lately I can't even do that! I have already tried
running `grub2-switch-to-blscfg`, but I don't think tha
boot natively in UEFI mode) which
successfully installed F29. Having done the install every time I boot
it does not display a grub menu even though there are multiple
kernels installed. In F28 there was a grub default file with supplied
initial "default" grub configurations which
which successfully installed F29. Having
done the install every time I boot it does not display a grub menu even
though there are multiple kernels installed. In F28 there was a grub
default file with supplied initial "default" grub configurations which
other files in /etc/grub.d supplemented to b
e the install every time I boot it does not display a grub menu even
though there are multiple kernels installed. In F28 there was a grub
default file with supplied initial "default" grub configurations which
other files in /etc/grub.d supplemented to build (in a bios
installation) /boot
@updates
kernel.x86_64
4.19.13-300.fc29 @updates
The first two kernel packages are highlighted. What is the significance of
that ?
The last package, 4.19.13-300 isn't highlighted. It also doesn't show in
the
> I see you got to the grub menu eventually, but in case it
> helps, there is a change in F29 to hide the grub menu by
> default.
> https://fedoraproject.org/wiki/Changes/HiddenGrubMenu
Thanks, it was good to know.
Regards,
F
___
u
re
> rebooting and then I did not get the usual GRUB menu where I can choos
> the kernel but instead just a black screen with a blinking cursor. So
> I suspect that the upgrade broke GRUB and I cannot load fedora
> anymore.
>
> I am probably able to boot with a USB stick. What should
(on Dec. 20, I said)
> If, after a few days, the grub menu still looks good, I'll
> promote this thread from CLOSED to SOLVED.
After a weekly patching, a few cycles of nightly power-down and morning
power-up, and a few days of regular operational use, I'm confident this
reall
> I am probably able to boot with a USB stick. What should I do to go
> back to normal?
Oh, after 3 reboot, GRUB is back!
Regards,
F
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject
GRUB menu where I can choos
the kernel but instead just a black screen with a blinking cursor. So
I suspect that the upgrade broke GRUB and I cannot load fedora
anymore.
I am probably able to boot with a USB stick. What should I do to go
back to normal?
Thanks,
F
Patrick O'Callaghan:
> IIRC it used to be 72.72 (my first job was working on an early
> typesetting system at Cambridge University Press :-) However
> according to Wikipedia a point is now officially 1/72 of an
> "international inch":
>
> https://en.wikipedia.org/wiki/Point_(typography)
I stayed
On Sat, 2018-12-22 at 15:56 +1030, Tim via users wrote:
> Don't believe me? Fire up LibreOffice, try out 12 and 24 point text,
> and look at the on-screen ruler, or print it out.
>
> There's approx 72 of *these* points in an inch.
IIRC it used to be 72.72 (my first job was working on an early
ty
Allegedly, on or about 21 December 2018, Rick Stevens sent:
> Note that "sizes" in most word processors or printing-related things
> are given in points
True. And when done correctly, it's an absolute size. i.e. 12 point
text is always the same size, no matter what it's printed on or
displayed o
> 3. put the name of the file into the GRUB_FONT option:
> GRUB_FONT=FreeSans24.pf2
>
> 4. do the grub2-mkconfig -o /etc/grub2.cfg
>
> This way, the name of the font file documents what font and size is
> being used.
>
> Also, I learned the hard way: the size (here, 2
On 12/20/18 5:39 PM, home user via users wrote:
Also, I learned the hard way: the size (here, 24) has a different
meaning (units) than the font size in LibreOffice. I actually tried 16
first. That's nice and big in LibreOffice, but it was tiny in the grub
menu.
In LibreOffice, the si
ont and size is
being used.
Also, I learned the hard way: the size (here, 24) has a different
meaning (units) than the font size in LibreOffice. I actually tried 16
first. That's nice and big in LibreOffice, but it was tiny in the grub
menu.
Thank-you, Rick.
If, after a few days, the g
On 12/20/18 10:04 AM, home user via users wrote:
> (Rick said)
>> Actually, you can change the grub font size. You need to convert a
>> font into the format grub understands (.pf2) using grub2-mkfont, ...
>
> 1. How can I determine what font is currently being used? /etc/grub2.cfg
> mentions "unic
(Rick said)
> Actually, you can change the grub font size. You need to convert a
> font into the format grub understands (.pf2) using grub2-mkfont, ...
1. How can I determine what font is currently being used?
/etc/grub2.cfg mentions "unicode.pf2", but the Fonts tool finds no font
with a name c
On 12/16/18 2:26 PM, home user via users wrote:
> The error messages that appeared before the grub menu are gone. I thank
> those who coached me through the fix.
>
> It seems the size of the font in the grub menu is not under my control.
> Realistically, there's nothing I/we
On Tue, Dec 11, 2018, 10:11 PM Samuel Sieb wrote:
>
> I also wonder if it's necessary to refresh grub's boot files. Does
> anyone else know if grub upgrades update the boot sectors?
>
BIOS, no update happens, run grub2-install.
UEFI, it's updated. Don't run grub2-install.
(Silverblue, bootloa
The error messages that appeared before the grub menu are gone. I thank
those who coached me through the fix.
It seems the size of the font in the grub menu is not under my control.
Realistically, there's nothing I/we can do about it. So I'm closing
t
Thank-you, Tim. I'll start a new thread on this shortly. - Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.h
Allegedly, on or about 12 December 2018, home user via users sent:
> Something keeps trying to do automated updates, but I have not been
> able to figure out what, or how to shut it off.
When you log into a GUI session, the GUI can fire off things as you log
in. In MATE, there's a "mate-session-p
Something keeps trying to do
automated updates, but I have not been able to figure out what, or how
to shut it off. Once this grub menu font issue is solved or closed,
I'll address this in a separate new thread.
___
users mailing list -- users@lis
On 12/12/18 10:48 AM, home user via users wrote:
> (Ed asked)
>> Has this system been installed at around F18
>> and then upgraded as time goes on?
> It occurs to me that I did not fully answer this. Since dnf was
> released into Fedora, I upgraded Fedora roughly every half year using
> "dnf upgra
I did as Samuel suggested.
The good news: No error messages (re-)appeared before the grub menu
showed up.
The bad news: I did not notice any differences in the grub menu itself;
the font still borders on being too small for me and needing a
magnifying glass
(Ed asked)
> Has this system been installed at around F18
> and then upgraded as time goes on?
It occurs to me that I did not fully answer this. Since dnf was
released into Fedora, I upgraded Fedora roughly every half year using
"dnf upgrade [etc]". Before that, I upgraded roughly every half y
On 12/11/18 9:59 AM, home user via users wrote:
Now to the greater problem...
When I upgraded to Fedora-28, the text of the grub menu was
significantly down-sized. It also seems to be a (darker?) gray. It is
split into two pieces into the corners of the left side of the left
monitor. It is
(Samuel said)
> I would say to comment out all the lines from 91-98.
Done. Re-booted. No more error messages before the grub menu appears.
Thank-you!
Now to the greater problem...
When I upgraded to Fedora-28, the text of the grub menu was
significantly down-sized. It also seems to b
On 12/10/18 3:51 PM, home user via users wrote:
Rather than deleting lines, I commented them out. It's safer; I can
restore them easily if needed. So now lines 91 to 98 look like this:
---
91 insmod gfxmenu
92 # loadfont ($root)/grub2/themes/system/DejaVuSans-10.pf2
(responding to Ed)
The system was originally installed in early spring of 2013. I would
have used either the then current release, or the immediately preceding
release. I don't recall anything more.
(responding to Samuel)
Rather than deleting lines, I commented them out. It's safer; I can
On 12/9/18 7:39 PM, home user via users wrote:
So it looks to me like I'm missing 3 font files and one text file. How
do I easily get them into the right places so they'll be properly
maintained by weekly "dnf upgrade" updates?
Just delete those lines from the grub config file. As Ed mention
On 12/10/18 7:35 AM, home user via users wrote:
> Hi Samuel,
>
> I see in /etc/grub2.cfg, it says at the top
> ---
> #
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by grub2-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
> ---
(Samuel said)
> Interesting, I don't have any of those files. Check if you do. ...
Results of checking for files referenced in lines 91-98 (done as root):
---
-bash.24[system]: pwd
/boot/grub2/themes/system
-bash.25[system]: ls -la
total 7080
drwxr-xr-x. 2 root root1024 Oct 11 12:
On 12/9/18 3:35 PM, home user via users wrote:
insmod gfxmenu
loadfont ($root)/grub2/themes/system/DejaVuSans-10.pf2
loadfont ($root)/grub2/themes/system/DejaVuSans-12.pf2
loadfont ($root)/grub2/themes/system/DejaVuSans-Bold-14.pf2
loadfont ($root)/grub2/fonts/unicode.pf2
insmod png
set theme=($r
Hi Samuel,
I see in /etc/grub2.cfg, it says at the top
---
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
---
I also see in lines 91-98
---
insmod gfxmenu
lo
On 12/9/18 2:33 PM, home user via users wrote:
1. What is the name and location of that grub config file?
Depending on whether or not you have an EFI system, it's either
/etc/grub2.cfg or /etc/grub2-efi.cfg. Both symlinks exist but only one
of them should be valid.
2. Is there anything I n
Samuel,
1. What is the name and location of that grub config file?
2. Is there anything I need to do after editing the file but before
re-booting?
Thank-you.
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email t
Thank-you for the suggestion, Wolfgang.
I tried "journalctl -n 10" as root.
I did find "boot --", but I saw no hint of the error messages.
I searched for "grub". I searched for "error". No hits.
This is a dual-boot workstation. The error messages
On 12/9/18 3:43 AM, Wolfgang Pfeiffer wrote:
On Sat, Dec 08, 2018 at 08:05:00PM -0700, home user via users wrote:
(Samuel said)
That should be in /boot. Do you have /boot on a separate partition?
How do I determine which partition /boot is in?
The directory mentioned in the error messages is
On Sat, Dec 08, 2018 at 08:05:00PM -0700, home user via users wrote:
(Samuel said)
That should be in /boot. Do you have /boot on a separate partition?
How do I determine which partition /boot is in?
The directory mentioned in the error messages is under /boot as you
said (thank-you!):
-
Thank-you, Joe. /boot is in partition /dev/sda3:
---
-bash.6[boot]: df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs7.8G 0 7.8G 0% /dev
tmpfs 7.9G 59M 7.8G 1% /dev/shm
tmpfs 7.9G 1.7M 7.9G 1% /run
tmpfs 7.9G 0 7
On 12/08/2018 08:05 PM, home user via users wrote:
How do I determine which partition /boot is in?
Three ways. First, you can look in /etc/fstab and see if it's listed
there. Second, you can do the same with /etc/mtab. Third, you can use
df -h which will not only tell you if there's a par
(Samuel said)
> That should be in /boot. Do you have /boot on a separate partition?
How do I determine which partition /boot is in?
The directory mentioned in the error messages is under /boot as you said
(thank-you!):
---
-bash.2[system]: pwd
/boot/grub2/themes/system
-bash.3[syst
On 12/8/18 9:58 AM, home user via users wrote:
By the way, I cannot find a "/grub2" directory.
That should be in /boot. Do you have /boot on a separate partition?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
Good morning,
After upgrading from F27 to F28, when booting up, I get a quickly
disappearing set of error messages just before the grub menu shows up.
Then the grub menu shows up in a very small gray font. The error
messages disappear too quickly for me to get the full text of them. But
by
On 11/13/18 1:17 PM, Stephen Morris wrote:
On 13/11/18 9:42 am, Tom Horsley wrote:
On Tue, 13 Nov 2018 07:30:05 +1100
Stephen Morris wrote:
I would be
questioning where that timeout code in grub.cfg came from
Brand new in fedora 29 (possibly only if you install from scratch,
not upgrade).
M
On 13/11/18 9:42 am, Tom Horsley wrote:
On Tue, 13 Nov 2018 07:30:05 +1100
Stephen Morris wrote:
I would be
questioning where that timeout code in grub.cfg came from
Brand new in fedora 29 (possibly only if you install from scratch,
not upgrade).
Maybe that's new functionality in F29, I'm st
On Tue, 13 Nov 2018 07:30:05 +1100
Stephen Morris wrote:
> I would be
> questioning where that timeout code in grub.cfg came from
Brand new in fedora 29 (possibly only if you install from scratch,
not upgrade).
___
users mailing list -- users@lists.fed
# timeout_style=menu + timeout=0 avoids the countdown code keypress check
set timeout_style=menu
set timeout=0
else
set timeout_style=hidden
set timeout=1
fi
fi
fi
with just
set timeout=5
will I get my grub menu back so I can do things
like choose previou
On Mon, Nov 12, 2018 at 6:55 PM Tom Horsley wrote:
> On Mon, 12 Nov 2018 14:30 Markus Schönhaber wrote:
>> Tom Horsley, Mon, 12 Nov 2018 08:11:12 wrote:
>>>
>>> If I edit the grub.cfg file and replace this absurd
>>> chunk of gibberish:
>>
>> Don't edit grub.cfg manually.
>
> Why not?, that's what
On Mon, 12 Nov 2018 14:30:41 +0100
Markus Schönhaber wrote:
> Tom Horsley, Mon, 12 Nov 2018 08:11:12 -0500:
>
> > If I edit the grub.cfg file and replace this absurd
> > chunk of gibberish:
>
> Don't edit grub.cfg manually.
Why not?, that's what "grubby" does when installing a new kernel.
The
e countdown code keypress check
set timeout_style=menu
set timeout=0
else
set timeout_style=hidden
set timeout=1
fi
fi
fi
with just
set timeout=5
will I get my grub menu back so I can do things
like choose previous kernels?
Or should I just delete the entire ch
t;1" ]; then
> # timeout_style=menu + timeout=0 avoids the countdown code keypress
> check
> set timeout_style=menu
> set timeout=0
> else
> set timeout_style=hidden
> set timeout=1
> fi
> fi
> fi
>
> with just
>
> s
Tom Horsley, Mon, 12 Nov 2018 08:11:12 -0500:
> If I edit the grub.cfg file and replace this absurd
> chunk of gibberish:
Don't edit grub.cfg manually.
> And why isn't there a way to disable the whole
> auto hide nonsense? The only thing it appears to be
> checking is a serial console, no define
1 - 100 of 224 matches
Mail list logo
