Official XBian 1.0 Beta 1.1 thread

[thedude459]

(2nd Aug, 2013 08:21 AM)mk01 Wrote:  

(2nd Aug, 2013 08:13 AM)thedude459 Wrote:  So the space in the SSID name actually does not work. I was using Belkin_2.4 which works but Savage 2.4 does not work. Also when I do an exit from the 'power' button on the homepage it just restarts even if I hold the shift key.

dude, this can happen for a specific case, when your asks xbmc to quit, xbmc tries to stop running child threads and fails. then xbmc stops / crashes with exit code not 0, so system thinks it was "just" crashed and restarts it - what was requested feature.

most of the time python add ons are "hanging". it was reported to xbmc devels as a bug many times two years ago with huge flame war and no solution.

---

(2nd Aug, 2013 08:13 AM)thedude459 Wrote:  So the space in the SSID name actually does not work. I was using Belkin_2.4 which works but Savage 2.4 does not work. Also when I do an exit from the 'power' button on the homepage it just restarts even if I hold the shift key.

hm, is this story with two different sticks pointing to a bug in driver / firmware rather then in scripting around them?

xbian config is writing the password to /etc/network/interfaces (please check content of the file), so it handles the sticks not directly. then wpa-supplicant process is picking this info, using it to create connection to ap.

so if "interfaces" file is ok for both, then the bad thing must happen at level we can't solve.

check the file, then we will discuss next steps.

When I select Savage 2.4 from the list it says it can't connect then it shows the SSID in the box as Savage/

I am going on vacation but I will look at the file that you said when I come back.

The part that you suggested worked for my SQL database though, thank you.