Native Monitor DPI?

I just got the Apple 30" display and can't seem to find the native dpi of the monitor. I'm not talking about the resolution.
I"m fairly new to Mac and my old monitors running in Windows was at 96 dpi. I'm trying to find out so I can set Photoshop up to view the right actual size. Perhaps the question should be what does OSX run in? I'm not sure, but would like to know the answer.
Any help would be greatly appreciated.
Dan

The specs <http://www.apple.com/ca/displays/specs.html> show Pixel pitch 0.250 mm
which is 101.6 dpi
Calculating from the 29.7" viewable screen size and number of pixels gives 101.6456 dpi

Similar Messages

Laptop: native monitor vs. external monitor

These days I usually switch on the laptop (an Asus Zenbook) when it is already plugged in to an external monitor. This causes the external monitor to be the *only* one to display anything -- which is fine most of the time, because that's precisely what I want. The problem is that, on the very few occasions when I need to revert back to the laptop's native monitor, I simply cannot make it display anything whatsoever -- unless I reboot the machine with the external monitor unplugged.
I've tried all the xrandr variations I could think (and google) of, and nada. Also, if I try doing it on KDE's System Settings, the resolution of the external monitor will change, but the native monitor will still be blank; and if I click "Identify Outputs", the identifiers for both monitors will be shown on the external one!! (albeit on slightly different locations). Here's the output of xrandr (external mon. plugged in, native disabled):
$ xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
eDP1 connected (normal left inverted right x axis y axis)
1920x1080 60.00 + 40.00
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
VGA1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 428mm x 255mm
1440x900 59.89*+ 74.98
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.08 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 60.00
720x400 70.08
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
Help?

ewaller wrote:Perhaps you should share some of the xrandr incantations you have tried and post the full output of those commands.
Perhaps I should have in my original question, but the point is now moot, for after more googling, I found these two bugs that I had missed yesterday:
https://bugzilla.redhat.com/show_bug.cgi?id=844985
https://bugs.freedesktop.org/show_bug.cgi?id=48652
Short version: it's an upstream problem...

Cant Achieve Native Monitor Resolution

I have an HP Elite H8-1240t with Intel HD Graphics and a 23" HPW2371d monitor with native resolution of 1920x1080. This monitor shipped with a VGA cable and adapter and it is plugged into a DVI port on desktop. I can only run the resolution at 1024x768. If I choose 1920x1080 it doesn't fit to screen. Can someone please explain what needs done to correct this.

If you are showing a "non-plug and play" monitor in the Windows device manger, I would guess is a problem with the "DDC-EDID" communictaion link between the computer and the monitor. Either the monitor isn't reporting, the computer isn't reading, or the link (cable) is damaged. If you have another monitor and/or computer and/or VGA cable, try swapping them around to determine where the issue is.
Examples...
1) HP Elite H8-1240t with different monitor
2) HP W2371d monitor with different computer
3) Repeat 1 or 2 with a different VGA cable
4) Try a different DVI-to-VGA dongle adapter with the HP Elite H8-1240t and HP W2371d monitor
5) Try a different VGA cable with the HP Elite H8-1240t and HP W2371d monitor
6) Try a different DVI-to-VGA dongle adapter and a different VGA cable with the HP Elite H8-1240t and HP W2371d monitor
If you can't identify the issue from the steps above, you may wish to manually set the Windows resolution to 1920 x 1080 and set the refresh rate to 59 or 60 Hz.
Please send KUDOs
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

Will macbook pro output video to a 1280x1024 native monitor well?

My standard resolution monitor is bigger than the laptop display but has a different native resolution. Will the operating system still look good?

Your MBP will support the native resolution of your monitor, and the monitor will look as good as it ever has, but that setup is less than ideal for the following reasons:
Using the monitor in Mirrored mode will reduce the resolution of your Mac's built-in display, making that look lousy, and the difference in aspect ratio between the two displays will cause one or the other of them to be distorted. You really won't want to do this.
Using the monitor in Extended Desktop mode will allow each display to be set independently and to operate at its native resolution, but because the pixels in the external display are bigger than those in the MBP display, its image will appear less detailed in a side-by-side comparison. You may find that when you shift your eyes from the MBP screen to the external, your eyes involuntarily strain to discern details that are equivalent in size to the smallest details visble on the MBP screen: details that the external simply can't render with its coarse pixel grid. This could be very tiring for your eyes.
Using the monitor in closed-clamshell mode (with the built-in display closed) would allow the external to be used at its native resolution and would eliminate the mismatched levels of detail seen side-by-side in Extended Desktop mode, but of course you'd be working with fewer pixels than the built-in display provides by itself.
A much more optimal two-screen setup is one in which the external display has a higher resolution than the built-in screen, and the physical pixel sizes of the two displays are similar.

Multiple monitor DPI Issues (Desktop not Metro)

Hi,
I have a Lenovo Yoga 2 pro with Win 8.1, which has an ultra high resolution (3,200X1,800) and I am using it with a Targus docking station. In order to see things, I have the custom DPI scaling set at 250%. Here is the problem, when i use the docking
station with an external monitor that has a maximum of 1900X1200, Metro looks nice, but anything on the desktop (office and other desktop only programs), everything is HUGE and unusable. If I try to set DPI scaling for multiple monitors, I can no longer
use my custom 250% DPI for the Lenovo, instead, I am given a slider that makes the external monitor look nice, but when the laptop is removed, it is so small that I'd need a magnifying glass to see. If I want to use a docking station, I have to change
the DPI scaling every time I switch between being docked and as a standalone, which requires me to go through all of the steps to switch and then log out and log back in. Is there a way to have custom DPIs for each monitor? I think this will only
become a bigger problem as more companies develop higher resolution devices.
Thanks,
Dean

Same issue here. I have looked on a lot of forums, and there are a lot of people who just don't understand the issue - offering completely irrelevant advice!
As with a number of others on this thread, I have a Surface Pro 3... fantastic machine, and beautiful display. But connect my external 1080x1920 24" display, and everything is too large on the external... so as with everyone else, I have to set the
Change the size of all items option in display settings, set it to the smallest value, then log out, and log back in. That fixes the external display, but...
Having to make this setting change every time I connect or disconnect to an external monitor is annoying enough... but having to log out, and then log back in to see the change is ridiculous!
But what REALLY annoys me is that I like to use extended display mode - I love to work with two monitors - my lapyop and external display side by side. With the scaling set to lowest, so that the external display looks correct, the Surface Pro 3 screen is
just unusable - its too small, and gives me a headache trying to use it. It makes me feel like an old man complaining that "owwww its too small for my old eyes!".
I realise that this is a Windows issue - but heck, if the Surface Pro 3 is really the tablet to replace my laptop, this flaw in Windows makes the SP3 a NON laptop replacement. Using dual monitor setups with my portable is essential to how I work.
I almost can't believe that in 2014 Windows still does not have proper per monitor PPI settings. Technology has landed a probe on a bloody comet for crying out loud - why can't Windows have proper UI scaling per monitor??!!
What really scares me is that I dont think this is a simple fix for MS, and it may be some time before we see this resolved... but here's hoping Microsoft are already working on s solution.
I'd like to see a Microsoft representative give us an official update on this issue... Hello? Are you out there?

High PPI Support Multiple Monitors: How it comes that Remote Desktop implements the hight PPI support very well and win 8.1 doesnt?

