Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #228865

Re: Fixing a Grub Foul-up, Not There Yet.

Show all headers | View raw

Martin McCormick composed on 2020-11-21 12:49 (UTC-0600):

> 	I appreciate the good suggestions I have gotten from
> several of you so far.

Save yourself many keystrokes by using the symlinks in the root directory instead
of the long-winded full version-named /boot/vmlinuz-4.19.0-5-686-pae....

So,
	linux (hd0,1)/boot/mlinuz-4.19.0-5-686-pae root=/dev/sda1
becomes
	linux (hd0,1)/vmlinuz root=/dev/sda1
and
	initrd (hd0,1)/boot/initrd.img-4.19.0-5-686-pae
becomes
	initrd (hd0,1)/initrd.img

The root also contains symlinks with .old appended for the previously installed
kernel.

Note that root=/dev/sda1 is an override to the root definition in the initrd. In
your case simply trying to recover boot ability, I seriously doubt you need to
make that override, and thus can safely leave root=/dev/sda1 off the linux line.

Also, unless your old 32bit PC has more than 2G of RAM, it's very unlikely you can
enjoy any advantage from PAE kernels. So, just keep linux-image-version-686
installed instead of linux-image-version-686-pae. It's not much typing saved, but
I imagine you welcome as much saving as you can get.

HTH
-- 
Evolution as taught in public schools, like religion,
	is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-16 20:00 +0100
  Re: Fixing a Grub Foul-up Dan Ritter <dsr@randomstring.org> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-17 04:00 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 05:00 +0100
      Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-12-01 15:40 +0100
        Re: Fixing a Grub Foul-up Solved! "Martin McCormick" <martin.m@suddenlink.net> - 2020-12-01 21:10 +0100
  Re: Fixing a Grub Foul-up John Boxall <jboxall47@gmail.com> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up Kenneth Parker <sea7kenp@gmail.com> - 2020-11-17 03:00 +0100
  Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-11-17 00:00 +0100
    Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-21 20:00 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-21 20:40 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 00:10 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-22 01:20 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Kushal Kumaran <kushal@locationd.net> - 2020-11-22 02:10 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Dan Ritter <dsr@randomstring.org> - 2020-11-22 01:10 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 04:50 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 18:00 +0100

csiph-web