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 07:28:31 +0000	[thread overview]
Message-ID: <bug-109758-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 109758
           Summary: AMD GPU for Ubuntu Linux Broken
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tomhansen992@gmail.com

You should put a warning label up whenever you are handing out free "break your
linux distro" drivers. A few months ago I tried to install the driver on 18.10
I had to look online to find out that it breaking the Linux install was the
intended effect. Okay, so I bought this computer with a 570 like two years ago
and it hasn't been properly supported this entire time. Linux gets updated to
4.18 on Ubuntu and my GPU isn't giving me the same error it has been for the
last entire time I had the computer, exciting. I try to install the drivers and
WOW it breaking is still the intended result. I notice I have Ubuntu 18.04.2,
the one advertised is 18.04.1 and sure enough Google tells me that the intended
effect was to break my Linux. My complaint is if you know that you're going to
break my computer over and over again just give me some warnings, like "hey
this doesn't work on Linux 4.18" instead of just handing it out like Malware.
This is 3 years in and I still do not have proper support for my GPU on Linux.
Sorry for being frustrated but this company has caused my anguish for no good
reason. The error is DKMS failed or something after it installs but you guys
already know that it doesn't work with a fresh install of Ubuntu. I'm not
downgrading my Linux so I get the errors on startup again I have to wait for
you guys to properly support my GPU 2 years after the GPU was released. Do you
guys give refunds for this sort of thing I had to reinstall my operating system
more than 6 times slowing down everything I wanted to do. When rich people have
their time wasted they get to sue people..

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

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

             reply	other threads:[~2019-02-24  7:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  7:28 bugzilla-daemon [this message]
2019-02-24 13:25 ` [Bug 109758] AMD GPU for Ubuntu Linux Broken bugzilla-daemon
2019-02-24 18:05 ` bugzilla-daemon
2019-02-24 18:19 ` bugzilla-daemon
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@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.