[GeForce 6] prince of persia= 6600gt is not supported

ı have msi nx6600gt 128 agp videocard. when ı start prince of percia, it shows error 6600gt not supported this game.
prince of percia game in msi nx6600gt box. ı was shochked.
what are your opinions about this event?
(excuse me ı speak english only bit)
msi k8n neo platinum
amd 64 3000+ s754
512 mb pc3200 twinmos 400mhz ddr

Quote from: MacBrave on 01-March-05, 03:34:17
I had the same problem with my 6600GT and POP, so I applied the patch. The game started but the tearing was so bad in the menu screen you couldn't play. Ended up having to set the vsync option in the drivers to 'OFF' instead of 'application-controlled'. This cleared up the problem.
Thats sounds more like a driver issue... try with another version..

Similar Messages

Audigy Se & Prince of Persia Forgotten Sands!!!!!

Hi AlL....
Somone help me...
Today i installed Prince of persia Forgotten sands in Xp Sp3.... The game sound is muffled[lack of detail & treble bass is good] while playing, but on cutscenes it's good but low audio output through out the game..... Installed drivers" Daniel Support pack 2.7"... But Badcompany 2 , Split a second and Blur has no problems sound was brilliant, had these muffled audio in some games too eg: X-men, Call of Juarez and most wanted.... But Tried these games on windows 7 no problems with sound quality... Direct X updated to latest... any idea is it with direct sound or anything.... Plz hel pme!!!
Any Audigy Users......

Source
Your computer
must meet or exceed these minimum requirements:
Operating System: Windows 98 SE/ 2000/ ME/ XP (ONLY)
Processor: 800 MHz Pentium III or AMD Athlon
Memory: 256 MB of RAM
Video Card: 64 MB GeForce 3 or higher, or ATI Radeon 8500 or higher,
Matrox Parhelia. (GeForce4 MX not supported)
Sound Card: DirectX 9.0 or higher compatible sound card
DirectX: Versions 9.0 or higher (included on game disc)
Hard Drive Space: 1.5 GB minimum hard drive space
CD-ROM: 16X or better (not recommended for use with CD-RWs)
Additional Supported Peripherals: ThrustMaster FIRESTORM Dual Analog
3
Controls: Windows-compatible keyboard and
mouse

Prince Of Persia Sands Of Time Detection

I Have an MSI GForce4 MX440 with AGP 8x 64MB. i just bought Prince of persia sands of time, and the game is not detecting my graphics card. ive tried installing the latest drivers from MSI. but there is no difference. the game requires a GForce 3 equivalent card as minimum. so i dont understand why it isent detecting the gfx card. My system specs are given below. Could someone please please please help me out here.

Source
Your computer
must meet or exceed these minimum requirements:
Operating System: Windows 98 SE/ 2000/ ME/ XP (ONLY)
Processor: 800 MHz Pentium III or AMD Athlon
Memory: 256 MB of RAM
Video Card: 64 MB GeForce 3 or higher, or ATI Radeon 8500 or higher,
Matrox Parhelia. (GeForce4 MX not supported)
Sound Card: DirectX 9.0 or higher compatible sound card
DirectX: Versions 9.0 or higher (included on game disc)
Hard Drive Space: 1.5 GB minimum hard drive space
CD-ROM: 16X or better (not recommended for use with CD-RWs)
Additional Supported Peripherals: ThrustMaster FIRESTORM Dual Analog
3
Controls: Windows-compatible keyboard and
mouse

Prince of Persia 3D on FX5200-128

Hi ,
:-]]]ALL games are fine, EXCEPT with Prince of Persia 3D(NOT sands of time), it crashes after the first movie logo . The only way to run POP3D is to disabling "direct draw" . the game grafics are still OK, but is soooo slow.
Thanks for your attention.

