No zoom level controls on second monitor!

I use a second monitor to display a loupe view of the photo I have selected in the grid view, which is on the first monitor. I have always had the zoom-level controls (Fit, Fill, etc.) at the bottom of the loupe display on the second moitor, until I replaced my first monitor this week. Everything else is still the same, but I no longer have the zoom controls on the second monitor. This means that I cannot change the zoom levels that are availabel to me. I either have Fit or 100% zoom. Without the zoom controls on the second monitor I can't change the settings. Does anyone know how to get the zoom controls back (or why they might have disappeared)?
Thanks for any help.

Never mind. I found the problem (the second monitor was in full-screen mode). Nothing
to see here. Keep moving.

Similar Messages

Can I keep firefox at a 125% zoom level? I use my HDTV as a monitor and would like the view to be larger without having to hit "ctrl +" on each web page.

I would like firefox to default to a 125% zoom level. Is ther a way I can do this through firefox or through my desktop?

The following Add-on will allow you to set whatever default %-age works best for you. After install, go to Add-ons > Extensions > Default FullZoom Level > Options, in the Options window, "Default FullZoom Level (percent)". That will set ALL pages at your choice.
*'''''Default FullZoom Level''''': https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/
*Support for '''''Default FullZoom Level''''': http://forums.mozillazine.org/viewtopic.php?f=48&t=659681&start=75
Also look at NoSquint
*'''''NoSquint''''': https://addons.mozilla.org/en-US/firefox/addon/nosquint/
*More info on NoSquint: http://urandom.ca/nosquint/
'''If this reply solves your problem, please click "Solved It" next to this reply when <u>signed-in</u> to the forum.'''

Mission Control second monitor...

Hello!
In Snow leopard expose showed all the windows even if I used a second monitor I could see all windows in my first screen!
Now in Lion I only see the acual windows at the actual monitor...
There is a problem with that... if I don´t have the second monitor on and a software window is placed on that second monitor I can't see it... I have to start the second monitor or get into double screen!
Please help if there is a solution for that!
/ Jan

Hi Bansaku,
Sorry to hear you're in the same boat. At least we don't have to suffer in silence : )
I'm also the same with desktop pictures being messed up (I also wish they'd let us rename each Desktop e.g. Photoshop, Mail, Safari etc).
I don't tend to restart my Mac that often, but overtime I do, my spaces are all are of sync.
Is there any easy way to report this problem to Apple?
Thanks!

CS4 NOT capable of sharp displays at all zoom levels

I must have been asleep, until now, and missed the significance and importance of what follows.
In post #11 here:
http://forums.adobe.com/thread/375478?tstart=30
on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
"You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.
1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
2. Here's another Adobe TV video from Deke McClelland:
http://tv.adobe.com/#vi+f1584v1021
In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
under the heading 'GPU powered display', this text appears :
"Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
http://tv.adobe.com/#vi+f1556v1686
After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

Thanks, Andrew, for bringing this up. I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels. I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels. After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off. They look similar, if not the same.
The "new", OpenGL way of display is using bilinear interpolation.
I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation. This infers that the interpolation is bilinear.
Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ). It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things. Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below). With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated. With bilinear, those details will still be visible but with less sharpness than other details. Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't. To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts. Resolution of the monitor used may also be a factor. The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not. CRT vs LCD may also play a role in noticeability.
The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up. I do not believe this is correct. There are some integer zoom percentages that will appear less sharp than others. It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
Overall conclusion:
The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect. I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%. It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows. When I think about it, that appears to be just what Adobe is doing.
Some sample comparisons:
I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation. One is of a simple grid made up of 1 pixel wide lines. The other is of an image of a squirrel. You might find them interesting. In particular, check out the following:
Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
Notice how nearest-neighbor favors sharp edges. It isn't accurate but it's sharp.
On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions. There are differences in sharpness though at different zoom percentages for bilinear, though. I just didn't include enough samples to show that clearly here. You can see this yourself by comparing results of zooms a few percentages apart.
Well, I hope that was somewhat helpful. Comments and corrections are welcomed.

CS4 - Is there a way to adjust gamma for second monitor or send to overlay?

One thing that is evident when I edit in Premiere CS4 using the AVCHD 1080i 60 template is that the preview in the second monitor, which in my case is my TV set connected using a DVI to HDMI cable, is that the output is too dark compared to what it should be. Darker areas of the frame sometimes even get crushed into black when the same footage, when played directly from the camcorder, or even burned to blu-ray and played, is noticeably brighter and at the right black levels.
This doesn't happen when editing in Vegas Pro 8, or when the untouched footage is played through other video player, including Windows 7 Media Center.
A workaround for this problem can be to go to the graphics card control panel, in my case ATI Catalyst, and adjust the gamma for the second monitor, with the problem being that when you're done editing in Premiere you have to go back to the normal gamma. At one point I had setup two profiles in Catalyst with shortcuts and it worked well, but one day Catalyst simply lost the profiles and noticing how buggy it was I wasn't going to keep creating profiles so that Catalyst would delete them.
So my question is, since it's not in the preferences, is there some settings file or registry address that I can tweak to make Premiere display a brighter gamma of my choice?
And this may be a dead end, but is there a way to send the output of the second monitor to the overlay so that it can take advantage of the graphic's card video capabilities and display video smoothly? It's nice to have a preview of the timeline, but it's rather annoying if I have to go to the Catalyst control panel and adjust gamma before editing and after editing and that motion is jerky and not interlaced when I'm editing interlaced content.

