[SOLVED] KDE black screen on resume after suspend

Yesterday I wasted the day investigating this and at the end the problem was not suspending the computer but the KDE lock screen as explained here. I thought to open a new thread so other people would not wasted their time looking into the wrong issue as I did.
Anyway, this is what happens, when KDE resumes, it only displays a black screen and the mouse pointer. The problem appears only when the system suspends through KDE (through the menu, the global shortcut or closing the laptop lid), suspending the system directly through systemd (systemctl suspend) or dbus (qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend true) works fine.
The way to recover is to kill kdm (ctrl+atl+backspace) or to restart kdm (switch to a terminal and execute systemctl restart kdm) .
As explained in the post #12 of this thread, if you use a transparent widget style (I use Oxygen Transparent) you have to add the lock screen to the background opacity exception list, for that go to:
System Settings -> Application Appearance -> Style -> Applications -> Configure … (to the right of 'Widget style') -> General -> Exceptions...
And select both "kscreenlocker" and "kscreenlocker_greet", if they do not exist add them through the 'Add' button.
Last edited by thepadawan42 (2013-07-20 08:43:33)

Hi,
I am also having this issue. After resuming from suspend-mode, I get a black screen with a mouse-cursor. I can follow you instructions up until "-> General". I don't see an "Exceptions"-button/area where I can select the kscreenlocker exceptions. Can you help?

Similar Messages

[SOLVED] black screen when resuming from suspend

Hi all,
I've got this new laptop and I can't get it to resume from sleep. The screen is black, probably not even powered. When I resume I am still logged into my session and can type commands (espeak for example, which works), and I can use my other computer to ssh and get the logs.
This new computer has got hybrid graphics card from AMD. I think this is relevant, as I've read some stuff about the GPU not being powered after sleep.
$ lspci
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Neptune XT [Radeon HD 8970M] (rev ff)
I'm using the open source drivers because I'd like to use bumblebee to switch between graphic cards. It's not working yet, though.
Also I've read some topics concerning similar issues, but most of them were solved by upgrading to a newer kernel, like 3.8 or 3.9 at that time. I am running 3.16.7 (these topics were from 2013, I found nothing more recent).
To suspend, I close the lid of the computer or use
systemctl suspend
I tried switching to pm-utils for suspend and resume, it still didn't work, event with all the troubleshooting tips on the wiki.
I'd be glad to provide any logs you would need in order to help me.
Thank you for your help
EDIT: I forgot to mention that the brightness keys work well before suspend but have no effect afterwards.
Last edited by Baudouin (2015-04-21 08:41:00)

I found this post, but I don't know if this is relevant or not.
It says:
ps: if you use this method, before suspending or hybernating make sure that the intel card is the one in use, or when you recover the pc the display won't show anything (or at least that's how it work on my laptop)
It is about AMD/Intel hybrid graphics with vga switcheroo, and I'm on AMD/AMD and not using switcheroo, but I don't know enough to say if this is the same problem or not.

Resume after suspend with uvesafb

Hello. I have an install with lxde on my acer one. It did resume after suspend before I did install v86d and set the framebuffer. No with uvesafb and v86d I do have a nice-looking framebuffer but I'm not able to resume after suspend. All I get is a black screen. I suppose it doesn't load proper modules. What to do?
Jan

