What's new
1669000043151.png


I don't understand why the SSID and credentials for the WiFi hotspot that is set up by default is listed under WiFi settings. I want to change this "hotspot mode" to "wifi direct" i believe.

When I try to enter my SSID and WIFI PW on the WiPi netbooter.local it changes these settings to my home wifi ones. But my home wifi is not a hotspot it is a router.

And after I change the WiPi's static IP i can no longer login thru putty. even after rebooting the pi. but it does change successfully and i can add a netdimm successfully.

Also should the country be set to US if im in the US? Does that matter?
 
My network SSID is NETGEAR82 and NETGEAR82-5G. However, when it lists it in the drop down it just shows NETGEAR82 twice.

I’ve tried both the NETGEAR82’s listed which have the same pw and no dice.

Maybe I can change the SSIDs to something without a hyphen
 
OK, here is my breakdown of your current situation:

WiPi uses 2 network configurations, wired for the Naomi side and wireless for connections to the website running on the Pi. By default the ranges are:

Wired: 10.0.0.1
Wireless: 192.168.42.1

This is how it is configured out of the box and will work if you are just using the WiPi-Netbooter wireless SSID. The issue has come when you've added the Pi to your home wifi network which clashes with the wired IP range on the Pi. Most people use a 192.168.0.0/24 or similar IP range for their home network, using a class A 10.x.x.x range is unusual but it can be worked around.

Firstly I would reset your wifi configuration by creating a file called reset.txt in the boot partition then starting up the Pi. Look at the activity lights, it will restart twice and you should then be able to see the WiPi-Netbooter SSID again.

Connect to WiPi-Netbooter and open up the WiPi interface in a browser, go to Setup and Network Configuration. Go to the Wired setup and you'll see it is set to 10.0.0.1, in the form on the page change it to a new static address: 192.168.0.1, subnet mask 255.255.255.0. Apply and the Pi will reboot with the new address.

Reconnect back to WiPi-Netbooter SSID and go back into Setup and Network Configuration to check that the wired interface now has the 192.168.0.1 address. If that has worked you can now join your home wifi network from the wireless configuration screen. Choose the SSID from the drop down and enter your password and apply, the Pi will reboot twice, watch the activity lights and when the Pi is back online you should be able to access it on your home network.

Depending on your router setup you may or may not be able to reach http://netbooter.local - if you can't you can scan your home network for the Pi, I use a mobile app called Fing. If the Pi appears on the list you can connect the IP address rather than the name, in the format http://<ipaddress>.

You have the option to set a static IP address on your Pi for the wireless network so it is easier to find, you need to know what DHCP addresses are given out by your router for this and choose an address that sits outside of that range.

You can now plug your Pi into the Naomi and set up an IP address in the service menu on the Naomi itself, use 192.168.0.2 with subnet mask 255.255.255.0 and restart. Then go into the Netdimm Config menu and create a new Sega Naomi netdimm with the matching IP address 192.168.0.2. The entry should turn green if everything is OK and then you start sending games.
 
I want to thank Nam 9 and everyone who dealt with my bs and tried to help me.

I unplugged my extender and renamed my NETGEAR-5G to NETGEAR5G.

Finally connected to the router.

Gonna keep testing but page is now accessible.
OK, here is my breakdown of your current situation:

WiPi uses 2 network configurations, wired for the Naomi side and wireless for connections to the website running on the Pi. By default the ranges are:

Wired: 10.0.0.1
Wireless: 192.168.42.1

This is how it is configured out of the box and will work if you are just using the WiPi-Netbooter wireless SSID. The issue has come when you've added the Pi to your home wifi network which clashes with the wired IP range on the Pi. Most people use a 192.168.0.0/24 or similar IP range for their home network, using a class A 10.x.x.x range is unusual but it can be worked around.

Firstly I would reset your wifi configuration by creating a file called reset.txt in the boot partition then starting up the Pi. Look at the activity lights, it will restart twice and you should then be able to see the WiPi-Netbooter SSID again.

