tree
so
I am guessing that grub2 somehow knows the proper, default boot image
-
even though the default does not have a menuentry in grub.cfg?
I bet it's related to BootLoaderSpec. If you look at the
### BEGIN /etc/grub.d/10_linux ###
section of grub.cfg you will see:
# The b
s the proper, default boot image -
> even though the default does not have a menuentry in grub.cfg?
I bet it's related to BootLoaderSpec. If you look at the
### BEGIN /etc/grub.d/10_linux ###
section of grub.cfg you will see:
# The blscfg command parses the BootLoaderSpec files stored
Sway files are in the /boot tree so
I am guessing that grub2 somehow knows the proper, default boot image -
even though the default does not have a menuentry in grub.cfg?
A pointer to a link for info would be great . .
Thanks!
Phil.
--
Philip Rhoa
menus is no longer reading /boot/grub2/grub.cfg, which I believe was
introduced into F36 and still continued in F37 until now, but has
reverted back to reading /boot/efi/EFI/fedora/grub.cfg.
Does anyone know why this version of grub seems to have moved
away from the philosophy of UEFI and l
grub2/grub.cfg, which I believe was
introduced into F36 and still continued in F37 until now, but has
reverted back to reading /boot/efi/EFI/fedora/grub.cfg.
Does anyone know why this version of grub seems to have moved away
from the philosophy of UEFI and legacy boots using the same config file?
Hi,
With the install of grub2 2.06.67 in F37 and playing around with
trying to eliminate the unicode font signing issue highlighted in
another thread, I've now found that grub2 when displaying its boot menus
is no longer reading /boot/grub2/grub.cfg, which I believe was
introduced
On 26 Aug at 09:38, Tom Horsley wrote:
> On Sat, 27 Aug 2022 00:27:24 +1000
> Philip Rhoades via users wrote:
> Don't recognize this problem specifically, but I
> have a USB stick with a bunch of iso files on it and a grub
> configured to let me boot any of them. I used the info at:
There is a FA
On Sat, 27 Aug 2022 00:27:24 +1000
Philip Rhoades via users wrote:
> Can anyone suggest what the problem is and how to resolve it?
Don't recognize this problem specifically, but I
have a USB stick with a bunch of iso files on it and a grub
configured to let me boot any of them. I used the info at
People,
My old Zenbook has problems running LiveUSBs so I generally use dnf
updates but the last update to F36 has caused problems with audio that I
can't resolve so I want to do a clean install and have been trying to do
this via running the iso from a grub2 config by adding stuff to
40_cust
On Sun, 2022-07-24 at 07:39 -0400, Jonathan Billings wrote:
> This is why Fedora always suggests using grubby.
Actually, I can't remember how I changed the kernel options on Fedora
36, though I don't recall using grubby. I've only done one Fedora
installation recently.
--
uname -rsvp
Linux 3
On Jul 23, 2022, at 23:54, Tim via users wrote:
>
> My preference has been a third option:
>
> First hand edit the grub.cfg file that we're not supposed to (because
> our changes won't be permanent, the next kernel install will recreate
> the whole thing from a
> On 24 Jul 2022, at 00:40, Jonathan Billings wrote:
>
> On Jul 23, 2022, at 16:15, Patrick Dupre wrote:
>>
>> What should I do to have
>> nouveau.modeset=0
>> added to the grub.cfg files ?
>
> There are two options:
> 1.) Edit /etc/default/
My preference has been a third option:
First hand edit the grub.cfg file that we're not supposed to (because
our changes won't be permanent, the next kernel install will recreate
the whole thing from a different mould), put in my kernel line changes
onto one of the boot choices, and reboo
On Jul 23, 2022, at 16:15, Patrick Dupre wrote:
>
> What should I do to have
> nouveau.modeset=0
> added to the grub.cfg files ?
There are two options:
1.) Edit /etc/default/grub and add it to the kernel command line variable, then
run “grub2-mkconfig -o /boot/grub2/grub.cfg”
(No
Hello,
What should I do to have
nouveau.modeset=0
added to the grub.cfg files ?
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9
On Fri, 27 Dec 2019 15:05:13 -0500
Robert McBroom via users wrote:
>
> $ man 5 console-setup
> No manual entry for console-setup in section 5
dnf install console-setup
Summary : Tools for configuring the console using X Window System
key maps
Description :
This package provides the console
On 12/27/2019 01:05 PM, Robert McBroom via users wrote:
never encountered sections to man before
You'll find a fairly brief explanation of them at the beginning of man's
own man page, although it doesn't list what the various sections are
for. Generally, of course, you only need to specify
On 12/24/19 1:47 PM, stan via users wrote:
On Tue, 24 Dec 2019 10:32:48 -0500
Robert McBroom via users wrote:
With the deprecating of the "vga=791" specification, what is the
method of passing the video resolution to the kernel in a text mode
boot? The setting in grub.cfg gives the
On Tue, 24 Dec 2019 10:32:48 -0500
Robert McBroom via users wrote:
> With the deprecating of the "vga=791" specification, what is the
> method of passing the video resolution to the kernel in a text mode
> boot? The setting in grub.cfg gives the grub menu resolution but the
With the deprecating of the "vga=791" specification, what is the method
of passing the video resolution to the kernel in a text mode boot? The
setting in grub.cfg gives the grub menu resolution but the kernel drops
back to 640x480 when it starts unless the vga specification is add
, 5 Dec 2019 at 19:04, Samuel Sieb <mailto:sam...@sieb.net>> wrote:
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> Updated from Fedora 29 to 31 on a legacy system. Kernel
updates no
> longer update grub.cfg to the new kernel. Ran
grub2-mkconfig -o
> /b
On 12/6/19 3:22 PM, Robert McBroom via users wrote:
On 12/6/19 5:41 PM, Samuel Sieb wrote:
If this is an old install, you might need to update the bootloader
bits that are stored in the mbr. It might too old to support BLS.
That's why if it's not an EFI system, you should run grub2-install to
sam...@sieb.net>> wrote:
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> Updated from Fedora 29 to 31 on a legacy system. Kernel
updates no
> longer update grub.cfg to the new kernel. Ran
grub2-mkconfig -o
> /boot/grub2/grub.cfg which finds Windows and Centos 6 b
9 8:02 AM, Robert McBroom via users wrote:
> Updated from Fedora 29 to 31 on a legacy system. Kernel
updates no
> longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
> /boot/grub2/grub.cfg which finds Windows and Centos 6 but none
of the
> Fedora kernels.
Updated from Fedora 29 to 31 on a legacy system. Kernel
updates no
> longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
> /boot/grub2/grub.cfg which finds Windows and Centos 6 but none
of the
> Fedora kernels. /boot is in its own partition and the Centos
ker
stem. Kernel updates no
> longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
> /boot/grub2/grub.cfg which finds Windows and Centos 6 but none
of the
> Fedora kernels. /boot is in its own partition and the Centos
kernels
> are in the Centos partit
On 12/6/19 2:06 AM, Anthony F McInerney wrote:
On Thu, 5 Dec 2019 at 19:04, Samuel Sieb <mailto:sam...@sieb.net>> wrote:
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
> longer update grub
On 12/6/19 1:45 AM, Samuel Sieb wrote:
On 12/5/19 10:31 PM, Robert McBroom via users wrote:
On 12/5/19 7:22 PM, Tom Horsley wrote:
On Thu, 5 Dec 2019 19:16:56 -0500
Robert McBroom via users wrote:
Where are the settings for
$kernelopts entered?
They are as hidden as they can make them in the
ed but the
suggested change was gone before it could be read.
AFAIK, kernel parameter should go into /etc/default/grub
the line starts with "GRUB_CMDLINE_LINUX"
and a sequencing run of
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o
/boot/efi/EFI/fedora/grub.cfg ||
On Fri, 2019-12-06 at 07:06 +, Anthony F McInerney wrote:
>
>
> On Thu, 5 Dec 2019 at 19:04, Samuel Sieb wrote:
> > On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> > > Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
> > > longer
On Thu, 5 Dec 2019 at 19:04, Samuel Sieb wrote:
> On 12/5/19 8:02 AM, Robert McBroom via users wrote:
> > Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
> > longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
> > /boot/grub2/grub.cfg wh
On 12/5/19 10:31 PM, Robert McBroom via users wrote:
On 12/5/19 7:22 PM, Tom Horsley wrote:
On Thu, 5 Dec 2019 19:16:56 -0500
Robert McBroom via users wrote:
Where are the settings for
$kernelopts entered?
They are as hidden as they can make them in the grubenv
file which usually lives for re
On 12/5/19 7:22 PM, Tom Horsley wrote:
On Thu, 5 Dec 2019 19:16:56 -0500
Robert McBroom via users wrote:
Where are the settings for
$kernelopts entered?
They are as hidden as they can make them in the grubenv
file which usually lives for real down in the efi
directories and has a symlink other
On Thu, 5 Dec 2019 19:16:56 -0500
Robert McBroom via users wrote:
> Where are the settings for
> $kernelopts entered?
They are as hidden as they can make them in the grubenv
file which usually lives for real down in the efi
directories and has a symlink other places.
grub2-editenv can be used t
On 12/5/19 2:03 PM, Samuel Sieb wrote:
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
/boot/grub2/grub.cfg which finds Windows and Centos 6 but none of the
On 12/5/19 8:02 AM, Robert McBroom via users wrote:
Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
/boot/grub2/grub.cfg which finds Windows and Centos 6 but none of the
Fedora kernels. /boot is in its own
Updated from Fedora 29 to 31 on a legacy system. Kernel updates no
longer update grub.cfg to the new kernel. Ran grub2-mkconfig -o
/boot/grub2/grub.cfg which finds Windows and Centos 6 but none of the
Fedora kernels. /boot is in its own partition and the Centos kernels
are in the Centos
Hi François,
I think I have a similar problem with an old server I might have
installed with a Fedora 26 or 27 where I used to have issues in the
past kernel updates used to generated grub.cfg with plenty of '=' chars
at the end of the file.
It seemed to be reoslved until last week
Le 16/12/2018 à 11:07, francis.montag...@inria.fr a écrit :
>
> Bonjour.
>
> On Sun, 16 Dec 2018 09:24:44 +0100 François Patte wrote:
>> I corrected this file using grub2-mkconfig. So, my question is: why the
>> kernel script is unable to correctly use grub2-mkconfig?
>
> As far as I know it us
Bonjour.
On Sun, 16 Dec 2018 09:24:44 +0100 François Patte wrote:
> I corrected this file using grub2-mkconfig. So, my question is: why the
> kernel script is unable to correctly use grub2-mkconfig?
As far as I know it uses grubby.
I personnaly prefer to use grub2-mkconfig. See my previous pos
On 12/02/2016 07:33 PM, Michael D. Setzer II wrote:
In doing more research, I am finding an error that might be cuasing the
grub2-mkconfig to not work.
Manually putting the lines in the grub.cfg file, I can boot to the windows 10
with no problem.
Just tried to mount the windows partition
In doing more research, I am finding an error that might be cuasing the
grub2-mkconfig to not work.
Manually putting the lines in the grub.cfg file, I can boot to the windows 10
with no problem.
Just tried to mount the windows partition from the fedora 25, and get the
following error??
/sbin
On 2 Dec 2016 at 18:54, jd1008 wrote:
Subject:Re: Windows missing from grub.cfg after updating to
Fedora 25?
To: Community support for Fedora users
From: jd1008
Date sent: Fri, 2 Dec 2016 18:54:05 -0700
Send reply to
On 12/02/2016 06:34 PM, Michael D. Setzer II wrote:
I just recently updated a system from Fedora 24 to Fedora 25, and
everything seemed to go just fine. Just noticed that windows is no longer on
the grub boot menu? Reran grub2-mkconfig -o /boot/grub2/grub.cfg and still
nothing. entries for 30
I just recently updated a system from Fedora 24 to Fedora 25, and
everything seemed to go just fine. Just noticed that windows is no longer on
the grub boot menu? Reran grub2-mkconfig -o /boot/grub2/grub.cfg and still
nothing. entries for 30-osprober show nothing. Running os-prober also shows
On 10/12/2015 11:18 PM, Gordon Messmer wrote:
On 10/12/2015 07:55 PM, sean darcy wrote:
i really don't want to edit grub.cfg directly, and I can't figure out
the templates.
grub2-mkconfig should generate a new configuration entirely.
Installing a kernel will run:
/bin/kernel-i
On 10/12/2015 07:55 PM, sean darcy wrote:
i really don't want to edit grub.cfg directly, and I can't figure out
the templates.
grub2-mkconfig should generate a new configuration entirely.
Installing a kernel will run:
/bin/kernel-install add /boot/vmlinuz-
I'd sugge
By a combination of ways, I've upgraded from 21 to 22.
One of my problems is that although the 22 kernel is installed, grub
doesn't show it on boot. I've erased kernel. kernel-core, then
reinstalled. No change in grub.cfg.
i'd expect an install script in the package to
On Fri, 2014-10-24 at 18:24 -0600, Chris Murphy wrote:
> Companies do not spend hundreds of millions of dollars (conservatively
> estimated at this point) completely retooling firmware to something
> that has about as many lines of code as the linux kernel, and
> *requiring* manufacturers to enable
Chris Murphy writes:
>
> That is correct, but it is a prerequisite for being able to even trust
> userspace if kernel space is already compromised then it's a problem.
I dont trust the Companies that their proprietary Bioses and UEFIs are
not itself a rootkit. So the only solution to fix this pr
On Oct 25, 2014, at 7:35 AM, Stefan Huchler wrote:
> Chris Murphy writes:
>
> I try to not answer to much, because I dont want to argue to much, I
> just wanted a solution for my problem and this had nothing to do with
> secure boot, but I give my 2 cents to it.
Indeed, it's completely on me
Maybe it was back then no GPT problem, this tool doenst support gpt, but
uefi is the next thing, you need to install the right 64bit uefi grub
version or something.
The point is it adds much more complexity and I personaly gain NOTHING
of it, so why the hell should I use it?
Yes because at some
Chris Murphy writes:
I try to not answer to much, because I dont want to argue to much, I
just wanted a solution for my problem and this had nothing to do with
secure boot, but I give my 2 cents to it.
Did you really happen to see such a exploit in the wild that somebody
used kvm to start window
On Oct 22, 2014, at 3:14 PM, Stefan Huchler wrote:
> Chris Murphy writes:
>
>
> So first of all, I am thankful that u helped me to understand the
> problem I was shure I somehow on a interupted dnf process or something I
> damaged something in fedora, because I did not remember or notice that
Mickey writes:
> I don't have uefi on my box and I'am getting the same error message
> that pops up in the Notification Jobs in my system tray.
Did you answer to the wrong thread or to what message do you refer?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subsc
On 10/22/2014 05:14 PM, Stefan Huchler wrote:
Chris Murphy writes:
So first of all, I am thankful that u helped me to understand the
problem I was shure I somehow on a interupted dnf process or something I
damaged something in fedora, because I did not remember or notice that
it did not updat
Chris Murphy writes:
So first of all, I am thankful that u helped me to understand the
problem I was shure I somehow on a interupted dnf process or something I
damaged something in fedora, because I did not remember or notice that
it did not update grub from the beginning.
Maybe I make a switch
;s about as close to not supported as it gets.
> I installed several gentoos in the past and arch linuxes
> and stuff, so I am able to install stuff by my own and can setup the
> grub stuff and so on. So now that I am a fedora User I should forget all
> that and only use the official i
can install fedora? which
windows pc each windows pc and nearly no android "pc". Yes thanks google
you done great in removing gnu from linux for good.
> Fedora Project, and by support it means an issue we'd block release on
> if it didn't work correctly. You can do what
On 21.10.2014 04:30, Chris Murphy wrote:
>
> On Oct 20, 2014, at 9:42 PM, poma wrote:
>
>> On 21.10.2014 03:26, Chris Murphy wrote:
>>>
>>> On Oct 20, 2014, at 8:53 PM, poma wrote:
>>>
On 20.10.2014 17:14, Chris Murphy wrote:
>
> The bug is in grubby, which is what's called fr
On 21.10.2014 16:17, Chris Murphy wrote:
>
> On Oct 21, 2014, at 8:07 AM, Stefan Huchler wrote:
>
>> Chris Murphy writes:
>>
>>> Where you get bad results is with, e.g. a pre-existing legacy OS like
>>> Windows XP, where it's not aligned and any subsequent partition is
>>> also not aligned. In
t support swapfiles. The officially supported layout for Btrfs
>> on UEFI is: EFI System partition, /boot on ext4, Btrfs with root and
>> home subvols mounted at / and /home respectively, and swap. That's
>> four partitions.
>
> the officially supported by whom? Redhat? I d
Chris Murphy writes:
> Where you get bad results is with, e.g. a pre-existing legacy OS like
> Windows XP, where it's not aligned and any subsequent partition is
> also not aligned. In that case, even a Btrfs volume wouldn't be
> aligned.
I dont want to care at all, I dont want to know if to use
On Oct 20, 2014, at 9:42 PM, poma wrote:
> On 21.10.2014 03:26, Chris Murphy wrote:
>>
>> On Oct 20, 2014, at 8:53 PM, poma wrote:
>>
>>> On 20.10.2014 17:14, Chris Murphy wrote:
>>>
The bug is in grubby, which is what's called from within kernel packages
to update bootloade
On 21.10.2014 03:10, Matthew Miller wrote:
> On Tue, Oct 21, 2014 at 02:53:42AM +0200, poma wrote:
>>> The bug is in grubby, which is what's called from within kernel
>>> packages to update bootloader configuration scripts: GRUB legacy,
>>> GRUB2, syslinux, yaboot, and probably a bunch of other boo
On 21.10.2014 03:26, Chris Murphy wrote:
>
> On Oct 20, 2014, at 8:53 PM, poma wrote:
>
>> On 20.10.2014 17:14, Chris Murphy wrote:
>>
>>>
>>> The bug is in grubby, which is what's called from within kernel packages to
>>> update bootloader configuration scripts: GRUB legacy, GRUB2, syslinux,
On Oct 20, 2014, at 8:53 PM, poma wrote:
> On 20.10.2014 17:14, Chris Murphy wrote:
>
>>
>> The bug is in grubby, which is what's called from within kernel packages to
>> update bootloader configuration scripts: GRUB legacy, GRUB2, syslinux,
>> yaboot, and probably a bunch of other bootloade
kernel. It
>> fails because it doesn't understand subvolumes.
>
> ok interesting, thx for clearification.
>
>> There is no grub-update or update-grub on Fedora or upstream. All it
>> does is call 'grub2-mkconfig -o /boot/grub2/grub.cfg' (on BIOS
>&g
On Tue, Oct 21, 2014 at 02:53:42AM +0200, poma wrote:
> > The bug is in grubby, which is what's called from within kernel
> > packages to update bootloader configuration scripts: GRUB legacy,
> > GRUB2, syslinux, yaboot, and probably a bunch of other bootloaders
> > are all supported by grubby. It
On 20.10.2014 17:14, Chris Murphy wrote:
>
> The bug is in grubby, which is what's called from within kernel packages to
> update bootloader configuration scripts: GRUB legacy, GRUB2, syslinux,
> yaboot, and probably a bunch of other bootloaders are all supported by
> grubby. It looks at the e
; fails because it doesn't understand subvolumes.
ok interesting, thx for clearification.
> There is no grub-update or update-grub on Fedora or upstream. All it
> does is call 'grub2-mkconfig -o /boot/grub2/grub.cfg' (on BIOS
> systems, it's different on UEFI system
te-grub on Fedora or upstream. All it does is
call 'grub2-mkconfig -o /boot/grub2/grub.cfg' (on BIOS systems, it's different
on UEFI systems).
>
> cant I not somehow disable this security-check or has this software a
> own fork of the update-grub command?
>
> I d
thx so far, I dont see one of the 2 solutions a good solution for me, I
dont see packages for this grubby version, I dont want to compile it
myself, it doesnt seem to be fixed soon, it seems that this patch will
not land for fedora 21, so I have to deal with that manual update... for
another year o
sts baked directly into grubby, and the message is saying that the
test has failed so grub.cfg isn't being modified.
>
> And is this normal?
Yes, because grubby doesn't grok Btrfs subvolumes, and the maintainer doesn't
really see the point for /boot on Btrfs anyway. There a
here some infos
dnf reinstall kernel -v
http://ix.io/eMK
and my rootfs/home (btrfs) mounts:
/dev/sda on / type btrfs (rw,noatime,compress=lzo,ssd,discard,space_cache)
/dev/sda on /home type btrfs (rw,noatime,compress=lzo,ssd,discard,space_cache)
I don't know how to debug that further or where
hmm I have direct a btrfs filesystem on my ssd without partitions direct
on /dev/sda. grub supports it, so I dont see a problem with that. And
because u have subvolumes I dont see a reason to use partitions anymore.
I think your suggestion sounds logical, but I am pretty shure that it
worked in th
On Oct 13, 2014, at 1:04 PM, Stefan Huchler wrote:
> When I update to a new kernel with dnf or yum, it
> installs it, creates a working initramfs file like it should, but it does
> not update grub.cfg in /boot/grub2/ .
>
>
> I see following error:
>
> grubby fatal
When I update to a new kernel with dnf or yum, it
installs it, creates a working initramfs file like it should, but it does
not update grub.cfg in /boot/grub2/ .
I see following error:
grubby fatal error: unable to find a suitable template
when I do then:
sudo grub2-mkconfig -o /boot/grub2
ions later, those changes are NOT 'automagically'
progressed into a new /etc/default/grub. I guess this has to be done manually.
The "grub2-mkconfig -o /boot/grub2/grub.cfg" uses the settings in
/etc/default/grub to create the grub.cfg file. Hence, without changing the
d
On Jan 22, 2014, at 1:23 AM, Stub wrote:
> Hi,
>
> I have F18 on an i686 PC.
>
> I have changed my boot up sequence from logical volumes to regular partitions.
> Upon regenerating the grub2 boot process, the grub2 keeps creating a
> /boot/grub2/grub.cfg file that refer
Hi,
I have F18 on an i686 PC.
I have changed my boot up sequence from logical volumes to regular partitions.
Upon regenerating the grub2 boot process, the grub2 keeps creating a
/boot/grub2/grub.cfg file that refers to the non-existing logical volumes.
Hence, the boot process fails with a
Lee,
thanks for your response.
I don't understand what you are saying.
how does
"just running mkconfig" do what you want?
I routinely use mkconfig but only
after I have made a change in grub.d/40_custom
Jack
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscriptio
t;
> "Changes to grub.cfg are enacted by editing etc/default/grub and files in
> the etc/grub.d directory, particularly 10_linux and 40_custom, and then
> running the grub2-mkconfig command with root privileges."
>
>
> BUT 10_linux in /etc/grub.d has no menuentry's, just
from fedora docs:
"Changes to grub.cfg are enacted by editing etc/default/grub and files in
the etc/grub.d directory, particularly 10_linux and 40_custom, and then
running the grub2-mkconfig command with root privileges."
BUT 10_linux in /etc/grub.d has no menuentry's, just a
f16 preupgrade from f14, and is apparently working well.
But os-prober has put in lot of menuentries, many of which
are either blatantly wrong, or outdated,
which I would like to remove from grub.cfg.
fedora wiki generally advises it is not safe to edit grub.cfg.
Can I safely edit grub.cfg if
On 06/21/2012 11:47 PM, JD wrote:
> After yum update (which produced no error messages)
> kernel-3.4.2-1 was installed. So, because of my prior
> problems with yum updating the kernel, I decided to
> look at grub.cfg.
>
> Again, dracut did not produce the initramfs for the new
After yum update (which produced no error messages)
kernel-3.4.2-1 was installed. So, because of my prior
problems with yum updating the kernel, I decided to
look at grub.cfg.
Again, dracut did not produce the initramfs for the new kernel.
I had to manually run
dracut -f /boot/initramfs-3.4.2-1
kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
> > grub.cfg had not been changed to reflect the new kernel. I updated to
> > F17 3.4 from updates-testing and the problem appears to have gone
> > away, i.e. grub is now correct.
> >
> > So it looks like the iss
at, ...) and a panic backtrace. This was completely reproducible.
>
> I then noticed that the running kernel was still
> kernel-3.3.7-1.fc16.x86_64, despite the fact that
> kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
> grub.cfg had not been changed to reflect the
at, ...) and a panic backtrace. This was completely reproducible.
>
> I then noticed that the running kernel was still
> kernel-3.3.7-1.fc16.x86_64, despite the fact that
> kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
> grub.cfg had not been changed to reflect the new
Patrick O'Callaghan wrote:
>On a related note: how does one capture the console output when a panic
>like this occurs? It isn't in any log files (maybe by this time there
>isn't a filesystem) and it's a chore to have to copy it all by hand,
>which is why I haven't bothered in this case.
I use a
This was completely reproducible.
>
> I then noticed that the running kernel was still
> kernel-3.3.7-1.fc16.x86_64, despite the fact that
> kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
> grub.cfg had not been changed to reflect the new kernel. I updated to
> F17 3.
On 06/04/2012 08:49 AM, Patrick O'Callaghan wrote:
So it looks like the issue was that grub.cfg should have been changed
during the preupgrade, but wasn't. Has anyone else seen this?
Yep. Happened to me, too. I saw it mentioned somewhere in a bugzilla
issue about the kernel
the running kernel was still
kernel-3.3.7-1.fc16.x86_64, despite the fact that
kernel-3.3.7-1.fc17.x86_64 had been installed by preupgrade, i.e.
grub.cfg had not been changed to reflect the new kernel. I updated to
F17 3.4 from updates-testing and the problem appears to have gone away,
i.e. grub is
94 matches
Mail list logo
