Forum

(27th Nov, 2017 10:46 AM)deeej Wrote: [ -> ]Ok, are you ready for the "kicker" off the year?

Changing Network SSID did it!!!!

Wow, unbelievable

Quote:And the even more funny thing is that it will list routers SSID with spaces "This is a router" :-D

Same here, I see ESSID's with spaces, but never used a ESSID with space included. AFAIR there is/was ? a problem, but can't remember in which context that was. Toooo long ago ...

Ehm, maybe the router was confused and needed restarting ....

Quote:This have to be a bug and not an intendent feature with Kodi 17.4 and up. SSID with spaces have never been a problem for me until after Kodi 17.4.

Again, that has nothing to do with Kodi 17.4, must be a different package, maybe wpasupplicant or kernel, don't know

But anyway, I'll test a ESSID with spaces next days, will see what happens

Quote:Just for the kick off it. I will try to reset my SSID to "Asus router" and see what will happen (will do that tomorrow) :-)

THANK YOU SO MUCH!!!! For your patience and guidance!!!

I will post a report what happened when i tried reseting to a SSID with spaces....will it let me scan?

Ok, so good night

Got the same problem (with the small difference that i'm still on 17.4 and not on 17.6) after installing the latest system-update and performing a restart, and the solution for me was also changing the ssid name from "Martin Router King" to "MartinRouterKing" first on my router and then on xbian via sudo nano /etc/network/interface
Now Kodi is able again to search for networks. But what i don't understand - there are plenty of networks with no blank in the ssid and Kodi couldn't find them before.

edit: one minute later and it's broken again
edit2: aaand it seems that i can't get it running again

(28th Nov, 2017 04:10 AM)ThePumisher Wrote: [ -> ]Got the same problem (with the small difference that i'm still on 17.4 and not on 17.6) after installing the latest system-update and performing a restart, and the solution for me was also changing the ssid name from "Martin Router King" to "MartinRouterKing" first on my router and then on xbian via sudo nano /etc/network/interface
Now Kodi is able again to search for networks. But what i don't understand - there are plenty of networks with no blank in the ssid and Kodi couldn't find them before.

edit: one minute later and it's broken again
edit2: aaand it seems that i can't get it running again

OMG so the culprit must be in one of the packages you upgraded


helps finding all packages which has been upgraded

Hi, I am not sure if it helps in the discussion, but I am also facing problems with the onboard wlan0 adapter. I am not running kodi on this interface, but it stopped working after upgrading to the new linux kernel (4.9.62+-1511024152). I have reverted back to kernel 4.9.60+. This works fine with Kodi 17.6.
The issue with the wlan0 adapter that I had is that it did not receive any DHCP offers. I also tried to configure the adapter using a static IP but that also did not work. So it looks to me that it has got to do something with the kernel the driver or maybe a combination?

(28th Nov, 2017 05:52 AM)Nachteule Wrote: [ -> ]OMG so the culprit must be in one of the packages you upgraded

Code:

sudo cat /var/log/dpkg.log | grep upgrade

helps finding all packages which has been upgraded

i somehow managed to install 17.6 in the past hour (via ethernet), but that doesn't help fixing the wifi

---

(28th Nov, 2017 06:22 AM)Roy Terhaar Wrote: [ -> ]it stopped working after upgrading to the new linux kernel (4.9.62+-1511024152).

after looking when installed that package, this seems to be the time my wifi was broken

how to i set back to an older kernel if that may be the solution? never done that

(28th Nov, 2017 06:27 AM)ThePumisher Wrote: [ -> ]

(28th Nov, 2017 05:52 AM)Nachteule Wrote: [ -> ]OMG so the culprit must be in one of the packages you upgraded

Code:

sudo cat /var/log/dpkg.log | grep upgrade

helps finding all packages which has been upgraded

i somehow managed to install 17.6 in the past hour (via ethernet), but that doesn't help fixing the wifi

Code:

2017-11-12 20:49:57 upgrade xbian-package-config-shell:armhf 20171001-1 20171108-0
2017-11-12 20:50:35 upgrade linux-image-bcm2836:armhf 4.9.58+-1508858583 4.9.60+-1509910371
2017-11-12 20:51:33 upgrade xbian-package-initramfs-tools:armhf 20171010-0 20171110-0
2017-11-12 20:52:05 upgrade xbian-package-repo:armhf 20170902-0 20171106-0
2017-11-21 17:40:00 upgrade linux-image-bcm2836:armhf 4.9.60+-1509910371 4.9.62+-1511024152
2017-11-27 19:54:52 upgrade xbian-package-initramfs-tools:armhf 20171110-0 20171122-0
2017-11-27 19:56:22 upgrade xbian-package-config-shell:armhf 20171108-0 20171124-0
2017-11-27 19:16:49 upgrade xbian-update:armhf 20171002-0 20171110-0
2017-11-27 19:39:02 upgrade xbian-package-xbmc:armhf 17.4-154187472 17.6-1511083250

---

(28th Nov, 2017 06:22 AM)Roy Terhaar Wrote: [ -> ]it stopped working after upgrading to the new linux kernel (4.9.62+-1511024152).

after looking when installed that package, this seems to be the time my wifi was broken

how to i set back to an older kernel if that may be the solution? never done that

1) get all versions available:


2) Install version you want:


