HT4682 Hwy is the XDCAM not supported???

Why is the XDCAM not supported? Anyone have any ideas about this most epic fail in FCPX.

Tom,
Sorry about this post. I use a few different cameras in my work and the XDCAM is the most user friendly of the bunch. It would seem though, every time I would ingest the footage on to my mac pro 2009-2012 using the XDCAM transfer software fCPX would crash and crash and crash until I stopped trying to import it. After a couple hours of frustration and trouble shooting, I finally figured out that it had nothig to do with XDCAM or FCPX. The crash was related to an old piece of firewire hardware and its driver. The hardware culprit was the M-audio FIrewire 410 series. Upgraded to the newer Profire series and Viola. Sorry about lashing out at FCPX. It really is a great program.

Similar Messages

I have problem with fonts for my site, i have used "Lucida sans unicode " family for certain texts. it shows perfect in mozilla 3.5 and mozilla 4. But the font not supporting in mozilla 5.0? please help me

i have problem with fonts for my site, i have used "Lucida sans unicode " family for certain texts. it shows perfect in mozilla 3.5 and mozilla 4. But the font not supporting in mozilla 5.0? please help me

i have problem with fonts for my site, i have used "Lucida sans unicode " family for certain texts. it shows perfect in mozilla 3.5 and mozilla 4. But the font not supporting in mozilla 5.0? please help me

What are all the features not supported in SQL Server 2012 trial version?

What are all the features not supported in SQL Server 2012 trial version?

The evaluation edition supports all features and expires after 180 days.
https://msdn.microsoft.com/en-us/library/cc645993.aspx?f=255&MSPPError=-2147217396

AirDrop on my MacBook Pro but not on my Desktop MacPro (Quad-Core Intel Xeon). Does the desktop not support it?

AirDrop on my MacBook Pro but not on my Desktop MacPro (Quad-Core Intel Xeon). Does the desktop not support it? What gives?

See if your Mac model supports it:
http://support.apple.com/kb/HT4783
Thanks ... Ken

Why does the iPad not support flash player? I would like to watch programming from att uverse but cannot because of this restriction

Why does the iPad not support flash player? I would like to watch programming from att uverse but cannot because of this restriction

Because NOTHING that is iOS supports Flash. Never has never will.
The only possible option is to try the Skyfire browser from the App store. It is an internet browser that converts flash to HTML 5 so that you can attempt to view it on iOS devices.
I have never tried it so I can tell you if it is any good, but it has gotten decent reviews.

Video sizes provided by the device not supported.

Hey guys,
I am trying to use FME to run a live broadcast of my desktop
PC on www.justin.tv. I have an 8800GT with forced s-video out on my
desktop, running to an HP ExpressCard TV Tuner on my HP Laptop. The
TV tuner lights up when it is plugged in, and I can receive video
via Windows Media Center (while browsing for TV signals, satellite
then svideo input) so I know that part is working. I'm trying to
use FME to pick up this input (like a capture card) from my desktop
and broadcast it on justin.tv. However, it seems like no matter
what I do, it always reports "unexpected problem encountered" and
says "video sizes provided by the device not supported."
Do I just have to bite the bullet and get a real capture
card, since this TV tuner is probably incompatible? I heard
something about FME needing raw video for input, rather than
something encoded, and I think this tuner encodes into MPEG
something or other automatically. Could someone suggest an
affordable and easy to use capture card for someone with limited
technical knowledge that will work flawlessly with FME?
Thanks for your time!
-Cameron

Then your Canon video camera is not really HD to the core
definition. It seems Canon (and everyone else for that matter),
tweak their statistics in order to say something to help boost
sales-and it works for them.
Use the DV option and you can stream live to the best of
your little canon's ability. The only sizes that pop up on your
select a size list, are the sizes that that camera can handle.
3.0-don't hold your breath thinking that 3.0 is going to
solve too many problems. Remember, it's still a free platform, and
Adobe or anyone else-will only give so much away for free. The
trick is to buy the $4,500 version and the World is yours.
Anyway, good luck Monty!
Happy Holidays,
Dirty South TV

Can you turn off the "Charging not supported with this device" messages?

I recently bought a standard dock extender cable in order to connect my iPad to my Apple HiFi and have had music from Pandora constantly interrupted by sporadic "Charging not supported with this device" messages. The messages will continue to come up repeatedly despite pressing the "Dismiss" bar repeatedly.
Is there a way to turn those kinds of warnings off in either iPad Settings or in iTunes when docking the iPad?

Try connecting the iPad to the iPod Hi-Fi with a male to male mini-stereo cable. I use one of these cables to connect my Airport Express to my iPod Hi-Fi, so that I can use it with AirTunes.
You can even combine the cable with the Apple iPad Dock, which would let you charge the iPad while using it with the iPod Hi-Fi.

Why having problems with the sim, not supported carrier?

