0

My father uses Ubuntu for his Dell 7530 and I'm asking this question on his behalf. He recently upgraded to Ubuntu 20.04 and found that the monitor for the laptop doesn't turn back on when the laptop is closed and then reopened.

When the sleep button and power button is tapped, the screen turns off but the power button light doesn't change or blink to indicate sleep mode.

Nothing wakes up the laptop or turns the screen back on, not pressing power, spacebar, switch screen buttons, none of the function keys to get into the terminal mode, nothing. The only way to get the screen back is to perform a hard reset.

Here's what I've done to try to solve this, with no success:

  • Upgraded to 20.10 and Kernel 5.8 to see if it's a kernel issue
  • Changed all sleep directives in /etc/systems/logins.cond to ignore
  • Disabled sleep mode in the BIOS (doesn't solve the problem but does stop the screen from turning off when the screen is closed or power button is used)
  • Removed gnome-tweak-tool because it has the ignore sleep mode extension.
  • Set grub boot property mem_sleep_default to all of the various states

I feel as though ignoring the sleep mode isn't really a solution to the screen problem, but it at least prevents it from happening if the monitor closes. I'd like to get the screen to turn back on or sleep mode to work properly.

One thing I should note is that when I tried pressing the volume up buttons once while the screen was off I could hear a ping tone, as if the volume was being affected, but I tried the same thing a few more times without the same result. I'm not certain if the OS is still running while the screen is off.

I can provide additional logs in a few days. I would be happy to provide anything I can.

4
  • Refer askubuntu.com/help/on-topic where you'll notice only supported releases of Ubuntu and flavors are on-topic for this site. For groovy gorilla [20.10] questions you'll need to use a development support site such as IRC (#ubuntu+1) or Ubuntu Forums, or wait until after release for this site (expected release date for Ubuntu 20.10 is 22 October (discourse.ubuntu.com/t/groovy-gorilla-release-schedule/15531) when your question will be on-topic here).
    – guiverc
    Oct 1, 2020 at 4:16
  • From your description you moved away from supported 20.04, and went to currently unsupported groovy, which will be on-topic on this site in a few weeks. If it's an issue on groovy; this site recommends you file a bug as that is where it's easiest to fix issues (ie. whilst in development). help.ubuntu.com/community/ReportingBugs
    – guiverc
    Oct 1, 2020 at 4:17
  • The problem started on 20.04. Wouldn't that still mean this is a valid question, even though in my troubleshooting I had tried to upgrade? If we find that it's related to a kernel or Ubuntu bug which possibly originated in the 5.3 kernel from 20.04, then I'd be happy to file a bug once we're more sure of the problem, if that is acceptable. I'm just looking for additional troubleshooting steps that I can take, assuming this started in 20.04.
    – Allan Bogh
    Oct 1, 2020 at 14:40
  • You're not running Ubuntu 20.04, and Ubuntu 20.04 doesn't use the 5.3 kernel either which you'd know if you were using Ubuntu 20.04. The 5.3 kernel is EOL on Ubuntu. It'll be on-topic in a few weeks when Ubuntu groovy becomes 20.10 (beta is available for testing now!)
    – guiverc
    Oct 1, 2020 at 14:41

1 Answer 1

0

The problem turned out to be a bug in the BIOS. After upgrading the BIOS firmware from Dell and undoing any changes within /etc/systemd/logind.conf, BIOS settings, gnome-tweak-tool, or Grub, everything seems to work as normal.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .