[SOLVED] GDM: black screen after "Reached target Graphical Interface"

Hi all,
Since an upgrade on my work PC a week back or so, it no longer boots properly into GDM / Gnome. It will boot up to this message:
[ OK ] Reached target Graphical Interface
Then the screen will flash to black and back, then again turn black permanently. I can still go to other tty's. It's just GDM that's being frustrating.
There are no useful logs for either GDM or Xorg - the last log for both dates from the last time things worked properly. Nothing useful in dmesg either. I've already reinstalled xorg, xorg-drivers, gdm, etc., but no luck.
Some guidance would be most appreciated!
Last edited by mhelvens (2014-11-20 12:37:31)

I finally found an answer here:
https://bbs.archlinux.org/viewtopic.php?id=188434
I've been using infinality-bundle, and those packages seem to have been moved (?) I had to add this repository to `/etc/pacman.conf`:
https://wiki.archlinux.org/index.php/un … ity-bundle
Then a system update, and presto!

Similar Messages

[Solved] Computer getting stuck at Reached target Graphical Interface

Okay so today.. I installed awesome window manager, lightdm by using the systemctl enable lightdm -f then i enable it. I also removed a series of video drivers.. When I got home from school to try out awesome. It won't boot and gets stuck at this. Sorry if I have been a pain the neck for y'all.
xf86-video-ark 0.7.5-5
xf86-video-ast 0.97.0-5
xf86-video-cirrus 1.5.2-4
xf86-video-dummy 0.3.7-3
xf86-video-fbdev 0.4.4-3
xf86-video-glint 1.2.8-5
xf86-video-i128 1.3.6-5
xf86-video-intel 2.99.916-2
xf86-video-mach64 6.9.4-4
xf86-video-mga 1.6.3-3
xf86-video-modesetting 0.9.0-2
xf86-video-neomagic 1.2.8-3
xf86-video-nouveau 1.0.11-1
xf86-video-nv 2.1.20-5
xf86-video-openchrome 0.3.3-4
xf86-video-r128 6.9.2-3
xf86-video-savage 2.3.7-3
xf86-video-siliconmotion 1.7.7-5
xf86-video-sis 0.10.7-6
xf86-video-tdfx 1.4.5-5
xf86-video-trident 1.3.6-6
xf86-video-v4l 0.2.0-14
xf86-video-vesa 2.3.2-5
xf86-video-vmware 13.0.2-2
xf86-video-voodoo 1.2.5-5
http://i.imgur.com/eExPX5T.jpg
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by StormHF (2014-11-30 03:02:36)

My first thought was to wonder why on eath you installed so many video drivers. That likely would not cause this problem, but it is just silly - and it is a separate symptom of the same underlying problem:
We've now learned that you did not install these drivers, nor the system, but two different people (neither you) have installed and configured your system. One of these people doesn't even use archlinux, and as you say has "limited knowledge" about it. Talk about the blind leading the blind ... but you are not blind, you've just opted to close your eyes and not learn anything about your system.
There is no way for us to know what is happening on your system when you yourself are clueless. You should just start from scratch and do it right following the beginner's guide. But even this should happen only after you ask yourself why on earth you'd want to use archlinux - it's really not what you seem to be looking for.
As for losing your usb drive ... can't you find another anywhere?

Stuck at 'Reached target graphical interface'