Hi ,
I tested the game with my old vodoo 3 3000 and the game goes perfectly . But with my Geforce FX 5200 the game crashes . I think it could be a "opengl" or "direct3d" configuration of my geforcefx5200, but I don´t know how options try first(so much combined options ).
:idea:One final question, Is that a problem if I put my old vodoo 3 3000 in the same computer with geforcefx5200???
Sorry for my english, I´m from Brazil.
Thank you.

Audigy 1 Platinum and Prince of Persia:Warrior Wit

Ok, I have an Audigy Platinum. I recently updated to the latest drivers and everything. I usually don't like updating the drivers for this card, but i recently had to due to PowerDVD6 sound not working correctly in 5.. Well I fixed the PowerDVD6 problem, and now have a new problem. I recently installed Prince of Persia :Warrior Within, and once passed the UBI soft logo, the sound shuts off, and I'm left without sound. I also noticed that when I ALT-TAB back to the desktop, I go to my AUDIO HQ, and check the EAX Control panel, and its empty, no presets, or environments.. All I wanna know is, WHAT DO I DO?!!!!
I would hate to have to purchase a new Card, even I understand this is an older card..
Please Help!!:angry:

I have the same problem, is there some way to change the language settings?
Edit:: press the i (info button) then press twice the first button, you can choose languages by clicking the right flag
Message was edited by: Emiel187

Nx6600 td256e meeting prince of persia.helppppppp

hello there.i just purschaced msi nx6600 td256e and i tried to play the game that it was in the package (prince of persia sands of time).the card was successfully installed on the motherboard with the latest drivers and direct x.when i installed the game and tried to play a window occured that said that this card was not supported by the game and that i will have problems.what is going on please help me.

Download the latest patch for the game at http://www.ubi.com/US/Downloads/Info.aspx?dlId=727 (50 kb). That fixes the compatibility issues with the never GF6 cards .

Photoshop CS6 3D not supported by my NVIDIA GeForce 9400 256MB graphics card

Hey I am trying to use CS6 Photoshop 3D options and when I open Photoshop it says my graphics card is not supported for 3D, it say I need a graphics card that has 512 MB of vRAM. Can I update my MacBook Pro or am I SOL?

Welcome to the Apple Support Communities
The MacBook Pro has got a soldered graphic card, and in your case, you have an integrated card which doesn't work properly with these type of apps. Unfortunately, it's not possible to replace this card

P4M890M Intial bootup giving me error message "Bus Processor is not supported"

