HDTV Resolution not supported, Desktop lost

I connected a HDTv to my G4. The image was great but circles were ellipses. I changed the resolution several times but one lost everything on the panel. It looks like a dark curtain. Changing the sets mode to a different input and then coming back shows part of the desktop. It is stretched and very low in resolution. The mouse and keyboard do not function.
The television has been tried on two computers, both with ATI cards. This sequence of steps reocurrs with both DVI and analog, VGA, ports and cables. The PRAM has been zapped with no result. Yasu has been run.
The old monitor still works fine when reconnected. The TV monitor works fine with the Tiger install disk.
Is there anyway to clear the computers memory and get this monitor working.
Dual 1 ghz mirror door Mac OS X (10.4.8)

The settings associated with moniors can be found in preferences files (.plist) that also have the name "windowserver" in them. If you search on the term windowserver you should find at least two occurances. One will be com.apple.windowserver.plist and one will be com.apple.windowserver.xxxxxx.plist where the Xs will be some random string of characters and numbers. If you trash those files, it should be like starting over with the TV.

Similar Messages

Camcorder video error: "Unable to record. Resolution not supported by memory card."

We purchased two Samsung Droid Charges the first day they were released and recently they've both been getting this error after 8-15 seconds of recording in HD (1280x720): "Warning: Unable to record. Resolution not supported by memory card."
Called Verizon tech support, but they referred me to Samsung. Not knowing much about micro SDHC cards, I was alarmed to discover that the factory pre-installed 32gb card is only rated class 2 for speed. Samsung told me you need a minimum of speed class 4 or higher to record at this resolution. The only problem is you need an SD card installed in order to use the camcorder, period. In other words, all of us who payed an arm and a leg for the best phone Verizon sells now have to go buy our own micro sd card that actually supports all of the phone features as advertised?! The lowest prices I've seen for the faster cards are $70. Are we the only two Charge owners experiencing this problem? I've read somewhere that lower speed class cards may initially support faster speeds than they are rated until they accumulate more files, so the problem may go undetected for some time until you have more files that are stored in different locations on the card (making them difficult to access at the faster speeds). This may explain why are the first ones to get this error since we've had the phones the longest and only 50% free space remaining on the SD card. Oh, Samsung also said they won't be able to replace your card for one that has the proper speed rating. Kind of seems like false advertising to say a feature is available (HD camcorder), and then not mention the fact that the memory card provided isn't sufficient for that feature (separate upgrade required). Anyone else sharing the same frustrations? Ideas?

Thanks for the response. I've tried everything on that page. It's not an issue with the cable, or firewire port or the cable being connected properly, as the iSight camera works fine with iChat. I've disconnected the only other firewire device on the computer, didn't make any difference. Camera works fine in iChat, so it's not the camera itself. And, as I mentioned in the post, the same camera, if hooked up to my laptop, works just fine recording in QuickTime. So, it appears to be an issue with the QuickTime installation on this computer. I've done a search for the same error I'm getting and found some other occurrences with the same problems, but none that offered a solution.

This ANE does not support Desktop(Mac) platform

I'm getting the following error when I try to add an ANE to my mobile project.
This ANE does not support Desktop(Mac) platform
I'm using Flash Builder 4.7.(Air 3.7) The iOS SDK path has been set. I've tried to just ignore the error and just apply settings but this causes and error. I'm having the problem with all ANE files. The Target is showing up as Google and iOS so I'm not sure why it thinks I'm trying to run on the desktop.

Created a new mobile project and still getting the same problem. I think it's a Flash Builder 4.7 issue.

Mac Pro to Samsung HDTV - "Mode not supported"???