Edit:
An important edit on mkinicpcio. Previously I reported it the other way around.
I went through a complicated process of turning my first single-partition arch install into a Windows 7 dual-boot install (windows first) with separate /var and /boot partiotions.
Notable stuff:
0. Now MBR instead of GPT
1. PArtition order changed
2. fstab now uses by-lebel (custom unique labels) mounting instead of UUID's
3. I had problems recreating kernel (initramfs) images. During the last, successful attempt I issued:
mkinitcpio -p linux -k linux
instead of
mkinitcpio -p linux
(I was desperate )
4. Since restoring clonezilla image of my arch was braking the existing Windows installation I restored my arch install using
rsync -ax <source> <target>
This should be a complete list of the stupid things I did.
Now I get just
[OK] Reached target graphical interface
Gdm service status (photo):
https://onedrive.live.com/redir?resid=6 … oto%2c.jpg
Xorg log:
https://onedrive.live.com/redir?resid=6 … ile%2c.txt
What I've already tried:
- updating the system (pacman -Syu)
- deleting my custom 20-intel.conf
I can [Alt+F2] to get access to root.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# two lines below - old entry from my single-boot installation
# /dev/sda2
# UUID=a4d4efe1-d07d-4531-9300-5e7362e68e6c / ext4 rw,relatime,data=ordered 0 1
# /dev/sda7 UUID=e4b15e16-e224-4284-9f00-141885ad8620
LABEL=oRoot / ext4 rw,relatime,data=ordered 0 1
# /dev/sda5 UUID=45b7acb0-1860-45a1-96ae-882010c38129
LABEL=oboot /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sda6 UUID=95ee952a-c254-424c-be0f-766d7f61301b
LABEL=ovar /var ext4 rw,relatime,data=ordered 0 2
# LABEL=HIT_160 /mnt/HIT_160 auto nosuid,nodev,nofail,x-gvfs-show 0 0
# LABEL=HIT_262 /mnt/HIT_262 auto nosuid,nodev,nofail,x-gvfs-show 0 0
Last edited by bbarcher (2014-03-08 14:07:46)

My first thought was to wonder why on eath you installed so many video drivers. That likely would not cause this problem, but it is just silly - and it is a separate symptom of the same underlying problem:
We've now learned that you did not install these drivers, nor the system, but two different people (neither you) have installed and configured your system. One of these people doesn't even use archlinux, and as you say has "limited knowledge" about it. Talk about the blind leading the blind ... but you are not blind, you've just opted to close your eyes and not learn anything about your system.
There is no way for us to know what is happening on your system when you yourself are clueless. You should just start from scratch and do it right following the beginner's guide. But even this should happen only after you ask yourself why on earth you'd want to use archlinux - it's really not what you seem to be looking for.
As for losing your usb drive ... can't you find another anywhere?

Stuck on "Reached Target Graphical Interface" GNOME

I was a bit hesitant to post this because I know there are tons of topics about this already, but after several hours of troubleshooting I've gotten nowhere and I really could use some help.
I got Arch installed earlier today and decided I was going to use Gnome as my DE. I installed gnome and gnome-extra using pacman -S and everything seemed to go fine. It asked me to chose between something called mesa libgl, nvidia and another option. I assume these are the drivers; I just chose the default "mesa".
I then used systemctl enable gdm.service. I'm not sure if something should have happened, but based on other threads I've read it sounds like this should have launched Gnome.
Either way I rebooted expecting it to launch Gnome, but it gets hung up on "[OK] Reached Target Graphical Interface". The only way out is to Alt+F2 then log in with "root" and my password.
Can someone tell me what logs I can post that can help and how I can get those logs to my Windows boot? I currently have Windows 7 on an SSD and Arch installed on a second hard drive. I have no idea how to copy or save the logs to bring into Windows (or if that is even possible).
I just installed Arch this morning with the newest ISO file.
My graphics card is an Nvidia GeForce GTX 570
Last edited by Herdo (2014-05-24 05:37:24)

henk wrote:
Herdo wrote:It asked me to chose between something called mesa libgl, nvidia and another option. I assume these are the drivers; I just chose the default "mesa".
My graphics card is an Nvidia GeForce GTX 570
Herdo wrote: I then download 3 new xorg packages
Herdo wrote:I installed xf86-video-nouveau driver and the xf86-video-vesa driver and it works. The only problem I am having now is that the colors look washed out. Slightly fuzzy and pixelated looking.
Correct me if I am wrong, but to me it looks like you went straight for Gnome without setting up X, or your graphics card.
I had a quick look at the Beginners Guide -after a very long time-, and to my surprise the Post Installation part had changed. Setting up X and graphic card has moved to
a different wiki page. I am wondering, did you look through this page?
- If you want your graphic card to work properly, you probably would be better of with the nvidia package.
- After installing Xorg an de video drivers why did you not just re-enable gdm?
That's exactly what happened. I wasn't aware I had to configure Xorg or my graphics card when I finished the initial setup. Thanks for the link.
When installing the nvidia package, do I need to uninstall the previous driver packages?

LXMD Hangs Reached Target Graphical Interface

Hey
I've just installed lxde & lxdm but it busts hangs at Reached target graphical interface,
here is the output from systemctl status: Started lxde display manager
Lxdm.service main process exited code=exited status=1/FAILURE
lxdm.service entered failed state
And ive tried starting x manually but that fails as well.

