Non-standard parallel port address

Support questions and answer and latest software.
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

I appreciate the help. After restarting I get some errors that go by quickly, I can try to capture them if necessary. I get a red stop sign and it says
"There is a problem with the configuration server. (/usr/lib/libconf2-4/gconf-sanity-check-2 exited with status 256)"

Is it hammer time?
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

Here is the report from the ldd nucore command. That one error is gone.

linux-gate.so.1 => (0x00a40000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0x0059b000)
libz.so.1 => /lib/libz.so.1 (0x00aff000)
libSDL_mixer-1.2.so.0 => /usr/local/lib/libSDL_mixer-1.2.so.0 (0x0011f000)
libSDL_image-1.2.so.0 => /usr/lib/libSDL_image-1.2.so.0 (0x0034d000)
libutil.so.1 => /lib/tls/i686/cmov/libutil.so.1 (0x00c2c000)
libltdl.so.3 => /usr/local/lib/libltdl.so.3 (0x009d5000)
libmpg123.so.0 => /usr/local/lib/libmpg123.so.0 (0x00dee000)
libftd2xx.so.0 => /usr/local/lib/libftd2xx.so.0 (0x00eea000)
libftchipid.so.0 => /usr/local/lib/libftchipid.so.0 (0x00b37000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0x0019a000)
libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x0073d000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0x0085c000)
/lib/ld-linux.so.2 (0x00fac000)
libtiff.so.4 => /usr/lib/libtiff.so.4 (0x0036a000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x002fc000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0x00488000)
libstdc++.so.5 => /usr/local/lib/libstdc++.so.5 (0x00cea000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00cb5000)
libpulse-simple.so.0 => /usr/lib/libpulse-simple.so.0 (0x0066e000)
libpulse.so.0 => /usr/lib/libpulse.so.0 (0x003c6000)
libdirectfb-1.2.so.0 => /usr/lib/libdirectfb-1.2.so.0 (0x00408000)
libfusion-1.2.so.0 => /usr/lib/libfusion-1.2.so.0 (0x009c9000)
libdirect-1.2.so.0 => /usr/lib/libdirect-1.2.so.0 (0x0031d000)
libpulsecommon-0.9.21.so => /usr/lib/libpulsecommon-0.9.21.so (0x0048c000)
librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0x00c49000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00875000)
libICE.so.6 => /usr/lib/libICE.so.6 (0x00beb000)
libSM.so.6 => /usr/lib/libSM.so.6 (0x00b53000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0x00bc6000)
libwrap.so.0 => /lib/libwrap.so.0 (0x00aca000)
libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x004d7000)
libdbus-1.so.3 => /lib/libdbus-1.so.3 (0x0053f000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00333000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00110000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00578000)
libXi.so.6 => /usr/lib/libXi.so.6 (0x00814000)
libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0x0083a000)
libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x005c1000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00fc9000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00620000)
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

error is something along the lines of- open dev/null failed. No such file or directory.
jbrove
member
Posts: 19
Joined: Wed Feb 14, 2018 11:08 pm

Re: Non-standard parallel port address

Post by jbrove »

I guess the X server is angry about something. Doesn't matter as you don't need it for Nucore. I would need a little more of the error output to know exactly whats going on. Pull up a terminal (ctrl+alt+f7 if all else fails) and try to start Nucore manually:

cd /root/nucore/bin
./run nucore

You should be able to see the whole error text from the terminal.

Did you remember to install the roms? There should be "roms" and "nucore" folders under /root/nucore/ if they are installed. I vaguely remember getting an error like that when I forgot to install them.
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

I decided to start from scratch in case i messed with something I shouldn't have. Now when i run ldd nucore I get
libSDL_image-1.2.so.0 => not found
I've tried the apt-get install libsdl-image1.2 command, but I get
eading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libstdc++5: Depends: gcc-3.3-base (>= 1:3.3.6-15ubuntu6) but it is not installable
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
Did I do something in the wrong order?
jbrove
member
Posts: 19
Joined: Wed Feb 14, 2018 11:08 pm

