Ups - Black screened Gnome Session after playing with Gnome Wayland

I was curious about gnome wayland, and just tried it by selection in gdm, with xorg-server-xwayland installed. It felt warm, spicy, and showed minor glitches and some bleeding edges. To my surprise, when I logged out, and went back to Gnome (without wayland), the gnome session starts up just to see the mouse pinter vanishing in front of a pure, black monitor while the hard drive led shows heavy activity. I went away to have a cup of coffee. Coming back, the hard drive was sleeping, and the monitor was still black. Ctrl - Alt - F2 gave me a console, but no idea what to do, so I decided to go for a reboot, and noticed I still could run Gnome Wayland, but no more Gnome.
Finally, I gave up on finding out what really happened. I guess something in the gnome configurations was messed up with wayland and non-wayland. Adding a new user and starting a new Gnome session showed me the problem was related to my user account. So I purged my .config-gnome-related files and folders, and things are behaving well again.
Therefore, I take this as a proof: running Gnome Wayland will change parts of your configuration, and be warned, Gnome might not be able to turn them back again.
Last edited by Moo-Crumpus (2014-10-27 14:00:28)

Similar Messages

Ipod touch wont turn on i tried restoring it but every time i do it just says its waiting for the ipod to respond. meanwhile my ipod is no longer a black screen but the apple logo with a loading bar underneath that after leaving for 8 hours hasnt moved.

my ipod touch wont turn on ive tried restoring it but every time i do it just says its waiting for the ipod to respond. meanwhile my ipod is no longer a black screen but the apple logo with a loading bar underneath that after leaving for 8 hours hasnt moved.

Try:
- Another cable
- Another USB port
- Reboot the computer
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

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

My iPhone 4S LCD screen is too bright,playing with brightness feature doesn't help.The colors have lost their vividness

My iPhone 4S LCD screen is too bright,playing with brightness feature doesn't help.The colors have lost their vividness

Definitly sounds like a physical issue with the phone. I suggest you go to your local Apple Store or Apple Authorized Service Provider for help.

What can i do to get my phone working. It went to a black screen when I was playing a game. I pressed the power and home button then it showed the apple logo and went back to a black screen. Doesn't came on, show a charging sign, read on iTunes.

What can i do to get my phone working. It went to a black screen when I was playing a game. I pressed the power and home button then it showed the apple logo and went back to a black screen. Doesn't came on, show a charging sign, read on iTunes.

Press and hold the home and power buttons for 15-20 seconds until the white Apple logo appears.

HT1688 My iphone is neither shown in itunes nor in redsnow .. what is the problem ? It has the black screen and the sound plays when it is plugged into the computer .. I tried to hard reset but only the sound plays nothing is shown is there any solution t

My iphone is neither shown in itunes nor in redsnow .. what is the problem ? It has the black screen and the sound plays when it is plugged into the computer .. I tried to hard reset but only the sound plays nothing is shown is there any solution to this ?? It says that my iphone is in soft dfu mode and in the my computer > manage>device manager > it shows the apple (dfu mode) having some error sign indicating no software installed i am running windows 8 ..

Jailbreaking iOS can't be discussed in this forum.

Why mu brand new macbook air always black screen while i use it with battery?

why mu brand new macbook air always black screen while i use it with battery?

Press F2 key couple of times.
Reset PRAM. http://support.apple.com/kb/PH4405
Reset SMC. http://support.apple.com/kb/HT3964
Choose the method for:
"Resetting SMC on portables with a battery you should not remove on your own".
Is the battery charged?
You can return a new Mac within 14 days of purchase.
A new Mac is in warranty for 1 year from the date of purchase.
A new Mac comes with 90 days of free tech support from AppleCare.
AppleCare: 1-800-275-2273
Call AppleCare.
Best.
Best.

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 When Trying To Play Videos

Hi,
Until recently I have been able to play movies on my iPod touch but after I restored it, I got a black screen whenever I open the video file. It is the proper format as iTunes accepts it and syncs it to the device. If I touch the play button, it shows the pause button for about a second and stops again. I have restored several times but I still get the same problem. I'm using iOS 4.3.3 and a 4th Gen iPod touch. Here are a couple of screenshots:
If I move the top slider to any time in the movie, it shows that scene as an image on the screen but will never play. Any suggestions?

In an attempt to consolidate numerous threads about video problems with Flash Player 11.2.202.228 I've created a new post where I'd like to have people who are still encountering this issue to either post or link to an existing post with their information.
Video investigation with Flash Player 11.2.202.228
We're asking for 4 pieces of information
1. A brief explanation of the problem
2. Did disabling hardware acceleration fix the issue
3. A sample URL
4. A copy of your dxdiag report
If you've already provided all 4 answers to us, thank you and please take a minute and copy the URL of your post (right click on the highlighted title of your post as shown in the example screenshot below) and paste it as a reply so your input is not lost.
If you haven't provided these answers, we ask that you take a few minutes and create a new post with the required information.