Barebones Desktop Specs;
P4 631 3Ghz HT 2M 800FSB Sock 775 w/Masscool 8W0141B 3.6Gz Cooling Fan
MSI P4M890M-L Socket 775 MB w/ 450 watt power - MSI Case w/Extra Cooling
Hitachi 250GB EIDE HD w/ HD Cooler
XFX GeForce 6200 Turbo Cache 256MB PCIe
2 - Ultra 512 PC4200 DDR2 533Mhz
NEC AD-7170 18X DVD/CD RW
Samsung CD 52x
Utra 3.5 Floppy Drive w/ All-In-One USB2.0 Reader
USB2.0/1394 8pt PCI Card/Comb
XP Pro SP2
Trend Micro 07 Internet Security Suite
PLEASE HELP!! I just purchased this Barebone Computer Kit from Tiger Direct to replace my wife's laptop which is dying. I finally have all the parts to assemble it and start it up. When I purchased the kit "Online" it was sold as a "All Systems Tested and Fully Compatable System".
I was having problems cold booting this computer for the first time. I have now resolved that issue and found the source of the problem in the bootup process itself. Evidently all is not well and fully tested and compatable as Tiger Direct says it is. As the computer boots up for the very first time, you have only 3-4 minutes to tell it weather or not to proceede with installing the following message. I have taken the time to copy the message exactly as it is displayed on my computer screen. I of course will be calling Tiger Direct's Tech Support Line. I have found them to be only as good as the person who answers the phone. Being I'm green anyhow and won't know weather or not I'm being feed a line of BS or not, I thought I'd get some other opinions from folks who understand Computers far better than I. I'm simply firefighter who is trying to buy his wife a decent computer without spending an arm and a leg. In fact I thought this thing would arrive already assembeld and all I needed to do was add an OS and some extras, like a decent video card. I never intended to build this thing from scratch, I could have purchased a simular spec'd Gateway complete with OS preinstalled with a warrenty for less money!!! I'm Not Happy and Not a Techie!! But looking on the bright side, I sure am learning a lot about computers! If I can get it to work without too many more problems I will be very happy.
When the computer first boots, here is the message that appears on the screen;
AMIBIOS C 2005 American Megatrends Inc
BIOs Date 8/25/06 24:17:51 Ver A7255VMS V1.0
Intel Pentium 4 CPU 3.00GHz Speed 266x12 =3200
Hyper Threading Enabled
DDR2 Speed 533MZ
A 200 MHz System Bus Processor is Installed
This Processor Is Not Supported On This Board And Will Run At A Reduced Processor Clock Speed. System Performance Will Be Impacted.
Do You Wish To Continue To Boot @ 266MHz
System Bus And Reduce Processor Speed (Y/N)
Press (Y) To Continue (N) to Shut Down
If I press the Y the computer will run and not shut off in 3 minutes. I let it run last night to see what would happen?? Would it burst into flames?? Would it shut down?? Well after a hour it shut down. Is that normal? Is it some kind of saftey mechinism?
It will start right up again, but it was almost 5am so I shut er down and went to bed. I'm waiting for some advice before I move forward from here. Please respond ASAP! I'd like to get this thing done so I can move on to the next 'Honey Do' project.
This is my first computer I have ever built so I am green to all this. I dont really understand what all this means and what kind of an impact will this have on my new computer??
1. What does this mean, my CPU is not compataible to this board?
2. If I keep it and install it, will it cause the computer to be unstable latter on?
3. How much of a negitive impact will this have on my computer?
4. How much will it slow it down?
5. What would you do if you were in my shoes? Replace the CPU for the right one or upgrade to a better one or keep it??
6. If I do upgrade, what would be a better choice and not break the bank??

:no-idea: Thanks Dry Heat,
I went to the link that you provided. Here is the latest problem...... I can get the computer to run longer than 3 minutes by pressing the Y key when asked during the initial boot-up. After that the computer will not move off that window I described in my 1st post, no matter what I do. I tried restarting the computer and pressed the Delete key to see if that would work and the F1 and F2 keys during the initial boot up, the Bios Window would appear but the computer would shut down, there was nothing I could do to get past this, let alone go on-line to download something. How would I get on-line without an operating system to update the Bios? Remember I am Green and have no idea what the heck I'm doing, let alone what is the real problem here. Its like fighting fire blindfolded! Please help and be detailed on how I should procede. Thanks! Woody

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!

G5 with samsung 52" tv Mode not supported

Does anyone know how I can make my Powermac G5(single 1.8 ATI Radeon 9800pro) work with my Samsung 52 inch TV at HD resolution
I am attempting to convert my old Powermac G5 into a media computer. At some point I may want to add a blu-ray drive.
When I use the DVI on the G5 with a DVI to VGA adapter and connect to the TV via its VGA input. There is no picture and the TV says "mode not supported".
When I connect a second monitor to the ADC (via ADC to DVI) I can get the G5 to show up on the TV in mirror or extended mode (if I set the resolution to 1024 x 768 or less).
I have tried hocking up a monitor via VGA, setting the resolution to 1024x768, then shut done, restart with TV attached and still "mode not supported"
I have also tried making the TV as the main desktop in extended mode then restarting without the second monitor and still "mode not supported"
I tried a DVI to HDMI adapter but I got nothing "searching for signal" I would assume this should work so it might have been bad so I am going to exchange it and get a new one and try that.
?

