MPB + 24" LED, weird behaviour after disconnect

When using my MPB in combination with my 24"LED (single screen setup), everything works perfectly. When I disconnect, the resolution drops to the maximum resolution of my MPB. This drop in resolution results in weird behaviour of application windows, expose (corner activation) and spaces.
Expose does not work anymore, seems like it still thinks there is a larger resolution, so putting my mouse pointer in the corner will not activate expose or any other corner function.
Spaces does not slide anymore, again it seems like it expects a larger desktop to slide which is not there anymore. The display flashes and skips to the next desktop.
Windows can not be resized because the sizing corner (lower right) is outside of the current screen area. So to be able to resize my applications, I have to resize them to small before I disconnect the 24"LED screen.
Solutions tried:
1) System preferences > Displays > Detect displays... Does not work
2) System preferences > Displays > Lower resolution > Normal (max) resolution : Works like a charm
3) Logout > Login : Also works
Does anyone else know how to make this work the way it should? So far it seems the programming (Leopard) is faulty.

AVrublevskiy
I agree that, at times, the SGE switches can be somewhat difficult when getting them in and out of stack mode. I would recommend getting them back to the config that they had before you tried to remove them from a stack, then configure them via the serial cable back to factory defaults. The pinout for the cable can be found here.
There is also a little, round, red hole at the bottom left of the switches face plate that allows you to factory reset the device. You should use a paper clip and hold it for a full 30 seconds.
These switches are designed to either be stacked or not, meaning they are not supposed to be put in and taken out of stacked mode at random. By default, the switches try to stack together, and do not work well when the stack gets broken up or changed. I sincerely suggest you pick either stacked or standalone and leave them as such.
As a side note, there is a newer firmware available for this switch. It is version 3.0.0.18. It can be found here.
Please report any new problems.
Bill

Similar Messages

[SOLVED] Weird behaviour after formatting USB installation media

Hi, I have noticed this weird behaviour with USB drives I used to install Arch linux with. I format them using fdisk and mkntfs but after replugging them in, the udevil daemon mounts them again as ARCH_2013...[something] and even the directory tree exists! This happens also when I use mkntfs without the -f flag (initializing with zeros). I also checked the other files in /dev/sd* in order to make sure that my drive does not appear twice, but there is only sda (my HD) and sdd (or sometimes sdb, sdc,...) which must be the USB drive, also according to dmesg.
Any ideas?
EDIT: I wrote something about not seeing any files when manually mounting but that was my bad, I only tried mounting /dev/sdb1 but mounting /dev/sdb brought me the same files as devmon showed.
Last edited by ysetdng (2014-07-12 22:36:46)

I am assuming you used dd to write the image to the disk. You can use it to remove the contents of the disk as well.
You should make use of the arch wiki, it is quite helpful.
https://wiki.archlinux.org/index.php/US … tion_Media
You can use this to zero out the entire device:
# dd if=/dev/zero of=/dev/sdx bs=8M // x is the letter assigned to the usb drive. Be careful, The dd command is destructive.
It may take a while to zero out the entire disk, depending on the size. After that use fdisk/cfdisk or gdisk/cgdisk to create the partition table and partition.
To create the filesystem type, this one, ext4:
# mkfs.ext4 /dev/sdx // or create a vfat
then create the label:
# e2label /dev/sdx1 USB_STICK_LABEL
Use my suggestion as a last resort. Read the wiki, most of what I have said is in there anyway.
Last edited by rgb-one (2014-07-12 18:21:18)

TTY colors problem (only 8 @ vim + weird behaviour after x started)

Hi,
I've got a problem with my tty colors. Everything seems to work pretty ok, but I have two weird problems - one is that vim doesn't display colors properly. It seems like it supports only colors 0-7, no more. My vim scheme & zshrc (dunno if helpful) attached below:
scheme: mustangzill4.vim
zshrc: .zshrc
What's more, when I start X, tty colors seem to become totally messed up. I don't know where are those new color settings taken from, but they're changed somehow and stay like that till next reboot.
Any help/tip appreciated. Thanks in advance.
edit: I know that "2xx" colors won't work in linux terminal since it supports only 16colors, but even 16 colors don't work for me under vim.
Last edited by muchzill4 (2010-01-24 21:00:25)