I'll post my /var/log/pm-suspend.log:
Initial commandline parameters: --quirk-none
Sat Jan 24 18:02:52 CET 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: success.
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux acerone 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 18 20:17:17 UTC 2009 i686 Intel(R) Atom(TM) CPU N270 @ 1.60GHz GenuineIntel GNU/Linux
Module Size Used by
i915 58500 2
drm 83752 3 i915
joydev 11712 0
uvcvideo 57736 0
compat_ioctl32 3072 1 uvcvideo
videodev 34176 1 uvcvideo
v4l1_compat 15364 2 uvcvideo,videodev
mmc_block 11012 0
psmouse 55828 0
iTCO_wdt 12836 0
iTCO_vendor_support 4996 1 iTCO_wdt
serio_raw 7172 0
sg 26804 0
i2c_i801 10896 0
i2c_core 22804 1 i2c_i801
pcspkr 4352 0
video 18576 0
output 4608 1 video
uhci_hcd 24592 0
ehci_hcd 36876 0
jmb38x_ms 11396 0
intel_agp 27580 1
agpgart 31572 3 drm,intel_agp
usbcore 136976 4 uvcvideo,uhci_hcd,ehci_hcd
sdhci_pci 9088 0
sdhci 17028 1 sdhci_pci
memstick 10652 1 jmb38x_ms
mmc_core 46876 2 mmc_block,sdhci
acer_wmi 16320 0
rfkill 11724 2 acer_wmi
wmi 7848 1 acer_wmi
evdev 11296 8
thermal 17180 0
processor 41388 3 thermal
fan 6276 0
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
button 7824 0
battery 12036 0
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8332 2 snd_seq_oss,snd_seq
ac 6020 0
snd_hda_intel 411956 0
snd_hwdep 9092 1 snd_hda_intel
snd_pcm_oss 40320 0
snd_pcm 70020 2 snd_hda_intel,snd_pcm_oss
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 10120 2 snd_hda_intel,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 50852 9 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8160 1 snd
arc4 3712 2
ecb 4608 2
ath5k 100864 0
mac80211 161184 1 ath5k
led_class 5508 2 acer_wmi,ath5k
cfg80211 31760 2 ath5k,mac80211
r8169 33924 0
mii 6528 1 r8169
rtc_cmos 12332 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
ext2 66184 1
mbcache 8708 1 ext2
uvesafb 28388 1
cn 9120 2 uvesafb
sd_mod 26904 2
ata_piix 23300 1
ata_generic 6788 0
pata_acpi 6016 0
libata 158240 3 ata_piix,ata_generic,pata_acpi
scsi_mod 102036 3 sg,sd_mod,libata
total used free shared buffers cached
Mem: 1543124 250256 1292868 0 2712 44088
-/+ buffers/cache: 203456 1339668
Swap: 0 0 0
success.
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: /bin/stty: standard input: Invalid argument
success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt suspend suspend: success.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0
success.
Sat Jan 24 18:02:54 CET 2009: performing suspend
Sat Jan 24 18:03:20 CET 2009: Awake.
Sat Jan 24 18:03:20 CET 2009: Running hooks for resume
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video resume suspend: success.
/usr/lib/pm-utils/sleep.d/95led resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
/usr/lib/pm-utils/sleep.d/90clock resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt resume suspend: success.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: /bin/stty: standard input: Invalid argument
success.
/usr/lib/pm-utils/sleep.d/01grub resume suspend: not applicable.
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
/usr/lib/pm-utils/sleep.d/00auto-quirk resume suspend: success.
Sat Jan 24 18:03:20 CET 2009: Finished.

Resume after suspend suspends again

Hi,
for the last two weeks I've been experiencing some weird ACPI behaviour. When I resume after suspending with pm-suspend my system immediately suspends again. Shortly before suspending again the screen blanks and shows a line like this
[ 98.602112] ACPI: Unable to dock!
After it suspended again, the system can be resumed normally.
The system is a X230 with a full disk encryption. The suspend is done by calling pm-suspend with acpid. For further power management I use laptop-mode-tools, but the problem persists even after disabling it. Furthermore the problem can be reproduced on battery as well as AC.
I tried looking around, but have only found people having similar problems on hibernate and never any satisfying solutions. Has anyone ever experienced this problem and found a solution?
The relevant dmesg output is
[ 98.139750] ACPI: Low-level resume complete
[ 98.139785] PM: Restoring platform NVS memory
[ 98.140189] Extended CMOS year: 2000
[ 98.140208] Enabling non-boot CPUs ...
[ 98.146952] Booting Node 0 Processor 1 APIC 0x1
[ 98.226464] CPU1 is up
[ 98.229850] Booting Node 0 Processor 2 APIC 0x2
[ 98.309586] CPU2 is up
[ 98.309636] Booting Node 0 Processor 3 APIC 0x3
[ 98.389393] CPU3 is up
[ 98.392736] ACPI: Waking up from system sleep state S3
[ 98.578985] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1 - docking
[ 98.602112] ACPI: Unable to dock!
[ 98.695344] xhci_hcd 0000:00:14.0: >wake-up capability disabled by ACPI
[ 98.695354] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.695357] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.695504] ehci_hcd 0000:00:1a.0: >wake-up capability disabled by ACPI
[ 98.695511] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.695514] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.695835] ehci_hcd 0000:00:1d.0: >wake-up capability disabled by ACPI
[ 98.695842] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.695845] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.696233] sdhci-pci 0000:02:00.0: >MMC controller base frequency changed to 50Mhz.
[ 98.696841] PM: noirq resume of devices complete after 1.637 msecs
[ 98.696952] PM: early resume of devices complete after 0.084 msecs
[ 98.697001] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.697162] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.697164] e1000e 0000:00:19.0: >irq 44 for MSI/MSI-X
[ 98.697168] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.697177] xhci_hcd 0000:00:14.0: >power state changed by ACPI to D0
[ 98.697187] xhci_hcd 0000:00:14.0: >setting latency timer to 64
[ 98.697227] snd_hda_intel 0000:00:1b.0: >irq 47 for MSI/MSI-X
[ 98.697242] ahci 0000:00:1f.2: >setting latency timer to 64
[ 98.697433] ehci_hcd 0000:00:1a.0: >power state changed by ACPI to D0
[ 98.697442] ehci_hcd 0000:00:1a.0: >setting latency timer to 64
[ 98.697461] ehci_hcd 0000:00:1d.0: >power state changed by ACPI to D0
[ 98.697470] ehci_hcd 0000:00:1d.0: >setting latency timer to 64
[ 98.697511] i915 0000:00:02.0: >power state changed by ACPI to D0
[ 98.697514] i915 0000:00:02.0: >power state changed by ACPI to D0
[ 98.697520] i915 0000:00:02.0: >setting latency timer to 64
[ 98.724116] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 98.934829] usb 3-1.6: >reset high-speed USB device number 4 using ehci_hcd
[ 99.034359] ata2: SATA link down (SStatus 0 SControl 300)
[ 99.034447] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 99.035035] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 99.035039] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 99.035774] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 99.035777] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 99.036070] ata1.00: configured for UDMA/133
[ 99.041012] ata5: SATA link down (SStatus 0 SControl 300)
[ 99.061091] sd 0:0:0:0: >[sda] Starting disk
[ 99.231087] PM: resume of devices complete after 535.501 msecs
[ 99.231683] PM: Finishing wakeup.