I had to do the same, that is, accept a lower resolution for my LCD TV.
Using a Geforce 6800 GT, I have an interesting mix of "i" and "p" resolutions, but, as with the 9800 Pro, no 1920x1080p.
Just as well, though, as I couldn't read the text at highest resolution.
I'm pretty sure that this is simply a case of the high resolution 16:9 ratios not being supported in these older cards.
The resolutions that are available in the firmware of the cards are predominately for 16:10 ratio screens.
Remember, HDTV is a lot newer than most all AGP graphics cards.
I guess, when I have time, I'll have to play with DisplayConfigX and see if there is hope.

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!

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which als

I have tried to view videos created in premiere elements 10 and I get the following message: "this file type is not supported, or the required codec is not installed. When it opens there is a red screen in the monitor panel with Korean writing which also appears in the place of each clip in the video. I tried uninstalling and reinstalling premiere elements 10, but that did not have any effect on the video. Do you have any suggestions? I researched codec, but do not understand them at all.

gloucester
In case you did not find it, the following is a copy/paste of the Announcement on Premiere Elements 19/NVIDIA GeForce
that appears at the top of this forum.
Premiere Elements 10 NVIDIA Video Card Driver Roll Back
If you are a Premiere Elements 10 user whose Windows computer uses a NVIDIA GeForce video card and you are experiencing
Premiere Elements 10 display and/or unexplained program behavior, then your first line of troubleshooting needs to be rolling
back the video card driver version instead of assuring that it is up to date.
Since October 2013 to the present, there have been a growing number of reports about display and unexplained workflow
glitches specific to the Premiere Elements 10 user whose Windows computer has a NVIDIA GeForce video card. If this applies
to you, then the “user to user” remedy is to roll back the NVIDIA GeForce video card driver as far as is necessary to get rid of
the problems. The typical driver roll back has gone back as far as March – July 2013 in order to get a working Premiere
Elements 10. Neither NVIDIA nor Adobe has taken any corrective action in this regard to date, and none is expected moving forward.
Since October 2013, the following thread has tried to keep up with the Premiere Elements 10 NVIDIA reports
http://forums.adobe.com/thread/1317675
Older NVIDIA GeForce drivers can be found
http://www.nvidia.com/Download/Find.aspx?lang=en-us
A February 2014 overview of the situation as well as how to use the older NVIDIA GeForce drivers for the driver roll back can be found
http://atr935.blogspot.com/2014/02/pe10-nvidia-video-card-roll-back.html
ATR

ITunes 7.4.1.2 does not support vista-utimate 64-bit.

[quote]Microsoft Windows Vista Professional (Build 6000)
MICRO-STAR INTERNATIONAL CO.,LTD MS-7235
iTunes 7.4.1.2
CD 驱动程序不可用
CD 驱动程序 DLL
UpperFilters: GEARAspiWDM
当前用户不是管理员。
视频显示器信息：
NVIDIA, NVIDIA GeForce 8600 GT
已连接的设备的信息：
磁盘驱动器, ST3250820AS ATA Device, Channel 0, Target 0, Lun 0
CD-ROM Drive, TSSTcorp CD/DVDW TS-H652D ATA Device, Channel 0, Target 0, Lun 0
有些电脑需要对 ATA 或 IDE 总线驱动程序或 Intel 芯片组的更新。如果 iTunes 在导入或刻录 CD 时，不能识别 CD，暂停或死机，请查看您的电脑或主板制造商的支持网站。
扫描 CD/DVD 驱动器时失败，错误 2500。
虚拟驱动器有时会干扰 iTunes 读写 CD。如果这是一个虚拟驱动器且其他驱动器发生问题，那么请尝试卸载虚拟 CD 应用程序。
H: 不支持的 CD 或 DVD 驱动器。
虚拟驱动器有时会干扰 iTunes 读写 CD。如果这是一个虚拟驱动器且其他驱动器发生问题，那么请尝试卸载虚拟 CD 应用程序。
[/quote]
yep, but it seems you can only use it as an administrator, but nowhere you can log in AS an adminstrator. sofar you get the notification that your ITune is not properly installed, so you can not burn your stuff..
tell me how to do this, apple people?
now I have back to the version of 7.3.2.6,no problem at all!!!

