Re: grub2 user interface disappears after upgrade from stretch to testing
Shane Dev <[email protected]>
| Newsgroups | gmane.linux.debian.user.testing |
|---|---|
| Message-ID | <CALuWMFkgW30+pk3ULLJm_es7Ln-DbUfuxpEpOyQbXGCDNfve3g@mail.gmail.com> |
Hello, I reinstalled stretch (bare minimum packages), then I replaced all references to "stretch" with "testing" in /etc/apt/sources.list and executed sudo apt update; sudo apt install gnome-core firefox-esr. Everything works as expected but I have the following questions - 1. according to uname -r, I am running 4.9.0-7-amd64 which appears to be the stretch kernel. Is it safe to run the stretch kernel with programs / apps / utilities from testing? 2. I noticed the intel-microcode package is not installed. If I install it, could this testing version conflict with the stretch kernel? 3. Last time I tried apt upgrade, my grub menu was replaced with the grub command prompted. If there any way to avoid this happening again? On Tue, 13 Nov 2018 at 05:54, Felix Miata <[email protected]> wrote: > Shane Dev composed on 2018-11-13 06:12 (UTC+0100): > > > Thanks for your fast reply. From memory, I think the grub2 text menu > > installed by firmware-9.6.0-amd64-netinst.iso became a grub command line > > prompt after upgrading to testing. > > > 1. For what possible reasons could have my grub menu disappeared? > > You're using "testing". Bugs are to be expected at least on occasion. > Sometimes > BIOS quirks interfere with Grub setup commands. UEFI BIOS writers probably > do > not spend much time debugging their use with Linux and Grub. UEFI code > still > has more maturing to do before consistency among different machines' > behavior > can be expected. > > > 2. You suggest I could boot Debian with "linux" and "initrd" commands. > How > > could I determine which parameters to pass to these commands? > > This is why I mentioned your backup grub.cfg file and provided a template > from > one of my own systems. > > The initrd line needs only the fullpath of the initrd to be loaded. The > linux > line may work with no more than the same. Most cmdline options used in Grub > linux lines are options, meaning not necessary to a successful boot. The > stanza > lines preceding the linux line may or may not be required. All you can do > is > try, preferably based upon your backup. If you can't locate a backup, > retrieve > the grub.cfg file via a rescue boot and work from it. Make use of tab > completion > to get the appropriate names of kernel and initrd. > -- > Evolution as taught in public schools is religion, not science. > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > >