|
Post by pla7er on Feb 24, 2007 15:30:47 GMT -5
Hi, First of all, kudos to the author of the emulator! IMO, none of the other PSX emulators currently compare with the ease of use and quality of pSX! Great job, really! Now, back to the issues. I used v1.11 for Linux release. I'm running Suse 10.2, and when I run the pSX from console, the following happens: #1: Every time I run the pSX, it prompts to look for the BIOS file, even though the BIOS file is under the bios folder. When I find and select the SCPH1001.bin file, it leads to the issue #2 (below). #2: After the bios file has been selected, the app prompts to select a language - I choose English (btw, this happens every time also and I though it should ask for it once and then write it to ini file) and the app crashes with the following messages: (pSX:6048): GtkGLExt-CRITICAL **: gtk_widget_get_gl_context: assertion `GTK_IS_WIDGET (widget)' failed (pSX:6048): GtkGLExt-CRITICAL **: gtk_widget_get_gl_window: assertion `GTK_IS_WIDGET (widget)' failed
|
|
|
Post by pSX Author on Feb 24, 2007 15:36:49 GMT -5
Can you download and try the last WIP version: psxemulator.gazaxian.com/pSX_wip.tar.bz2and see if that also crashes in the same way. If it does please run it under gdb: gdb ./pSX run then after it crashes type: bt and paste the results here.
|
|
TryA
New Member
Posts: 2
|
Post by TryA on Feb 24, 2007 19:40:48 GMT -5
I tested the emulator on Debian Sid and it crashed with the same message as pla7er.
Here are the results from GDB:
~/pSX_wip$ gdb ./pSX GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"... Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /home/mika/Desktop/pSX_wip/pSX Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1231320832 (LWP 17764)]
(pSX:17764): GtkGLExt-CRITICAL **: gtk_widget_get_gl_context: assertion `GTK_IS_WIDGET (widget)' failed
(pSX:17764): GtkGLExt-CRITICAL **: gtk_widget_get_gl_window: assertion `GTK_IS_WIDGET (widget)' failed buffer_time=341315us buffer_size=15052 offset=882 period=21333us period_size=940 (dir=1) pad=0
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1231320832 (LWP 17764)] 0xb489ba50 in ?? () (gdb) bt #0 0xb489ba50 in ?? () #1 0xb7da5373 in gdk_gl_get_proc_address () from /usr/lib/libgdkglext-x11-1.0.so.0 #2 0xb7da8bcf in gdk_gl_get_glXSwapIntervalSGI () from /usr/lib/libgdkglext-x11-1.0.so.0 #3 0x0810c285 in video::init () #4 0x080c3877 in psx_gpu_software::show_frame () #5 0x080d5959 in idle_callback () #6 0xb7637da1 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0x00000000 in ?? () (gdb) quit
Otherwise, keep up the good work!
|
|
|
Post by pSX Author on Feb 24, 2007 19:43:08 GMT -5
Okay, this appears to be a video driver issue.
Try upgrading your nvidia or ati glx driver. Someone else had this issue with the WIP and it was fixed by upgrading to the latest nvidia driver.
|
|
TryA
New Member
Posts: 2
|
Post by TryA on Feb 24, 2007 21:29:47 GMT -5
Yes, you were right: i've updated my nvidia driver (I have a GeForce MX 4000) and it works smoothly now! Thanks a lot!
|
|
|
Post by patrickp on Feb 24, 2007 21:35:01 GMT -5
I'm still getting the GtkGLExt-CRITICAL message, but now not until I close the emulator - and I'm not getting any crashes. In the last WIP, I got the message on starting the emulator - but again no crashes.
I'm using the ATI 6.33.6 driver in Ubuntu 6.10; since I installed it, the emulator has been running beautifully, although not as fast as in Windows yet...
|
|
|
Post by pSX Author on Feb 24, 2007 21:55:27 GMT -5
Yeah - I noticed that warning on my system too - its not a serious problem though - you can ignore it.
|
|
|
Post by pla7er on Feb 25, 2007 16:29:30 GMT -5
Can you download and try the last WIP version: psxemulator.gazaxian.com/pSX_wip.tar.bz2and see if that also crashes in the same way. If it does please run it under gdb: gdb ./pSX run then after it crashes type: bt and paste the results here. I already have the latest Nvidia driver for my video card, so I assume the driver version should not be a problem. I've got Geforce FX 5900XT. Ran the psxemulator.gazaxian.com/pSX_wip.tar.bz2 with gdb: the app launched, selected English, asked to locate the bios file - located it, then the pSX window froze with the following message in the console: Failed to read a valid object file image from memory. [Thread debugging using libthread_db enabled] [New Thread -1232656656 (LWP 14253)]
(pSX:14253): GtkGLExt-CRITICAL **: gtk_widget_get_gl_context: assertion `GTK_IS_WIDGET (widget)' failed
(pSX:14253): GtkGLExt-CRITICAL **: gtk_widget_get_gl_window: assertion `GTK_IS_WIDGET (widget)' failed buffer_time=371519us buffer_size=16384 offset=882 period=725us period_size=32 (dir=0) pad=0
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1232656656 (LWP 14253)] 0xb50d1ef0 in ?? () bt gave this: (gdb) bt #0 0xb50d1ef0 in ?? () #1 0xb7e13d17 in gdk_gl_get_proc_address (proc_name=0xb7e21eaa "glXSwapIntervalSGI") at gdkglquery-x11.c:408 #2 0xb7e18585 in gdk_gl_get_glXSwapIntervalSGI () at gdkglglxext.c:466 #3 0x0810c285 in video::init () #4 0x080c3877 in psx_gpu_software::show_frame () #5 0x080d5959 in idle_callback () #6 0xb7623061 in g_source_is_destroyed () from /opt/gnome/lib/libglib-2.0.so.0 #7 0xb7624de2 in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0 #8 0xb7627e1f in g_main_context_prepare () from /opt/gnome/lib/libglib-2.0.so.0 #9 0xb76281c9 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0 #10 0xb7a92cd4 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0 #11 0x080d7572 in do_main () #12 0x080d7c59 in main ()
|
|
|
Post by pSX Author on Feb 25, 2007 16:40:23 GMT -5
Well, this is the same problem - other people have fixed it by upgrading their driver (see above).
Which version of the driver are you using?
|
|
|
Post by pla7er on Feb 25, 2007 17:55:59 GMT -5
Well, this is the same problem - other people have fixed it by upgrading their driver (see above). Which version of the driver are you using? Yes, I saw that. The driver I'm using: Linux Display Driver - x86 Version: 1.0-9746 Operating System: Linux x86 Release Date: December 21, 2006 www.nvidia.com/object/linux_display_ia32_1.0-9746.html
|
|
|
Post by Ultima on Feb 25, 2007 18:12:23 GMT -5
Maybe you can try downgrading? I'm using 1.0-8776, and don't experience this.
|
|
|
Post by pla7er on Feb 28, 2007 21:21:37 GMT -5
Maybe you can try downgrading? I'm using 1.0-8776, and don't experience this. I need the latest driver for other things. Anyway, no a problem, as the Win build seems to have run under Wine pretty decent...
|
|