Closed
Bug 784524
Opened 12 years ago
Closed 12 years ago
Can't get wifi to work on self-built Otoro
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: joe, Unassigned)
Details
On my otoro device, no matter what I do, I can't get wifi to work. When I tap the wi-fi checkbox, it unchecks itself, and since I enabled debug mode in wifi_worker.js, I get an error in my logcat: WifiWorker component: WIFI: load_driver returned: -1 No errors happen at the same time in the device's dmesg.
Comment 1•12 years ago
|
||
Did you upgrade the device to ICS and upgrade the kernel?
Reporter | ||
Comment 2•12 years ago
|
||
Yes to both.
Reporter | ||
Comment 3•12 years ago
|
||
And it works when I use a prebuilt otoro image.
Comment 4•12 years ago
|
||
You have old GB executables in your build tree. Nuke the whole tree and extract new blobs.
Reporter | ||
Comment 5•12 years ago
|
||
Deleting out/ and gecko-objdir/ isn't enough, then?
Comment 6•12 years ago
|
||
I started to see the "Tap the Wifi box and have it uncheck itself" behaviour. I had pushed a wpa_supplicant.conf file because I got tired of having to reenter the password every time I reflashed the board. In my case the wpa_supplicant.conf file was owned by root.root after doing the adb push. Changing the permissions on this file (or removing the wpa_supplicant.conf file) and rebooting allowed wifi to start working again.
Comment 7•12 years ago
|
||
No. I think the binary blobs are stored outside out/ and gecko-objdir/. Blow away everything, start over, to confirm that this is the cause. Comment 6 sounds useful too.
Reporter | ||
Comment 8•12 years ago
|
||
Yup, this was simple bad drivers.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•