https://bugs.freedesktop.org/show_bug.cgi?id=30620
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@lists.freedesktop.org ReportedBy: zajec5@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 anything.
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?
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #1 from Alex Deucher agd5f@yahoo.com 2010-10-05 08:12:07 PDT --- Can you attach the kms dmesg output and the Xorg log?
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #2 from Alex Deucher agd5f@yahoo.com 2010-10-05 09:15:37 PDT --- Also, please attach a copy of your video bios. To get a copy, do the following as root:
cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #3 from Rafał Miłecki zajec5@gmail.com 2010-10-05 10:24:22 PDT --- Created an attachment (id=39185) --> (https://bugs.freedesktop.org/attachment.cgi?id=39185) dmesg for KMS
I didn't want to explain how to blacklist module, test, then remove it so I proposed something different for Westa: 1) Booting with radeon.modeset=0 2) rmmod radeon && modprobe radeon modeset=1
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #4 from Rafał Miłecki zajec5@gmail.com 2010-10-05 10:25:18 PDT --- Created an attachment (id=39186) --> (https://bugs.freedesktop.org/attachment.cgi?id=39186) [UMS] Xorg.0.log
Xorg.0.log form *UMS* as problem seems to be shared between KMS and UMS. This may give some hint on fixing it.
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #5 from Alex Deucher agd5f@yahoo.com 2010-10-05 10:42:02 PDT --- Everything looks correct. Can you dump the regs using radeontool with kms and with radeonfb? As root: with radeonfb: radeontool regmatch '*' > working.regs with kms: radeontool regmatch '*' > broken.regs
You can get radeontool here: http://cgit.freedesktop.org/~airlied/radeontool/
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #6 from Rafał Miłecki zajec5@gmail.com 2010-10-05 12:29:10 PDT --- Created an attachment (id=39189) --> (https://bugs.freedesktop.org/attachment.cgi?id=39189) regs dump when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #7 from Rafał Miłecki zajec5@gmail.com 2010-10-05 12:29:37 PDT --- Created an attachment (id=39190) --> (https://bugs.freedesktop.org/attachment.cgi?id=39190) regs dump when using radeonfb
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #8 from Rafał Miłecki zajec5@gmail.com 2010-10-05 12:31:36 PDT --- Created an attachment (id=39192) --> (https://bugs.freedesktop.org/attachment.cgi?id=39192) diff -u broken.regs working.regs
https://bugs.freedesktop.org/show_bug.cgi?id=30620
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #39192|text/x-diff |text/plain mime type| | Attachment #39192|0 |1 is patch| |
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #9 from Alex Deucher agd5f@yahoo.com 2010-10-05 14:43:25 PDT --- Does the following fix kms/ums? radeontool regset 0x0284 0x00230000
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #10 from Alex Deucher agd5f@yahoo.com 2010-10-05 15:10:25 PDT --- Created an attachment (id=39197) View: https://bugs.freedesktop.org/attachment.cgi?id=39197 Review: https://bugs.freedesktop.org/review?bug=30620&attachment=39197
disable alt timing for CRT
This kms patch should fix the issue I think.
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #11 from Rafał Miłecki zajec5@gmail.com 2010-10-16 00:58:35 PDT --- (In reply to comment #9)
Does the following fix kms/ums? radeontool regset 0x0284 0x00230000
I got false positive report about this :(
What I asked for was executing: 1) Boot without vga=... and with radeon.modeset=0 3 2) Executing rmmod radeon 3) Executing: modprobe radeon modeset=1; sleep 5s; radeontool regset 0x0284 0x00230000
I got response monitor gone black and then came on again. But I now I know it has happened after 1s, not 5s! It seems loading radeon this one time didn't break VGA output.
Maybe some register survived reboot? Maybe regs dumps are not clean actually, maybe I should ask to grab them from cold boot? :|
https://bugs.freedesktop.org/show_bug.cgi?id=30620
Jerome Glisse glisse@freedesktop.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|KMS on RS100: no display on |[RADEON:KMS:RS100:MODESET] |VGA |no display on VGA
https://bugs.freedesktop.org/show_bug.cgi?id=30620
--- Comment #12 from auxsvr@gmail.com --- Created attachment 68470 --> https://bugs.freedesktop.org/attachment.cgi?id=68470&action=edit diff -u regs-fail regs-working
I just tried installing openSUSE 12.1 on an old compaq presario 900 with a broken TFT panel and have exactly the same problem. Setting register 0x0284 does not work, and shortly after reloading radeon with modeset=1 the system hangs. Is there anything else to try?
The attached diff compares the register values when modeset=0 (working) with them when modeset=1 (fail).
https://bugs.freedesktop.org/show_bug.cgi?id=30620
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #13 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/160.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org