http://skovalev.de/wp-content/uploads/2014/05/RemoteDesktop-HighPPI-Perfect.png
Hello all: i am using an High PPI Monitors from Dell XPS15 (3600x1800) and a Normal FullHD above it. The FullHD monitor is an external device and is set up as the primary device. Scaling is set to per Monitor DPI.
Now the Question: how it comes, that my RemoteDesktop on the secondary (internal) screen has almost perfect implementation for this????
BUT i am am talking only about the RemoteDekstopManager, normal one does not works with high ppi in this way... Also ModernUI has no problems with scaling
http://skovalev.de/wp-content/uploads/2014/05/Firfox-and-Resolution-RemoteDesktop.png
NOTE that the resolution on the remote desktop is set to 1600x900 and there are NO scaling problems even on the 3200x1800 monitor!
On both picutures you find the dell monitor on the bottom and the scaled original windows explorer/firefox on the bottom right. See how blurry it is? I really breaks my eyes :(
I hope Microsoft can finally fix the high PPI Monitors issue, since the solutions seems to be already implemented

No, i mean the Scaling Support.
If you use multiple monitor, in windows 8.1 you can scale per monitor. If you use this option with a High PPI monitor, like ultra HD or 4K, the image on the monitors with other PPI than the main monitors appears fuzzy and blury.
But there are also scaling problems even if you use only single monitor. This article blog describes it pretty good:
http://www.hanselman.com/blog/LivingAHighDPIDesktopLifestyleCanBePainful.aspx
By the way there are lot article like this describing the scaling problems, not only by users but also by professinals and IT magazines...
BUT here it comes: watch @ my screenshots. If the remote desktops resolution is 1800x900 and the native resolution is 3600x1800, there are no scaling problems! HOW? So like you can see on my screenshots a native application on my monitor appears fuzzy while
the same application runnin of the remote desktop has clear type!
That means for me, that windows HAS the possibility to scale clearly, but somehow this feature is only supported by RDCM...

J2SE Adapter Monitoring

Hi
Is there any way of activating native monitoring from within the J2SE Adapter engine? How do we monitor errors on the J2SE Adapter engine automatically?
Can it notify us automatically if an error occurs?
Thanks!

Hi Riaz,
>>>I would like specific alerts based on the type of error on the adapter to be sent to recipients in a mail distribution list for instance.
You can call SALERT_CREATE RFC from the Java adapter module and raise alerts based on the error.
Refer:
/people/amol.joshi2/blog/2006/11/27/alerts-from-adapter-modules--the-jra-way
Regards,
Aravind

Unable to use external display native resolution

Dear all,
Here is the current setup I'm using :
MacbookPro 15", hi res, Mid 2010 with Mac OS 10.6.6, software up-to-date
Apple MiniDisplayPort to VGA Adapter Firmware 1.03
IIYAMA Prolite E2607WSD, a 26" monitor with native resolution of 1920x1200 @ 60Hz
When connecting the MiniDisplayPort to VGA adapter to the VGA cable, the MBP doesn't enable me to set the external native monitor resolution of 1920x1200 with extended desktop. The maximum available resolution the macbookpro is able to diaply is 1920x1080.
What I tried :
-using high performance graphics in the energy saver settings
-using clamshell mode
-using mirroring mode
-reset PRAM
-reset SCM
-delete com.windowserver.plist
-use SwitchResX.app and DisplayConfigX.app to force the native resolution
To make sure that the monitor was correctly behaving, I tried with a PC with WinXP, and I was able to get max resolution of 1920x1200 without an issue. I also tried with a Macbook 2008 with 10.5.6, and with it's own DisplayPort to VGA adapter (the "normal size" one, not the "mini" one I'm using with the MBP), and it worked as well with the native resolution of 1920x1200.
I 'm coming to the conclusion that either the minidisplayport to vga adapter doesn't accept any resolution higher than 1920x1080 or that the one I bought from Apple is not properly working, or that I should use the minidisplay port to DVI adapter (no HDMI here as an input for the monitor)...
I also browsed the forum and found a lot of similar issues, so I guess it's pretty common, but no workaround seems possible.
Does anybody in the community had the same issue and know how to solve it ?
Thanks in advance.
PolCls

Hello BSteely,
I actually tried to get the EDID information and to replicate them as much as possible but everytime I tried a custom resolution, after reboot, SRX will say " the system didn't accept this setup"... and the proper resolution is not available..
See below the data :
DDC block report generated by SwitchResX version 4.2 for display
PLE2607WSD
------------------- RAW DATA ------------------------
0 1 2 3 4 5 6 7 8 9 A B C D E F
0 | 00 FF FF FF FF FF FF 00 26 CD 03 66 21 02 00 00
1 | 0C 14 01 03 68 37 22 78 2A 7B 65 A5 55 48 99 26
2 | 12 50 54 BD EF 80 71 4F 81 80 81 8F 95 00 95 0F
3 | A9 40 B3 00 D1 C0 7D 4B 80 A0 72 B0 2D 40 88 C8
4 | 36 00 26 58 21 00 00 1C 00 00 00 FF 00 31 31 30
5 | 35 36 30 31 32 30 30 35 34 35 00 00 00 FD 00 37
6 | 4C 1D 51 14 00 0A 20 20 20 20 20 20 00 00 00 FC
7 | 00 50 4C 45 32 36 30 37 57 53 44 0A 20 20 00 11
< 00FFFFFF FFFFFF00 26CD0366 21020000 0C140103 68372278 2A7B65A5 55489926 125054BD EF80714F 8180818F 9500950F A940B300 D1C07D4B 80A072B0 2D4088C8 36002658 2100001C 000000FF 00313130 35363031 32303035 34350000 00FD0037 4C1D5114 000A2020 20202020 000000FC 00504C45 32363037 5753440A 20200011 >
{ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x26, 0xCD, 0x03, 0x66, 0x21, 0x02, 0x00, 0x00, 0x0C, 0x14, 0x01, 0x03, 0x68, 0x37, 0x22, 0x78, 0x2A, 0x7B, 0x65, 0xA5, 0x55, 0x48, 0x99, 0x26, 0x12, 0x50, 0x54, 0xBD, 0xEF, 0x80, 0x71, 0x4F, 0x81, 0x80, 0x81, 0x8F, 0x95, 0x00, 0x95, 0x0F, 0xA9, 0x40, 0xB3, 0x00, 0xD1, 0xC0, 0x7D, 0x4B, 0x80, 0xA0, 0x72, 0xB0, 0x2D, 0x40, 0x88, 0xC8, 0x36, 0x00, 0x26, 0x58, 0x21, 0x00, 0x00, 0x1C, 0x00, 0x00, 0x00, 0xFF, 0x00, 0x31, 0x31, 0x30, 0x35, 0x36, 0x30, 0x31, 0x32, 0x30, 0x30, 0x35, 0x34, 0x35, 0x00, 0x00, 0x00, 0xFD, 0x00, 0x37, 0x4C, 0x1D, 0x51, 0x14, 0x00, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x50, 0x4C, 0x45, 0x32, 0x36, 0x30, 0x37, 0x57, 0x53, 0x44, 0x0A, 0x20, 0x20, 0x00, 0x11, }
Valid EDID block: checksum passed
------------------- MAIN EDID BLOCK -----------------
EDID Version........1.3
Manufacturer........IVM
Product Code........870 (0366) (6603)
Serial Number.......00000221
Manufactured........Week 12 of year 2010
Max H Size..........55 cm
Max V Size..........34 cm
Gamma...............2,20
Display Supported Features:
Power Management: Active off
Display type:
RGB color display
Display is non continuous frequency
Default color space is not sRGB standard
Preferred timing mode includes Native Pixel Format
Input signal & sync:
Analog input with: 0.700V / 0.000V
Composite Sync
Color info:
Red x = 0,646 Green x = 0,283 Blue x = 0,149 White x = 0,313
Red y = 0,335 Green y = 0,601 Blue y = 0,072 White y = 0,329
Established Timings:
720 x 400 @ 70Hz
640 x 480 @ 60Hz
640 x 480 @ 67Hz
640 x 480 @ 72Hz
640 x 480 @ 75Hz
800 x 600 @ 60Hz
800 x 600 @ 72Hz
800 x 600 @ 75Hz
832 x 624 @ 75Hz
1024 x 768 @ 60Hz
1024 x 768 @ 70Hz
1024 x 768 @ 75Hz
1280 x 1024 @ 75Hz
Manufacturer Reserved Timings:
1152 x 870 @ 75Hz
Standard Timing Identification:
#0: 1152 x 864 @ 75Hz (714F)
#1: 1280 x 1024 @ 60Hz (8180)
#2: 1280 x 1024 @ 75Hz (818F)
#3: 1440 x 900 @ 60Hz (9500)
#4: 1440 x 900 @ 75Hz (950F)
#5: 1600 x 1200 @ 60Hz (A940)
#6: 1680 x 1050 @ 60Hz (B300)
#7: 1920 x 1080 @ 60Hz (D1C0)
Monitor Description blocks:
Descriptor #0 - Timing definition:
Mode = 1920 x 1200 @ 59,885Hz
Pixel Clock............. 193,25 MHz Non-Interlaced
Horizontal Vertical
Active.................. 1920 pixels 1200 lines
Front Porch............. 136 pixels 3 lines
Sync Width.............. 200 pixels 6 lines
Back Porch.............. 336 pixels 36 lines
Blanking................ 672 pixels 45 lines
Total................... 2592 pixels 1245 lines
Scan Rate............... 74,556 kHz 59,885 Hz
Image Size.............. 550 mm 344 mm
Border.................. 0 pixels 0 lines
Sync: Digital separate with
* Positive vertical polarity
* Negative horizontal polarity
Descriptor #1 - Serial number:
1105601200545
Descriptor #2 - Monitor limits:
Horizontal frequency range.......29-81 kHz
Vertical frequency range.........55-76 Hz
Maximum bandwidth unspecified
Descriptor #3 - Monitor name:
PLE2607WSD
What do you think are the parameters I should use ?
Thanks in advance;
Paul

