From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71516] RV350 Radeon 9550 - no Unity 3D hardware support in Ubuntu 13.10, extremely slow
Date: Fri, 15 Nov 2013 02:34:59 +0000 [thread overview]
Message-ID: <bug-71516-502-HsgXnFLoeu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71516-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 933 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71516
--- Comment #11 from Elven Decker <sailing@together.net> ---
X won't start without LIBGL_ALWAYS_SOFTWARE set. Log file is Xort.0.log.sav
above.
I notice that Xorg.0.log and lspci identify my card in different ways? Radeon
9600 vs. 9550?
>From Xorg.0.log
(--) RADEON(0): Chipset: "ATI Radeon 9600 AS (AGP)" (ChipID = 0x4153)
lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] RV350 [Radeon 9550] [1002:4153]
***
Another thought...
Not sure anybody needs to run Xorg -configure anymore, but I tried it to see if
I could learn anything and got the message "Number of created screens does not
match number of detected devices". The configure process noted three screens
and three monitors, I believe my card supports my monitor and an external TV.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1790 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-15 2:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 0:54 [Bug 71516] New: RV350 Radeon 9550 - no Unity 3D hardware support in Ubuntu 13.10, extremely slow bugzilla-daemon
2013-11-12 2:55 ` [Bug 71516] " bugzilla-daemon
2013-11-12 13:21 ` bugzilla-daemon
2013-11-12 13:23 ` bugzilla-daemon
2013-11-12 13:41 ` bugzilla-daemon
2013-11-13 1:58 ` bugzilla-daemon
2013-11-13 3:51 ` bugzilla-daemon
2013-11-14 1:25 ` bugzilla-daemon
2013-11-14 2:07 ` bugzilla-daemon
2013-11-15 1:29 ` bugzilla-daemon
2013-11-15 2:20 ` bugzilla-daemon
2013-11-15 2:34 ` bugzilla-daemon [this message]
2013-11-15 3:05 ` bugzilla-daemon
2013-11-15 11:23 ` bugzilla-daemon
2013-11-15 11:43 ` bugzilla-daemon
2013-11-15 11:46 ` bugzilla-daemon
2013-11-15 22:30 ` bugzilla-daemon
2013-11-16 22:26 ` bugzilla-daemon
2013-11-17 20:00 ` bugzilla-daemon
2013-11-17 20:01 ` [Bug 71516] [SOLVED] " bugzilla-daemon
2013-11-18 6:35 ` bugzilla-daemon
2013-12-31 13:35 ` 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=bug-71516-502-HsgXnFLoeu@http.bugs.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