[Bug 30620] New: KMS on RS100: no display on VGA

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Oct 5 04:41:29 PDT 2010


           Summary: KMS on RS100: no display on VGA
           Product: DRI
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: zajec5 at gmail.com

I've bug report from user with old notebook with ATI 320M (RS100). She
installed openSUSE 11.3 which comes with 2.6.34 and can not get driver display

The important part is that notebook's PANEL is broken and she uses VGA for
external monitor.

There are two KMS cases I got tested by her:
1) "vga=0x31a" ─ black VGA screen right after booting start
2) "" (no vga) ─ black VGA screen right after booting start

So I asked to experiment with UMS a little:
3) "vga=0x31a radeon.modeset=0 3" ─ radeonfb loads, VGA works!
4) "vga=0x31a radeon.modeset=0" ─ radeonfb works, black VGA screen on X start

Without radeonfb:
5) "radeon.modeset=0 3" ─ pure console works on VGA, no radeonfb
6) "radeon.modeset=0" ─ pure console works on VGA, black VGA on X start

My conclusions:
1) KMS can not initialize VGA
2) UMS can not initialize VGA
3) radeonfb *can* initialize VGA
4) There is no conflict with radeonfb, as dropping "vga=0x31a" does not help

What else can I ask for to make it debuggable?

I thought of Xorg.0.log but it may be hard to get for her as she had to mount
some USB storage in console and copy file to it.
Taking "dmesg | grep drm" could be easier. Would it be useful?

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list