Search the Community
Showing results for tags 'service'.
-
This thread aims to document the process of building fujinet-pc in a Linux environment. As usual, there will be many ways of accomplishing this, so comments, questions, and suggestions are welcome. There is an assumption being made that the person seeking to build fujinet-pc is comfortable with working in a Linux shell (commandline) environment. It's not necessary to be the best in the world at it by any means, but being familiar with package management tools, sudo, running shell scripts, etc. is necessary. It's also worth mentioning that the environment I'm primarily building this in is Raspberry Pi OS on a Raspberry Pi 3B. Depending on the architecture and Linux distribution in use, some parts of the process may be different to how it has been detailed below. If you run into any issues, by all means ask for assistance - just make sure to detail the Linux distribution in use, the architecture you're building under (x86, x64, ARM, etc.) and we'll help with figuring it out. MacOS is not covered by these instructions. With that said, open a terminal and start by making sure that three requirements are satisfied first: Python3 Python3 may already be installed on your system. To test if it is, type `python3 --version' at a shell prompt and hit Return. If you see output along the lines of 'Python 3.x.x', you're good to go. If not, check if it's available from your distribution's package manager (which it almost certainly will be). Platformio Unless you're doing python development, chances are that this one isn't installed. Check your package manager to see if it's available; if it is, go ahead and install it. If the package manager doesn't include it, see https://platformio.org/install/cli for information on how to obtain and install it. jinja2 Also not likely to have been installed unless doing Python development. It can be installed using either the system's package manager or pip. See https://pypi.org/project/Jinja2/ for details. git If git isn't installed, the system's package manager will again come to the rescue. For a quick check, type 'git --version' at a shell prompt; if you don't see a line similar to 'git version 2.39.3 (Apple Git-145)', this would be a good time to install it. Build tools such as g++, cmake, libraries, etc. will also need to be present. These are typically installed by default on most distributions, but not always. Pro-tip: missing packages can cause the build process to fail, so if a build error refers to something missing or not found, install the necessary packages (where appropriate) and try again. Having got that out of the way, it's time to set up a directory to build out of. From the terminal, issue the following command: mkdir ~/build && cd ~/build Next, clone the fujinet-firmware git repo and change directory into it: git clone https://github.com/FujiNetWIFI/fujinet-firmware && cd fujinet-firmware Running the 'build.sh' script in that directory will start the build process, but the target 8-bit platform needs to be specified first: For Atari: ./build.sh -p ATARI For Apple: ./build.sh -p APPLE The capital letters are intentional. There are no other target platforms at this time; simply choose the one that sounds more appealing if yours isn't covered. At this point, the build process should have started. Go grab a snack. If any errors occur, copy and paste them into this thread and we'll try to help you figure out what went wrong. Now that the software is built, we can move on to installing, configuring, and running it. There are a few housekeeping tasks that need to take place first. The first step is to create a user and group for fujinet to run as: sudo adduser --system --no-create-home --shell /sbin/nologin --group fujinet Next, the fujinet binary needs to be copied to a suitable location for it to run from. This example uses /usr/local/bin, but anywhere appropriate on your system can be used: sudo mv build/dist/fujinet /usr/local/bin Third, the support files used by the fujinet binary need to be put somewhere convenient. Again, /usr/local/etc is used for this but can be changed to suit: sudo mkdir /usr/local/etc/fujinet-pc && sudo cp -rp build/dist/* /usr/local/etc/fujinet-pc Moving on, ownership of the support file directory needs to be changed: chown -R fujinet: /usr/local/etc/fujinet-pc Edit the fnconfig.ini file to reflect the environment fujinet-pc is being run in: sudo <name of your favourite editor here> /usr/local/etc/fujinet-pc/fnconfig.ini fujinet-pc is now essentially installed and ready to go. To test it, issue the following command, changing pathnames as needed: /usr/local/bin/fujinet -c /usr/local/etc/fujinet-pc/fnconfig.ini -s /usr/local/etc/fujinet-pc/SD A bunch of text should go scrolling up the terminal window, and if you point a browser to http://<your IP address>:8000, you should see the fujinet-pc web interface. To return to the shell prompt, hit CTRL-C. If the test run was successful, congratulations! You now have a working fujinet-pc installation. But what if you want to start and stop it a bit more conveniently in the future? This is where creating a unit file comes in. Without going too far off into the weeds, if your machine uses systemd to control the starting and stopping of services, it uses unit files to manage those processes. There are other ways of doing this, but as most distributions currently use systemd, this is the one that we'll focus on here. The first order of business is to create a unit file. Again, adjust the pathname as needed to reflect your system: sudo touch /lib/systemd/system/fujinet-pc.service Open the file that was just created for editing, and copy and paste the following into it. Be sure to once again change pathnames as necessary before saving the file: [Unit] Description=Start fujinet-pc as a service After=syslog.target network-online.target remote-fs.target [Service] User=fujinet ExecStart=/usr/local/bin/fujinet -c /usr/local/etc/fujinet-pc/fnconfig.ini -s /usr/local/etc/fujinet-pc/SD WorkingDirectory=/usr/local/etc/fujinet-pc ExecReload=/bin/kill -s HUP $MAINPID ExecStop=/bin/kill -s QUIT $MAINPID PrivateTmp=true [Install] WantedBy=multi-user.target systemd needs to be made aware of the new unit file. Issue the following command: sudo systemd daemon-reload Now go ahead and try starting fujinet-pc: sudo systemctl start fujinet-pc If this returns you straight back to a shell prompt, that's expected. Now issue the following: sudo systemctl status fujinet-pc Check the output for a line similar to the following: Active: active (running) since Sat 2024-03-23 11:23:45 CDT; 6h ago That indicates that fujinet-pc is running, and should again be reachable through a browser at http://<your IP address>:8000 . To stop fujinet-pc, issue the following: sudo systemctl stop fujinet-pc If changes are made to fnconfig.ini while fujinet-pc is running, it can be restarted in order to pick up the changes: sudo systemctl restart fujinet-pc Note that the above commands will only allow fujinet-pc to run while you are logged in. To make it start at boot: sudo systemctl enable fujinet-pc And, predictably, if you don't want it to start at boot, the following will take care of that: sudo systemctl disable fujinet-pc Hopefully this has been useful to anyone looking to build fujinet-pc. Again, comments, questions, and suggestions are most welcome.
- 4 replies
-
- 1
-
- fujinet
- fujinet-pc
- (and 4 more)
-
Hello everyone! I recently purchased an XEGS with 4 carts, keyboard, light gun and original PSU, for about US$70 on eBay. Unfortunately, i was DOA (Red Screen of Death), but the seller promptly refunded me and allowed me to keep the item! So, I intend now to try to fix it, being that it is now literally free... By doing some research, I understand that the first suspect for this RSoD is the RAM chip(s). I already ordered a couple of Samsung 64K x 4 RAM chips for a couple of bucks each (same class as the original ones, although I read that the Texas Instruments were more common), but I thought that maybe a field service manual for the XEGS would come very handy on this, and any future, repair. However I've found service manuals for almost any other 8-bit Atari computer but the XE Game System (I found just the owner's manual). So, anyone have a PDF dump of those that could kindly share?
-
I wasn't sure if this would be the right place to post, but I was wondering if there was a way to get in contact with folks that did game repairs. I have quite a few things I want to have fixed, and just don't have the time or resources to do it myself.
-
I need some jobs done with my AGS-101 Game Boy Advance SP: 1. The charging port (The rectangle port next to the link cable port) doesn't charge all the way and it's very finicky. Could be a bad ac adapter, I'll try a new one out maybe. Either case I'd like someone to take a look at the port to make sure it's not damaged. I'll get a new battery too for it. 2. The volume slider is almost unusable. I have tried cleaning the little slot out but it looks like it's going to need a new volume control module or whatever that thing is. 3. A check of the capacitors just to be safe.
-
i'm not sure if this is known even if, i recognized that the site was down until today. but whenever in need for the service manual you can be sure it won't be available online. the online version of the "Intellivision Service Manual (Model 2609)" is located here: http://www.kohtz.com/andrew/intv_sm/index.html the uploader stated that the pictures are from "INTVfunhouse", but i couldn't find them there. however, i downloaded the manual and made a PDF file from it, with the advantage that you can easy read or download it for a offline use: Intellivision Service Manual (Model 2609).pdf since the Schematic Diagram has some additional artefacts from converting/compressing, here the picture which i downloaded:
-
I just found this youtube series of videos and I think they're quite interesting. It's from an old VHS, so the quality isn't very good, and I noticed a couple of inaccuracies about how the 6532 is wired to the joystick ports, but it's still very useful for someone learning how the VCS works and how to fix the most common problems. https://www.youtube.com/watch?v=wc6CYLFjKoo https://www.youtube.com/watch?v=5eGJdNxFuXw https://www.youtube.com/watch?v=0rxuD4mxBZU https://www.youtube.com/watch?v=jb6FZ8rB5gU https://www.youtube.com/watch?v=xBHKWYJAPyQ https://www.youtube.com/watch?v=uBVjD84nwNU https://www.youtube.com/watch?v=zLYGMrUJado https://www.youtube.com/watch?v=OvjdP79m4go https://www.youtube.com/watch?v=XD1Ci9L1AuM https://www.youtube.com/watch?v=tdh4vt8UEtI
-
ElectronicSentimentalities http://electronicsentimentalities.com/InstallationServices.html Spectacular...If I had to choose one word to describe both my dealings with and the end results of the service that ElectronicSentimentalities offers, spectacular would be that word. I have had the pleasure of purchasing and currently own the Best 7800 Composite mod system, a 7800 system mod from Yurkie, and now one from ElectronicSentimetalities. Yurkie was dead on the money recommending their service after discontinuing the one he provided. The recommendation meant a lot to me, knowing how satisfied I was and how awesome Yurkie's work was on the 7800, for him to recommend another - I knew it had to be good. I was wrong. It is not good, but excellent. Joe was friendly, fast, and a pleasure to deal with; including shipping my console back way before the expected return date. Further, the price is extremely reasonable. You get S-Video, Composite, and audio out jacks. The composite picture is the clearest I have seen and the S-Video is even more stunning. Being that I own a "CPS 7800 Diagnostic Test Cartridge'', the console was tested, and the color calibration was shown to have been performed perfectly as well. The console was packaged very carefully when sent back including a second box with padding/insulation in addition to the one I utilized sending my system out. Externally, you could not tell (Outside of the new connectors) the system was even touched. In fact, it was wrapped nearly exact the way I shipped it. You're not a DIY console mod person or not very good at it; or just want the ease and convenience of having your 7800 system mod done beautifully and professionally with spectacular results, this would be the place your console needs to go. Highly recommended and highly impressed - Bravo, Joe/ElectronicSentimentalities.
-
A quick search didn't turn this up in the forums so thought I would post it here. Apologies if I missed it. http://www.atariguide.com/pdfs/Atari_2600_VCS_Domestic_Field_Service_Manual.pdf I've also attached a PDF copy. Wish I had the diagnostic cart to go with it but there is still a lot of useful information. Atari_2600_VCS_Domestic_Field_Service_Manual.pdf