[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 and looping after installing and updating Mountain Lion on Macbook pro 2011 13 "i5 2.4Ghz

After first installing the new Mountain Lion upgrading Lion on my Macbook Pro was a little slow, so I decided to format and install Mountain Lion via a thumb drive. After installation on my Macbook Pro was restarting all the time and showing a black screen with codes on the screen. I decided to reformat and reset the PRAM, and that seems to have worked. Occasionally a black screen appears with the codes and my macbook restarts again. Last night I updated the Mountain Lion and error and looping retornartam. I thought I had lost all my works, do more entered in the login screen. I turned off my macbook, went to sleep and this morning I called and finally worked Do not know what's going on in my friends' macbook not occur this problem. The macbook them is the 2011 13 "i5 2.0Ghz and another 2010 and they both work perfectly with the Mountain Lion.
Below is the error that occurred this morning after login.
Interval Since Last Panic Report: 1690 sec
Panics Since Last Report:          1
Anonymous UUID:                    67D1DCE1-6759-7BF0-6682-40BCBB09D01B
Thu Sep 20 07:24:10 2012
panic(cpu 2 caller 0xffffff80206b7bd5): Kernel trap at 0xffffff8020687d02, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007ccd02000009, CR3: 0x00000000228a6000, CR4: 0x00000000000606e0
RAX: 0x00007ccd02000001, RBX: 0x000000000000003e, RCX: 0xffffff8020cbd000, RDX: 0x000000000000003e
RSP: 0xffffff8110da3720, RBP: 0xffffff8110da3740, RSI: 0xffffff8031ef80c8, RDI: 0xffffff8020cbd000
R8: 0xffffff8031ef7750, R9: 0xffffff8031ef0438, R10: 0xffffff8020cbcc20, R11: 0xffffff814c6e0000
R12: 0xffffff8033b0ec00, R13: 0xffffff8033b0ecb0, R14: 0x00000000000000c1, R15: 0xffffff8031ef0438
RFL: 0x0000000000010296, RIP: 0xffffff8020687d02, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007ccd02000009, Error code: 0x0000000000000002, Fault CPU: 0x2
Backtrace (CPU 2), Frame : Return Address
0xffffff8110da33c0 : 0xffffff802061d626
0xffffff8110da3430 : 0xffffff80206b7bd5
0xffffff8110da3600 : 0xffffff80206ce4ed
0xffffff8110da3620 : 0xffffff8020687d02
0xffffff8110da3740 : 0xffffff802065f445
0xffffff8110da38a0 : 0xffffff8020681b58
0xffffff8110da3bf0 : 0xffffff802065e1b4
0xffffff8110da3c50 : 0xffffff8020a52e4f
0xffffff8110da3d40 : 0xffffff8020a53052
0xffffff8110da3d70 : 0xffffff7fa1e35434
0xffffff8110da3de0 : 0xffffff7fa1e2412f
0xffffff8110da3e10 : 0xffffff7fa1e33afe
0xffffff8110da3e60 : 0xffffff8020a3181b
0xffffff8110da3ea0 : 0xffffff8020a3133e
0xffffff8110da3f30 : 0xffffff8020a2d2d0
0xffffff8110da3f70 : 0xffffff8020a31e99
0xffffff8110da3fb0 : 0xffffff80206b26b7
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelHD3000Graphics(8.0)[EAD976F9-7469-3F17-AB8E-6A039213 8DCB]@0xffffff7fa1e06000->0xffffff7fa1e67fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.1)[9901C237-547C-3B52-99DE-C4870A19E2B5]@0xffff ff7fa0caf000
            dependency: com.apple.iokit.IONDRVSupport(2.3.5)[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7fa11fc000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.5)[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7fa11b9000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C54
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000020400000
Kernel text base: 0xffffff8020600000
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
System uptime in nanoseconds: 22884276012
last loaded kext at 22356664762: com.apple.driver.AppleMikeyHIDDriver          122 (addr 0xffffff7fa1d76000, size 20480)
loaded kexts:
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDAHardwareConfigDriver          2.3.1f2
com.apple.driver.AppleHDA          2.3.1f2
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.2.11
com.apple.driver.AppleIntelHD3000Graphics          8.0.0
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleBacklight          170.2.3
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.iokit.IOBluetoothUSBDFU          4.0.9f33
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f33
com.apple.driver.AppleMikeyDriver          2.3.1f2
com.apple.driver.SMCMotionSensor          3.0.2d6
com.apple.driver.AppleSMCLMU          2.0.2d0
com.apple.driver.AppleIntelSNBGraphicsFB          8.0.0
com.apple.driver.AppleMuxControl          3.2.11
com.apple.driver.AppleUSBTCButtons          235.4
com.apple.driver.AppleUSBTCKeyEventDriver          235.4
com.apple.driver.AppleUSBTCKeyboard          235.4
com.apple.driver.AppleIRController          320.15
com.apple.driver.AppleFileSystemDriver          3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.iokit.SCSITaskUserClient          3.5.1
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.2.2
com.apple.driver.AppleSDXC          1.2.2
com.apple.driver.AppleUSBHub          5.2.5
com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3
com.apple.driver.AppleAHCIPort          2.4.1
com.apple.driver.AirPort.Brcm4331          602.15.22
com.apple.driver.AppleFWOHCI          4.9.6
com.apple.driver.AppleUSBEHCI          5.4.0
com.apple.driver.AppleUSBUHCI          5.2.5
com.apple.driver.AppleEFINVRAM          1.6.1
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleACPIButtons          1.6
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleHPET          1.7
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.6
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.driver.DspFuncLib          2.3.1f2
com.apple.iokit.IOAudioFamily          1.8.9fc10
com.apple.kext.OSvKernDSPLib          1.6
com.apple.iokit.IOSurface          86.0.3
com.apple.iokit.IOBluetoothFamily          4.0.9f33
com.apple.driver.AppleThunderboltEDMSink          1.1.8
com.apple.driver.AppleThunderboltEDMSource          1.1.8
com.apple.driver.AppleThunderboltDPOutAdapter          1.8.5
com.apple.driver.AppleHDAController          2.3.1f2
com.apple.iokit.IOHDAFamily          2.3.1f2
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.IOPlatformPluginFamily          5.2.0d16
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.0.9f33
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.driver.AppleSMC          3.1.4d2
com.apple.driver.AppleGraphicsControl          3.2.11
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.3.5
com.apple.iokit.IOGraphicsFamily          2.3.5
com.apple.driver.AppleThunderboltDPInAdapter          1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.5
com.apple.driver.AppleUSBMultitouch          235.7
com.apple.iokit.IOUSBHIDDriver          5.2.5
com.apple.driver.AppleUSBMergeNub          5.2.5
com.apple.driver.AppleUSBComposite          5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.iokit.IOAHCISerialATAPI          2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1
com.apple.driver.AppleThunderboltNHI          1.6.0
com.apple.iokit.IOThunderboltFamily          2.1.1
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IOUSBUserClient          5.2.5
com.apple.iokit.IOAHCIFamily          2.2.1
com.apple.iokit.IO80211Family          500.15
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOUSBFamily          5.4.0
com.apple.driver.AppleEFIRuntime          1.6.1
com.apple.iokit.IOHIDFamily          1.8.0
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          344
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.6
com.apple.iokit.IOPCIFamily          2.7.1
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 1.68f98
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393955353432382D3034302E413031472020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x0198, 0x393955353432382D3034302E413031472020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Hitachi HTS545050B9A302, 500,11 GB
Serial ATA Device: MATSHITADVD-R   UJ-8A8
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 4
Is there a hardware problem?
thank you

Before you upgrade, make sure all your software supports it based on post July, 25, 2012 reports on
http://roaringapps.com/apps:table
Reports prior to this date are unreliable, as they are likely with beta releases of Mountain Lion to developers. Other pitfalls to realize include:
https://discussions.apple.com/docs/DOC-3761

Only black screen on the external monitor with intel-virtual-output

Hello,
I tried to install bumblebee on my Lenovo W520 with this tutorial:
http://www.unixreich.com/blog/2013/linu … ly-solved/
I can activate my external monitor with "intel-virtual-output" and the monitor is switching on. But I can only see a black screen.
In the settings of gnome I can see my external monitor and configure it - but it shows nothing.
Have you any ideas?
Thanks a lot!

Hi,
Same problem here on my Lenovo W530.
Intel-virtual-output used to work fine but since it got upgraded the virtual output stays black.
I tried downgrading the xf86-video-intel package but there is a dependency conflict.
Available packages:
1) xf86-video-intel-2.99.916-3-x86_64.pkg.tar.xz (local)
2) xf86-video-intel-2.99.916-3-x86_64.pkg.tar.xz (remote)
3) xf86-video-intel-2.99.916-2-x86_64.pkg.tar.xz (local)
4) xf86-video-intel-2.99.916-2-x86_64.pkg.tar.xz (remote)
5) xf86-video-intel-2.99.916-1-x86_64.pkg.tar.xz (remote)
6) xf86-video-intel-2.99.914-4-x86_64.pkg.tar.xz (local)
7) xf86-video-intel-2.99.914-4-x86_64.pkg.tar.xz (remote)
8) xf86-video-intel-2.99.914-3-x86_64.pkg.tar.xz (remote)
9) xf86-video-intel-2.99.914-2-x86_64.pkg.tar.xz (remote)
10) xf86-video-intel-2.99.914-1-x86_64.pkg.tar.xz (remote)
11) xf86-video-intel-2.99.912-2-x86_64.pkg.tar.xz (local)
12) xf86-video-intel-2.99.912-2-x86_64.pkg.tar.xz (remote)
13) xf86-video-intel-2.99.912-1-x86_64.pkg.tar.xz (local)
14) xf86-video-intel-2.99.912-1-x86_64.pkg.tar.xz (remote)
15) xf86-video-intel-2.99.911-2-x86_64.pkg.tar.xz (local)
16) xf86-video-intel-2.99.911-2-x86_64.pkg.tar.xz (remote)
17) xf86-video-intel-2.99.911-1-x86_64.pkg.tar.xz (local)
18) xf86-video-intel-2.99.911-1-x86_64.pkg.tar.xz (remote)
19) xf86-video-intel-2.99.910-1-x86_64.pkg.tar.xz (local)
20) xf86-video-intel-2.99.910-1-x86_64.pkg.tar.xz (remote)
21) xf86-video-intel-2.99.909-2-x86_64.pkg.tar.xz (local)
22) xf86-video-intel-2.99.909-2-x86_64.pkg.tar.xz (remote)
23) xf86-video-intel-2.99.909-1-x86_64.pkg.tar.xz (remote)
24) xf86-video-intel-2.99.908-1-x86_64.pkg.tar.xz (remote)
25) xf86-video-intel-2.99.907-2-x86_64.pkg.tar.xz (local)
26) xf86-video-intel-2.99.907-2-x86_64.pkg.tar.xz (remote)
27) xf86-video-intel-2.99.907-1-x86_64.pkg.tar.xz (local)
28) xf86-video-intel-2.99.907-1-x86_64.pkg.tar.xz (remote)
29) xf86-video-intel-2.21.15-1-x86_64.pkg.tar.xz (local)
30) xf86-video-intel-2.21.15-1-x86_64.pkg.tar.xz (remote)
31) xf86-video-intel-2.21.14-2-x86_64.pkg.tar.xz (remote)
select a package by number: 16
loading packages...
warning: downgrading package xf86-video-intel (2.99.916-3 => 2.99.911-2)
resolving dependencies...
warning: cannot resolve "glamor-egl", a dependency of "xf86-video-intel"
:: The following package cannot be upgraded due to unresolvable dependencies:
xf86-video-intel
:: Do you want to skip the above package for this upgrade? [y/N]
error: failed to prepare transaction (could not satisfy dependencies)
:: xf86-video-intel: requires glamor-egl
Any Ideas what glamor-egl is?
Thanks!