Dell Latitude E6400 won't recognize 1600-900 dpi settings.

Just bought a new HP W2071d 20" monitor and installed the driver on my Dell E6400 laptop. Then, when restarting the monitor shows 1280 X 768 as the recommended resolution and will not let you set it higher. Do I have a defective monitor? Why isn't the driver allowing the higher native monitor resolution?
I have tried just about everything including downloading and installing the newest Windows 7 drivers from HP.

The Laptop won't recognize the native resolution of the monitor no matter if I remove the HP furnished drivers or not. I'm going to attach the monitor to my desktop and see what happens. If the desktop recognizes the monitor and will allow 1600X900 resolution (It's a 1 year old Gateway desktop) then I will suspect some Dell issues. If it won't recognize the 1600X900 resolution I will think the monitor is faulty. The Dell detects the monitor but, again, won't allow the resolution it should.

Specific pixel size & dpi

Is it possible to set specific a combination of size (in pxls) and dpi? (in Illustrator CS5)
I need to create a .png document which is 16x16 px and 96dpi. The ability to chose the dpi size when setting up a new doc is very limited.
The only thing I've managed to do is create a 19x19 px 72dpi image, export it "for web" and then take it into photoshop and change the dpi to 96.
Is there a better, easier way? Also, we're considering upgrading to CS6 - are these features better in CS6?

Bidds, you are confusing DPI (Dots Per Inch) with PPI (Pixels Per Inch).
DPI is a technical specification of the output or input of hardware devices like a printer when you print, monitor when you display your digital image, scanner when you scan to make digital images, and etc. For printers DPI specifies the size of the ink drops when printing. For monitors, DPI specifies the monitor's resolution or in other words the size of the monitor's pixels. The term DPI for monitors came from the use of the CRT displays (those heavy monitors and TVs in the past with big tubes) which are no longer in production. These displays used guns to shoot light at the back of the screen with variable size dots and the term DPI perfectly described the monitor resolution used. Today there is only LCD displays on the market and thy use fixed cells which define the monitor resolution. Because the cells are fixed, for describing the resolution of LCD monitors, people mostly use the term Pixels Per Inch when they want to describe the size of monitors' pixels (cells). And this can cause some confusion that you are experiencing.
PPI is an attribute of a digital raster image. It specifies the output resolution of a raster image or in other words how large the pixels in the digital file will be output.
In Photoshop you are setting PPI not DPI.
Illustrator is a vector program. Vector graphics are resolution independent (have no pixels) and don't have PPI attributes. The PPI attributes are valid only when creating a raster image for outputting to devices like printers. Printers can print the pixels of your digital image with different size, and thus the image with the same number of pixels can be printed with different sizes. Monitors however don't use PPI settings of digital files to display images, instead they use the zoom level specified by the user using software, and by default the software programs (your browser for example) use 100% zoom which fits one image pixel to one monitor pixel. Because different monitors have monitor pixels (cells) with different sizes that cannot be changed on LCD screens, a digital image with the same number of pixels will be displayed at different size at the default 100% zoom on different monitors. Also have in mind that certain elements like software interfaces cannot be zoomed (changed) by the user.
So, the DPI mentioned in the link you provided does not mean PPI and it doesn't suggest in anyway that you should set PPI in Photoshop or any other program when creating images for the web. You got that wrong. It is only telling you that monitors with higher resolution (DPI) will display your image smaller so, you may want to make the image larger (with more pixels) and vice versa. The PPI settings in a raster image are simply ignored for display on monitors and thus on the web. That's why you don't have an option for PPI in Save for Web and devices. Whether an image with a certain number of pixels is 72, 96, 300, 1 million or 1 PPI (pixels per inch) this will not make any difference when displayed on the web.

RAW converter dpi

Our Olympus E-500 writes images in RAW files (.orf) at 314 dpi. The Olympus software opens the .orf files at 314 dpi but Photoshop Elements RAW converter opens the files at 240 dpi.
How do we open the RAW .orf files at it's native 314 dpi??
We have the current version of the RAW converter.
PSE 5.02
Win XP
thank you

There is no "native" resolution. The pixel count is what matters. The DPI setting just tells the software how to print it and is, otherwise, and arbitrary number.
I'm not sure that you can set this number in Camera Raw when hosted by Photoshop Elements. The interface is slightly different and I only see 8/16-bit depth as an option. 240 dpi might be the default (and only) option in Elements.
However,you can change it at any time in Photoshop by going to Image>resize>Image Size and unchecking the "resample image" box and typing in a new number.
John

T410 + Ubuntu Lucid: Two Weeks of Use (the Good, the Bad, the Ugly)

System
Lenovo ThinkPad T410 laptop, Integrated Intel Graphics, Intel Centrino Advanced-N 6200 wireless.
Fixed
Resume did not work after second suspend. Fixed by updating BIOS. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/532374
Font antialiasing misconfiguration that made small fonts look bad; had to edit ~/.fonts.conf manually to defeat the system preventing antialiasing at small font sizes. Screen is small (14") but has very high resolution (1440x900), so this seems to work ok here.
Evolution doesn't autocomplete the email addresses of people you communicate with regularly. Fixed: turn on automatic contacts and autocomplete.
Printer config didn't work til I changed system-config-printer to not use the Python on the user path: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/328657
Emacs copy/cut (meta-W, ctrl-W) doesn't put the text being operated on into the X clipboard. Likewise, putting something into the X clipboard doesn't make it possible to paste it into Emacs via ctrl-Y. Fixed via:
(global-set-key "\C-w" 'clipboard-kill-region)
(global-set-key "\M-w" 'clipboard-kill-ring-save)
(global-set-key "\C-y" 'clipboard-yank)
See also http://www.emacswiki.org/emacs/CopyAndPaste#toc2
Toggle state of hardware mute button and software mute button not synchronized. If you hit the hardware mute button, it lights. If you subsequently unmute via software, the sound is umuted, but the hardware mute button remains lit. Pressing the lit hardware mute button in that state will result in the hardware mute button becoming unlit but the sound muted. Seems to have gotten fixed in upgrade to 2.6.34-999-generic kernel while trying to fix USB resume issue.
USB broken after resume: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/566149 . (Installed http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-05-06-lucid/ aka kernel version 2.6.34-999-generic as per the instructions in https://wiki.ubuntu.com/KernelTeam/MainlineBuilds while waiting for "official" kernel update from Ubuntu).
Outstanding
Sometimes Bluetooth icon in indicator applet shows a red X next to it, sometimes it doesn't. I haven't bothered with Bluetooth yet, so I don't know why it's changing state.
Sometimes audio mute button stops working. What's in syslog: keyboard.c: can't emulate rawmode for keycode 240 for each button press. Not sure why it works sometimes and not others.
HDMI audio probably busted with installation of http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-05-06-lucid/ to fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/5661492. KDE came up and warned me the device had disappeared when I rebooted with the new kernel.
Complete system lockups at various points (maybe once every couple days) requiring a hard power reset. I haven't been able to distinguish a pattern yet. Might be related to the wireless errors below; someone else claimed that a similar wireless card got hot enough under Linux to cause disconnects and weird system behavior. I haven't seen crazy temperatures yet though.
Wireless network card (Intel Centrino Advanced-N 6200, using the iwlagn driver) freaks out every 20 minutes or so and "restarts" (whatever that means). Seems to be a firmware problem. Symptom: Microcode SW error detected. Restarting 0x2000000. in syslog. sudo iwconfig wlan0 power off doesn't fix it, upgrade to 2.6.34.99 kernel didn't fix it, can't seem to find any newer firmware to try than what's in http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.193.4.1.tgz. Reported bug at http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2205 as per http://www.intellinuxwireless.org/?n=fw_error_report
Some potentially related Ubuntu info: http://ubuntuforums.org/archive/index.php/t-1142917.html
WTF in syslog, every so often: wpa_supplicant[1196]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys plus about 10 other lines of gibberish. Probably related to the microcode problem above, no use trying to figure it out until that gets fixed. See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992
At boot time, xdpyinfo | grep resolution still reports wrong DPI (reported: 96x96; actual: 120x120) and screen size (reported: 381x238mm; actual: 300x190mm) even after generating an xorg.conf and adding a DisplaySize 300 190 to the single Section "Monitor" in the config. This doesn't seem to be harming anything, but I don't know really what uses this info. Using xrandr -dpi 120 fixes the resolution and screen size reported by xdpyinfo.
Firefox is a problem child for display at 120DPI (native screen DPI); some fonts are huge or tiny when they shouldn't be. Setting the layout.css.dpi in about:config to 120 seems to have no effect. This makes Firefox unusable for me on this system. Thankfully, Google Chrome doesn't have the same problem.
Fingerprint reader unsupported.
When bringing up a backgrounded Emacs window, sometimes Emacs refuses to give me control of the point in that window until I sacrifice the chicken of selecting any item from that window's menu bar.
Emacs acts upon first click of any frame; clicking in a background emacs window reposititions the point in that window. I tried to fix this by adding (setq x-mouse-click-focus-ignore-position t) to my .emacs file as per http://www.gnu.org/software/emacs/manual/html_node/emacs/Mouse-Commands.html. This actually solved the problem: the first click of a window no longer repositioned the point. Unfortunately, contrary to the docs and contrary to the experience of somebody else in #emacs on freenode IRC, this setting also makes the mouse useless for selecting text, moving the point, or scrolling the window text in emacs. It just won't do any of those things for me anymore when this option is set. I can't even shift click on a window to set the font size. This symptom is worse than the problem I was trying to solve by doing it, so I left it off.
Audio CD burning doesn't work from Rhythmbox: https://bugs.launchpad.net/ubuntu/lucid/+source/brasero/+bug/543892
Pulse Audio advertises airport express send capability; it doesn't actually work (very choppy playback, unlistenable). http://pulseaudio.org/ticket/495#comment:23
Opening Rhythmbox from the applications menu doesn't actually open the main window, it just creates a toolbar icon. You then need to know enough to go click on "Show Rhythmbox" in the toolbar icon dropdown.
Konversation: sometimes the mouse pointer "disappears" while hovering over the nick list and the channel list. Only fixed by a restart of Konversation (closing the window and restoring it from the system tray doesn't help).
Cut and paste is, as always, horrific. You need to use Shift-Ctrl-C in the Gnome terminal vs. Ctrl-C in other Gnome apps; Emacs meta-W doesn't put things onto the X clipboard by default, etc. I really don't understand why you can't remap cut copy and paste under Gnome. If you could remap the Gnome keybindings for cut, paste, copy, etc, I'd bind copy to Windowskey-C, paste to Windowskey-V, cut to Windowskey-X, and Undo to Windowskey-Z. Then at least for all Gnome apps that followed the system keybindings, most of the pain would disappear, because the cutnpaste shortcuts wouldn't step on alternate meanings.
Still doesn't look quite as nice as the Mac does, dispite newer and better video and display hardware, no matter how many hours I spend messing around with display settings, font settings, etc.

Not sure how you figure it's an "advanced router" problem. I'd be happy to buy a different router, but I'd need to be told which one to buy. The router I'm connecting to is a barebones Linksys WRT54G (the blue and black one with the two antennas that you see everywhere). These routers are maybe the most common router on the planet, AFAICT.
I have also seen Compiz lockups, but I didn't mention those in the above; the lockups I'm seeing are true system lockups. The system stops responding to any input on network, so it cannot even be restarted remotely.

Black screen on startx with ati radeon HD4330 Mobility and fglrx

Hi,
I managed to install Archlinux on my HP Butterfly laptop that's great !
However I am not able to get X running properly.
lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
01:00.0 VGA compatible controller: ATI Technologies Inc M92 LP [Mobility Radeon HD 4300 Series]
Firstly I tried to use the xf86-video-ati open source driver but it made my kernel crash during the module init.
So I am now trying fglrx, and at least my kernel is unharmed.
But all I get is a black screen after running startx.
Here is my X log :
[ 95.354]
X.Org X Server 1.9.2
Release Date: 2010-10-30
[ 95.354] X Protocol Version 11, Revision 0
[ 95.354] Build Operating System: Linux 2.6.35-ARCH i686
[ 95.354] Current Operating System: Linux myhost 2.6.36-ARCH #1 SMP PREEMPT Mon Jan 24 18:34:55 UTC 2011 i686
[ 95.355] Kernel command line: root=/dev/sda7 ro nomodeset
[ 95.355] Build Date: 01 November 2010 10:35:30PM
[ 95.355]
[ 95.362] Current version of pixman: 0.20.2
[ 95.363] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 95.363] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 95.364] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 9 20:52:31 2011
[ 95.397] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 95.408] (==) ServerLayout "aticonfig Layout"
[ 95.408] (**) |-->Screen "base-screen" (0)
[ 95.408] (**) | |-->Monitor "native-monitor"
[ 95.408] (**) | |-->Device "radeon-4330HD"
[ 95.408] (==) Automatically adding devices
[ 95.408] (==) Automatically enabling devices
[ 95.467] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 95.467] Entry deleted from font path.
[ 95.467] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 95.467] Entry deleted from font path.
[ 95.489] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 95.489] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 95.489] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 95.489] (II) Loader magic: 0x81f1f80
[ 95.489] (II) Module ABI versions:
[ 95.490] X.Org ANSI C Emulation: 0.4
[ 95.490] X.Org Video Driver: 8.0
[ 95.490] X.Org XInput driver : 11.0
[ 95.490] X.Org Server Extension : 4.0
[ 95.491] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0281 rev 7, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00004110/8
[ 95.491] (--) PCI: (0:1:0:0) 1002:9552:1025:0281 rev 0, Mem @ 0xd0000000/268435456, 0xf4400000/65536, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
[ 95.491] (II) Open ACPI successful (/var/run/acpid.socket)
[ 95.491] (II) "extmod" will be loaded by default.
[ 95.491] (II) "dbe" will be loaded by default.
[ 95.491] (II) "glx" will be loaded by default.
[ 95.491] (II) "record" will be loaded by default.
[ 95.492] (II) "dri" will be loaded by default.
[ 95.492] (II) "dri2" will be loaded by default.
[ 95.492] (II) LoadModule: "extmod"
[ 95.492] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 95.506] (II) Module extmod: vendor="X.Org Foundation"
[ 95.506] compiled for 1.9.2, module version = 1.0.0
[ 95.506] Module class: X.Org Server Extension
[ 95.506] ABI class: X.Org Server Extension, version 4.0
[ 95.506] (II) Loading extension MIT-SCREEN-SAVER
[ 95.506] (II) Loading extension XFree86-VidModeExtension
[ 95.506] (II) Loading extension XFree86-DGA
[ 95.506] (II) Loading extension DPMS
[ 95.506] (II) Loading extension XVideo
[ 95.506] (II) Loading extension XVideo-MotionCompensation
[ 95.506] (II) Loading extension X-Resource
[ 95.506] (II) LoadModule: "dbe"
[ 95.506] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 95.509] (II) Module dbe: vendor="X.Org Foundation"
[ 95.509] compiled for 1.9.2, module version = 1.0.0
[ 95.509] Module class: X.Org Server Extension
[ 95.509] ABI class: X.Org Server Extension, version 4.0
[ 95.509] (II) Loading extension DOUBLE-BUFFER
[ 95.509] (II) LoadModule: "glx"
[ 95.510] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 95.528] (II) Module glx: vendor="FireGL - ATI Technologies Inc."
[ 95.528] compiled for 7.6.0, module version = 1.0.0
[ 95.529] (II) Loading extension GLX
[ 95.529] (II) LoadModule: "record"
[ 95.529] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 95.529] (II) Module record: vendor="X.Org Foundation"
[ 95.529] compiled for 1.9.2, module version = 1.13.0
[ 95.529] Module class: X.Org Server Extension
[ 95.529] ABI class: X.Org Server Extension, version 4.0
[ 95.529] (II) Loading extension RECORD
[ 95.529] (II) LoadModule: "dri"
[ 95.530] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 95.535] (II) Module dri: vendor="X.Org Foundation"
[ 95.535] compiled for 1.9.2, module version = 1.0.0
[ 95.535] ABI class: X.Org Server Extension, version 4.0
[ 95.535] (II) Loading extension XFree86-DRI
[ 95.535] (II) LoadModule: "dri2"
[ 95.535] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 95.536] (II) Module dri2: vendor="X.Org Foundation"
[ 95.536] compiled for 1.9.2, module version = 1.2.0
[ 95.536] ABI class: X.Org Server Extension, version 4.0
[ 95.536] (II) Loading extension DRI2
[ 95.536] (II) LoadModule: "fglrx"
[ 95.536] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 95.719] (II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
[ 95.731] compiled for 1.4.99.906, module version = 8.81.5
[ 95.731] Module class: X.Org Video Driver
[ 95.736] (II) Loading sub module "fglrxdrm"
[ 95.736] (II) LoadModule: "fglrxdrm"
[ 95.736] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 95.765] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
[ 95.765] compiled for 1.4.99.906, module version = 8.81.5
[ 95.765] (II) ATI Proprietary Linux Driver Version Identifier:8.81.5
[ 95.765] (II) ATI Proprietary Linux Driver Release Identifier: 8.812
[ 95.765] (II) ATI Proprietary Linux Driver Build Date: Jan 4 2011 21:30:56
[ 95.765] (--) using VT number 7
[ 95.767] (WW) Falling back to old probe method for fglrx
[ 95.852] (II) Loading PCS database from /etc/ati/amdpcsdb
[ 95.861] (--) Chipset Supported AMD Graphics Processor (0x9552) found
[ 95.862] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 95.862] (II) AMD Video driver is running on a device belonging to a group targeted for this release
[ 95.871] (II) AMD Video driver is signed
[ 95.871] (II) fglrx(0): pEnt->device->identifier=0x8f63678
[ 95.872] (II) fglrx(0): === [xdl_x760_atiddxPreInit] === begin
[ 95.873] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
[ 95.873] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 95.873] (==) fglrx(0): Default visual is TrueColor
[ 95.873] (**) fglrx(0): Option "DPMS" "true"
[ 95.873] (==) fglrx(0): RGB weight 888
[ 95.873] (II) fglrx(0): Using 8 bits per RGB
[ 95.873] (==) fglrx(0): Buffer Tiling is ON
[ 95.874] (II) Loading sub module "fglrxdrm"
[ 95.874] (II) LoadModule: "fglrxdrm"
[ 95.874] (II) Reloading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 95.876] ukiDynamicMajor: found major device number 252
[ 95.876] ukiDynamicMajor: found major device number 252
[ 95.876] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[ 95.876] ukiOpenDevice: node name is /dev/ati/card0
[ 95.876] ukiOpenDevice: open result is 11, (OK)
[ 95.876] ukiOpenByBusid: ukiOpenMinor returns 11
[ 95.876] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[ 95.876] (==) fglrx(0): NoAccel = NO
[ 95.876] (==) fglrx(0): ATI 2D Acceleration Architecture enabled
[ 95.876] (--) fglrx(0): Chipset: "ATI Mobility Radeon HD 4300 Series" (Chipset = 0x9552)
[ 95.876] (--) fglrx(0): (PciSubVendor = 0x1025, PciSubDevice = 0x0281)
[ 95.876] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
[ 95.876] (--) fglrx(0): Linear framebuffer (phys) at 0xd0000000
[ 95.876] (--) fglrx(0): MMIO registers at 0xf4400000
[ 95.876] (--) fglrx(0): I/O port at 0x00003000
[ 95.877] (==) fglrx(0): ROM-BIOS at 0x000c0000
[ 95.889] (II) fglrx(0): AC Adapter is used
[ 96.174] (II) fglrx(0): ATI Video BIOS revision 9 or later detected
[ 96.174] (--) fglrx(0): Video RAM: 524288 kByte, Type: DDR3
[ 96.174] (II) fglrx(0): PCIE card detected
[ 96.174] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
[ 96.174] (WW) fglrx(0): board is an unknown third party board, chipset is supported
[ 96.180] (II) fglrx(0): Using adapter: 1:0.0.
[ 96.224] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf00000000, MCFBSize = 0x20000000)
[ 96.453] (II) fglrx(0): Interrupt handler installed at IRQ 46.
[ 96.453] (II) fglrx(0): RandR 1.2 support is enabled!
[ 96.453] (II) fglrx(0): RandR 1.2 rotation support is enabled!
[ 96.453] (==) fglrx(0): Center Mode is disabled
[ 96.453] (II) Loading sub module "fb"
[ 96.453] (II) LoadModule: "fb"
[ 96.454] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 96.475] (II) Module fb: vendor="X.Org Foundation"
[ 96.475] compiled for 1.9.2, module version = 1.0.0
[ 96.475] ABI class: X.Org ANSI C Emulation, version 0.4
[ 96.475] (II) Loading sub module "ddc"
[ 96.475] (II) LoadModule: "ddc"
[ 96.475] (II) Module "ddc" already built-in
[ 96.725] (II) fglrx(0): Finished Initialize PPLIB!
[ 96.773] (II) fglrx(0): Output LVDS using monitor section native-monitor
[ 96.773] (II) fglrx(0): Output DFP1 has no monitor section
[ 96.773] (II) fglrx(0): Output CRT1 has no monitor section
[ 96.785] (II) Loading sub module "ddc"
[ 96.785] (II) LoadModule: "ddc"
[ 96.786] (II) Module "ddc" already built-in
[ 96.786] (II) fglrx(0): Connected Display0: LVDS
[ 96.786] (II) fglrx(0): Display0: Failed to get EDID information.
[ 96.862] (II) fglrx(0): Cannot get EDID information for LVDS
[ 96.862] (II) fglrx(0): EDID for output LVDS
[ 96.862] (II) fglrx(0): Not using mode "640x350" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "640x400" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "720x400" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "640x480" (unknown reason)
[ 96.880] (II) fglrx(0): Not using mode "640x480" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "640x480" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "640x480" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (unknown reason)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "800x600" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "848x480" (unknown reason)
[ 96.880] (II) fglrx(0): Not using mode "1024x768i" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1024x768" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1024x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1024x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1024x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1024x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1152x864" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x768" (monitor doesn't support reduced blanking)
[ 96.880] (II) fglrx(0): Not using mode "1280x768" (unknown reason)
[ 96.880] (II) fglrx(0): Not using mode "1280x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x800" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x800" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x800" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x800" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x800" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x960" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x960" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x960" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x1024" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x1024" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x1024" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1280x1024" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1360x768" (unknown reason)
[ 96.880] (II) fglrx(0): Not using mode "1360x768" (vrefresh out of range)
[ 96.880] (II) fglrx(0): Not using mode "1400x1050" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1400x1050" (hsync out of range)
[ 96.880] (II) fglrx(0): Not using mode "1400x1050" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1400x1050" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1400x1050" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1440x900" (hsync out of range)
[ 96.881] (II) fglrx(0): Not using mode "1440x900" (hsync out of range)
[ 96.881] (II) fglrx(0): Not using mode "1440x900" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1440x900" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1440x900" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (hsync out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1600x1200" (vrefresh out of range)
[ 96.881] (II) fglrx(0): Not using mode "1680x1050" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1680x1050" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1680x1050" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1680x1050" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1680x1050" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1792x1344" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1792x1344" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1792x1344" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1856x1392" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1856x1392" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1856x1392" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1200" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1200" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1200" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1200" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1200" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1440" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1440" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "1920x1440" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "2560x1600" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "2560x1600" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "2560x1600" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "2560x1600" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Not using mode "2560x1600" (width too large for virtual size)
[ 96.881] (II) fglrx(0): Printing probed modes for output LVDS
[ 96.881] (II) fglrx(0): Modeline "1366x768"x60.0 69.50 1366 1414 1446 1466 768 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "1280x768"x60.0 69.50 1280 1414 1446 1466 768 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "1280x720"x60.0 69.50 1280 1414 1446 1466 720 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "1024x768"x60.0 69.50 1024 1414 1446 1466 768 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "1024x600"x60.0 69.50 1024 1414 1446 1466 600 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "800x600"x60.0 69.50 800 1414 1446 1466 600 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "800x480"x60.0 69.50 800 1414 1446 1466 480 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "720x480"x60.0 69.50 720 1414 1446 1466 480 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): Modeline "640x480"x60.0 69.50 640 1414 1446 1466 480 771 777 790 +hsync +vsync (47.4 kHz)
[ 96.881] (II) fglrx(0): EDID for output DFP1
[ 96.881] (II) fglrx(0): EDID for output CRT1
[ 96.881] (II) fglrx(0): Output LVDS connected
[ 96.881] (II) fglrx(0): Output DFP1 disconnected
[ 96.882] (II) fglrx(0): Output CRT1 disconnected
[ 96.882] (II) fglrx(0): Using exact sizes for initial modes
[ 96.882] (II) fglrx(0): Output LVDS using initial mode 1366x768
[ 96.882] (II) fglrx(0): DPI set to (96, 96)
[ 96.882] (II) fglrx(0): Adapter ATI Mobility Radeon HD 4300 Series has 2 configurable heads and 1 displays connected.
[ 96.882] (==) fglrx(0): PseudoColor visuals disabled
[ 96.882] (II) Loading sub module "ramdac"
[ 96.882] (II) LoadModule: "ramdac"
[ 96.882] (II) Module "ramdac" already built-in
[ 96.882] (==) fglrx(0): NoDRI = NO
[ 96.882] (==) fglrx(0): Capabilities: 0x00000000
[ 96.882] (==) fglrx(0): CapabilitiesEx: 0x00000000
[ 96.882] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
[ 96.882] (==) fglrx(0): UseFastTLS=0
[ 96.882] (==) fglrx(0): BlockSignalsOnLock=1
[ 96.882] (--) Depth 24 pixmap format is 32 bpp
[ 96.882] (II) Loading extension ATIFGLRXDRI
[ 96.882] (II) fglrx(0): doing swlDriScreenInit
[ 96.882] (II) fglrx(0): swlDriScreenInit for fglrx driver
[ 96.882] ukiDynamicMajor: found major device number 252
[ 96.882] ukiDynamicMajor: found major device number 252
[ 96.883] ukiDynamicMajor: found major device number 252
[ 96.883] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[ 96.883] ukiOpenDevice: node name is /dev/ati/card0
[ 96.883] ukiOpenDevice: open result is 12, (OK)
[ 96.883] ukiOpenByBusid: ukiOpenMinor returns 12
[ 96.883] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[ 96.883] (II) fglrx(0): [uki] DRM interface version 1.0
[ 96.883] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:1:0:0"
[ 96.883] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x2000
[ 96.883] (II) fglrx(0): [uki] mapped SAREA 0x2000 to 0xb76f0000
[ 96.883] (II) fglrx(0): [uki] framebuffer handle = 0x3000
[ 96.883] (II) fglrx(0): [uki] added 1 reserved context for kernel
[ 96.883] (II) fglrx(0): swlDriScreenInit done
[ 96.883] (II) fglrx(0): Kernel Module Version Information:
[ 96.883] (II) fglrx(0): Name: fglrx
[ 96.883] (II) fglrx(0): Version: 8.81.5
[ 96.883] (II) fglrx(0): Date: Jan 4 2011
[ 96.883] (II) fglrx(0): Desc: ATI FireGL DRM kernel module
[ 96.883] (II) fglrx(0): Kernel Module version matches driver.
[ 96.883] (II) fglrx(0): Kernel Module Build Time Information:
[ 96.883] (II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.36-ARCH
[ 96.883] (II) fglrx(0): Build-Kernel MODVERSIONS: no
[ 96.883] (II) fglrx(0): Build-Kernel __SMP__: no
[ 96.883] (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
[ 96.883] (II) fglrx(0): [uki] register handle = 0x00004000
[ 96.922] (II) fglrx(0): DRI initialization successfull
[ 96.922] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x01004000
[ 96.933] (==) fglrx(0): Backing store disabled
[ 96.933] (II) Loading extension FGLRXEXTENSION
[ 96.933] (**) fglrx(0): DPMS enabled
[ 96.934] (II) fglrx(0): Initialized in-driver Xinerama extension
[ 96.934] (**) fglrx(0): Textured Video is enabled.
[ 96.934] (II) LoadModule: "glesx"
[ 96.944] (II) Loading /usr/lib/xorg/modules/glesx.so
[ 97.061] (II) Module glesx: vendor="X.Org Foundation"
[ 97.062] compiled for 1.4.99.906, module version = 1.0.0
[ 97.062] (II) Loading extension GLESX
[ 97.062] (II) fglrx(0): GLESX enableFlags = 528
[ 97.062] (II) fglrx(0): GLESX is enabled
[ 97.062] (II) LoadModule: "amdxmm"
[ 97.062] (II) Loading /usr/lib/xorg/modules/amdxmm.so
[ 97.072] (II) Module amdxmm: vendor="X.Org Foundation"
[ 97.072] compiled for 1.4.99.906, module version = 2.0.0
[ 97.072] (II) Loading extension AMDXVOPL
[ 97.072] (II) Loading extension AMDXVBA
[ 97.091] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):
[ 97.094] (II) fglrx(0): Enable composite support successfully
[ 97.094] (WW) fglrx(0): Option "VendorName" is not used
[ 97.094] (WW) fglrx(0): Option "ModelName" is not used
[ 97.094] (II) fglrx(0): X context handle = 0x1
[ 97.094] (II) fglrx(0): [DRI] installation complete
[ 97.094] (==) fglrx(0): Silken mouse enabled
[ 97.101] (==) fglrx(0): Using HW cursor of display infrastructure!
[ 97.101] (II) fglrx(0): Disabling in-server RandR and enabling in-driver RandR 1.2.
[ 97.101] (II) fglrx(0): 'LVDS LCD' ConnectorType, abstracted as 'Panel'
[ 97.101] (II) fglrx(0): 'eDP LCD' ConnectorType, abstracted as 'Panel'
[ 98.234] (--) RandR disabled
[ 98.234] (II) Initializing built-in extension Generic Event Extension
[ 98.234] (II) Initializing built-in extension SHAPE
[ 98.234] (II) Initializing built-in extension MIT-SHM
[ 98.234] (II) Initializing built-in extension XInputExtension
[ 98.234] (II) Initializing built-in extension XTEST
[ 98.234] (II) Initializing built-in extension BIG-REQUESTS
[ 98.234] (II) Initializing built-in extension SYNC
[ 98.234] (II) Initializing built-in extension XKEYBOARD
[ 98.234] (II) Initializing built-in extension XC-MISC
[ 98.234] (II) Initializing built-in extension SECURITY
[ 98.234] (II) Initializing built-in extension XINERAMA
[ 98.234] (II) Initializing built-in extension XFIXES
[ 98.234] (II) Initializing built-in extension RENDER
[ 98.234] (II) Initializing built-in extension RANDR
[ 98.234] (II) Initializing built-in extension COMPOSITE
[ 98.234] (II) Initializing built-in extension DAMAGE
[ 98.240] ukiDynamicMajor: found major device number 252
[ 98.240] ukiDynamicMajor: found major device number 252
[ 98.240] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[ 98.240] ukiOpenDevice: node name is /dev/ati/card0
[ 98.240] ukiOpenDevice: open result is 13, (OK)
[ 98.240] ukiOpenByBusid: ukiOpenMinor returns 13
[ 98.240] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
[ 98.965] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0
[ 99.057] (II) fglrx(0): Enable the clock gating!
[ 99.058] (II) fglrx(0): Setting screen physical size to 361 x 203
[ 99.597] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 99.597] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 99.597] (II) LoadModule: "evdev"
[ 99.611] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 99.622] (II) Module evdev: vendor="X.Org Foundation"
[ 99.622] compiled for 1.9.0, module version = 2.5.0
[ 99.622] Module class: X.Org XInput Driver
[ 99.622] ABI class: X.Org XInput driver, version 11.0
[ 99.622] (**) Power Button: always reports core events
[ 99.622] (**) Power Button: Device: "/dev/input/event5"
[ 99.630] (--) Power Button: Found keys
[ 99.630] (II) Power Button: Configuring as keyboard
[ 99.630] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 99.630] (**) Option "xkb_rules" "evdev"
[ 99.630] (**) Option "xkb_model" "evdev"
[ 99.630] (**) Option "xkb_layout" "us"
[ 99.695] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
[ 99.695] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 99.695] (**) Video Bus: always reports core events
[ 99.695] (**) Video Bus: Device: "/dev/input/event7"
[ 99.703] (--) Video Bus: Found keys
[ 99.703] (II) Video Bus: Configuring as keyboard
[ 99.703] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 99.703] (**) Option "xkb_rules" "evdev"
[ 99.703] (**) Option "xkb_model" "evdev"
[ 99.703] (**) Option "xkb_layout" "us"
[ 99.704] (II) config/udev: Adding input device Video Bus (/dev/input/event8)
[ 99.704] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 99.704] (**) Video Bus: always reports core events
[ 99.704] (**) Video Bus: Device: "/dev/input/event8"
[ 99.713] (--) Video Bus: Found keys
[ 99.713] (II) Video Bus: Configuring as keyboard
[ 99.713] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 99.713] (**) Option "xkb_rules" "evdev"
[ 99.713] (**) Option "xkb_model" "evdev"
[ 99.713] (**) Option "xkb_layout" "us"
[ 99.731] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 99.731] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 99.731] (**) Power Button: always reports core events
[ 99.731] (**) Power Button: Device: "/dev/input/event1"
[ 99.753] (--) Power Button: Found keys
[ 99.753] (II) Power Button: Configuring as keyboard
[ 99.753] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 99.753] (**) Option "xkb_rules" "evdev"
[ 99.753] (**) Option "xkb_model" "evdev"
[ 99.753] (**) Option "xkb_layout" "us"
[ 99.754] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 99.754] (II) No input driver/identifier specified (ignoring)
[ 99.754] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 99.755] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 99.755] (**) Sleep Button: always reports core events
[ 99.755] (**) Sleep Button: Device: "/dev/input/event4"
[ 99.770] (--) Sleep Button: Found keys
[ 99.770] (II) Sleep Button: Configuring as keyboard
[ 99.770] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 99.770] (**) Option "xkb_rules" "evdev"
[ 99.770] (**) Option "xkb_model" "evdev"
[ 99.770] (**) Option "xkb_layout" "us"
[ 99.773] (II) config/udev: Adding input device HD Video WebCam (/dev/input/event10)
[ 99.773] (**) HD Video WebCam: Applying InputClass "evdev keyboard catchall"
[ 99.773] (**) HD Video WebCam: always reports core events
[ 99.773] (**) HD Video WebCam: Device: "/dev/input/event10"
[ 99.796] (--) HD Video WebCam: Found keys
[ 99.796] (II) HD Video WebCam: Configuring as keyboard
[ 99.796] (II) XINPUT: Adding extended input device "HD Video WebCam" (type: KEYBOARD)
[ 99.796] (**) Option "xkb_rules" "evdev"
[ 99.796] (**) Option "xkb_model" "evdev"
[ 99.796] (**) Option "xkb_layout" "us"
[ 99.797] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event9)
[ 99.798] (II) No input driver/identifier specified (ignoring)
[ 99.806] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 99.806] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 99.806] (**) AT Translated Set 2 keyboard: always reports core events
[ 99.806] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 99.823] (--) AT Translated Set 2 keyboard: Found keys
[ 99.823] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 99.823] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 99.823] (**) Option "xkb_rules" "evdev"
[ 99.823] (**) Option "xkb_model" "evdev"
[ 99.823] (**) Option "xkb_layout" "us"
[ 99.824] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6)
[ 99.824] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 99.824] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 99.824] (**) SynPS/2 Synaptics TouchPad: Device: "/dev/input/event6"
[ 99.840] (--) SynPS/2 Synaptics TouchPad: Found 10 mouse buttons
[ 99.840] (--) SynPS/2 Synaptics TouchPad: Found absolute axes
[ 99.840] (--) SynPS/2 Synaptics TouchPad: Found x and y absolute axes
[ 99.840] (--) SynPS/2 Synaptics TouchPad: Found absolute touchpad.
[ 99.840] (II) SynPS/2 Synaptics TouchPad: Configuring as touchpad
[ 99.840] (**) SynPS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
[ 99.840] (**) SynPS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 99.840] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[ 99.840] (II) SynPS/2 Synaptics TouchPad: initialized for absolute axes.
[ 99.840] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 99.840] (II) No input driver/identifier specified (ignoring)
[ 99.841] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 99.841] (II) No input driver/identifier specified (ignoring)
[ 100.317] (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
[ 103.491] (II) fglrx(0): Preparing normal LeaveVT...
[ 103.860] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 103.860] (II) fglrx(0): Backup framebuffer data.
[ 103.860] (II) fglrx(0): Backup complete.
[ 119.766] (II) fglrx(0): Preparing normal EnterVT...
[ 119.766] (II) Open ACPI successful (/var/run/acpid.socket)
[ 119.766] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 120.803] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):
[ 121.433] (II) fglrx(0): Hot-plug event occurs on device: 1:0:0
[ 124.299] (II) fglrx(0): Preparing normal LeaveVT...
[ 124.633] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 124.633] (II) fglrx(0): Backup framebuffer data.
[ 124.633] (II) fglrx(0): Backup complete.
All seems normal to me.
Here is my X configuration (/etc/X11/xorg.conf.d/10-monitor.conf) :
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "base-screen" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "native-monitor"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "radeon-4330HD"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "base-screen"
Device "radeon-4330HD"
Monitor "native-monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1366x768_60.00"
EndSubSection
EndSection
I initially wanted to use slim as a login manager but it always complains about not beeing able to connect to any X server.
As a bonus I give you my rc.conf, might be usefull :
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Amsterdam"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fglrx)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#INTERFACES=(!eth0 !wlan0)
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.100.255"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng hal acpid network !netfs crond !wicd)
I tried those tips Archlinux Catalyst Wiki but it didn't help.
I may be missing something obvious, but I am quite desperate so any help is welcome.
I can give you any other log that would be meaningfull to you.
Thanks for helping Archlinux to spread a little more.

