I got similar testing results as [email protected]
Most image failed to boot.

BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
and
bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
booted successfully,
but wlan0 did not work.

I did a lot of manual work on 
BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
after that, I could make wlan0 working, but I didn't know what I was doing, 
just guessing*,* trial and error.
And even wlan0 is working, it is not stable.

I have to work on some other projects.
Hope SEEED would provide a real fix.


[email protected]於 2017年1月3日星期二 UTC+8上午10時04分45秒寫道:
>
> Robert,
> I tried that build and also the last one from yesterday (1/1) but I cannot 
> make the wlan0 work on any of those builds.
> When I do a ifconfig I get this:
>
> root@beaglebone:~# ifconfig wlan0 up
> SIOCSIFFLAGS: No such file or directory
>
> And this is the dmesg:
>
> [   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl1271-nvs.bin failed with error -2
> [   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [   30.243578] wlcore: loaded
> [  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.343465] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.711388] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  189.075406] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.086887] wlcore: ERROR firmware boot failed despite 3 retries
>
>
> What do you think could be the problem here? Is this a problem with the 
> ti-connectivity version?
> Thanks for your help and time!
> Regards,
> J
>
> On Friday, December 30, 2016 at 6:44:55 AM UTC-8, RobertCNelson wrote:
>>
>> On Fri, Dec 30, 2016 at 2:37 AM, Linq John <[email protected]> wrote: 
>> > 
>> > I brought a Beaglebone Green Wireless. 
>> > At the first day, its wifi worked, so I did some apt-get 
>> > update/upgrade/dis-upgrade. 
>> > My main purpose is to use it to do some python work. UART/I2C/GPIO etc. 
>> > So I didn't discover that the wifi no longer working after the apt-get 
>> > upgrade. 
>> > I spent two working days trying to make its wifi working again, but no 
>> > success. 
>> > I didn't record the version info of the original working Debian. 
>> > And I can't find the pre-load image from 
>> > https://debian.beagleboard.org/images/ 
>> > What I can find are: 
>> > bone-debian-8.5-seeed-gcp-iot-armhf-2016-08-26-4gb.img.xz - failed to 
>> boot 
>> > bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz - failed to boot 
>> > bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz - wifi doesn't 
>> work 
>> > I also tried to use the kernel in *-iot-armhf-2016-12-09-* with 
>> > *seeed-iot-armhf-2016-11-06*, but no success. 
>> > (By changing uname_r of uEnv.txt, and even by renaming the files.) 
>> > After all these I found a thread in TI E2E: 
>> > 
>> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/p/541235/1978301
>>  
>> > So I guess it's a hardware problem, but without wifi, there is no 
>> internet 
>> > connection on BBGW, 
>> > then I am not able to install python packages, my BBGW becomes useless. 
>> > 
>> > And I guess the below images are not for BBGW. 
>> > https://rcn-ee.net/rootfs/2016-11-10/microsd/ 
>> > 
>> > Is there any work-around available for a general user? 
>>
>> Use this build: 
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2016-12-27/ 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5affe43c-e6a6-4437-b12f-de8ea8ceeb7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to