SSH WIFI ISSUE
-
@90sgamer back up your image. Flash the new OS. Use 7zip to extract the BIOS, ROMS, and CONFIG folders from your backed-up image. Copy them to the new OS.
-
@sleve_mcdichael Yes, I understand, I know what I need to do which is make a back up. I understand how to back up an sd card. What I don't understand is how do I then implement the backup on the new OS without completely wiping out everything. If I don't understand how the entire process works, I'm not going to even start or risk destroying my card.
-
What I don't understand is how do I then implement the backup on the new OS without completely wiping out everything.
Use 7zip to extract the BIOS, ROMS, and CONFIGS folders from your backed-up image, and copy them over to the new OS.
(Edit: sorry, configS with an S.)
If I don't understand how the entire process works, I'm not going to even start or risk destroying my card.
You can always write the backup back to the card and pick up right where you left off...
-
@sleve_mcdichael To my knowledge, the only way to access the BIOS, ROMS, and CONFIG folders is to access them via SSH using wifi (which was the initial issue and reason for this thread). Are you saying that this can be done (access and backup the BIOS, ROMS, and CONFIG folders ) by inserting the sd card directly into the computer? Because I've tried that and all I see are a bunch of folders I don't get the neat and clean BIOS ROMS CONFIGS SPLASHSCREENS, that i see everywhere on other tutorials.
-
@90sgamer said in SSH WIFI ISSUE:
I know what I need to do which is make a back up. I understand how to back up an sd card.
Okay so you've backed up the SD card and the
.imgfile of the SD card is saved somewhere on your PC. Download and install 7zip to your PC. Use 7zip to open and view the contents of the.imgfile.Extract the
/home/pi/RetroPie/romsfolder and save it somewhere (you can just drag it out of the 7zip window and alt-tab into whatever file folder on the PC you want to drop it into.)Extract
/home/pi/RetroPie/BIOS.Extract
/opt/retropie/configs.Wipe your card (this is safe, since it's backed up.) Write the new OS to the card in the same manner you did the first time. Set up your locale settings and keyboard layout.
Set up your WiFi. As soon as it's on your WiFi, you can get on the network share and drop the extracted folders right there where it says "roms," "configs," and "bios."
-
@90sgamer what i see is this...
-
@sleve_mcdichael Oh thats a great idea, didnt think of that. I'll try it!
-
@sleve_mcdichael ok now I have a fresh clean slate of the latest version of buster on my retropie with everything backed up. I setup the country, and enabled SSH. Tried to connect to SSH to transfer files and ... nothing :( Just says device doesnt exist or timed out. I should be very easily able to connect a retropie out of the box?? Not sure what the dealio is.
-
@90sgamer you've set up WiFi on the Pi?
-
@90sgamer as I understand it, your Pi is supposedly on your WiFi network but you can't connect to it?
Let's go back to basics:
How is your Pi obtaining an IP address (I'm assuming normal DHCP)
Can you plug a keyboard into the Pi and get to a shell. From there, can you ping FROM the Pi to any other device (your router for example)?
Can you execute 'sudo ifconfig -a' and post the results for the 'wlan0' section? For example,. here is mine:
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.1.8 netmask 255.255.255.0 broadcast 10.1.1.255
inet6 fe80::5256:e6e5:714e:108f prefixlen 64 scopeid 0x20<link>
ether dc:a6:32:8b:d4:fe txqueuelen 1000 (Ethernet)
RX packets 900 bytes 225393 (220.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 127 bytes 21111 (20.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0None of the above will solve anything but it may point to a potential issue. Many thanks.
-
@greyareauk yes I have a keyboard, not sure what dhcp is or how to check for it, but probably yes.
This is my result...
-
I didn't see the question asked, but did you enable SSH under interface options from the CLI? If you have a keyboard connected, you can press F4 to the CLI, then run 'sudo raspi-config'. In the configuration utility, access 'interface options' and enable SSH.
You seem to have the Pi on the network and getting an address, could just need to have SSH enabled.
-
@theotherdan Yes, did that first, SSH is enabled.
-
What SSH client are you using?
Also, need more framing...
- What is the client you are using?
- What is the protocol you are using?
- What are you trying to do?
WinSCP is an FTP client, you will need to ensure you can reach port 21. WinSCP likes to use SFTP by default, so make sure you set it to FTP(21).
SSH on the other hand is port 22 and a CLI option to the PI. There is no real default beside port 22, even for apps like PuTTY.
-
@theotherdan
1.Using WinSCP client.
2. I was using SFTP with port 22 to connect with SSH. (I tried FTP too, just because you mentioned it, didnt work either.)
3. Trying to transfer my backed up roms and config files. -
@90sgamer said in SSH WIFI ISSUE:
1.Using WinSCP client.
2. I was using SFTP with port 22 to connect with SSH. (I tried FTP too, just because you mentioned it, didnt work either.)
3. Trying to transfer my backed up roms and config files.Have you tried the Samba-shares? Just type
\\retropiein your PC's search bar.https://retropie.org.uk/docs/Transferring-Roms/#samba-shares
-
@90sgamer said in SSH WIFI ISSUE:
@mitu Correct, it's always worked and now it isn't. Not trying to be a difficult case. Perhaps the wifi chip in the retropie is fried? I've looked at this from several different angles and I don't think its router related. If I could get my pi to transfer files i would be so happy. There are not many tutorials on transfering roms without wifi. I appreciate your help. Ive been stuck on this for a few months, any other ideas would be greatly appreciated, maybe something outside the box or easily overlooked?
- I would say this is the biggest sticking point
- If you have a wifi adapter showing up in the OS, I don't think your chip is fried
- High level, possible your router and or a switch is not passing traffic from the pi (TCPdump would show that or not)
- It could be due a stale table, per say, as you are using DHCP
- You could look at rebooting your router and any switches you are using if you have not
- As far as using something besides Wifi, just take the Pi and plug it straight into the router
Let me know if you want to look at a packet trace and I can help you with the syntax
-
@theotherdan I've rebooted my router on several occasions. Didn't work.
How would connecting my router directly to my pi help? I still would not be able to transfer files.
All I want to know is how to connect my computer to my retropie. Should I call my Internet service provider and have them change the settings on my router, or is it something in the physical I can do in front of me, like a switch or something. I'm not sure what a packet trace is nor am I very familiar with terminal code. I think its something to do with my router, but not sure where to start. -
If you can connect directly to your switch, with a cable, you will effectively use a new MAC and will help prove or disprove the theory.
Don't know what router you are using, but if it a wifi router, should have some ports you can plug a cable into.
Additionally, if you have a spare memory card, load a fresh image and connect to wifi, and see if you can reach it via Samba or SFTP/FTP.
-
@theotherdan Not sure the issue, but this thread is solved. I got a new computer and now my pi is updated and set!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.