My provider Orange UK has allowed me to unlock my iphone and has send to me all the steps. WHen trying to unlock my iphone, it gives me this message error
" The SIM card that you currently have installed in this iphone is from a carrier that is not supported under the activation policy that is currently assigned by the activation server. This is not a hardware issue with the iphone. Please insert another SIM card from a supported carrier or request that this iphone be unlocked by your carrier. Please contact Apple for more information"
I bought a non Orange 3G sim card as they mentioned and there is this message. Anyone can help me to unlock my iphone?
THanks!

Have you followed all the steps for unlocking your iPhone, as listed here?
http://support.apple.com/kb/HT5014
If so, did you get the "your iPhone has now been unlocked" message after you restored the iPhone?

Why is the c5180 not supported in the eprint/mobile print apps?

HP C5180 All in one iOS for iPhone and iPad I used to be able to print to my printer when I had iPrint on my iPhone but I upgraded to the eprint app and now I can't print

This only means that HP's enhanced web printing feature is not available in Firefox, as it had been in the past. All it allowed you to do was select portions of websites and then print them.
You can continue to print websites normally in Firefox using an HP printer.

"Mode not supported" freezes AppleTV Gen3 on Samsung 61in DLP. AppleTV is ok when moved to another TV... Help me get it back online with the Samsung?

I just hooked up the AppleTV Gen3, and it worked great on my 61in Samsung DLP TV that should do 1080i. When I looked at the resolution settings in the AppleTV menu, it said 720i. I tried to change the resolution in the settings menu, and it came back with a message "mode not supported..." I was able to initially get back to the menu and choose what I thought was a supported resolution (1080i), and it again displayed the same message, this time freezing the AppleTV. I could no longer communicate with the AppleTV device although the remote was working fine.
I tried most solutions that I read on the support forums. So far nothing has worked ie changing HDMI inputs, removing power, etc. I moved the AppleTV to another Samsung TV, and it worked fine - and I was able to adjust the resolution. When I returned to the orignal Samsung it again displayed the "mode not supported" menu and it remains frozen. Any solution? Will a reset back to factory settings help - or am I stuck? Frustrated. Help?

Same thing happened to me with my peruvian credit card in the peruvian app store, I want to buy an app, but it says that my credit card is "not supported in the Peruvian app store"

MacBook Mini-DVI to VGA - Samsung 32" LCD - Mode Not Supported

I followed the instructions on Apple's site to use the MacBook with the lid closed and an external LCD. It worked perfectly the first time I tried it. (I believe in 1920 x 1024). It seemed a little hard to read so I changed the Display resolution, then encountered the "Mode Not Supported" on my LCD. I unhooked and used my MacBook to change the settings back, but the MacBook seems to revert to the "Mode Not Supported" resolution when I close the lid. Any suggestions? Can I reset the Display Preferences on my MacBook?

I think this procedure should work, but it requires an external USB keyboard.
- Shut down the Mac.
- Have all the following connected:
- MacBook power supply
- External display
- USB keyboard and mouse
- Open the lid on the MacBook and hit the power button.
- Immediately close the lid on the MacBook and start holding down the Shift key on the USB keyboard.
- Release the Shift key once you see the spinning gear on the gray screen on the external display.
The above procedure should cause the Mac to start in Safe mode and hopefully will finish booting into a useable screen. If that is the case, go into Displays preferences and select a known working resolution different from the one the Mac started up in under Safe mode. Now restart normally. Hopefully the newly selected resolution will persist through the normal restart and you will have a working external screen again.

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!

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!

HELP!!! "Charging is not supported with this accessory" suddenly happening CONSTANTLY with iphone 4

