On May 18, 2014, at 4:08 PM, Stephen Morris wrote:
> On 05/18/2014 11:57 PM, Michael Schwendt wrote:
>> On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
>>
>>> Hello,
>>>
>>> After an update of teh kernel. the file:
>>> /boot/grub2/grub.cfg is updated.
>>> However thsi file is not upda
On 05/19/2014 08:42 AM, Michael Schwendt wrote:
On Mon, 19 May 2014 08:08:54 +1000, Stephen Morris wrote:
My experience with grubby being run after kernel installs, when I
have been able to get it to run, is that it does recreate the entire
grub.cfg file. For example, I have been in the s
On Mon, 19 May 2014 08:08:54 +1000, Stephen Morris wrote:
> My experience with grubby being run after kernel installs, when I
> have been able to get it to run, is that it does recreate the entire
> grub.cfg file. For example, I have been in the situation where the boot
> menu had an entry
On 05/18/2014 11:57 PM, Michael Schwendt wrote:
On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
Hello,
After an update of teh kernel. the file:
/boot/grub2/grub.cfg is updated.
However thsi file is not update properly.
How? In which way is it not updated "properly"?
Prior to install
On Sun, 18 May 2014 22:30:46 +0200, Patrick Dupre wrote:
> > You've skipped looking at /proc/cmdline (which would also tell the root=
> > kernel parameter used at boot-time).
> It is correct:
> BOOT_IMAGE=/vmlinuz-3.14.3-200.fc20.x86_64
> root=/dev/mapper/VolGrpSys_DK1-root ro rd.md=0 rd.dm=0
>
On May 18, 2014, at 1:42 PM, Patrick Dupre wrote:
> OK,
>
> Thank you.
>
> I understand the mistake:
> in /etc/fstab, there is
> /dev/mapper/VolGrpSys_DK0-root / ext4defaults
> 1 1
> instead of:
> /dev/mapper/VolGrpSys_DK1-root / ext4
> - Original Message -
> From: Michael Schwendt
> Sent: 05/18/14 10:23 PM
> To: users@lists.fedoraproject.org
> Subject: Re: update grub2
>
> On Sun, 18 May 2014 21:42:16 +0200, Patrick Dupre wrote:
>
> > OK,
> >
> > Thank you.
> >
On Sun, 18 May 2014 21:42:16 +0200, Patrick Dupre wrote:
> OK,
>
> Thank you.
>
> I understand the mistake:
> in /etc/fstab, there is
> /dev/mapper/VolGrpSys_DK0-root / ext4 defaults
> 1 1
> instead of:
> /dev/mapper/VolGrpSys_DK1-root / ext
On May 18, 2014, at 10:14 AM, Tom Horsley wrote:
> On Sun, 18 May 2014 18:09:32 +0200
> Patrick Dupre wrote:
>
>> How does it get this information?
>
> I always thought grubby just copied the entry for the
> current kernel and replaced the vmlinuz and initrd
> with the new names it just instal
OK,
Thank you.
I understand the mistake:
in /etc/fstab, there is
/dev/mapper/VolGrpSys_DK0-root / ext4 defaults
1 1
instead of:
/dev/mapper/VolGrpSys_DK1-root / ext4 defaults
1 1
However,
mount gives:
/dev/mapper/VolGrpSys_DK1-root
On Sun, 18 May 2014 18:09:32 +0200, Patrick Dupre wrote:
> OK, I understand, my point is that the inserted part is wrong!
> This is wrong:
> linux /vmlinuz-3.14.3-200.fc20.x86_64 root=/dev/mapper/VolGrpSys_DK0-root
>
> It should be DK1 (not DK0). How does it get this information?
/sbin/new-ke
On Sun, 18 May 2014 18:09:32 +0200
Patrick Dupre wrote:
> How does it get this information?
I always thought grubby just copied the entry for the
current kernel and replaced the vmlinuz and initrd
with the new names it just installed, but it may be
more complicated than that.
--
users mailing li
>
> > Hello,
> >
> > After an update of teh kernel. the file:
> > /boot/grub2/grub.cfg is updated.
> > However thsi file is not update properly.
>
> How? In which way is it not updated "properly"?
>
> Prior to installing a new kernel, you could save a copy of grub.cfg,
> install a new kernel p
On Sun, 18 May 2014 14:57:14 +0200, Patrick Dupre wrote:
> Hello,
>
> After an update of teh kernel. the file:
> /boot/grub2/grub.cfg is updated.
> However thsi file is not update properly.
How? In which way is it not updated "properly"?
Prior to installing a new kernel, you could save a copy o
Hello,
After an update of teh kernel. the file:
/boot/grub2/grub.cfg is updated.
However thsi file is not update properly.
If I run:
grub2-mkconfig -o /boot/grub2/grub.cfg
then the file is OK.
Somebody can tell me what is going on?
Thank.
===
On Tue, 24 Dec 2013 11:52:11 -0700 Chris Murphy
wrote:
>
> On Dec 24, 2013, at 9:28 AM, Ranjan Maitra
> wrote:
>
> >>
> >>
> >> grub2-install --debug /dev/sda
>
>
> Looks good.
>
> >
> >> bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
>
> FYI:
> Line 79, I do not see resume= having bee
On Dec 24, 2013, at 9:28 AM, Ranjan Maitra
wrote:
>>
>>
>> grub2-install --debug /dev/sda
Looks good.
>
>> bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
FYI:
Line 79, I do not see resume= having been added to /etc/default/grub, therefore
it won't be in the grub.cfg.
Line 127/128, it f
On Tue, 24 Dec 2013 18:53:26 +0100 Michael Schwendt
wrote:
> On Tue, 24 Dec 2013 10:28:37 -0600, Ranjan Maitra wrote:
>
> > > bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
> >
> > Uploading (8.6KiB)...
> > http://ur1.ca/g93u5 -> http://paste.fedoraproject.org/64214/02391138
>
> So, the initrd
On Tue, 24 Dec 2013 10:28:37 -0600, Ranjan Maitra wrote:
> > bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
>
> Uploading (8.6KiB)...
> http://ur1.ca/g93u5 -> http://paste.fedoraproject.org/64214/02391138
So, the initrd for the F20 release kernel 3.11.10-301.fc20 is missing
here, too:
+ echo
On Tue, 24 Dec 2013 09:04:27 -0700 Chris Murphy
wrote:
>
> On Dec 24, 2013, at 2:12 AM, Michael Schwendt wrote:
>
> > On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
> >
> >> ### BEGIN /etc/grub.d/10_linux ###
> >> menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora
On Dec 24, 2013, at 2:12 AM, Michael Schwendt wrote:
> On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
>
>> ### BEGIN /etc/grub.d/10_linux ###
>> menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora
>> --class gnu-linux --class gnu --class os $menuentry_id_option
>> 'g
On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
> ### BEGIN /etc/grub.d/10_linux ###
> menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora
> --class gnu-linux --class gnu --class os $menuentry_id_option
> 'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0
Thanks!
On Mon, 23 Dec 2013 22:25:52 -0700 Chris Murphy
wrote:
>
> On Dec 23, 2013, at 9:32 PM, Ranjan Maitra
> wrote:
>
> > So I will add resume=uuid="" (gigantic
> > alphanumeric number) to the GRUB_CMDLINE_LINUX?
>
> Correct.
>
>
> > Here is what
> > /etc/default/grub reads current
On Dec 23, 2013, at 9:32 PM, Ranjan Maitra
wrote:
> So I will add resume=uuid="" (gigantic
> alphanumeric number) to the GRUB_CMDLINE_LINUX?
Correct.
> Here is what
> /etc/default/grub reads currently:
>
> GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)
On Mon, 23 Dec 2013 18:52:45 -0700 Chris Murphy
wrote:
>
> On Dec 22, 2013, at 3:04 PM, Ranjan Maitra
> wrote:
> >
> > So, add this resume=/dev/sda2 to the stuff on GRUB_CMDLINE_LINUX ? Any
> > way to do this without the hardcoding for resume?
>
> /etc/sysconfig/grub is a link to /etc/defau
On Dec 22, 2013, at 3:04 PM, Ranjan Maitra
wrote:
>
> So, add this resume=/dev/sda2 to the stuff on GRUB_CMDLINE_LINUX ? Any
> way to do this without the hardcoding for resume?
/etc/sysconfig/grub is a link to /etc/default/grub. You should use
resume=uuid= and insert the blkid uuid for swap
On Mon, 23 Dec 2013 21:18:32 +0100 Michael Schwendt
wrote:
> On Mon, 23 Dec 2013 13:01:46 -0600, Ranjan Maitra wrote:
>
> > sudo /bin/kernel-install add
> > 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
> > grubby fatal error: unable to find a suitable template
>
> Gre
On Mon, 23 Dec 2013 13:01:46 -0600, Ranjan Maitra wrote:
> sudo /bin/kernel-install add
> 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
> grubby fatal error: unable to find a suitable template
Great! As expected.
Save a backup of the current grub.cfg file. It may make s
On Mon, 23 Dec 2013 18:53:40 +0100 Michael Schwendt
wrote:
> On Mon, 23 Dec 2013 08:20:53 -0600, Ranjan Maitra wrote:
>
> > > You could become superuser root, then run exactly the kernel-install
> > > command found above, and check the exit return code and watch out for
> > > any warning/error i
On Mon, 23 Dec 2013 08:20:53 -0600, Ranjan Maitra wrote:
> > You could become superuser root, then run exactly the kernel-install
> > command found above, and check the exit return code and watch out for
> > any warning/error it might print.
>
> Thanks!
> $ sudo rpm -q --scripts kernel|tail -2
>
On Mon, 23 Dec 2013 11:52:13 +0100 Michael Schwendt
wrote:
> On Sun, 22 Dec 2013 16:04:47 -0600, Ranjan Maitra wrote:
>
> > OK, thanks! I am not sure I understood this correctly, but here is what
> > I did:
> >
> > sudo yum update -y (this brings back the new kernel and installs it).
> >
> > r
On Sun, 22 Dec 2013 16:04:47 -0600, Ranjan Maitra wrote:
> OK, thanks! I am not sure I understood this correctly, but here is what
> I did:
>
> sudo yum update -y (this brings back the new kernel and installs it).
>
> rpm -q --scripts kernel|tail -2
> posttrans scriptlet (using /bin/sh):
> /bin/
On Sun, 22 Dec 2013 22:47:05 +0100 Michael Schwendt
wrote:
> On Sun, 22 Dec 2013 15:26:32 -0600, Ranjan Maitra wrote:
>
> > I removed the new kernel, updated grub2-mkconfig and rebooted into the
> > old kernel. Does this not bring it back to the old setup (before
> > installation of the new kern
On Sun, 22 Dec 2013 15:26:32 -0600, Ranjan Maitra wrote:
> I removed the new kernel, updated grub2-mkconfig and rebooted into the
> old kernel. Does this not bring it back to the old setup (before
> installation of the new kernel). Or if your question was if the problem
> is reproducible in the se
Thanks!
On Sun, 22 Dec 2013 21:08:05 +0100 Michael Schwendt
wrote:
> On Sun, 22 Dec 2013 14:03:08 -0600, Ranjan Maitra wrote:
>
> > OK, I have downdated the kernel, run grub2-mkconfig so we should be
> > back on the same plane as before.
>
> "Should be"? Do you mean the problem is reproducible
On Sun, 22 Dec 2013 14:03:08 -0600, Ranjan Maitra wrote:
> OK, I have downdated the kernel, run grub2-mkconfig so we should be
> back on the same plane as before.
"Should be"? Do you mean the problem is reproducible after simple
downgrade of the kernel package?
> An important thing to note is th
On Sun, 22 Dec 2013 20:14:27 +0100 Michael Schwendt
wrote:
> On Sun, 22 Dec 2013 08:54:54 -0600, Ranjan Maitra wrote:
>
> > Hi,
> >
> > I updated using yum last night and while the new 3.12.5 kernel was
> > installed, it does not show up on grub. So, I did the following:
> >
> > sudo grub2-mkc
On Sun, 22 Dec 2013 08:54:54 -0600, Ranjan Maitra wrote:
> Hi,
>
> I updated using yum last night and while the new 3.12.5 kernel was
> installed, it does not show up on grub. So, I did the following:
>
> sudo grub2-mkconfig -o /boot/grub2/grub.cfg
> Generating grub.cfg ...
> Found linux image:
Hi,
I updated using yum last night and while the new 3.12.5 kernel was
installed, it does not show up on grub. So, I did the following:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64
Found initrd image: /boot/initramfs-3
39 matches
Mail list logo