Everyone is talking about systemd, but on RHEL 6 there is no systemd installed and also it is not supported. But I am still seeing the exact problem as described in the original question. This is on x230 lenovo.
Linux OS ver
Linux xxxxxxxxxxxxxxxxx 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed May 15 10:48:38 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
But currently the os is using pm_utils to do shutdown, suspend and hibernate etc.,
I couldn't suspend, hibernate nor shutdown. system wakes up in all three modes.
Any help would be much appreciated.
Last edited by yru (2013-07-28 14:20:01)

Resume after suspend / upgrades

Hi all, I've been using arch for about half a year and I'm very satisfied with it. There is, however, one thing that I can't change/find in arch, that is "after which event my laptop resumes after suspend". Suspend (s2ram or default scripts, that were in the system) / resume work fine, but after every (almost every) kernel upgrade somehow "resume event trigger" changes. It becomes or "resume after lid is open" or "resume after lid is open _and_ any key is pressed". I want it to resume just after lid is open without pressing key, but I can't find where I can set it. Could someone help me, please? Thanks.
Sorry for my English, it's my third language.
About the system:
laptop is Sony Vaio vpcea3s1e;
Latest upgrades (kde 4.6.2/kernel 2.6.38);
Suspend is done by s2ram.
here is my /proc/acpi/wakeup:
Device S-state Status Sysfs node
P0PF S4 *disabled pci:0000:00:1e.0
USB1 S3 *disabled
USB2 S3 *disabled
USB3 S3 *disabled
USB4 S3 *disabled
USB5 S3 *disabled
USB6 S3 *disabled
USB7 S3 *disabled
HDEF S4 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
PXSX S3 *disabled pci:0000:02:00.0
RP03 S3 *disabled pci:0000:00:1c.2
PXSX S3 *disabled pci:0000:04:00.0
EHC1 S3 *disabled pci:0000:00:1d.0
EHC2 S3 *disabled pci:0000:00:1a.0
RP06 S3 *disabled pci:0000:00:1c.5
PXSX S3 *disabled
PWRB S4 *enabled
It works exactly the same whether apcid is started, though.
and /etc/mkinitcpio.conf (HOOKS) :
HOOKS="base udev v86d autodetect pata scsi sata uresume filesystems "

Hi all, I've been using arch for about half a year and I'm very satisfied with it. There is, however, one thing that I can't change/find in arch, that is "after which event my laptop resumes after suspend". Suspend (s2ram or default scripts, that were in the system) / resume work fine, but after every (almost every) kernel upgrade somehow "resume event trigger" changes. It becomes or "resume after lid is open" or "resume after lid is open _and_ any key is pressed". I want it to resume just after lid is open without pressing key, but I can't find where I can set it. Could someone help me, please? Thanks.
Sorry for my English, it's my third language.
About the system:
laptop is Sony Vaio vpcea3s1e;
Latest upgrades (kde 4.6.2/kernel 2.6.38);
Suspend is done by s2ram.
here is my /proc/acpi/wakeup:
Device S-state Status Sysfs node
P0PF S4 *disabled pci:0000:00:1e.0
USB1 S3 *disabled
USB2 S3 *disabled
USB3 S3 *disabled
USB4 S3 *disabled
USB5 S3 *disabled
USB6 S3 *disabled
USB7 S3 *disabled
HDEF S4 *disabled pci:0000:00:1b.0
RP01 S3 *disabled pci:0000:00:1c.0
PXSX S3 *disabled pci:0000:02:00.0
RP03 S3 *disabled pci:0000:00:1c.2
PXSX S3 *disabled pci:0000:04:00.0
EHC1 S3 *disabled pci:0000:00:1d.0
EHC2 S3 *disabled pci:0000:00:1a.0
RP06 S3 *disabled pci:0000:00:1c.5
PXSX S3 *disabled
PWRB S4 *enabled
It works exactly the same whether apcid is started, though.
and /etc/mkinitcpio.conf (HOOKS) :
HOOKS="base udev v86d autodetect pata scsi sata uresume filesystems "

[P6N SLI Platinum] black screen NO BOOT after D-bracket replug [RMA-SOLVED]

