dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 22:30:20 +0000	[thread overview]
Message-ID: <bug-71516-502-uFaU4p3qC7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71516-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=71516

--- Comment #16 from Elven Decker <sailing@together.net> ---
Progress!!

Starting from the login screen, I press control-alt F2 to bring up a command
line.  Then I run startx.  I don't get a window manager, but I can find my way
to xterm and then work from the command line after X starts.  glxgears looks
normal - smooth and as quickly as I believe the 9550 can go. :)  Opening
firefox, CNN and youtube videos play smoothly.

>From your comments, I believe I have sidestepped lightdm. I opened synaptic and
reinstalled lightdm and associated programs.  I then minimized synaptic and now
I know what the display manager does.  That's OK, I'll be rebooting anyway.

Next steps?  I believe there is /usr/lib and an /etc folders.  Can I clean them
out and do another re-install?  Will the config files get regenerated?

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1789 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

  parent reply	other threads:[~2013-11-15 22:30 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
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 [this message]
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-uFaU4p3qC7@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