Date: Tue, 13 Dec 2016 14:49:22 +0100 From: Werner Lehmann <lehmannwer@gmail.com> To: x11@FreeBSD.org Subject: Linux 3D Games/Ports do not work anymore with Mesa-Drivers Message-ID: <1481636962.12224.0@smtp.gmail.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Dear Sirs, I have FreeBSD amd64 11.0-p1 installed with a Radeon HD 4850 graphics card on a spare PC for experimental purposes. In the past (maybe 2 or 3 years ago) the linux-doom3-port used to run perfectly on FreeBSD with that Radeon card and the Mesa-Drivers. But now suddenly I get the following error for all of these ports: linux-doom3-demo, linux-quake4-demo and ut2003-demo $ ut2003-demo fcntl: Invalid argument Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. libGL error: unable to load driver: r600_dri.so libGL error: driver pointer missing libGL error: failed to load driver: r600 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast X Error: BadValue Request Major code 154 (GLX) Request Minor code 3 () Value 0x0 Error Serial #31 Current Serial #32 linux-doom3-demo: ... -------------------------------------- ----- R_InitOpenGL ----- dlopen(libGL.so.1) Initializing OpenGL display Using XFree86-VidModeExtension Version 2.2 DGA DirectVideo Mouse (Version 2.0) initialized Free86-VidModeExtension Activated at 640x480 Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. libGL error: unable to load driver: r600_dri.so libGL error: driver pointer missing libGL error: failed to load driver: r600 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast Using 8/8/8 Color bits, 8 Alpha bits, 24 depth, 8 stencil display. Fatal X Error: Major opcode of failed request: 154 Minor opcode of failed request: 3 Serial number of failed request: 53 BadValue Fatal X Error: Major opcode of failed request: 154 Minor opcode of failed request: 5 Serial number of failed request: 55 GLXBadContext Fatal X Error: Major opcode of failed request: 154 Minor opcode of failed request: 26 Serial number of failed request: 55 0 GL_RENDERER: (null) GL_EXTENSIONS: (null) Terminated linux-quake4-demo: ... --------------- R_InitOpenGL ---------------- Initializing SDL subsystem Loading GL driver 'libGL.so.1' through SDL Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. Couldn't dlopen libudev.so.1 or libudev.so.0, driver detection may be broken. libGL error: unable to load driver: r600_dri.so libGL error: driver pointer missing libGL error: failed to load driver: r600 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast X Error: BadValue Request Major code 154 (GLX) Request Minor code 3 () Value 0x0 Error Serial #31 Current Serial #32 It appears to be that the issue in these three cases (and probably any other linux-3D-program) is a dependency on "libudev.so.1" which does not exist in FreeBSD. Googeling I also found this following older bug report which seems to confirm a relation of Mesa libGL to linux systemd: https://bugzilla.redhat.com/show_bug.cgi?id=1168475 Could you please look into this matter and respond if this issue can be fixed? Needless to say that these games run fine with an nvidia-card on another computer, but it would be a pity that this possibility would be lost for Radeon (and Intel?) users when it did work in the past. I also would like to point out that the port darkplaces works fine with 60 fps on the Radeon as it is native. Kind regards, Werner Lehmann [-- Attachment #2 --]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1481636962.12224.0>