[SOLVED] HDMI resolution and Radeon HD 4250

Hello,
I am a noob to Arch. Iam sorry in advance for my ignorance. I have searched for a week on the wiki and forums and then gone back and re-read everything I have found. The answer is still eluding me. I am trying to connect my laptop to my tv through hdmi. I figured out the sound on my own, that was easy. I can't however get the native resolution for the tv. I have used xrandr and cvt as in the wiki. I have messed with a xorg.conf yet because it seems a bit confusing, but again, I'm a noob. Coming from ubuntu and that unity thing that just, well, anyway.
basically this is what i have done:
cvt 1366 768
xrandr --newmode "1368x768_60.00"   85.25  1368 1440 1576 1784  768 771 781 798 -hsync +vsync
xrandr --addmode HDMI-0 1366x768
xrandr --output HDMI-0 --mode 1366x768
and I get format not supported on my tv screen and yet that is the native resolution on the tv.
This is what I get with xrandr now:
[george@archbook ~]$ xrandr
Screen 0: minimum 320 x 200, current 2646 x 768, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1366x768 60.0*+
1280x720 59.9
1152x768 59.8
1024x768 59.9
800x600 59.9
848x480 59.7
720x480 59.7
640x480 59.4
HDMI-0 connected 1280x720+1366+0 (normal left inverted right x axis y axis) 16mm x 9mm
1280x720 60.0*+
720x480 59.9
1366x768 60.0
1368x768_60.00 (0x174) 85.2MHz
h: width 1368 start 1440 end 1576 total 1784 skew 0 clock 47.8KHz
v: height 768 start 771 end 781 total 798 clock 59.9Hz
I don't know what else to do. Is this a driver problem. Should I try the catalyst driver or is there a fix to this?
I'm sorry if there is already a thread for this. I've read through these forums and after a week I decided to finally post my question. If there is another thread please provide me with the link as I have missed it. If there is not, anyone have any ideas?
Last edited by yourhereticself (2011-08-01 01:35:32)

So I solved this myself last night, however, it seems I was so caught up in trying to get the native resolution of my tv detected I did not realize that my sound is still not fuctional (I had it working in gnome 3, but i decided to switch to kde and kmix recognizes that there is hdmi but includes no channels for control of the volmue). so any way...
i solution to getting 1366x768 resolution through hdmi is: apparently 1366x768 is not a recognized mode which is why cvt gives the modeline for 1368x768; however, I 1360x768 is recognized (which I think is a fair comprimize). It looks decent on my setup anyway. So for anyone who actually has their hdmi sound working here is the solution:
$ cvt 1360 768
# 1360x768 59.80 Hz (CVT) hsync: 47.72 kHz; pclk: 84.75 MHz
Modeline "1360x768_60.00" 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync
then take the modeline and create a new mode using xrandr as such:
$ xrandr --newmode "1360x768_60.00" 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync
then add the newcode to HDMI-0 as such making sure you replace "0" in HDMI-0 with the number of the HDMI port you are planning to use:
$xrandr --addmode HDMI-0 1360x768_60.00
then change your output to this resolution via:
xrandr --output HDMi-0 --mode 1360x768_60.00
If anyone knows who to get the proper channels in kmix to control hdmi sound please let me know. Otherwise I am going to switch vga and headphone out jack for now. Thanks.

