Official XBian 1.0 Beta 1.1 thread

[mk01]

(30th Jul, 2013 08:12 AM)thedude459 Wrote:  With this release xbian isn't picking up my sql database. With openelec I had to delay startup for 10 seconds so the network could start. Should I have to do this with this as well? I am running an unraid that is hard lined but the pi is wifi.

open xbmc-preload.conf

and change as here - so add network device initialized as dependency
http://forum.xbian.org/thread-1172-post-13497.html#pid13497

---

(2nd Aug, 2013 02:44 AM)slovdahl Wrote:  sensitive data like passwords for NFS/SMB shares, FTP servers, and so on.. @mk01, maybe you could exclude .xbmc/userdata/mediasources.xml and sources.xml at least?

xbmc is using password files now, you should remove the usernames and passwords from sources, if they are historically there. otherwise you are leaking your password, not me.

i will not be able to review issues in categories "my xbmc is not connecting to nas or samba server".

i'm sure everybody is removing sensitive data before sending to me. this process is manual, not files are send away automatically.

but you have +1 for making this clear for other users

---

(2nd Aug, 2013 02:44 AM)slovdahl Wrote:  AirPlay stopped working for me after updating from beta 1.0 to 1.1 as well. I have tried all fixes mentioned in the thread and dbus and avahi are running now, but it still doesn't work. My iPad mini recognizes XBian as a AirPlay receiver, but when I choose XBian in eg.

unfortunately, if dbus and avahi is running, on top of the fact that xbian is presenting itself as airplay renderer…

i can't do much. Take xbmc from beta 1.0 and install to beta 1.1 - to pinpoint the source.

[thedude459]

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.

[mk01]

(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.

[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.

[mk01]

(3rd Aug, 2013 12:01 AM)thedude459 Wrote:  The part that you suggested worked for my SQL database though, thank you.

ok thanks. it's in the beta2 already as standard.

about the savage, as you described more details now, can even happen, that "iwlist" provides different output with this card (so points again to driver difference), but could be solved within xbian-config.

can you please send "lwlist wlan0 scanning" output, for both usb sticks? thanks

[numanoids]

I did a clean-installation followed by an xbmc-restore and I've discovered that zeroconf isn't showing any of my sources. Anyone able to confirm this or not? Normally I see NFS and SFTP sources in there and this worked previously.

[thedude459]

xbian@xbian ~ $ lwlist wlan0 scanning
-bash: lwlist: command not found

Am I doing something wrong?

[f1vefour]

(6th Aug, 2013 12:53 AM)thedude459 Wrote:  xbian@xbian ~ $ lwlist wlan0 scanning
-bash: lwlist: command not found

Am I doing something wrong?

That's iwlist

[thedude459]

I also do not have iwlist

xbian@xbian ~ $ iwlist wlan0 scan
-bash: iwlist: command not found

[f1vefour]

(6th Aug, 2013 12:56 AM)thedude459 Wrote:  I also do not have iwlist

xbian@xbian ~ $ iwlist wlan0 scan
-bash: iwlist: command not found

Try sudo apt-get install wireless-tools...not at home to check.

I looked it up.

[thedude459]

Had to do /sbin in front of it

Code:

xbian@xbian ~ $ sudo /sbin/iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 94:44:52:1B:88:0D
                    ESSID:"Savage_2.4"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    Bit Rates:144 Mb/s
                    Extra:rsn_ie=30140100000fac020100000fac020100000fac020c00
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Quality=99/100  Signal level=67/100
          Cell 02 - Address: C8:60:00:94:DC:C0
                    ESSID:"Savage_2.4"
                    Protocol:IEEE 802.11bgn
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    Bit Rates:300 Mb/s
                    Extra:rsn_ie=30140100000fac040100000fac040100000fac020000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD8F0050F204104A0001101044000102103B00010310470010BC329E001DD811B28601C8600094DC​C0102100154153555354654B20436F6D707574657220496E632E1023000A57505320526F75746572​1024000752542D4E3536551042000830303030303030301054000800060050F20400011011000F41​5355532057505320526F7574657210080002008C103C000101
                    Quality=100/100  Signal level=58/100

[f1vefour]

Do you have a dual-band router with both SSID's named the same?

Or a virtual interface named the same?

[thedude459]

Terminal

xbian@xbian ~ $ sudo iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:"Savage_2.4" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.437 GHz Access Point: 94:44:52:1B:88:0D
Bit Rate:72 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=99/100 Signal level=68/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[f1vefour]

When your posting logs please enclose them with [code] or [term], you didn't answer my previous question. Your scan showed two SSID's named the same but on different channels.

[thedude459]

Sorry I didn't see your question. We must have posted at the same time. I have 2 dual band routers. One attached to the other via cat5 cable.

So yes I have Savage_2.4 on channel 1 and 6 then I have Savage_5 on 2 different channels.

One router is setup as the gateway with DHCP then other is a router with no DHCP.