I've also used systemctl enable lxdm.service but nothing happens any help?

Black screen after login while on battery with graphics switching enabled

Getting a black screen after entering my password while logging into my account while on battery with graphics switching enabled. Everything is up and running, I just can't see it.
I can log into the guest account on battery
I can log into my account while plugged into power
I can log into my account on battery if graphics switching is disabled
I believe something that is starting up in my account is causing the system to switch from integrated to discrete graphics on login, and that switch isn't working correctly on battery power.
As a work around for now, I can run with graphics switching disabled, but I'd like to solve this so I get longer battery life.
MacBook Pro Retina 15"
Mountain Lion
All updates applied

I had the same issue and managed to reslove it.
Shut down your machine.
Power it back on while holding the 'shift' key (left or right, doesn't matter)
You will see a greay progress bar go across the screen while you boot in to 'safe boot'
Once booted, login, and go to Energy Saver and turn on 'Automatic Graphics Switching'.
Reboot back in to normal mode, and you should be able to log back in and see again.
I did this without being plugged into AC power.
Hope it helps!
Cheers!

[Solved] Amilo XI 2550 - Black screen after fresh install

Dear archlinux users,
I have been reading the archlinux wiki and forums since I started using arch several years ago. It was always possible to solve the problems I ran into by consulting these webpages, therefore a big thanks to the community for the provided help.
Two weeks ago I installed arch on a Fujitsu Siemens Amilo XI 2550. The first problem I ran into was that booting the live-cd resulted in a black screen and I could not even start with installing arch. This problem was solved with the kernel parameter 'nomodeset'.
The first boot of the freshly installed arch also resulted in a black screen after the GRUB menu which was perfectly displayed. After some searching (here and here and ...) I plugged in an external monitor and it showed the login screen. I then installed KDE because I thaught the problem might not show up with X and KDE running. After the login to KDE I realized that the brightness of the laptop display is nearly black but not totally. It seems as if the brightness is at a very low level, but brightness cannot be controlled with the Fn+F8 or Fn+F9 commands. But I see a OSD that indicates that the controls are used but without effect. So at the moment it is only possible to work on the laptop with another display connected to it.
Maybe of use:
ls /sys/class/backlight/
acpi_video0
radeon_bl0
less /sys/class/backlight/acpi_video0/bl_power
0
less /sys/class/backlight/acpi_video0/actual_brightness
7
less /sys/class/backlight/acpi_video0/brightness
7
less /sys/class/backlight/acpi_video0/max_brightness
7
less /sys/class/backlight/radeon_bl0/bl_power
0
less /sys/class/backlight/radeon_bl0/actual_brightness
255
less /sys/class/backlight/radeon_bl0/brightness
255
less /sys/class/backlight/radeon_bl0/max_brightness
255
dmesg | grep drm
[ 0.736559] [drm] Initialized drm 1.1.0 20060810
[ 0.743608] [drm] radeon kernel modesetting enabled.
[ 0.743678] fb: switching to radeondrmfb from VESA VGA
[ 0.744054] [drm] initializing kernel modesetting (RV630 0x1002:0x9583 0x1734:0x1107).
[ 0.744065] [drm] register mmio base: 0xCFEF0000
[ 0.744067] [drm] register mmio size: 65536
[ 0.744172] [drm] Detected VRAM RAM=256M, BAR=256M
[ 0.744174] [drm] RAM width 128bits DDR
[ 0.744257] [drm] radeon: 256M of VRAM memory ready
[ 0.744259] [drm] radeon: 512M of GTT memory ready.
[ 0.744275] [drm] Loading RV630 Microcode
[ 0.744345] [drm] Internal thermal controller without fan control
[ 0.744386] [drm] radeon: power management initialized
[ 0.744389] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 0.762830] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 0.762873] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.762874] [drm] Driver supports precise vblank timestamp query.
[ 0.762937] [drm] radeon: irq initialized.
[ 0.794780] [drm] ring test on 0 succeeded in 1 usecs
[ 0.795253] [drm] ib test on ring 0 succeeded in 0 usecs
[ 0.795942] [drm] radeon atom DIG backlight initialized
[ 0.795945] [drm] Radeon Display Connectors
[ 0.795947] [drm] Connector 0:
[ 0.795948] [drm] LVDS-1
[ 0.795950] [drm] DDC: 0xac0 0xac0 0xac4 0xac4 0xac8 0xac8 0xacc 0xacc
[ 0.795951] [drm] Encoders:
[ 0.795952] [drm] LCD1: INTERNAL_LVTM1
[ 0.795953] [drm] Connector 1:
[ 0.795954] [drm] DIN-1
[ 0.795955] [drm] Encoders:
[ 0.795956] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 0.795957] [drm] Connector 2:
[ 0.795958] [drm] HDMI-A-1
[ 0.795960] [drm] HPD1
[ 0.795961] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 0.795963] [drm] Encoders:
[ 0.795964] [drm] DFP1: INTERNAL_KLDSCP_TMDS1
[ 0.795965] [drm] Connector 3:
[ 0.795966] [drm] VGA-1
[ 0.795968] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 0.795969] [drm] Encoders:
[ 0.795970] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 1.278449] [drm] fb mappable at 0xD0141000
[ 1.278451] [drm] vram apper at 0xD0000000
[ 1.278453] [drm] size 9216000
[ 1.278454] [drm] fb depth is 24
[ 1.278455] [drm] pitch is 7680
[ 1.278527] fbcon: radeondrmfb (fb0) is primary device
[ 1.726069] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 1.770030] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:00.0 on minor 0
Until now and amongst others I tried the following things.
Using kernel parameters
video.use_native_backlight=1
video.use_native_backlight=0
acpi_osi=linux
acpi_backlight=vendor
and others I just cannot remember.
Masking backlight
systemctl mask systemd-backlight@backlight:acpi_video0.service
systemctl mask systemd-backlight@backlight:radeon_bl0.service
Setting bl_power
echo 1 > /sys/class/backlight/acpi_video0/bl_power
echo 1 > /sys/class/backlight/radeon_bl0/bl_power
Nothing of the above was improving the situation.
Your help on the problem would be highly appreciated.
Best regards
mgs
Last edited by mgs (2014-10-27 10:15:11)

