New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
absence of ../hash/mameROMs.xml.gz causing NPEs (I think). #3
Comments
happens with both openjdk-7-jre and sun-java6-jre |
Same issue for me on Raspberry Pi. Clean install. wheezy-armel But mostly posting this just to say I'm on a Raspberry Pi. ... No.. I'm ona boaaaaat. (load average: 2.49, 3.94, 3.64) |
Thanks for finding this out. If you git pull and then go to the Client directory and run mvn package and then java -jar target/MAMEHubClient-0.0.1-SNAPSHOT.jar it should be able to read the hashes in the hash directory. |
Found the hash dir and missing mameROMs.xml.gz in the http://10ghost.net/MAMEHubDownloads/MAMEHub2_Linux32_0.6.zip package, which I imagine is a stable release. Is what is here on github a fork, current dev version, or other? |
Its a copy :-D
|
Heya MisterTea... Just wanted to report (in this dead and closed issue) that your commit resolved that issue. And, also, the lobby finally loaded on my Raspberry Pi.... but took 2 days for the Audit to complete! haha. :-) I moved over to the Sun JDK 8 prerelease for arm/hardfloat. Much faster than OpenJDK on the rPi on the heavy tasks (maybe 5x to 10x speedup). Anyway, thought you'd get a kick outa the info. JB |
Awesome!! Does MAME work on the raspberry pi? I'm going to open source the MAME changes pretty soon. On Sun, May 12, 2013 at 12:56 PM, Jeremy Blow notifications@github.comwrote:
|
So far, I've only worked on mamehub. I'm going to give csmame/mame a go later this evening. I'll let you know how it goes. Cool, looking forward it! JB |
If you could share a pic of your pi running mamehub, that would be awesome! |
Shirley.. CPU eventually settles down. Player state changes peg it for about 15-30 seconds. |
Hey, Now that the emulator is open sourced, would it be possible to get the entire thing working on a pi? |
Totally. Our rag-tag fugitive team is hacking on it. CSMame first. Mamehub is a bear on rPi... we'll need to dig in to the internals to see where the bottlenecks are (Java vs. mamehub processes). |
Here's what we are facing. At the versions of MAME that CSMame is using, ARM support is non-trivial. The forks, advanceMAME and MAME4ALL seem to have moved forward and will build on ARM, but are such a step backwards as far as the emulator version, and offer no hope of compatibility with CSMame. Could we plow through and get it to work, probably, but it'd end up being yet another port of MAME, and, I'm guessing it would take a MAME dev 1/100th the time to fix the problems. There was one guy who seems to have gotten MAME to build on a cubox. His patch to MAME was pretty large. But, cubox is ARMv7 and the rPi is ARMv6, which is also a non-trivial issue. There is much speculation out there stating that it's a lost cause anyway because the rPi is under-powered for modern MAME. Somewhat annoying because it's all speculation, I'm pretty certain nobody has been able to even try it. Certainly they are not considering the perf improvements MAME has encountered as a result of its c++ overhaul. Will it still be underpowered, I don't know, I believe it's an open question. |
Hey Jeremy, Are you sure about ARM support in current versions? I compiled the latest IIRC, I had to change all of the dynamic_cast<..> functions to use C++ On Tue, Jun 11, 2013 at 5:31 PM, Jeremy Blow notifications@github.comwrote:
|
Hey, that's encouraging. Can't imagine much has changed since .146. Surprised haven't found anyone doing it yet. Do you happen remember your build environment? I may be missing something basic. I've been building either via qemu'd raspbian, chrooted cross compiling on deb 7 64 as armv6 (gcc version 4.6.3 (Debian 4.6.3-14+rpi1)), or straight cross via gcc linaro-4.7.-2013.01 / crosstool-ng w/ arm-unknown-linux-gnueabi. |
I don't remember the build environment, but if you give me instructions on
|
That'd be excellent. My MAME exposure is just about one month. :-) Plus I only dig into C++ when troubleshooting stuff. Chrooted is probably the quickest path, here are my build steps. Note this also includes using directfb / cubox patch at the bottom, which is optional but moved me further along. Grab Raspbian
Grab qemu
The raspbian image is a little too cozy, only couple hundred MB free. Expand it to 4GB.
Raspbian will have boot problems via qemu unless we prevent preloading some libraries.
We need to make a another change to udev so we can expand the partition via raspi-config.
Great. Go ahead and umount the img.
Next, we'll boot up the image, run a quick fsck, reboot, and expand the second partition.
On the launched vm, you'll see some file system errors, when you get to the shell you can fix
You should be exited out of qemu, relaunch the vm again:
When you get to the shell, login (username pi, password raspberry). Launch raspi-config using From here, we're ready to chroot the img. First mount it back up:
Next, chroot the mount.
From here, most things will work. You won't have /proc, /sys or /dev, but for building this seems On to MAME. Some deps, some may not be needed, but were added while troubleshooting.
Get MAME
From here, you can I've been looking at this guy's patch
That's it so far. A few of us who are interested this generally hang out in IRC. E-mail me if you want the server/channel info. Kewl. Looking forward. |
oh hey now. Just saw Dave Spencer post on your g+. Do you work with him? I worked with him at his start-up a long long time ago in a land far far away called Santa Monica. If u see him tell him I say hello! :-) |
I used to work with him, but I still see him from time to time. I'll let On Wed, Jun 12, 2013 at 12:36 AM, Jeremy Blow notifications@github.comwrote:
|
That's really cool. I learned a LOT from Dave. Thx! |
Hey Jeremy: The MAMEHub GUI is MUCH faster now, I bet it will run pretty smoothly on a raspberry pi. |
hi,
having this problem on both Raspbian (ARM6) and Debian (x86_64).
after submitting MAMEhub creds at login screen, getting an error dialog reading:
in ErrorLog.txt is the message:
And, the exception as seen from the terminal (on Debian/x86_64):
The text was updated successfully, but these errors were encountered: