Advance MAME (Findings so far)

That's very helpful. I think for certain distros that should be the default though - this being one of them. A LOT of windows only guys will be coming to the RPi and that's the kind of elemental step that people who work with linux take for granted, so never explain and becomes stumbling blocks for the new people.

Is there an example of a line of code a standard user would type where ./[command] would work out fine, but an accidental [command] would royally mess things up?

[jamesh]

Probably lots, but I'm no Linux expert.

Now then, do I have to do the sound deopmod thing on every reboot? Is there a way around that?

I'll test out Defender for you tomorrow I have a feeling it'll work fine

Thanks SSilver2k2. Now if I can only get my hands on a Raspberry Pi, then I'll be asking how to configure it

Defender works fine (just a little awkward because of the control scheme it uses). No slowdown at all.

Thanks for the info. I'm just waiting to get my hands on a Raspberry Pi.

[dom]

Now then, do I have to do the sound deopmod thing on every reboot? Is there a way around that?

Use the Wheezy image is one solution.

Just when I had this squeeze thing purring away too. Ahh well, time for a re-imaging I guess to keep current.

[texy]

Can't get advmame to run any roms because it fails with no monitor clocks error.
Also the command to run without X in the first post doesn't appear to work as it just returns a list of options as if its not valid.
Thas is using the advmame download from this page :
http://blog.sheasilverman.com/?p=44

There also seems to be contradiction as to where the roms actually go - the above link says "mame/share/roms/", but it stated missing files from the
zip, so above it says " MAME Folder/share/advance/rom/", which I think is correct. However I now get the monitor clock error.

T.

Can't get advmame to run any roms because it fails with no monitor clocks error.
Also the command to run without X in the first post doesn't appear to work as it just returns a list of options as if its not valid.
Thas is using the advmame download from this page :
http://blog.sheasilverman.com/?p=44

There also seems to be contradiction as to where the roms actually go - the above link says "mame/share/roms/", but it stated missing files from the
zip, so above it says " MAME Folder/share/advance/rom/", which I think is correct. However I now get the monitor clock error.

T.

I updated the path on my tutorial. Thanks for the catch

I don't know about the monitor clock error. Can you post the actual error message?

[texy]

Hi,
the message is

Code: Select all

No monitor clocks specification 'device_video_p/h/vclock'
Video init failed

Note that if I run up X, I do not get the message, and some of my roms do run. No sound however. This is with debian wheezy.

Thanks,
Texy

Hi,
the message is

Code: Select all

No monitor clocks specification 'device_video_p/h/vclock'
Video init failed

Note that if I run up X, I do not get the message, and some of my roms do run. No sound however. This is with debian wheezy.

Thanks,
Texy

You need to edit your ~/.advance/advmame.rc to include the proper display configuration
For HDMI try:
device_video_clock 5 - 50 / 15.62 / 50 ; 5 - 50 / 15.73 / 60
For NTSC TVs try:
device_video_clock 5 - 50 / 15.73 / 60

[texy]

I did that already. However I entered it by hand copied from my laptop screen.
Perhaps I made an error

Texy

anyone got the sound on HDMI working?