Hello Trilby,
thanks for the reply.
Trilby wrote:If nomodeset worked with the installation medium, why haven't you tried that for the same problem on your installed system?
The kernel parameter 'nomodeset' results in a working display but without X support, due to the fact that with 'nomodeset' there is no KMS support and therefore no X. But nevertheless I tried it and as expected X did not start.
Trilby wrote:Could you also post information about your graphics card and what drivers you've installed.
The graphics card is a Radeon HD 2700 and according to the above dmesg log it is recognized as RV 630. The radeon module is loaded via /etc/mkinitcpio.conf and xf86-video-ati (1:7.5.0-1) is installed.
I hope the provided information is what you asked for, thanks for your help.
Best regards
mgs

HP Pavilion DV3 41700-EE Problem-Black Screen after installing graphic card driver

Hi,
Laptop Model : HP Pavilion DV3 41700-EE Entertainment series.
I download the latest official driver for my lap top from this link : http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-93326-1&cc=us&dlc=en&lc=en&...
After the installation i rebooted my device and after the windows loading i got a black screen ! i went to safe mode and unistall the video card and also it's driver from device manager and when i came back the black screen was gone but i have only my onboard Integ graphic which is very slow.
also i went to AMD web site and get AMD Catalyst from their web site but nothing happened after the installation and i think they don't provide an appropriate driver for my lap top.
i also tries to go to device manager and with right click on my display adapter and update driver point to the display driver location on my syste but this time it does not take time the black screen after restart, and in the middle of installation i got a black screen.
Also i upgraded my BIOS Firmware from 16 to 24, but nothing changed.
i just wanna know is it a software problem or hardware problem ? how can i find out that ?
also i don't want this switchy manner and i don't care about the power efficency. i just want to my device work on maximum performance.
What you suggest i do ?

Use the recovery manager to reinstall the original AMD graphics driver and Catalyst Control center.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

[SOLVED] Black screen after GRUB

Hello everyone
I was setting up a machine with E17 and was trying various DM's since none seemed to work. After attempting to use LightDM, I get a black screen after GRUB. I was trying to read the various logs at /var/log/ but I cannot understand them properly. I tried reinstalling entrance and LightDM with no luck. I even tried editing grub's entry appending '1' or 's' and still no dice. Any help would be appreciated.
Last edited by Linoman (2014-01-20 09:22:33)