i have this problem
lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc M93 [Mobility Radeon HD 4500 Series]
when I have install catalyst-utils 11.1 and catalyst-daemons .after rebooting i saw a black screen.
if I install xf86-video-ati occures lots of crash of KWIN plasma desktop .
i want using Catalyst

PowerMac 8600/250 LCD connection problem

I've an 8600/250 with a Sonnet Crescendo G4 processor upgrade; Sonnet Tempo ATA133 card; USB (v.1.1.2) card w/2 HDs--running both the native 4 gb scsi and a Seagate ATA/128 gb drives. It's all connected to a ViewSonic VX-710 15 inch LCD monitor. It is not internet connected. Of concern, a recent problem has arisen with the monitor connection. I've developed a thin white line that vertically extends down the face of the monitor adjacent the mouse scrolling marker. The line "moves" with the mouse scroll (a constant 1/2 inch relationship). Changing the monitor DPI setting to (1024X768--74.9mghz) will shorten the vertical length of the line to half the distance down the page. I'm using the analog connection with the monitor. Everything worked fine until very recently--the evolution of the line erratically developing over a few short days. The monitor, functions perfectly when hooked up as a second to my I-Mac, so I've ruled the monitor out as being faulty. Any ideas out there? VRAM memory issues? Would an ATA Rage 1280 video card installation help? I've grown rather fond of this useful, adaptive, tough little machine and it's reliability over the years. I use the computer as a dedicated platform for storage and management of years of my old OS 9.1 files and OS specific programs. I'm open to any and all suggestions.
Thanks,TMc

