[nmglug] RE weirder
okeefe at cybermesa.com
Sat May 18 20:12:59 PDT 2019
I finally got around to this and implemented your suggestions. I'
including my grub file as it now exists. After implementing the changes
my machine shuts down in a reboot but loads only the splash screen and
no further. If I boot it as opposes to reboot, I get the newer kernel
and the bad graphics. If I choose, manually, the 4.15.0-48 kernel, it
boots normally with the proper resolution. Here's my grub file and
# If you change this file, run 'update-grub' afterwards to update
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT="Ubuntu, with Linux 4.15.0-48 generic"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
# Uncomment to disable graphical terminal (grub-pc only)
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
# Uncomment to disable generation of recovery mode menu entries
# Uncomment to get a beep at grub start
GRUB_INIT_TUNE="480 440 1"
On 4/25/19 6:33 PM, Alucard wrote:
> Hi Brian,
> If you are able to get to a x session (GUI) I would adjust grub with
> grub-customizer. You can do this from command line, however, it would
> mean adjusting /etc/grub.d files.
> sudo add-apt-repository ppa:danielrichter2007/grub-customizer ; sudo
> apt update ; sudo apt install grub-customizer ; grub-customizer
> However, I would probably would just tell grub to not display the
> menu. As long as you're going to manually enter the GRUB_DEFAULT
> option in /etc/default/grub
> I also forgot to tell you to run update-grub after you edit
> So this is what you should do.
> sudo cp -p -v /etc/default/grub /etc/default/grub.bak
> sudo nano /etc/default/grub
> (Change GRUB_DEFAULT=0 to GRUB_DEFAULT="Ubuntu, with Linux 4.15.0-48
> generic" ) (Make sure you include the double quotes, "")
> (Also add this any where in the same file, just make sure it has it's
> own line to itself, GRUB_DISABLE_OS_PROBER=true ) (Ctrl + O then Ctrl
> + X to save and exit)
> sudo update-grub
> sudo systemctl reboot
> That should force that particular kernel to load on it's own, without
> a grub menu at boot time.
> On 4/25/19 5:54 PM, Brian O'Keefe wrote:
>> Many thanks Jared,
>> I will give this a shot tomorrow. I don't think it will fix the
>> restart issue but perhaps this kernel is magical. I will find out.
>> Any idea why my user name would show up in the Bios boot order? Do
>> you think it's something I could delete safely?
>> On 4/25/19 5:40 PM, Alucard wrote:
>>> Hi Brian,
>>> I think this should work.
>>> sudo cp -p -v /etc/default/grub /etc/default/grub.bak
>>> sudo nano /etc/default/grub
>>> (Change GRUB_DEFAULT=0 to GRUB_DEFAULT="Ubuntu, with Linux 4.15.0-48
>>> generic" ) (Make sure you include the double quotes, "") (Ctrl + O
>>> then Ctrl + X to save and exit)
>>> sudo systemctl reboot
>>> See if that will do what you're asking. TBH I'm use to systemd-boot,
>>> not grub. It's been a while since I've used grub. If that change
>>> broke things, you can move the grub.bak file back to /etc/default/grub
>>> On 4/25/19 5:18 PM, Brian O'Keefe wrote:
>>>> I tried a bunch of fixes but found one that worked! I edited /
>>>> "etc/default/grub" and manually changed the screen resolution to
>>>> 1366x768. that may have worked so I shutdown (hard) and booted
>>>> (after, once again, moving my user name down in the boot order in
>>>> the Bios) and successfully bringing up the Grub menu. I arbitrarily
>>>> picked 4.15.0-48 generic and lo and behold Wifi, sound, resolution,
>>>> xrandr output shows many screen res. options and things seem to be
>>>> ok, for now. I would like this kernel to be the first choice for
>>>> booting. I'm sure there is a simple way to do this. can anyone
>>>> enlighten me? I would really appreciate it but I can also search
>>>> and I'm sure there is a solution to be found.
>>>> Talk about Ghosts in the Shell!!
>>>> Thanks for your indulgences!
>>>> nmglug mailing list
>>>> nmglug at lists.nmglug.org
>>> nmglug mailing list
>>> nmglug at lists.nmglug.org
> nmglug mailing list
> nmglug at lists.nmglug.org
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3148 bytes
Desc: not available
More information about the nmglug