..:: PCSX2 Forums ::..

Full Version: For everyone with issues starting PCSX2 Mac
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
(12-05-2013, 09:46 PM)thestiffler3 Wrote: [ -> ]
Code:
F1 - save state
(Shift +) F2 - cycle states
F3 - load state
PCSX2 beta (r2620254) - compiled on Jan 27 2011
Savestate version: 8b410001
EE pc offset: 0x2a8, IOP pc offset: 0x208
x86Init:
Features:
Loading plugins...
Loading GS...
Loading PAD1...
Loading PAD2...
Loading SPU2...
Loading CDVD...
Loading DEV9...
Loading USB...
Loading FW...
Plugins loaded successfully.
Offset 0xf75da000 invalid. Legit SIGSEGV. Aborting.
hellpssssss

As I said, please try to redownload and reinstall everything related to pcsx2...
I've looked through everything. The "segmentation fault" comes up in conversation many times and it doesn't seem to be directly addressed. Has ANYONE actually gotten 9.7 Alpha working with Mountain Lion?? Anyone at all?
I'm just getting that segmentation fault 11 message.

Please. For the love of god. Halp.

[attachment=47551]
(12-28-2013, 01:37 AM)tychmc Wrote: [ -> ]I've looked through everything. The "segmentation fault" comes up in conversation many times and it doesn't seem to be directly addressed. Has ANYONE actually gotten 9.7 Alpha working with Mountain Lion?? Anyone at all?
I'm just getting that segmentation fault 11 message.

Please. For the love of god. Halp.
(12-28-2013, 01:37 AM)tychmc Wrote: [ -> ]I've looked through everything. The "segmentation fault" comes up in conversation many times and it doesn't seem to be directly addressed. Has ANYONE actually gotten 9.7 Alpha working with Mountain Lion?? Anyone at all?
I'm just getting that segmentation fault 11 message.

Please. For the love of god. Halp.


I am pretty sure that I have mentioned the segmentation fault several times in this thread already, but yeah, I should probably add it to the FAQ section.

The segmentation fault is caused by bad rips. Meaning that you will have to re rip your ISO.
Offset 0xea0004d0 invalid. Legit SIGSEGV. Aborting.
Bus error: 10
logout

[Process completed]



I get this when trying to run an iso. Any help?
Did you rip your disc like this:
onetwo Wrote:1.
Insert the DVD, and in the terminal do:
2.
Code:
diskutil unmountDisk disk1
3.
Code:
dd if=/dev/disk1 of=/Users/your-username/Desktop/Game_name_here.iso
?
(12-29-2013, 02:27 AM)Blyss Sarania Wrote: [ -> ]Did you rip your disc like this:
?


Nah, I used Disk Utility to create a .cdr image, then used Terminal to convert it to .iso. I will try your method though, see if that fixes my problem.
(12-29-2013, 02:31 AM)spazmos Wrote: [ -> ]Nah, I used Disk Utility to create a .cdr image, then used Terminal to convert it to .iso. I will try your method though, see if that fixes my problem.

It's not my method, but it's the method the guy recommends in the OP.
(12-28-2013, 05:24 AM)Kaze Wrote: [ -> ]I am pretty sure that I have mentioned the segmentation fault several times in this thread already, but yeah, I should probably add it to the FAQ section.

The segmentation fault is caused by bad rips. Meaning that you will have to re rip your ISO.

Thanks Kaze! I did see it mentioned but I must have missed the explanation. I just noticed a few times it was mentioned and determined to be an unsolved mystery. You're awesome.
(12-29-2013, 02:33 AM)Blyss Sarania Wrote: [ -> ]It's not my method, but it's the method the guy recommends in the OP.

I tried making an iso using this method, but I'm still getting bus error: 10. Any help? Sad
(12-29-2013, 03:10 AM)spazmos Wrote: [ -> ]I tried making an iso using this method, but I'm still getting bus error: 10. Any help? Sad

Unfortunately, that's really all I know to suggest. I don't have a mac and don't know much about mac. All I know is what I read in the OP, and if that doesn't work, I'm pretty clueless lol.

I did just look up the error itself, and I found this info:

Quote:Bus errors are rare nowadays on x86 and occur when your processor cannot even attempt the memory access requested, typically:

using a processor instruction with an address that does not satisfy its alignment requirements.

So it appears that something in the code is behaving in a strange way. Well, PCSX2 mac is super alpha quality, so maybe that is to be expected.

Sorry that I couldn't be more useful.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31