> On Aug 6, 2023, at 10:13, John Paul Adrian Glaubitz > <glaub...@physik.fu-berlin.de> wrote: > > Hi! > > On Sun, 2023-08-06 at 15:08 +0000, Pedro Miguel Justo wrote: >> ow much automation can be used for bisecting a problem on grub? >> >> My rx2660 is considerably up to date and still booting. >> >> What do you recommend for best bisecting the offending step? > > You cannot automate this as the machine needs to be rebooted all the time.
That is what I was expecting. > > Basically, you need to do the following: > > # apt build-dep grub2 Sourt of embarrassing question but… what is the deb-src right entry for debian ports? > # git clone git://git.savannah.gnu.org/grub.git > # cd grub > # git bisect start > # git bisect good grub-2.06 > # git bisect bad HEAD > > Then build grub, install and testboot: > > # ./bootstrap && ./configure && make && make install > # /usr/local/sbin/grub-install /dev/sda (when sda is your primary disk) > > Reboot the machine and chose the "grub" boot entry, "debian" will be your > fallback entry in case you have run into the bug. > > If the machine boot successfully using the "grub" boot entry in EFI, go back > into the "grub" source directory and run "git bisect good". Run "make clean" > and repeat the build and install step above. > > If a boot fails, reset the machine, boot the "debian" entry and then go back > into the "grub" source directory and run "git bisect bad". Run "make clean" > and repeat the build and install step above. > > Repeat this procedure until git shows you the offending commit. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer > `. `' Physicist > `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
