[SOLVED] Dual-Screen Setup with ATI Catalyst

I'm having a beast of a time trying to set up X to work on my two screens.
Screen 1 is a 23" screen connected with a DVI cable.  My preferred resolution for this one is 1920x1080.  Screen 2 is a 17" screen (4:3) connected with a VGA cable.  My preferred resolution for this one is 1280x960.
I tried using "aticonfig --initial=dual-head".  This does not produce a working xorg.conf file.  Specifically, my smaller monitor simply complains about not being able to display the given video mode.  Running xrandr (from the main screen) shows only that output as being "connected" - the rest of them (including the CRT outputs which seem to correspond to the VGA port) as "disconnected".
I've spent about 5 hours searching for an answer to this, and the only ones I seem to be able to find are nvidia-specific.
I have an ATI Radeon HD 4850 or 4870 - I honestly forget which, although the drivers should be the same.  I'm using the catalyst driver from the AUR, because I'd like to have 3D acceleration.
I've read through the entire xorg.conf man page, and tried a few things from there (including writing my own xorg.conf from scratch).  Unfortunately, this seems incredibly useless, as the man page doesn't list any of the options that I seem to need (for example, I've read about and tried the "PairModes" option under "Device").
I can probably eventually figure this out, but it would be nice to have a few pointers.  For example:
Should I have one or two "Device" sections in xorg.conf?  Should I have one or two "Screen" sections in xorg.conf?  Where can I find a full list of possible "Option" keys, at least for the Device section?  Should I be using Xinerama (I've tried with and without, to no avail).
EDIT:  I solved this by using the aticonfig tool some more, and not by messing around with xorg.conf.  Specifically, the command:
aticonfig --initial=dual-head --xinerama=on --resolution=0,1920x1080 --resolution=1,1280x960 --screen-layout=right
I'll leave this here in the hopes that it can help someone else.
Last edited by Tempest (2011-08-06 02:28:41)

If you aren't playing games, it may be worth it to check out xf86-video-ati. Then you can configure your displays the standard way with xrandr.

Similar Messages

  • [SOLVED] dual-screen problem with awesome3.2 and firefox/gedit

    Hi,
    my problem is that firefox/gedit (+maybe other apps, i don't know yet) are starting in awesome like they are fullscreen apps. Firefox covers the wibox at the top of the screen, and even overlaps a bit to the seconds screen. So the keyboard-shortcuts doenst work well, because awesome then changes the tags in bots screens when on one tag firefox is opened.
    I dont know why this happens, here is my rc.lua:
    -- Load libraries
    require("awful")
    require("beautiful")
    require("wicked")
    -- {{{ Variable definitions
    -- User styles for windows, statusbars, titlebars and widgets
    theme_path = os.getenv("HOME") .. "/.config/awesome/themes/zenburn"
    beautiful.init(theme_path)
    -- Modifier keys
    modkey = "Mod4" -- Super_L
    -- Window titlebars
    use_titlebar = true
    -- Window management layouts
    layouts = {
    awful.layout.suit.tile, -- 1
    awful.layout.suit.tile.left, -- 2
    awful.layout.suit.tile.bottom, -- 3
    awful.layout.suit.tile.top, -- 4
    awful.layout.suit.fair, -- 5
    awful.layout.suit.fair.horizontal, -- 6
    awful.layout.suit.max, -- 7
    -- awful.layout.suit.max.fullscreen, -- /
    awful.layout.suit.magnifier, -- 8
    awful.layout.suit.floating -- 9
    -- Application specific behaviour
    apprules = {
    -- Class Instance Name Screen Tag Floating
    { "Firefox", nil, nil, nil, 2, false },
    { "Firefox", "Download", nil, nil, nil, true },
    { "Firefox", "Places", nil, nil, nil, true },
    { "Firefox", "Extension", nil, nil, nil, true },
    { "MPlayer", nil, nil, nil, nil, true },
    { nil, nil, "VLC media player", nil, nil, true },
    { "Gimp", nil, nil, nil, nil, true },
    { "Xmessage", "xmessage", nil, nil, nil, true },
    { "Skype", nil, nil, nil, 1, true },
    { "Pidgin", nil, nil, nil, 1, true },
    -- {{{ Tags
    -- Define tags table
    tags = {}
    tags.settings = {
    { name = "im", layout = layouts[9] },
    { name = "www", layout = layouts[1] },
    { name = "terms", layout = layouts[3] },
    { name = "dev", layout = layouts[3] },
    { name = "other", layout = layouts[5] },
    -- Initialize tags
    for s = 1, screen.count() do
    tags[s] = {}
    for i, v in ipairs(tags.settings) do
    tags[s][i] = tag(v.name)
    tags[s][i].screen = s
    awful.tag.setproperty(tags[s][i], "layout", v.layout)
    awful.tag.setproperty(tags[s][i], "setslave", v.setslave)
    end
    tags[s][1].selected = true
    end
    -- {{{ Wibox
    -- Widgets configuration
    -- Reusable separators
    myspace = widget({ type = "textbox", name = "myspace", align = "right" })
    myseparator = widget({ type = "textbox", name = "myseparator", align = "right" })
    myspace.text = " "
    myseparator.text = "|"
    -- Date, time and...
    mydateicon = widget({ type = "imagebox", name = "mydateicon", align = "right" })
    mydateicon.image = image(beautiful.widget_date)
    mydatewidget = widget({ type = "textbox", name = "mydatewidget", align = "right" })
    wicked.register(mydatewidget, wicked.widgets.date, "%b %e, %R", 60)
    -- a Calendar
    function calendar_select(offset)
    local datespec = os.date("*t")
    datespec = datespec.year * 12 + datespec.month - 1 + offset
    awful.util.spawn("cal -m " .. (datespec % 12 + 1) .. " " .. math.floor(datespec / 12) .. " | xmessage -geometry +1135+17 -file -")
    end
    mydatewidget:buttons({
    button({ }, 1, function () calendar_select(0) end),
    button({ }, 4, function () calendar_select(1) end),
    button({ }, 5, function () calendar_select(-1) end)
    -- System tray
    mysystray = widget({ type = "systray", align = "right" })
    -- Create a wibox and...
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = { button({ }, 1, awful.tag.viewonly),
    button({ modkey }, 1, awful.client.movetotag),
    button({ }, 3, function (tag) tag.selected = not tag.selected end),
    button({ modkey }, 3, awful.client.toggletag),
    button({ }, 4, awful.tag.viewnext),
    button({ }, 5, awful.tag.viewprev) }
    -- ...add it to each screen
    for s = 1, screen.count() do
    -- Create a promptbox
    mypromptbox[s] = widget({ type = "textbox", align = "left" })
    -- Create an imagebox widget with icons indicating active layout
    mylayoutbox[s] = widget({ type = "imagebox", align = "left" })
    mylayoutbox[s]:buttons({ button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    button({ }, 5, function () awful.layout.inc(layouts, -1) end) })
    -- Create the taglist
    mytaglist[s] = awful.widget.taglist.new(s, awful.widget.taglist.label.all, mytaglist.buttons)
    -- Create the wibox
    mywibox[s] = wibox({ position = "top", height = "14", fg = beautiful.fg_normal, bg = beautiful.bg_normal })
    -- Add widgets to the wibox (order matters)
    mywibox[s].widgets = { mylayoutbox[s],
    mytaglist[s],
    mypromptbox[s],
    myspace,
    mydateicon, mydatewidget,
    myspace,
    s == screen.count() and mysystray or nil
    mywibox[s].screen = s
    end
    -- {{{ Mouse bindings
    root.buttons({
    button({ }, 4, awful.tag.viewnext),
    button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = {
    -- Applications
    key({ modkey }, "Return",function () awful.util.spawn("uxterm") end),
    -- Prompt menus
    key({ modkey }, "F2", function () awful.prompt.run({ prompt = "Run: " }, mypromptbox[mouse.screen],
    awful.util.spawn, awful.completion.shell, awful.util.getdir("cache") .. "/history")
    end),
    -- Awesome controls
    key({ modkey, "Shift" }, "q", awesome.quit),
    key({ modkey, "Shift" }, "r", function () mypromptbox[mouse.screen].text = awful.util.escape(awful.util.restart()) end),
    -- Layout manipulation
    key({ modkey, "Shift" }, "Plus", function () awful.client.incwfact(-0.05) end),
    key({ modkey, "Shift" }, "Minus", function () awful.client.incwfact(0.05) end),
    key({ modkey }, "space", function () awful.layout.inc(layouts, 1) end),
    key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    -- Focus controls
    key({ modkey }, "Tab", function () awful.client.focus.history.previous(); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Down", function () awful.client.focus.bydirection("down"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Up", function () awful.client.focus.bydirection("up"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Left", function () awful.client.focus.bydirection("left"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Right", function () awful.client.focus.bydirection("right");if client.focus then client.focus:raise() end end),
    key({ modkey, "Shift" }, "Down", function () awful.client.swap.bydirection("down") end),
    key({ modkey, "Shift" }, "Up", function () awful.client.swap.bydirection("up") end),
    key({ modkey, "Shift" }, "Left", function () awful.client.swap.bydirection("left") end),
    key({ modkey, "Shift" }, "Right", function () awful.client.swap.bydirection("right") end),
    -- Client manipulation
    clientkeys = {
    key({ modkey, "Control" }, "space", awful.client.floating.toggle),
    -- Bind keyboard digits
    keynumber = 0
    for s = 1, screen.count() do
    keynumber = math.min(9, math.max(#tags[s], keynumber));
    end
    -- Tag controls
    for i = 1, keynumber do
    table.insert(globalkeys,
    key({ modkey }, i,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewonly(tags[screen][i])
    end
    end))
    table.insert(globalkeys,
    key({ modkey, "Shift" }, i,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.movetotag(tags[client.focus.screen][i])
    end
    end))
    end
    -- Set keys
    root.keys(globalkeys)
    -- {{{ Hooks
    -- Hook function to execute when focusing a client
    awful.hooks.focus.register(function (c)
    if not awful.client.ismarked(c) then
    c.border_color = beautiful.border_focus
    end
    end)
    -- Hook function to execute when unfocusing a client
    awful.hooks.unfocus.register(function (c)
    if not awful.client.ismarked(c) then
    c.border_color = beautiful.border_normal
    end
    end)
    -- Hook function to execute when marking a client
    awful.hooks.marked.register(function (c)
    c.border_color = beautiful.border_marked
    end)
    -- Hook function to execute when unmarking a client
    awful.hooks.unmarked.register(function (c)
    c.border_color = beautiful.border_focus
    end)
    -- Hook function to execute when the mouse enters a client
    awful.hooks.mouse_enter.register(function (c)
    -- Sloppy focus (but disabled for magnifier layout)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    -- Hook function to execute when a new client appears
    awful.hooks.manage.register(function (c)
    -- If we are not managing this application at startup, move it to the screen where the mouse is
    if not startup and awful.client.focus.filter(c) then
    c.screen = mouse.screen
    end
    -- Add a titlebar to each client
    if use_titlebar then
    awful.titlebar.add(c, { modkey = modkey })
    end
    -- Set client mouse bindings
    c:buttons({
    button({ }, 1, function (c) client.focus = c; c:raise() end),
    button({ modkey }, 1, awful.mouse.client.move),
    button({ modkey }, 3, awful.mouse.client.resize)
    -- New clients may not receive focus if they're not focusable, so set the border anyway
    c.border_width = beautiful.border_width
    c.border_color = beautiful.border_normal
    -- Check application->screen/tag mappings and floating state
    local target_screen
    local target_tag
    local target_float
    for index, rule in pairs(apprules) do
    if (((rule[1] == nil) or (c.class and c.class == rule[1]))
    and ((rule[2] == nil) or (c.instance and c.instance == rule[2]))
    and ((rule[3] == nil) or (c.name and string.find(c.name, rule[3], 1, true)))) then
    target_screen = rule[4]
    target_tag = rule[5]
    target_float = rule[6]
    end
    end
    -- Apply mappings, if any
    if target_float then
    awful.client.floating.set(c, target_float)
    end
    if target_screen then
    c.screen = target_screen
    awful.client.movetotag(tags[target_screen][target_tag], c)
    end
    -- Focus after tag mapping
    client.focus = c
    -- Set client key bindings
    c:keys(clientkeys)
    -- Put windows at the end of others instead of setting them as a master
    --awful.client.setslave(c)
    -- ...or do it selectively for certain tags
    if awful.tag.getproperty(awful.tag.selected(mouse.screen), "setslave") then
    awful.client.setslave(c)
    end
    -- New floating windows don't cover the wibox and don't overlap until it's unavoidable
    awful.placement.no_offscreen(c)
    --awful.placement.no_overlap(c)
    -- Honoring size hints: false to remove gaps between windows
    c.size_hints_honor = false
    end)
    -- Hook function to execute when arranging the screen
    awful.hooks.arrange.register(function (screen)
    -- Update layout imagebox widget with an icon indicating active layout
    local layout = awful.layout.getname(awful.layout.get(screen))
    if layout and beautiful["layout_" ..layout] then
    mylayoutbox[screen].image = image(beautiful["layout_" .. layout])
    else
    mylayoutbox[screen].image = nil
    end
    -- Give focus to the latest client in history if no window has focus
    -- or if the current window is a desktop or a dock one
    if not client.focus then
    local c = awful.client.focus.history.get(screen, 0)
    if c then client.focus = c end
    end
    -- Fine grained border controls
    local visible_clients = awful.client.visible(screen)
    if #visible_clients > 0 then
    for unused, current in pairs(visible_clients) do
    -- Floating clients always have borders
    if awful.client.floating.get(current) or (layout == 'floating') then
    current.border_width = beautiful.border_width
    -- Floating clients always on top
    if not current.fullscreen then
    current.ontop = true
    end
    -- Don't draw the border if there is only one tiled client visible
    elseif (#visible_clients == 1) or (layout == 'max') then
    visible_clients[1].border_width = 0
    else
    current.border_width = beautiful.border_width
    end
    end
    end
    end)
    I added "xrandr --output DVI-1 -- right-of DVI-0" to the .xinitrc to get the extended desktop i want.
    Any suggestions?
    Last edited by Wishes (2009-03-29 10:52:00)

    Still the same
    Edit: i deleted my ~/.mozilla folder. Now firefox starts not overlapping with the wibox, but still a bit overlapping to the other screen, so hat my keystrokes toggle both screens. it seems that it start in floating mode, because i can move it with the mouse. When i move it a bit towarts the wibox and a bit right, it seems to get stuck in the chosen tile-layout and everything is fine... until i quit firefox and start it again.
    Edit2: Hmmm, ok, i think i found it... or at least something:
    -- New floating windows don't cover the wibox and don't overlap until it's unavoidable
        --awful.placement.no_offscreen(c)  //THIS was first uncommented
        awful.placement.no_overlap(c)  //THIS was first commented
    So now with no_overlap it seems to work finde (although i cannot move gedit between the screens with the mouse, but i dont know if this isn't normal. Firefox is moveable between the screens.), no overlapping anymore with the wibox or to the other screen.
    When i uncomment both lines, firefox and gedit are starting both on the 2nd screen (the left one), and gedit cannot be moved to the right one (although firefox can be moved.).
    Last edited by Wishes (2009-03-28 20:24:52)

  • Is it possible to have a dual screen setup with an iMac (2012) and an iMac (mid 2007)?

    Hello Everyone,
    I have two iMacs. One is a 2012 model and the other is a mid 2007 model. Would I be able to use the mid 2007 model as an extra monitor?
    I was going to purchase a mini dvi to mini display port cable and see what happens but I think it would be a good idea to see what everyone else thinks. Thanks for any suggestions!
    - Nolan

    The Apple Support Communities are an international user to user technical support forum. As a man from Mexico, Spanish is my native tongue. I do not speak English very well, however, I do write in English with the aid of the Mac OS X spelling and grammar checks. I also live in a culture perhaps very very different from your own. When offering advice in the ASC, my comments are not meant to be anything more than helpful and certainly not to be taken as insults.
    I am thinking that won't work. The older iMac's video port only goes on direction - out. It won't take the signal from the newer iMac. You might be able to do something with this software;
    http://www.screenrecycler.com/ScreenRecycler.html

  • Dual Screen setup with laptop

    I have the ideapad u400.. is it possitble to connect 2 external monitors to this machine to have 3 displays if not.. can i use the 2 external monitors and just close the lid to the laptop to use just 2 monitors?
    let me know
    Thanks.

    As you need to connect two external monitor with your IdeaPad U400. You can connect the external Monitor via HDMI port, if it is available in your system.
    Alternatively, you will need to create a two monitor connection via the USB input with a VGA to USB conversion cable, you can purchase these cables at any local computer store. And able this feature in your system.
    Thanks  & Regards,
    Sameer
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • X crashes on startup with AMD dual screen setup

    Ever since I bought my AMD Kaveri A10-7850K at the end of January last year I've been having trouble getting a dual screen setup to work properly. Initially I put this down to poor beta drivers, and as I had far too much going on to investigate the issue further beyond some fiddling with xorg.conf, I bought an AMD A4-4000 as a temporary solution while waiting for the Catalyst drivers to catch up.
    In June last year I decided to give my A10-7850K another go, assuming that the Catalyst driver would have matured enough in the meantime to cater for the Kaveri processors. Unfortunately the situation was still the same, and I I didn't have the time nor want to be swapping processors all constantly to I decided to just give up on a dual monitor setup for the time being.
    After many years of using two screens, however, it is very hard to get used to a single monitor again, and as January is a quiet month for me I decided today to have another at getting it to work properly.
    My setup is as follows:
    an LG LG 23EA63V connected via HDMI as my main monitor at 1920x1080
    a Viewsonic VP-171b connected via DVI as my secondary monitor at 1280x1024
    AMD A10-7850K APU
    Catalyst 14.12-1 drivers installed from Vi0l0's repo
    Xorg 1.15 installed from Vi0l0's repo
    KDE 4.14.3 using kwin
    KDM is launched using kdm.service
    KMS disabled via nomodeset
    fglrx module loaded on boot via cat /etc/modules-load.d/catalyst.conf
    Tear free rendering enabled
    After plugging in my secondary monitor configuring it in amdcccle to be to the right of my primary moniotor in multi-display desktop mode, everything works correctly. This even works in my preferred setup where the secondary monitor is rotated into portrait mode, although I currently have not configured rotation so as to not overcomplicate the troubleshooting.
    Upon rebooting, however, X hangs with a static white cursor in the top left hand of both screens, which after a while disappears completely. I then have to unplug the secondary (DVI) monitor and hard reset the PC before I can boot into my desktop again. The bizarre thing is though that when I plug in my secondary monitor again and configure it as desired, either through amdcccle or krandr, everything works perfectly again.
    This is, of course, an incredibly cumbersome way of working, especially when most of the time I forget to disconnect my DVI monitor prior to turning on my PC, hence me just making do with a single monitor for the past 7 months.
    I did a complete fresh install of Catalyst yesterday (uninstall drivers, delete remaining config files, reinstall drivers from repo), to no avail.
    Output from xrandr after rebooting with the secondary monitor disconnected:
    $ xrandr
    Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
    DFP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
    1920x1080 60.00*+ 50.00 59.94 60.00 50.00 59.94
    1776x1000 50.00 59.94 50.00 59.94
    1680x1050 50.00 59.95
    1400x1050 50.00 59.98
    1600x900 50.00 60.00
    1280x1024 50.00 60.02
    1440x900 50.00 59.89
    1280x960 50.00 60.02
    1280x800 50.00 59.81
    1152x864 50.00 59.96
    1280x768 50.00 59.81
    1280x720 60.00 50.00 59.94
    1024x768 50.00 60.00
    1152x648 50.00 59.94
    800x600 50.00 60.32
    720x480 50.00 60.00 59.94
    640x480 50.00 60.00 59.94
    DFP2 disconnected (normal left inverted right x axis y axis)
    CRT1 disconnected (normal left inverted right x axis y axis)
    Output from xrandr after reconnecting the secondary monitor:
    $ xrandr
    Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 16384 x 16384
    DFP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
    1920x1080 60.00*+ 50.00 59.94 60.00 50.00 59.94
    1776x1000 50.00 59.94 50.00 59.94
    1680x1050 50.00 59.95
    1400x1050 50.00 59.98
    1600x900 50.00 60.00
    1280x1024 50.00 60.02
    1440x900 50.00 59.89
    1280x960 50.00 60.02
    1280x800 50.00 59.81
    1152x864 50.00 59.96
    1280x768 50.00 59.81
    1280x720 60.00 50.00 59.94
    1024x768 50.00 60.00
    1152x648 50.00 59.94
    800x600 50.00 60.32
    720x480 50.00 60.00 59.94
    640x480 50.00 60.00 59.94
    DFP2 connected 1280x1024+1920+0 (normal left inverted right x axis y axis) 338mm x 270mm
    1280x1024 60.02*+ 75.02
    1280x960 75.02 60.02
    1152x864 75.00 60.02
    1280x768 75.02 60.02
    1280x720 75.02 60.02
    1024x768 85.00 75.03 70.07 60.00
    800x600 85.06 72.19 75.00 60.32 56.25
    640x480 85.01 75.00 72.81 66.61 59.94
    CRT1 disconnected (normal left inverted right x axis y axis)
    my xorg.conf file:
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-1"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Monitor"
    Identifier "0-DFP1"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    Option "Position" "0 0"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection
    Section "Monitor"
    Identifier "0-DFP2"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1280x1024"
    Option "TargetRefresh" "60"
    Option "Position" "1920 0"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    Option "Monitor-DFP1" "0-DFP1"
    Option "Monitor-DFP2" "0-DFP2"
    BusID "PCI:0:1:0"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-1"
    Driver "fglrx"
    Option "Monitor-DFP1" "0-DFP1"
    BusID "PCI:0:1:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Virtual 3200 3200
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-1"
    Device "aticonfig-Device[0]-1"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    My Xorg.0.log:
    http://pastebin.com/ki5A0T7R
    I'm quite desperate to get this working, almost a year after buying my new setup, so any pointers are welcome!
    Thanks in advance!

    Actually of the above listed commands only xclock is in xorg-apps .
    pacman -S xorg-apps xorg-twm xterm
    is needed.

  • [SOLVED] Best DE for dual screen setups?

    Sorry if this is a dumb question, but what is the best DE for a dual screen setup on Arch? Also, can I just use the standard xrandr method to be able to drag windows between screens, if not, what do I do?
    Many thanks.
    Last edited by treeman1111 (2013-02-19 22:44:59)

    Ok, so here is the output of xrandr -q:
    Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 1920 x 1920
    DFP1 disconnected (normal left inverted right x axis y axis)
    DFP2 disconnected (normal left inverted right x axis y axis)
    DFP3 disconnected (normal left inverted right x axis y axis)
    DFP4 disconnected (normal left inverted right x axis y axis)
    DFP5 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
    1920x1080 60.0*+ 50.0 59.9 60.1 50.0 60.0
    1776x1000 50.0 59.9 50.0 60.0
    1680x1050 60.0 50.0 59.9
    1400x1050 60.0 50.0 59.9
    1600x900 50.0 59.9
    1280x1024 50.0 75.0 60.0
    1440x900 50.0 59.9
    1280x960 50.0 75.0 60.0
    1152x864 50.0 59.9 75.0
    1280x768 50.0 75.0 60.0
    1280x720 60.0 50.0 59.9
    1024x768 50.0 75.0 60.0
    1152x648 50.0 59.9
    800x600 50.0 75.0 60.3
    720x480 50.0 60.1 60.0 60.1 59.9
    640x480 50.0 75.0 60.0 59.9
    DFP6 disconnected (normal left inverted right x axis y axis)
    DFP7 disconnected (normal left inverted right x axis y axis)
    CRT1 disconnected (normal left inverted right x axis y axis)

  • Dual monitor setup with seperate resolutions

    hey guys!
    i currentley run thye latest version of archlinux with the cinnamon desktop environment and an nvidia geforce 7300SE graphics card.
    im running a dual monitor setup with one 27" 1920x1080 monitor and one 27" 1024X768 monitor
    because they have the same physical size they line up perfectley but because the resolution is different programs/mouse cursor movement doesnt, is there any way (without changing the resolutions) to compensate this effect so that in the eyes of linux/cinnamon the monitors line up so that for example dragging a window goes seamlessley between the 2 monitors.
    i HAVE found out the panning option in the nvidia x server settings, but that really isnt what i am looking for...
    Last edited by RikSolo (2014-08-04 11:25:02)

    A magnifier following the window down to the pixel, zooming to the exact size of 540 pixels the 384 pixels window could create an illusion of just that. It would be highly impractical however, not mention all the hacking time. Even if you would manage to get two screen with different sized icons, so that they match visually, the windows and fonts resizing on the fly, wmctrl might help with windows alone, no their themes (buttons, borders thickness etc.), you would still be left with a visually differently sized mouse cursor. Technically such a feat should be possible, but who is going to code it? Nvidia?
    Last edited by emeres (2014-08-04 18:48:59)

  • I have a dual-screen setup - Workspace Layout Panels - not functioning properly.

    I have a dual-screen setup and since updating to 10.10.2, the panels open on the main screen - and not in the positions as they were saved in a Workspace layout.
    Tried trashing the prefs - which works, but when I save a new Workspace layout, it does the exact same thing.
    Any help is greatly appreciated. Thanks.

    Hi Christopher,
    This is a known issue and the product team is working with Apple to address it. Stay tuned.
    Thanks,
    Preran    

  • ITunes startup reinitializes dual screen setup

    Dear all,
    as a dual screen setup, I have a MacbookPro7,1 (late 2010 Core2Duo 2,4GHz 13" model, OSX 10.6.6) attached to a NEC MultiSync LCD2690WUXi via DVI-I, using the digital signal flow. I am not using display mirroring. The resolution of the external LCD2690WUXi is 1920x1200@60Hz.
    Everything works fine and "as expected" until I start iTunes.
    Doing this, both the MacBookPro and the external NEC monitor blank for a short time, as if the MacBook would reinitialize the displays. After doing so, I get the correct resolution on both screens back again, but all windows have now moved to the main screen and decreased in their size, so the dual screen arrangements are lost during this phase. I have to manually put everything back in place, which is highly annoying.
    I suspect this behavior might also relate to QuickTime being part of iTunes?
    If you have any ideas, please share your knowledge or experience with me.
    Kind regards,
    Jens

    The only solution (well, it's not really a solution, it's a miserable workaround) was to exchange the assingment of the primary and the scondary display, including all the negative side effects you can imagine.
    Hopefully Firefox will gain a higher grade of intelligence one day.

  • Does LR handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?

    Does LR 5 handle a dual monitor setup with different aspect ratios (16:9 and 16:10)?
    I'm planing to buy a 27" 16:9 monitor and use it as primary together with a 22" 16:10. Does any have any idea?
    Thanks

    Moreover, the two monitors can have completely different characteristics.  As always, you really need to calibrate/profile any monitor (with a hardware tool - Spyder, Colormunki etc).  That's no more important with two monitors, but you see for sure if you don't, as two dissimilar monitors will then probably look different. 

  • Dual-Screen Sessions with Oracle Desktop Client

    Dear All,
    I have read that the new version of the SRSS and SRWC support dual-screen separation with Windows 2008 R2 sessions, i.e. Windows sessions are able to determine that they are running on a dual-screen device and allow separation as you'd expect on a fat client. Does anyone know if this functionality is available via the Sun Ray software client or if I'll have to invest in Sun Ray 3 Plus devices? Has anyone actually got this working at all?
    Many thanks.
    Chris

    OK. I've applied patch -05 to the SRSS (which is odd because I thought I'd downloaded 5.1.1) which installed without complaint and have upgraded my copy of the Mac OVDC to 2.1.9.
    I've run the command (see previous post) and now I can't seem to connect to the SRSS with or without a card - it's not even connecting to the server to get a pseudo session.
    What version of the SRSS patching comes with the 5.1.2 download? It's very confusing with the version numbers not correlating. 5.1.1 seems to come with patch -06 but it refuses to install...
    Many thanks.
    Chris

  • Firefox 6.0.1 causes extreme problems with ATI Catalyst 10.x drivers on a Win7 x64 system. When I roll back to Firefox 6.0, no problems. Can this be resolved?

    Firefox 6.0.1 causes extreme problems with ATI Catalyst 10.x drivers on a Win7 x64 system. Took me quite awhile to identify, but when I roll back to Firefox 6.0, no problems. Once Firefox recognizes this and reinstalls the 6.0.1 update then severe display driver problems occur causing very erratic display behavior and ultimately rendering the system inoperative. The problem appears to occur within a minute or two after Firefox has been opened and it occurs even if Firefox has been subsequently closed prior to the actual event taking place. I have attempted this 6 times just to ensure that the problem was associated with the 6.0.1 update.

    On Mac OS, plugins are installed to a common location, usually ''' /Library/Internet Plugins''' for system-wide availability or to '''~/Library/Internet Plugins''' for a specific user. Ref: http://kb.mozillazine.org/Issues_related_to_plugins#Background
    Does Java 1.6.0_31 work on Safari or another browser?
    I also found the following, in case it helps:
    *http://reviews.cnet.com/8301-13727_7-57414869-263/how-to-use-java-applets-in-os-x-after-java-2012-003-update/
    *http://stackoverflow.com/questions/6411909/how-to-downgrade-jre-jdk-on-mac-osx

  • [Solved]Dual Monitor Setup

    So, I inherited a new monitor from my friend just a couple days ago and had a go at setting it up. Here's my current setup, to illustrate:
    -- MOD EDIT -- Please follow image posting rules
    The one on the right is mirroring the left at the moment, which happened via default when I booted up. I have the monitor to the left plugged via a dvi cable, and the one to the right that is rotated (for the purpose of better viewing webpages) with plain old vga. Both are running off my only graphics card, a Radeon X300:
    $ lspci | grep VGA
    01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
    Here is the compatible resolutions and refresh rates and such for each:
    $ xrandr
    Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
    VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
    1280x1024 60.0*+ 75.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 450mm x 280mm
    1680x1050 60.0 +
    1280x1024 75.0 60.0*
    1440x900 75.0 59.9
    1152x864 75.0 70.0 60.0
    1024x768 75.1 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 66.7 60.0
    720x400 70.1
    S-video disconnected (normal left inverted right x axis y axis)
    So, this information aside, I went and tried to add my second screen and make everything happy, I used the dual screen section in the X.Org Wiki page, which I believe was for the nVidia users, but I couldn't find any direction otherwise, so I figured with a few changes it could work with my radeon just fine. I am on xorg-server 1.9.4.901-1 with openbox as my window manager, no complete DE.
    This is my current /etc/X11/xorg.conf.d/10-monitor.conf written for two monitors, which at the moment does not work, saying no screens found when I run startx:
    Section "ServerLayout"
    Identifier "DualScreen"
    Screen 0 "Screen0"
    Scren 1 "Screen1" RightOf "Screen0" #Screen1 is to the right of Screen0
    Option "Xinerama" "1" #To move windows between screens, set to 1
    EndScetion
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "radeon"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0" #Set to 1 to make both monitors act as one big screen, with no distinction between the two
    SubSection "Display"
    Depth 24
    Modes "1680x1050_60.00"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor" "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    SubSection "Display"
    Depth 24
    Modes 1280x1024_75.00
    EndSubSection
    EndSection
    And here is the same file, in a working configuration:
    Section "Monitor"
    Identifier "Monitor0"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon" #Driver used for this monitor
    EndSection
    Section "Screen"
    Identifier "Screen0" #Collapse Monitor and Device section to Screen section
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24 #Choose the Depth (16 || 24) (24 for true colour)
    Subsection "Display"
    Depth 24
    Modes "1680x1050_75.00" #Choose the resolution
    EndSubSection
    EndSection
    This leaves me with 3 questions I cannot seem to figure out:
    1) What did I do wrong with the non-working xorg config file, giving the error "no screens found"?
    2) Another extra twist of difficulty comes from the rotated monitor on the right.  How should I adopt for that, with resolutions and such?
    3) Xinerama/Twinview  - I am confused which one of these I should choose, what they offer over the other, or should I just not bother at all?
    I would like, in a "perfectly good configuration", windows to be able to move from each monitor to the other, the monitors to be two distinct monitors (ie. they don't mirror each other), a maximized window to only fill up just the one monitor (and not both), and finally, fullscreen programs (like games and such) only fullscreen to the monitor they are on. Is such a configuration possible with all of these parameters?
    -Scott
    Last edited by Inxsible (2011-06-05 18:33:38)

    BurntSushi wrote:
    Your desired configuration is quite common, and indeed, is the default setup provided by Openbox---once the monitors are properly configured, of course :-)
    Anywho, modifying xorg.conf files for something like this is a thing of the past, man. (Incidentally, you have made the lethal mistake of assuming an nvidia config will work with an ATI card. For example, "TwinView" is only available when you are using the nvidia proprietary driver.)
    Judging by your use of "radeon" as your video driver, it looks like you're using xf86-video-ati. Therefore, congratulations, xrandr will rescue you :-) (This should also be the case if you you're using the Catalyst driver.)
    thinkwiki should be enough to get your feet wet. Note: This guide is a bit dated, but 90% of it is still relevant and useful. For example, it claims that you need to modify your xorg.conf to add a Virtual screen size---this is only true if kernel modesetting is disabled. If it's enabled (and it should be if you're using xf86-video-ati), then you're good to go. If you're using Catalyst, you will have had to disable KMS. So you'd either have to add a Virtual screen to use xrandr, or configure your monitor setup with amdcccle.
    Finally, you asked about rotation. I don't think this is anything that `man xrandr` can't answer, and you should be okay as far as support goes---rotation was added in RandR 1.2, which any civilized video driver should support. (Except nvidia blob.)
    Anywho, feel free to come back with more questions if you have any!
    (For terminology sake, this means you will be using neither Xinerama nor TwinView to configure your multi-monitors. You will be using RandR if you use xrandr. Interestingly, your screen setup will still be reported to Openbox via the Xinerama extension. You may be interested in a utility like `lxrandr` if the command line frightens you.)
    Xrandr does the job elegantly, thanks! It's a simple matter of putting the commands I needed in openbox's autostart.sh. Thanks for pointing me in the right direction.
    #xrandr --output DVI-0 1680x1050 --output VGA-0 1280x1024 --right-of DVI-0
    # xrandr --output VGA-0 --rotate left
    Scott

  • Probs with ATI Catalysts Drivers

    I’m currently using ATI Catalyst Drivers 6.14.10.6404 (3.9) for my ATI Radeon 9600xt.
    If I upgrade to the latest ATI or Omega Drivers (4.7 I think), my card crashes and is very unstable.
    my current graphics settings are:
    enabled VPU recover
    fast write is on
    AGPx8
    Why does 3.9 work and 4.7 not work, I have only had this problem since changing to this board.
    Any help appreciated.

    Well I hope it works for you engrrowl!  I was installing a slipstreamed version of XP with SP2.  But that sure didn't help me.  I would randomly have my screen corrupt with my 9700.  And that stupid card has given me headaches since I got an LCD.  So driver incompatibility used to make my screen go black all the time.  It would then revert to normal (maybe!).  But there were many times I had to shutdown by the keyboard and disconnect the DVI cable to get it to work again.  And the LCD is a Samsung so it's not cheap.
    I broke down the other night and when I had to reinstall WinXP from scratch I reverted to an older GF4.  This morning I ordered a Geforce 6800, and it will "upgrade" fine.  But if I tried to go from an ATI to an Nvidia I would have had to reload my OS again.    So it worked out for me.
    But it's strange that switching video cards solved all my "issues".  That and the fact that I've never really like ATI's drivers means I will never get another of their cards.  

  • Dual monitor setup with Docking station and W500 on windows 8

    Hi there
    I have a w500 with ATI Radeon 3650
    Trying hard to have it set up with windows 8 and two monitors with my docking station. It worked with XP, Vista, W7...but no go now.
    Any solutions out there? I don't care about catalyst control center, or which drivers I have to use, just give me back my two monitors connected to a docking station

    I have the same W500 setup and have had no luck finding Windows 8 drivers on Lenovo's site or AMD's. I have a support ticket in to Lenovo to see what they come up with. I have two flat panel monitors that I need to work. According to  MS, Catalyst Control Center has compatibility issues with Win8. It was easy to set up both monitors under Win7 with CCC. I have not been able to set them up using Windows display setting in Control Panel. Does anyone out there know of an app that I can use to replace CCC and run two monitors?
    kb5

Maybe you are looking for