ACD screwed-up colour

I have a Mac Pro with a 20" Apple Cinema Display (aluminium).
I changed the colour of the display to 'Use greyscale' in System Pteferences/Universal Access to see a Web page in black and white.
When I unchecked 'Use greyscale' to switch back to colour, the display colours were not as before, and this makes seeing elements on the screen very difficilt. How can I restore the default display colours?
I have logged in to another account and the display shows the default colours, just as before.

I have now resolved this – by reinstalling the OS.
Apparently, nobody here has experienced this problem, so, to elucidate ya, I'll attempt to describe in agonising detail what happened.
I have a Mac Pro and a 20" ACD. I got this bundle of goodness about two weeks ago with Mac OS X 10.5.2 pre-installed. I updated everything as necessary and all was well.
On Wednesday (16/7), I wanted to look at a Web page in black and white and used System Preferences/Universal Access to switch to 'Greyscale'. When I unchecked the checkbox to return to 'colour', immediately the display generally became considerably darker and looked slightly 'solarised'. Some elements of the screen either became invisible (such as highlighted text, the scroll bar on windows, and other things like that). Other areas, such as text, became very difficult to see and the normally darker colours became much darker or almost black, with the normally lighter colours becoming very light or almost white.
I switched to another account and this unwelcome change vanished but returned when I switched back to the previous account. I knew now that there was no problem with the display itself, just with the software. I looked everywhere for a way to change back to my previous settings; I logged out of my 'troubled' account, I restarted the Mac, I looked in all Preferences which might affect even remotely the Display settings, I deleted all my Home/Prefs and replaced them with those from a backup. Nothing worked!
Until I reinstalled the OS. I have now checked that this problem will not return by switching to black and white in the way I did originally and the problem has not returned. Although it seems unlikely, I now have to conclude there was a 'fault' in the original 'factory installation'.

Similar Messages

Tiger Install Screws Up Colours

Hi all.
I've been going crazy - no one can seem to help me out. And I've been on two other forums with this...
I'm not certain it's an Adobe issues, actually. I think it's an Apple issue. However, no one on the Apple forums can help me. Perhaps there's a genius out there somewhere in Adobe world who knows the answer!
Here's my issue:
I have a PowerMac G4 with two HDs. I've had Panther on one of them and have just recently installed Tiger on the other.
After installing Tiger for the first time on a second interior HD, I selected in my display prefs the Adobe RGB 1998 setting, which has been perfect on my other interior HD with Panther on it. Yet colours on screen appeared to be way too contrasty.
So I calibrated my monitor. Soon after clicking 'done' and saving my profile, the screen seemed to change again to the way too contrasty look of the Adobe RGB 1998 profile!
I then opened an Illustrator CS1 file that I had created on my Panther disk. The image had an orange background which was now viewing as insanely bright assaulting redish orange, while all dark colours were too saturated!
Keeping this file open, I recalibrated my monitor using it as a barometer for colour comparison. Everything seemed to be going well, and I even set my Target Gamma to a much lower number (1.27) until my Illustrator file resembled the colour I had viewed it on my Panther disk.
Then again when clicking 'done' and saving my profile, the screen reverted to a dark and intense colour as before.
My Illustrator file looked 'normal', so I closed it. Then I opened a Photoshop file - same intensely saturated colour issue!
Upon reopening the Illustrator file to view alongside this Photoshop one, the colour was back to the insanely intense reddish orange prior to my calibration!
I will mention here that my entire Creative Suite is set to Adobe RGB as the colour space - just like on my Panther disk. I am convinced it isn't a CS problem.
And what convinces me even more is what happened next:
I kept the too bright Illustrator file open, and opened up an older copy of it that I had created days before (I had made a minor change to a graphic, then did a 'Save As'). They both were viewing as different colours! The original intensely orange one remained so, and the older file had a browny colour to it! Same file, same colours, viewing as if they were on two different monitors! I even went into the individual files to compare the colour values and they were exact.
I even went so far as to replace all Colorsync folders/files with the ones on my Panther disk, which I wouldn't normally do, but hey - I'm desperate! Anyway, no difference at all - still screwed up colour.
The odd thing is that even when I select all of the other display settings, they still make my CS documents look awful. So neither profile works at all.
What to do, what to do....!?
At first, I thought it was an issue when I selected the 'import' option at the end of the Tiger install. It imported all settings from my Panther disk. But the I erased the disk, and reinstalled Tiger clean with no imports. Same glitch.
And it isn't just my CS apps - my desktop is affected (wallpaper) and icons....
Any geniuses out there who can help poor lil old me?
thanks,
B.

