All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109758] AMD GPU for Ubuntu Linux Broken
Date: Sun, 24 Feb 2019 18:19:52 +0000	[thread overview]
Message-ID: <bug-109758-502-RcZ5Ds4Ad7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109758-502@http.bugs.freedesktop.org/>


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

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

--- Comment #3 from Michael Eagle <xanto@egaming.ro> ---
I am aware that the following not improve your past situation, but please
keep in mind for the future, that for a regular linux user, there is
currently 0 reasons to choose the proprietary close source amdgpu-pro.

Use the default all opensource instead. It was demonstrated multiple times
that they offer better performance, and robustness. See various articles,
forum posts, reddit/r/linux_gaming, phoronix, etc.

 And also, due to their nature of being packed together with all distros,
are much wider tested by the audience with a much broader hardware
combination. As a added bonus, you can also use the latest and greatest
bleeding endge mesa+kernel(not just that you can, but also highly
recommended) and completely forget about dkms breakage.

---
Sent from mobile, apologies for typos.

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

[-- Attachment #1.2: Type: text/html, Size: 1803 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-24 18:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  7:28 [Bug 109758] AMD GPU for Ubuntu Linux Broken bugzilla-daemon
2019-02-24 13:25 ` bugzilla-daemon
2019-02-24 18:05 ` bugzilla-daemon
2019-02-24 18:19 ` bugzilla-daemon [this message]
2019-02-24 19:21 ` bugzilla-daemon
2019-02-26  3:09 ` bugzilla-daemon
2019-02-26 19:51   ` Mihai
2019-02-26  4:28 ` bugzilla-daemon
2019-02-26  4:48 ` bugzilla-daemon
2019-02-26  5:08 ` bugzilla-daemon
2019-02-26  6:47 ` bugzilla-daemon
2019-02-26  7:51 ` bugzilla-daemon
2019-02-26  7:55 ` bugzilla-daemon
2019-02-26  8:52 ` bugzilla-daemon
2019-02-26  9:53 ` bugzilla-daemon
2019-02-26 12:30 ` bugzilla-daemon
2019-02-26 12:30 ` bugzilla-daemon
2019-02-26 12:31 ` bugzilla-daemon
2019-02-26 12:32 ` bugzilla-daemon
2019-02-26 12:32 ` bugzilla-daemon
2019-02-26 12:45 ` bugzilla-daemon
2019-02-26 19:51 ` 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-109758-502-RcZ5Ds4Ad7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.