You need the VESA mount option. That way your minimum angle would be completely vertical and you could open it to a negative 10 degrees.
Hope this helps.
Pete
I am not an HP employee, But I did stay at a Holiday Inn Express last night.
TouchSmart IQ526t CTO Intel 2.26 Ghz 4 gig ram 750 gig HDD Vista Premium 64 bit

How can i have a full screen preview of my photo on second monitor? I mean i want to live broadcast the result without save the file

I want to see the result of my editing on the second monitor for broadcasting

Window > Arrange and right at the bottom New window for (your file name)
You can drag this across to the second monitor, and work on either window. The results will be reflected in the other window. You can have each window at different zoom levels, so It's a useful trick for seeing an overall result of making a local edit while zoomed in.
Note: if your dual monitor workspace has panels open on the second screen, they will obscure the new window. So you would need to change the workspace back to something like Essentials.

Shadows of 1st monitor on second monitor.

Hello!
I just "upgraded" my setup from macmini to mbp. Which means I'm new to 2 screen setup, that I have now on my table. There are some really annoying things about it. As I use laptop in front of my cinema display I have laptop screen on the bottom and cinema display above it. I'm running LogicPro from the edge of the screen to another edge of the screen (not fullscreen mode). And when I have some other application on the display of the laptop it has terrible looking shadow from my main monitor on it. Is there a way to disable the shadows going from one monitors windows to another monitor? I undestand that shadows only appear to the active application's windows but they don't look and feel nice.

Window > Arrange and right at the bottom New window for (your file name)
You can drag this across to the second monitor, and work on either window. The results will be reflected in the other window. You can have each window at different zoom levels, so It's a useful trick for seeing an overall result of making a local edit while zoomed in.
Note: if your dual monitor workspace has panels open on the second screen, they will obscure the new window. So you would need to change the workspace back to something like Essentials.

Accessibility "zoom" - counterintuitive controls

I am looking for a way to reverse the direction of scrolling it takes to initiate the screen zoom with trackpad and modifier key. As it is, scrolling "up" (towards the screen, away from the user) zooms in. Elsewhere (on other OSes I mean), this can be customized, and the default is what I consider to be more natural.
If you read text on some actual sheet of paper, and there is fine print that's too small to read at the standard distance, you pull the paper closer to your eyes. That would naturally translate into using the trackpad to "pull" the screen content closer to you, not pushing it away. As it is, the gesture is pushing it away. The same orientation applies when using a mouse - scrolling towards you should zoom in
It would be great if there could be a control field added in a future version which would allow to reverse this.
My 88-year old Mom uses that feature all the time, and now after switching to a Mac, she has to adapt. For now, I would settle for some command line-level control setting where this could be changed.
BTW, that gesture is labeled "Use scroll gesture with modfier key to zoom" but it does not seem to honor the global setting of the scroll sense. When I uncheck the "natural" scroll direction, it does not revert the direction it takes for the zoom.
Any help or insights would be highly appreciated. Thanks!

I just found a great workaround for the zoom and it works better than before.
The zoom defaults to fullscreen zoom and when you have multiple monitors it zooms all of them. Normally I don't need to zoom all just the one monitor that I'm working on.
Go to "system preferences " ,"accessibility ", set zoom style to "picture in picture" and then click "more options" and then click "adjust size and location" then you can set the zoom window to the size of a monitor. then when you zoom only the monitor you are on gets zoomed and is fast.
Works for me. Hopefully helps others as well.

Want to make my Ipad 4 into a second monitor

I have an iPad 4 and a macbook pro and I want to connect them and make my ipad a second monitor. I know that I have to download an app but I want to make sure that I get the best/right one.
I also saw that I can connect my ipad to my computer and control my computer from my ipad, so if anyone has experience with either of these things let me know!

If you plan on using your iPad as a semi permanent second display when working at your Mac, if you plan to do this for long periods of time, make sure your iPad is plugged into power.
These remote display apps tend to be more of a drain on the iPad's battery. Especially so if the remote display app uses Bluetooth instead of over WiFi.
I like and use an app called Air Display.
For using your iPad as a remote client to run your Mac remotely, there are a few decent apps for thiis, but it depend so what you really want to do.
I wanted remote control of my Mac, locally, so I use a remote app called SplashTop remote.
If you need remote location control of your Mac, also, there are other apps for that like LogMeIn and Team Viewer to name a few.

DVI- HDMI discoloration on HDTV (as second monitor)

