08-22-2015, 11:20 PM
08-23-2015, 11:18 PM
Ah so this is genuinely a problem with the nvidia drivers? Is the mesa implementation needed from upstream, or within pcsx2?
08-23-2015, 11:23 PM
Wait what is your hw/driver exactly?
08-24-2015, 09:16 PM
(08-23-2015, 11:23 PM)gregory Wrote: [ -> ]Wait what is your hw/driver exactly?
I'm running an nvidia GeForce GTX 460 with the nvidia closed source driver no. 352.21:
Code:
$ uname -a
Linux media.weaver 4.0.8-300.fc22.x86_64 #1 SMP Fri Jul 10 21:04:56 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa | grep nvidia
kmod-nvidia-4.0.8-300.fc22.x86_64-352.21-1.fc22.x86_64
akmod-nvidia-352.21-1.fc22.x86_64
xorg-x11-drv-nvidia-kmodsrc-352.21-1.fc22.x86_64
xorg-x11-drv-nvidia-352.21-1.fc22.x86_64
xorg-x11-drv-nvidia-libs-352.21-1.fc22.x86_64
xorg-x11-drv-nvidia-libs-352.21-1.fc22.i68608-24-2015, 10:35 PM
Download latest source and retry please. Don't strip the debug symbol so I can see the source of the crash.
08-25-2015, 12:23 AM
Seem fixed (this is the Debug build, so let me know if you want me to test it more):
Code:
glX-Version 1.4 with Direct Rendering
OpenGL information. GPU: GeForce GTX 460/PCIe/SSE2. Vendor: NVIDIA Corporation. Driver: NVIDIA 352.21
INFO: GL_EXT_texture_filter_anisotropic is available
INFO: GL_ARB_gpu_shader5 is available
INFO: GL_ARB_draw_buffers_blend is available
INFO: GL_ARB_separate_shader_objects is available
INFO: GL_ARB_shader_image_load_store is available
INFO: GL_ARB_copy_image is available
INFO: GL_ARB_buffer_storage is available
INFO: GL_ARB_clear_texture is available
INFO: GL_ARB_clip_control is available
INFO: GL_ARB_direct_state_access is available
INFO: GL_ARB_texture_barrier is available08-25-2015, 09:31 AM
Strange, did you update your driver?
08-25-2015, 10:05 AM
Hi! sorry to bother you.
First: thanks fot the new build, i upgraded succesfully and now it boots with gsdx. Unfortunately a new problem came up.
With the previous version i used to enter controller plugin to configure the keyboard or mi ps3 pad (using xboxdrv to let him be seen by the pc as a pad). Now when i click on plugin settings (from config -> controllers (pad) ) nothing opens. I tried running pcsx2 from the terminal and i got this messages at first:
Found input device => bustype:0, vendor:0, product:0, version:0
Name:Xbox Gamepad (userspace driver)
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
New device created. Found axe:8, buttons:11, m_rel:0
Found input device => bustype:0, vendor:0, product:0, version:0
Name:Xbox Gamepad (userspace driver)
FULL Axis info -32768=>32767, current 516, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current -768, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 516, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
New device created. Found axe:8, buttons:11, m_rel:0
and then nothing. Previously when accessing the settings it recognised perfectly the pad.
Any ideas?
First: thanks fot the new build, i upgraded succesfully and now it boots with gsdx. Unfortunately a new problem came up.
With the previous version i used to enter controller plugin to configure the keyboard or mi ps3 pad (using xboxdrv to let him be seen by the pc as a pad). Now when i click on plugin settings (from config -> controllers (pad) ) nothing opens. I tried running pcsx2 from the terminal and i got this messages at first:
Found input device => bustype:0, vendor:0, product:0, version:0
Name:Xbox Gamepad (userspace driver)
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
New device created. Found axe:8, buttons:11, m_rel:0
Found input device => bustype:0, vendor:0, product:0, version:0
Name:Xbox Gamepad (userspace driver)
FULL Axis info -32768=>32767, current 516, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current -768, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 516, flat 0, resolution 0
Scale not supported
FULL Axis info -32768=>32767, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info 0=>255, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
New device created. Found axe:8, buttons:11, m_rel:0
and then nothing. Previously when accessing the settings it recognised perfectly the pad.
Any ideas?
08-25-2015, 11:01 AM
Select onepad plugin. Those messages are from lilypad but port isn't finish yet.
08-25-2015, 11:48 AM
and it works! thanks!