Date: Thu, 16 Aug 2018 22:11:03 +0300 From: Greg V <greg@unrelenting.technology> To: Stefan Rumetshofer <sterum77@gmail.com> Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Testing the linux compatibility with the amdgpu driver and linux-doom3 fails Message-ID: <1534446663.2150.2@hraggstad.unrelenting.technology> In-Reply-To: <CAK_LXuA3H3JTrpMY6F_rk62iEV_9TjvXkWcdEBB2hkxFKGcQqQ@mail.gmail.com> References: <255786377.P3pStmDMii@saturn.lan> <1534440727.2150.0@hraggstad.unrelenting.technology> <CAK_LXuA3H3JTrpMY6F_rk62iEV_9TjvXkWcdEBB2hkxFKGcQqQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 16, 2018 at 9:42 PM, Stefan Rumetshofer=20 <sterum77@gmail.com> wrote: >=20 >=20 > Am Donnerstag, 16. August 2018 schrieb Greg V : >>=20 >>=20 >> On Thu, Aug 16, 2018 at 7:46 PM, Stefan Rumetshofer=20 >> <sterum77@gmail.com> wrote: >>> Firts of all i hope this is not the wrong mailing list. >>>=20 >>> I was trying to run linux-doom3 from the ports collection with my=20 >>> graphics >>> hardware but this fails with an error realted to OpenGL or so. Also=20 >>> other >>> linux games are failing like Unreal or RTCW. It seems that there is=20 >>> a general >>> Problem with the amd Graphics driver and the linux compatibility. I=20 >>> also teted >>> the game wit the intel driver on my SandyBridge GPU with no error. >> Hi, >>=20 >> was the sandybridge system running i915 also from drm-next or the=20 >> old in-tree version? >=20 > It was the same system with the Radeon card detached. The i915kms.ko=20 > was loaded via the rc.conf and the xf86-video-intel port was=20 > installed and loaded with the xorg.conf file. Tomorrow i can upload=20 > the Xorg.0.log files if they are needed. If you just load it without the full /boot/modules path, it's the=20 system one=85 >>=20 >>> My graphics hardware is an AMD Radeon RX560. OS is a FreeBSD=20 >>> 11.2-RELEASE with >>> drm-next-kmod and xf86-video-amdgpu. The kernel module is loaded=20 >>> with >>> kld_list=3D"amdgpu" in the rc.conf and the X11 driver is loaded with=20 >>> 'Driver >>> "amdgpu"' in the Device Section of the xorg.conf. Xorg works fine=20 >>> with this >>> configuration. >>>=20 >>> Following linux related packages are installed: >>> linux-c7-dri-17.0.1 =3D up-to-date with remote >>> linux-c7-elfutils-libelf-0.168 =3D up-to-date with remote >>> linux-c7-expat-2.1.0_2 =3D up-to-date with remote >>> linux-c7-fontconfig-2.10.95_3 =3D up-to-date with remote >>> linux-c7-glx-utils-8.2.0_4 =3D up-to-date with remote >>> linux-c7-libpciaccess-0.13.4_3 =3D up-to-date with remote >>> linux-c7-xorg-libs-7.7_5 =3D up-to-date with remote >>> linux-doom3-1.3.1.1304,1 =3D up-to-date with remote >>> linux_base-c7-7.4.1708_6 =3D up-to-date with remote >>>=20 >>> When running linux-doom3 i get the following output: >>> % linux-doom3 >>> [...] >>> ------------------------------- >>> using ARB_vertex_buffer_object memory >>> using ARB2 renderSystem >>> signal caught: Segmentation fault >>> si_code 1 >>=20 >> A backtrace would be useful here. >> Was a core dump produced? >=20 > No coredump because i disabled it with kern.coredump=3D0 but i can=20 > change this and look if a dump will be created. Tomorrow... >>=20 >>=20 >> Anyway, I definitely have run Linux GL applications on amdgpu, but I=20 >> was using an Ubuntu chroot instead of the linux-* ports. >=20 > Which Ubuntu version should i try? How can i create such a chroot. Is=20 > it possible to install an Ubuntu on a separate disk, tar it up and=20 > unpack it to /compat/linux. 16.04 or older. Just download e.g.=20 https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64= -root.tar.xz untar somewhere (anywhere, e.g. under the home dir), mount linprocfs,=20 linsysfs and devfs under there, chroot into that, and you can use apt=20 and whatnot =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1534446663.2150.2>