I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread:
Tue Jun 21 23:07:12 AKDT 2011: performing suspend
Tue Jun 21 23:07:28 AKDT 2011: Awake.
Tue Jun 21 23:07:28 AKDT 2011: Running hooks for resume
[code]...
I'm running Debian Squeeze on a Dell Studio 1558 laptop, and I have my laptop set to suspend when my lid is closed. Resuming from suspend seems to work but the screen remains blank, forcing me to hard reboot every time. Upon reading this thread
Code:
Tue Jun 21 23:07:12 AKDT 2011: performing suspend
Tue Jun 21 23:07:28 AKDT 2011: Awake.
[code]...
I like to suspend my laptop when I close the lid. I have squeeze installed. When I open the laptop lid all lights indicated that it coming out of suspend but the monitor stays black. It is worse since I install the ati drivers for the card instead of the xorg. It did it with both but worse with nonfree drivers. I can get it to come out by ctrl alt f2 and the ctrl alt f7. However yesterday that did not work but that was the first time. My laptop is an acer 5251-1513 amd processor v120, and hd 4250 radeon
View 6 Replies View RelatedAfter applying upgrades to debian 8.2 on a lenovo yoga3 notebook and a reboot I am not able to login into my GNOME desktop. The login screen stays black. If I press the power button to suspend I can see the login screen with default background for ~1 second before it turns black again. What can I do to fix this issue? Is there a way to login via terminal and do a rollback? Can I use my home folder an personal settings if i reinstall debian and keep the /home partition?
View 14 Replies View RelatedI have an ati 2600 mobile. I am running fedora 10 64 bit. If I have compiz enabled when I resume from suspend I just get a black screen with some garbed colors and I have to hold the power button to shut it off. I have tried turing sync to vblank off. It works fine with no compiz. Is there anyway I can get resume working with compiz enabled?
View 11 Replies View RelatedI just upgraded to 9.10 (Karmic Koala) on a Dell laptop. Now when I close the laptop lid to suspend and then open it to resume, the audio disappears; have to reboot to get the audio back. I remember having this problem a while ago back on Hardy Heron and finding a kludge to fix it - a line inserted in a shell script that gets invoked on resume
View 9 Replies View RelatedI have installed squeeze on a HP notebook. I have one small problem though.It does not resume from suspend. If I shutdown -> suspend, or close the the lid, or shut downs (suspends) as expected, but whenower it backup up, the screen just stays black.Hibernate is working fine.
output of lspci (if needed)
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
[code]...
My Acer Aspire 7552 laptop is running Debian Testing (just the main repos, no contrib or non-free). For some reason, it takes over five minutes to resume from suspend, and an absurd period to come back from hibernate (well over half an hour). Has anyone encountered this problem before, or have any tips on how to fix it? For the time being, I'm completely powering off every time I close my laptop because it's faster that way.
Output of lspci in case it helps:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
[code]...
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
View 8 Replies View RelatedWhatever way I suspend my laptop (menu, keyboard shortcut, close lid), it seems to suspend just find (no panic lights, suspend LED indicator flashing as expected). However, when i try to resume, the laptop seems to begin the proper wakeup process (for example, the DVD-drive is tested), there's a lot of HDD activity for about 5 seconds, screen does not power on, and then the laptop just shuts off.
System setup:
lucid beta 2, fully updated (just check now)
LG E-500 laptop /w nvidia gforce mobile 8400G
bios version 1.17 from June 2007 (not sure this is important)
Things I tried:
* Completely remove anything to do with gpu drivers and installed nvidia-current driver.
* Suspend stress test described here. this didn't work at all. The first test failed (with ac adapter attached) and the second test suspended but didn't automatically resume (see "the behavior" above). Also, when I booted up again, no apport bug report is created. I tried both with rtc set to utc=yes and utc=no. with utc=yes, the second test did automatically resume, but the same problem happened (laptop shutdown while resuming).
* The debugging steps described here, but I couldn't get the "no_console_suspend" option to work. I tried adding both "no_console_suspend" and "no_console_suspend=1" (without quotes) to the boot script in the grub menu, but when I did pm-suspend in tty1, the laptop really did suspend. I would like to try to do this again if someone could explain how to add this option.
Notes:
* Not sure this is relevant, but when I boot up after a failed resume attempt, wireless network is disabled (this only happens after a failed resume!!!).
* I found a package called nvram-wakeup in synaptic that seems to be related to this. This package is not installed. Should I install it?
In case this is relevant, forgot to mention I'm running ubuntu in dual-boot along side windows7.
I am having some pain with my new Squeeze installation, I am not sure if I am asking to much of it or it is an easy fix.
Firstly my system is laptop which I regularly plug a second monitor into. The video adaptor is an ATI HD4550 mobile.
My problem is that when ever suspend or hibernate my system, and even sometime when I boot up the screen(s) are just blank, although sometime they don't, it always happens if I suspend by closing the lid of my laptop, and only sometime happend with through Gnome is go ->System->Shutdown->Suspend. This is really annoying.
Another issue which I think is connected is that as I said I have a second monitor (most of the time) and when I boot up then it works until I log in, then a message pops up say the configuration can not be applied and it revert to Mirror mode or it does this thing where it places the second screen inside (virtually) the built in Laptop panel, it will not let me fix this through the monitors dialog just displaying the same message. I can fix this by doing
invoke-rc.d gmd3 restart
This gets as far as killing Gnome them it prints an error the to console, at which point Imopen a new terminal by ctrl+alt+f2 and
invoke-rc.d gmd3 stop
invoke-rc.d gmd3 start
then it works fine and even remember that I set the secondary screen to be the primary monitor through xrandr.
I tried install fgrlx drivers instead but it didn't really fix the issue, so I removed them.
I have recently updated my Ubuntu 9.10 install to Ubuntu 10.04 and the default kernel to 2.6.32-23 on my Acer Aspire 5738z laptop with 3 GB RAM and Intel GMA 4500m graphics card.
My problem is sometimes the laptop fails to resume after being Suspended to RAM. The problem is not consistent. Most of the time the system resumes properly but then some times it doesn't . It even doesn't respond to the Magic Keys. I am left with no other alternative but to keep the power button pressed till the laptop shuts down.
I downloaded Fedora-14-i686-Live-Desktop.iso and used the Fedora liveusb-creator to put this on a 2GB USB stick. Everything seemed to have gone well and it said complete; however, when I try to boot from the USB stick, I get a black screen with a linux copyright notice at the top and it just stays at that screen forever. I tried this on two computers with the same results.
I'd previously tried with Ubuntu and had a similar issue, it would go to a purple (if I remember correctly) Ubuntu screen and it sat that forever.
When I close my laptop lid (it goes into suspend mode). When I open it again, I can't see anything but a black screen. I have to reset the computer manually to accessUbuntu again.On a related note probably.. for 'some' screensavers, when I click to re-access my desktop, the screensaver freezes, but I can't see the unlock dialogue. I can however still type my password and it will unlock, I just can't see what I'm doing
View 2 Replies View RelatedI have tried booting from 2 different Ubuntu CD's (10-04-01 and 10-10) and a Fedora CD.All 3 CD's do the same thing, in Ubuntu I just see the first screen (Keyboard/Battery on the bottom with the guy next to it) and then the screen goes black but the lights, that indicate there's a computer connected and transmitting info onto the screen, are still on.
I know the CD's aren't the problem because they work on 2 other computers I have.The CD drive isn't the problem because took it out of a working computer and that booted up fine with the CD's.I've restored BIOS to default settings.I've tried booting with 1 stick of ram at a time but still doesn't boot.I've left the computer on for 3 hours but nothing appeared on the screen and the lights never turned off. It was just a black screen, nothing on it, not even a blinking cursor.I know it's capable of booting up CD's because the Windows XP setup disc boots.
I've installed Ubuntu on another PC and most things are great except fore the black screen that you get when you start the PC (just before the Ubuntu Logo). It stays black for 20 seconds. Is there something I can do to make it shorter like on my other PC.
View 9 Replies View RelatedTitle says it all. I close my laptop lid. It goes into suspend mode. I open it up again, the computer powers up... and I see a black blank screen. No key combinations seems to bring anything back.
View 9 Replies View RelatedI have an Acer 1551 4755, with Debian Squeeze. Normally my Debian Squeeze installations and suspending work fine on my other 2 laptops. For some reason this one is troubled. I can put into sleep with "pm-suspend" or "pm-hibernate" but the thing is that my laptop never wakes up. I endup restarting.
here is the hardware and module list
[URL]
I'm using a dell latitude d630 with an nvidia quadro 135M card. I'm able to suspend without any problems while running the X server. If I try to suspend on console without the X server running, the laptop wakes up to a blank screen. The screen remains blank and my only resort is to type sudo halt (with the screen off).I'm using the proprietary nvidia driver with the nvidia-kernel package on testing.
View 4 Replies View RelatedHad Ubuntu installed, it worked fine but I had to format for a new partition (out of space) I program in Windows, I would consider myself a Windows geek, and would like to try out Linux. After I boot into setup, it stays at a black screen. It did that when I was installed Ubuntu, the first time. I don't know how exactly it ended up working, after a lot of different things I was able to get it to boot.
View 3 Replies View RelatedFor the sake of security, I want the screen to be locked after the system is resumed from suspend or hibernation. Now the only way I can do this is to check the options "Lock screen when screen saver is active." in the screensaver preference. But this method is annoying since I have to type the password to quit the screensaver. Is there other way to do this? Thanks.
By the way, I use CentOS 5.2 x86_64.
Leonard
2009-3-21
Ubuntu Server 11.04 64bit seems to work fine on my Dell - most of the time at least. Sometimes upon boot, the screen stays black after grub. If it does boot correctly, I can find the following in dmesg:
[Code]...
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
View 11 Replies View RelatedI have a quite simple installation of Debian 8 Jessie XFCE and the resume from suspend is not working 9 out of 10 times. The system is single booted if that matters. I have found a few solutions to this problem but they were not suitable to my case as I don't have an Nvidia GPU but only Intel Onboard:
Code: Select all# lspci -v
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 2818
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0b <?>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 2818
[CODE]..
When I try to resume, I can hear the system booting but I can't see anything on the screen and the keyboard is not working either (no light on Num Lock and Caps Lock). The only option is to press the power button for a few seconds to stop the machine and then push again to start booting again.
After suspending my laptop, and then resuming the screen has black and white jagged wide zig zags across the screen. I can move the mouse and login fine, it's just the graphics are all screwed up. Has anyone had this problem before? Is this X? Is it a driver issue, my info is in my sig.
View 4 Replies View RelatedI have a laptop and an external monitor connected via displayport. I can configure both displays via settings with correct resolution and arrangement. However, this configuration is not sticking, and every time I shut down the laptop or close the lid I will need to fight with black screens and more to bring the same configuration again. Basically, it seems that the monitor is "stealing" the primary role to the laptop's native screen (I have it configured as secondary, but also being primary the configuration gets messed).
After many trial & errors, this is the routine I have found to make things work every time I boot / awake the system:
1. Boot. Laptop's display shows the booting sequence.
2. When the login screen should appear, laptop's display goes black, monitor shows background.
3. If I press F9 to increase brightness, the brightness icon appears in the monitor, but it is stuck at the minimum.
4. The only way to leave this point is by pressing F7 (project screen) and then F9 again to increase brightness. Then the laptop's screen does light up.
This is when I'm lucky. Sometimes the configuration goes mad and I get mirrored displays and different resolutions, without touching the settings myself. Also, if I unplug the displayport I run the risk of getting stuck with a black screen in the laptop, without any way of recovering the GUI other than rebooting (Ctrl Alt F2 will still show the command line screen).
My system is Debian 8 testing up to date, running in a Lenovo T430 with Intel components. I'm not sure the monitor is relevant here, but in any case it is an Eizo CS240.
I have an Asus z9100 laptop with an Intel 855GM integrated graphics chip, which is running Karmic (the purpose of the laptop is to be a MythTV frontend so my understanding is that it needs to run 9.x in order to connect to the MythTV 0.22 backend - I have installed and configured this using the installable Mythbuntu package) and the laptop is subject to this bug which causes random freezes:
[URL]
So, following advice for similar freezes I've seen, I have added the following options to my grub menu.lst on the kernel line:
nolapic nomodeset
and I have edited xorg.conf so that it makes use of the vesa driver instead of the Intel driver. This results in no freezes and if I wanted to watch Myth on the laptop screen I'd be squared away. However, the laptop has a damaged screen so the point was always to output the signal to an external monitor via its VGA out.
When I attach the external monitor and boot with the setup as described, the external monitor is never detected. But I noticed that if I remove the "nolapic nomodeset" from the kernel boot line, it is detected. However, signal is only output to it during the earliest part of boot (when the Ubuntu logo is in the center of the screen before the full-screen graphic with the animated progress line), after which the external monitor goes black and all the display output goes to the laptop screen. The external monitor power button is still lit up green as if it has been detected and is receiving signal, but it's just a black screen.
get the signal out to the external monitor after the initial part of the boot process, using the vesa driver? Here is the current state of my xorg.conf:
Code:
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection
[Code].....
I have just joined the Debian community, for the past 2 years I have been using Linux Mint (ubuntu), I am now using Linux Mint Debian 64. I have a Lenovo A700 ideacentre with a Broadcom 4313 WiFi card. I manage to get the card working, now I have a new problem. If I suspend the machine the WiFi will not connect on resume. Is there a simple command I can use to getting the connection restarted, or better yet a work around so it will restart on its own?
View 14 Replies View RelatedI'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation:
I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options:
Install newer kernel from Squeeze backports (2.6.38.2 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 2.6.37.0 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
out of no where it seems ubuntu no longer wants to cooperate when suspending/hibernating. the screen will just turn to a black screen without shutting down. each time i have to maually power down my laptop.
View 1 Replies View Related