Debian/KDE - Display Won't Wake Up

[ArchiMark]

Upgraded Cosmo to the latest firmware and CODI the other day.

Works OK in Android.

Booted up to Debian/KDE today.

Worked OK, but then left Cosmo unattended for a half hour.

Came back and display is black. Tried to 'wake up' Cosmo by tapping on screen, but no go.

Tried tapping on various keys, but no go.

How do you wake up the Cosmo?

Thanks,

Mark

[cam1965]

Upgraded Cosmo to the latest firmware and CODI the other day.

Works OK in Android.

Booted up to Debian/KDE today.

Worked OK, but then left Cosmo unattended for a half hour.

Came back and display is black. Tried to 'wake up' Cosmo by tapping on screen, but no go.

Tried tapping on various keys, but no go.

How do you wake up the Cosmo?

Thanks,

Mark

In this case, maybe an ssh from your PC, like in gemini  (  ssh -Y gemini@10.15.19.82 ) is an option to reboot.
Maybe you have to install a new kernel with support to a lid close suspend support . Please see https://www.oesf.org/forum/index.php?showto...ommit&st=27 . ( Please Read  everything ). According to the post ,  this kernel does not install the module for wlan. You will have to install a new system image ( you will lose  your install ) or install the module manually .  ( modprobe -f ).  Please see https://www.oesf.org/forum/index.php?showto...mp;#entry295271   ( modprobe --force wlan_drv_gen3 ). But first you have to copy the old modules to the the correct place.  

In gemini, when the screen was black ( power saving and lock screen ) I had to type the password, but I don´t know if it is the case.
Good Luck.

[ArchiMark]

Upgraded Cosmo to the latest firmware and CODI the other day.

Works OK in Android.

Booted up to Debian/KDE today.

Worked OK, but then left Cosmo unattended for a half hour.

Came back and display is black. Tried to 'wake up' Cosmo by tapping on screen, but no go.

Tried tapping on various keys, but no go.

How do you wake up the Cosmo?

Thanks,

Mark

In this case, maybe an ssh from your PC, like in gemini  (  ssh -Y gemini@10.15.19.82 ) is an option to reboot.
Maybe you have to install a new kernel with support to a lid close suspend support . Please see https://www.oesf.org/forum/index.php?showto...ommit&st=27 . ( Please Read  everything ). According to the post ,  this kernel does not install the module for wlan. You will have to install a new system image ( you will lose  your install ) or install the module manually .  ( modprobe -f ).  Please see https://www.oesf.org/forum/index.php?showto...mp;#entry295271   ( modprobe --force wlan_drv_gen3 ). But first you have to copy the old modules to the the correct place.  

In gemini, when the screen was black ( power saving and lock screen ) I had to type the password, but I don´t know if it is the case.
Good Luck.

Thank you for all your input.

Seems like a lot of effort to get a working system....

Oh well....

[Tom D]

Thank you for all your input.

Seems like a lot of effort to get a working system....

Oh well....

A little clarification. when I close the lid, and then open it, I get the desktop background, just no way to do anthing - no login, no way to click anything, etc.

What does work for me is using the menu to sleep. Then resume does work. So basically, the LID CLOSE EVENT needs to do the same thing as the menu for sleep. So it is close to working.

So for now,

1. Change the power settings to not let it go to sleep automatically.
2. Don't close the lid unless you have manually put the device to sleep first.

[ArchiMark]

Thank you for all your input.

Seems like a lot of effort to get a working system....

Oh well....

A little clarification. when I close the lid, and then open it, I get the desktop background, just no way to do anthing - no login, no way to click anything, etc.

What does work for me is using the menu to sleep. Then resume does work. So basically, the LID CLOSE EVENT needs to do the same thing as the menu for sleep. So it is close to working.

So for now,

1. Change the power settings to not let it go to sleep automatically.
2. Don't close the lid unless you have manually put the device to sleep first.

Thank you, Tom!

Sounds like a good workaround for now.