Announcement

Collapse
No announcement yet.

RadeonHD dual screen issue with a Kohjinsha DZ

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    not sure...

    according to $(systool -b acpi -v)
    http://pastebin.ca/1795710
    the relevant section cut and pasted below:
    .....
    Device = "LNXVIDEO:00"
    Device path = "/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVI
    DEO:00"
    hid = "LNXVIDEO"
    modalias = "acpi:LNXVIDEO:"
    path = "\_SB_.PCI0.PB2_.VGA_"
    uevent = "MODALIAS=acpi:LNXVIDEO:"

    Device = "LNXVIDEO:01"
    Device path = "/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:46/LNXVI
    DEO:01"
    hid = "LNXVIDEO"
    modalias = "acpi:LNXVIDEO:"
    path = "\_SB_.PCI0.AGP_.VGA_"
    uevent = "DRIVER=video
    MODALIAS=acpi:LNXVIDEO:"
    .....

    however, a $(systool -c backlight -v) only shows:

    Class = "backlight"

    Class Device = "acpi_video0"
    Class Device path = "/sys/devices/virtual/backlight/acpi_video0"
    actual_brightness = "9"
    bl_power = "0"
    brightness = "0"
    max_brightness = "9"
    uevent =

    Device = "device:48"
    Device path = "/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:46/LNXVIDEO:01/device:48"
    hid = "device"
    modalias = "acpi:device:"
    path = "\_SB_.PCI0.AGP_.VGA_.LCD_"
    uevent = "MODALIAS=acpi:

    what I don't understand is that the O.P. seems to have both screens work fine. BUT i think he's using the 1.6.x xserver with git repository oss ati drivers while I'm using the latest 1.7.4.901 server. Of course I'm also on the latest 2.6.32.8 kernel as well, which I (maybe naively or wrongly) presume should exhibit the same behavior.

    now that I'm looking at the systool outputs, is it possible that udev is not handling the setup correctly if at all ?

    Thanks for the help.

    Comment


    • #17
      here are the contents of /proc/acpi/video/VGA1:

      /proc/acpi/video/VGA1/LCD/EDID
      /proc/acpi/video/VGA1/LCD/brightness
      /proc/acpi/video/VGA1/LCD/state
      /proc/acpi/video/VGA1/LCD/info
      /proc/acpi/video/VGA1/DVI/EDID
      /proc/acpi/video/VGA1/DVI/brightness
      /proc/acpi/video/VGA1/DVI/state
      /proc/acpi/video/VGA1/DVI/info
      /proc/acpi/video/VGA1/DOS
      /proc/acpi/video/VGA1/POST
      /proc/acpi/video/VGA1/POST_info
      /proc/acpi/video/VGA1/ROM
      /proc/acpi/video/VGA1/info

      I7m assuming my primary screen is LCD so the content of
      /proc/acpi/video/VGA1/LCD/brightness is:
      levels: 10 20 30 40 50 60 70 80 90 100
      current: 100

      but /proc/acpi/video/VGA1/DVI/brightness contains:
      <not supported>

      Is something not being loaded correctly is is there additional parameters I need ?

      Comment


      • #18
        Originally posted by scruffidog View Post
        I7m assuming my primary screen is LCD so the content of
        /proc/acpi/video/VGA1/LCD/brightness is:
        levels: 10 20 30 40 50 60 70 80 90 100
        current: 100

        but /proc/acpi/video/VGA1/DVI/brightness contains:
        <not supported>

        Is something not being loaded correctly is is there additional parameters I need ?
        You probably need some system specific magic to adjust the birghtness on the second panel. It really depends how the oem wired it up.

        Comment


        • #19
          sorry to keep harping on this since I'm not a programmer and I really like to fully use my hardware under an OS that is more flexible. is there anything that I can do on my end to track this down and come up with a resolution ?

          Is there a better forum or venue for me to be asking to in ?

          thanks in advance

          Comment


          • #20
            Originally posted by scruffidog View Post
            sorry to keep harping on this since I'm not a programmer and I really like to fully use my hardware under an OS that is more flexible. is there anything that I can do on my end to track this down and come up with a resolution ?

            Is there a better forum or venue for me to be asking to in ?

            thanks in advance
            Ask you laptop manufacturer for details on how it works. You might also ask on the linux acpi mailing list.

            Comment


            • #21
              Step by step for dual screen output for Onkyo DX / Kohjinsha DZ

              Finally some good news. I figured out a workaround to the whole backlighting control issue. And maybe this was something the OP already was doing but was not really clear so I'm going to explicitly spell them out here. I want to stress that this is a working convfiguration for me, ymmv applies.

              1) In the BIOS, enable dual screen clone mode:
              Advanced -> IGD Mode -> [LCD-1-2]
              save and exit [F10]

              This will turn on the backlighting for the right screen.

              2) I'm on 2.6.32.8 kernel and xorg-server 1.75. If someone needs the kernel config, drop me a line, I'm still tuning.

              Hopefully when the 1.8 line comes out, this won't need to be repeated all over again.

              3) remove /etc/X11/xorg.conf, let dbus and/or HAL do their thing. Going to let the whole dbus/HAL settle before I start playing around with X parameters. The defaults seems to be working ok, but I'm sure there could be some optimized settings to increase battery life and/or performance.

              4) compile from git the following packages (working as of 2010-02-19):
              dri2-proto
              glproto
              libdrm
              xf86-video-ati
              mesa

              5) startx and hopefully you'll have cloned desktops on both screens.

              6) xrandr --output DVI-0 --right-of LVDS

              at this point, you should have an expanded desktop.

              Now to figure out the following ACPI messages spamming my logs:

              ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC0.EC0_._Q11] (Node ffff88016181f980), AE_NOT_FOUND
              ACPI Error (psargs-0359): [\_TZ_.TZ01] Namespace lookup failure, AE_NOT_FOUND

              Comment

              Working...
              X