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


Groups > linux.debian.user > #267599 > unrolled thread

Re: Re: GRUB lost graphical terminal mode

Started byBorden <borden_c@tutanota.com>
First post2024-02-19 23:10 +0100
Last post2024-02-20 18:50 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  Re: Re: GRUB lost graphical terminal mode Borden <borden_c@tutanota.com> - 2024-02-19 23:10 +0100
    Re: GRUB lost graphical terminal mode Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-02-20 09:10 +0100
      Re: GRUB lost graphical terminal mode Charles Curley <charlescurley@charlescurley.com> - 2024-02-20 18:50 +0100

#267599 — Re: Re: GRUB lost graphical terminal mode

FromBorden <borden_c@tutanota.com>
Date2024-02-19 23:10 +0100
SubjectRe: Re: GRUB lost graphical terminal mode
Message-ID<I9jZL-bhH9-11@gated-at.bofh.it>
> On 18 Feb 2024 21:28 +0100, from borden_c@tutanota.com (Borden):
> > what the default is when neither of those are set (which doesn't
> > work). Is this another "undocumented feature" of GRUB?
> 
> Would you be willing to post your /boot/grub/grub.cfg for a setup where you get the blank screen GRUB?

Yeah, I probably should have opened with that. Sorry:

```
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false

# 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 ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# 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'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
```

For what it's worth, my graphics adapter is an ancient Intel HD 4000 series processor (Ivy Bridge era). It's possible that my card is dying or no longer supported. It's just a pain that it worked a few weeks ago and now it doesn't. It would be nice to know why.

[toc] | [next] | [standalone]


#267621

FromMichael Kjörling <2695bd53d63c@ewoof.net>
Date2024-02-20 09:10 +0100
Message-ID<I9tmp-bnu4-1@gated-at.bofh.it>
In reply to#267599
On 19 Feb 2024 22:44 +0100, from borden_c@tutanota.com (Borden):
>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>> where you get the blank screen GRUB?
> 
> Yeah, I probably should have opened with that. Sorry:
> 
> ```
> # If you change this file, run 'update-grub' afterwards to update
> # /boot/grub/grub.cfg.
> # For full documentation of the options in this file, see:
> #   info -f grub -n 'Simple configuration'
> 
> GRUB_DEFAULT=0
[snipped remainder]

If that's your /boot/grub/grub.cfg, it's a miracle that your GRUB
installation is working at all and not dumping you to a grub> rescue
prompt.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

[toc] | [prev] | [next] | [standalone]


#267641

FromCharles Curley <charlescurley@charlescurley.com>
Date2024-02-20 18:50 +0100
Message-ID<I9CpI-bsOG-7@gated-at.bofh.it>
In reply to#267621
On Tue, 20 Feb 2024 08:04:47 +0000
Michael Kjörling <2695bd53d63c@ewoof.net> wrote:

> On 19 Feb 2024 22:44 +0100, from borden_c@tutanota.com (Borden):
> >> Would you be willing to post your /boot/grub/grub.cfg for a setup
> >> where you get the blank screen GRUB?  
> > 
> > Yeah, I probably should have opened with that. Sorry:
> > 
> > ```
> > # If you change this file, run 'update-grub' afterwards to update
> > # /boot/grub/grub.cfg.
> > # For full documentation of the options in this file, see:
> > #   info -f grub -n 'Simple configuration'
> > 
> > GRUB_DEFAULT=0  
> [snipped remainder]
> 
> If that's your /boot/grub/grub.cfg, it's a miracle that your GRUB
> installation is working at all and not dumping you to a grub> rescue
> prompt.
> 

That clearly isn't the OP's /boot/grub/grub.cfg, but
/etc/default/grub.

As the former is often rather lengthy, and the list does reject large
attachments, perhaps Borden <borden_c@tutanota.com> will put it up at
https://paste.debian.net or some other pastebin facility and provide
the URL.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web