System appears to wake from sleep but monitor does not

Ubuntu Support Template

Ubuntu Version: 24.04, Ubuntu Studio

Desktop Environment (if applicable): KDE Plasma 5.27.12

Problem Description:
The system appears to wake from sleep but monitor does not. I can hear the system waking up, see lights change, etc. Monitor is black and will not wake until I unplug and re-plug it. When I plug the HDMI cable back in the monitor wakes up instantly and works normally until the system goes to sleep again.

This doesn’t seem to happen every single time, but probably 80+% of the time the system goes to sleep. All elements of the display seem to work fine otherwise.

Relevant System Information:
monitor is a Samsung LC32G5xT

Screenshots or Error Messages:
System logs (ie from system category in the gnome log viewer):

11:05:51 kernel: Buffer I/O error on dev sr0, logical block 512, async page read
11:05:51 kernel: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
11:05:51 kernel: sr 2:0:0:0: [sr0] tag#28 CDB: Read(10) 28 00 00 00 04 00 00 00 02 00
11:05:51 kernel: Buffer I/O error on dev sr0, logical block 1040064, async page read
11:05:51 kernel: I/O error, dev sr0, sector 8320512 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
11:05:51 kernel: sr 2:0:0:0: [sr0] tag#27 CDB: Read(10) 28 00 00 1f bd 80 00 00 02 00
11:05:51 kernel: I/O error, dev sr0, sector 8320512 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2
11:05:51 kernel: sr 2:0:0:0: [sr0] tag#26 CDB: Read(10) 28 00 00 1f bd 80 00 00 40 00
11:05:50 kernel: Buffer I/O error on dev sr0, logical block 512, async page read
11:05:50 kernel: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
11:05:50 kernel: sr 2:0:0:0: [sr0] tag#10 CDB: Read(10) 28 00 00 00 04 00 00 00 02 00
11:05:50 kernel: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
11:05:50 kernel: sr 2:0:0:0: [sr0] tag#9 CDB: Read(10) 28 00 00 00 04 00 00 00 02 00
11:05:49 kernel: e1000e 0000:00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
11:05:46 kernel: ata2.00: configured for UDMA/133
11:05:46 kernel: sd 1:0:0:0: [sdb] Starting disk
11:05:46 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
11:05:45 kernel: ata1.00: configured for UDMA/133
11:05:45 kernel: sd 0:0:0:0: [sda] Starting disk
11:05:45 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
11:05:45 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device Samsung LC32G5xT (HDMI-0)
11:05:44 kernel: input: Generic X-Box pad as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12.1/1-12.1.3/1-12.1.3:1.0/input/input37
11:05:44 kernel: usb 1-12.1.3: SerialNumber: 00000001
11:05:43 kernel: audit: type=1400 audit(1764950743.803:203): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=13632 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
11:05:43 kernel: input: Microsoft X-Box One S pad as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12.1/1-12.1.3/1-12.1.3:1.0/input/input36
11:05:43 kernel: usb 1-12.1.3: SerialNumber: 3034433031333539423944463743
11:05:43 kernel: firewire_core 0000:06:00.0: rediscovered device fw0
11:05:43 kernel: usb 1-12.1.3: new full-speed USB device number 29 using xhci_hcd
11:05:43 kernel: PM: suspend exit
11:05:43 kernel: random: crng reseeded on system resumption
11:05:43 kernel: done.
11:05:43 kernel: xpad 1-12.1.3:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
11:05:43 kernel: usb 1-12.1.3: USB disconnect, device number 26
11:05:43 kernel: pci 0000:03:00.0:   bridge window [mem 0xe2200000-0xe23fffff 64bit pref]
11:05:43 kernel: pci_bus 0000:04: Allocating resources
11:05:43 kernel: pci 0000:05:00.0: bridge window [io  size 0x1000]: failed to assign
11:05:43 kernel: Restarting tasks ... 
11:05:43 kernel: pci 0000:05:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 06] add_size 200000 add_align 100000
11:05:43 kernel: OOM killer enabled.
11:05:43 kernel: pci 0000:05:00.0: bridge window [io  0x1000-0x0fff] to [bus 06] add_size 1000
11:05:43 kernel: pci_bus 0000:06: Allocating resources
11:05:43 kernel: xpad 1-12.1.3:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
11:05:43 kernel: usb 1-12.1.3: device firmware changed
11:05:43 kernel: ata3.00: configured for UDMA/100
11:05:43 kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
11:05:43 kernel: ata4.00: configured for UDMA/133
11:05:43 kernel: sd 3:0:0:0: [sdc] Starting disk
11:05:43 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
11:05:43 kernel: serial 00:06: activated
11:05:43 kernel: parport_pc 00:04: activated
11:05:43 kernel: ACPI: PM: Waking up from system sleep state S3
11:05:43 kernel: CPU3 is up
11:05:43 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
11:05:43 kernel: CPU2 is up
11:05:43 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
11:05:43 kernel: CPU1 is up
11:05:43 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
11:05:43 kernel: Enabling non-boot CPUs ...
11:05:43 kernel: ACPI: PM: Restoring platform NVS memory
11:05:43 kernel: smpboot: CPU 1 is now offline
11:05:43 kernel: Disabling non-boot CPUs ...
11:05:43 kernel: ACPI: PM: Saving platform NVS memory
11:05:43 kernel: ata4.00: Entering standby power mode
11:05:43 kernel: ata2.00: Entering standby power mode
11:05:43 kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
11:05:43 kernel: ata1.00: Entering standby power mode
11:05:43 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
11:05:43 kernel: e1000e: EEE TX LPI TIMER: 00000011
11:05:43 kernel: parport_pc 00:04: disabled
11:05:43 kernel: serial 00:06: disabled
11:05:43 kernel: printk: Suspending console(s) (use no_console_suspend to debug)

What I’ve Tried:
Googling. Googling the random error codes (looks like something’s up with my CD/DVD drive. Cool cool.)

Thanks!

1 Like

The line above looks like it would be worth investigating as the reference is specific to your monitor. The I/O errors referencing the DVD drive probably mean a bad DVD.

1 Like

Thank you, that put me on the right track! Chasing that error down led me to this: https://nvidia.custhelp.com/app/answers/detail/a_id/3571/~/managing-a-display-edid-on-linux

which resolved the problem. thanks again

1 Like

Oh no. I spoke to soon - I thought I had fixed it, but then it happened again, and I noted that I’m getting an error in nvidia-settings:

Unable to write EDID to file ... Binary mode: permission denied

I tried running nvidia-settings as root, no luck. I tried writing the EDID file to another directory – luck!

However in then trying to copy the EDID into the correct directory (which from what I can tell is

/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-HDMI-A-1/

or

/sys/class/drm/card1-HDMI-A-1,

which seems to be just a link to the former?)

I get

cp: cannot create regular file '/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1/card1-HDMI-A-1/edid.bin': Permission denied"

…even though I’m running as root. I checked lsattr for the directory, but only get


lsattr: Operation not supported While reading flags on ./uevent
lsattr: Operation not supported While reading flags on ./enabled
lsattr: Operation not supported While reading flags on ./power
lsattr: Operation not supported While reading flags on ./dpms
lsattr: Operation not supported While reading flags on ./device
lsattr: Operation not supported While reading flags on ./connector_id
lsattr: Operation not supported While reading flags on ./subsystem
lsattr: Operation not supported While reading flags on ./status
lsattr: Operation not supported While reading flags on ./edid
lsattr: Operation not supported While reading flags on ./modes

This is maybe a totally different, question, now, I realize, but would appreciate any ideas :slight_smile: