dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Paterni <bpaterni@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Some issues with the new amdgpu driver
Date: Sat, 09 May 2015 19:11:09 -0500	[thread overview]
Message-ID: <554EA21D.8030109@gmail.com> (raw)
In-Reply-To: <554DC68A.3030808@daenzer.net>

On 05/09/2015 03:34 AM, Michel Dänzer wrote:
> On 09.05.2015 11:44, Brian Paterni wrote:
>> On 05/07/2015 04:07 AM, Michel Dänzer wrote:
>>> On 06.05.2015 12:12, Brian Paterni wrote:
>>>>
>>>> I was on irc a few days ago trying to get the new amdgpu driver up and
>>>> running on my system. I am able to get the kernel booted successfully,
>>>> however X via amdgpu is turning out to be a real roadblock. It is the
>>>> problem with amdgpu_drv.so seeing gbm_create_device as an undefined
>>>> symbol. From what little I understand, I may be needing a more recent
>>>> xserver to resolve this...
>>>
>>> I don't think that would help.
>>>
>>> Does the attached xf86-video-amdgpu patch fix the problem?
>>>
>>> If not, you can manually load the glamoregl module in /etc/X11/xorg.conf
>>> to pull in libgbm:
>>>
>>> Section "Module"
>>> 	Load	"glamoregl"
>>> EndSection
>>>
>>>
>>
>> Hi Michel, thanks for the reply. I got around to recompiling the stack
>> from the latest trees as noted by Alex earlier. However, I'm afraid
>> something may have changed recently and I may be needing a newer xserver
>> after all. Loading amdgpu_drv.so now results in:
>>
>> [  1122.347] (EE) module ABI major version (19) doesn't match the
>> server's version (18)
> 
> That just means the driver it's trying to load wasn't built against the
> same version of xserver. Make sure the xf86-video-amdgpu build is
> picking up the xorg-server.pc and header files of the same version of
> xserver you're trying to run.
> 
> 

Oops! Looks like I forgot to cc the mailing list.

I think my version mismatch issues above may have been resolved by a
recent upload of xserver-xorg-core 2:1.17.1-2 to debian unstable(?)...

As a result, I could finally test Michel's patch, and I am happy to say
that X via amdgpu is now working for me! Thanks to Michel! :)

However, the two additional issues mentioned in my initial post are
still present:

*) Non-working DVI-I-0 -- even if I use xrandr to turn it off and on
again, a signal is never acquired.

*) System lockup on xen boot (even magic sysrq is not recognized)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-05-10  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  3:12 Some issues with the new amdgpu driver Brian Paterni
2015-05-07  9:07 ` Michel Dänzer
     [not found]   ` <554D7478.40408@gmail.com>
     [not found]     ` <554DC68A.3030808@daenzer.net>
2015-05-10  0:11       ` Brian Paterni [this message]
2015-05-10 16:06         ` Brian Paterni

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=554EA21D.8030109@gmail.com \
    --to=bpaterni@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    /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