The long and winding road...
Voila!...it's working again. First of all, I want to thank everyone for their time and input--I tried it all. The final equation to the problem; stock VRAM.
Frustrated to no end, I wandered through the door of "Mc2", a local Mac shop (20+ years) in the nearby northern Monterey coastal burg of Soquel, CA. The shop always keeps a few older Mac's of various releases in the back for bits & pieces salvaging along with a couple of grey-hair techies who've been through it all.
The first thing asked was whether the "line" I was experiencing on the desktop had been accompanied by gradual pixel degradation over a a number of startups--it had! He responded by stating on the 85/86/9600 series motherboards VRAM serve as a through-put point, regardless of the Video card installed. He suggested "A faulty chip, especially with newer LCD monitors, will often manifest itself with a vertical line down the monitor." Additionally, he suggested this problem can also be confused as an indicator of a faulty LCD screen, BUT if the line moves with the mouse scroll or can be changed by pixel resolution/screen refresh rates, it suggests faulty VRAM--memory that should to be left in these machines for video stability. He suggested they should not be mixed and matched and need to be replaced in matching pairs.
A quick online over-night order to my trusty memory source "4AllMemory" (an excellent and reliable source for on-the-cheap new goodies for PCI macs), and Voila! With a little testing as to which chip(s) required replacement, I restarted and everything returned to normal. Relief, finally!

