|
Post by pSX Author on Feb 13, 2007 17:08:34 GMT -5
You can ignore those GtkGlExt warnings - they are harmless - I'll fix them soon.
I'm not sure why Ubuntu is crashing.. can you still switch to a text mode console? (ie. is it just the X server that has crashed?)
If so can you try looking in /var/log/messages (and other log files) to see if there are any errors.
|
|
|
Post by patrickp on Feb 13, 2007 17:26:44 GMT -5
Trouble is, it just seems to kill everything dead - as I said, no mouse input, no keyboard input. I'll have a look round to see if I can find any logs etc. Are there any logs that would show the cause of a crash previous to a total reboot?
|
|
|
Post by pSX Author on Feb 13, 2007 17:44:09 GMT -5
/var/log/messages is usually saved from previous boots, but that is up to the init scripts...
I can't remember what [K]Ubuntu does (don't have it booted atm to check).
|
|
|
Post by markos on Feb 13, 2007 18:51:41 GMT -5
Im still having some trouble with the latest WIP build, I am pretty sure my athlon has MMX on it...
markos@maria-desktop:~/pSX$ gdb pSX GNU gdb 6.4-debian Copyright 2005 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/markos/pSX/pSX [Thread debugging using libthread_db enabled] [New Thread -1229862656 (LWP 23014)]
Program received signal SIGILL, Illegal instruction. [Switching to Thread -1229862656 (LWP 23014)] 0x080ef5b0 in __static_initialization_and_destruction_0 () (gdb)
|
|
hanman
Full Member
Irvine "Super-Pimp" Kinneas
Posts: 142
|
Post by hanman on Feb 13, 2007 22:08:32 GMT -5
well, everything seems to work great! the only thing i've noticed, is in the controller configuration dialog, the keys don't progress down the first column, and then the second; they go left to right, and then down. this wouldn't be that bad, except that when you get to the axises, it goes to the reverse checkbox and you have to click on the next button. also, now it segfaults when i tried to load a save state from the windows version. but, these are minor annoyances. the only other thing i can request is the ability to set the window size to maintain aspect ratio, and i think this is already lined up for the 1.11 final release.
|
|
|
Post by Ultima on Feb 13, 2007 22:34:18 GMT -5
Hm...? That's odd... pSX Author already fixed the button configuration problem in the SSE2 build, and it's still configuring properly for me right now with the MMX build
|
|
|
Post by patrickp on Feb 14, 2007 0:14:16 GMT -5
Well, I tried the Controller configuration in the MMX build, and it behaves exactly as hanman describes.
@psx Author: I deliberately caused the booting twice crash, then had a quick trawl through the files in /var/log. There was very little that might relate to it; mostly it just seems to be normal processes, suddenly followed by a reboot.
However, I got these lines in kern.log and syslog (the same in each):
Feb 14 04:42:05 altpat1 kernel: [17180740.952000] hdd: write_intr: wrong transfer direction! Feb 14 04:42:05 altpat1 kernel: [17180740.960000] hdc: write_intr: wrong transfer direction!
Don't know if that might have anything to do with it?
|
|
|
Post by anders190 on Feb 14, 2007 5:06:33 GMT -5
well, everything seems to work great! the only thing i've noticed, is in the controller configuration dialog, the keys don't progress down the first column, and then the second; they go left to right, and then down. this wouldn't be that bad, except that when you get to the axises, it goes to the reverse checkbox and you have to click on the next button. also, now it segfaults when i tried to load a save state from the windows version. but, these are minor annoyances. the only other thing i can request is the ability to set the window size to maintain aspect ratio, and i think this is already lined up for the 1.11 final release. You could always save normaly in the Windows version, then load your memcard in linux pSX and than use savestates from there. A little more work but it's a solution for your problem.
|
|
hanman
Full Member
Irvine "Super-Pimp" Kinneas
Posts: 142
|
Post by hanman on Feb 14, 2007 15:18:13 GMT -5
You could always save normaly in the Windows version, then load your memcard in linux pSX and than use savestates from there. A little more work but it's a solution for your problem. yeah, luckily, i had the foresight not to completely trust savestates, so i have current memcard saves for everything. i wouldn't be able to do what you suggest anyway because i don't have windows on my machine at all, and pSX won't run in vmware, or any such emulator, due to lack of 3D support. lol, thats kinda perverse; running an emulator in an emulator. ;D
|
|
|
Post by patrickp on Feb 14, 2007 17:05:19 GMT -5
BTW, pSX Author, Would I be right in guessing that the list of switches I just got from pSX: are ones you left in from Windows and won't work in Linux? I notice one there, for instance, for IOControl, which wouldn't have much relevance for Linux, and I just tried writing a command to start a game in fullscreen, with memory cards selected, and of course, it didn't work... ;(
Edit: no, some of them do work. The -f switch doesn't, which is what messed things up, but the pad type and memory card selection switches work. I think the image selection switch may work as well - it doesn't ATM, but that may be because of spaces in the path...
|
|
|
Post by pSX Author on Feb 14, 2007 17:44:37 GMT -5
Yes, the usage text will need fixing before release. All of the options that make sense should work...
|
|
|
Post by patrickp on Feb 14, 2007 18:13:02 GMT -5
BTW Image selection _does_ work, but you don't seem to be able to have spaces in the path.
|
|
hanman
Full Member
Irvine "Super-Pimp" Kinneas
Posts: 142
|
Post by hanman on Feb 14, 2007 23:16:32 GMT -5
you can have spaces in the path, but in linux, you have to use a backslash before spaces and brackets (possibly other special characters) like "/media/hde/ISOs/PSX\ ISOs/Final\ Fantasy\ IX\ \[Disc1of4\]\ \[U\]\ \[SLUS-01251\].cdz"
lol, that really looks ridiculous, but, just remember, the TAB key is your friend!
EDIT: this may be easier to read:
notroot@bahamut:~/pSX$ ./pSX /media/hde/ISOs/PSX\ ISOs/Final\ Fantasy\ IX\ \[Disc1of4\]\ \[U\]\ \[SLUS-01251\].cdz
|
|
|
Post by patrickp on Feb 15, 2007 8:16:51 GMT -5
I get it; thanks, hanman! I changed all my path references anyway, though (annoying because my images are actually on an NTFS volume, so I had to keep switching OSs to change things and then try them ).
|
|
|
Post by anders190 on Feb 15, 2007 14:27:04 GMT -5
yeah, luckily, i had the foresight not to completely trust savestates, so i have current memcard saves for everything. i wouldn't be able to do what you suggest anyway because i don't have windows on my machine at all, and pSX won't run in vmware, or any such emulator, due to lack of 3D support. lol, thats kinda perverse; running an emulator in an emulator. ;D Actually, vmware nowadays have some experimental directx acceleration. Last I checked I had to manually edit one of the vm's config files to enable it. It was mentioned in the documentation. I think I used version 5.5.3 or something. But well, it sure is a hell-of-a-lot of work but it would propably solve it. =)
|
|