Alright, so I have just received my new Mac Pro in the mail yesterday and wanted to hook it up to my television - a 1080p Samsung (Samsung LN-T4671F) HDTV. I am using a DVI-to-VGA cable. I feel I should probably explain the entire situation so that it's all clear.
The first time I started the computer after plugging it into the TV, the Apple logo with the Loading, spinning thing (not the multicolored wheel) showed in beautiful 1920x1080. After loading, the screen jumped to a lower resolution for a second and then went black, finally giving me a "Mode not supported" error. Thinking it was just a little hiccup, I restarted the computer and after the Apple logo screen, it showed me a screen on how to put batteries in my mouse (or something along those lines, I didn't really look), and then it had me set up my wireless keyboard. After this, it showed me the WELCOME video and allowed me to log on to my computer and start using it.
After about 15 minutes, I was going through the system prefs and came across display. Thinking maybe I should lower the resolution to better see text, I clicked on a lower resolution around 1600xsomething. The screen went black and gave me the "Mode not supported" error again. I thought I could just wait a few seconds and if I didn't confirm the resolution, it would go back...but it never did. After trying to restart my computer a number of times and receiving the error message each time, I booted in Safe Mode, which I am in right now.
I went into the sys prefs and made sure the resolution was set to 1920x1080, which it already was, and restarted the computer. Error again. I went into the settings of my TV and went to PC and had it auto correct the resolution to the input. Error again. I have been running in Safe Boot since - no sound is annoying - and enjoying the display in full 1920x1080 (1080p)...so the set obviously supports it (and the manual says it does too).
My video card is an NVIDIA GeForce 8800 GT. What's most annoying is that it's pretty obvious that the display supports this resolution and yet won't allow it to work outside of Safe Boot mode.
Please help

Had the same problem with an AOC 1080p TV, trying to connect to it using VGA cable.
Ivan's earlier post clued me in to solution:
- Plug in the TV, get the "Mode not supported" message on the TV
- Open the Display Preferences, you should see the display preferences for the laptop "Color LCD" monitor. Click the "Gather Displays" button - this should bring the display preferences for the TV behind the laptop preferences window. Switch to the TV's display preferences window.
- In the TV's display preferences window, switch refresh rate down to 59.9 Hertz (your TV may need different refresh rate, but on mine I only get options for 59.9 or 60).
That did it for me!

BENQ FP241W on Retina Macbook Pro - native resolution not supported?

Hi there,
I have tried connecting my BENQ FP241W monitor to my new Macbook Pro with retina display via HDMI.
The monitor appears to be displaying at only 1600x900 and looks very blurry since the native resolution of the monitor is 1920x1200. I have actually tried this with an older 2009 model macbook pro and the same thing happend, although I was using a dispaly port to HDMI adaptor and never investigated further to the reason the native resolution was not supported.
Going back to the Retina Macbook and the BENQ FP241W. It gives the following resolution options for scaled: 1080p, 1080i and 1600x900. When I choose 1080p or 1080i it looks the same as 1600x900 i.e very blury and not even close to the sharpness that is capable of the display - true 1080p should look sharper than how it looks selected so I dont believe it is actually displaying 1080p. It also has the option for 'best for display' which I would expect it to show native resolution of 1920x1200 - unfortunately it still apears to be 1600x900.
Can anyone help me out? Is this a driver issue or something else?
Thanks
Rich

I can sort this out by just using a HDMI > DVI cable which works fine. I think there must just be an issue with the BenQ HDMI input supporting 1920x1200. Its annoying because the screen is also connected to a PC workstation by DVI so it would be good to have the HDMI for the Macbook so I can quickly switch the display by pressing a button instead of having to unplug cables...

SXGA+ Projector resolution not supported ?

I have a projection design f30 projector that has a maximum native display of 1400 x 1050 SXGA+
From a PC it will display this resolution no problem however with a macpro or any laptop i've tried the most I can get is 1280 x 720 ?
Is their anything I can do to rectify this ?
Many thanks
Matt

Dual Link DVI is used to support displays that are very wide, such as the Apple Cinema display. These displays divide the LCD into left and right zones, (as if it were made of two LCD units side-by-side). The control signals are used for both sides, but the data are provided for the left and right panes separately, on two sets of pins in the cable.
A dual link DVI cable/port must have all pins populated. A single-link DVI port/cable often has three columns of pins near the center missing.
You can only Mirror resolutions that also work for your built-in display. If your built-in display cannot do this resolution, then the setting will not be available for the external display.
When you switch to "Extended Desktop", many more resolutions will become available for the external, because the built-in and the external can each operate independently. Each display in "Extended Desktop" will be looking at a portion of a very large Virtual Desktop, (i.e., they will not hold exactly the same picture.) You can then use the arrange button that appears to position the two displays into the Up/Down Left/Right orientation you prefer.
The windows you wish to display can be moved to display completely on one display or the other, or overlapping both displays. This feature works for all well-behaved Mac Applications.

Is there any way to export a desktop AIR package when desktop is not supported by an ANE?

I have a third party ANE that I need to use. The ANE has a target for Android, but when I add it in Build Path->Native Extensions an error shows up "This ANE does not support Desktop(Mac) platform". Now, my app is targeting android, but to make it easy for others in my company to play builds without having a device, I've been using the "Export Release Build->Signed AIR package for installation on desktop" option. The problem is, since I've added the ANE, I'm no longer able to hit the "finish" button because it's greyed out due to the error (even though the checkbox to include the ANE is unchecked in the export settings. The only way I've found to work around this is to remove the ANE temporarily and comment out references to it to build the desktop package, which is not optimal. Any other suggestions?
Thanks!

Rather than commenting it out, you could define a compiler parmeter:
[code]
-define=CONFIG::includeAndroidANE,true
[/code]
Then, in your code, wrap any references to the problem code in the config statement
[code]
CONFIG::includeAndroidANE
import the.problem.package.ProblemExtensionClass;
[/code]
And:
[code]
CONFIG::includeAndroidANE
   if(ProblemExtensionClass.isSupported()) {
        var v:ProblemExtensionClass = new ProblemExtensionClass();
         v.init();
         v.doSomethingThatIsntSupportedOnAMac();
[/code]
Then, when you compile for Mac, you just need to set CONFIG::includeAndroidANE,false;
This is what OSMF does to support different versions of the player, and also what SWIZ do to support different versions of Flex.
All good.
G

Changed resolution by mistake and have lost everything "mode not supported"

Guys,
This one is totally my own fault but ive managed to crash my Apple TV and was wondering if someone may be able to assit me with a solution?
Apple TV was working fine on my samsung HD TV and i was playing about with the settings.
I belive i was in "resolution" at the time and the setting was 'auto'.
For no reason other than my own stupdity, i changed the resolution to 780p or something like that and the screen went immediately blank.
All i get now is "mode not supported".
Ive held down + and menu and done the scan and it wont retrueve my previous settings.
Ive also tried - and menu and still nothing.
Why didnt i just leave it alone.
Any ideas folks on how i can get this back working and restore to auto?
Panicking.....
Simon.

Have you tried restarting it.

"Mode not supported" when connecting MacBook Pro to HDTV

When I connect my MacBook Pro to the SAMSUNG widescreen HDTV and hit "Detect Displays", it does detect it as VGA Display and it gives me a bunch of options for resolutions and refresh rates, but there was no "Options" tab where I could check or uncheck "Overscan" and even keeping the refresh rate at 60 Hz, and even trying mirrored and non-mirrored screens, nothing worked. It still said "Mode not supported". I used a dual-link DVI to YPbPr cable which I just bought and my friend can connect his MacBook Pro to his HDTV with the same cable, but it doesn't seem to work for me. What's wrong?

Try using an app like to get the stranince resolution:
SwitchResX – The Most Versatile Tool For Controlling Screen Resolutions On Your Mac
Display Menu from Mac App Store
The monitor specs
Native resolution1440 x 900
Resolution720p
Supported DTV resolutions576i
Supported computer resolutions640 x 480 (VGA)
PC InterfaceVGA (HD-15)
Video InterfaceComponent, composite, HDMI, S-Video, SCART
From:
http://www.cnet.com/products/samsung-le19r86wd-19-lcd-tv/specs/

WINDOWS 8 DID NOT SUPPORT MY PALM ZIRE 72 PROGRAM. LOST ALL DATA.

My new windows 8 computer does not support my Palm Zire 72 software. I had my handheld charged, but unplugged and lost all my data since there was no backup. I have my old hard drive with most of the backup on it. Is there any way I can get this data back. It was YEARS of contacts that I lost. Thanks for your help.

vhk,
Win 8 does support Palm desktop software for Zire 72.
I have been using it for 3 months with no problems.
If you have 64bit Win 8 you need to download and install the Aceeca driver to HotSync.
http://h30434.www3.hp.com/t5/Palm-OS-WinMo-Hardware-and-Software/64-Bit-Windows7-8-8-1-USB-drivers-f...
I have my Windows UAC (User account Control) set to Never Notify.
I set the Palm Desktop/ Properties/Compatibility to Run this program as administrator
I use the same PD software (4.14e) on Vista, Win 7, and Win 8 ( I HotSync my Zire 72 on all 3 PCs weekly)
When you install the PD software skip check the internet for updates step.
If you can find your Palm desktop user folder on the old hard drive you might be able to copy it and paste it into the palmOne folder when you have Palm Desktop installed on the Win 8 PC.
User folder path for PD 4.1for XP & Vista is: Computer (C drive)/Program Files/ palmOne/User ID (same as Zire 72 last Hotsync)
User folder path for PD 4.1for Win 7 & 8 is: Computer (C drive)/Program Files (x86)/ palmOne/User ID (same as Zire 72 last Hotsync)
If you had a long user ID on the Zire 72 it will be shortened to 5 or 6 characters in the palmOne folder.
http://h30434.www3.hp.com/t5/Palm-OS-WinMo-Hardware-and-Software/How-to-copy-Palm-Desktop-data-to-a-...

GT 120 does not support resolution 1440 x 900?

Hi there.
I have a 15" Macbook Pro and wish to use the Apple remote desktop to control my 2009 Mac Pro remotely. However I can't figure out a proper resolution -- 1440x900 in the remote desktop... This resolution is not supported either when I work on the Mac Pro itself.
Suggestions are appreciated.
-oolong

Hi, SophiaHat and a Warm Welcome to Apple Discussions and the G5 Power Mac forum!
Do you have or are you buying a dual-core G5 with the PCI Express graphics?
http://www.apple.com/powermac/graphics.html
Which display do you have or are getting?
Can you link to the exact card you are thinking about?

Xrandr not supporting old resolution

Upgrading Xorg completely broke my system. Lots of not-fun later, I found out that setting up dual-head has to be done with xrandr, which seems like a good way to do it.
However, xrandr does not support setting the resolution from before...
I want to have my two screens running at 1280x1024 (which is quite normal I think, anyone having two 19''ers ).
Now xrandr tells me, that the maximum resolution I can use is 1920x1200. Perviously with xinerama I could set the resolution to 2560x1024 without any problems.
Anyone have similar problems? Anyone have a solution?
xrandr -q:
VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1920x1200 60.0 60.0
1920x1080 69.9 60.0 59.9
1600x1200 60.0
1680x1050 69.9 60.0 59.9
1600x1024 60.2
1400x1050 70.0 70.0 60.0
1280x1024 60.0*
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1280x800 75.0 70.0 60.0
1152x864 75.0 75.0 70.0 60.0
1280x768 70.0 60.0
1280x720 75.0 70.0 60.0
1024x768 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 72.8 75.0 59.9
DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
1280x1024 60.0*+ 76.0 75.0 71.9 59.9
1152x864 75.0 74.8
1024x768 75.1 70.1 60.0 59.9
832x624 74.6
800x600 72.2 75.0 74.9 60.3
640x480 75.0 72.8 66.7 60.0
720x400 70.1
640x350 70.1
S-video disconnected (normal left inverted right x axis y axis)
graphics card, lspci:
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
xorg.conf (excerpt):
Section "screen"
Identifier "screen1"
Device "device1"
Defaultdepth 24
Monitor "monitor1"
SubSection "Display"
Depth 24
Virtual 2560 1024
Modes "1280x1024" "1280x1024"
EndSubSection
EndSection
This is the only screen running right now, the one I wish to extend using xrandr...

I have a Mac Mini Late 2012, 16GB ram, 2.6GHz, Intel core i7, Intel HD Graphics 4000 1024 MB.
Many of the posts/solutions that I read recommended copying the file: AppleIntelFramebufferCapri.kext (contains video/res/buffer settings?) from a Mavericks Time Machine backup. Next downloading a program called KextBeast (installs .kext files) and run KextBeast to install that file into Yosemite. Since I didn't have a Mavericks Time Machine backup - I did a fresh install of Mavericks then copied the AppleIntelFramebufferCapri.kext file to an external drive. Next I did another fresh install of Yosemite. Booted up into Yosemite. Copied the AppleIntelFramebufferCapri.kext file to my desktop. Ran the KextBeast program and it installed the file exactly where it is suppose to be. I rebooted and then opened System Preferences/Displays -chose the "Scaled" option and there was the 3440x1440 resolution at the top of the list. My LG 34UM94-P Monitor is running in all its 3440x1440 glory!!!!
To locate the AppleIntelFramebufferCapri.kext in Mavericks:
From the Finder, select Go > Go to folder... and enter "/System/Library/Extensions/".
KextBeast can be downloaded here: www.tonymacx86.com
I have to admit I was worried about running KextBeast - just because I know nothing about the program - but I figured worse comes to worse I would do a fresh install back to Mavericks. But KextBeast worked like a charm! If you have the know-how using Terminal you can do manually what KextBeast does -do a search for jonathans Blog. KextBeast requires that you first copy the AppleIntelFramebufferCapri.kext file to your desktop.
SOME OTHER NOTES:
There were some posts that recommended getting a Hex Editor and editing the AppleIntelFramebufferCapri.kext file - I assume they meant the version of the file that is used by Yosemite - but I went the easy way.
Hopefully this is helpful,
dc
WUPS - I forgot to mention that I am using an Apple Thunderbolt cable NOT a DisplayPort cable.

Windows 7 Screen Resolution not changing at all when I try to change settings. I ve lost my ToolBar on internet for settings ( deletion of cache) Please help me to reset screen.

Windows 7 Screen Resolution not changing at all when I try to change settings. I ve lost my ToolBar on internet for settings ( deletion of cache) Please help me to reset screen. The screen seems to have slipped or moved to the right. Only icons on left of
screen showing. I Need to regain The right side of the scree
I have tried everything I know to sort this out. Thankyou you in advance. Katy Nanna x

Hi,
When you set your monitor to a screen resolution that it won't support, the screen will go black for a few seconds while the monitor reverts back to the original resolution.
Regarding screen resolution, we may follow the below two articles to change it:
Change your screen resolution
Getting the best display on your monitor
Follow the steps below:
1. Open Screen Resolution by clicking the Start button, clicking
Control Panel, and then, under Appearance and Personalization, clicking Adjust screen resolution.
2.Click the drop-down list next to Resolution. Check for the resolution marked (recommended). This is your LCD monitor's native resolution—usually the highest resolution your monitor can support.
And if the monitor is LCD monitor, The monitor's manufacturer or reseller should also be able to tell you the native resolution for your LCD monitor. Or we may check the monitor's manual to adjust.
Best regards
Michael Shao
TechNet Community Support

Can any one help i have lost safari on my powerMAC g4 and cant figure out how to get it back and safari 5 is not supported on my cumputer

can any one help i have lost safari on my powerMAC g4 and cant figure out how to get it back and safari 5 is not supported on my computer

Make sure there's enough free space on the startup disk.
Right or control click the MacintoshHD icon on your Desktop.
Click Get Info. In the Get Info window you will see Capacity and Available.
Make sure there's a minimum of 15% free disk space.
If there's sufficient disk space, the startup disk may need repairing.
Launch Disk Utility located in /Applications/Utilities
Select the startup disk on the left then select the First Aid tab.
Click Verify Disk (not Verify Disk Permissions)
You will need your install disc if the startup disk needs repairing.
Using Disk Utility to verify or repair disks

Vizio HDTV will not display - Not Support!

Using Arch x86_64
Nvidia 450 GTS
Nvidia 430 GT
So I am trying to output to my Vizio 37" HDTV via HDMI on my 450 GTS, but I always get the error "Not Support!" displayed on my TV. I have 3 monitors configured in nvidia-settings, all 3 are in the "separate X screens" configuration. I have an Acer 23" (DVI) and the Vizio on my 450 GTS and I have a 19" LG (also DVI) on my 430 GT.
I have been able to get this working easily on past distros (ubuntu) but I fear this may have something do with the newer Xorg version from Arch, but I am not sure and would like to work around it if i can. Here is my Xorg.0.log file:
[ 11.961]
X.Org X Server 1.11.3
Release Date: 2011-12-16
[ 11.961] X Protocol Version 11, Revision 0
[ 11.961] Build Operating System: Linux 3.1.5-1-ARCH x86_64
[ 11.961] Current Operating System: Linux TeetoArch 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET 2012 x86_64
[ 11.961] Kernel command line: root=/dev/disk/by-uuid/a581f4d1-b664-4b00-832b-7ad7323d7e0e ro
[ 11.961] Build Date: 17 December 2011 09:17:41AM
[ 11.961]
[ 11.961] Current version of pixman: 0.24.2
[ 11.961] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 11.961] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11.961] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 2 01:51:52 2012
[ 11.971] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 11.984] (==) ServerLayout "Layout0"
[ 11.984] (**) |-->Screen "Screen0" (0)
[ 11.984] (**) | |-->Monitor "Monitor0"
[ 11.984] (**) | |-->Device "Device0"
[ 11.984] (**) |-->Screen "Screen1" (1)
[ 11.984] (**) | |-->Monitor "Monitor1"
[ 11.984] (**) | |-->Device "Device1"
[ 11.984] (**) |-->Screen "Screen2" (2)
[ 11.984] (**) | |-->Monitor "Monitor2"
[ 11.984] (**) | |-->Device "Device2"
[ 11.984] (**) |-->Input Device "Keyboard0"
[ 11.984] (**) |-->Input Device "Mouse0"
[ 11.984] (**) Option "Xinerama" "0"
[ 11.984] (==) Automatically adding devices
[ 11.984] (==) Automatically enabling devices
[ 12.021] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 12.021] Entry deleted from font path.
[ 12.030] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 12.030] Entry deleted from font path.
[ 12.030] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 12.030] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 12.030] Entry deleted from font path.
[ 12.030] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 12.030] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 12.030] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 12.030] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 12.030] (WW) Disabling Keyboard0
[ 12.030] (WW) Disabling Mouse0
[ 12.030] (II) Loader magic: 0x7ccae0
[ 12.030] (II) Module ABI versions:
[ 12.030] X.Org ANSI C Emulation: 0.4
[ 12.030] X.Org Video Driver: 11.0
[ 12.030] X.Org XInput driver : 13.0
[ 12.030] X.Org Server Extension : 6.0
[ 12.031] (--) PCI:*(0:1:0:0) 10de:0dc4:10de:085a rev 161, Mem @ 0xf4000000/16777216, 0xe0000000/134217728, 0xec000000/33554432, I/O @ 0x0000ef00/128, BIOS @ 0x????????/524288
[ 12.031] (--) PCI: (0:2:0:0) 10de:0de1:10de:0828 rev 161, Mem @ 0xf9000000/16777216, 0xd0000000/134217728, 0xde000000/33554432, I/O @ 0x0000df00/128, BIOS @ 0x????????/524288
[ 12.031] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 12.031] (II) LoadModule: "extmod"
[ 12.043] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 12.051] (II) Module extmod: vendor="X.Org Foundation"
[ 12.051] compiled for 1.11.3, module version = 1.0.0
[ 12.051] Module class: X.Org Server Extension
[ 12.051] ABI class: X.Org Server Extension, version 6.0
[ 12.051] (II) Loading extension MIT-SCREEN-SAVER
[ 12.051] (II) Loading extension XFree86-VidModeExtension
[ 12.051] (II) Loading extension XFree86-DGA
[ 12.051] (II) Loading extension DPMS
[ 12.051] (II) Loading extension XVideo
[ 12.051] (II) Loading extension XVideo-MotionCompensation
[ 12.051] (II) Loading extension X-Resource
[ 12.051] (II) LoadModule: "dbe"
[ 12.051] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 12.051] (II) Module dbe: vendor="X.Org Foundation"
[ 12.051] compiled for 1.11.3, module version = 1.0.0
[ 12.051] Module class: X.Org Server Extension
[ 12.051] ABI class: X.Org Server Extension, version 6.0
[ 12.051] (II) Loading extension DOUBLE-BUFFER
[ 12.051] (II) LoadModule: "glx"
[ 12.051] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 12.407] (II) Module glx: vendor="NVIDIA Corporation"
[ 12.415] compiled for 4.0.2, module version = 1.0.0
[ 12.415] Module class: X.Org Server Extension
[ 12.415] (II) NVIDIA GLX Module 290.10 Wed Nov 16 18:01:24 PST 2011
[ 12.415] (II) Loading extension GLX
[ 12.415] (II) LoadModule: "record"
[ 12.415] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 12.426] (II) Module record: vendor="X.Org Foundation"
[ 12.426] compiled for 1.11.3, module version = 1.13.0
[ 12.426] Module class: X.Org Server Extension
[ 12.426] ABI class: X.Org Server Extension, version 6.0
[ 12.426] (II) Loading extension RECORD
[ 12.426] (II) LoadModule: "dri"
[ 12.426] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 12.442] (II) Module dri: vendor="X.Org Foundation"
[ 12.442] compiled for 1.11.3, module version = 1.0.0
[ 12.442] ABI class: X.Org Server Extension, version 6.0
[ 12.442] (II) Loading extension XFree86-DRI
[ 12.442] (II) LoadModule: "dri2"
[ 12.442] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 12.443] (II) Module dri2: vendor="X.Org Foundation"
[ 12.443] compiled for 1.11.3, module version = 1.2.0
[ 12.443] ABI class: X.Org Server Extension, version 6.0
[ 12.443] (II) Loading extension DRI2
[ 12.443] (II) LoadModule: "nvidia"
[ 12.443] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.503] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 12.504] compiled for 4.0.2, module version = 1.0.0
[ 12.504] Module class: X.Org Video Driver
[ 12.513] (II) NVIDIA dlloader X Driver 290.10 Wed Nov 16 17:41:10 PST 2011
[ 12.513] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 12.513] (++) using VT number 7
[ 12.516] (II) Loading sub module "fb"
[ 12.516] (II) LoadModule: "fb"
[ 12.516] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.521] (II) Module fb: vendor="X.Org Foundation"
[ 12.521] compiled for 1.11.3, module version = 1.0.0
[ 12.521] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.521] (II) Loading sub module "wfb"
[ 12.521] (II) LoadModule: "wfb"
[ 12.521] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.532] (II) Module wfb: vendor="X.Org Foundation"
[ 12.532] compiled for 1.11.3, module version = 1.0.0
[ 12.532] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.532] (II) Loading sub module "ramdac"
[ 12.532] (II) LoadModule: "ramdac"
[ 12.532] (II) Module "ramdac" already built-in
[ 12.533] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.533] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.533] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.535] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.535] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 12.535] (==) NVIDIA(0): RGB weight 888
[ 12.535] (==) NVIDIA(0): Default visual is TrueColor
[ 12.535] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 12.535] (**) NVIDIA(0): Option "TwinView" "0"
[ 12.535] (**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select +0+0"
[ 12.535] (**) NVIDIA(0): Enabling 2D acceleration
[ 13.375] (II) NVIDIA(GPU-0): Display (Acer S231HL (DFP-0)) does not support NVIDIA 3D
[ 13.375] (II) NVIDIA(GPU-0): Vision stereo.
[ 13.408] (II) NVIDIA(GPU-0): Display (VIZ VO370M (DFP-1)) does not support NVIDIA 3D Vision
[ 13.408] (II) NVIDIA(GPU-0): stereo.
[ 13.409] (II) NVIDIA(0): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 13.409] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 13.409] (--) NVIDIA(0): VideoBIOS: 70.06.1f.00.01
[ 13.409] (II) NVIDIA(0): Detected PCI Express Link width: 8X
[ 13.409] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 13.409] (--) NVIDIA(0): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0)
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1)
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0): 330.0 MHz maximum pixel clock
[ 13.409] (--) NVIDIA(0): Acer S231HL (DFP-0): Internal Dual Link TMDS
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1): 165.0 MHz maximum pixel clock
[ 13.409] (--) NVIDIA(0): VIZ VO370M (DFP-1): Internal Single Link TMDS
[ 13.410] (II) NVIDIA(0): Display Device found referenced in MetaMode: DFP-0
[ 13.410] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been
[ 13.410] (**) NVIDIA(0): enabled on all display devices.
[ 13.430] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 13.430] (II) NVIDIA(0): Validated modes:
[ 13.430] (II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0"
[ 13.430] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 13.458] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 13.458] (--) NVIDIA(0): option
[ 13.458] (**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
[ 13.458] (==) NVIDIA(1): RGB weight 888
[ 13.458] (==) NVIDIA(1): Default visual is TrueColor
[ 13.458] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
[ 13.458] (**) NVIDIA(1): Option "TwinView" "0"
[ 13.458] (**) NVIDIA(1): Option "MetaModes" "nvidia-auto-select +0+0"
[ 13.458] (**) NVIDIA(1): Enabling 2D acceleration
[ 14.402] (II) NVIDIA(GPU-1): Display (LG Electronics L196W (DFP-0)) does not support NVIDIA
[ 14.402] (II) NVIDIA(GPU-1): 3D Vision stereo.
[ 14.403] (II) NVIDIA(1): NVIDIA GPU GeForce GT 430 (GF108) at PCI:2:0:0 (GPU-1)
[ 14.403] (--) NVIDIA(1): Memory: 1048576 kBytes
[ 14.403] (--) NVIDIA(1): VideoBIOS: 70.08.29.00.01
[ 14.403] (II) NVIDIA(1): Detected PCI Express Link width: 8X
[ 14.403] (--) NVIDIA(1): Interlaced video modes are supported on this GPU
[ 14.403] (--) NVIDIA(1): Connected display device(s) on GeForce GT 430 at PCI:2:0:0
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0)
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0): 330.0 MHz maximum pixel clock
[ 14.403] (--) NVIDIA(1): LG Electronics L196W (DFP-0): Internal Dual Link TMDS
[ 14.405] (II) NVIDIA(1): Display Device found referenced in MetaMode: DFP-0
[ 14.405] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID has been
[ 14.405] (**) NVIDIA(1): enabled on all display devices.
[ 14.425] (II) NVIDIA(1): Assigned Display Device: DFP-0
[ 14.425] (II) NVIDIA(1): Validated modes:
[ 14.425] (II) NVIDIA(1): "nvidia-auto-select+0+0"
[ 14.425] (II) NVIDIA(1): Virtual screen size determined to be 1440 x 900
[ 14.428] (--) NVIDIA(1): DPI set to (89, 87); computed from "UseEdidDpi" X config
[ 14.428] (--) NVIDIA(1): option
[ 14.428] (**) NVIDIA(2): Depth 24, (--) framebuffer bpp 32
[ 14.428] (==) NVIDIA(2): RGB weight 888
[ 14.428] (==) NVIDIA(2): Default visual is TrueColor
[ 14.428] (==) NVIDIA(2): Using gamma correction (1.0, 1.0, 1.0)
[ 14.428] (**) NVIDIA(2): Option "TwinView" "0"
[ 14.428] (**) NVIDIA(2): Option "MetaModes" "DFP-1: nvidia-auto-select +0+0; DFP-1: 1920x1080 +0+0"
[ 14.428] (II) NVIDIA(2): NVIDIA GPU GeForce GTS 450 (GF106) at PCI:1:0:0 (GPU-0)
[ 14.428] (--) NVIDIA(2): Memory: 1048576 kBytes
[ 14.428] (--) NVIDIA(2): VideoBIOS: 70.06.1f.00.01
[ 14.428] (II) NVIDIA(2): Detected PCI Express Link width: 8X
[ 14.428] (--) NVIDIA(2): Interlaced video modes are supported on this GPU
[ 14.428] (--) NVIDIA(2): Connected display device(s) on GeForce GTS 450 at PCI:1:0:0
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0)
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1)
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0): 330.0 MHz maximum pixel clock
[ 14.428] (--) NVIDIA(2): Acer S231HL (DFP-0): Internal Dual Link TMDS
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1): 165.0 MHz maximum pixel clock
[ 14.428] (--) NVIDIA(2): VIZ VO370M (DFP-1): Internal Single Link TMDS
[ 14.429] (II) NVIDIA(2): Display Device found referenced in MetaMode: DFP-1
[ 14.429] (**) NVIDIA(2): Using HorizSync/VertRefresh ranges from the EDID has been
[ 14.429] (**) NVIDIA(2): enabled on all display devices.
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "720x576" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "720x576".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's HorizSync (27.0 kHz); ignoring HorizSync check
[ 14.429] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.429] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.429] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.429] (WW) NVIDIA(2): valid VertRefresh range (50.000-77.000 Hz) would exclude
[ 14.429] (WW) NVIDIA(2): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
[ 14.429] (WW) NVIDIA(2): check for mode "1920x1080".
[ 14.430] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.430] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.430] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.430] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.430] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.431] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.431] (WW) NVIDIA(2): "720x576" is specified in the EDID; however, the EDID's
[ 14.431] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.431] (WW) NVIDIA(2): this mode's HorizSync (15.6 kHz); ignoring HorizSync check
[ 14.431] (WW) NVIDIA(2): for mode "720x576".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 14.432] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid HorizSync range (31.000-70.000 kHz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's HorizSync (27.0 kHz); ignoring HorizSync check
[ 14.432] (WW) NVIDIA(2): for mode "1920x1080".
[ 14.432] (WW) NVIDIA(2): The EDID for VIZ VO370M (DFP-1) contradicts itself: mode
[ 14.432] (WW) NVIDIA(2): "1920x1080" is specified in the EDID; however, the EDID's
[ 14.432] (WW) NVIDIA(2): valid VertRefresh range (50.000-77.000 Hz) would exclude
[ 14.432] (WW) NVIDIA(2): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
[ 14.432] (WW) NVIDIA(2): check for mode "1920x1080".
[ 14.451] (II) NVIDIA(2): Assigned Display Device: DFP-1
[ 14.451] (II) NVIDIA(2): Validated modes:
[ 14.451] (II) NVIDIA(2): "DFP-1:nvidia-auto-select+0+0"
[ 14.451] (II) NVIDIA(2): "DFP-1:1920x1080+0+0"
[ 14.451] (II) NVIDIA(2): Virtual screen size determined to be 1920 x 1080
[ 14.454] (WW) NVIDIA(2): Cannot find size of first mode for Acer S231HL (DFP-0); cannot
[ 14.454] (WW) NVIDIA(2): compute DPI from Acer S231HL (DFP-0)'s EDID.
[ 14.454] (==) NVIDIA(2): DPI set to (75, 75); computed from built-in default
[ 14.454] (--) Depth 24 pixmap format is 32 bpp
[ 14.454] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 14.454] (II) NVIDIA: access.
[ 14.456] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.456] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 14.456] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 14.456] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 14.456] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 14.456] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 14.456] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.456] (II) NVIDIA(0): Config Options in the README.
[ 14.458] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select+0+0"
[ 14.490] (II) Loading extension NV-GLX
[ 14.556] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 14.556] (==) NVIDIA(0): Backing store disabled
[ 14.556] (==) NVIDIA(0): Silken mouse enabled
[ 14.556] (**) NVIDIA(0): DPMS enabled
[ 14.556] (II) Loading extension NV-CONTROL
[ 14.556] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "CRT", but no
[ 14.556] (WW) NVIDIA(0): such display device could be found, or all display devices
[ 14.556] (WW) NVIDIA(0): by that name are currently unavailable.
[ 14.556] (WW) NVIDIA(0): Option "TwinViewXineramaInfoOrder" requested "TV", but no such
[ 14.556] (WW) NVIDIA(0): display device could be found, or all display devices by
[ 14.556] (WW) NVIDIA(0): that name are currently unavailable.
[ 14.556] (II) Loading extension XINERAMA
[ 14.556] (II) Loading sub module "dri2"
[ 14.556] (II) LoadModule: "dri2"
[ 14.557] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.557] (II) Module dri2: vendor="X.Org Foundation"
[ 14.557] compiled for 1.11.3, module version = 1.2.0
[ 14.557] ABI class: X.Org Server Extension, version 6.0
[ 14.557] (II) NVIDIA(0): [DRI2] Setup complete
[ 14.557] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 14.557] (==) RandR enabled
[ 14.559] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.559] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
[ 14.559] (II) NVIDIA(1): configuration option may not be set correctly. When the
[ 14.559] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
[ 14.559] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
[ 14.559] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
[ 14.559] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.559] (II) NVIDIA(1): Config Options in the README.
[ 14.561] (II) NVIDIA(1): Setting mode "nvidia-auto-select+0+0"
[ 14.654] (==) NVIDIA(1): Disabling shared memory pixmaps
[ 14.654] (==) NVIDIA(1): Backing store disabled
[ 14.654] (==) NVIDIA(1): Silken mouse enabled
[ 14.655] (**) NVIDIA(1): DPMS enabled
[ 14.655] (II) Loading sub module "dri2"
[ 14.655] (II) LoadModule: "dri2"
[ 14.655] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.655] (II) Module dri2: vendor="X.Org Foundation"
[ 14.655] compiled for 1.11.3, module version = 1.2.0
[ 14.655] ABI class: X.Org Server Extension, version 6.0
[ 14.655] (II) NVIDIA(1): [DRI2] Setup complete
[ 14.655] (II) NVIDIA(1): [DRI2] VDPAU driver: nvidia
[ 14.655] (==) RandR enabled
[ 14.657] (II) NVIDIA(2): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.657] (II) NVIDIA(2): may not be running or the "AcpidSocketPath" X
[ 14.657] (II) NVIDIA(2): configuration option may not be set correctly. When the
[ 14.657] (II) NVIDIA(2): ACPI event daemon is available, the NVIDIA X driver will
[ 14.657] (II) NVIDIA(2): try to use it to receive ACPI event notifications. For
[ 14.657] (II) NVIDIA(2): details, please see the "ConnectToAcpid" and
[ 14.657] (II) NVIDIA(2): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.657] (II) NVIDIA(2): Config Options in the README.
[ 14.657] (II) NVIDIA(2): Setting mode "DFP-1:nvidia-auto-select+0+0"
[ 14.834] (==) NVIDIA(2): Disabling shared memory pixmaps
[ 14.834] (==) NVIDIA(2): Backing store disabled
[ 14.834] (==) NVIDIA(2): Silken mouse enabled
[ 14.834] (**) NVIDIA(2): DPMS enabled
[ 14.834] (II) Loading sub module "dri2"
[ 14.834] (II) LoadModule: "dri2"
[ 14.834] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 14.834] (II) Module dri2: vendor="X.Org Foundation"
[ 14.834] compiled for 1.11.3, module version = 1.2.0
[ 14.834] ABI class: X.Org Server Extension, version 6.0
[ 14.834] (II) NVIDIA(2): [DRI2] Setup complete
[ 14.834] (II) NVIDIA(2): [DRI2] VDPAU driver: nvidia
[ 14.834] (==) RandR enabled
[ 14.834] (II) Initializing built-in extension Generic Event Extension
[ 14.834] (II) Initializing built-in extension SHAPE
[ 14.834] (II) Initializing built-in extension MIT-SHM
[ 14.834] (II) Initializing built-in extension XInputExtension
[ 14.834] (II) Initializing built-in extension XTEST
[ 14.834] (II) Initializing built-in extension BIG-REQUESTS
[ 14.834] (II) Initializing built-in extension SYNC
[ 14.834] (II) Initializing built-in extension XKEYBOARD
[ 14.834] (II) Initializing built-in extension XC-MISC
[ 14.834] (II) Initializing built-in extension SECURITY
[ 14.834] (II) Initializing built-in extension XINERAMA
[ 14.834] (II) Initializing built-in extension XFIXES
[ 14.834] (II) Initializing built-in extension RENDER
[ 14.834] (II) Initializing built-in extension RANDR
[ 14.834] (II) Initializing built-in extension COMPOSITE
[ 14.834] (II) Initializing built-in extension DAMAGE
[ 14.835] (II) Initializing extension GLX
[ 15.155] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 15.155] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 15.156] (II) LoadModule: "evdev"
[ 15.156] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.161] (II) Module evdev: vendor="X.Org Foundation"
[ 15.161] compiled for 1.10.99.902, module version = 2.6.0
[ 15.161] Module class: X.Org XInput Driver
[ 15.161] ABI class: X.Org XInput driver, version 13.0
[ 15.161] (II) Using input driver 'evdev' for 'Power Button'
[ 15.161] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.161] (**) Power Button: always reports core events
[ 15.161] (**) Power Button: Device: "/dev/input/event4"
[ 15.161] (--) Power Button: Found keys
[ 15.161] (II) Power Button: Configuring as keyboard
[ 15.161] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 15.161] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 15.161] (**) Option "xkb_rules" "evdev"
[ 15.161] (**) Option "xkb_model" "evdev"
[ 15.161] (**) Option "xkb_layout" "us"
[ 15.172] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 15.172] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 15.172] (II) Using input driver 'evdev' for 'Power Button'
[ 15.172] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.172] (**) Power Button: always reports core events
[ 15.172] (**) Power Button: Device: "/dev/input/event3"
[ 15.172] (--) Power Button: Found keys
[ 15.172] (II) Power Button: Configuring as keyboard
[ 15.172] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3/event3"
[ 15.172] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 15.172] (**) Option "xkb_rules" "evdev"
[ 15.172] (**) Option "xkb_model" "evdev"
[ 15.172] (**) Option "xkb_layout" "us"
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event6)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event8)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event9)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event10)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event11)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event12)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.173] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event13)
[ 15.173] (II) No input driver/identifier specified (ignoring)
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/event1)
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: Applying InputClass "evdev pointer catchall"
[ 15.174] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:1025'
[ 15.174] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: always reports core events
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: Device: "/dev/input/event1"
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found 20 mouse buttons
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found scroll wheel(s)
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found relative axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:1025: Found x and y relative axes
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: Configuring as mouse
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: Adding scrollwheel support
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: YAxisMapping: buttons 4 and 5
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 15.174] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.4/1-1.2.1.4:1.2/0003:046D:C52B.0005/input/input1/event1"
[ 15.174] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:1025" (type: MOUSE, id 8)
[ 15.174] (II) Logitech Unifying Device. Wireless PID:1025: initialized for relative axes.
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) keeping acceleration scheme 1
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration profile 0
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration factor: 2.000
[ 15.174] (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration threshold: 4
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/mouse0)
[ 15.174] (II) No input driver/identifier specified (ignoring)
[ 15.174] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4004 (/dev/input/event2)
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: Applying InputClass "evdev keyboard catchall"
[ 15.174] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4004'
[ 15.174] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: always reports core events
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: Device: "/dev/input/event2"
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found 1 mouse buttons
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found scroll wheel(s)
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found relative axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found absolute axes
[ 15.174] (--) Logitech Unifying Device. Wireless PID:4004: Found keys
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Configuring as mouse
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Configuring as keyboard
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: Adding scrollwheel support
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: YAxisMapping: buttons 4 and 5
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 15.174] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1.4/1-1.2.1.4:1.2/0003:046D:C52B.0005/input/input2/event2"
[ 15.174] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4004" (type: KEYBOARD, id 9)
[ 15.174] (**) Option "xkb_rules" "evdev"
[ 15.174] (**) Option "xkb_model" "evdev"
[ 15.174] (**) Option "xkb_layout" "us"
[ 15.174] (EE) Logitech Unifying Device. Wireless PID:4004: failed to initialize for relative axes.
[ 15.174] (II) Logitech Unifying Device. Wireless PID:4004: initialized for absolute axes.
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) keeping acceleration scheme 1
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration profile 0
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration factor: 2.000
[ 15.174] (**) Logitech Unifying Device. Wireless PID:4004: (accel) acceleration threshold: 4
[ 15.175] (II) config/udev: Adding input device raphnet.net GC/N64_USB (/dev/input/event0)
[ 15.175] (II) No input driver/identifier specified (ignoring)
[ 15.175] (II) config/udev: Adding input device raphnet.net GC/N64_USB (/dev/input/js0)
[ 15.175] (II) No input driver/identifier specified (ignoring)
[ 15.175] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 15.175] (II) No input driver/identifier specified (ignoring)
Lines 14.429 - 14.432 are what interests me the most. What I got from it was that the refresh rates weren't set right, but after I changed those values in my /etc/X11/xorg.conf.d/10-monitor.conf file to what this log suggested, it still did not work. Here is that file:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 290.10 ([email protected]) Wed Nov 16 18:46:42 PST 2011
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 1920 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" LeftOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Acer S231HL"
HorizSync 30.0 - 80.0
VertRefresh 55.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor1"
VendorName "Unknown"
ModelName "LG Electronics L196W"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 75.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor2"
VendorName "Unknown"
ModelName "VIZ VO370M"
HorizSync 27.0 - 70.0
VertRefresh 24.0 - 77.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTS 450"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GT 430"
BusID "PCI:2:0:0"
EndSection
Section "Device"
Identifier "Device2"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTS 450"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-0: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "Device2"
Monitor "Monitor2"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP-1: nvidia-auto-select +0+0; DFP-1: 1920x1080 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
I am really out of ideas, I know the tv works inputs work fine because I watch tv on it (!). Does anyone have any suggestions?

cteeto wrote:
Fixed
HDMI cable was bad.
Edit your first post and change the thread title so that it has [Solved] in it.
Good to know that it was a simple fix - sometimes the most overlooked things lead to much frustration!

HDTV Resolution not supported, Desktop lost

Similar Messages

Maybe you are looking for