Faucon2001 wrote:A quick search on the net showed that Pi can't connect to a wifi setup on canal 12 and 13. Is it your case?
http://raspberrypi.stackexchange.com/qu ... 7921#37921
Faucon2001 wrote:Ok, I believe I have found the culprit ; the script to setup network interface for Linux side was not working properly all the time.
It should improve greatly Wifi connection, and works with WPA-PSK et WPA2-PSK security.
I have also added in this first update some other improvement to reduce boot time significantly. Instructions are in the archive.
http://www.philippeworld.net/ftp/Instal ... pdate1.zip
Tell me if it helps.
Faucon2001 wrote:No, netmask has nothing to do with your problem. Leave it like that.
From the questions you are asking, I guess you have not read the online manual. I would recommend you to read the manual before trying to tweak anything.
Alt-F12 is used to open Aranym setup. I don't understand what do you mean by "switch". If it no longer opening Aranym setup you may have screwed up something.
I repeat, your issue is not on the Atari side so far, it's Linux which can't connect to your network. And forget Wifi for now, try to have an Ethernet connection first. So let us fix that first and after we will see if there an issue on the Atari side.
I don't like to ask to reinstall, it's sound like a hotline, but in order to have a fresh base, it's better
Apply the update following the readme.
Confirm that your chain is :
Internet -> router -> Pi
Do you have several routers in your chain? Do you use different subnet? Do you have free IP address in the DHCP range? Do you have Mac filtering?
Network setup is done by right clicking on the desktop, menu setup/system setup.
To connect by Ethernet, you must choose option 4 "Wifi_Ethernet", option 2 "connect_Ethernet" , and cold reboot.
After reboot, you should see on the desktop phweather showing the weather of Mexico, if not there is an issue.
What is showing ifconfig on the Linux side (ssh root@beepi, ifconfig)?
You should see l0 , tap0 and eth0 with an IP address . If you don't have eth0 or don't have an IP address, your Pi is not connected. As the Pi connect via DCHP, it means that or your Ethernet cable is bad, or your router is not allowing it to connect. Revise your router setup.
If you have eth0 and an IP address, from another machine try to ping this address.
From root@beepi try to ping your router.
If everything is ok till now but you don't have internet access in Mint, we will have to dive into the Atari side.
So on the linux side should there be a gateway in the routing table? And should the interface be tap0? I guess I don't understand the layers yet as far as the pi side and the linux side.
On the linux side I just have one line in the routing table. I sent you pictures earlier of the results I see after booting via PM.
Faucon2001 wrote:So on the linux side should there be a gateway in the routing table? And should the interface be tap0? I guess I don't understand the layers yet as far as the pi side and the linux side.
I am going to answer your question here instead of PM, as it could interest others.
Aranym (Atari emulation side) is running on top of Linux (host system or Linux side)
The host system is providing to Aranym several services and in particular the network.
Linux connects to your network via Ethernet or Wifi and is configured automatically by DHCP.
In order to communicate with Aranym, we set a bridge with tap0 between the host and the Aranym.
So the connection looks like : network <-> host eth0 or wlan0 <-> tap0 <-> Aranym eth0
your problem so far is that you don't have host eth0 or wlan0 configured.
That's why, I asked you to check the network connection on the host (linux side) by connecting to the host with ssh root@beepi and running ifconfigOn the linux side I just have one line in the routing table. I sent you pictures earlier of the results I see after booting via PM.
Yes, and it showed that Linux side was not connected nor to Ethernet nor to Wifi.
Do you have now eth0 or wlan0 on the linux side? No need to look at the routing if your Pi is not connected.
When you are on the linux side, enter :
You should see eth0 with an ip address, otherwise I don't have a clue, sorry.
mikro wrote:Really, the only complication is video output,
nobox wrote:It isnt. You can connect a Raspberry PI to an SC1224 and even to an SM124.
But I guess there maybe a problem with IKBD. As far as Iknow, It is an IKBD Injector and not an "bidirectional IKBD Communikation Device"
The solution would be to add an Arduino micro beside the Pi, who can handle the IKBD Inputs and switch between Raspberry and Atari.
mikro wrote:Whaaaat.... but still, you have to do some wiring from the DVI port, one way or another.
mikro wrote:I'm not sure what you mean here:
IKBD commands (mouse, keystrokes) --> IKBD injector --> RPi --> handling of the commands
This is basically how it works.
Users browsing this forum: No registered users and 2 guests