Images look fine in Bridge, but way off when opened in Photoshop

Not sure what I've done to my system, but am now having some color-management woes. I am using Photoshop and Bridge CS5.1, and for some reason, the color-management is not consistent between Bridge and PS... although it used to be until just recently. I am on a Mac Pro tower with a properly calibrated monitor (using an Eye One Pro), and all my other color-managed applications are behaving just fine, but I have this discrepancy now within Adobe where if I view an image in Bridge, it looks correct, but when I open that same image in Photoshop, it comes up way too light and desaturated. I have verified that a correct profile is embeded in each image, but this happens regardless of the source file. I have opened up grayscale images with a dot gain or gamma profile embedded, images with no profile embedded, sRGB and Adobe 1998 profiled images, and they all open up too bright. It seems like some kind of conversion must be happening, but I can't understand what that would be. Color Settings is set to preserve embedded and ask when opening for mismatches, but that's the same as it's always been on my system. I understand without a "suite" install, I cannot access the Creative Suite Color Settings dialog to sync color across multiple Adobe apps, but things have been fine for years between my PS & Bridge, so clearly I've done something wrong. It's also worth noting that RAW images in Bridge open up looking identical in the Photoshop RAW processing dialog, so somehow this is more related to TIFF, PSD & JPEG files.
I have used the Cocktail app for general system maintenance on my Mac, and in the dialog to delete old cahce files, I do recall it had an option to clear Color Sync cache (along with a bunch of other caches), so maybe that "clean up" somehow dirsupted my color matching abilities?
I was on CS5 when I noticed this problem, so I tried uninstalling that, downloading the slightly newer CS5.1 and re-installing, but the problem persists. Maybe the uninstaller app doesn't get rid of all the hidden support files, or maybe this is something else entirely? Have trashed prefs files and relaunched, still same problem.
Note how image on right is much lighter, shadows start to look posterized, colors lose saturation. Left is Bridge and Right is Photoshop. Screenshot done on calibrated monitor.
Thanks for any suggestions!

