Buttons on display no longer work

We have an Apple Cinema HD display (23", I think) that has been in use for a couple of years and now the power and brightness buttons on the side no longer seem to work. They just don't do anything at all most of the time. So sometimes when the computer is being booted the monitor will not turn on. At that point we'll have to unplug/plug the display and try again. We may have to do this several times before the button will finally work and the monitor will come on.
Anyone have experience with this? Is this something that is fixable?

Hmm... I didn't notice this post already. I made a similar post here:
http://discussions.apple.com/thread.jspa?threadID=1897005&tstart=0
I'm having the same problem. My power button works intermittently... Rather my monitor will only turn on when it feels like it. When it's on the power buton works 100% of the time to turn it off. The trouble is that once it's off, it may not come back on.
I'm not sure if the brightness buttons are affected for me as I hardly ever touch them.

Similar Messages

  • The shuffle button in itunes no longer works

    the shuffle button in itunes no longer works. it used to work fine.

    That's weird.
    Here are some random thoughts, sorry if they're not too awesome.
    * Do you get the Manage Widgets window with no list in it? OR not even the window?
    * How long do you wait for your list to pop up? On my (admittedly ancient)
    powerbook, it may take a few seconds the first time I try it.
    * You might consider looking at the Console log messages (set to "All messages") to see if
    there are any error messages being generated when you ask to "Manage Widgets".
    * You might try removing all your widgets manually via the ~/Library/Widgets folder. This
    could be a workaround, I guess, too. But my thought is maybe there is a bad widget in there which is somehow clogging up the Manage Widgets thing.
    charlie

  • Buttons on 20" Display No Longer Work

    For the past two years I've been using my 20" Apple Cinema Display (the one with the white edges, not the newest version) with my 12" PowerBook by connecting it through Apple's ADC to DVI adapter and plugging it into the Mini-DVI slot on my PowerBook. It worked great and I especially liked how the power button on the display would turn the computer on without the need to open the lid of the PowerBook.
    I just bought a Black MacBook Pro last night, used the Migration assistant to transfer over my User folder. All works fine except the buttons on the display no longer does anything. I'll push it and it will glow but it doesn't seem any signal is sent to the MacBook. The display works fine when plugged in but neither the power button or the brightness button works anymore with the new MacBook.
    Very frustrating...any ideas?
    MacBook 2.0 GHz Core Duo   Mac OS X (10.4)  

    While its hugely unlikly to be RAM related and more than likely the problem is due to lack of support via the DVI connector. I would probably look in two places…
    1) The cinema displays forums…
    http://discussions.apple.com/category.jspa?categoryID=111
    It is possible this issue exists with other Macs and the solution posted.
    2) Call AppleCare. You are current covered by the 90 day telephone support so there's no harm is simply asking.

  • IMac 24¨External display no longer working

    I have a Intel iMac 24¨using an additional external display - Fujitsu.
    It has worked perfectly since I bought it and suddenly the external display will no longer work. There is nothing wrong with the Fujitsu because I have tested it on other computers but will no longer work with the iMac.
    I have checked all connections, running current update and I am now at a loss as to what to do next.
    I read that there were problems linking external displays when the iMac 24¨came out but I am assuming that this was resolved long ago. Even so, mine has worked fine until now. Any ideas please?!
    Thank you

    Hi Canaryguy
    1. Shut everything off display, computer and disconnect everything.
    2. Reset the iMac's SMC > http://support.apple.com/kb/HT3964
    +● Shut down the computer.+
    +● Unplug the computer's power cord.+
    +● Press and hold the power button for 5 seconds.+
    +● Release the power button.+
    +● Attach the computers power cable.+
    +● Press the power button to turn on the computer.+
    3. Now first reconnect the DVI or VGA cable to the Display.
    4. Then connect the Mini DVI to ??? to the Cable coming from the Display.
    5. Lastly plug the Mini-DVI adapter into the iMac.
    6. Then turn the Display on and startup the iMac.
    If that does not work try a different Mini-DVI to ??? adapter and cable, or test your adapter, cable and display with another iMac.
    If all of the above fail, then the iMac needs to be serviced.
    Dennis

  • Home button on iPad2 no longer works after iOS 7 upgrade

    I upgraded my iPad2 to iOS 7 today.  The home button no longer works.  I've powered it down and back up as well as restarted it but it's still not working.  Any suggestion greatly appreciated.
    About to fly to China and was looking forward to watching movies and reading on the long flight.
    Thanks!

    Hi SUSOA!
    Try using the steps in the following article to address this issue:
    iOS: An app you installed unexpectedly quits, stops responding, or won’t open
    http://support.apple.com/kb/ts1702
    Thanks for being a part of the Apple Support Communities!
    Cheers,
    Braden

  • External display no longer working

    I recently purchased a Macbook Pro Retina 13" (Late 2013) model and was able to use it with my external display yesterday. Everything was working great out of the box and I was using the hdmi port on my mac to connect it to my monitor (dvi). Today though when I first turned on my mac after shutting it down for the night, my external display no longer receives a signal.
    I've tested the cable and monitor with another laptop and everything is working, but for some reason just not with my mac.
    I've tried resetting PRAM and SMC, and have been googling how to resolve this but have no luck. Any help would be appreciated.

    So I somehow got it to work again, although it was unexpected, random and 100% luck.
    I think what fixed it was that I switched off and unplugged the power strip that my monitor was connected to (I was reorganizing my cables). I didn't plug my rmbp right away though. The external monitor was still hooked up to my windows laptop. On a whim though I decided to plug the hdmi cable into my rmbp and it worked! My monitor set up also went back to how it was the other day.
    I am sure that I didn't do anything on my rmbp that would have fixed it because I was just browsing internet on it. So if anyone is having this problem of where the monitor used to work but then suddenly didn't then I would suggest them to try this out. Let me know if anyone wants me to recall what I was actually doing. Good luck!
    I think in the future to prevent this from happening again, I will probably unplug my rmbp from the monitor before shutting it down for the night.

  • External Display No Longer Working (Air & Thunderbolt)

    My MacBook Air just decided it no longer wants to work with my external Dell U2711 display via Thunderbolt to DisplayPort cable. Frustrating as this has been working for the past 3 years. Currently running OS X 10.10.2. Have tried PRAM and SMC resets to no avail. Not sure what is going wrong, but looking at the error log it is obviously trying to set it to the wrong resolution "1440 x 900". Previously everything was working great with a resolution of 2560 x 1440. Thoughts?
    ****Error Log Below****
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Received display connect changed for display 0x42737c0
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Found 16 modes for display 0x042737c0 [16, 0]
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Received display connect changed for display 0x3f003d
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Found 1 modes for display 0x003f003d [1, 0]
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Received display connect changed for display 0x3f003e
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Found 1 modes for display 0x003f003e [1, 0]
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x042737c0: GL mask 0x1; bounds (0, 0)[1440 x 900], 16 modes available
      Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9cdf, S/N 0, Unit 0, Rotation 0
      UUID 0x2fa49b462ac314062ce76fce977d6525, ColorSpace { 189789772 }
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00003ab3, unit 0, caps QEX|MIPMAP, vram 451 MB
      texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003f: GL mask 0x8; bounds (2464, 0)[1 x 1], 2 modes available
      off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00003ab3, unit 0, caps QEX|MIPMAP, vram 451 MB
      texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003e: GL mask 0x4; bounds (2465, 0)[1 x 1], 1 modes available
      off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003d: GL mask 0x2; bounds (2466, 0)[1 x 1], 1 modes available
      off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x042737c0: Unit 0: Startup Mode 1440 x 900, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80001000, ioModeDepth 0x0, IOReturn 0x0
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: CGXDisplaysDidReconfigure: Display added
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: CGXDisplaysDidReconfigure: Display removed
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x042737c0: GL mask 0x1; bounds (0, 0)[1440 x 900], 16 modes available
      Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9cdf, S/N 0, Unit 0, Rotation 0
      UUID 0x2fa49b462ac314062ce76fce977d6525, ColorSpace { 189789772 }
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00003ab3, unit 0, caps QEX|MIPMAP, vram 451 MB
      texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003f: GL mask 0x8; bounds (2464, 0)[1 x 1], 2 modes available
      off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00003ab3, unit 0, caps QEX|MIPMAP, vram 451 MB
      texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003e: GL mask 0x4; bounds (2465, 0)[1 x 1], 1 modes available
      off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:13 Nick-MacBook-Air-2.local WindowServer[154]: Display 0x003f003d: GL mask 0x2; bounds (2466, 0)[1 x 1], 1 modes available
      off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
      UUID 0xffffffffffffffffffffffffffffffff
    Mar  2 14:39:15 Nick-MacBook-Air-2.local WindowServer[154]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
    Mar  2 14:39:15 --- last message repeated 1 time ---
    Mar  2 14:39:15 Nick-MacBook-Air-2.local WindowServer[154]: CGXSetDisplayColorProfileAndTransfer: Display 0x042737c0: Unit 0; ColorProfile { 189789772 }; TransferTable (256, 12)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD Agent: xpc connection became invalid during event handler
    Mar  2 14:39:15 Nick-MacBook-Air-2.local WindowServer[154]: CGXSetDisplayColorProfileAndTransfer: Display 0x042737c0: Unit 0; ColorProfile { 189789772 }; TransferTable (256, 12)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD Agent: xpc connection became invalid during event handler
    Mar  2 14:39:15 Nick-MacBook-Air-2.local DMProxy[612]: AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AmbientDisplayAgent started
    Mar  2 14:39:15 Nick-MacBook-Air-2.local WindowServer[154]: CGXSetDisplayColorProfileAndTransfer: Display 0x042737c0: Unit 0; ColorProfile { 189789772 }; TransferTable (256, 12)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD initializing devices
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD Agent: xpc connection became invalid during event handler
    Mar  2 14:39:15 Nick-MacBook-Air-2.local DMProxy[613]: AMBD Services: connection interrupted: com.apple.AmbientDisplayAgent (Connection interrupted)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AmbientDisplayAgent started
    Mar  2 14:39:15 Nick-MacBook-Air-2.local WindowServer[154]: CGXSetDisplayColorProfileAndTransfer: Display 0x042737c0: Unit 0; ColorProfile { 189789772 }; TransferTable (256, 12)
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD initializing devices
    Mar  2 14:39:15 Nick-MacBook-Air-2.local com.apple.AmbientDisplayAgent[304]: AMBD Agent: xpc connection became invalid during event handler

    Howdy Haknat,
    Thanks for using the Apple Support Communities.
    If you're still seeing no image on the external display after resetting the SMC and PRAM, then the next step I'd like you to do is to start the device in Safe Mode.
    Reset the resolution
    Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
    Start up in Safe Mode.
    From the Apple () menu, choose System Preferences.
    Choose Displays from the View menu to open the preferences pane.
    Select any resolution and refresh rate that your display supports.
    Restart your computer.
    If you tried all of these steps for your display and the video issues persist, contact Apple technical support or take your Apple computer to the nearest Apple Store or Apple Authorized Service Provider (AASP) for diagnosis. If you plan to visit an Apple Retail Store, make a reservation at the Genius Bar using http://www.apple.com/retail/geniusbar/ (available in some countries only).
    Note: Diagnostic fees may apply for issues not covered under warranty or the AppleCare Protection Plan (APP).
    Apple computers: Troubleshooting issues with video on internal or external displays - Apple Support
    Take care,
    Alex H.

  • Detect Displays no longer works after upgrade

    Mac Mini 2009 - two weeks old, came with Leopard. Took some doing, but have it hooked up to Sony Bravia 40" LCD via Mini-Display port to VGA adaptor. Detect Display worked fine, connected at High Def resolution. Upgraded to Snow Leopard 10.6.1 today, and Detect Displays finds nothing, I can't get any more than 1280 x 768 out of the display, no high-def. Tried many of the tricks I found in forum - zapped PRAM, booted into safe mode, deleted windowsserver preference plist files. No avail. Is this a general problem with Snow Leopard?

    I do have the same problem with the macbook alum. After the upgrade, i have no more resolution of 1080i, becouse it fails. Only res like 1280*1024 is the max i can get. I figured out that the profile of my LCD bravia is no longer detected by the display manager, back in 10.5 it was "Sony Lcd" (or something) now is "Vga display". EXTREMELY WEIRD is that after a lot of test's (reset ram, delete profiles, etc, etc) i try to change my vga cables, first try... no luck, back to the classical cable and "MAGIC" 1080i res came out of nowhere, and the profile was Sony LCD... but it was just one time (i reboot and it was gonne!!!) i haven't been able to recreate the same thing. So i still stuck with this subject and low res for the mini VGA display adapter!!!

  • Javascript buttons and links no longer work in Firefox after latest update

    Whenever I try to use a javascript button or link, nothing happens, I just get a message in the bottom bar such as: "javascript:window.close();" telling me what the command is, but when I click on it, nothing happens. I cannot close windows in social security or in any other program using javascript. This has happened since the last upgrade to Firefox 11. I even tried completely uninstalling and reinstalling (using the Mozilla instructions to '''completely''' remove Firefox) a fresh Firefox eleven, to no avail. I made sure javascript was completely enabled in tools/options/content

    I have a similar problem like this. I dont know what the deal is but since some type of either add on upgrade or firefox upgrade i get notifications to install flash when i try to launch anything from google music. I did everything you can think of including uninstalling, reinstalling both the add on "No Script" Firefox itself, ran several diagnostic programs to ensure it wasnt any type of malware, reinstalled Adobe Flash 11, Verified Java version. I even tried to play music from google music in IE8 and that worked so its clearly Mozilla and its add ons. I disabled No Script and Google Music miraculously started working fine. This is pretty irritating considering I do everything in my power to ensure I dont get hit with any type of malware, virus, spyware, etc and No Script is definitely an Add on i like to use for that very reason since Firefox no longer supports the Norton Web Tracker add on. Any fix for this foolishness would be great, thanks!!

  • Apple 23" HD Cinema Display no longer working with new Macbook Pro

    I bought a 23" used HD Cinema display the other day along with the ADC-DVI and DVI-Mini Display adapters. I had it hooked up and it was working perfectly for 3 days. Today my wife tried to connect her Macbook accidentally via the USB that is part of the ADC-DVI adapter which didn't work (why is that USB there anyway?). Then when she went to connect the external display back to my Macbook Pro it did not wake up after being connected. I have tried resetting the PRAM on the MBP and have disconnected and re-connected all connections but nothing will get the display working with the MBP anymore. When I connect and disconnect the mini-display plug into the MBP the MBP flashes the blue screen as it appears to be reacting, but that's it. I can't detect any display when I go into the display system preferences. Does anyone know how I can get the Apple Cinema display working again? Thanks for any help.

    Ryan Nagy wrote:
    Upon reflection, I think my issue is different. Probably should not have posted it here. As it turns out sometimes my display works, sometimes it does not. I think the power adapter has gone bad. A common occurrence here in Mexico where the power can fluctuate quite a bit. - Ryan
    There are couple of long threads in the display section about problems with the power supplies on the 23" HD DVI. See this one for instance: https://discussions.apple.com/message/17981683#17981683
    Mine one day just wouldn't turn on -- connected to an old G4 MDD and the Mini -- a bit of fiddling it would occasionally start up, sometimes not. Similar to what you described, the Macs would see it in System Profiler, but it just wouldn't turn on.
    Based on that thread, I figured the problem was mostly likely the power supply. A local authorized repair place didn't have a spare for me to try, but the tech sniffed it and mentioned it the burnt electronics smell. LOL, I sniffed it and sniffed the power supply for my 20" DVI Cinema display -- indeed a weird smell.
    Based on that thread, I decided to bite the bullet and buy a beefier 150" power supply for the 30" Cinema display, which Apple says in compatible with the 23". See: http://support.apple.com/kb/HT2803
    I hooked it up, crossed my fingers, and it fired up right away. It's been working fine for about 3 months now. Cheaper than buying a new monitor.

  • External display no longer works after Mavericks install

    I have a minidisplay port to DVI adapter that connects my Macbook Pro to my television through HDMI port (cable is HDMI to DVI).
    This has worked fine for over 2 years, but as soon as I upgraded my Leopard OS to Mavericks, it stopped working.
    A side topic is that my Android TV media centre also stopped working as it can no longer connect to my Macbook Pro (it used to work for the past few years).
    What am I doing wrong? How can I solve my problems? I have tried everything on the forums, but nothing works at all.
    Help, please, pretty please with sugar on top and a cherry!
    Carlos

    I'm not sure how installing an application would cause that to happen. Have you shut down (powered off) the iMac completely, and then restarted, since this problem occurred?
    Some display settings are stored in PRAM, so if you have not already, try resetting PRAM
    http://support.apple.com/kb/HT1379
    If that does not help, you can try disconnecting the iMac from power and reconnecting it, using the reset SMC (power management) procedure.
    http://support.apple.com/kb/HT1543
    When you reconnect it, initially connect the iMac to a wall outlet, by itself. Leave all peripherals disconnected, except for your USB keyboard/mouse. Make sure it is working properly, then connect only the external display.
    If it still does not work, as a test, start up with your Mac OS X installation disc. You are not installing anything, but note if the second display is displaying the background image or not when you are booted from a different system.

  • External display no longer working - stuck at blue screen

    Hi everyone. I just don't know what in the bloody **** happened here.
    Everything was working fine, I even had my macbook 13 upgraded to 10.5.6 and it always worked fine with my external DELL 2007WFP screen thru DVI cable and miniDVI adapter.
    Suddenly when I got home today and plugged the miniDVI adapter, I saw the screen blinking forever at the blue screen that usually fades out to both screens with extended desktop turned on.
    If I unplug the miniDVI adapter, everything gets back to normal on the macbook screen. I plug it again, I get the blinking blue screen.
    Tried rebooting, unplugging everything else from the external screen, no luck.
    If I boot the macbook with the external screen on and the macbook closed, then it is recognized fine and I can use it, but when I want to use both screens, it will blink again.
    I need to use both screens as that's how I arranged my workspace.
    Again, everything was working fine yesterday.
    Thanks

    Did you ever figure out what was doing this, and more importantly, did you get it fixed? I have the same thing happening to my macbook 13. It has worked fine in the past with external displays, both mini-DVI to DVI and mini-DVI to VGA, and many types of monitors/projectors. All of a sudden last week, i try to connect to my external monitor and I get the flashing blue - dark blue - light blue - repeat...
    I tried the command-f1 trick to switch displays, and it sits there for a second, my desktop will flash onto the external monitor for a second, and then it'll give up and go back to the repeating blues.
    I ran the hardware test, both the short and the long, to no avail.
    I tried with the lid closed and an external mouse and keyboard. I tried this both from the startup and from when the laptop was already on.
    Any ideas? Time to go to the genius bar?

  • Caller Display no longer working

    I have had Caller Display since our exchange was updated to System X - must be 20 years (it used to be called CLI when I worked for BT) and it has always worked perfectly.
    A few weeks ago, it stopped working and seems to be beyond BT's capability to fix it. I have scanned the forum and have tried everything suggested but nothing seems to make any difference.
    I have a separate 50 number caller display, which I had from the beginning and a modern BT Hudson cordless phone. The caller display doesn't register and the phones just say 'external call'. Dialling *#234# gives announcement 'callers identity will be displayed'.
    I have tried connecting the display and a different phone, directly to the NTE, under the faceplate, and using different makes of filter.
    BT have made several attempts to reset the facility and have taken it out of service and reinstated it. Nothing has made any difference, although on one occasion a couple of numbers did briefly display and then it stopped working again.
    Finally, I got cross and insisted that they sent engineer to sort it. When he arrived, he had no idea what to do about it and said that he wouid hand it back to the exchange. Later that day I received a text to say it was fixed but it wasn't.
    After all this I began to wonder whether both my devices had coincidentially gone faulty together, so yesterday I took the display to a friends house where it worked perfectly!
    I have reported the fault again but have no confidence that it will be rectified. If anyone has anything else I could try I would be most grateful. CLI is a really useful facility and I miss it greatly!
    Maybe the only solution is to go to Virgin which, as a loyal BT person, I would hate to do?

    Martin Hi
    It does sound that you have done all the relevent tests to prove where the fault is.
    I assume you have tried it without a Home Hub / Router connected? I have known these to mask the CLI.
    (If I have helped you in any way to say "Thank You" please click on the star next to the message. Thank You)
    If I have solved your Issue please click the "Mark as accepted solution" button.

  • Display no longer working

    Hi All
    I have a brand new iMac 27.5". The following problem arose:
    - working on Safari
    - Safari disappeared suddenly
    - Safari application no longer on dock
    - display turned a darker shade
    - dialog box indicated to press down on power to shut off computer and press once again to restart
    - now computer no longer starting!
    Any idea what the problem is? Thanks a bunch.
    - PK

    Thanks.
    Were there any other apps running in the background?
    Just Pages.
    Were the fans running high? Was it hot? Were you indoors with AC?
    Not really re fans. Yes, a bit hot. Yes, indoors with AC.
    Was it bumped?
    No.
    When you say "won't start", you mean, no power, or power+grey screen or...?
    Display is blank. Cannot tell if there is any power being drawn.
    If it's not starting at all, it could be one of the fail-safes kicked in (motion or heat). Let it rest for an hour and restart it.
    Yes, not starting at all. Have left for several hours, but no luck.

  • Guide and Info buttons on remote not longer working?

    The Guide and Info buttons on my remote do not seem to be working any longer, like they've been remapped. Could anything have changed with my FIOS box via download?

    Sounds like you may have an error in your code causing something to fail?
    Without more info, it's pretty much impossible to help, other than giving generalities.
    Run your page through the validator at http://validator.w3.org to clean up any html errors. If the problem persists, post a link to your page in the forum so we can take a look at what's going on, as Ben suggests.
    Another thing to look for is multiple calls to jQuery libraries, especially different versions of jQuery libraries. That will cause your scripts to fail more often than not. Usually, you can keep the newest version's link and delete the older one and everything will come back, but sometimes scripts will conflict due to issues like using the same variables or function names and there's no good way to fix it, short of rewriting one of them.

Maybe you are looking for