I just set up vim and my terminal (urxvt-256 via .Xdefaults) and I'm experiencing this. When I start X, TTY2 picks up a grey background. Just curious about how this configuration should affect a console...
EDIT:
Apparently this is less reproducible for me than I thought. After a system upgrade and subsequent reboot, this didn't happen again. Maybe the console liked vim's colors and decided to hold on for a while.
Last edited by nsoodak (2010-02-03 04:52:53)

Mac weird behaviour after wrong switch off.

A few days ago I inadvertently switched off my Mac OS 10.6.8 by using the back on/off button instead of file/ shut down. Since then, random changes keeps happening: as soon as I switched it back on the desktop image had reverted to the original, then a few application seems to have disappeared, and today PhotoBooth no longer has the Video function but only Camera.
As anyone any idea what is going on?
Cristina

FWIW, you cannot repair the disk you are booted from, so in order to run the repair disk function you will need to be booted from another source (either an external bootable clone or the recovery partition).
Afterthought: if you are on 10.6.8, there is no recovery partition, so you'd need to boot from an external source.
You can easily repair permissions while booted from the startup disk/hard drive.

Horizontal shifting bars on MBP 15 after disconnecting 24" LED cinema display and waking up from clamshell mode.

I use my MBP 15 (late 2011) with 24" Apple LED Cinema display in a clamshell mode. After disconnecting external display, and opening display, it shows horizontal shifted bars, so it becomes completely unusable. Have to hard reset laptop. Any hints on how to resolve this? Thanks.

Ok, more information for anyone that might care. The wake-up seems to be the familiar dark wake in order to go into hibernate mode. Except now, it's a death wake. Looking at the logs, I see that it happens exactly 70 minutes after sleeping, even though hibernatemode = 0 (which shouldn't hibernate at all!)
So my power settings look like this:
Currently in use:
standbydelay         4200
standby              1
halfdim              1
hibernatefile        /var/vm/sleepimage
darkwakes            0
gpuswitch            2
disksleep            10
sleep                10
autopoweroffdelay    14400
hibernatemode        0
autopoweroff         1
ttyskeepawake        1
displaysleep         2
acwake               0
lidwake              1
standbymode is 70 minutes, what a coincidence. I'm going to try setting it to 0 and see what that does.

Macbook Pro dark screen after disconnecting from Cinema Display