for example sudo apt-get install linux-image-bcm2836=4.9.60+-1509910371

(28th Nov, 2017 06:22 AM)Roy Terhaar Wrote: [ -> ]Hi, I am not sure if it helps in the discussion, but I am also facing problems with the onboard wlan0 adapter. I am not running kodi on this interface, but it stopped working after upgrading to the new linux kernel (4.9.62+-1511024152). I have reverted back to kernel 4.9.60+. This works fine with Kodi 17.6.
The issue with the wlan0 adapter that I had is that it did not receive any DHCP offers. I also tried to configure the adapter using a static IP but that also did not work. So it looks to me that it has got to do something with the kernel the driver or maybe a combination?

Thanks for reporting

Hmmm, that's strange. I was testing with this version yesterday, no issue occurred.

There was one brcmfmac related commit after release of 4.9.62, I'll build new kernel (4.9.65) now

Ok, everything worked great last night.

So today, i did the HUGE mistake on updating everything. Now, it is broke again...even if my ESSID is now a one word. This is brutal :-(

That´s it...i´m turning off ALL updates!

Here is my dpkg.log

I used a clean install on Xbian_2017.11.24_rpi3.img

(28th Nov, 2017 07:45 AM)deeej Wrote: [ -> ]Ok, everything worked great last night.

So today, i did the HUGE mistake on updating everything. Now, it is broke again...even if my ESSID is now a one word. This is brutal :-(

That´s it...i´m turning off ALL updates!

Revert to an older snapshot (root partition), that's not a problem. Only kernel has to reverted manually

(28th Nov, 2017 07:49 AM)Nachteule Wrote: [ -> ]

(28th Nov, 2017 07:45 AM)deeej Wrote: [ -> ]Ok, everything worked great last night.

So today, i did the HUGE mistake on updating everything. Now, it is broke again...even if my ESSID is now a one word. This is brutal :-(

That´s it...i´m turning off ALL updates!

Revert to an older snapshot (root partition), that's not a problem. Only kernel has to reverted manually

I have no idea how to do that :-)

Suddenly, after rebooting....my wifi is back on (haven´t changed anything). Will try a couple of reboots.

---

I managed to roll back a snapshot. But it made no difference. 1 out of 10 reboots i have wifi connection.

I´m wiping the card again, going to install Xbian_Latest_rpi3 (Xbian_2017.11.24_rpi3.img) and this time i´m not going to do any updates. I´m not going to restore my home folder and see if that makes any difference.

I don´t know what to do. I have installed a fresh xbian version (Xbian_2017.11.24_rpi3.img). No restoring home folder or any updating.

At initial setup...it will find my wlan0 network. No problems.

But after a reboot. The network is gone. Can´t scan for routers or anything. It´s just gone.

Once again "sudo iwlist wlan0 scanning | grep ESSID" results in:

Which kernel version are you running? Roy Teheran posted that reverting to 4.9.60 solves his WLAN issue
In the meantime 4.9.65 is available, perhaps this version solves your issue

(28th Nov, 2017 09:08 AM)Nachteule Wrote: [ -> ]Which kernel version are you running? Roy Teheran posted that reverting to 4.9.60 solves his WLAN issue
In the meantime 4.9.65 is available, perhaps this version solves your issue

I run 4.9.62+.

Will follow the instructions you gave to ThePumisher. And see if that fixes the problem.

---

Tried the instruction you gave in an earlier post.

Reverted back to 4.9.60. Tried shuttingdown the system, rebooting a couple of times. And Wifi works again!!!

And also, i have learned a little Linux on the way. Thanks for ALL your help. Would have been totally lost without you!

But what does this mean? Is there a bug in the actual kernel? Do i always have to run on 4.9.60?

You mentioned 4.6.5 but i didn´t see it in the list of kernels.

I have everything turned off right now under Xbian/Update except for:
package inventory (can´t remember the actual text)
and make a APT-GET snapshot

Am i safe so it doesn´t update the system now?

(28th Nov, 2017 10:55 AM)deeej Wrote: [ -> ]

(28th Nov, 2017 09:08 AM)Nachteule Wrote: [ -> ]Which kernel version are you running? Roy Teheran posted that reverting to 4.9.60 solves his WLAN issue
In the meantime 4.9.65 is available, perhaps this version solves your issue

I run 4.9.62+.

Will follow the instructions you gave to ThePumisher. And see if that fixes the problem.

---

Tried the instruction you gave in an earlier post.

Reverted back to 4.9.60. Tried shuttingdown the system, rebooting a couple of times. And Wifi works again!!!

And also, i have learned a little Linux on the way. Thanks for ALL your help. Would have been totally lost without you!

But what does this mean? Is there a bug in the actual kernel? Do i always have to run on 4.9.60?

You mentioned 4.6.5 but i didn´t see it in the list of kernels.

I have everything turned off right now under Xbian/Update except for:
package inventory (can´t remember the actual text)
and make a APT-GET snapshot

Am i safe so it doesn´t update the system now?

new kernel has version 4.9.65 !

If you do not have enabled the auto-update feature, updates are installed on user action only. That's usually the standard setting

I would appreciate if you could install 4.9.65 kernel, to see if this strange wlan issue has gone, because unfortunately I can not reproduce this issue with my Pi 3

Thanks

(28th Nov, 2017 12:25 PM)Nachteule Wrote: [ -> ]

(28th Nov, 2017 10:55 AM)deeej Wrote: [ -> ]

(28th Nov, 2017 09:08 AM)Nachteule Wrote: [ -> ]Which kernel version are you running? Roy Teheran posted that reverting to 4.9.60 solves his WLAN issue
In the meantime 4.9.65 is available, perhaps this version solves your issue

I run 4.9.62+.

Will follow the instructions you gave to ThePumisher. And see if that fixes the problem.

---

Tried the instruction you gave in an earlier post.

Reverted back to 4.9.60. Tried shuttingdown the system, rebooting a couple of times. And Wifi works again!!!

And also, i have learned a little Linux on the way. Thanks for ALL your help. Would have been totally lost without you!

But what does this mean? Is there a bug in the actual kernel? Do i always have to run on 4.9.60?

You mentioned 4.6.5 but i didn´t see it in the list of kernels.

I have everything turned off right now under Xbian/Update except for:
package inventory (can´t remember the actual text)
and make a APT-GET snapshot

Am i safe so it doesn´t update the system now?

new kernel has version 4.9.65 !

If you do not have enabled the auto-update feature, updates are installed on user action only. That's usually the standard setting

I would appreciate if you could install 4.9.65 kernel, to see if this strange wlan issue has gone, because unfortunately I can not reproduce this issue with my Pi 3

Thanks

Sure. I will try 4.9.65 but how do i get it?
It is not listed under XBMC/Updates (only 4.9.62+) neither will 65 show up if i use:
sudo apt-cache policy linux-image-bcm2836

4.9.62+ is the highest. When i had the 4.9.62+ version it didn´t list 65 either. Because i first thought i should try to upgrade then to downgrade. But i couldn´t because it was not listed.