Re: Non-standard parallel port address

Post by jbrove »

Your best bet would be to start from scratch again but use the "bigger hammer" instructions for libstdc++5 (do this last). I think you were about done before you started from scratch and just needed to install the roms.
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

I started from scratch one more time and went through all of the steps. LDD Nucore gives no errors. NuCore install still fails. Running NuCore using terminal gets me to the screen select screen. NuCore does not auto start when the computer turns on. I get an audio error (unable to initialize audio) when the computer is plugged into the game.

To install the roms, I just copied the ROMS folder from a working setup into the directory. Is there more to it than that?
jbrove
member
Posts: 19
Joined: Wed Feb 14, 2018 11:08 pm

Re: Non-standard parallel port address

Post by jbrove »

Getting nucore to start on boot is pretty simple:

You can skip step 1 if the nucore menu can "see" your power driver board without using the "-parallel" commandline option ie. if you can accept or decline the the license agreement with the buttons without the "-parallel" option. Otherwise you'll need to determine your parallel port address.

1. Edit the startup script at /root/nucore/install/start/exec/nucore to include the "-parallel [your parallel port address here]" commandline option.
2. Copy the exec_nucore script to /etc/init.d/
3. update-rc.d -f gdm remove (this will stop gdm from starting on boot)
4. update-rc.d exec_nucore start 99 2 3 4 5 .

Regarding the roms:
The "roms" and "update" folders (including subfolders) should be copied to the /root/nucore/ folder. I think nucore will still boot a game without the "update" folder but you'll be running the lowest version of the game.

The audio issue:
Nucore wont boot a game unless it can "talk" to your sound card. I don't know the specifics of the hardware you are using. You should first check to see that your sound card has been detected. Easiest way to do that is:

aplay -L

you should see a list of sound devices. If you do - try running a speaker test

speaker-test

if you get a bunch of errors then your system probably just has the wrong audio device selected by default. You can go here:

https://linux.die.net/man/1/speaker-test

and look at examples to determine which output you want. Then, you need to set that output as the new default. That step can be a bit tricky but you should be able to find a bunch of tutorials on Google.
Shredso
member
Posts: 36
Joined: Wed May 04, 2011 10:02 pm

Re: Non-standard parallel port address

Post by Shredso »

Thanks. I'll check that out. One (hopefully) last question. I bought a cheap amp for the speakers. I read somewhere the pinout was incorrect in the manual. How should I wire this to a stereo amp? Cabinet speaker will have to go on either L/R. Will this mess with anything?
jbrove
member
Posts: 19
Joined: Wed Feb 14, 2018 11:08 pm

Re: Non-standard parallel port address

Post by jbrove »

I used the original amp in my setup - I just soldered a jumper from the 78L05 on-board regulator output to the #mute line on the prism card connector and soldered an 3.5mm patch cable to the unpopulated RCA jack pads. I saw a post where someone else soldered an RC network between the molex 5V line and the #mute line to accomplish the same thing but the extra cap and resistor aren't needed since R18 and C19 are already there for that purpose (Check the pinball 200 schematic and TDA7375 datasheet Part 5.5 - STANDBY DRIVING) for reference.

If you are using your own amp then I think the configuration you are looking for is called "Bridged Stereo Center". According to the pinball 2000 schematics - the cabinet speaker is just a mono sum of the left and right channels. Careful, I think the stock speakers are 4 Ohm which means in "Bridged Stereo Center" configuration the left and right back-box speakers will need to be connected to the 8 Ohm outputs of the amp. You can find a bunch of wiring diagrams on Google for this type of configuration. Regarding the incorrect pin-out - I'm not sure but I assume you're gonna cut the stock connector off the speaker wiring harness. In that case the pin-outs don't matter as long as you verify the right wires are going to the right places.
Post Reply