From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40576] HD4290 (Asus M4A89GTD/Pro onboard): no DRI (/dev/dri/card0) with CONFIG_DRM_RADEON_KMS enabled
Date: Fri, 2 Sep 2011 08:42:16 -0700 (PDT) [thread overview]
Message-ID: <20110902154216.8B45E1300BD@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-40576-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=40576
--- Comment #5 from RandomCore <freedesktop@erben.com> 2011-09-02 08:42:15 PDT ---
You were right; partly. It was tehre, but I guess the pathes in the kernel
build got mixed up. Since I didn't know which firmware to include I included
all, whihc made the string constant too long and the make fell back to
configuration. So I changed the _DIR to "/lib/firmware/radeon" and added the
firmwares without "radeon/" as prefix. Well, seems to have messed up the build
process.
Anyway, I did a mrproper and just included the R*.bin files. Here's the
outcome:
$ dmesg|grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
[drm] initializing kernel modesetting (RS880 0x1002:0x9714).
[drm] register mmio base: 0xFE6F0000
[drm] register mmio size: 65536
[drm] Detected VRAM RAM=368M, BAR=256M
[drm] RAM width 32bits DDR
[drm] radeon: 368M of VRAM memory ready
[drm] radeon: 512M of GTT memory ready.
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
[drm] radeon: irq initialized.
[drm] GART: num cpu pages 131072, num gpu pages 131072
[drm] Loading RS780 Microcode
[drm:r600_ring_test] *ERROR* radeon: ring test failed
(scratch(0x8504)=0xCAFEDEAD)
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm] VGA
[drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[drm] Encoders:
[drm] CRT1: INTERNAL_KLDSCP_DAC1
[drm] Connector 1:
[drm] DVI-D
[drm] HPD3
[drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[drm] Encoders:
[drm] DFP1: INTERNAL_KLDSCP_LVTMA
[drm] radeon: power management initialized
[drm] fb mappable at 0xD0141000
[drm] vram apper at 0xD0000000
[drm] size 9216000
[drm] fb depth is 24
[drm] pitch is 7680
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
fbcon: radeondrmfb (fb1) is primary device
fb1: radeondrmfb frame buffer device
drm: registered panic notifier
[drm] Initialized radeon 2.10.0 20080528 for 0000:01:05.0 on minor 0
I guess a failing ring-test is not that good. Performance (glxgears) is still
around 730 FPS.
Which firmwares shall I include for my HD4290 / RS880?
Shall I disable the VESA console fb device?
Oh, and there was no 30s pause anymore.
cu, RandomCore
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-09-02 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 12:03 [Bug 40576] New: HD4290 (Asus M4A89GTD/Pro onboard): no DRI (/dev/dri/card0) with CONFIG_DRM_RADEON_KMS enabled bugzilla-daemon
2011-09-02 13:06 ` [Bug 40576] " bugzilla-daemon
2011-09-02 13:58 ` bugzilla-daemon
2011-09-02 14:50 ` bugzilla-daemon
2011-09-02 14:59 ` bugzilla-daemon
2011-09-02 15:42 ` bugzilla-daemon [this message]
2011-09-02 15:58 ` bugzilla-daemon
2011-09-02 16:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110902154216.8B45E1300BD@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox