Linux Lite Forums
Hardware - Support => Video Cards => Topic started by: jas on March 16, 2015, 01:02:58 PM
-
Hello
Just installed LL on my netbook, and I love it, but there is one thing I cannot live with. Looking at this forum, and many others, but cannot find a solution. Maybe, and I hope, there is!
So after putting the lid down of my netbook, or putting it to sleep manually. I cannot see it woken up.
There is a black screen, no mouse cursor, but there is hdd movement. (the led is blinking).
Sometimes, after more than 5 minutes, the login screen appears again. (but that can be because I clicked something in the black screen.)
output of inxi -zv7
[sup][sup] inxi -zv7
System: Host: asus-e Kernel: 3.13.0-24-generic i686 (32 bit, gcc: 4.8.2)
Desktop: Xfce 4.11.8 (Gtk 2.24.23) info: xfce4-panel dm: lightdm Distro: Ubuntu 14.04 trusty
Machine: System: ASUSTeK product: 1025C version: x.x Chassis: type: 10 version: x.x
Mobo: ASUSTeK model: 1025C version: x.xx Bios: American Megatrends version: 1025C.1301 date: 08/16/2013
CPU: Dual core Intel Atom CPU N2800 (-HT-MCP-) cache: 512 KB flags: (nx pae sse sse2 sse3 ssse3) bmips: 7449.34
Clock Speeds: 1: 798.00 MHz 2: 1862.00 MHz 3: 798.00 MHz 4: 798.00 MHz
Graphics: Card: Intel Atom Processor D2xxx/N2xxx Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0be2
X.Org: 1.15.1 drivers: (unloaded: fbdev,vesa) Resolution: [email protected]
GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits) GLX Version: 2.1 Mesa 10.1.3 Direct Rendering: Yes
Audio: Card: Intel NM10/ICH7 Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:27d8
Sound: Advanced Linux Sound Architecture ver: k3.13.0-24-generic
Network: Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k bus-ID: 02:00.0 chip-ID: 168c:0032
IF: wlan0 state: down mac: <filter>
Card-2: Qualcomm Atheros AR8152 v2.0 Fast Ethernet
driver: atl1c ver: 1.0.1.1-NAPI port: e000 bus-ID: 03:00.0 chip-ID: 1969:2062
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
WAN IP: <filter> IF: eth0 ip: <filter> ip-v6: <filter> IF: wlan0 ip: N/A ip-v6: N/A
Drives: HDD Total Size: 320.1GB (4.9% used)
1: id: /dev/sda model: WDC_WD3200BPVT size: 320.1GB serial: WD-WX41A81W3494
Optical: No optical drives detected.
Partition: ID: / size: 9.5G used: 3.6G (40%) fs: ext4 dev: /dev/sda5
label: N/A uuid: b4aab858-5ef1-47e4-9fc7-e9ee684c78b8
ID: /home size: 87G used: 12G (14%) fs: ext4 dev: /dev/sda6
label: N/A uuid: f389577a-38e9-40b3-bc0e-6e744b124987
RAID: System: supported: linear multipath raid0 raid1 raid6 raid5 raid4 raid10
No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Unused Devices: none[/sup][/sup]
Any clue, please?
-
Have you tried this? https://www.linuxliteos.com/forums/index.php?topic=1480.msg12791#msg12791
-
Have you tried this? https://www.linuxliteos.com/forums/index.php?topic=1480.msg12791#msg12791
Now I tried, Installed
sudo apt-get install acpi-support
But no luck. Same thing.
Also tried disabling the screensaver. Which is not possible, so I put it to be active after many hours.
Fiddled around with the settings in the Power Manager. Dont see any difference in suspend or hibernate behaviour. Sometimes one of the two is greyed out, and I cannot choose.
I was trying this, as I think it is an option for LL no? But cannot find the file. (Off topic, but where is the search in the file manager Thunar?)
https://sites.google.com/site/easylinuxtipsproject/8#TOC-Disable-hibernation-suspend-to-disk- (https://sites.google.com/site/easylinuxtipsproject/8#TOC-Disable-hibernation-suspend-to-disk-)
Thanks for any help in advance!
-
Also tried disabling the screensaver. Which is not possible, so I put it to be active after many hours.
Don't forget to do File, Restart Daemon on Screensaver after any changes, or they won't stick.
-
Also tried disabling the screensaver. Which is not possible, so I put it to be active after many hours.
Don't forget to do File, Restart Daemon on Screensaver after any changes, or they won't stick.
Ok, but we were many forced shutdowns later already ;).
Found the disable screensaver and restarted the daemon. It is something different than Ubuntu, and I like it. But not this black screen.............
-
Update
- black screen problem continues
also after totally disabling the screensaver.
Workaround.
in Powermanager select "do nothing" when run on AC power when lid closes.
on battery power select "suspend" (that is what I want to function normally)
So unplugged and lid closed, result black screen.
Plug AC in, black screen stays.
Close lid.
Open lid
And I do have my screen back.
(what a way...)
-
How about giving Jerry a
sudo parted -l
report because you cut off the ram report on your inxi report and your inxi report shows no ram specs like mine does.
or a /swap partition.
Info: Processes: 106 Uptime: 1:26 Memory: 241.5/2010.5MB
Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301) inxi: 2.2.18
$ sudo parted -l
[sudo] password for harry:
Model: ATA TOSHIBA MK6028GA (scsi)
Disk /dev/sda: 60.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 15.7GB 15.7GB primary ext4 boot
2 15.7GB 20.0GB 4245MB primary linux-swap(v1)
3 20.0GB 60.0GB 40.0GB extended
5 20.0GB 60.0GB 40.0GB logical ext4
Because memory is tied into how fast a machine wakes up.
https://wiki.archlinux.org/index.php/Suspend_and_hibernate (https://wiki.archlinux.org/index.php/Suspend_and_hibernate)
-
That sounds familiar (see post: https://www.linuxliteos.com/forums/index.php?topic=839.msg12349#msg12349).
As in my last post there, after killing light-locker the system now uses the XScreenSaver look screen when coming back from suspend. Since then I didn't have to reboot, even if it takes sometimes quite a while (and lots of disk I/O) for the XScreenSaver window to show up.
Still an issue however is the network connection after coming back from suspend, but also not consistent. Roughly half of the time the network has been disabled. Enabling it via the panel icon doesn't help though. I need to restart the NetworkManager:
$ sudo kill $(pidof NetworkManager)
Then all is fine. For me it's annoying but I know what to do. :) It stops me however to put the system on other people's computer :(
Are you able to get to a console (Ctrl+Alt+F1)?
PS: Just saw your last post with your workaround... haven't tested this.
-
How about giving Jerry a
sudo parted -l
report because you cut off the ram report on your inxi report and your inxi report shows no ram specs like mine does.
or a /swap partition.
Great!!!
You pointed me in the right direction. THANKS
Yesterday during install I formatted the boot (sda5) and the home (sda6) dir. And in some way, the swap got lost. So with Gparted I recreated it again, and it works. The output
e@asus-e:~$ sudo parted -l
Model: ATA WDC WD3200BPVT-8 (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags
1 2096kB 211GB 211GB extended
5 2097kB 10,5GB 10,5GB logical ext4 boot
6 10,5GB 105GB 94,4GB logical ext4
7 105GB 211GB 106GB logical ext4
3 211GB 319GB 108GB primary ext4
2 319GB 320GB 1311MB primary
doesnot state in File system that sda2 is a swap, (don't know why) but Gparted shows me. (and cannot show you as images are not allowed as attachment)
It is working!
GREAT. THANKS
-
That sounds familiar (see post: https://www.linuxliteos.com/forums/index.php?topic=839.msg12349#msg12349).
As in my last post there, after killing light-locker the system now uses the XScreenSaver look screen when coming back from suspend. Since then I didn't have to reboot, even if it takes sometimes quite a while (and lots of disk I/O) for the XScreenSaver window to show up.
Still an issue however is the network connection after coming back from suspend, but also not consistent. Roughly half of the time the network has been disabled. Enabling it via the panel icon doesn't help though. I need to restart the NetworkManager:
$ sudo kill $(pidof NetworkManager)
Then all is fine. For me it's annoying but I know what to do. :) It stops me however to put the system on other people's computer :(
Are you able to get to a console (Ctrl+Alt+F1)?
PS: Just saw your last post with your workaround... haven't tested this.
Yes, I saw your post. Had it once that the network manager was not working. (out of 20). I am on cable now, because wireless does not want to connect. We will see. One thing at a time. ;)
And yes, I could get in the console, and shut down the machine. But off course being a blind man.
-
Ok, so the problem is still not solved. (I deleted the mark solved, and the best answer)
There is a definitively a relation between the memory and the waking up. but also with battery power and being plugged in or not.
I sometimes still have the black screen problem. Running low on battery, (around 10%) I had the black screen after logging in. Closing the lid, plugging the machine in on AC, opening the lid, logging in, all fine.
While unplugged, and having the black screen, and then plugging in, no success.
This morning, all night on suspend mode, I had no problem at all waking it up.
I was able to activate sys.log (Thanks for that thread). Is there any output I can post which can shine a light? (the whole sys.log is too private I believe)
Thanks!!
-
My Dell D610 has got this issue after an upgrade to LL 2.4 from 2.2. I used to open lid and just press the esc button twice and I'd get the login. Now it black screens. Is there a way of going back a version? Meanwhile I fiddled round in power manager and using settings of on ac/hibernate and on battery/suspend I can press menu/logout/suspend and close lid. On opening it goes to login and I can log in no problem. This is with wall power permanently on. I never use the battery alone although there's one in with little charge holding ability.
-
well JAS, I was just about to put up a request for help for my machine (eee pc 1000HE) until I saw your message. When I'd put the screen lid down, it would shut the thing off correctly but when I opened it back up, black screen and no control.
In my particular case, I went into the power manager and there were settings "When laptop lid is closed:", that was set to lock screen so that is why I couldn't do anything after I opened it back up. I just selected "Suspend" and now everything is ok.
This is with Linux lite 2.4
I don't know if this will help anyone or not but I wanted to put this up.
Glin22
-
I have this issue on my older gateway as well. I changed screensaver / power options and no change.
However after I login, the screen is blank/black, If I close the laptop lid again and open it right away the screen returns to normal.
It doesn't bother me that much except at night, just one extra step to do.
-
Hello!
Is there a way of going back a version?
Short of you reinstalling 2.2, no. The updater was designed to go forward only, not back.
I know you don't want to hear this, but that's why backing up everything first is so important. Besides, once one of 'the big guns' steps in, they may know how to fix this issue short of 'nuking it and starting over'...
73 DE N4RPS
Rob
-
My Dell Netbook (w/ Intel Graphics) appears to do the similar. Running LL2.2 and same with LL2.6
Since its a "laptop" I want to close the lid or after X time have it hibernate after a screen saver. After waking from hibernate , I see the log on screen I can log in then black... Rebooting corrects until the next time.
I've read that it could be lightdm (I think how it was referenced) and/or the screen saver..
I used the following workaround when I want to hibernate..
In terminal (does require root)
sudo pm-hibernate
I typically leave a terminal window up just having to up arrow to the last command. If I put into hibernate, I have no issues waking.
One of these days I'm going to chase the cause down.... But the above works for the time being.
-
My Dell Netbook (w/ Intel Graphics) appears to do the similar. Running LL2.2 and same with LL2.6
Since its a "laptop" I want to close the lid or after X time have it hibernate after a screen saver. After waking from hibernate , I see the log on screen I can log in then black... Rebooting corrects until the next time.
I've read that it could be lightdm (I think how it was referenced) and/or the screen saver..
I used the following workaround when I want to hibernate..
In terminal (does require root)
sudo pm-hibernate
I typically leave a terminal window up just having to up arrow to the last command. If I put into hibernate, I have no issues waking.
One of these days I'm going to chase the cause down.... But the above works for the time being.
On some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.
Read the manual.
man pm-suspend
try running sudo pm-suspend with some of the quirks
For example:
sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restore
or
sudo pm-suspend --quirk-reset-brightness
or
sudo pm-suspend --quirk-dpms-on
All the quirks:
--quirk-dpms-on
--quirk-dpms-suspend
--quirk-radeon-off
--quirk-reset-brightness
--quirk-s3-bios
--quirk-s3-mode
--quirk-vbe-post
--quirk-vbemode-restore
--quirk-vbestate-restore
--quirk-vga-mode-3
--quirk-none
The trick is finding the right combination. It could be just one parameter or several.
When you find the right quirk. Test your system to see if all is running OK.
From the manual, to save it create a file in /etc/pm/config.d/
Name it anyway you like.
gksu leafpad /etc/pm/config.d/my-quirk
containing ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore"
to make the quirk stick. Just use the parameters that work for you.
Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. :)
Save. After reboot it should work.
You can put the pc to suspend without sudo with dbus-send.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
-
Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. :)
I hear ya, lol ;D
Issue is with Dell Mini with Intel video, my other Dell with SIS all seems to work fine (I don't close a lid but still sleeps/hibernate)..
Is there a way to see what fails or doesn't initialize - debug or something, I sometimes wonder if its not the driver too..
Just a thought..
-
On some hardware putting the video card in the suspend state and recovering from it needs some special quirk handling.
Read the manual.
man pm-suspend
Thanks - Didn't know about the manual..
try running sudo pm-suspend with some of the quirks
For example:
sudo pm-suspend --quirk-reset-brightness
The trick is finding the right combination. It could be just one parameter or several.
When you find the right quirk. Test your system to see if all is running OK.
From the manual, to save it create a file in /etc/pm/config.d/
Name it anyway you like.
gksu leafpad /etc/pm/config.d/my-quirk
containing ADD_PARAMETERS="pm-suspend --quirk-vbe-post --quirk-vbemode-restore"
to make the quirk stick. Just use the parameters that work for you.
Which quirk works depends on your hardware, kernel, driver, KMS settings and the probably the phase of the moon. :)
Save. After reboot it should work.
Testing a quirk seems to work initially but after creating the "my-quirk" file it no longer works..
Does the my-quirk file need referenced in a script or ?? (Like adding to grub to activate the file - just as an example)
Can the quirk file have multiple lines of parameters like:
ADD_PARAMETERS=pm-suspend --quirk-reset-brightness
ADD_PARAMETERS=pm-hibernate --quirk-reset-brightness
Or should I have a separate my-quirk for each function
I know I can string additional quirks on a line
sudo pm-suspend --quirk-vbe-post --quirk-vbemode-restore
You can put the pc to suspend without sudo with dbus-send.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
Is this another way to suspend the vs pm-suspend? I tested with by closing the lid :)
Thanks again!!
-
Try
sudo update-grub
Remember to use the quotes " "
Just add parameters without the command
Should work with all pm-utils
ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
This is another way, very usefull because it doesn't need sudo.
-
Thanks for the update - I'll retry a few.
-
Hey here https://www.linuxliteos.com/forums/video-cards/screen-running-and-flickering/ (https://www.linuxliteos.com/forums/video-cards/screen-running-and-flickering/) is a solved similar issue which may be of some help.
-
Try
sudo update-grub
Remember to use the quotes " "
Just add parameters without the command
Should work with all pm-utils
ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
This is another way, very usefull because it doesn't need sudo.
Thought I'd update.....
This issue is weird :P I've tried a few quirks individually... Some "seem" to work but only once...
The dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
only suspends the system - which the system doesn't seem to have to a problem waking from - only a lid closed hibernate.
I can add a quirk/update grub - close lid the system hibernates no problems - after a few I'll press power to wake, I get GRUB, it "thinks" feather bar, shows a tty screen for a second then the log on prompt. - which.. The big IF..
If I get the "this session is locked - redirecting" screen pop up, which then comes back to same log on = it will work..
If it stays on the log on screen and I log on - goes black, needs to be rebooted.
- thus far it seems to work the 1st time after a reboot, after a 2nd hibernate goes black.
I've disabled light locker was able to wake and go thru "waking" and directly to desktop (no log on prompt)
I'm still testing 8)..
FWIW: Intel Mobile 945GSE Express Integrated Graphics Controller
I'll keep updated - not sure but since I'm not running "Asus EEE1025" I can move to a new thread..??...
@hb Was your issue with a flickering screen? Mines not doing this, other than waking from hibernate screen working normally.
- but may look into a bit..
-
Try
sudo update-grub
Remember to use the quotes " "
Just add parameters without the command
Should work with all pm-utils
ADD_PARAMETERS="--quirk-vbe-post --quirk-vbemode-restore"
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
This is another way, very usefull because it doesn't need sudo.
Thought I'd update.....
This issue is weird :P I've tried a few quirks individually... Some "seem" to work but only once...
The dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
only suspends the system - which the system doesn't seem to have to a problem waking from - only a lid closed hibernate.
I can add a quirk/update grub - close lid the system hibernates no problems - after a few I'll press power to wake, I get GRUB, it "thinks" feather bar, shows a tty screen for a second then the log on prompt. - which.. The big IF..
If I get the "this session is locked - redirecting" screen pop up, which then comes back to same log on = it will work..
If it stays on the log on screen and I log on - goes black, needs to be rebooted.
- thus far it seems to work the 1st time after a reboot, after a 2nd hibernate goes black.
I've disabled light locker was able to wake and go thru "waking" and directly to desktop (no log on prompt)
I'm still testing 8) ..
FWIW: Intel Mobile 945GSE Express Integrated Graphics Controller
I'll keep updated - not sure but since I'm not running "Asus EEE1025" I can move to a new thread..??...
Weird stuff. There is a known issue with lightdm-webkit-greeter that's where the popup window is coming from.
We should change a greeter eventualy. Probably with LL 3.0.
This command will put the comp to hibernation:
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
As for new thread question, please do so. Opening a new thread would help some folks with the same hardware.
This is Asus EEE1025 thread.
-
As for new thread question, please do so. Opening a new thread would help some folks with the same hardware.
This is Asus EEE1025 thread.
Started a new https://www.linuxliteos.com/forums/video-cards/black-screen-after-hibernate-intel-graphics/ (https://www.linuxliteos.com/forums/video-cards/black-screen-after-hibernate-intel-graphics/)
Updates will be posted...
***** UPDATE *****
I corrected the waking from hibernate on my hardware - Please see the new thread...
https://www.linuxliteos.com/forums/video-cards/black-screen-after-hibernate-intel-graphics/ (https://www.linuxliteos.com/forums/video-cards/black-screen-after-hibernate-intel-graphics/)