Hi tnx for both answers.
I missed something important in Xorg.log. As you can see, fbdev and modesetting aren't loading as usual. I didn't check grub stuff, I don't think it's related, since loading in level 3 (text mode) I get a black screen but I can login as root and turn off the computer blindlessly.
[ 2.969] (II) LoadModule: "modesetting"
[ 2.969] (WW) Warning, couldn't open module modesetting
[ 2.969] (II) UnloadModule: "modesetting"
[ 2.969] (II) Unloading modesetting
[ 2.970] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2.970] (II) LoadModule: "fbdev"
[ 2.970] (WW) Warning, couldn't open module fbdev
[ 2.970] (II) UnloadModule: "fbdev"
[ 2.970] (II) Unloading fbdev
[ 2.970] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2.970] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[ 2.970] (II) VESA: driver for VESA chipsets: vesa
[ 2.970] (++) using VT number 7
[ 2.974] (WW) Falling back to old probe method for vesa
javex wrote:Post the content of the following files:
Also does disabling LightDM again help resolve the issue, i.e. can you get it to work without LightDM?
No, I can't get it to work changing DM's. I'm not sure if I pacman -Syu before changing DM's another time. Maybe it wasn't LightDM's fault afterall.
Spider.007 wrote:Additionally; try booting without the 'quiet' entry that is in the kernel line by default; and disable https://wiki.archlinux.org/index.php/Ke … de_Setting too
Thanks for pointing out that. I didn't knew I had it on.
Last edited by Linoman (2014-01-11 21:34:08)

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

Black Screen After Windows 8 64-bit Upgrade (Clean Install) on TouchSmart IQ508A (IQ500 series)

Hi there,
Just installed Windows 8 and am getting a black screen after booting up like many others. I currently have disabled the graphics driver and this has solved the black screen issue but I can no longer use my web cam for Skype (although web cam works for W8 Camera App oddly).
To date I have tried the following:
Loading up the latest Nvidia drivers from the Nvidia website
Attempting to use the drivers for Windows 7 both in compatability mode and normally. I unzipped SP44488 to get this working
I know many others are having this problem so I really would like someone from HP to respond and state whether a Windows 8 display driver for the Nvidia GE Force 9300M GS is being developed.
I ran the compatability wizard prior to the clean install and it came up with no issues so I am very disappointed I am having these problems.
I've found out that HP have a customised version of the above card so that explains why the Nvidia drivers dont work so I believe HP is therefore obligated to provide a driver.
If anyone else is having similar issues please respond as this will hopefully lead to more action.
cheers
Steve

I'm in the same boat. On my IQ804, the Nvidia GE Force 9300M GS card crashes when I use NVidia's latest Windows 8 driver and Microsoft's LIVE UPDATE drivers. I have to resort to the Standard VGA driver in order for the pc not to crash into a black screen.
I read on another forum you can try installing a July 2012 version of the driver from NVidia and that should solve the problem. I tried it once. Using the July 2012 version, the screen would stay on longer, but eventually it crashes into a black screen...but definitely more usable than the latest from NVidia and Microsoft.
I too have heard that HP used a customized version of the graphics card and that's why neither HP nor NVidia's drivers work.
I also tried installing the Nvidia GE Force 9300M GS drivers for Windows 7 that I downloaded from the HP website. It didn't work either. It actually failed to install altogether, saying my system is incompatible.
As is, the pc works fine. But videos and games that require motion is noticably choppy.
Any help from HP??

Black Screen After Upgrading to Windows 8

Hi
I'm experiencing a black screen after upgrading a Dell N5050 B890 to Windows 8.
Tried to refresh the installation but the problem persited. re-installed the Windows 8, the machine logged in successfully but the problem arose again after reboot.
Urgent assistance needed

This problem is solved...
I guess the problem is concerned with the display module controller in the BIOS which is having a slight compatibility issue with windows 8.
This issue is solved by updating the BIOS of your Laptop/PC to the latest version. You can download the latest BIOS from the website of the Laptop company/Motherboard Company.
But for updating the BIOS, you have to start your computer/Laptop for at least one time in Normal Mode. So here are the steps to do so...
1) Boot the Laptop/PC.
2) After the boot screen (The Circle Animation & Windows 8 logo), you will be presented by the lovely & awesome blank screen.
3) Wait for 1 minute so that drivers load into the memory.
4) Press the Power button of your laptop/PC for only a moment (Just Press and release it quickly. Don't hold. We don't want to shut down).
5) This will force the laptop/PC to go into Sleep mode.
6) When the laptop/PC goes in sleep, the laptop fan & other sounds will stop.
7) After 4-5 seconds, press the power button again & release it quickly.
8) Voilllaa!!! The laptop/PC starts & you are presented with the lock screen. Now..... Login! What are you waiting for! :P
This is not the permanent solution. It just lets you start you Laptop/PC.
After updating the BIOS, I strongly suggest that you must download the latest graphics driver for your Computer/Laptop to avoid any further issues.