Connect to WiPi-Netbooter and open up the WiPi interface in a browser, go to Setup and Network Configuration. Go to the Wired setup and you'll see it is set to 10.0.0.1, in the form on the page change it to a new static address: 192.168.0.1, subnet mask 255.255.255.0. Apply and the Pi will reboot with the new address.

Reconnect back to WiPi-Netbooter SSID and go back into Setup and Network Configuration to check that the wired interface now has the 192.168.0.1 address. If that has worked you can now join your home wifi network from the wireless configuration screen. Choose the SSID from the drop down and enter your password and apply, the Pi will reboot twice, watch the activity lights and when the Pi is back online you should be able to access it on your home network.

Depending on your router setup you may or may not be able to reach http://netbooter.local - if you can't you can scan your home network for the Pi, I use a mobile app called Fing. If the Pi appears on the list you can connect the IP address rather than the name, in the format http://<ipaddress>.

You have the option to set a static IP address on your Pi for the wireless network so it is easier to find, you need to know what DHCP addresses are given out by your router for this and choose an address that sits outside of that range.

You can now plug your Pi into the Naomi and set up an IP address in the service menu on the Naomi itself, use 192.168.0.2 with subnet mask 255.255.255.0 and restart. Then go into the Netdimm Config menu and create a new Sega Naomi netdimm with the matching IP address 192.168.0.2. The entry should turn green if everything is OK and then you start sending games.
following these directions to the tee helped fix everything!

So I think my mistakes were bountiful.

1. I was trying to set the static ip for the WiPi Ethernet thru dietpi-config which requires a gateway for the 192 range and I was guessing on that.

2. My 5ghz and 2ghz NETGEAR router came up with the same SSID for when scanning (even tho ugh they are separate) so I saw the same SSID in the wireless network list twice.

3. The 5ghz NETGEAR SSID had a hyphen in it. I removed the hyphen. Once I did that it seemed like only one option for the NETGEAR SSID came up within the WiPi netbeooter.local settings.

A combo of those mistakes seems to be the culprit.

But if you follow these instructions above for this scenario you will be golden! Thank you Chunksin. You really modernized this arcade experience from the 90s and made my “mini Sega arcade” awesome!
 

Attachments

  • BF4C1435-5FF5-42EB-8156-38D74300CE77.png
    BF4C1435-5FF5-42EB-8156-38D74300CE77.png
    256.8 KB · Views: 99
  • image.jpg
    image.jpg
    228.1 KB · Views: 102
Last edited:
I searched through the thread and no one seemed to have a solution to the whole "Some 32GB cards don't have enough space", so I managed to truncate the image so it'd fit on mine by removing a bit of the free space on the larger partition. Here's a pretty decent guide on how to do it provided you have access to a linux box. https://askubuntu.com/questions/117...d-card-how-to-shrink-a-bootable-sd-card-image . I did test it afterwards and everything seems to work fine (and probably will unless there are log rotation issues that rely on that free space).
 
@chunksin released an 8gb image with nothing in it on discord, just a base image with the latest version

With this image, you can then expand to any 32gb card and fit everything properly - that's what I've done on a number of 32gb cards I've had.

Happy to post the link here, but will need confirmation from Chunksin before I do it
 
@chunksin released an 8gb image with nothing in it on discord, just a base image with the latest version

With this image, you can then expand to any 32gb card and fit everything properly - that's what I've done on a number of 32gb cards I've had.

Happy to post the link here, but will need confirmation from Chunksin before I do it
Oh dang that would have been super useful for me haha. Glad there's a more official resource out there somewhere.
 
Is there any option to make the netbooter.local webpage to change to dark mode? I see OSD has a dark mode but don't think thats quite what I'm looking for. Maybe it just doesn't look good so was left out as a feature?
 
@chunksin released an 8gb image with nothing in it on discord, just a base image with the latest version

With this image, you can then expand to any 32gb card and fit everything properly - that's what I've done on a number of 32gb cards I've had.