Thanks for your reply. Screenshot of my Color Settings attached. These are the same settings I've been using for many years.
What's most interesting is your reminder to look at Soft Proofing. I normally only use that when prepping an image for print, and want to predict what different paper types will "do" to my image.,, i.e. matte paper has less d-max, etc. SO, My assumption was that Soft Proofing is normally in the OFF position unless I turn it on, and/or toggle it on-off with Cmd-Y keyboard shortcut one engaged. BUT, your assessment was spot-on, in that when I opened up the View > Proof Colors dialog, it was set to Working CMYK. Not sure why, how, or when that became the default.
In all my time years with Photoshop, I've never needed to worry about soft proofing being ON without my permission, so I'm unclear how this came about. I honestly don't even know what the default has been for all the time that this was not on my radar as being a problem, I only know that when I did opt to soft proof an image, I woulp open the Proof Colors dialog, choose the appropriate device-specific paper profile to simulate, and then turn it back off when done. It would make sense to me that the default display in PS should match the (hopefully calibrated) monitor as a starting point.
Several more screenshots below, experimenting with various Proof conditions. This one is a 16-bit Grayscale image, with my usual 1.8 Gray Gamma color space embedded. This was my first experiment, not knowing what the correct default should have been (or was for many years). My assumption was that proofing the same color space as the document (G 1.8 = G 1.8), there should be no visible difference, but in fact there is. The left image is open in PS being soft proofed to it's own G 1.8 color space, and it appears visibly brighter than the same image to the right in Bridge.
Now here's the same comparison, with Proofing set to G 2.2, which should be wrong, but visually looks like a much better match.
Next I tried a color image, with Document Profile as the proof condition. Again, the Bridge image on the right looks correct, the PS image on the left looks washed out by comparison.
Here is the same image comparison, now with Monitor RGB enabled (which pulls my current monitor profile as the device to simuulate). I'd say this is either perfect, or a much better match. This also makes sense and correlates to my suspicion that PS should be showing you things in your native monitor profile until you ask it to do otherwise with a custom soft-proofing scenario.
So now that I think I've figured it out, I leave the Monitor RGB as the device to simulate, close the image, and re-open the image just to be sure, and this is what I get...
Essentially back to the same problem. I verified that View > Proof Colors is still set to my Monitor RGB, but it's as if it's not really being applied. SO, I changed it so something else, and then changed it back, and then it looks correct... as if I somehow need to kick it and remind it to do what it's already set to do.
So, the short answer is THANK YOU for reminding me to look at the proofing setup, becasue no I at least have a kind of workaround and know where to look. The tricker part is to understand why the default doesn't really stick to the Monitor RGB (if that is even the correct place for it to stay set to), and how or why did i get off into Working CMYK in the first place, as that's not a setting I've ever used on purpose.
Thanks again,
Eric

Native Monitor DPI?

Similar Messages

Maybe you are looking for