Hello all.
I have been having some issues when using my Philips CRT 30" 1080i HDTV as a second monitor via a DVI->HDMI cable. There seems to be a discoloration that occurs (my best guess being a "green" discoloration) that occurs in the top left corner of the screen. It is made all the more apparent when you then unplug, and a purple haze is left in the corner of the "blue" video input channel. (i imagine the green discoloration on the blue channel yields purple).
From what I can tell, this problem does not occur on any other video input (say, a Wii on the composite channel, or an XBOX on the component, etc).
I had heard rumblings that it could be, in order of bad to worst: a bad HDMI cable, a bad HDMI input on the television, or the television going bad period.
Wanted to know if any of you have had or heard of similar experiences. Need to decide soon if I'm going to had to just buy a new HDMI cable, or if I need to buy a new television/monitor for a job coming up.
Thanks in advance!
Brian
4/30/10 2:47 PM
Hardware:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version (system): 1.16f11
Sudden Motion Sensor:
State: Enabled
Network:
Bluetooth DUN:
Type: PPP (PPPSerial)
Hardware: Modem
BSD Device Name: Bluetooth-Modem
Has IP Assigned: No
Service Order: 0
Ethernet:
Type: Ethernet
Hardware: Ethernet
BSD Device Name: en0
Has IP Assigned: No
Service Order: 1
FireWire:
Type: FireWire
Hardware: FireWire
BSD Device Name: fw0
Has IP Assigned: No
Service Order: 2
AirPort:
Type: AirPort
Hardware: AirPort
BSD Device Name: en1
Has IP Assigned: Yes
Service Order: 3
Software:
System Software Overview:
System Version: Mac OS X 10.6.3 (10D573)
Kernel Version: Darwin 10.3.0
64-bit Kernel and Extensions: No
Time since boot: 12 minutes
ATA:
ATA Bus:
MATSHITADVD-R UJ-857E:
Model: MATSHITADVD-R UJ-857E
Revision: ZA0E
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: Yes
Power Off: Yes
Audio (Built In):
Intel High Definition Audio:
Device ID: 0x106B00A0
Audio ID: 44
Available Devices:
Speaker:
Connection: Internal
Headphone:
Connection: Combo
Internal Microphone:
Connection: Internal
Line In:
Connection: Combo
S/P-DIF Out:
Connection: Combo
S/P-DIF In:
Connection: Combo
Bluetooth:
Apple Bluetooth Software Version: 2.3.1f4
Hardware Settings:
Vendor ID: 0x5ac
Product ID: 0x8205
Devices (Paired, Favorites, etc):
Device:
Type: Mouse
Firmware Version: 0x200
Services: Mighty Mouse
Manufacturer: Broadcom (0x2, 0x314)
Vendor ID: 0x5ac
Product ID: 0x30c
Diagnostics:
Power On Self-Test:
Last Run: 4/30/10 2:35 PM
Result: Passed
Disc Burning:
MATSHITA DVD-R UJ-857E:
Firmware Revision: ZA0E
Interconnect: ATAPI
Burn Support: Yes (Apple Shipping Drive)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -R DL, -RW, +R, +R DL, +RW
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media: To show the available burn speeds, insert a disc and choose View > Refresh
Ethernet Cards:
pci168c,24:
Type: Other Network Controller
Bus: PCI
Slot: PCI Slot 5
Vendor ID: 0x168c
Device ID: 0x0024
Subsystem Vendor ID: 0x106b
Subsystem ID: 0x0087
Revision ID: 0x0001
Link Width: x1
BSD name: en1
Kext name: AirPortAtheros.kext
Location: /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros.k ext
Version: 422.19.10
Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA:
Name: ethernet
Type: Ethernet Controller
Bus: PCI
Vendor ID: 0x11ab
Device ID: 0x436a
Subsystem Vendor ID: 0x11ab
Subsystem ID: 0x00ba
Revision ID: 0x0013
Link Width: x1
BSD name: en0
Kext name: AppleYukon2.kext
Location: /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleYukon2 .kext
Version: 3.1.14b1
FireWire:
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
G-Drive mini Device 00:
Manufacturer: G-TECH
Model: 0x0
GUID: 0x1C0D02E00B0A3E
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
G-Drive mini Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x103
Product Revision Level: FBEO
Sub-units:
G-Drive mini Device 00 SBP-LUN:
Capacity: 250.06 GB (250,059,350,016 bytes)
Removable Media: Yes
BSD Name: disk1
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
Volumes:
disk1s3:
Capacity: 249.93 GB (249,925,091,328 bytes)
Available: 21.68 GB (21,684,412,416 bytes)
Writable: Yes
File System: Journaled HFS+
Graphics/Displays:
NVIDIA GeForce 8600M GT:
Chipset Model: GeForce 8600M GT
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0407
Revision ID: 0x00a1
ROM Revision: 3175
Displays:
Color LCD:
Resolution: 1440 x 900
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Built-In: Yes
Display Connector:
Status: No Display Connected
Memory:
Memory Slots:
ECC: Disabled
BANK 0/DIMM0:
Size: 2 GB
Type: DDR2 SDRAM
Speed: 667 MHz
Status: OK
Manufacturer: 0x7F7F7F7F7F9B0000
Part Number: 0x4354323536363441433636372E4D31364647
BANK 1/DIMM1:
Size: 2 GB
Type: DDR2 SDRAM
Speed: 667 MHz
Status: OK
Manufacturer: 0x7F7F7F7F7F9B0000
Part Number: 0x4354323536363441433636372E4D31364647
PCI Cards:
pci168c,24:
Type: Other Network Controller
Driver Installed: Yes
Bus: PCI
Slot: PCI Slot 5
Vendor ID: 0x168c
Device ID: 0x0024
Subsystem Vendor ID: 0x106b
Subsystem ID: 0x0087
Revision ID: 0x0001
Link Width: x1
Link Speed: 2.5 GT/s
Serial-ATA:
Intel ICH8-M AHCI:
Vendor: Intel
Product: ICH8-M AHCI
Link Speed: 1.5 Gigabit
Negotiated Link Speed: 1.5 Gigabit
Description: AHCI Version 1.10 Supported
FUJITSU MHW2160BHPL:
Capacity: 160.04 GB (160,041,885,696 bytes)
Model: FUJITSU MHW2160BHPL
Revision: 0081001C
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified
Volumes:
disk0s2:
Capacity: 131.94 GB (131,936,026,624 bytes)
Available: 23.73 GB (23,733,391,360 bytes)
Writable: Yes
File System: Journaled HFS+
disk0s3:
Capacity: 27.63 GB (27,626,639,360 bytes)
Available: 13.65 GB (13,652,635,648 bytes)
Writable: Yes
File System: Journaled HFS+
USB:
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x2836
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfd
Built-in iSight:
Product ID: 0x8502
Vendor ID: 0x05ac (Apple Inc.)
Version: 1.45
Serial Number: 607F59A99AB2811A (03.00)
Speed: Up to 480 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0xfd400000
Current Available (mA): 500
Current Required (mA): 500
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x283a
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfa
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2835
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0x3a
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2834
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0x1a
Bluetooth USB Host Controller:
Product ID: 0x8205
Vendor ID: 0x05ac (Apple Inc.)
Version: 19.65
Speed: Up to 12 Mb/sec
Manufacturer: Apple Inc.
Location ID: 0x1a100000
Current Available (mA): 500
Current Required (mA): 0
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2830
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0x1d
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2831
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0x3d
USB Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBUHCI
PCI Device ID: 0x2832
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0x5d
Apple Internal Keyboard / Trackpad:
Product ID: 0x021a
Vendor ID: 0x05ac (Apple Inc.)
Version: 0.18
Speed: Up to 12 Mb/sec
Manufacturer: Apple Computer
Location ID: 0x5d200000
Current Available (mA): 500
Current Required (mA): 40
IR Receiver:
Product ID: 0x8242
Vendor ID: 0x05ac (Apple Inc.)
Version: 0.16
Speed: Up to 1.5 Mb/sec
Manufacturer: Apple Computer, Inc.
Location ID: 0x5d100000
Current Available (mA): 500
Current Required (mA): 100
AirPort:
Software Versions:
Menu Extra: 6.2.1 (621.1)
configd plug-in: 6.2 (620.15.1)
System Profiler: 6.0 (600.9)
Network Preference: 6.2.1 (621.1)
AirPort Utility: 5.5.1 (551.19)
IO80211 Family: 3.1 (310.6)
Interfaces:
en1:
Card Type: AirPort Extreme (0x168C, 0x87)
Firmware Version: Atheros 5416: 2.0.19.10
Locale: FCC
Country Code: US
Supported PHY Modes: 802.11 a/b/g/n
Supported Channels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 149, 153, 157, 161, 165
Status: Connected