I tried the sudo modprobe snd-bcm2835 command but no luck.
tried it on both squeeze and wheezy. (wheezy doesn't find the asla-util package)

I plugged in some headphones to see if output goes to analogue jack but nothing there either.

help?

The audio on my RPI is working fine, but for some reason I dont have any audio with advancemame. Does anyone know why this might be happening?

I am on wheezy (not the 2012-07-15 release)

Brilliant team work lads!!!

I seem to have got this loaded OK on my Pi, after following the blog instructions, but it's a no-go with any of my old roms. They were from a 2008/2009 Mame32 version on Wintel from what I remember.

Not asking for d/l links or anything - just to know if certain romsets only are OK for this Linux version, or if there are any conversion/update processes for roms.

Thanks in advance.

Further to this, I have the error details as they appear on the Pi screen whenever I try to run any of my roms (just after two copyright output lines):

Signal SIGSEGV[MAPERR], fault at 05x54442d18, from code at (nil)
Compiled Jun 11 2012, 17:28:43
No stack backtrace: compile without CFLAGS=-fomit-frame-pointer and with LFLAGS=-rdynamic

Can anyone give me some clues?

I'm having the same error:

Code: Select all

Signal SIGSEGV[MAPERR], fault at 05x54442d18, from code at (nil)
Compiled Jun 11 2012, 17:28:43
No stack backtrace: compile without CFLAGS=-fomit-frame-pointer and with LFLAGS=-rdynamic

On the bublbobl ROM I get this one too:

Code: Select all

68701.bin NOT FOUND (NO GOOD DUMP KNOWN)

Not entirely sure where to go from here.

@lukeren - Not just me then. I'm on the latest Raspbian, all updated but no additional out-of-distro patches. You?

@lukeren - Not just me then. I'm on the latest Raspbian, all updated but no additional out-of-distro patches. You?

Same here.
I'm compiling from source now to see if that'll help, but I'm not holding my breath.
I've changed to gcc 4.7, as I saw that suggested elsewhere to help get the thing to actually compile.

Compile from source worked!

Before running configure, I changed to gcc 4.7 by doing this:

Code: Select all

apt-get install gcc-4.7
export CC=gcc-4.7
export GCC=g++-4.7


Then:

Code: Select all

./configure
make
make install


It takes a good while to compile, I just left it during the night.
I've still got problems running some roms, I just get a blank/black screen and nothing happens.

OK - I'm going to try the GCC update and I'll compile from source. Sounds like you've sorted the main problem we both saw. Nice one!

This does work. I've recompiled the source and had to update to gcc 4.7. I've also recompiled AdvanceMESS. I haven't seen any speed improvements sadly I'll be posting the binaries to my site this weekend.

Compile from source worked!

Before running configure, I changed to gcc 4.7 by doing this:

Code: Select all

apt-get install gcc-4.7
export CC=gcc-4.7
export GCC=g++-4.7


Then:

Code: Select all

./configure
make
make install


It takes a good while to compile, I just left it during the night.
I've still got problems running some roms, I just get a blank/black screen and nothing happens.

For the people who've been compiling AdvanceMAME on the new Raspbian - which version of AdvanceMAME are you using?

I compiled v0.106.1 (after changing to gcc 4.7) and it compiled fine, but I couldn't run it without starting x, and then it was incredibly slow, even on older ROMs like Space Invaders.

I know there's been talk of using v0.106.0 - have you got this to work from the command line in Rasbian? If so, I'll recompile.

I tried with 0.160.0, but some things weren't working, I switched to 0.106.1, and I haven't had any issues. Both were compiled with gcc-4.7 and doesn't require X.

I'm running 106.1 . If you are getting an error on the command line but it works in X, it's probably because you havent set your display clock in the advmame.rc file.

edit your ~/.advance/advmame.rc to include the proper display configuration
For HDMI try:
device_video_clock 5 - 50 / 15.62 / 50 ; 5 - 50 / 15.73 / 60
For NTSC TVs try:
device_video_clock 5 - 50 / 15.73 / 60

For the people who've been compiling AdvanceMAME on the new Raspbian - which version of AdvanceMAME are you using?

I compiled v0.106.1 (after changing to gcc 4.7) and it compiled fine, but I couldn't run it without starting x, and then it was incredibly slow, even on older ROMs like Space Invaders.

I know there's been talk of using v0.106.0 - have you got this to work from the command line in Rasbian? If so, I'll recompile.

I'm running 106.1 . If you are getting an error on the command line but it works in X, it's probably because you havent set your display clock in the advmame.rc file.

I did set those values, and I've tried it on a few different monitors and a tv. I get a brief flash of oversized text then a blank screen rather than any kinds of errors. The system is responding - I can quit out of it by pressing esc, so it's obviously working to some degree, just not giving me the pretty pictures.

At least I now know I can stick with the latest version - thanks.