Screen blank on first boot, appears after REISUB

[weeninja]

I have had this intermittent fault for many months, but now it occurs on every power-up start after I upgraded to Linux Mint 21.1.

This is the fault: on first start, the machine wakes up my monitor but the monitor then goes to sleep after a couple of seconds and does not wake again. I then reboot with REISUB and I see the grub boot menu and then everything is fine.

Any ideas please?

Code: Select all

inxi -SGx
System:
  Host: puget Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc
    v: 11.3.0 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera
    base: Ubuntu 22.04 jammy
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 3440x1440~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
    v: 4.6 Mesa 22.2.5 direct render: Yes

[SMG]

I have had this intermittent fault for many months, but now it occurs on every power-up start after I upgraded to Linux Mint 21.1.

Welcome to the forum, weeninja.

It is difficult to know what the issue might be with so little information. Please provide the complete output of

Code: Select all

inxi -Fxxxrz

The z at the end redacts any personal information.

This is the fault: on first start, the machine wakes up my monitor but the monitor then goes to sleep after a couple of seconds and does not wake again. I then reboot with REISUB and I see the grub boot menu and then everything is fine.

Do you always see the grub menu or only when you reboot with REISUB?

[weeninja]

Hello SMB, thanks for your message and your kind welcome.

Code: Select all

$ inxi -Fxxxrz
System:
  Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: H97I-PLUS v: Rev X.0x serial: <superuser required>
    BIOS: American Megatrends v: 2103 date: 06/27/2014