It sounds like you are going through the growing pains of figuring out the basics of color management, and of monitor profiling in particular.
It would behoove you to stop all the frantic going-around, take a breath, and figure out the fundamentals before you go any further and compound the confusion.
Read "Real World Color Management", for example (
), slowly, starting from page 1. Try to understand and absorb the basic concepts, and then move on from there to the specifics (monitor profiling, print profiling, scanner profiling, etc.).
It will take time, but it will be time well spent.

How to fix screwed up colour matching?

I can never get consistent colour reproduction when printing files from illustrator. My monitor is calibrated and I am using unified colour management across the Creative Suite (as recommended) and have tried every combination of colour spaces and profiles known to man when it comes to printing through either an Epson 1290 or Epson 2880.
I am not talking about slight differences but some look as dark as Hades and others have skin looking radioactive pink!
Is there no easy way to ensure that what is shown on the screen at every stage actually comes out on the paper?????
I understand that the colour space of the file is mapped to the colour space of the monitor and then to the colour space of the printer, but something is clearly going very wrong indeed. I never had the issue with CS2 or CS3. When these tools are meant to help and do nothing but get in the way it is time to change!

I never had the issue with CS2 or CS3.
So, can we assume you are using a version other than 12 (CS2) and 13 (CS3)?
If it's version 12 or earlier, I can attest to profile-based color management working exactly as advertised with various printers, including Epsons, with the following caveat: If you are not printing to your 1290 or 2880 via a PostScript RIP (such as Epson's own StylusRIP or a third-party product) -- i.e., if you are using the native Epson drivers -- then your Illustrator document must be RGB mode. If you are printing CMYK documents via the native drivers, results will be unpredictable.
Of course, if you're using an Illustrator version earlier than 9, you must print via a PostScript RIP because there was no such thing as an RGB document mode back then. Illustrator merely outputted 'device' CMYK.
When these tools are meant to help and do nothing but get in the way it is time to change!
Change to what? Not a lot of choices out there for professional illustration. If you had this working properly in versions 12 and 13, I guess you could change back to one of those from whatever version you're now using. I suppose it is possible that the version you are using now has a bug in this regard.
It sounds like you're doing things correctly, but if you'd be more specific about your color and print-time settings (plus document color mode, printer driver, etc.), perhaps one of us might be able to suggest a procedural change.
Do let us know which Illustrator version you're using, and, while you're at it, tell us which operating system and version you're running. (We might be looking at, for example, a Win 2000/XT vs. Vista driver issue.)

Satellite P870 - underside screws - what is their size/part number?

Hi,
The underside of my P870 has lost some screws which fasten it so the laptop lid now opens with a bit of a crunch.
Can you please tell me what size these screws are so I can order some? Are they, for example, M2.5 x 2.5mm?
I've looked for this information and can't find it.
Thanks for your help.
Graeme

You are right. 9 screws are visible but two of them are placed under the HDD/RAM cover but I presume both of them are still there. ;)
You are right about screws colour. All original screws are coloured blue. The same is on my Satellite machine. Thats the reason why I cannot understand that screws become loose. Usually that should not happen. Originally they are right in place and also fixed with this blue colour material.
Of course I cannot discuss about screws you got from China but what you can try is to call nearest Toshiba service provider and check if my information was correct or not.

