No Wifi Results after using Disconnect/Remove Wifi Config

columboscoat

@trigger_death plug it all in and reboot.

trigger_death

If you mean connect my Pi to ethernet, it's been on ethernet this entire time.

columboscoat

@trigger_death then post iwconfig output again.

columboscoat

@trigger_death Ha! Sorry!

trigger_death

I didn't notice any differences. Like I said I've been on ethernet since the start. :P

wlan0     IEEE 802.11bgn  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

lo        no wireless extensions.

eth0      no wireless extensions.

columboscoat

@trigger_death DO YOU HAVE A CUSTOM SETUP? IF NOT PLEASE REFLASH THE IMAGE. IT WILL BE QUICKER THAN MANUALLY CONFIGURING THE CONNNECTIVITY.

trigger_death

Nope, I don't have a custom setup but... wouldn't reflashing the image erase everything I've modified on my RetroPie since setting it up?

columboscoat

@trigger_death it would... but it means you have a fairly standard setup. Just as a by the way have you tried just reconnecting to wifi via the ES menu?

trigger_death

That's how I've been trying to connect to the Wifi the entire time. Through the RetroPie Wifi App.

columboscoat

@trigger_death Have you tried via the desktop or through the commmand line interface /terminal?

trigger_death

I haven't installed any desktop interface and I'm not familiar with how to do it through terminal.

trigger_death

Also I'm flashing a new image to a spare Micro SD I have.

columboscoat

@trigger_death go to the desktop. I assume it is PIXEL. Top right hand corner. Do you see a wifi logo or a broken connection?

trigger_death

startx doesn't seem to be recognized.

If I recall, the desktop environment isn't installed with RetroPie by default.

columboscoat

@trigger_death it's not.

columboscoat

@trigger_death Really, I would just boot a new image if I were you. Debugging this is not worth it and it's 03:30 am here so... I'm out. Good luck!

trigger_death

Thank you for the help

trigger_death

I have now narrowed the steps to reproducing this issue on a newly flashed USB and boot Micro SD.

Use this guide to enable wiimote connections.
Install the "old format hiscore.dat" in the mame2003 bios as explained in the high scores section here.
Enable Root Login over SSH by doing the following:
sudo nano /etc/ssh/sshd_config
Change PermitRootLogin to "PermitRootLogin yes"
Enter "sudo passwd root" then enter in the root password.
Restart for changes to take effect

I'm still trying to narrow it down even farther.

So far, finishing with the Wiimote steps has triggered the issue and finishing with the hiscore.dat has triggered the issue (which is really strange).

Edit: Upon narrowing it even further. You don't need to be running off USB for this to occur. All you have to do is follow the wiimote connection guide to cause this issue.

Based on this info I can assume that it's also inconsistent when the issue will first occur after following these steps, as one reboot often wasn't enough to cause it.

I've now narrowed down the cause to the following line in "/home/pi/bin/attachwii.sh".

wminput -d -q -c  /home/pi/mywminput 00:1C:BE:F2:D8:64 > /dev/null 2>&1 &

The '&' at the very end of the line is the cause of this. Removing the '&' and then running it does not cause the same issue.

Now the problem seems to be that removing the '&' at the end will not allow your system to finish booting if you have "/home/pi/bin/attachwii.sh" run on startup. Now the question is getting a little more specific as what to fix so I'll create a new post and link it below:

https://retropie.org.uk/forum/topic/7296/wminput-command-with-on-the-end-breaks-wifi