Similar Messages

  • [SOLVED]HDMI audio and gnome volume applet issues

    Hi all,
    After setting up Arch without too many problems came the real pain in the ass: HDMI audio over a Asus NVIDIA GeForce EN210....
    Eventually I got everything to work with the help of the ASLA en Pulse wiki pages, but I found the last piece of the puzzle here:
    http://wiki.xbmc.org/index.php?title=HO … ,_or_GT240
    Maybe this is useful for others too.
    The only problem I have now is that the ALSA deamon fails to load. I found this in the boot log file (/var/log/boot):
    Thu Apr 12 13:54:19 2012: :: Restoring ALSA Levels    [BUSY] Found hardware: "HDA-Intel" "Nvidia GPU 0b HDMI/DP" "HDA:10de000b,10de0101,00100200" "0x1043" "0x8343"
    Thu Apr 12 13:54:20 2012: Hardware is initialized using a generic method
    Does this mean I don't need the alsa deamon anymore? Sound still works normally after boot but a strange thing is that I can turn up and down the volume with the gnome shell volume applet but the volume of media applications like vlc do not react. Same problem with flash video's like youtube. I do hear the "blip" sound from the applet.
    Does anyone have ideas how to fix this?
    Last edited by Jurry (2012-04-26 23:46:31)

    yeah have the samre problem, adjusting sound in Amarok doesn't change anything.... happened after the last udev update, here is my bootup log :
    Sat Apr 14 17:28:55 2012: :: Adjusting system time and setting kernel timezone    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Starting UDev Daemon    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Triggering UDev uevents    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Loading User-specified Modules    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Waiting for UDev uevents to be processed    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Bringing up loopback interface    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Unlocking encrypted volumes:    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Checking Filesystems    [BUSY] /dev/sda1: clean, 29/40160 files, 24631/160616 blocks
    Sat Apr 14 17:28:55 2012: /dev/sda4: clean, 76872/18530304 files, 16371381/74101820 blocks
    Sat Apr 14 17:28:55 2012:    [DONE]
    Sat Apr 14 17:28:55 2012: :: Remounting Root    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Mounting Local Filesystems    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Activating Swap    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Configuring Time Zone    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Initializing Random Seed    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Removing Leftover Files    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Setting Hostname: Nashed    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Setting Consoles to UTF-8 mode    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Loading Keyboard Map: us    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Saving dmesg Log    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: INIT: Entering runlevel: 5
    Sat Apr 14 17:28:55 2012: :: Starting Syslog-NG    [BUSY]    [DONE]
    Sat Apr 14 17:28:55 2012: :: Starting Network    [BUSY]    [DONE]
    Sat Apr 14 17:29:26 2012: :: Starting net-profiles    [BKGD]
    Sat Apr 14 17:29:26 2012: :: Mounting Network Filesystems    [BUSY]    [DONE]
    Sat Apr 14 17:29:26 2012: :: Starting crond daemon    [BUSY]    [DONE]
    Sat Apr 14 17:29:26 2012: :: Restoring ALSA Levels    [BUSY] Found hardware: "HDA-Intel" "Realtek ALC888" "HDA:10ec0888,80860024,00100202" "0x8086" "0x0024"
    Sat Apr 14 17:29:26 2012: Hardware is initialized using a generic method
    Sat Apr 14 17:29:26 2012:    [FAIL]
    Sat Apr 14 17:29:26 2012: :: Starting D-BUS system messagebus    [BUSY]    [DONE]
    I hope it helps identify the problem

  • |Solved| - Screen resolution and nVidia

    I installed arch, xorg, nvidia's drives, openbox and gnome.
    I can run gnome and openbox without any problem, however, my screen resolution isn't recognised.  Here's my /etc/X11/xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jun 5 00:08:24 PDT 2008
    # File generated by xorgconfig.
    # Copyright 2004 The X.Org Foundation
    # Permission is hereby granted, free of charge, to any person obtaining a
    # copy of this software and associated documentation files (the "Software"),
    # to deal in the Software without restriction, including without limitation
    # the rights to use, copy, modify, merge, publish, distribute, sublicense,
    # and/or sell copies of the Software, and to permit persons to whom the
    # Software is furnished to do so, subject to the following conditions:
    # The above copyright notice and this permission notice shall be included in
    # all copies or substantial portions of the Software.
    # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
    # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
    # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
    # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    # SOFTWARE.
    # Except as contained in this notice, the name of The X.Org Foundation shall
    # not be used in advertising or otherwise to promote the sale, use or other
    # dealings in this Software without prior written authorization from
    # The X.Org Foundation.
    # Refer to the xorg.conf(5) man page for details about the format of
    # this file.
    # Module section -- this section is used to specify
    # which dynamically loadable modules to load.
    # Files section. This allows default font and rgb paths to be set
    # Server flags section.
    # Input devices
    # Core keyboard's InputDevice section
    # Core Pointer's InputDevice section
    # Other input device sections
    # this is optional and is required only if you
    # are using extended input devices. This is for example only. Refer
    # to the xorg.conf man page for a description of the options.
    # Section "InputDevice"
    # Identifier "Mouse2"
    # Driver "mouse"
    # Option "Protocol" "MouseMan"
    # Option "Device" "/dev/mouse2"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball"
    # Driver "magellan"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "spaceball2"
    # Driver "spaceorb"
    # Option "Device" "/dev/cua0"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen0"
    # Driver "microtouch"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "1412"
    # Option "MaxX" "15184"
    # Option "MinY" "15372"
    # Option "MaxY" "1230"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Section "InputDevice"
    # Identifier "touchscreen1"
    # Driver "elo2300"
    # Option "Device" "/dev/ttyS0"
    # Option "MinX" "231"
    # Option "MaxX" "3868"
    # Option "MinY" "3858"
    # Option "MaxY" "272"
    # Option "ScreenNumber" "0"
    # Option "ReportingMode" "Scaled"
    # Option "ButtonThreshold" "17"
    # Option "ButtonNumber" "1"
    # Option "SendCoreEvents"
    # EndSection
    # Monitor section
    # Any number of monitor sections may be present
    # Graphics device section
    # Any number of graphics device sections may be present
    # Standard VGA Device:
    # Device configured by xorgconfig:
    # Screen sections
    # Any number of screen sections may be present. Each describes
    # the configuration of a single screen. A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    # ServerLayout sections.
    # Any number of ServerLayout sections may be present. Each describes
    # the way multiple screens are organised. A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option. In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    # Section "DRI"
    # Mode 0666
    # EndSection
    Section "ServerLayout"
    # The Identifier line must be present
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens. The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen. In this example, screen 2 is located to the
    # right of screen 1.
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used. Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
    Identifier "Simple Layout"
    Screen "Screen 1" 0 0
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    EndSection
    Section "Files"
    # The location of the RGB database. Note, this is the name of the
    # file minus the extension (like ".txt" or ".db"). There is normally
    # no need to change the default.
    # RgbPath "/usr/share/X11/rgb"
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
    # FontPath "/usr/share/fonts/TTF"
    # FontPath "/usr/share/fonts/Type1"
    # FontPath "/usr/lib/X11/fonts/local/"
    # FontPath "/usr/lib/X11/fonts/misc/"
    # FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    # FontPath "/usr/lib/X11/fonts/Speedo/"
    # FontPath "/usr/lib/X11/fonts/Type1/"
    # FontPath "/usr/lib/X11/fonts/TrueType/"
    # FontPath "/usr/lib/X11/fonts/freefont/"
    # FontPath "/usr/lib/X11/fonts/75dpi/"
    # FontPath "/usr/lib/X11/fonts/100dpi/"
    # The module search path. The default path is shown here.
    # ModulePath "/usr/lib/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    EndSection
    Section "Module"
    # This loads the DBE extension module.
    # This loads the miscellaneous extensions module, and disables
    # initialisation of the XFree86-DGA extension within that module.
    # This loads the font modules
    # Load "type1"
    # This loads the GLX module
    # Load "glx"
    # This loads the DRI module
    # Load "dri"
    Load "dbe" # Double buffer extension
    SubSection "extmod"
    Option "omit xfree86-dga" # don't initialise the DGA extension
    EndSubSection
    Load "freetype"
    # Load "xtt"
    Load "glx"
    EndSection
    Section "InputDevice"
    # Option "Xleds" "1 2 3"
    # Option "LeftAlt" "Meta"
    # Option "RightAlt" "ModeShift"
    # To customise the XKB settings to suit your keyboard, modify the
    # lines below (which are the defaults). For example, for a non-U.S.
    # keyboard, you will probably want to use:
    # Option "XkbModel" "pc105"
    # If you have a US Microsoft Natural keyboard, you can use:
    # Option "XkbModel" "microsoft"
    # Then to change the language, change the Layout setting.
    # For example, a german layout can be obtained with:
    # Option "XkbLayout" "de"
    # or:
    # Option "XkbLayout" "de"
    # Option "XkbVariant" "nodeadkeys"
    # If you'd like to switch the positions of your capslock and
    # control keys, use:
    # Option "XkbOptions" "ctrl:swapcaps"
    # These are the default XKB settings for Xorg
    # Option "XkbRules" "xorg"
    # Option "XkbModel" "pc105"
    # Option "XkbLayout" "us"
    # Option "XkbVariant" ""
    # Option "XkbOptions" ""
    # Option "XkbDisable"
    Identifier "Keyboard1"
    Driver "kbd"
    Option "AutoRepeat" "500 30"
    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    Option "XkbRules" "xorg"
    Option "XkbModel" "logicd"
    Option "XkbLayout" "pt"
    Option "XkbVariant" "pt"
    EndSection
    Section "InputDevice"
    # Identifier and driver
    # Option "Resolution" "256"
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    # Option "BaudRate" "9600"
    # Option "SampleRate" "150"
    # Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
    # horizontal wheel to buttons 6 & 7. Change if your mouse has more than
    # 3 buttons and you need to map the wheel to different button ids to avoid
    # conflicts.
    # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    # Option "Emulate3Buttons"
    # Option "Emulate3Timeout" "50"
    # ChordMiddle is an option for some 3-button Logitech mice
    # Option "ChordMiddle"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "Auto" # Auto detect
    Option "Device" "/dev/input/mice"
    # Mouse-speed setting for PS/2 mouse.
    Option "ZAxisMapping" "4 5 6 7"
    # Emulate3Buttons is an option for 2-button mice
    EndSection
    Section "Monitor"
    # HorizSync is in kHz unless units are specified.
    # HorizSync may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    # HorizSync 30-64 # multisync
    # HorizSync 31.5, 35.2 # multiple fixed sync frequencies
    # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
    # VertRefresh is in Hz unless units are specified.
    # VertRefresh may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    Identifier "My Monitor"
    HorizSync 80.0 - 80.0
    VertRefresh 75.0
    EndSection
    Section "Device"
    # The chipset line is optional in most cases. It can be used to override
    # the driver's chipset detection, and should not normally be specified.
    # Chipset "generic"
    # The Driver line must be present. When using run-time loadable driver
    # modules, this line instructs the server to load the specified driver
    # module. Even when not using loadable driver modules, this line
    # indicates which driver should interpret the information in this section.
    # The BusID line is used to specify which of possibly multiple devices
    # this section is intended for. When this line isn't present, a device
    # section can only match up with the primary video device. For PCI
    # devices a line like the following could be used. This line should not
    # normally be included unless there is more than one video device
    # intalled.
    # BusID "PCI:0:10:0"
    # VideoRam 256
    # Clocks 25.2 28.3
    Identifier "Standard VGA"
    Driver "nvidia"
    VendorName "Unknown"
    BoardName "Unknown"
    EndSection
    Section "Device"
    # unsupported card
    #VideoRam 319488
    # Insert Clocks lines here if appropriate
    Identifier "My Video Card"
    Driver "nvidia"
    EndSection
    Section "Screen"
    Identifier "Screen 1"
    Device "My Video Card"
    Monitor "My Monitor"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 8
    Modes "1440x900"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    Modes "1440x900"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1440x900"
    EndSubSection
    EndSection
    If I run "xorgconfig" and after that "nvidia-xconfig", my screen resolution is 1024x860, but after changed very mode to my native resolution ("1440x900"),  is changes to "800x600".
    Last edited by Nomearod (2008-07-23 09:19:07)

    heleos wrote:
    Widescreen resolutions are not possible with newest vista and linux drivers if the tft is connected with dvi.
    Use an older driver or the vga-port instead.
    There are maybe some hacks, but I tried many times in vista and linux. And it's always the same, only 1280x1024.
    did some googling:
    http://forums.nvidia.com/lofiversion/in … 20005.html
    Thanks for the reply, but I don't believe that's the problem since that topic is from 2006 and I didn't had any problems last time I instaled arch (3 months ago).

  • T430 1600x900 i5 Core: Mini DisplayPort To HDMI 1920x1080 TV Resolution And Sizing-Overscan Problems

    Hello, and thanks in advance for any help.  Also, my apologies if these issues have been previously resolved; I've spent 2 days searching for answers and none of my effort has resulted in a solution, either here or elsewhere.  
    I very recently for the first time connected my ThinkPad T430 2344-5GU (i5 core, native screen resolution 1600x900, Intel HD 4000 v9.17.10.2843, NVIDIA Optimus NVS 5400M v9.18.13.1100) to a Panasonic HD TV (native screen resolution 1920x1080) using a Mini DisplayPort to HDMI connector, with the hope of playing 1080p movies on my laptop while watching them on the TV.  This seemingly worked fine at first--both audio and video were present--but I quickly noticed that the image on the TV was, very slightly, larger than the image on the laptop screen (cutting off roughly 5% of the image on each of the 4 sides) and that the resolution wasn't 1920x1080.  So I hunted for a solution.  
    Windows display properties were no help.  In fact, as soon as I tweaked something there I lost the picture on the TV (the options available are "Show desktop only on 1" (the laptop screen), "Show desktop only on 2" (the TV screen), and "Extend these screens", which annoyingly turns the TV blank yet allows the cursor to to enter the TV screen depending on the chosen layout and the cursor's approach direction to the TV).  So, from having a functional-if-slightly-oversized-and-lower-quality picture on the TV screen I went to nothing, at least for my desired use.  
    Further research led me to the Intel HD 4000 settings, but those didn't even show that multiple screens were in use when the TV is attached.  Finally, I tried using the NVIDEA Control Panel, but although multiple displays seem to be supported the best I can do when cloning is have the screens' resolutions meet in the middle at 1440x900, which makes them both look worse than the original plug-and-play result described above.  Heck, I went so far as to enter the BIOS and try every combination possible under "Graphics": no NVIDEA, Integrated, Discrete, each with and without "Auto Detect NVIDEA capability" enabled and disabled.  I even updated the NVIDEA driver to their newest, a version not available at the Lenovo Support site.  Nothing.  And worse, ever since my very first tweak under Windows display properties I wasn't able to return to the original  functional-if-slightly-oversized-and-lower-quality picture.
    At this point I used a very recent image to return my system to it's Pre Original Tweak state (allowing for the  functional-if-slightly-oversized-and-lower-quality picture originally obtained), which is better than nothing, I guess, but surely not what I'd expect from a higher end laptop.
    Please, does anyone know if there's a way to connect my T430, native resolution 1600x900, to an HD TV, native resolution 1920x1080, while actually maintaining each screens respective native resolution and not losing any of the image?  Thank you again for your time.
    Edit:  After more research I've fit the desktop image to the screen by adjusting the TV's "Picture/Advanced picture/HD size" setting from "Size 1" to "Size 2".  Now my only question is if it's possible to somehow play a 1080p movie at the TV's native resolution of 1920x1080 or if I'm stuck with the laptop's navtive resolution of 1600x900.

    Try grabbing the latest NVIDIA driver off of the NVIDIA website. It might help.
    Extending it should also allow you to run the 1600x900 T430 screen plus the 1920x1080 TV screen each at their native resolutions.
    W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
    X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
    Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

  • [Solved] A75A-G35 gives no video signal over HDMI, resolution over DVI limited

    Hello community,
    following problem: I have been using my A75A-G35 board with an A4-3400 Llano APU, the APU has been connected to a 19" BenQ FP91GP monitor via a DVI cable. I got its maximum resolution of 1280x1024 with no issues.
    Now I have purchased a 24" Dell U2415 monitor with a maximum resolution of 1920x1200 and wanted to connect it to my computer. However, I got stuck:
    1. I get no signal whatsoever using the HDMI output and a HDMI>HDMI cable. I have tested a different computer and connected it to the Dell with the same cable successfully, so the cable and the monitor should be fine.
    edit: Disregard the following as the problem with the DVI cable appears also with the other computer. The problem is therefore just the fact that the HDMI output of the board doesn't work!
    2. I get a signal with a DVI>DVI cable + DVI>HDMI adapter. I can access the BIOS, the boot manager and see the boot screen, however once the desktop should be displayed the screens turns black and the monitor keeps switching to standby and back on again, the screen staying black all the time, however. But before installing the driver package (for chipset and video, downloaded from the MSI website), I could see the desktop with a resolution of 800x600. Also, if I boot into safe mode, I can see the desktop and increase the resolution up to 1280x1024. Higher resolutions up to 1600x1200 are available, however selecting any of them results in severe screen flickering.
    3. If I boot my Linux install, I have almost the same behaviour. I see the boot messages but then the screen turns black when the desktop should appear. However, if I connect the old BenQ monitor to the VGA port, I get a signal on both screens, however both screens have the resolution 1280x1024 and I cannot increase the resolution of the Dell, because if I try to, the screen turns black again. Lower resolutions than 1280x1024 are possible, though. Note that the "second monitor trick" does only work with Linux, with Windows I get only a black screen on both monitors.
    As a side note, the DVI cable I'm using is a DVI-D single link, so the maximum resolution it supports is actually exactly the resolution of the Dell, 1920x1200.
    Thanks for any hint,
    Photon

    your welcome! 
    when you said your problem and the symptoms I thought that board sounded familiar as alot of people when it first came out that we had to explain that to them so I had a look and yes it had the jumpers to switch ports for its digital display display signal to be routed to another port so i thought that was the cause!
    have fun with your board now you have it in HDMI mode! 

  • Find monitor instance name , device name , resolution and frequency of multiple monitors (VGA and HDMI)

    hi,
    In my system multiple monitors are connected (VGA and  HDMI). In need to know the
    monitor instance name , device name , resolution and frequency of each monitor.. any solution?
    i used wm class 'WmiMonitorConnectionParams'  to determine Video output technology connection type and InstanceName.
    But i didn't get the device name , resolution and frequency of each monitor.??
    There are other wmi class like :
    WmiMonitorBrightnessEvent 
    WmiMonitorConnectionParams 
    WmiMonitorRawEEdidV1Block 
    WmiMonitorListedFrequencyRanges 
    WmiMonitorDigitalVideoInputParams 
    WmiMonitorAnalogVideoInputParams 
    WmiMonitorID 
    WmiMonitorBrightnessMethods 
    WmiMonitorBasicDisplayParams 
    WmiMonitorColorCharacteristics 
    WmiMonitorDescriptorMethods 
    WmiMonitorListedSupportedSourceM… 
    WmiMonitorBrightness 
    WmiMonitorColorXYZinCIE 
    WmiMonitorSupportedDisplayFeatures
     WmiMonitorBasicDisplayParams
     Win32_VideoController
    Win32_VideoConfiguration
    Win32_VideoSettings Win32_DisplayControllerConfiguration
    Win32_DisplayConfiguration
    But unable to determine monitor having  its corresponding values? please help me to find a solution .
    is there any other method to get multi monitor details?
    thank  you

    Hi sumith,
    I read some documents about WmiMonitorConnectionParams class, it should be able to get the video putput technology by the D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY enumeration.
    D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY enumeration
    So what happens when you are using WmiMonitorConnectionParams class? What prevent you? Anyway, please see a example of using WmiMonitorConnectionParams class, maybe you could get some hints on it.
    http://stackoverflow.com/questions/10085900/querying-wmi-for-d3dkmdt-video-output-technology
    Best regards,
    Shu Hu
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • RESOLUTION: GNB MAX and Radeon 9700 Crashes

    I had various lock-ups, crashes and "Windows detected and recovered from a device failure" error messages with my GNB MAX motherboard and Radeon 9700 and they are now fixed.
    I was able to receive a beta version of an upcoming set of drivers from ATI and they did the trick!!
    Just wanted to give you all some hope.
    Hang in there!

    Oops, I spoke too soon.  I think FastWrites is on (I remember turning it off before on previous drivers and noticing a big slow down that is not present now) but there isn't a SmartGart tab appearing in my ATI control panel any more.  I checked Advanced - Options - Details and yes, 8X is on.
    How can I verify that FastWrites is on without the SmartGart tab?

  • [SOLVED] NVidia GT240 HDMI Audio and ALSA

    I have an NVidia GT240 video card with HDMI out and I cannot for the life of me get the audio working through it!
    I've installed the drivers for NVidia (I've managed to load up XBMC and the video works beautifully) but when loading ALSA (aplay -l) there are no devices listed! I've disabled my onboard audio outputs just to avoid conflicts, aplay -l used to output my onboard realtek devices.
    I'm not sure why the devices aren't listed anywhere, either in "aplay -l" or "aplay -L".
    I'm looking to see if there's a config file somewhere where I would need to declare the device or something? The device shows up as an HD Audio Controller in lspci.
    Last edited by nerditup (2010-06-14 19:20:59)

    Hey Nerditup,
    I managed to get my card working. Here is the thread http://bbs.archlinux.org/viewtopic.php?id=90350. Mine is the last post. Basically I had to manually build the Alsa-driver package which contains the kernel modules. No patches need or anything. I just downloaded the latest package from the Alsa site and extracted it, did a cofigure, make, make install and followed the rest of the steps posted at the start of the thread(the sound.conf file) and it worked. It would not work at all with the stock Arch package.
    Hope that helps and ask if you need some more help...
    Kevin

  • [SOLVED] GTX 660 and hdmi cable

    Helo everyone,
    I have the GTX 660Ti and a monitor display with integrated speakers and hdmi port.In the gtx box there isn't the mini HDMI adaptor.
    If I connect the monitor-vga with hdmi I have no signal.So i connect with DVI port but how can I do to have the audio with a hdmi cable.
    Is necessary the mini-hdmi dongle ?
    Thanks

    So checked the GTX660 cards N660-2GD5(/OC) and N660 TF-2GD5(/OC) all have normal HDMI ports. Haven't checked before because you were talking of a missing mini hdmi connector. You just haver to connect screen and graphics card with a normal hdmi cable and you are good to go. Don't install a DVI or D-Sub cable also to connect the screen.
    Windows has nothing to do with what connection is used just to get a signal to the screen. Check if your monitor needs manual setting for what connection to use (hdmi/dvi/d-sub).

  • [SOLVED] HDMI audio not functioning

    I'm having trouble getting audio working. My setup is audio through HDMI, but I actually don't have a way to test audio through any other means, so I'm not sure if HDMI has anything to do with the problem.
    My onboard video chipset is ATI Radeon HD 4250, and so I have added "radeon.audio=1" to my GRUB's boot entry, however nothing seemed to change. Where I seem to be stuck is that aplay will not pick up any sound devices:
    $ aplay -l
    aplay: device_list:252: no soundcards found...
    From http://lkubuntu.wordpress.com/2011/07/2 … eshooting/ I was able to yield the following:
    $ lspci -nn | grep '04[80][13]'
    00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
    01:05.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI RS880 HDMI Audio [Radeon HD 4200 Series] [1002:970f]
    From some commands in the ALSA page at the wiki:
    $ lsmod | grep '^snd' | column -t
    $
    $ ls -l /dev/snd
    ls: cannot access /dev/snd: No such file or directory
    No idea why almost all of the commands I'm seeing are returning the opposite of what they should. Any ideas?
    Last edited by skoh-fley (2012-03-10 19:05:13)

    Thanks for your replies guys! Using both of your posts' information I was able to get HDMI audio working. Here's what I did:
    # modprobe -v snd-hda-intel
    FATAL: Module snd-hda-intel not found.
    At this point I found a post that suggested reinstalling kernel26:
    # pacman -S kernel26
    warning: linux-3.2.9-1 is up to date -- reinstalling
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): linux-3.2.9-1
    Total Installed Size: 57.45 MiB
    Net Upgrade Size: 0.00 MiB
    And after that all the commands starting working:
    # modprobe -v snd-hda-intel
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/soundcore.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/core/snd.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/core/snd-timer.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/core/snd-page-alloc.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/core/snd-pcm.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/core/snd-hwdep.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/pci/hda/snd-hda-codec.ko.gz
    insmod /lib/modules/3.2.9-1-ARCH/kernel/sound/pci/hda/snd-hda-intel.ko.gz
    # cat /proc/asound/{cards,devices}
    0 [SB ]: HDA-Intel - HDA ATI SB
    HDA ATI SB at 0xfeb00000 irq 16
    1 [HDMI ]: HDA-Intel - HDA ATI HDMI
    HDA ATI HDMI at 0xfe710000 irq 19
    2: [ 0- 2]: digital audio capture
    3: [ 0- 1]: digital audio playback
    4: [ 0- 0]: digital audio playback
    5: [ 0- 0]: digital audio capture
    6: [ 0- 0]: hardware dependent
    7: [ 0] : control
    8: [ 1- 3]: digital audio playback
    9: [ 1- 0]: hardware dependent
    10: [ 1] : control
    33: : timer
    Using this information I just followed OrionFyre's instructions and the sound works perfectly! Thanks all!

  • 4-Port IOGear KVM (DVI, USB) and Radeon 9600 Pro (dual G5) Problem

    I recently bought a 4-port KVM with DVI video and USB support for keyboard and mouse. I have the KVM hooked up to my dual processor G5 with DVI, to the ATI Radeon 9600 Pro video card in it. When I switch between my Windows Vista PC and my Mac (both running 85hz refresh rate and 1280x1024 resolution), the video is fine on the PC, but the Mac video is first initialized at 800x600 at 60hz. After about 3 seconds, it switches to 1280x1024 at 85hz, but this screws up my program views. I run Final Cut Express HD and DVD Studio Pro 2.0 and the windows in these programs are totally messed up. I have tried updating the drivers to the newest one from ATI, leaving the KVM on until Mac OS X Tiger is totally booted up to my desktop, before switching to one of my PCs, and updating the firmware on the KVM. Has anyone else had this problem? Any ideas to correct this problem? Thank you for your help!

    Problem solved.....I used a little shareware program called SwitchResX:
    http://www.madrau.com/html/SRX/About.html
    Fabulous little problem solver. You can set up custom resolutions of just about any dimension, although I only tested my needed resolution, and magically once you restart the machine, the resolutions are available in the Display preferences pane. If the display doesn't look right at first, i.e. shifted to the left or right, keep playing with it and perhaps switch back to a different resolution and then back to your custom res and all should be well. 75 Mhz as a refresh rate seemed to make my video card and the monitor happiest.
    Cheers.

  • AMD M880G with ATI Mobility Radeon HD 4250 display driver stopped responding

    I have received the following message on my HP Pavilion dv7:
    Display driver AMD driver stopped responding and has successfully recovered. It is an AMD M880G with ATI Mobility Radeon HD 4250.
    The screen randomly does this starting a day or so ago. Maybe once every few hours or it may do it once every 5 min three times in a row. The screen has random little blue dots here and there.
    What do I need to do? Is this something I could potentially fix/replace/etc?

    Is this they way you did a factory reset tomu96?  Performing an HP System Recovery (Windows 7)
    If so, that should have resolved the issue, but since it continues to crash if you made no changes after that restore, you probably have hardware failure.
    In North America, call (800)-474-6836 outside of North America find your support number here HP Technical Support
    TwoPointOh
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • I want to buy a new apple tv but it used hdmi cables and my house is only wired for analog.  Is there any way I can use the apple tv on analog cables?

    I want to buy a new apple tv but it used hdmi cables and my house is only wired for analog.  Is there any way I can use the apple tv on analog cables?

    Welcome to the Apple Community.
    It's do-able, but I don't think it's a great idea.
    DVI
    Some users with DVI have managed to get their TV's to work with DVI-HDMI cables. DVI carries no audio, so alternative connections need to be explored to enable audio. DVI doesn't necessarily support HDCP as well as other standards used by HDMI (which may or may not be an issue)
    Analogue
    There are hardware converters that will convert HDMI to various other types of output, however there are some issues with doing so that you should be aware of.
    HDCP
    HDCP compliant converters will not allow you to watch HDCP protected content such as that from the iTunes Store. Non compliant converters exist but we cannot discuss them under the Terms of Use for these communities.
    Resolution and aspect ratio
    I'm not aware of any converters that will scale the output from the Apple TV, any TV or projector which is used will need to be widescreen and support resolutions of 720p (Apple TV 2), 720p/1080p (Apple TV 3)
    DAC
    DAC (Example Only - Not a recommendation or suggestion that this is suitable in your circumstances)

  • I bought a mini DVI to HDMI convertor and  a HDMI to VGA cable to connect my mac book pro to a tv but it doesn't work any one can help.\\\\\

    i bought a mini DVI to HDMI convertor and  a HDMI to VGA cable to connect my mac book pro to a tv but it doesn't work any one can help.

    I would suggest looking into a Thunderbolt to HDMI connector. In this case, you may be able to use the TV as an external monitor. For this option, please confirm through additional research. I have not tested it personally.
    You can also use an Apple TV, which connects with HDMI. In this case, you can use Airplay Mirroring. Not all Macs support Airplay Mirroring, so you need to check first. I have a Mid-2011 27" iMac, and it supports Airplay Mirroring. I don't use it often because my TV is in another room, but I just tried it and it worked. It had to change the screen resolution to work well, so I don't know if I would want to use it as my day to day monitor. http://support.apple.com/kb/ht5404

  • I've just hooked my 20" iMac up to my Toshiba 37" HDTV using a mini dvi-HDMI adapter, and works well, EXCEPT for the green tinge (or hue) that is showing up on my TV. Any suggestions or ideas?

    I've just hooked my 20" iMac display up to my Toshiba 37" HDTV using a mini dvi-HDMI adapter, and everything works well, EXCEPT for the green tinge (or hue) that is showing up. Everything else looks pretty good though..... The color that is on my iMac is still good, Its just green on the TV.
    Anyone have suggestions or ideas?

    Try opening the Display System Preferences, then click on the Color options in the Display preferences window that appeared on the Toshiba display. Click on the Calibrate button and follow the instructions for creating a custom ColorSync profile that will hopefully solve the green tinge issue. The Apple Display Calibrator Assistant software that launches when you click on the calibrate button will walk you through the process.Assuming that the green tinge is minor and that you don't have a more serious cable or hardware issue, I am hopeful the results will be worth it.

Maybe you are looking for