iTunes is not supported on any of the 64-bit versions of Windows, so you will not be able to get any official assistance from Apple (and they don't provide any technical support in the Discussions anyway; these forums are, with rare exceptions, user-to-user only). You can search the forum for "64-bit" and see what people are suggesting in other threads. One suggestion I've seen is that you need the 64 bit Gear drivers. You can download them from here:
http://www.gearsoftware.com/support/drivers.cfm
Hope that helps.

I own Final Cut Pro 6 and have been running it on an older G4 tower. I upgraded to a MacPro tower and the app will not install. I get a message "Not supported on this computer" cannot believe this. Help anyone.

I own Final Cut Pro 6 and have been running it on an older G4 tower. I upgraded to a MacPro tower and the app will not install. I get a message "Not supported on this computer" cannot believe this. Help anyone.

Here are the min. system requirements.... it looks like you meet them.... but I may have missed something...
Final Cut Studio 2 (Including Final Cut Pro 6)
• A Macintosh computer with a 1.25GHz or faster PowerPC G4, PowerPC G5, Intel Core Duo, or Intel Xeon processor
• 1GB of RAM
• An AGP or PCI Express Quartz Extreme graphics card (Final Cut Studio is not compatible with integrated Intel graphics processors)
• A display with 1024-by-768 resolution or higher
• Mac OS X v10.4.9 or Mac OS X v10.5.5 or later
• QuickTime 7.1.6 or later
Additional Recommendations
• 2GB of RAM when working with compressed HD and uncompressed SD sources
• 4GB of RAM when working with uncompressed HD sources
• A display with 1280 x 1024 resolution or higher
Additional Requirements for Motion
• A standard or built-to-order system configuration with a NVIDIA GeForce 5200, FX Go5200, FX 5200 Ultra, 6600, 6600 LE, 6800, 7300, 7300 GT, 7800, 7600 GT, 8600, 8800 or Quadro class graphics card.
• A standard or built-to-order system configuration with a ATI Radeon 9800, 9700, 9600Pro, 9600XT, 9700Pro, X800, X1600, X1900, or X2600 class graphics card; or a ATI Mobility Radeon 9700 or 9600 graphics card.
• For 16- and 32-bit rendering: a graphics card with at least 128MB of VRAM.
Additional Requirements for Color
• The standard graphics card in any Mac Pro, 17-inch MacBook Pro, 24-inch iMac, or 2.5GHZ or faster Power Mac G5 Quad:
• ATI Mobility Radeon X1600
• ATI Radeon X1600
• NVIDIA GeForce 7800 GT, 7600 GT, 7300 GT, 6800 Ultra DDL, 6800 GT DDL, 660, or Quadro FX 4500.
• For 32-bit rendering: a graphics card with at least 256MB of VRAM.
• A display with 1680-by-1050 resolution or higher (excluding 20" iMac); dual displays are highly recommended.
• A three-button mouse for full functionality
Apple article on Final Cut Studio 2: http://support.apple.com/kb/SP535

Premiere Elements V4 does Not Support Matrox Parhelia 128mb Vid Crd - What video card should I get?

Premiere Elements V4 does not support Matrox Parhelia 128bm Video Card. Is there a recommended card that will work?
I have an Asus P2B Mother Board. Many thanks for any feedback.

Welcome to the forum.
About any current card, with good driver support, should work fine. The amount of VRAM is not that important, but I would go with ~ 1GB. The driver support is the main factor.
I am running PrE 4.0 and PrPro CS 2 Production Studio on my laptop w/ an nVidia GeForce 8800M GTX - 512GB VRAM, with no issues. That card/chip is a bit old now, and obviously the VRAM is less, than I mentioned, but to "future-proof" the computer a bit, the ~ 1GB VRAM would possibly help.
Good luck,
Hunt

[GeForce 6] prince of persia= 6600gt is not supported

Similar Messages

Maybe you are looking for