Dear all,
the issue I am having:
- after disconnecting from Cinema display (having first put my Macbook Pro in "sleep" mode) I just ca't make the Macbook pro scren show anything....black display
- but is it really asleep? NO!!! It just STILL believes it's connected to the Cinema Display
That's what I though was happening, so I thought: "if I now plug in the thunderbolt-to-VGA dongle that I use for the videoprojector then the screen might come back... and.... Voilá! It comes back, BUT starts flickering until in the end it just dissappears....
I can reproduce the error all the time. Worse than that: a reboot does not help at all.
Looks like there is an internal hardware switch that must be left "engaged" and then the Mac just believes it is connected to an External screen and sends the signal though the thuderbolt port instead of through the screen!!!
WEIRD error/bug or whatever!!
I have no idea how to make this reach the Apple guys.... I tried to report a Bug but they asked me to join in as Apple developer which I just can't do (for working issues).
Can anyone tell me if they have had this problem, and whether Apple is taking care of it?
(this reminds me of an issue with an internal switch with the headphones in my old MacBook Pro.... after disconnecting the headphones, the internal switch was not being disengaged, so sound would NEVER come out as it was being sent to the headphones instead of to the speakers... Same problem here but with the Image??? :-((( )
Thanks a lot.
BTW: here go my Mac characteristics:
Mac OSX 10.8.2
Model Name:          MacBook Pro
Model Identifier:          MacBookPro10,1
Processor Name:          Intel Core i7
Processor Speed:          2.6 GHz
Number of Processors:          1
Total Number of Cores:          4
L2 Cache (per Core):          256 KB
L3 Cache:          6 MB
Memory:          8 GB
Boot ROM Version:          MBP101.00EE.B02
SMC Version (system):          2.3f32
Intel HD Graphics 4000:
Chipset Model:          Intel HD Graphics 4000
Type:          GPU
Bus:          Built-In
VRAM (Total):          512 MB
Vendor:          Intel (0x8086)
Device ID:          0x0166
Revision ID:          0x0009
gMux Version:          3.2.19 [3.2.8]
MacBook Pro:
Vendor Name:          Apple, Inc.
Device Name:          Macintosh
UID:          0x0001000D11C0EF80
Firmware Version:          11.1
Port:
Status:          Connected
Link Status:          2
Link Controller Firmware Version:          0.11.4
Port:
Status:          No devices connected
Link Status:          7
Link Controller Firmware Version:          0.11.4

Sometimes I experience the same after disconnecting my 24" display (in seldom cases, the mouse cursor is not painted correctly, as well).
Can you check - when it happens - if in System Profiler > Hardware > Graphic > Quartz Extreme is listed as 'supported'. I found it to be 'not supported' when the scrolling and display behaves strangly. Also the Menu Bar is not transparent any more.
Next to rebooting, logout and login again fixed the issue for me. But I am also looking for a better fix/explanation.
marcus

Error and weird behaviour in executable launch

Hello folks,
This post is regarding a weird behaviour i am experiencing with an executable i built.
LABVIEW version(Includes Runtime engine) LV2012 SP1 f3
DAQmx: 9.6.1
The behaviour is listed below in detail.
In a nutshell, the exectuable runs on the development computer but does not run on the Target computer. Also, Irresepctive of which PC i run the executable on, i cannot access the block diagram even after enabling debugging everywhere.
On the target PC, the app fires up but does not run further, no error codes appear on the screen, it's like the app freezes after firing up. And to add to the misery, i cannot access the block diagram to debug and know what's going on.
Also, I have tried including the dynamic vis to my build script. No bueno.
What I see on running the app is addressed below:
TARGET COMPUTER:
DAQmx 9.7 and LV2012 SP1 f4 RTE have been installed manually.
App does not run: No broken run button, the app launches but does nothing when the vi is run. No error messages.
The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
DEVELOPMENT COMPUTER:
The app launches and runs perfectly.
The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
DAQmx 9.7 and LV2012 SP1 f4 RTE were not installed as the app recognized the already installed Labview environment.
Additional steps that I have tried,
Created and ran only an executable on the target PC, the attempt was unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section.
Created and ran an installer with additional install options(LV2012 f4 RTE and DAQmx 9.7)on the target PC, the attempt was again unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section. No error messages.
Tried both the steps mentioned above on the development computer and the attempts were successful. .
To the best of my knowledge, I believe, the issue here is with the environment I am creating for the executable and the installer to run with/off of. After having carefully followed the installation procedure for the Run-Time Engine and the DAQmx drivers, I still do not know what I am missing.
Please advise.
Thanks guys,
RP.

Hey guys,
So, got the application to work. Almost.
The problem was that the executable was missing the hardware config from the Device.
Now, the new issue is as following:
The goal of the vi is to generate a report of the test conducted. So, the way the vi works is that, the second the vi is run, an empty word file is created with only the company logo,
Field headings, which are populated after the test is conducted.
The logo is a .jpg file, which has a relative path into the executable.
The field heading are String constants wired into a 'concatenate strings.vi' which are in turn wired to into the report generation vis.
What's happening is that when i run the app on the target pc, Only the logo appears on the word template. Even when i conduct the whole test and stop the vi, the results aren't populated in the word file. Which is a little weird.
Does any one know whats doing that?
Please refer to the attached word files.
Right - It is the file format desired.
Wrong - It is the file format achieved.
Please advise.
Thanks,
RP.
Attachments:
Right.docx ‏17 KB
Wrong.docx ‏16 KB

Mail / Exchange 2013 weird behaviour?

I’m hoping someone here can help with weird behaviour from Mail which is driving me nuts. It doesn’t appear to be the same problem as the odd Exchange behaviour described in other threads. It appeared about a month back, and I had made no changes to my software or hardware at that time.
I have the latest version of OSX Mail in Mavericks, set up with an Exchange 2013 and iCloud mail accounts. There are no extensions or add-ons running. I have two Macs and two iOS devices on these accounts, all fully updated. The problems exist regardless of which devices are powered up at any one time. Mail is set to download messages automatically.
On both of the Macs I get the same following problems:
- When new messages arrive, the mailbox notifier indicates the new messages, but they are not shown in the message list. If I select the ‘Exchange’ inbox they are visible, and remain so when I switch back to the combined ‘Inbox’.
- When I select the ‘Exchange’ inbox, rather than the combined ‘Inbox,’ then after 30 seconds or so the ‘From’ field in the message list changes to ‘To’, so all the senders are shown as my email address.
- The entire send/receive function seizes up half a dozen times a day, necessitating a Force Quit to restart the app.
iOS devices work just fine.
Is this in fact the same as the reported Exchange problems, or have I got something else going wrong here? I’ve tried deleting and recreating the account, and also had my hosted Exchange provider take a look, to no avail.
Many thanks,
Tobes

Hi Ivan,
It is really an odd issue. Working for a while, then crash.
According to your description, I found that we suspect it is a certificate issue.
If this issue really related to the certifcate mismatch or something additional, it shouldn't connect to Exchange server, even just for a while (As we
encountered).
I suggest double check our ECP VD configuration and Authentication method. Steps as below:
1. Please try to re-build ECP Virtual Directory, commands as below:
a. To remove current ECP VD:
Remove-EcpVirtualDirectory -Identity "Server01\ecp (default Web site)"
b. To check whether the Remove operation completed successfully:
Get-EcpVirtualDirectory -Server Server01
c. To create a new ECP VD:
New-EcpVirtualDirectory -Server SERVER01 -ExternalURL https://mail.contoso.com/ecp -InternalURL
https://mail.contoso.com/ecp
2. Please verify that the Microsoft Forms Based Authentication service is running on all Exchange servers.
a. To check:
Get-EcpVirtualDirectory -Server <server name> | fl *auth*
b. To enable:
Set-EcpVirtualDirectory -Identity "Server01\ecp (default Web site)" -FormsAuthentication
$true
3. Please also make sure the remote apps are all installing the trusted certificate.
4. Please also collect detailed App logs or error message in event viewer for the further troubleshooting.
Maybe I have not enough experiences, I am not sure whether the logs above that we provided is useful. Maybe others have different opinions.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Weird behaviour with inlined SubVI's

Every now and then I've ran into some serious weird behaviour where I've eventually traced it down to some inlined subVI. It has seemed as if the values used inside the inlined subVI don't match what the calling VI is feeding into its inputs. I haven't been able to consistently reproduce this issue so I apologize for the vague description, but since I felt I should finally address this and I couldn't really find anything similar by searching, I'll do my best to describe it and we'll see what turns up.
As I mentioned, the issue certainly doesn't occur consistently. I use inlined subVI here and there and most of the time there are no problems whatsoever. I ran into the issues randomly I think four times now, first three of them were on LV2013 and this last time on LV2014. In all cases I have been using AF and I think the first times were actually with an actor class. At the time I thought it might have been related to the AF, and it still might, but now the last time it wasn't the actor class itself but a data member of one. So far all of the problems have occured with class methods, and I think the "corrupt values" have been the object private data, but I can't confirm this.
This time the inlined subVI was a static dispatch method with contents shown below on the left and the calling on the right.
I'm showing the calling just to point out that when I was investigating the problem and I probed the object wires before and after the inlined subVI the values (Calibration.X Step and Calibration.Y Step) were OK, but the result of the VI (Point out) was some insane value as if the actual division inside was performed by corrupt data. I think that the output value wasn't Inf, though, so the divider might not have been a default value such as 0.
Other notes:
I checked that the wires are connected to the inputs and outputs
As I mentioned, the projects have always been relatively large AF setups, the problematic method has been an actor method or a method called by an actor somewhere down the chain. I have no reason to assume AF is the culprit, I'm just pointing this out, just in case
The problem seems to occur quite randomly but once it "starts" it doesn't go away until I find which inlined subVI it was and change it to a normal VI call
The problem might not even be specifically inlined subVI related but for example pre-allocated VI related instead
I don't know whether the problem would occur in a built executable as well, so far I've only ran into them while testing while developing and fixed them there
Looking at the "Known Issues" related to inlined subVI's I don't know if this related to them. The other one deals with execution systems, which I haven't touched to my knowledge, and the other one says "An Inline public methodVI calling a private-scope method VI, inlined into a non-class caller may give a runtime error when trying to call the private method from the inlined code in the non-class caller."
LabVIEW version is 14.0.1 (2014 SP1 32bit) on Windows 8.1
Yep, reading through this post I gotta say I'm not expecting much, what a mess, but it would be great to find out if anyone else has ever ran into similar problems or has a clue what's going here.

Just for the sake of your sanity, I've seen "funky" behaviour with inlined VIs also, but on Real-Time targets.
I've never been able to narrow down the exact problem but it seems to be related to changed made to inlined VIs not being reflected in the compiled code od VIs which call them.
I've reported it but without code which can actually reproduce it, it cannot be fixed.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Mini DVI to Video: blue screen after disconnect

Hi,
can't find a solution: after disconnecting the mini dvi to video-adapter I always get a blue screen and I need to restart my brandnew 20" iMac.
I use it to connect my (old) television via s-video. It is clear that I bought the right Mini-DVI-Adapter.
Can anyone help or has the same problem?
iMac 20" Mac OS X (10.4.8)

Thanks for the help. I'd figured out that shutting it off would keep it from happening and was probably a "best practice," but since 90% of my television watching is from my eyeTV, I'd be turning it on and off a lot.
The only problem with leaving the setup plugged in, is that as soon as the mini DVI cable is plugged in, the resolution on the iMac resets itself to super-large fit for television mode and becomes virtually unusable as a computer, thus when I want to use my computer, the cable has to be unplugged....unless of course you know something I don't
Thanks,
Shaun

MacBook Pro scrolling choppy after disconnecting from Cinema Display

Hi, I keep my 2.5 GHz 4GB RAM MBP in clamshell mode most of the time, connected to a 30-inch Cinema Display. When I pick it up and open it, scrolling in every application is super choppy and slow, and won't correct unless I reboot the computer. This is aggravating. Anyone have a fix? Thanks in advance!

Sometimes I experience the same after disconnecting my 24" display (in seldom cases, the mouse cursor is not painted correctly, as well).
Can you check - when it happens - if in System Profiler > Hardware > Graphic > Quartz Extreme is listed as 'supported'. I found it to be 'not supported' when the scrolling and display behaves strangly. Also the Menu Bar is not transparent any more.
Next to rebooting, logout and login again fixed the issue for me. But I am also looking for a better fix/explanation.
marcus

After installing Mountain Lion my MacBookPro crashes after disconnecting from Cinema Display

Ever since I installed Mountain Lion on my 15" MacBookPro (early 2011 first with Tunderbolt connector) it crashes after disconnecting from Cinema display (this Cinema does not have Thunderbolt but mini display port). It woked fine under Lion.
This crash occurs in following situation:
MacBookPro is in closed clam shell operation. When Cinema display is still connected, I put MacBookPro into sleep. Then I disconnect Cinema display mini diplay connector from Thuderbotl port.
When I get home and open MacBookPro it is in deep kernel crash.
It happens every time.
Any ideas how to fix this?
Thanks
Rich

You can bypass GateKeeper.

Right USB Port stops working after disconnecting device since 10.9.2

Hi,
Since updating to 10.9.2 the right USB port on my MBA stops working after diconnecting a device (tested: external hard drive, USB flash drive, USB HSPA Modem). The only way to get the port recognizing the device on that port is to do a restart. If the device is connected from starting the MBA it works fine, if I then eject the drive and reinsert it or a different USB device the device doesn't get recognized. The devices do get power, my WD passport ultra spins up just fine, the USB HSPA modem also indicates it's working (with signal) but nothing shows up in finder or diskutility. If the modem is connected from start (and thus working) and then disconnect from the internet but not remove the drive I can reconnect to the internet. The problem only occurs after disconnecting the device. The port becomes inactive. The left USB port works as expected.
Steps I've taken:
Disk Persmission
PRAM
SMC
Reapplied the 10.9.2 update
Sent feedback to Apple
Some Output:
Boot Mode: Normal
Total CPU usage:
   User 11%                    System 10%
Max %CPU by process (name, UID, %):
   WindowServer         0   4.6
Loaded extrinsic kernel extensions:
   at.obdev.nke.LittleSnitch (4052)
   com.driver.JRDUSBModemData64 (4.0.5)
   com.protech.NoSleep (1.3.3)
Loaded extrinsic daemons:
   net.sourceforge.MonolingualHelper
   com.oracle.java.JavaUpdateHelper
   com.oracle.java.Helper-Tool
   com.microsoft.office.licensing.helper
   com.freemacsoft.appcleanerd
   com.adobe.fpsaud
   at.obdev.littlesnitchd
Loaded extrinsic user agents:
   com.oracle.java.Java-Updater
   at.obdev.LittleSnitchUIAgent
/Library/LaunchAgents:
   at.obdev.LittleSnitchUIAgent.plist
   com.oracle.java.Java-Updater.plist
/Library/LaunchDaemons:
   at.obdev.littlesnitchd.plist
   com.adobe.fpsaud.plist
   com.freemacsoft.appcleanerd.plist
   com.microsoft.office.licensing.helper.plist
   com.oracle.java.Helper-Tool.plist
   com.oracle.java.JavaUpdateHelper.plist
   net.sourceforge.MonolingualHelper.plist
/Library/PrivilegedHelperTools:
   com.freemacsoft.appcleanerd
   com.microsoft.office.licensing.helper
   com.oracle.java.JavaUpdateHelper
   net.sourceforge.MonolingualHelper
Extrinsic loadable bundles:
   /System/Library/Extensions/JRDMassStorageDriver32.kext
             (No bundle ID)
   /System/Library/Extensions/JRDMassStorageDriver64.kext
             (No bundle ID)
   /System/Library/Extensions/JRDUSBModemData32.kext
             (com.driver.JRDUSBModemData32)
   /System/Library/Extensions/JRDUSBModemData64.kext
             (com.driver.JRDUSBModemData64)
   /System/Library/Extensions/LittleSnitch.kext
             (at.obdev.nke.LittleSnitch)
   /System/Library/Extensions/NoSleep.kext
             (com.protech.NoSleep)
   /Library/Audio/Plug-Ins/Components/A52Codec.component
             (com.shepmater.A52Codec)
   /Library/Internet Plug-Ins/Flash Player.plugin
             (com.macromedia.Flash Player.plugin)
   /Library/Internet Plug-Ins/JavaAppletPlugin.plugin
             (com.oracle.java.JavaAppletPlugin)
   /Library/PreferencePanes/Flash Player.prefPane
             (com.adobe.flashplayerpreferences)
   /Library/PreferencePanes/JavaControlPanel.prefPane
             (com.oracle.java.JavaControlPanel)
   /Library/PreferencePanes/NoSleep.prefPane
             (com.protech.NoSleepPref)
   /Library/QuickTime/AC3MovieImport.component
             (com.cod3r.ac3movieimport)
   /Library/Spotlight/LogicPro.mdimporter
             (No bundle ID)
   Library/Address Book Plug-Ins/SkypeABDialer.bundle
             (com.skype.skypeabdialer)
   Library/Address Book Plug-Ins/SkypeABSMS.bundle
             (com.skype.skypeabsms)
   Library/QuickLook/Pacifist.qlgenerator
             (com.charlessoft.pacifist.qlgenerator)
   Library/Services/Clip to Day One.workflow
             (No bundle ID)
Login hook:
   /Library/Scripts/Hooks/login.sh
Global login items:
   $HELPER_PATH
   $HELPER_PATH
   $HELPER_PATH
   $HELPER_PATH
   $HELPER_PATH
User login items:
   iTunesHelper
   Sparrow
   Sort Menubar Items
   AppCleaner Helper
   SurplusMeterAgent
Safari extensions:
   Shut Up
   AdBlock
   SafariKeywordSearch
   Disconnect
   MapTricks
Restricted user files: 28
Font problems: 0
Elapsed time (s): 130
etrecheck output:
Hardware Information:
          MacBook Air - model: MacBookAir3,1
          1 1.4 GHz Intel Core 2 Duo CPU: 2 cores
          2 GB RAM
Video Information:
          NVIDIA GeForce 320M - VRAM: 256 MB
System Software:
          OS X 10.9.2 (13C64) - Uptime: 0 days 0:20
Disk Information:
          APPLE SSD TS064C disk0 : (60.67 GB)
                    EFI (disk0s1) <not mounted>: 209.7 MB
                    disk0s2 (disk0s2) <not mounted>: 59.81 GB
                    Recovery HD (disk0s3) <not mounted>: 650 MB
USB Information:
          EFI (disk2s1) <not mounted>: 209.7 MB
          Radha (disk2s2) /Volumes/Radha: 1.81 TB (1.73 TB free)
          disk2s3 (disk2s3) <not mounted>: 189.89 GB
          Boot OS X (disk2s4) <not mounted>: 134.2 MB
FireWire Information:
Kernel Extensions:
          at.obdev.nke.LittleSnitch          Version: 4052
          com.driver.JRDUSBModemData64          Version: 4.0.5
          com.protech.NoSleep          Version: 1.3.3
Problem System Launch Daemons:
Problem System Launch Agents:
Launch Daemons:
                 [loaded]          at.obdev.littlesnitchd.plist
                 [loaded]          com.adobe.fpsaud.plist
                 [loaded]          com.freemacsoft.appcleanerd.plist
                 [loaded]          com.microsoft.office.licensing.helper.plist
                 [loaded]          com.oracle.java.JavaUpdateHelper.plist
                 [loaded]          net.sourceforge.MonolingualHelper.plist
Launch Agents:
                 [loaded]          at.obdev.LittleSnitchUIAgent.plist
User Launch Agents:
User Login Items:
          iTunesHelper
          Sparrow
          Sort Menubar Items
          AppCleaner Helper
          SurplusMeterAgent
3rd Party Preference Panes:
          Flash Player
          Java
          NoSleep
Internet Plug-ins:
          Default Browser.plugin
          Flash Player.plugin
          FlashPlayer-10.6.plugin
          JavaAppletPlugin.plugin
          QuickTime Plugin.plugin
User Internet Plug-ins:
Bad Fonts:
          None
Top Processes by CPU:
              12%          com.apple.WebKit.Networking
               6%          Safari
               4%          WindowServer
               3%          EtreCheck
               2%          hidd
               1%          Terminal
               1%          notifyd
               1%          opendirectoryd
               1%          com.apple.WebKit.WebContent
               0%          Dock
Top Processes by Memory:
          147 MB          Safari
          137 MB          com.apple.WebKit.WebContent
          49 MB          mds_stores
          29 MB          com.apple.WebKit.Networking
          27 MB          TextEdit
          23 MB          WindowServer
          20 MB          Disk
          20 MB          Sparrow
          20 MB          CVMCompiler
          18 MB          Finder
Nothing out of the ordinairy. Thanks for any help

It's an Apple Pro keyboard and mouse, the dongle is
plugged into the Mac and not the keyboard. The same
set-up is, and has been working on all our other
Macs.
The sleep issue sounds interesting- hum, maybe...
Is your keyboard plugged into one of the USB connections on an Apple monitor? If so, you may want to change that connection to one that is on the G5 itself. My monitor came with a warning note indicating that problems will likely occur if the keyboard is connected to the monitor.
I also had a problem with the automatic sleep function. After much trouble-shooting and a logic board replacement, it was concluded that coming out of the automatic sleep function with any USB device active would freeze the entire USB bus. After disabling automatic sleep in system preferences, I've had no freezing problems. My machine works fine with the manual sleep function in the Apple Menu.
AndyH

How do I get the full volume to return after disconnecting HDMI and MAC BOOK PRo from tv?

After buying and connecting the HDMI cable from my MAC BOOK PRO to my tv to play DVDs I had no sound on my tv. So I followed suggestions from this communintyl through selecting PREFERENCES/sound and following the instructions and was successful. After disconnecting all from my TV my tv will not return to it's FULL volume capabiliity. How do I get the full volume to return to my tv?

Some suggestions
Turn off the TV/ turn it back on
Turn up the volume

HDMI does not come back after disconnect

Hello Archers,
this one is bugging me for a while now, perhaps someone has an idea.
I have a headless ARCH home server that mainly has the following purposes:
1. being a 24/7 file/backup/ssh server for family and friends
2. being an MPD server connected to my music system
The setup may seem a bit exotic. The computer is connected to the music system via HDMI over an S/PDIF audio extractor to the music system. This is because the machine replaced a RaspberryPi that really had crappy analog audio output and my music system has an optical input and can perform the digital to analog conversion itself. I have not installed Pulse just alsa and jack2-dbus.
aplay -l shows the following:
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC887-VD Analog [ALC887-VD Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 0: PCH [HDA Intel PCH], Gerät 3: HDMI 0 [HDMI 0]
Sub-Geräte: 0/1
Sub-Gerät #0: subdevice #0
The Problem:
Whenever I switch off the music system and later switch it back on, the HDMI-connection is lost and does not get reestablished. I tried various things but essentially only a reboot of the machine helps (which opposes purpose 1 of the machine). On the RaspberryPi I did not have that problem, probably due to the hdmi_force_hotplug=1 in /boot/config.txt.
My Observations so far:
The first problem that made the sound disappear was the screen blanker on the console after 10 minutes. This can be prevented with
setterm --term linux --blank 0 >/dev/tty1 # You need write permission on /dev/tty1 for this to work!
There are no appearant error or warning messages when using e.g. aplay or speaker-test, just no sound at all
There are tipps in the forums/the internet sugesting to disable power management on the display involving xset and xrandr. However, I have no X running and the tools complain that they cannot find/open the display
In /proc/asound/PCH/codec#2 I find the HDMI codec to show the following as long as it is connected after a reboot:
Codec: Intel Valleyview2 HDMI
Address: 2
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x80862882
Subsystem Id: 0x80860101
Revision Id: 0x100000
No Modem Function Group found
Default PCM:
rates [0x0]:
bits [0x0]:
formats [0x0]:
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
Power states: D0 D3
Power: setting=D0, actual=D0
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x02 [Audio Output] wcaps 0x6611: 8-Channels Digital
Device: name="HDMI 0", type="HDMI", device=3
Converter: stream=8, channel=0
Digital: Enabled GenLevel
Digital category: 0x2
IEC Coding Type: 0x0
PCM:
rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000
bits [0x1e]: 16 20 24 32
formats [0x5]: PCM AC3
Power states: D0 D3
Power: setting=D0, actual=D0
Node 0x03 [Audio Output] wcaps 0x6611: 8-Channels Digital
Converter: stream=0, channel=0
Digital: Enabled
Digital category: 0x0
IEC Coding Type: 0x0
PCM:
rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000
bits [0x1e]: 16 20 24 32
formats [0x5]: PCM AC3
Power states: D0 D3
Power: setting=D0, actual=D0
Node 0x04 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
Control: name="HDMI/DP,pcm=3 Jack", index=0, device=0
Control: name="IEC958 Playback Con Mask", index=0, device=0
Control: name="IEC958 Playback Pro Mask", index=0, device=0
Control: name="IEC958 Playback Default", index=0, device=0
Control: name="IEC958 Playback Switch", index=0, device=0
Control: name="ELD", index=0, device=3
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x00]
Pincap 0x09000094: OUT Detect HBR HDMI DP
Pin Default 0x18560010: [Jack] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Pin-ctls: 0x40: OUT
Unsolicited: tag=01, enabled=1
Power states: D0 D3
Power: setting=D0, actual=D0
Connection: 2
0x02* 0x03
Node 0x05 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x80]
Pincap 0x09000094: OUT Detect HBR HDMI DP
Pin Default 0x58560020: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0x2, Sequence = 0x0
Pin-ctls: 0x40: OUT
Unsolicited: tag=00, enabled=0
Power states: D0 D3
Power: setting=D0, actual=D0
Connection: 2
0x02 0x03*
Node 0x06 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x00 0x80]
Pincap 0x09000094: OUT Detect HBR HDMI DP
Pin Default 0x58560030: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0x3, Sequence = 0x0
Pin-ctls: 0x40: OUT
Unsolicited: tag=00, enabled=0
Power states: D0 D3
Power: setting=D0, actual=D0
Connection: 2
0x02 0x03*
Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono
After disconnect/reconnect it changes to this:
Codec: Intel Valleyview2 HDMI
Address: 2
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x80862882
Subsystem Id: 0x80860101
Revision Id: 0x100000
No Modem Function Group found
Default PCM:
N/A
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
Power: setting=UNKNOWN, actual=UNKNOWN, Error, Clock-stop-OK, Setting-reset
Invalid AFG subtree
I figured that the problem is probably related to powermanagement, so I experimented with powertop. This resulted in a reduced consumption of 1W when idle, which is nice but did not solve the original problem...
The Questions
Is there a way to completely reinit the HDMI subsystem just like on a reboot?
Is there an option comparable to hdmi_force_hotplug=1 on the pi that forces the HDMI signal to stay up?
Thank You for Your time!
Best regards,
Lars

I can confirm what zofiel said. I have tested it by connecting a TV and HDMI reactivitated by switching from X to console. However, this option only works one time and requires X running in the first place, which I usually have not on a headless server, but it made me think: Obviousely the X server needs to activate the graphics in the first place. Then I came up with an idea for a really messy work around. I could try to remotely start X. Normally, this is not possible and you get:
% startx
/usr/lib/xorg-server/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
You can force it to work:
sudo startx
You get lots of error messages, but HDMI audio is back, even if one kills the X process afterwards with Ctrl+C (Audio stops, but resumes two seconds later). The downside is that starting X with sudo messes up permissions with the x related files in your home directory and you will have problems to use startx afterwards, so it is probably better to use su instead of sudo. If root does not have a properly configured .xinitrc file then one can also just execute the desktop environment directly e.g., for XFCE:
su - root -c "startxfce4"
Then kill it with Ctrl+C and you should have HDMI Audio working.
So now I could pack this in a script followed by some command to kill it, but, well, it is an ugly workaround
Is there really no better way?

MPB + 24" LED, weird behaviour after disconnect

Similar Messages

Maybe you are looking for