CPU:
  Info: quad core model: Intel Core i7-4790 bits: 64 type: MT MCP
    smt: enabled arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 2429 high: 3492 min/max: 800/4000 cores: 1: 3492
    2: 3492 3: 3492 4: 3492 5: 1573 6: 1299 7: 1298 8: 1297 bogomips: 57466
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel ports: active: DP-1
    empty: HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0412 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.8x15.0")
    s-diag: 987mm (38.8")
  Monitor-1: DP-1 model: AOC U34G2G1 serial: <filter> res: 3440x1440 hz: 60
    dpi: 110 size: 797x334mm (31.4x13.1") diag: 864mm (34") modes:
    max: 3440x1440 min: 720x400
  OpenGL: renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
    v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 9 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-67-generic running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.99.1 running: yes
  Sound Server-4: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: kernel
    port: f080 bus-ID: 00:19.0 chip-ID: 8086:15a1 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br-2450be65556a state: down mac: <filter>
  IF-ID-2: br-49b774624d6b state: down mac: <filter>
  IF-ID-3: br-4f895d88fe0d state: down mac: <filter>
  IF-ID-4: br-6280afda4eeb state: down mac: <filter>
  IF-ID-5: br-6fe076818539 state: down mac: <filter>
  IF-ID-6: br-818e473e9ace state: down mac: <filter>
  IF-ID-7: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 704.24 GiB used: 504.22 GiB (71.6%)
  ID-1: /dev/sda vendor: Samsung model: SSD 840 PRO Series size: 238.47 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 6B0Q scheme: MBR
  ID-2: /dev/sdb vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q scheme: MBR
Partition:
  ID-1: / size: 97.87 GiB used: 85.37 GiB (87.2%) fs: ext4 dev: /dev/sdb1
  ID-2: /home size: 358.95 GiB used: 210.55 GiB (58.7%) fs: ext4
    dev: /dev/sdb2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 3537 apt: 3525 flatpak: 12
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/element-io.list
    1: deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main
  Active apt repos in: /etc/apt/sources.list.d/gazebo-stable.list
    1: deb [signed-by=/usr/share/keyrings/gazebo.gpg] http://packages.osrfoundation.org/gazebo/ubuntu-stable jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirrors.ukfast.co.uk/sites/linuxmint.com/packages vera main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/openshot_developers-ppa-focal.list
    1: deb [signed-by=/usr/share/keyrings/openshot.gpg] http://ppa.launchpad.net/openshot.developers/ppa/ubuntu jammy main
  No active apt repos in: /etc/apt/sources.list.d/riot-im.list
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
  Active apt repos in: /etc/apt/sources.list.d/teams.list
    1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
    1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 292 Uptime: 4m wakeups: 0 Memory: 15.08 GiB
  used: 4.02 GiB (26.7%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11/12/9 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

I do not see the grub menu on first start, only after reboot with REISUB. I see the monitor start up as the machine begins to boot - the monitor shows the AOC spash screen and the power LED is white, then it displays "No connection" and goes blank, and the power LED turns red.

I used to have this problem as an intermittent fault before I upgraded to Mint Linux 21.1 last week. It used to occur about 5-10% of the time, and I worked around it by using REISUB. It now happens every time since I upgraded to 21.1 last week.

[SMG]

I do not see the grub menu on first start, only after reboot with REISUB. I see the monitor start up as the machine begins to boot - the monitor shows the AOC spash screen and the power LED is white, then it displays "No connection" and goes blank, and the power LED turns red.

A "no connection" message is usually not an operating system message. It's a message the monitor is not connecting with the computer. However, usually, DP ports are not known to be problematic.

The data seems to indicate you did an in-place upgrade from LM20.3 to LM21. Did you do that?

I suggest you clean your computer's root partition or else you will soon have problems logging in.
Partition:
ID-1: / size: 97.87 GiB used: 85.37 GiB (87.2%) fs: ext4 dev: /dev/sdb1
ID-2: /home size: 358.95 GiB used: 210.55 GiB (58.7%) fs: ext4
dev: /dev/sdb2

I don't understand why the reboot is taking you to a grub screen if the initial booting does not. What is the output of

Code: Select all

cat /etc/default/grub

Please place the results in code tags as explained by this tutorial How to use code display tags on forums.linuxmint.com.

[weeninja]

Correction: that message is "No Display". That's right, SMG - the message is generated by the display.

Yes, I did an upgrade from 20 to 21.1.

Thanks for your tip about space on the root partition - I am aware of that. I installed ARM cross-compilers and they have taken up a lot of room.

Code: Select all

$ cat /etc/default/grub
# 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_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# 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-pc only)
#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"

[SMG]

Although I don't know if this is related to your issue, this is unusual.

Code: Select all

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10

Below are the default settings for those lines when one has only one operating system installed.

Code: Select all

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0

When only one operating system is installed, the grub menu is hidden and, because it is hidden, the time to show the menu is 0 seconds.

Your system is set up to not show the grub menu for 10 seconds before it starts loading the operating system. Do you recall changing that value?

If you want the menu to show, see the instructions in this post, otherwise I suggest changing the 10 to a 0 and see if that helps this issue. (Remember to run sudo update-grub after making any changes to that file.)

[JerryF]

Try changing

GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu

Don't forget to perform the command

Code: Select all

sudo update-grub

[weeninja]

Although I don't know if this is related to your issue, this is unusual.

Code: Select all

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10

Below are the default settings for those lines when one has only one operating system installed.

Code: Select all

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0

When only one operating system is installed, the grub menu is hidden and, because it is hidden, the time to show the menu is 0 seconds.

Your system is set up to not show the grub menu for 10 seconds before it starts loading the operating system. Do you recall changing that value?

If you want the menu to show, see the instructions in this post, otherwise I suggest changing the 10 to a 0 and see if that helps this issue. (Remember to run sudo update-grub after making any changes to that file.)

Thanks SMG. I do not recall changing the timeout value. I don't think I have ever edited

Code: Select all

/etc/default/grub

before. I bought this machine with Windows on /dev/sda and some time later I fitted a larger SSD and installed Mint Linux on the new disk. I made Windows the last of the boot options when I installed Mint Linux. I found that Mint usually booted on first start as expected, but every now and then would not start and my monitor would go back to standby, as I described above. This is now happening on every start from power off.

I just tried the change you describe above. No change to the problem.

[weeninja]

Try changing

GRUB_TIMEOUT_STYLE=hidden
to
GRUB_TIMEOUT_STYLE=menu

Don't forget to perform the command

Code: Select all

sudo update-grub

Hi Jerry, thanks for your thoughts on this problem. I just tried this change with and without the change to TIMEOUT, but it made no difference.

[JerryF]

If you leave GRUB_TIMEOUT at 0 then it won't show either way.

You'll need to put a higher number than 0 or a -1 which indefinitely shows the menu, waiting for your response.

[weeninja]

If you leave GRUB_TIMEOUT at 0 then it won't show either way.

You'll need to put a higher number than 0 or a -1 which indefinitely shows the menu, waiting for your response.

Yes, of course Jerry, and that's what I did, with the value 10. No difference, sadly.

[SMG]

I just tried the change you describe above. No change to the problem.

After making the change, are you seeing the grub menu when you boot?
And then the monitor goes to sleep after you make a selection?

[weeninja]

After I make the change, I still don't see the grub menu when I boot the first time.
On first boot, I see the monitor splash screen for a second or two, then it does dark for a few seconds, then the monitor displays "No signal" and shortly after that the monitor LED changes from white to red, and there it sits indefinitely. When I reboot with REISUB I see the ASUS Bios splash screen and the monitor LED turns white, then I see the grub menu. I can boot successfully from there.

[weeninja]

I ran boot-info and that made some suggestions - please see http://sprunge.us/mw8TG6.
It ends with

Code: Select all

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub2 of
sdb1 into the MBR of sdb.
Grub-efi would not be selected by default because no ESP detected.
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix

Blockers in case of suggested repair: __________________________________________

 Please use this software in a live-session (live-CD or live-USB). This will enable this feature.

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your BIOS boot on sdb (ATA Samsung SSD 870) disk!

Here is a bit of background: I bought this machine with Windows on the disk at sda, as you can see in the report. Later, I installed sdb and installed Mint Linux 20 on that. I have always had an intermittent boot problem, but it usually occurred once in maybe every 20 boots.
I am happy to sacrifice the Windows boot option if that helps, as long as I can still get at the files on sda.
@SMG, do you think I should run boot-repair and make those changes?

[SMG]

Here is a bit of background: I bought this machine with Windows on the disk at sda, as you can see in the report. Later, I installed sdb and installed Mint Linux 20 on that. I have always had an intermittent boot problem, but it usually occurred once in maybe every 20 boots.
I am happy to sacrifice the Windows boot option if that helps, as long as I can still get at the files on sda.
@SMG, do you think I should run boot-repair and make those changes?

You posted on the Graphics Cards & Monitors forum. I usually help with graphics issues and not boot issues. I suggest asking the question about boot changes on the Installation & Boot forum. There may be a way to get it fixed so you can boot into either.

Then if you get that fixed and that does not fix the screen blank error, return here and we'll see what we might be able to do. The fact there are currently two different places to boot may be the problem, but I don't know how that is handled in Legacy BIOS mode.

Your computer can do UEFI mode, but apparently it is set for Legacy BIOS mode. I don't know if that might be contributing to the issue, because I don't usually troubleshoot those issues.

[weeninja]

Roger that, thanks very much @SMG