Suddenly without warning my IPhone 4 has been giving me a "charging is not supported with this accessory error" every time I plug it into ANY charging device. That means my car charger, USB to the PC... USB to a macbook pro... Directly to the wall with the included charger, etc. It doesn't matter. I guess I'm past the 1 year warranty so Apple is not any help. Essentially I'm supposed to accept that my $200 (with a contract) phone has a 1 year life span and that I should be completely fine with it becoming useless out of nowhere. Here's some facts.
#1 - It has nothing to do with 3rd party accessories. One day it was working... one day it wasn't.
#2 - I cleaned lint out of the charging port on the phone. That was the first thing I tried. I used compressed air to blow it out, I used a soft bristle tooth brush... It's lint free. It has nothing to do with lint. I understand this is the most likely cause of the problem.
#3 - When I plug it into a PC or macbook via USB, I'm able to access the IPhone 4 like I ALWAYS have. In other words, I can see pictures, I can back up the phone, I can restore the phone, I can transfer music, sync, etc. So this would presumably rule out the idea that it's the dock connector, right? Why would USB work, but the charging function will NOT work?
#4 - On that note, I was able to update the software to the latest version 5.1.1. That was one of the first things I tried. No dice. I still get the "charging not supported with this accessory" error literally every time I plug it in with a yellow triangle icon... Seen here for example: http://tapatalk.com/mu/4c5f44af-af20-d86c.jpg .
#5 - So since it's not charging, the phone inevitably dies. Here's the weird part... if I leave it plugged into the wall/pc/mac/car when it's dead... eventually it will charge enough to turn back on. But once it's back on... that **** error will pop back up, it will stop charging... and inevitably die again. So then... that would suggest that it actually IS capable of taking a charge... it's just that something in the software is preventing it from charging when the software is active, no? Am I off base here?
#6 - So I decided I'd take it to the genius bar to have them look at it. Right before I did that, I got the brilliant idea to try using an alcohol swab on the dock connector just to make sure it was super duper extra clean. Oddly enough, it suddenly started working without the error. It was working on every charger I tried. Wow. I thought I had fixed it. A day later it started happening again, though. Bizarre. I've tried the alcohol swab thing again and it didn't make a difference... maybe it was just a fluke.... the one day I take it to the Apple genius bar and it works. Go figure, right?
#7 - The only helpful thing the tech at the Apple Genius Bar was able to tell me was that the phone did NOT have any kind of water damage. That rules that out. No water damage in the charging dock OR the headphone jack. So there's that.
#8 - Since it's no longer under warranty... I took it upon myself to buy a replacement battery via Amazon.com and installed it myself. Didn't make a difference... still the same error.
What, if anything, can I try? Could it really be the dock connector? Should I try replacing the dock connector? Is there any software-related thing I can try? Has this happened to anyone else? Apple has essentially told me it's my problem. From my perspective... any product that randomly stops working a little over a year is a faulty product. I'm not pleased at all.

Tried at least 6 different cables. It isn't the cable. All of them worked one day... then stopped working the next day. My girlfriend has an identical Iphone 4 and all of the cables still work for her.
Interesting point on the data and power using different pins. So your suggestion would be to replace the dock connector? Found this on Amazon: http://www.amazon.com/Apple-iPhone-dock-connector-cable/dp/B003UGVOO2/ref=sr_1_1 ?ie=UTF8&qid=1338277549&sr=8-1 ... and found a tutorial online: http://www.ifixit.com/Guide/Installing-iPhone-4-Dock-Connector/3147/1#.T8SG_sXWu -o ... Sounds like that might be my best bet here.
It's just odd to me that the phone gives me that error and refuses to charge... then inevitably dies. But once the phone is dead, it starts charging enough to actually turn back on. Isn't that slightly odd?

LCD Panel not supported (acpi brightness)

Hi all,
This is my first post, Hello! I have used several distros but this is my first time using Arch.
I have a dell d420 (dual core / intel graphics). I have installed Arch with lxde / compiz.
Things have been going pretty well so far, I really like the distro. However, I am having problems with laptop-tools and adjusting the brightness of my lcd on AC acpi events.
Basically, I have /etc/laptop-mode/conf.d/lcd-brightness.conf configured as follows:
# Should laptop mode tools control LCD brightness?
CONTROL_BRIGHTNESS=1
# Commands to execute to set the brightness on your LCD
BATT_BRIGHTNESS_COMMAND="echo 20"
LM_AC_BRIGHTNESS_COMMAND="echo 70"
NOLM_AC_BRIGHTNESS_COMMAND="echo 100"
BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"
Further, laptop-mode is running and set up as a daemon.
The problem is when I plug/unplug the power cable the brightness of the panel does not change in the way I would expect it to. Sometimes it does not change at all, sometimes it gets brighter on battery than it does on AC!!! The brightness keys on my laptop work fine (however, they are I believe prgrammed into the bios and rely on no software to adjust the panel.)
Things I have installed / setup:
acpid
acpi
laptop-tools
I have noticed that there seems to be a problem recognising my panel, when I do a
cat /proc/acpi/video/VID/LCD/brightness
I get the response:
<not supported>
Also:
cat /proc/acpi/video/VID/LCD/info
device_id: 0x0400
type: UNKNOWN
known by bios: no
I think this is the problem, as laptop-tools and acpi seem to be configured correclty apart from this issue. Any thoughts?
Many, thanks.
Last edited by e-dard (2008-10-25 16:11:37)

OK, it looks like others have had a similar issue with the NVS 3100M adapter. I found this prior post:
I followed the advice there and installed the 32 bit A08 driver that I found here:
Now the backlight works fine on startup. Unfortunately my system has lost some other small functions and seems a bit slower, however, at least I can now work while I travel.
It's a bit disappointing that newer drivers seem to break my computer. I'd very much like for that not to happen.
Some steps of this, like updating the BIOS and installing the driver were a bit complicated, so I'm happy to give advice on how to do that if anyone needs. In the meantime if anyone has a better way to fix this, I'm keen to find out.

HT4682 Hwy is the XDCAM not supported???

Similar Messages

Maybe you are looking for