Happy to post the link here, but will need confirmation from Chunksin before I do it
Please do! Myself (and a lot of people I assume) don't use Discord.

Paging @chunksin
 
I got the 480x320 touchscreen to work, but does this image also support higher resolutions screens? The tiny low res screen combined with the resistive touch controls makes it very difficult to use, even with the NDS lite stylus.

I have a cheapo 1024x600 7" touchscreen that would probably be a lot easier to use if it worked
 
Hi @chunksin!!

I got this odd message today - after the obligatory 7 day card clean, it rebooted as usual and came with a card writer error (log below). I jumped into the test menu and back out, and it loaded up fine.

root@Netbooter:/tmp# more card_output.txt

703---> Previous process PID: 705

---> No Card file name provided, using autogen and switching to real time mode

COM port opened and named: Chihiro

---> New random filename /var/log/activecard/card_3MA2Tj generated. It will be available for purchase as a new card in t

he game.

2022-10-27 11:21:17.633084: Chihiro

02 07 10 00 00 00 30 03 24

Command Code is: 10: CARD_INIT(10)

Reader Emulator: Acknowledging: 06

2022-10-27 11:21:18.016620: Chihiro

05

Reader Emulator: Sending Init Reply(10): 02 06 10 30 30 30 03 25 - Initializing Variables

2022-10-27 11:21:18.181584: Chihiro

02 0C 78 00 00 00 37 31 34 30 30 30 03 75

Command Code is: 78: CARD_78(78)

Reader Emulator: Acknowledging: 06

2022-10-27 11:21:18.534333: Chihiro

05

Reader Emulator: Sending 78 Reply: 02 06 78 30 30 30 03 4D

2022-10-27 12:02:16.616626: Chihiro

02 0C 78 00 00 00 37 31 34 30 30 30 03 75

Command Code is: 78: CARD_78(78)

Reader Emulator: Acknowledging: 06

2022-10-27 12:02:16.935285: Chihiro

02 06 A0 00 00 00 03 A5 05 05

Command Code is: A0: CARD_CLEAN_CARD(A0)

Reader Emulator: Acknowledging: 06

2022-10-27 12:02:17.136133: Chihiro

05

Reader Emulator: Sending: CARD_CLEAN_CARD(A0) Reply Step 0: 02 06 A0 30 30 33 03 96

2022-10-27 12:02:17.283579: Chihiro

05

Reader Emulator: Sending: CARD_CLEAN_CARD(A0) Reply Step 1: 02 06 A0 31 30 33 03 97

2022-10-27 12:02:17.894558: Chihiro

05

Reader Emulator: Sending: CARD_CLEAN_CARD(A0) Reply Step 2: 02 06 A0 34 30 30 03 91

2022-10-27 12:02:18.939058: Chihiro

05 05

Reader Emulator: Sending: CARD_CLEAN_CARD(A0) Reply Step 3: 02 06 A0 30 30 30 03 95

2022-10-27 12:02:19.952644: Chihiro

05

Reader Emulator: Sending: CARD_CLEAN_CARD(A0) Reply Step 3: 02 06 A0 30 30 30 03 95

2022-10-27 12:02:44.477431: Chihiro

82 10 04 00 00 30 03 24

Command Code is: 0 : UNKNOWN COMMAND!(0 )

ERROR: Emulator is ignoring or does not know how to respond to: 82 10 04 00 00 30 03 24


Matt
 
http://netbooter.local/options.php - can you load the page directly?

Depending on the device you're connecting from, you may need to replace "netbooter.local" with the IP address.
Raspberry Pi 1 doesn't have wifi module, so I can't access to options or Time Hack. Where is the file with the activation variable of that mode for hand-modifying?
 
Could connect it with a standard network cable as well. But if you can't do that, try editing this file:

/sbin/piforce/zeromode.txt

Try changing it from "hackoff" to "hackon". I haven't tried manually changing it, but that appears to be the file that the php and python files call on when toggling through the web interface.
 
Back
Top