Re: X11 on Ryzen 2400G?

2019-01-31 Thread Phil Norman
On Wed, 30 Jan 2019 at 22:24, Pete Wright  wrote:

>
>
> On 1/30/19 12:10 PM, Phil Norman wrote:
>
[snip]

>
>> - after you have configured the amdgpu.ko to load on boot verify it is
>> able to load the kernel module and your console display looks good.  if
>> you have issues loading the kernel module let us know, there are some
>> things you can try to setup to get a useful backtrace that will help us
>> debug this.
>>
>
> This is where I get to. I've removed amdgpu from /etc/rc.conf, so I don't
> have to boot single-user mode; when I run kldload amdgpu, the following
> happens:
>
> 1: the 'kldload amdgpu' process doesn't return immediately, yet the
> terminal is responsive; I can hit return, and have the cursor move. The
> mouse pointer also moves.
> 2: something around 5s later, the screen turns off, the keyboard goes
> unresponsive (caps lock light doesn't toggle), and the machine no longer
> responds to pings.
>
>
> interesting, it looks like the kernel module and firmware modules do
> load.  one thing you may want to test is setting the
> "debug.debugger_on_panic=0" sysctl knob before loading the amdgpu.ko.
> hopefully this will allow you to get into a debugger before the system
> locks up.
>

I just tried 'sysctl debug.debugger_on_panic=0' from the command line - it
printed out that it was being switched from 1 -> 0. Then tried kldload
amdgpu, and unfortunately it behaved exactly the same as previously
reported. So no debugger for me.

Should I be reporting this in freebsd-x11? Or some other forum? I remember
there being a somewhat heated discussion about the drm kernel module not
always being 100% stable, back in the Summer I believe.

I suppose one further question: is anyone else successfully using the
in-built graphics from a Ryzen G chip with X11? And if so, any advice on
versions of things, or flags to set?

Thanks again for the advice.
Phil
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: X11 on Ryzen 2400G?

2019-01-30 Thread Pete Wright



On 1/30/19 12:10 PM, Phil Norman wrote:

Hi.

First of all, thanks for the detailed instructions. Response inline.



sure thing!


-- pay special attention to the update the /boot/loader.conf


Are you referring to the need to set 'hw.sysconf.disable=1', or is 
there something else I'm missing? I didn't see anything else on the 
wiki page, except for some debugging options (which I guess I'm going 
to end up using soon).


yes that is what i was referring to.  I do not have an AMDGPU system 
myself but have been told several times that it is required.




- after you have configured the amdgpu.ko to load on boot verify
it is
able to load the kernel module and your console display looks
good.  if
you have issues loading the kernel module let us know, there are some
things you can try to setup to get a useful backtrace that will
help us
debug this.


This is where I get to. I've removed amdgpu from /etc/rc.conf, so I 
don't have to boot single-user mode; when I run kldload amdgpu, the 
following happens:


1: the 'kldload amdgpu' process doesn't return immediately, yet the 
terminal is responsive; I can hit return, and have the cursor move. 
The mouse pointer also moves.
2: something around 5s later, the screen turns off, the keyboard goes 
unresponsive (caps lock light doesn't toggle), and the machine no 
longer responds to pings.




interesting, it looks like the kernel module and firmware modules do 
load.  one thing you may want to test is setting the 
"debug.debugger_on_panic=0" sysctl knob before loading the amdgpu.ko.  
hopefully this will allow you to get into a debugger before the system 
locks up.


cheers,
-pete


--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: X11 on Ryzen 2400G?

2019-01-30 Thread Phil Norman
Hi.

First of all, thanks for the detailed instructions. Response inline.

On Wed, 30 Jan 2019 at 20:07, Pete Wright  wrote:

>
>
> On 1/30/19 9:57 AM, Phil Norman wrote:
> > Hi.
> >
> > I recently got a Ryzen 2400G, which has on-board AMD Vega 11 graphics. I
> > can get a console to display via the motherboard's on-board HDMI, but
> > haven't been able to get Xorg working yet. I'm trying the 'amdgpu'
> driver,
> > and am using an xorg.conf file generated with 'Xorg -configure' (albeit
> > hand-tweaked to get rid of the nonexistent second screen it added, and
> fix
> > a few more things).
> >
> > My understanding is that the driver is likely borrowed from linux, and
> > (from http://forum.mxlinux.org/viewtopic.php?t=46887) Vega support only
> > started working with linux kernel 1.19. The /var/log/Xorg.0.log file says
> > that the amdgpu module was 'compiled for 1.18.4, module version =
> 18.1.0'.
> > Does the 1.18.4 refer to a linux kernel version? If so, what's my best
> > solution here? Should I just wait until the FreeBSD drivers are updated?
> Is
> > there anything I can do in the meantime?
>
> I believe there may be some previous success running Vega graphics on
> FreeBSD.  Couple things to note:
>
> - If possible run 12.0-RELEASE
>

Already doing that. I also did a 'pkg update ; pkg upgrade' to make sure
everything's shiny. I'm not using any self-built modules.
$ uname -a
FreeBSD bob 12.0-STABLE FreeBSD 12.0-STABLE r343112 GENERIC  amd64



> - install the drm-kmod package, then closely follow the instructions
> printed on your console.  This wiki section should offer some help:
> https://wiki.freebsd.org/Graphics#AMD_Graphics


Instructions followed.


> -- pay special attention to the update the /boot/loader.conf
>

Are you referring to the need to set 'hw.sysconf.disable=1', or is there
something else I'm missing? I didn't see anything else on the wiki page,
except for some debugging options (which I guess I'm going to end up using
soon).


>
> - after you have configured the amdgpu.ko to load on boot verify it is
> able to load the kernel module and your console display looks good.  if
> you have issues loading the kernel module let us know, there are some
> things you can try to setup to get a useful backtrace that will help us
> debug this.
>

This is where I get to. I've removed amdgpu from /etc/rc.conf, so I don't
have to boot single-user mode; when I run kldload amdgpu, the following
happens:

1: the 'kldload amdgpu' process doesn't return immediately, yet the
terminal is responsive; I can hit return, and have the cursor move. The
mouse pointer also moves.
2: something around 5s later, the screen turns off, the keyboard goes
unresponsive (caps lock light doesn't toggle), and the machine no longer
responds to pings.

I see nothing in /var/crash/. /var/log/messages has a bunch of text:

Jan 30 16:52:50 bob kernel: [drm] amdgpu kernel modesetting enabled.
Jan 30 16:52:50 bob kernel: drmn0:  on vgapci0
Jan 30 16:52:50 bob kernel: vgapci0: child drmn0 requested pci_enable_io
Jan 30 16:52:50 bob syslogd: last message repeated 1 times
Jan 30 16:52:50 bob kernel: [drm] initializing kernel modesetting (RAVEN
0x1002:0x15DD 0x1002:0x15DD 0xC6).
Jan 30 16:52:50 bob kernel: [drm] register mmio base: 0xFE50
Jan 30 16:52:50 bob kernel: [drm] register mmio size: 524288
Jan 30 16:52:50 bob kernel: [drm] PCI I/O BAR is not found.
Jan 30 16:52:51 bob kernel: drmn0: successfully loaded firmware image with
name: amdgpu/raven_gpu_info.bin
Jan 30 16:52:51 bob kernel: [drm] probing gen 2 caps for device 1022:15db =
700d03/e
Jan 30 16:52:51 bob kernel: [drm] probing mlw for device 1002:15dd = 400d03
Jan 30 16:52:51 bob kernel: [drm] VCN decode is enabled in VM mode
Jan 30 16:52:51 bob kernel: [drm] VCN encode is enabled in VM mode
Jan 30 16:52:51 bob kernel: pci_is_thunderbolt_attached not implemented --
see your local kernel hacker
Jan 30 16:52:51 bob kernel: [drm] BIOS signature incorrect 0 0
Jan 30 16:52:51 bob kernel: ATOM BIOS: 113-RAVEN-110
Jan 30 16:52:51 bob kernel: [drm] vm size is 262144 GB, 4 levels, block
size is 9-bit, fragment size is 9-bit
Jan 30 16:52:51 bob kernel: drmn0: VRAM: 2048M 0x00F4 -
0x00F47FFF (2048M used)
Jan 30 16:52:51 bob kernel: drmn0: GTT: 1024M 0x00F5 -
0x00F53FFF
Jan 30 16:52:51 bob kernel: Successfully added WC MTRR for
[0xe000-0xefff]: 0;
Jan 30 16:52:51 bob kernel: [drm] Detected VRAM RAM=2048M, BAR=256M
Jan 30 16:52:51 bob kernel: [drm] RAM width 64bits UNKNOWN
Jan 30 16:52:51 bob kernel: [TTM] Zone  kernel: Available graphics memory:
7270680 kiB
Jan 30 16:52:51 bob kernel: [TTM] Zone   dma32: Available graphics memory:
2097152 kiB
Jan 30 16:52:51 bob kernel: [TTM] Initializing pool allocator
Jan 30 16:52:51 bob kernel: [drm] amdgpu: 2048M of VRAM memory ready
Jan 30 16:52:51 bob kernel: [drm] amdgpu: 3072M of GTT memory ready.
Jan 30 16:52:51 bob kernel: i_size_write unimplemented
Jan 30 16:52:51 bob kernel: [drm] GART: num 

Re: X11 on Ryzen 2400G?

2019-01-30 Thread Pete Wright



On 1/30/19 9:57 AM, Phil Norman wrote:

Hi.

I recently got a Ryzen 2400G, which has on-board AMD Vega 11 graphics. I
can get a console to display via the motherboard's on-board HDMI, but
haven't been able to get Xorg working yet. I'm trying the 'amdgpu' driver,
and am using an xorg.conf file generated with 'Xorg -configure' (albeit
hand-tweaked to get rid of the nonexistent second screen it added, and fix
a few more things).

My understanding is that the driver is likely borrowed from linux, and
(from http://forum.mxlinux.org/viewtopic.php?t=46887) Vega support only
started working with linux kernel 1.19. The /var/log/Xorg.0.log file says
that the amdgpu module was 'compiled for 1.18.4, module version = 18.1.0'.
Does the 1.18.4 refer to a linux kernel version? If so, what's my best
solution here? Should I just wait until the FreeBSD drivers are updated? Is
there anything I can do in the meantime?


I believe there may be some previous success running Vega graphics on 
FreeBSD.  Couple things to note:


- If possible run 12.0-RELEASE
- install the drm-kmod package, then closely follow the instructions 
printed on your console.  This wiki section should offer some help:

https://wiki.freebsd.org/Graphics#AMD_Graphics
-- pay special attention to the update the /boot/loader.conf

- after you have configured the amdgpu.ko to load on boot verify it is 
able to load the kernel module and your console display looks good.  if 
you have issues loading the kernel module let us know, there are some 
things you can try to setup to get a useful backtrace that will help us 
debug this.


- try moving your Xorg.conf out of the way then try starting X.
-- If that fails try dropping your custom config in there which is using 
the amdgpu Xorg driver.



Hope this helps!
-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: X11 on Ryzen 2400G?

2019-01-30 Thread Matt Garber

> On Jan 30, 2019, at 12:57 PM, Phil Norman  wrote:
> 
> My understanding is that the driver is likely borrowed from linux, and
> (from http://forum.mxlinux.org/viewtopic.php?t=46887) Vega support only
> started working with linux kernel 1.19. The /var/log/Xorg.0.log file says
> that the amdgpu module was 'compiled for 1.18.4, module version = 18.1.0'.
> Does the 1.18.4 refer to a linux kernel version? If so, what's my best
> solution here? Should I just wait until the FreeBSD drivers are updated? Is
> there anything I can do in the meantime?

Just a point of clarification, I think you’re mixing version numbers up a bit: 
the Linux kernel version discussed in that forum refers to kernel 4.19 
(released Oct 22, 2018), not 1.19. The “compiled for 1.18.4” line is referring 
to the Xorg server version, not a Linux kernel version (there never was a Linux 
kernel 1.18, it jumped from patches against 1.0 to 1.1.x versions around 
~April-May 1994.

Depending on where your amdgpu module came from (e.g., if you compiled it 
yourself), the first thing I’d verify as a starter is that the “compiled for” 
version actually matches the Xorg server version you have installed via 
packages/ports/etc.


Thanks,
—
Matt Garber

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


X11 on Ryzen 2400G?

2019-01-30 Thread Phil Norman
Hi.

I recently got a Ryzen 2400G, which has on-board AMD Vega 11 graphics. I
can get a console to display via the motherboard's on-board HDMI, but
haven't been able to get Xorg working yet. I'm trying the 'amdgpu' driver,
and am using an xorg.conf file generated with 'Xorg -configure' (albeit
hand-tweaked to get rid of the nonexistent second screen it added, and fix
a few more things).

My understanding is that the driver is likely borrowed from linux, and
(from http://forum.mxlinux.org/viewtopic.php?t=46887) Vega support only
started working with linux kernel 1.19. The /var/log/Xorg.0.log file says
that the amdgpu module was 'compiled for 1.18.4, module version = 18.1.0'.
Does the 1.18.4 refer to a linux kernel version? If so, what's my best
solution here? Should I just wait until the FreeBSD drivers are updated? Is
there anything I can do in the meantime?

Thanks in advance,
Phil
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"