Black screen after windows auto update

New laptop in use for 3 weeks. After Windows auto update restart I get to splash screen and am able to enter Windows password to log onto desktop. After successfully entering password I am not able to view my desktop; I get the black screen with cursor function; cursor disappears when moved within an inch of left or right of screen (seems to go behind something). I believe I am at the desktop but just not able to view it, because I receive app popups on the black screen (need to update McAfee, etc).
In safe mode I restored to pre auto update date; manually installed all Windows updates; worked fine until NEXT auto update, same problem.
Graphics Card: Stock Intel HD Graphics
Monitor: Generic PnP
Why would it be fine with the manual update and not after auto update?
I do not have an external monitor to attach this laptop for diagnosis. I have run windows partition checks and hard drive partition checks with no issues to resolve.
I did get an error message once when running a diagnosis (can't remember which) : Windows Update Error 0x80070490
No real luck finding anyway for me (the average Joe) to resolve this issue.
If this is a harddrive issue I don't want to keep pussyfooting around while my warranty window shrinks.
I have downloaded driver updates from HP, but cannot get the Synaptics Touchpad driver to download. I don't think this is my issue though.
I am going to manually update all my drivers then manually update Windows. We will see what happens on the next auto update.
Please advise if this is an issue I need to just give up on and return this laptop for replacement. It seems like this is not a completely unheard of issue, but I'm shocked at what we are asked to do to attempt to resolve it. Out of my depth.

Hi @Justanothermom
Welcome to the HP Support Forums!
I understand that you are having troubles with a black screen after an update. I am happy to help you with this.
Firstly, there is nothing wrong with modifiying your update settings. I was going to suggest it myself as I read through your post, and then saw you ask the question. Sometimes updates can have unintended results by the creator. With all the different combinations of hardware, and the fact that updates come from different sources, it is one of those things that is hard to completely control.
Please see the following for how to make adjustments to your update settings.
Turn automatic updating on or off - windows.microsoft.com
Or if you know which update seems to be causing the issue you can take a look at this page:
win 8.1 August 12 updates - black screen after 2nd reboot - answers.microsoft.com
Let me know if this helps at all.
Malygris1
I work on behalf of HP
Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
Click Kudos Thumbs Up on the right to say “Thanks” for helping!

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade.
What happen: My laptop was working fine, no blue screen issue, no funny business at all. I bought a new SSD Intel 120 GB and thought it would be a good idea to replace the HDD. I shutdown and disconnected the power adapter, waited a couple of minutes and removed the battery. I opened up the back case and replaced the HDD. And put all the screws back and put the battery back in.
Problem: The very first time I turned the power on, nothing happens besides a black screen. I pressed the dvd drive it works and opens up and closes. I waited for about 30 mins and still has blac screen. When I mean black screen, no bios menu, no logo, just a black screen with the fan sound on.
I have tried these:
1. Unplugged everything - battery, adapter, and pressed the power on button for about 60 seconds, nothing, the laptop turns on with the LED display on for both on and battery LED's. But nothing but black screen, no sound of windows loading just the fan and black screen.
2. I tried putting back my old 2.5" and nothing but black screen.
Thoughts and suggestions?
Solved!
Go to Solution.

Hi Autoexit173,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not booting in your Lenovo G560 laptop.
As you have mentioned that the system not booting, please try to remove the RAM and turn on the system and check if you can hear any beep sound. Also try to clean the RAM slots and check for the issue.
Click here for the steps to remove the RAM and refer page number 40.
Hope this helps. Do post back if issue persists!
Best regards,
Ashwin.S
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

IOS adhoc displays black screen after launch

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

[SOLVED] GDM: black screen after "Reached target Graphical Interface"

Similar Messages

Maybe you are looking for