Problems like that are caused by stray magnetism that cause misalignment of the electron beams from landing on the proper phosphor color. The set itself has a demagnetizer, but sometimes the magnetism is too strong for the built-in demagnetizer to overcome. But calling in a TV repair person to do a demagnetization is, I'm afraid, a throw back to bygone days. But that's what your TV needs.

How do I get my Mac Pro to see the second monitor through a video splitter and/or switcher?

In a recording studio we have a Mac Pro with two video display monitors in the control room and we want to be able to show the content of the second monitor to the person in the recording room on a big display monitor there. However, when we interpose a switcher or splitter between the computer and the second monitor so that we can (with a switcher) switch the second monitor signal from the control room monitor to the record room monitor or (with a splitter) split the signal to go to both monitors, we have no luck. On startup the computer does not see the monitor through the switcher, so it doesn't recognize its existence. If we start the computer up without the switcher in the signal chain, it sees the second monitor just fine, and (weirdly enough) we can then change the cabling to interpose the switch, which then works to switch back and forth between second monitors (control room and record room), but that cable swapping's a royal PITA. We want a simple solution that will allow us to start up the computer, see the second monitor in the control room, then choose to show it to the person in the record room with a simple flip of the switch (or even better, split the signal so it's available both places). The splitter we've tried most recently is this one: http://tinyurl.com/curen39 I'd appreciate any advice from people who have tried this configuration or something similar with success. We have a full ProTools HD Accel 3 system installed, so there's no room to install a second video card. Thanks.
Mac Pro 8-Core 2.4 GHz, OS 10.6.8

Christopher Dobrian wrote:
Thanks for the response! Yes, it's a 5x70 video card, a 5770 I believe. In any case, it does have the three ports, but (a not-well documented fact) that doesn't mean one can really get three full-resolution signals out of it at one time, as you alluded to in your message. So, yes, we did try hooking all three up directly to the computer, but the computer would only recognize two of those monitors, and the only way to get it to "de-recognize" the second monitor and recognize the third monitor was to physically disconnect the second monitor.
I did say when you want to connect three monitors to 5x70's there are some rules to adhere to. These are covered in the first two apple docs mentioned above, or by title:
Mac Pro (Mid 2010), Mac Pro (Early 2009): Issues with three displays and multiple DVI, HDMI connections
Mac Pro (Early 2009), Mac Pro (Mid 2010): Supported display configurations
The general gist of these rules is that to drive three monitor son a 5x70 you need two active adapters. That is why one of your monitors was disabled when you tried to add a third.
Here's a good explanation of what's going in here and why you need two active adapters on these cards:
Active vs. Passive Displayport adapters *the truth*
If you use DVI monitors and any of them have resolutions less than 1920 x 1200 then you can use single link active adapters. The "AMD Eyefinity Validated Dongles" chart shows some active (and passive) adapters that are acceptable. For example of a single link DVI active adapter is the Accell B087B-006B. An example of a dual link DVI active adapter would be the one from monoprice.com if you need to connect monitors with a resolution greater than 1920 x 1200.
I'm doubtful that SwitchResX would be able to convince the computer that there were only two monitors connected and direct the second monitor signal to the correct place, but it certainly seems worth a try, so thanks for the idea! Any other ideas are still welcome in the meantime.
I'm not doubtful. It is a very powerful utility for dealing with all aspects of multiple monitor configurations (they call them "Display Sets") complete with forcing EDID information if necessary. The different configurations can be controlled with a (contextual) menu and/or hot key.
SwitchResX is academic at this point if you want to have all three monitors connected. You would need to get that working first. Then use SwitchResX to vary the configuration combinations. So if you go this route the "name of the game" is figure out the active adapters you need.
I only described in general terms above about the adapters since you never said exactly what kind of connections these monitors require (single link DVI, dual link DVI, hdmi, mini-displayport, vga).

Any way to put your own zoom level in the zoom dropdown?

It turns out that on my 15.6" laptop screen a 65% zoom level is about perfect for fitting my spread in the display so that I can actually read the text in the text frames. (Double-clicking the Zoom tool puts me at a 75% zoom level but with text frames going outside my screen viewing area).
Pressing Control-Alt-0 puts me at 53.3% but with text slightly too small to read. Being stubborn, I want 65%, because then I can read all my text and fit the whole spread in the window minus the white blank area between the pink (magenta?) margins and the page trim (black border) which I don't need to see.
I know about the script method - I've already made my own keyboard shortcut for a 60% zoom level using a custom zoom60.jsx script file with a Control-Shift-1 keyboard shortcut.
Is there any way to add that 65% zoom level to the Zoom dropdown menu on the Application Bar (top of window)?
Note: You can't set a default Zoom level with no documents open because the Zoom control (dropdown at top) is greyed out - not accessible.

I found the ultimate solution to this - buy a new (business model) laptop with a better video card and screen. My top ("recommended") resolution is now 1600 x 900. The old one had a top resolution of 1366 x 768.
Pressing Control-Alt-0 to Fit Spread in Window on the old laptop gives me a 53% zoom level with fuzzy text that borders on unreadable. Pressing Control-Alt-0 on the new laptop gives me a 65% zoom level with text readable.
But, what I want is a command called: Fit Spread in Window But With A Smidgeon of White Showing Beyond The Margins. That turns out to be a 75% zoom level for me (which exists as a preset in the Zoom dropdown on the Application Bar at top of the interface), but I'll still need to do a script and map it to something like Control-Shift-1 because 75% does not result from any of the choices under the View menu. (Using Control-minus(-) and Control-plus(+) will get me to the 75% though). And, I want to get to that 75% without using the mouse.
Without getting too technical, I think working on a program like InDesign on a consumer model laptop (Acer Aspire 5535) with one of those horrible shiny screens is basically bad for your eyes. I'm now on a Lenovo Thinkpad W530 with beautiful matte screen (no glare) and text with very sharp edges.
I guess there are other solutions - like mapping Control-Alt-0 to a 75% zoom using a script to replace my current 65% zoom level.

Can I use the HDMI out on a HP ALL IN ONE TOUCHSCREEN Desktop to connect a second monitor with HDMI

Can I use the HDMI out on a HP ALL IN ONE TOUCHSCREEN Desktop to connect a second monitor with HDMI in without any additional software or graphics adaptor. I have a 520-1070
HP - 23" Touch-Screen TouchSmart All-In-One Computer - 8GB Memory - 2TB Hard Drive ? I used a HDMI to HDMI cable and the monitor was not recognized.

Here are the specs for your HP TouchSmart 520-1070 Desktop Computer. As previously stated your computer Doesn't have a HDMI output, instead it has a HDMI input. This is designed to let you connect a game console, a DVD/Bluray player, etc. to use as a monitor.
If you wish to conect a second monitor to your computer, you will need to use a USB-to-video adapter such as the EVGA UV Plus+ UV39 or EVGA UV Plus+ UV19. Using an adapter like these with the touch feature of your computer may cause issues with pointer control and you may need to disable the touch feature to use "extended desktop".
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

How do I Add second monitor to ALL in One ENVY23 that has a HDMI port

How do I Add second monitor to my ALL in One ENVY23 that has a HDMI port the computer has Win 8 Model #: 23se-d494
Product #: F3D93AA#ABA
Serial #: [edited Serial Number by Moderator]
Software Build #: 14AM1HRA601#SABA#DABA
Service ID #: 20140521
PCBRAND #: HP

Here are the specs for your HP ENVY TouchSmart 23se-d494 All-in-One Desktop Computer. Based the specs, the HDMI port on the side of your computer is an INPUT only. This model doesn't have a video output of any kind.
1 - Controls 2 - HDMI In port (model dependent)
You will need to purchase and use a USB-to-video adapter such as the EVGA UV Plus+ UV39 (or any of the many other adapters on the market) to connect an external display to your computer. I personally use and recommend the EVGA UV Plus+ UV39.
If you have any further questions, please don't hesitate to ask.
Please click the White KUDOS "Thumbs Up" to show your appreciation
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

Can't get correct resolution for second monitor

I am trying to use two monitors with a Vostro 1400 (Intel X3100 video card), the problem is I can't set the external monitor to 1280x1024. Gnome's screen resolution program only let me choose from 640x480 to 1360x768. Besides the resolution of the second monitor, everything else seems to be working fine. Some relevant info:
Xorg.0.log
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH x86_64
Current Operating System: Linux 2.6.27-ARCH #1 SMP PREEMPT Sun Dec 21 09:13:30 UTC 2008 x86_64
Build Date: 17 December 2008 10:46:49PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 25 02:18:40 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Failsafe Monitor"
(==) No device specified for screen "Default Screen".
Using the first device section listed.
(**) | |-->Device "Intel GMA X3100"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(==) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(**) Extension "RENDER" is enabled
(**) Extension "DAMAGE" is enabled
(**) Extension "XFIXES" is enabled
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x7b54e0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7
(--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfea00000/1048576, 0xe0000000/268435456, I/O @ 0x0000eff8/8
(--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfeb00000/1048576
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(==) AIGLX enabled
(==) Exporting typical set of GLX visuals
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.1.0
ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.4.3
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
965GM, 965GME/GLE, G33, Q35, Q33,
Mobile Intel® GM45 Express Chipset,
Intel Integrated Graphics Device, G45/G43, Q45/Q43
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Reloading /usr/lib/xorg/modules//libvbe.so
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 4.1
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(**) intel(0): Option "AccelMethod" "exa"
(**) intel(0): Option "DRI" "True"
(II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xE0000000
(--) intel(0): IO registers at addr 0xFEA00000
(II) intel(0): 2 display pipes available.
(**) intel(0): Using EXA for acceleration
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) intel(0): initializing int10
(WW) intel(0): Bad V_BIOS checksum
(II) intel(0): Primary V_BIOS segment is: 0xc000
(II) intel(0): VESA BIOS detected
(II) intel(0): VESA VBE Version 3.0
(II) intel(0): VESA VBE Total Mem: 7616 kB
(II) intel(0): VESA VBE OEM: Intel(r)GM965/PM965/GL960 Graphics Chip Accelerated VGA BIOS
(II) intel(0): VESA VBE OEM Software Rev: 1.0
(II) intel(0): VESA VBE OEM Vendor: Intel Corporation
(II) intel(0): VESA VBE OEM Product: Intel(r)GM965/PM965/GL960 Graphics Controller
(II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section Failsafe Monitor
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(**) intel(0): Option "NoDDC" "True"
(II) intel(0): found backlight control method /sys/class/backlight/acpi_video1
(II) intel(0): Output TV has no monitor section
(II) intel(0): Output VGA connected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TV disconnected
(II) intel(0): Using user preference for initial modes
(II) intel(0): Output VGA using initial mode 1280x800@60
(II) intel(0): Output LVDS using initial mode 1280x800
(II) intel(0): Monitoring connected displays enabled
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 7676 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(**) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(**) intel(0): Display dimensions: (336, 210) mm
(**) intel(0): DPI set to (193, 247)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.4.0
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x00000206 to 0x00000000
(WW) intel(0): PIPEBSTAT before: status: VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): PIPEBSTAT after: status:
(WW) intel(0): Register 0x68084 (TV_FILTER_CTL_2) changed from 0x0001f5f6 to 0x00028283
(WW) intel(0): Register 0x68088 (TV_FILTER_CTL_3) changed from 0x0000fafb to 0x00014141
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 488960 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 1955836 kB available
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 11, (OK)
drmOpenByBusid: drmOpenMinor returns 11
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xfea00000
(II) intel(0): [drm] ring buffer = 0xe0000000
(II) intel(0): [drm] mapped front buffer at 0xe0100000, handle = 0xe0100000
(II) intel(0): [drm] mapped back buffer at 0xe5600000, handle = 0xe5600000
(II) intel(0): [drm] mapped depth buffer at 0xe6a00000, handle = 0xe6a00000
(II) intel(0): [drm] mapped classic textures at 0xe7e00000, handle = 0xe7e00000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(**) intel(0): Option "MigrationHeuristic" "greedy"
(**) intel(0): Option "EXANoComposite" "false"
(II) EXA(0): Offscreen pixmap area of 62914560 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0077f000 (pgoffset 1919)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01a00000 (pgoffset 6656)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x05600000 (pgoffset 22016)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x06a00000 (pgoffset 27136)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x07e00000 (pgoffset 32256)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB)
(II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB)
(II) intel(0): 0x00032000-0x00043fff: exa G965 state buffer (72 kB)
(II) intel(0): 0x00044000-0x00044fff: overlay registers (4 kB)
(II) intel(0): 0x00045000-0x00045fff: power context (4 kB)
(II) intel(0): 0x00100000-0x019fffff: front buffer (25600 kB) X tiled
(II) intel(0): 0x0077f000: end of stolen memory
(II) intel(0): 0x01a00000-0x055fffff: exa offscreen (61440 kB)
(II) intel(0): 0x05600000-0x069fffff: back buffer (20480 kB) X tiled
(II) intel(0): 0x06a00000-0x07dfffff: depth buffer (20480 kB) Y tiled
(II) intel(0): 0x07e00000-0x09dfffff: classic textures (32768 kB)
(II) intel(0): 0x10000000: end of aperture
(II) intel(0): using SSC reference clock of 96 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is on
(II) intel(0): Display plane A is now enabled and connected to pipe A.
(II) intel(0): Pipe B is on
(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe A
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TV is connected to pipe none
(II) intel(0): [drm] dma control initialized, using IRQ 16
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): using SSC reference clock of 96 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): DPMS enabled
(II) intel(0): Set up textured video
(II) intel(0): Set up overlay video
(II) intel(0): direct rendering: Enabled
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 12, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 12, (OK)
drmOpenByBusid: drmOpenMinor returns 12
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) intel(0): Setting screen physical size to 338 x 211
(EE) intel(0): underrun on pipe A!
(II) config/hal: Adding input device AlpsPS/2 ALPS GlidePoint
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.99.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.1
(II) Synaptics touchpad driver version 0.99.2
(**) Option "Device" "/dev/input/event9"
(II) AlpsPS/2 ALPS GlidePoint: x-axis range 0 - 1023
(II) AlpsPS/2 ALPS GlidePoint: y-axis range 0 - 767
(II) AlpsPS/2 ALPS GlidePoint: pressure range 0 - 127
(II) AlpsPS/2 ALPS GlidePoint: finger width range 0 - 0
(II) AlpsPS/2 ALPS GlidePoint: buttons: left right middle
(**) Option "SHMConfig" "True"
(--) AlpsPS/2 ALPS GlidePoint touchpad found
(**) AlpsPS/2 ALPS GlidePoint: always reports core events
(II) XINPUT: Adding extended input device "AlpsPS/2 ALPS GlidePoint" (type: TOUCHPAD)
(--) AlpsPS/2 ALPS GlidePoint touchpad found
(II) config/hal: Adding input device Video Bus
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.1
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event8"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Video Bus: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) Video Bus: xkb_model: "evdev"
(**) Option "xkb_layout" "br"
(**) Video Bus: xkb_layout: "br"
(**) Option "xkb_variant" "abnt2"
(**) Video Bus: xkb_variant: "abnt2"
(II) config/hal: Adding input device PS/2 Mouse
(**) PS/2 Mouse: always reports core events
(**) PS/2 Mouse: Device: "/dev/input/event7"
(II) PS/2 Mouse: Found 3 mouse buttons
(II) PS/2 Mouse: Found x and y relative axes
(II) PS/2 Mouse: Configuring as mouse
(**) PS/2 Mouse: YAxisMapping: buttons 4 and 5
(**) PS/2 Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
(II) config/hal: Adding input device Microsoft Microsoft Trackball Optical?
(**) Microsoft Microsoft Trackball Optical?: always reports core events
(**) Microsoft Microsoft Trackball Optical?: Device: "/dev/input/event5"
(II) Microsoft Microsoft Trackball Optical?: Found 5 mouse buttons
(II) Microsoft Microsoft Trackball Optical?: Found x and y relative axes
(II) Microsoft Microsoft Trackball Optical?: Configuring as mouse
(**) Microsoft Microsoft Trackball Optical?: YAxisMapping: buttons 4 and 5
(**) Microsoft Microsoft Trackball Optical?: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Microsoft Trackball Optical?" (type: MOUSE)
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event11"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Video Bus: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) Video Bus: xkb_model: "evdev"
(**) Option "xkb_layout" "br"
(**) Video Bus: xkb_layout: "br"
(**) Option "xkb_variant" "abnt2"
(**) Video Bus: xkb_variant: "abnt2"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event10"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Video Bus: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) Video Bus: xkb_model: "evdev"
(**) Option "xkb_layout" "br"
(**) Video Bus: xkb_layout: "br"
(**) Option "xkb_variant" "abnt2"
(**) Video Bus: xkb_variant: "abnt2"
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "evdev"
(**) AT Translated Set 2 keyboard: xkb_model: "evdev"
(**) Option "xkb_layout" "br"
(**) AT Translated Set 2 keyboard: xkb_layout: "br"
(**) Option "xkb_variant" "abnt2"
(**) AT Translated Set 2 keyboard: xkb_variant: "abnt2"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
AUDIT: Thu Dec 25 02:18:51 2008: 11649 Xorg: client 5 rejected from local host ( uid=1000 gid=1000 pid=11673 )
AUDIT: Thu Dec 25 02:18:51 2008: 11649 Xorg: client 5 rejected from local host ( uid=1000 gid=1000 pid=11674 )
AUDIT: Thu Dec 25 02:18:51 2008: 11649 Xorg: client 5 rejected from local host ( uid=1000 gid=1000 pid=11675 )
(EE) intel(0): underrun on pipe B!
xorg.conf
Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
Load "freetype"
Load "GLcore"
Load "glx"
Load "dri"
Load "int10"
Load "vbe"
EndSection
Section "Device"
Identifier "Intel GMA X3100"
Driver "intel"
BusID "PCI:0:2:0"
Option "DRI" "True"
Option "NoDDC" "True"
Option "AccelMethod" "exa"
Option "MigrationHeuristic" "greedy"
Option "ExaNoComposite" "false"
Screen 0
EndSection
Section "Monitor"
Identifier "Failsafe Monitor"
Vendorname "Generic LCD Display"
Modelname "LCD Panel 1280x800"
Horizsync 31.5-50.0
Vertrefresh 56.0 - 65.0
modeline "1280x800@60" 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync
DisplaySize 336 210 # 96 DPI @ 1280x800
Gamma 1.0
EndSection
#Section "Monitor"
# Identifier "Monitor externo"
# Vendorname "Samsung"
# Modelname "917p"
# Horizsync 31.5-50.0
# Vertrefresh 56.0 - 65.0
# modeline "1280x1024@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
# DisplaySize 339 271 # 96 DPI @ 1280x1024
# Gamma 1.0
#EndSection
Section "Screen"
Identifier "Default Screen"
Device "Failsafe Device"
Monitor "Failsafe Monitor"
Defaultdepth 24
SubSection "Display"
Depth 24
Modes "1280x800@60"
#Modes "1280x1024@60"
Virtual 2560 2048
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
Option "DAMAGE" "Enable"
Option "XFIXES" "Enable"
EndSection