Colours screwing up in InDesign CS6

Basically I am printing my 2nd year graphic design folio in three days and Ive got a page where the colours are screwing up. I have them in photoshop all fine in RGB, then when I save them and place in indesign the colours screw up. I know this is CYMK but it has never changed my colours so much!!
Do I have to export as CYMK if I am taking it to the printers? Can't I export as RGB?
Heres an example
THE FIRST IMAGE IS THE RIGHT COLOURS. IN PHOTOSHOP
THE SECOND IMAGE IS WHAT IT LOOKS LIKE IN INDESIGN. (WE'RE TALKING ABOUT THE BLUE GETTING PALER)
THANKS

Color gamuts go both ways. There are also CMYK colors that can't be displayed in an RGB color space (like 95%-100% Cyan), so when you do a typical conversion of saturated RGB blues into CMYK via the default color settings you won't get the best result. You can improve saturated cyans by converting to CMYK and making a color correction.
So the default conversion to US SWOP CMYK of the blue in your capture is something like 79|38|0|0, which eliminates a full 20% of the cyan separation and adds a lot of magenta in attempt to compensate for a darker value. You have to keep in mind that because a 90-100% cyan can't be displayed, soft proofing colors like this is impossible and you have to rely on numbers.
With a post CMYK edit you can't get some saturation back. Here at the bottom I've converted to CMYK and color corrected the blue to 100|13|0|0 again keeping in mind that because 100% cyan can't be displayed the color will likely improve on an offset press. When you make CMYK edits like this for a press you want to make sure the values output, so don't embed a profile:

20" ACD (Aluminum): Glare and harsh colours

Compared to my 12" Powerbook G4 screen, I notice that the brightness of the 20" ACD is much higher. Also, the colours on the ACD are harsher (perhaps more saturated is the term?) and not "cool" to look at in comparison with the 12" PB screen. The result of this is bad glare.
Also, I notice that the "Colour LCD" colour profile that is used with the PB screen cannot be used with the ACD. The result is that the same image looks different on both screens.
Does anyone have any remedies?
I tried changing my ACD gamma to 2.2 TV gamma to reduce glare but this doesn't really help.

Heavyfeet
The brightness of your ACD is much higher and the color Gamut greater than your 12 PB. You can reduce the brighness to about 75% to try and match it. The default profiles are designed for specific displays and you shouldnt use them on the wrong device. If you are working with color and making decisions on the monitor I would recomened creating custom profiles using a colorimeter that are relatively inexpensive. An added bonus is you can get different displays to match much more closely.
Take a look at my post here for some devices.
http://discussions.apple.com/message.jspa?messageID=1613681#1613681
MikeR

Colour issues - 23" ACD

Hi gang,
Another question, if you don't mind.
I mainly work on 3D Architectural presentations. The clients are handed a digital files and I never deal with the printing of the images. Some go onto large billboards, some even get framed .
In most of the cases the colour is "close enough, good enough".
i am finding that the ACD is much warmer than the MBP, even if set to the same colour space; I mostly work in Adobe RGB 1998.
I don't think I need to calibrate the display with a hardware device (like the spider) as I don't output, but which do I trust more?
I am afraid I'll end up with images being overall too blue or too yellow depending which screen I rely upon.
Any ideas? Happy to hear about your experiences.
cheers
i.3d

I see your point WRT the brightness moving to zero, but my question remains, how long should this decay go on and what is acceptable?
I will do another experiment tonight turning off all power management on the display to see if indeed it ever does settle. I'm going to note the starting level (no adjustment after the display has been running for at least 30 minutes), then after 1, 2, 4, 8, and 16 minutes post slider adjustment. If it continues to decay after 16 minutes, I would think that is unacceptable.
Sound reasonable?

ACD Colour banding

Been to my local Apple store today to have a look at the 30' ACD.
While the Apple guy in the shop promised the display to be top notch colour etc I did the old black to white gradiant across the full screen (2560 x 1600 at 100% pixels) and the banding was terrible. I checked all the settings in the display preferences and all were set correctly.
When I say terrible I mean bad. I even turned the brightness down to 50% and the results were just as bad.
What I would like to know from Eizo Coloredge/Samsung XL or NEC Spectraview owners is if you do the same on your screen does this show tonal banding?
Is this just an LCD thing, an uncalibrated ACD or just out of date ACD technology?
Thanks in advance.
Gareth.

I hear the banding is glue that still hasn't dried properly ,apparently they were trying to ship them out the door a little too quickly...who knows !

XTerm colours screwed up after upgrade.

After a system upgrade back on Sunday, xterm always starts up with black text on a black background. I just tried running it from another terminal instead of via KRunner, and I got the following warnings:
Warning: Color name "WINDOW_BACKGROUND" is not defined
Warning: Color name "WINDOW_FOREGROUND" is not defined
I've never really tried to customise xterm before as I usually like the defaults (and I typically use GNU screen anyway), but I haven't been able to figure out how to get it back to a usable state. In the meantime, I've just been using Konsole.

Maybe try a defined .Xdefaults so this type of thing won't happen in the future. See http://wiki.archlinux.org/index.php/Xdefaults

[Solved] Xorg 1.5 screwed up my NVIDIA

Hi,
Today I did a pacman -Syu and I got the newest NVIDIA driver installed and the newest Xorg. Everything broke. Well not exactly everything. But my settings are all screwed up. For a start my screen refuses to load at the normal resolution (1680x1050). I got a default 1024x860 (or whatever it is). Also my colour depth is 16. And regardless of any changes I make in NVIDIA settings manager the changes never stick. Also my compiz-fusion is totally screwed up. When it starts up my screen goes completely white. I have to blindly alt+F2 and run kwin to be able to do anything.
Also my fonts are really small.
Here is my xorg.conf:
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
# RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
# FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
# Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
# Load "type1"
Load "freetype"
# Load "record"
# Load "synaptics"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "sv-latin1"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 32
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
#Section "DRI"
# Mode 0666
#EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
This is what my Xorg.0.log says:
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 i686
Current Operating System: Linux myhost 2.6.27-ARCH #1 SMP PREEMPT Fri Nov 28 10:56:24 UTC 2008 i686
Build Date: 09 November 2008 07:16:27PM
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: Mon Dec 1 21:55:19 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Xorg Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "PS/2 Mouse"
(**) Option "AutoAddDevices" "False"
(**) Not automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
(WW) The directory "/usr/share/fonts/ttf/western" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
Entry deleted from font path.
(==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
(**) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/misc,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/100dpi,
/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"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d66e0
(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@1:0:0) nVidia Corporation GeForce 8800 GT rev 162, Mem @ 0xfa000000/0, 0xe0000000/0, 0xf8000000/0, I/O @ 0x0000ac00/0, BIOS @ 0x????????/131072
(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 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -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 by default.
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(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 XFree86-DGA
(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: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 177.82 Tue Nov 4 14:03:48 PST 2008
(II) Loading extension GLX
(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: "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: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) NVIDIA dlloader X Driver 177.82 Tue Nov 4 13:42:45 PST 2008
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(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 "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: 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 "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(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] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 16, (--) framebuffer bpp 16
(==) NVIDIA(0): RGB weight 565
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce 8800 GT (G92) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.92.12.00.05
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8800 GT at PCI:1:0:0:
(--) NVIDIA(0): Samsung SyncMaster (DFP-1)
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal Dual Link TMDS
(II) NVIDIA(0): Assigned Display Device: DFP-1
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1024x768"
(II) NVIDIA(0): "800x600"
(II) NVIDIA(0): "640x480"
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): DPI set to (55, 65); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
(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] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[17] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[19] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Unable to connect to the ACPI daemon; the ACPI daemon may not
(II) NVIDIA(0): be running or the "AcpidSocketPath" X configuration option
(II) NVIDIA(0): may not be set correctly. When the ACPI daemon is
(II) NVIDIA(0): available, the NVIDIA X driver can use it to receive ACPI
(II) NVIDIA(0): events. For details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "1024x768"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms" "true"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(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
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "sv-latin1"
(**) Keyboard0: XkbLayout: "sv-latin1"
(WW) Option "XkbVariant" requires an string value
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(**) Option "Protocol" "auto"
(**) Option "Device" "/dev/psaux"
(II) PS/2 Mouse: Setting mouse protocol to "ExplorerPS/2"
(**) PS/2 Mouse: Device: "/dev/psaux"
(**) PS/2 Mouse: Protocol: "auto"
(**) Option "SendCoreEvents" "true"
(**) Option "CorePointer"
(**) PS/2 Mouse: always reports core events
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "true"
(**) Option "Emulate3Timeout" "70"
(**) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 70
(**) Option "ZAxisMapping" "4 5"
(**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5
(**) PS/2 Mouse: Buttons: 9
(**) PS/2 Mouse: Sensitivity: 1
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (PS/2 Mouse)
(II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
(II) PS/2 Mouse: Setting mouse protocol to "ExplorerPS/2"
(II) PS/2 Mouse: ps2EnableDataReporting: succeeded
(II) config/hal: Adding input device ImExPS/2 Logitech Explorer Mouse
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceRequest failed
(II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select@1680x1050+0+0"
Any help would be much appreciated!
BFC
Last edited by BlueFightingCat (2008-12-02 16:41:01)

fLuXx wrote:Ok, so i tried, but it didn't work. All works but the fonts - they're messed up pretty bad. I can't even read what I'm typing right now. Here are some screenshots (just so you know - it gets even worse than that):
http://img254.imageshack.us/my.php?image=fluki1qu4.png
http://img254.imageshack.us/my.php?image=fluki2ax1.png
hmmm, I have exactly the same problem and I also use the nvidia-96xx.
I noticed that I only get the scrambled text for the lines beyond 20 lines...so if I rescale the height of my window to 20 lines I never get scrambled text and and when I change the height of the window larger then 20 lines, only the 20+ lines get scrambled.
Last edited by Bob Day (2008-12-02 18:05:24)

Strange colours on screen after upgrading memory.

Hi all.
I bought a 2nd hand eMac from eBay and have just received a 512MB SDRAM module to upgrade the memory from it's current 384MB to 768MB.
On the first install I removed my 128MB module and installed the 512 module - No Boot. (beeping on startup)
I thought I'd try the 512MB module on its own - No Boot (again beeps).
I then tried just my 256MB module - Booted fine.
I then tried the 512MB module on its own and it did boot but this time the display colours were very off (the apple logo in Tiger was pink for instance)
Last of all I took out all ram and reseated it all - Success finally.
Now my questions are:
Were the beeps a memory error warning (I assumed they were)?
Is the display issue possibly related to poorly seated memory?
I do have big hands and found it difficult getting the ram in the eMac, especially with the sharp(ish) mesh on the underside of the eMac.
I feel this may be related to me seating the memory poorly but that time it booted with the colours all screwed has me worried in case something more is wrong.
I'm currently testing the memory with Remember and all is fine so far (I'm up to the 256 block sequential test so far)
Thanks for reading and apologies for the long post!

Thanks for the suggestion srojtas.
The eMac has been running fine since posting this and completely passed the Remember memory test. I also tested it by filling the memory up by opening many apps and it didn't crash at all there either.
The eMac didn't come with a hardware CD sadly, so I can't test it that way!
I feel now it must have all been due to me not seating the memory correctly.

[SOLVED] I screwed up my kernel hooks... I think

I upgraded to the newest kernel and when I rebooted... failure. Here's what did manage to printout when I tried:
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60, 0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
registered taskstats version 1
Freeing unused kernel memory: 460k freed
:: Loading Initramfs
:: Running Hook [udev]
:: Loading udev...done
:: Running Hook [resume]
Waiting 10 seconds for device /dev/sda2 ...
Waiting 10 seconds for device /dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29 ...
Root device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29'
ERROR: Unable to detect or create root device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29'
You are being dropped to a recovery shell
Type 'reboot' to reboot
Type 'exit' to try and continue booting
Note: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/disk/by-uuid/1720446b-eb15-raf6-94c4-1aa40e959b29' gets created while you are here,
try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$
Reboot gets me the same and exiting results in a kernel panic.
Ok, so what I think happened. With the old kernel I spent a lot of time screwing around trying to make my comp boot faster. One of the things I did was to delete the [ide] and [sata] hooks from my mkinitcpio.conf. At the time I looked up my computer (Compaq Presario F700) and saw that it had a scsi harddrive and thought that I didn't need the other 2 hooks (Does my laptop need them? All this is a guess based on the fact that it all screwed up and that its probably my fault). Looking back, I don't think I even did that tweak right because I don't remember regenerating the kernel and fallback images. Its probably been sitting there just waiting. So when I updated to the new kernel today it did the regenerating and because I screwed with the settings... failure. It can't read my harddrive anymore.
My questions are this: Am I right in what I did wrong? and how do I fix it?
Thanks in advance.
Last edited by Oliver_Schmid (2009-06-24 00:59:22)

I don't remember where I got that faulty info, but I was a fool for trusting it.
The fallback kernel has the same problem. Probably because it was made using the same hooks.
More updates: I found my recovery disk. Booted into it and mounted my HDD. Changed the hooks in mkinitcpio.conf back to the originals. Ran 'mkinitcpio -g /mnt/boot/kernel26.img' trying to rebuild the image based on correct hooks based on the info on the mkinitcpio page of the ArchWiki. Didn't seem to work though, think I need to reread the man page. Anyone know the command(s) I should be running?

Colour issue with 'Save for Web' - Photoshop Elements 6 (Mac)

Cross posted here, but no answer so far. Sorry for cross posting. For me, this is urgent, but I know it's not for anyone else, so apologies for putting 'urgent'.
http://www.mac-forums.com/forums/images-graphic-design-digital-photography/150670-colour-i ssue-save-web-photoshop-elements-6-a.html#post840419
This is a similar issue to this:
Save for web color issue
Except the user who posted the above was using photoshop cs3, and I'm using Adobe Photoshop Elements 6.
When I work on a photo, I get it just right, then go to Save for Web, and the original it previews is loads lighter than the orginal I was working on in the first place. See 'Picture 1' attachment.
I have changed the colour settings on the Save for Web options - I've chosen each one in turn, and none fix the problem.
There seems to be no similar option in PSE6 to this that fixed it in CS3:
IN the save for web box there is a small round button with an arrow in it (near the Done button).
In the list when this button is pressed deselect Convert to sRGB
I used to use PSE2 on a PC, and never had this problem. I didn't need to mess about with colour profiles or anything similar on the PC. The original was the original, not a washed out version of the original. Why spend ages getting the file just right, only for Save for Web to screw it up?
Any advice to fix this would be much appreciated.
Thanks

Thanks very much for your reply.
I've uploaded the images here:
http://jimpix.co.uk/images/Picture 1.jpg
http://jimpix.co.uk/images/Picture 2.png
I deleted the prefs. file you suggested, and then opened PSE6.
I then tried the profile setting you suggested - but it's not an option:
http://jimpix.co.uk/images/Picture 3.png
I tried 'remove profile' just in case that worked, but the same effect happens on Save for Web.
Not sure what to try next!
Thanks

New 30" acd & old 23" acd problems

Hey
Last week my 23” 2-year-old acd power bar completely died. With Apple care, I had it replaced in store. Once I got home, when I powdered on the display the screen was full of dust spots, sandwiched between the LCD and the protective screen. So the next day I was back in the apple store. We were all puzzled on how the dust got in there, but since you can’t just clean it they placed an order for a replacement monitor. I took this one back home...so far so good.
For the past few weeks I was toying with the idea of getting a 30” acd, so the next day I went to another apple store (it was on my way) and picked a brand new one. Got home, plugged it in...and what the...! First, the backlight bleeding at the bottom left and right corners was terrible. Left bleed was sort of extending upwards, in a weird spiral. But that’s not all...I replaced the background with a solid white, and to my surprise, left quarter of the display was shifting towards blue.
I didn’t go to the apple store right away, i actually waited to get the 23” replacement. After few days i picked it up, came home, plugged it in, and again...more troubles. The white background didn’t match at all. The 30” was white, with that annoying shift towards blue on the left, and the 23” was just yellowish/pinkish.
Off the the apple store yet again. First, we dealt with the 23” - waiting for yet another replacement. Then the 30”. I tried 2 monitors in the store and BOTH had the same blue shift on the left. The backlight bleeding was uniform on those two new, but that shift was present on both. I wasn’t happy, but i took the 2nd display (3rd 30” i tried) just to see how i’d feel using it...and so far, I can’t stand it. All i see is the blue on the white background.
just today i replaced my old sypder 2 with eye-one display 2 calibrating device. I ran multiple tests on the 30” monitor (center, bot/bottom left and right) and found out that the left side of the monitor is quit a bit different. The blue linear curve on is quite a bit off at the top (at about 240) on the left calibration point comparing to the center. Reds and greens are off in colorant tristimulus (when checking the profiles), and the tristimulus value is off towards the blue on left calibartion when looking at the chart. It's there, it's visible.
Now, i’m trying to calibrate the 23” and 30”, trying to get the same white look. No luck!
This is driving me insane. Same panel technology, same manufacturer, two different colors. And the 30”....all where made in korea...is it possible its a bad batch or something. I’ve never seen anything like this with any display I owned or worked on, from a cheap 200$ panel to 1000$ 24” - none had backlight bleeding, much less any color shifts.
I do a lot of post image post processing (advanced amateur photographer), and this is simply unacceptable. As far as I'm concerned i own 3.5 thousand pixels that are complete worthless...
I’ll hit the apple store tomorrow with the 30”, again. I don’t think i’m expecting a lot from a 2,000$ display.
I’d really appreciate help, comments, anything that could help...
Thanks
adrian

Update:
picked up a brand new 30" - this one is great - uniform backlight, no weird colour shifts, just ever so slightly less bright at corners, no dead/stuck pixels. later on today I'm going to pick up the new 23" that just arrived...will test it in store.
adrian

LG Monitor and New Mac Pro -- Colours out of Whack

I have an LG L226WT and a 20" Apple Cinema Display connected to a brand new Mac Pro.
Both monitors (in the same configuration) were running on my old PowerMac G5 before.
The Cinema Display works fine, colours are good, so is light etc.
The LG first had ghosting (severe at that) and this morning the colours are totally out of whack. Looking at some photos I had taken a week ago and colour corrected on the G5 now look like a child painted them (on the LG monitor, on the Cinemadisplay they are fine).
It's not the graphics card either. If I take a screenshot on the LG and look at it on the Cinemadisplay the colours etc. are correct, but the LG is right now pretty useless to me. I tried to calibrate it but the end result is pretty much the same, it just does not seem to want to play nice.
I don't think it is the DVI cable, as it is securely screwed in and in the same location as on the PowerMac, turning the monitor off / on seems to resolve the shadow problem but not the colour issue.
Anybody have experienced this? Any tips outside of trashing the LG and buying a new screen?

The ghosting issue is still one when I first turn the computer on. I found that I have to turn the monitor off and on and it resolves the issue.
I also found the source of my colour problem, it comes down to the LG "resetting" itself to some "automatic improvement" or whatever you want to call it, which completely messed with the tones. After I turned that "feature" off it worked well, but man, that took me three days to figure out.

ACD screwed-up colour

Similar Messages

Maybe you are looking for