Black screen upon wakeup after longer sleep...

In the last 2 months or so, I have seen my MacMini 2011 OSX 10.7.3 crashing withing a minute of wakeup, after sleeps of more than 2-3 hours.
Sometimes the Black screen occurs almost immediately, sometimes it takes up to a minute after the desktop appears (after logging in).
This did not occur until I got 10.7.3 and only within the last 2 months.

Anyone?
I am up to 100 crashes upon wakeup now. Various versions of Lion 10.7.x. I have done clean installs as well.
Does anyone else get the black screen of death shortly after wakeup from sleep?
This never happened on 10.7.0, 10.7.1 or 10.7.2
Crashes happen in both 10.7.3 and now 10.7.4, and for sleeps as short as 90 minutes.

Macbook Air 2014 Black Screen w cursor after waking from sleep.

I just purchased a brand new macbook air this past week. I noticed within the first day of using that if my machine went into sleep mode, and I hit a key to take it out of sleep mode, it would go to a black screen with my cursor for about 30 seconds.
It does not do it every time but enough that it is annoying. I am coming from a mid 2011 mac air that did not have any issues. (only replaced for all day battery)
Do you think this a hardware or software issue? If i swap this mac out do you think I will just encounter the same thing?
I have read numerous posts regarding waking from sleep issues but they all seem to be affecting MacBooks purchased between 2012 and 2013.
Any help would be much appreciated.
Nick

UPDATE:
I called apple tech support and after talking a bit decided best course of action was to replace the macbook air as I was inside my 14 day buyers remorse.
I came home and hoped all was well when this one began doing the same thing. I made an appt with the genius bar to dive further in to this and we did a complete wipe on the computer and reinstalled the OS. The "genius" said I'm probably bringing something over from my previous mac air. (even though it never had this issue).
So after completely reinstalling the OS and setting up my macbook as new I pretty much lost all my settings and what not accumulated after 3 years with my previous mac. They did use Time Machine to at least bring my iPhoto library over and iTunes music.
It has been exactly one day since this was completed and the computer is doing the exact same thing. ***!!!

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)

Ups - Black screened Gnome Session after playing with Gnome Wayland

Similar Messages

Maybe you are looking for