Quick setup specs;
P6N SLI Platinum
E6600 (box/stock 2400mhz basic)
2x 1Gb DDR2 6400 Gskill HZ
Sapphire ATI X1600Pro (PCI-e basic)
Aerocool Zero DBA 620W
(2 HDs sata, 2 Hds pata, 2 optical pata at first -all OK at first, disconnected after, so irrelevant here ,( )
(XP Pro clean new install from start)
I tried to check the forum old posts before trying to write that new one, but could not find any really related totally adequate posts so far (or i missed them, sorry if so, then -?). I could already find very useful informations on first aid usual 'rebooting' procedures to follow with minimum new boot configurations, d-bracket new LED signals etc. But so far no luck, all same, nothing better, nothing cured here for the stuation here. ,(( Also excuse my english if not perfect, i am not english either. ,(
VERY bad & sad problem here... ,(((( :
All was working perfectly great during 5 days.. the P6N SLI platinum install went GREAT initially (as normal, not a first pc built, all normally happening, so far so good, etc).... all hardwares compatible together at first (dedicated ATX 'full' 8x8 pins connector too for the cpu only for ex -all working perfect at first try. quick tensions 5V/12V under msi dual core control tool perfect too etc), was great easy going/ great strong ultra-stability feeling on the hardware side.. i was just now concentrating on the software side (no special BIOS tweaks even attempted so far, all on basics-normal e6600/ddr2 auto-settings, apart at the end ddr2 quick test -when problem occured- on 450(900?)Mhz at 2.1V, far far easy under its possible specs max anyway.. and had been working perfect for 3 days with that little ddr2 boost try -no time for special bios further tweakings now, etc), reinstalling and transfering/reorganizing slowly my necessary files/hds/softwares from old to new setup, no oc, nothing special tempted (i was planning oc, new cpu more suited fan/silver6 etc only for the end..), LAN file sharing setup done, Realtek audio setup test done, etc ; installation had been so far one of the quickest and problem free ever... explaining maybe also my fatal lack of cautioun for just (too much) 3 sec in the end after 5/- days of perfect working new ring going on.. ,((( :
At first, i also tried to immediately install the D-Bracket too to check possible hardware install problems -very useful feature i of course thought too..and wanted to try too, "in case of"..- (installing it from quick reading of the printed manual..with no colour pic coding inside..and quick error coming from there thereafter with an initial mismatch usb/jbd1 inverted plugs connections.. *both* having the exact same pins numbers and dispositions, beeing side by side on mainboard layout.. and so able to connect both headers indifferently.. so i did not see it immediately (( .. and no way to see it otherwise as such, anyway.. ,( ), just to be sure all was ok. I noticed that LED were of course, never lightning (not normal).. but as EVERYTHING else was working fine (GLAN, sound, etc etc).. i did not bother more than that -- error checking not necessary.
Till that fatal clumsy day i wanted suddenly to.. check the D-bracket too. ((((
All was working well, XP pro opened for hours as usual etc..
i had not yet totally finished to install the motherboard in the pc-case (always on desk, free in sight..)... so i could always see the connections on it. ... and i noticed that ... the colour headers codes were NOT matching (usb=yellow..).. i had just stupidly initially badly connected the D-Bracket jdb1/usb adjacent plugs (inverting them), so... And still, all had ever worked perfect.. except the D-Bracket, of course, was sending back no lights then, obviously.. so i did the fatal error.. confident all was stable enough and strong if even that initial plug error had had no consequences at all.. i did the fatal bad move to try to UNPLUG the D-Bracket connectors and put them back in right orders WITHOUT switching OFF the power supply so... like an hot USB plug, sort of, in a way. fatal error.. :( :( :(
As soon as i began to remove the usb/jdb1 connectors and put them back in normal order... the system suddenly SHUT DOWN ... no special bad noise, no special smell.. just sudden SHUT DOWN.
From there.. impossible ever to boot back again the so far perfectly working machine (((((((((((( , always same till now :
i switch on the power supply.. orange led appears on motherboard (ok)... i switch on the motherboard.. green led on motherboard appears (ok)... CPU fan begins (ok), video fan begins (ok) .... and... NOTHING.. total black video screen. no more even possibility to see the BIOS. :( total dead startup .. and the fans are going on eternally, blocked eternally in that inital startup with leds on too (no sudden shut down after a few seconds.. just.. nothing)... :(
Suprem irony.. the D-bracket LED seems to 'work' now.. "of course". Just the PC no more booting at all ^. Only thing is that only green LEDs are appearing, no red ones... simply the sequence, from start and never changing :
1. GREEN 2. GREEN
3. GREEN 4. (---) (not red, just nothing -?)
If i look in manual, it means "Testing RTC (real time clock)". I don't know exactly what it means *here*, but sounds to me it is the most basic initial first BIOS checking.. and BIOS can't be reached for even that so ; BIOS fried???? :( :(
I tried every 'standard' things recommanded usually here in older posts, for new boots recovery attempts thereafter in such 'boot errors' situations (clear cmos button pushed in every possible ways -quick, long, quick etc..-, removing little by little everything but the very minimal least energy taxing setup; keyboard, cpu, video, motherboard; 1 ddr2 nearest cpu slot.. point).. NOTHING. Worst, i tried to boot with one of those elements missing.. exact same D-Bracket lightning from start to.. eternally (123 GREEN 4-nothing). Even tried to remove the little (cmos?) KTS lithium battery for a few hours -that could work sometimes with the old already ultra-sensitive amd/nforce2 chipset bioses problems, so i tried there too-?-; same 3 green lights and fans running and nothing else happening from there.. ((
Always the same; total dead boot as above. black screen. no possible access to even bios panel. ,(((
So my desperate questions, now: of course, the origin is obvious here; all happened "by my fault" when i tried 'too quickly' to 'hot-plugging' replace correctly the D-BRACKET plugs *without* switching off the power supply... all shut down suddenly when i put back correctly the usb& jdb1 headers... :( ;
- do you think there could be any possible last HOPES to recover the situation that i had missed (a well known situation in such d-bracket handling 'common' (?) connection error, a simple trick to try i had missed ??)
- do you think i FRIED something in the process on the motherboard ?? :( :(
- do you think it is 'only' the BIOS (fried????) ?? :( :(
- do you think i could have fried a specifical external key component in the process (not necessarily motherboard) : ddr2 modules, cpu, video card????? :( :(
- is my only solution is to send the motherboard to RMA (no other ways now) ???
please, don't hesitate to give me any possible hints to try to avoid the RMA process.
can i avoid it, right now?
is that possible to fry an whole board just with such a D-Bracket 'hot plug switch' (on a so far perfectly working -light- setup - no oc, little video card, etc) ???? :( :(
That is the only C2D Intel/ddr2 motherboard i have here around. No possibility to test elements by elements for precise error checking (cpu, ddr2 modules, video card or powersupply).
Only things i could check so far are;
- the power supply (aerocool 620W zeroDBA) ;
i tested it back on my old amd xp-m nforce2 setup.. always working apparently. NOT 'fried' so, apparently. but no way of course to test for exemple the special 8x8 (or 8x4) Intel ATX cpu connector on old xp-m motherboard. But power supply NOt fried at least, apparently -?
- the video card.
no way for me to really test the pci-e card on other motherboard around but.. i tried a very old PCI VGA card.. that one works on old setup.. and on P6N, no effect, doesn't improve the situation. So, not sure the new pci-e video card isn't fried.. but a new video card doesn't correct the dead boot problem.. (
No way for me to test the ddr2 or CPU directly though.
Do you think DDR2 or CPU could have been fried in the process too ???
or just, as i fear anyway, 'simply', the motherboard BIOS fried -??? :-(
Really, thx for any suggestions..
if there could be an 'hidden' trick i did not try yet to try to recover the (initially working perfectly!!! (( ) setup, WITHOUT engaging the motherboard RMA process (at least 2 or 3 weeks lost here to wait the return..online store etc..)....
please, suggest me.. ,((
i am *really* very sad of that stupid clumsy idea to want to 'enable' the D-Bracket.. all was working great so far.. and i lost all with just that stupid idea to try an hot plug bracket reconnection without switching off the power supply it seems.. can it be possible,sigh?? all seemed so stable before that, that i.. just lost my usual cautious just 3 sec too long it seems... :-(
Thanks in advance
hoping post not too long too, but i tried to expose the situation as precisely as possible; first time i ever had such a problem with a motherboard/system install.. that is quiet ironical knowing it was also the best and quickest/easiest easy going new built i ever had so far too.. till then ,( .. and all came from the 'helper' d-bracket 'luxury second hand possible boot helper diagnostic tool' checking in the end too, here.. really hoping i can avoid an RMA process.. and no other hardware elements (apart the motherboard?) could have been damaged in the process ? ,(((

hi, thx a lot for the quick answer. sorry for the length indeed (i did not know exactly how to describe the situation.. without omitting any later possibly important details).
Alas, i already tried that many times in following interesting asnwers on similar problems in old posts here; did NOTHING. ,(
But after your post, i tried it again, and removed for the remaining *hours* (6/8h?) the cmos battery as suggested again *too* so -pushed again the clear cmos button etc when battery out, then when in again, then replugging the powersupply etc; NOTHING better alas too. always same, no boot, black screen, no bios. ,(
Problem always the same, to sum up, for clarity:
power supply on => orange motherboard led is lightning up, motherboard on => green motherboard led is lightning up, cpu/video/case fans are working up as normal and.. that's all. nothing else forever. black screen. no signal. not a single chance to get again the bios setup screen.
another detail i omitted, maybe; keyboard lights are all lightnng up too.. and stay blocked in that state too. tested with 2 different keyboards, same. to shut down the leds, fans etc, only one solution, shut down the power supply button directly, at that stage.
right now, i test on barebone minimal system as recommanded too;
cpu, 1 dimm (closest cpu slot), video, keyboard. all rest disconnected.
i of course tried to reset the cmos with the 'magical red button' many times before, with power supply cable plugged out, pushed the button trying almost every possible way so far (quick, long, long sequences, short sequences etc etc)... changed NOTHING so far -is that thing working?? ,(. and right now, same after hours with cmos battery removed too. ,(
the d-bracket leds are always (now it is correctly plugged..) :
123 GREEN 4 (nothing)
"Testing RTC (real time clock)"
another 'interesting' detail is that; those leds are appearing IMMEDIATELY after the motherboard is switched on, from start (green led appearing on P6N). and it is staying as such till the end. nothing else. i tried to connect also the case speaker ; no bips, no sound signals at all too.
I also remind the system was WORKING like a dream during 5 days *before* i had that sudden TOTAL boot problem.... AND i touched almost nothing in the bios too all along, for initial security reasons too.. (i was concentrating on the software installs anyway right now, NOT on the oc side..). The ddr2 quick little change i did was also the ONLY change i tempted to simply test quickly some setting i already saw working without problem with that P6N and that kind of ram.. and it was working without problem so far too, so.. all the time idem. And it had been perfectly working for 3 days as such untouched from there; no problems at all (those memory modules have been seen on that motherboard largely at those specs, why i did that quick test anyway.. far under their possible max -micron chips). it was even working so well i forgot to put the setting back as default after that quick ram test.. so much it was stable too (even if i had not time to do real memtest test on that one - i did for many hours with the initial automatical default settings too, to check the ram quality, was perfect for many hours, so ok too, no bad ram initially too-; was so stable for all my XP software installs operations etc.. that i forgot it thereafter, to be true..why it stayed like that till that moment (incidently).. but i preferred to mention it 'just in case' though, yes. i also did not push at all the dimm voltages in the process, it was always far inside the specs at 2.05V to be exact -usual for that ram too up to those numbers easy for it. i did not push the ram voltages either so..).
The problem ONLY appears when i wanted to unplug the *initially* badly connected D-bracket headers so (inverted headers.. but that caused NO problems either so far too for the system stability.. only the LEDs were of course not working so far..) : i did the error to NOT switch off the power supply. :(
*then* immediately the system shut down... and above situation appeared. ,(
BUT all was working perfect before.. ram setting included so. ,((
So my simple questions now too ;
- do you know what means *exactly* the d-bracket message 'Testing RTC" (123 GREEN, 4 nothing).. initial bios problem, isn't it?? other ways to recover it now?? ,((
- is it a WELL KNOWN PROBLEM when we try to disconnect and replug too hastily the d-bracket headers without switching off the power supply (*my* main erorr here, it seems :( :( ) ????
... and of course, do you think it could have *fried* another key component (cpu, ram -?? why i reminded the setting, just in case-?-, video card? .. ) with that d-bracket initial disconnection error ... ,(
as i said, i have no secondary c2d/ddr2 motherboard here : no way to test the cpu and ddr2 modules on another motherboard to be sure too here. :( i absolutely can't know if they have been damaged or not, here.. :( :(
any other idea for the motherboard itself though ??? ,(
once again, thx a lot for any suggestions and precisions on that problem (is that a COMMON well known problem with the d-bracket, when we unplug and replug it without extrem care like i did -my main inattention error it seems.. mainly because all was so stable before too.. ((( - without shutting down the power supply/system FIRST ???? can it be possible 'only' that shut down all the system??? (( )
thx in advance again +

Black screen on resume from sleep using open source AMD/ATI driver

When waking from sleep using systemctl suspend or pm-suspend , I am presented with a black screen. I can still open programs, type, etc. but cannot see what I am doing. I usually just wind up rebooting from whatever terminal I had open, but again I can't see what I am typing. Upon reboot, the screen starts back up again. Everything else seems to resume from sleep just fine, it's just the screen that won't turn back on.
I came from Ubuntu and had this same problem there. However, I only had this problem when using the open source xf86-video driver; when using the proprietary drivers, I was able to suspend/resume just fine. So it seems this problem is specific to the open source drivers.
If I'm using an external monitor, my external monitor will resume just fine after waking from sleep, but the laptop screen will not.
Googling around shows this is a common problem with AMD/ATI cards, and after a lot of attempts and failures I'm interested in knowing if anyone else has solved this problem.
What I've tried so far (without success):
-various quirks included with pm-utils to turn on dpms after resume
-xrandr after resumption from sleep
==xrandr --output LVDS --off (If used without suspending (so while the screen still works) this seems to crash Gnome the first time around, but Gnome automatically restarts. If used a second time, it completely blanks the screen and requires a reboot)
==xrandr --output LVDS --mode 1600x900
-xset dpms force on or xset dpms force off after resumption from sleep
-vbetool dpms off and vbetool dpms on results in error message "Real mode call failed"
-scripts using vbetool or xrandr when resuming from sleep
-switching between virtual consoles and gnome using alt-ctrl-fn-f1 and alt-ctrl-fn-f2 keys
My setup:
-HP Envy dv7
-UEFI dual-boot with Windows 8
-AMD Radeon HD 7640G
-xf86-video-ati 1:7.2.0-1 driver
-Gnome DE using GDM login manager
Thank you.
EDIT: I did try using the proprietary drivers for a time, but found I couldn't adjust my brightness. At first I thought working suspension > adjustable brightness, but I quickly changed my mind after one night of trying to work on an unadjustable maximally bright screen.
Last edited by broahmed (2013-11-23 02:18:57)

Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
John

Resume after suspend-to-ram not working whit catalyst

$uname -a
Linux drog-laptop 3.4.6-1-ARCH #1 SMP PREEMPT Fri Jul 20 08:21:26 CEST 2012 x86_64 GNU/Linux
$ pacman -Qs catalyst
catalyst-hook 12.6-3
catalyst-utils 12.6-1
lib32-catalyst-utils 12.6-1
/var/log/pm-suspend.log
http://pastebin.com/kWMWKqBy
groups
lp,wheel,games,video,audio,storage,power
The suspend works fine with foss, but fails with catalyst
EDIT:
kernel line: root=/dev/sda1 ro nomodeset vga=0
lsmod
http://pastebin.com/NHpZRTv0
i have xorg-server 1.11.4-2
Last edited by drog (2012-07-23 17:31:43)

I have a Dell Studio 1555 - ATI 4570 with stock kernel26_x86_64 (2.6.33.3-1), catalyst 10.3 and all is woking ok (hibernate/suspend/restore).
The "multibyte access to EC" patch is added to stock kernel and all related problems is gone for me.
It is a problem with restore from suspend (black screen) because of catalyst 10.4, but until that problem is solved I keep catalyst 10.3.
I posted that problem here:
http://bbs.archlinux.org/viewtopic.php?id=96482
If you use xf86-video-ati driver, I don't know what is the problem.
When I tested open source ati driver to see if powersave features is added, suspend/resume was working for me, but no luck with powersave features, so I stay with catalyst driver)
Last edited by mits (2010-05-07 10:16:36)

Black screen of death after warning "Disk 1 has the same disk identifiers as one or more disks connected to the system. "

Hi,
I am having the same problem / event warning, only one second after the warning occurs, I face a black screen of death leaving me with no other option than to switch off and reboot. After reboot I can work for some time but as far as I can see there is a
spontaneous re-occurance of the same warning and subsequent black screen of death.
It is hugely frustrating and don't seem to be able to solve it. It occurred in W8/W8.1 and W10 TP. All hardware seems fine. There are no other events that occur near the time when the BSOD occurs so I suppose its that.
HD (SSD'S) seem to have unique identifiers so I don't understand it at all. It does not matter whether I am browsing the internet, rendering images or simply leaving my laptop untouched (M6500 DELL).
Please help. It occurs 3 - 5 times a day and it seems unworkable.
Mike

Hi MAVH2014,
Which version are you running? Do you installed all updates for current Technical Preview?
Can you find any related events in Event Viewer?
For your disk identifier issue, if you have checked them already, I suggest you use following command to change the value:
Uniqueid
http://technet.microsoft.com/en-us/library/cc730793.aspx
Alex Zhao
TechNet Community Support

Windows 7 Black screen with cursor after boot camp partition

So I realise this is a problem that was plaguing people a few years back. So I'll go from the very start.
I've downloaded a copy of windows 7 professional 64bit from the Microsoft website. My optical/CD drive isn't working, so I've been unable to use it
to install windows. I decided I'd try booting from my USB. So I have the ISO file and formatted my USB and I've downloaded the latest drivers for boot camp assistant on my mac (version 5.0.4) I'm up to date with every update for my mac. Now, I do realise that Apple doesn't recommend using a USB to load windows, but I watched this http://www.youtube.com/watch?v=8z1gqw0ougo and it explained how to get the checkbox up when you're in boot camp so you can run from your USB.
My problem now, is that straight after I have partitioned my hard drive, it goes on to install windows but upon restarting it reaches "the black screen of death" with just the white cursor blinking. I've tried multiple times and keep getting the same result. I've even tried what Apple suggested and only have one USB device plugged in http://support.apple.com/kb/TS4536
The details for my mac are as follows:
Model Name:
iMac
Model Identifier:
iMac10,1
Processor Name:
Intel Core 2 Duo
Processor Speed:
3.06 GHz
Number of Processors:
1
Total Number of Cores:
2
L2 Cache:
3 MB
Memory:
4 GB
Bus Speed:
1.07 GHz
Boot ROM Version:
IM101.00CC.B00
SMC Version (system):
1.53f13
Serial Number (system):
W800992A5PE
Hardware UUID:
A108E54E-3C53-5AF8-BFDF-2CF7ED567A74
and it's a late 2009 model.

I have solved this issue now but seem to have encountered another one. I solved the above issue simply by keep on trying time and time again, partitioning the hard drive and trying to install windows 7.
Anyway, I have encountered this error: windows setup could not apply the configuration set. The WINDOWS folder cannot be found.
Please help!

Black Screen On Boot After Nvidia Driver

I just installed arch and went to install my nvidia driver right afterwards. I now boot up and after grub i get a black screen. I am 99 percent sure i know what this problem is and i have had somthing similar with gentoo. I have a sandybridge so i have my nvidia card and the intel hd graphics. i remember in gentoo i had to go in the kernel config and disable intel hd graphics . i dont know how i would go about doing this here as i am new . i really dont want a custom kernel.
Last edited by paulb787 (2012-06-18 09:25:03)

SEMI-SOlVED
if you have a sandybridge motherboard and have intel hd graphics on in your bios (Lucid). after the nvidia driver is installed udev seems to pick up the intel card at boot. Blacklist i915 and intel_agp to fix this problem.
what loads those modules udev? mkinitcpio? is there any way to have them both? like choice your primary video card? im sure if i had two monitors i would be able to boot up with the one pluged in to intel graphics and when X loads xinerma would work with both. i dont have dual monitors but it still would be nice to have an option. is there any sandybridge features in linux?
Thank You
Paul
Last edited by paulb787 (2012-06-18 09:28:46)

MacBook Pro with Black Screen at restart after apple logo

Hi,
My MacBoock Pro get a black screen with the arrow working after restart. At restart works the chime, the apple logo but after that instead of login screen appears a black screen with the mouse arrow. Sound works, bright works but nothing. I had testing all the comands to restart: Cmd+Alt+N+V, Cmd+Alt+P+R, Shift+S, S, D, Shift+S, Shift+Ctrl+Alt+Start... reinstalling without format... everithing. What can i do without rainstall from 0?
Thanks

Blank (lighted, but black) screen with cursor at bootup
[SOLVED] - Macbook Air Sleep/Wake problem
Dark screen on start-up can only see curser

Black screen on startup after installing security updates KB293357 and KB2937610 on Win 7 64bit

After installing security updates KB293357 and KB2937610 (both related to .NET) on Win 7 Enterprise 64 bit, my computer fails to start up correctly:
- start up and windows boot screen
- then black screen and computer freezes
The only option to this problem I found so far is do a cold reboot and then let system repair uninstall the updates. Is there a better way to solve this problem?
System:
Asus UL80VT laptop
NVIDIA GeForce G210M (driver version 9.18.13.2702)
Win 7 Enterprise, fully updated

Hi,
After you unstall the two updates, does the black screen issue completely disappear? We should first figure out whether the two updates are the culprits.
Since the two updates are related with .net as you mentioned, then here's a .NET Framework Repair Tool released by Microsoft, I suggest you try it and check if it cna detect something.
http://www.microsoft.com/en-in/download/details.aspx?id=30135
Check your event viewer and see if it recorded something valuable.
Yolanda Zhu
TechNet Community Support

Help solving the Black Screen of Death

Hello There!
I have an HP Touchsmart 610-1100z 3 days ago I put it to sleep and when I tried to wake it up nothing happened. I restarted it and it was just a black screen, no HP logo ect, but I could hear all the fans and drives working. I checked the light issue with a desk lamp and revealed that is not the problem. I then tied the BIOS F10 to F5 work around with no luck. I have gotten it to boot up twice since then by repeatedly turning it off and on until by sheer luck it just boots up. When it boots up there is absolutely no issue but clearly something is eskew that I would like to fix so that I don't live in fear of turning off my computer. Does anyone have any ideas?

Hello Vman009,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that you are getting a blank screen when you boot your HP Touchsmart 610-1100x All-In-One Desktop PC. I am providing you with a link to an HP Support document: HP and Compaq All-in-One and TouchSmart Desktop PCs - Screen is Blank after Starting the Computer, which addresses what appears to be the issue you are describing. I would recommend that you review the document and make the adjustments recommended.
Please re-post if you require additional support. Thank you for posting on the HP Forums. Have a great day!
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
Dunidar
I work on behalf of HP
Find out a bit more about me by checking out my profile!
"Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

Black screen with underscore after updating ubuntu on Lenovo G560

hello everybody, I'm new here. I looked for this problem online during the past few days but I haven't found a solution. I have a Lenovo G560 and I divided my hard drive into two partition, I installed Ubuntu on C:\ and Windows on D:\ and I haven't had any problem, but after updating ubuntu to version 14 my computer couldn't boot anymore. the bios loads and I see the Lenovo icon but then I just get a black screen with an underscore (not a blinking underscore), I tried booting from a bootable USB stick but the same thing happened (I put it as the first device to boot from in BIOS settings). can anyone please tell me what are my other options ? what should I try now ? thanks in advance and have a good day !

Hi s, and welcome to Apple Discussions.
Try this:
Hold down the Option+Command (Apple)PR keys, boot/restart your MBP while continuing to hold down those four keys, and after you hear the startup chime for the second time, release the keys. That should reset your PRAM and resolve the issue.
If the issue persists, while you're booted into Open Firmware, just after the prompt, type in:
reset-nvram
then press return, then type in:
reset-all
and press return. This should restart your MBP and it should go back to starting normally.

[SOLVED] KDE black screen on resume after suspend

Similar Messages

Maybe you are looking for