MBP to Vizio HDTV

I am having an issue trying to hook up my MBP to my Vizio e470vle hdtv via mini display port to hdmi. I've read many dicussions on this topic but it seems that when someone finds the answer then they fall off the face of the planet. Can someone please give me some ideas

Ok. So I bought a new mini display port to hdmi and it works like a charm. Turns out that some third party adapters aren't all there cracked up yo be. you get what you pay for i suppose. Thanks Mac Cafe!!!!!! There's the answer. go to preferences/sound/output and choose the tv audio. Enjoy!

Similar Messages

Why does my Vizio hdtv say no signal when I connect my minidisplay port to hdmi cord between my macbook pro and tv?

My Vizio hdtv says "No Signal" when I use my mini displayport to hdmi cord. It worked flawlessly for a month but randomly decided to no longer work.
I am using a macbook pro from early 2011 running os x Lion 10.7.5 and a thunderbolt to hdmi cord. The cord has worked without a hitch the numerous times I've used it until recently. Now plugging it in will cause the macbook to flash blue quicker than normal and immediately go back to the normal screen. I know the macbook recognizes the TV because changing the input on the TV to the hdmi connected to the computer will cause the macbook to flash blue again, with the same result. The TV remains unresponsive. I have tried all combinations of turning on and off the TV and macbook with the cord plugged in and unpugged from either and both systems and in both hdmi inputs on the TV. I've changed the display resolution to every possible option with no result. The TV is not recognized as a display on either the Display section of System Preferences or the Sound section.
It confounds me that the cord should work flawlessly until now, a month after buying it, for no apparent reason. I've been gentle with the cord, so the problem being a result of damage is unlikely. I had not updated my computer in any way between the successful and unsuccessful uses of the cord, but I have since updated my computer and the problem remains.
I have searched for this problem on the Internet and have seen others with similar problems, but I have not found a solution that resolves my problem. I hope to avoid having to make any additional purchases.
And a thousand and one thanks to any and all who help.