ichbinesderelch wrote:have you tried using xrandr? xrandr -q shows available outputs, xrandr --output outputadapter(like VGA) --mode 1280x1024, as far as i can see, virtual monitor is set high enough that this should kinda work!
Yes, I tried xrandr:
$ xrandr --newmode "1280x1024" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
$ xrandr --addmode VGA 1280x1024
$ xrandr --output VGA --mode 1280x1024
$ xrandr --output VGA --right-of LVDS
At first this didn't work at all, so I tried to mess with screen resolution applet and got output on the second monitor, but not at the desired resolution.
I tried running these commands again and got output on the second monitor, but at the wrong resolution. The strange part is that the resolution I want is listed by xrandr:
$ xrandr -q
Screen 0: minimum 320 x 200, current 2304 x 800, maximum 2560 x 2048
VGA connected 1024x768+1280+0 (normal left inverted right x axis y axis) 0mm x 0mm
1280x800@60 60.0 +
1360x768 59.8
1024x768 60.0*
800x600 60.3 56.2
640x480 59.9
1280x1024 60.0
LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1280x800 60.0*+
1024x768 85.0 75.0 70.1 60.0
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
TV disconnected (normal left inverted right x axis y axis)

No zoom level controls on second monitor!

Similar Messages

Maybe you are looking for