Do you have gfxCardStatus installed? Is your monitor set to "Integrated" or "Discrete". You want it set to Discrete to drive the external HDMI display.
Try resetting the PRAM and SMC
<About NVRAM and PRAM>
<Intel-based Macs: Resetting the System Management Controller (SMC)>
Are you sure you have a good miniDisplayPort to HDMI cable?
Do you have another HDMI display you can test against (your neighbor's HDMI capable TV).
Do you have friend that can test the cable using their Mac and maybe their TV or a monitor that has HDMI input.

How can I connect my '07 MBP to an HDTV via HDMI for audio/video?

How can I connect my '07 MBP to an HDTV via HDMI for audio/video?

About Mini DisplayPort to HDMI adapters
Stefan

Connect Mac OS X to Vizio HDTV

What is the easiest and cheapest way to use a VIZIO HDTV as a monitor for my Mac OS X

DVI to HDMI adaptor cable is the easiest and the cheapest, if your TV has HDMI port.

MBP Connected to HDTV Problem

Last night I connected my MBP to my HDTV (37" Toshiba Regza)and was really impressed with the movie quality with iTunes. Anyway, after I disconnected the laptop I noticed the picture on my HDTV was really stretched (even in native format). I had to completely reset my TV to fix the problem. Did my MBP adjust the aspect on my TV? I tried every which way through the TV to adjust tha aspect but I could not fix the problem. Now, the TV stations are okay but the Guide function on my HD tuner looks out of whack (Has vertical borders).
Any thoughts?

Never heard of such a thing before but I guess that doesn't mean it didn't happen this time. There is really no way for a Mac to send control signals to a display, except maybe via something called DDCci which I don't think the Mac supports. And even if it did, I'd be surprised if your Regaza responded to DDCci control signals. You might want to check your Toshiba's manual to see if there is any mention of it.

Using MBP with LCD HDTV

So I've been looking at getting a new LCD HDTV. Someone said that I needed to get a minimum of a 42'' and also at least 1080p resolution. I was going to hook this all up using the HDMI out into a DVI in the TV.
Is this true? What are your set ups? I'm pretty anxious. I want to use this for movies but also possibly as an external monitor (I know a little ridiculous, but not all the time). Let me know guys! Thanks.

It is easier than you think. First, get a TV with at least 2 HDMI ports. You may wish to connect the other to a HDTV DVR (cable or satellite) or even an HD-DVD/BluRay player.
Next, measure the distance. This is critical. 1080p has TWICE as much bandwidth used as a 1080i signal.
Now, open a new tab in your browser (Apple+T) and go to my favorite cable guys www.bluejeanscable.com I say they are my favorite as they were courteous and honest. Alan Denke, the proprietor of the business, answered truthfully when I asked if his cheapest line of DVI-HDMI cables, the Tartan series, would make it at 50 feet. He asked what kind of hardware I was connecting. I told him, "Well, a brand new 47-inch Vizio with 1080p native support, and a 2.4GHz MacBook Pro." It was then that he said the display didn't really matter, but the source did. And he said the MBP would work just fine.
Cable arrived here from Oregon in one business day, though I didn't pay anything extra for it. Just plain old Priority Mail.
It was then I learned I needed about 30 feet, rather than 50. Remember the step up there where it says ,"Measure?" Yeah, I guesstimated. I kept the cable though, thinking that some day I might use the computer in the kitchen or something.
Now, you'll need to get appropriate playback software. Quicktime just doesn't do .ts (transport stream) files, nor does it do .mkv (Matroska Video Codek) files. It ought to, but it won't. So, no Front Row for HD playback at 1080i. There is hope on the Open Source horizon, though. Go off and open another tab to direct yourself to www.videolan.org
The latest release even has support for the Apple Remote!
Getting audio to your setup is a slightly different thing, but can be done with parts from (ugh) radio shag. For analog audio (which is fine for me as my system don't do any better with digital input), just get a 1/8" STEREO (will have 3 conductors [or two 'rings']) to dual RCA out. They usually have 3 and 6 foot versions of this cable. To extend, you've got 3 options: 8', 16' or 20' male to female 1/8" stereo.
Hope this info helped. If you haven't bought your lcd tv yet, take a look at Vizio. I believe them to be the best bang for the buck out there.
Doctor V

Connecting a 15.4" MacBook Pro to a Vizio HDTV monitor - which adapter?

Hi, I have one of the new MacBook Pro models, 15.4", 2.4 GHz, 4 GB Ram, 250 GB hard drive, and an NVIDIA GeForce 9600M GT with 256 MB VRAM.
I have just purchased a 32" Full HD 1080P HDTV/monitor from Vizio (the product's URL is http://www.vizio.com/product.aspx?id=2710&pid=1506) and was wondering if anyone could tell me what the best type of adapter I'd need from Apple to connect this to my MacBook Pro?
Thanks!
null

Suggest that you do a forum search. There are several postings listing items that you need to connect your MBP to a TV. Also, check the manual that came w/your MBP.

How do I connect my 27" Imac to my 47" Vizio HDTV?

Good Morning!
I am attempting to connect my 27" Imac to my brand-spankin-new 47" Vizio 1080p HDTV. I know there is a way to use the TV to display videos, internet (Netflix), and such, but I'm not sure what is the simplest and most effective way to get the best display and performance.
What equipment do I need to make this happen?
Thank you for your assistance, brilliant people!

I have the 22" imac
beside it I have an 24" dell monitor
I used a miniDisplayport->DVi converter in the TB port of the imac
thats the best performance because DVI like Displayport are both digital interfaces
same deal with hdmi really
so you need a miniDisplayport to dvi or hdmi depending on the inputs on your tv
and a cable and thats it

My new Macbook air won't connect to my Vizio HDTV.

My new Macbook Air won't connect to my Vizio VO32LF HDTV. I bought a mini-displayport to HDMI cable to connect the two. When I connect the cable, and switch to the appropriate HDMI input on the TV, my Macbook Air screen will flash blue for a second, and then return to normal. The TV reports it's unable to find a signal. I use the HDTV as my primary monitor, so I'd really appreciate some help on getting the two to place nicely together!

Cp,
Thanks for the reply. However, it appears that the issue is not with the hotspot, but with the network settings in the MacBook Air as every other device I have (including non-Apple devices) will connect to the iPhone hotspot. Another symptom is that my MacBook Air can find my iMac (and other network devices) on my wireless network, but the iMac can't find the MacBook Air.
KDR

Using a Vizio HDTV as an external monitor

I've bought the right connector and cable to connect my MacBook to an external monitor, and with two of our HDTVs, it works great. The problem is, it doesn't work with the TV I want it to.
We have a Vizio 27", a Phillips 47", and a Sony Bravia 52". On the Phillips and Sony, the picture quality is 1080p and amazing quality, and everything fits on the screen perfectly (as in the menu bar and dock).
But with the Vizio, which I'm wanting to use as a main monitor with external mouse and keyboard also, the picture quality is awful. It looks decent at 1280x764, which it tries setting it to by default, but when I change that to 1080i, the picture quality becomes really fuzzy and unreadable, and the dock and menu bar aren't even on the screen (you can barely see the top of the dock at the bottom though, so I know it's there.)
My question is: Does anyone know a way to fix this? So the Vizio can show the image in good quality? I've searched all through the MacBook's settings and my TVs settings, but I couldn't find anything. Any ideas?

I have a Samsung HDTV with HDMI Sockets etc etc
What cable will I need to connect my MacBook to my HDTV to watch movies direct from my MacBook on my HDTV?

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!

Connecting my MBP to my HDTV???

Anyone know of a cable set up that will feed video and audio to my hdtv from my MBP???? My hdtv has a VGA hookup, S-Video, RCA, Component hookups & HDMI.
If I were to hookup a MiniDisplay to DVI to my MBP and then a DVI to HDMI to the TV would that give me audio too?
I really want to simplify my cable situation so one cable that does it all would be better than multiple cables running from my MBP to my TV.

Can I just piggy-back onto this question? I'm totally clueless to all this audio/visual stuff, but I'm trying to connect my 15 inch MBP (2009) to my Pioneer HDTV (it's something like "Pioneer Elite Pro Kuro", but I don't remember exactly). I just ordered the Mini DisplayPort to HDMI adaptor from Monoprice and I also ordered the Toslink cable. Looking now though, I only see a output optical audio port on the back of the TV - so that's not going to work for the audio, right? Can someone please just tell me exactly what cable to buy to make sound go from my MBP to the TV? I know that sounds totally helpless, but I've been googling for days and just can't quite figure it out. There's one hole on the MBP and a million on the TV and I have no idea what any of it means.

A 'How to..." question - Connecting a MBP to a HDTV

Just finished installing my new Pioneer HDTV (PDP-427XD) and want to connect my MBP to it. I'm not ready to invest in an Apple TV just yet so I am looking to connect the MBP physically to my HDTV.
Can anyone recommend the best way to do this. I know I need a cable but don't know which one to get.
Any recommendations?
Thanks for the help.
G5 Dual Processor, 2GHz, 1GB RAM Mac OS X (10.4.10) MBP 15inch

What you need is a DVI to HDMI cable like this one from monster. The DVI end will hook right up to your MBP and your TV will have a HDMI slot so this is all you need.
-Sam

Vizio hdtv via VGA to HDMI cable - can't get correct resolution

I'm trying to configure the resolution for a Vizio va22lfhdtv10t on a Mini. When I used a DVI to VGA adapter the resolution was very good at 1920*1080. Now that I'm using a DVI to HDMI cable it defaults to 1080p with 30hz refresh. Font resolution is terrible on this setting and only marginally better when trying the other resolution options. I have seen some posts about creating a custom resolution, but don't know how to do this, or if there is a danger of damaging the LCD with improper settings. Has anyone gotten this HDTV to work other than as a VGA display?
Thanks!

1920 x 1080 is the native resolution, so (a) I wouldn't try any other resolution, and (b) I'd ONLY use a digital input (HDMI).
If you're getting crummy unsharp pictures, it sounds as if the TV's scaler is working. You need to look for a menu setting (on the TV) to turn off the scaler. It might be called something like "1:1 pixel" mapping, or "overscan OFF" or some thing similar.
I see on the manual p.35:
+4. Wide - The Wide option lets you determine how the image appears on the screen. Select Normal, Wide, or Panoramic.+
Try those three. My guess is you want "wide" mode for a 1920x1080 feed.
Also, H and V size and position can be adjusted (p.35/36) - maybe that will help?

Cabling from MacBook 2 Vizio HDTV

Is there a cable that can connect my MacBook to HDTV (have two, Vizio/Samsung) in order to watch movies currently residing on laptop?

Depends on what input plug you'll be using on your TV. VGA, DVI or HDMI. You'll need a Mini DisplayPort adapter and a cable from that to your TV. Here's the various types of Mini DisplayPort adapters on Amazon.com http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=min i-dvi&x=9&y=13#/ref=nb_sb_ss_sc_2_16?url=search-alias%3Daps&field-keywords=mini+ displayport&sprefix=mini+displayport&rh=i%3Aaps%2Ck%3Amini+displayport
If you connect the MacBook using a Mini DisplayPort to HDMI adapter you will probably need to use external speakers or a 3.5mm stereo headphone jack to RCA sound plugs connected to a stereo sound system if your TV doesn't have separate RCA input plugs or a 3.5mm stereo input plug for audio with the HDMI plug. The MiniDisplayPort to HDMI doesn't carry audio unless you have the Mid 2010 model 7,1 and there're no audio plugs on most TVs to work with HDMI since it's expecting audio with the HDMI.
With the model 6,1 there is an adapter that can combine video and audio to HDMI. http://www.monoprice.com/products/product.asp?c_id=104&cp_id=10428&cs_id=1042802 &p_id=5969&seq=1&format=2

MBP to Vizio HDTV

Similar Messages

Maybe you are looking for