Tiny Core Base > CorePlus

WiFi Cannot Scan

<< < (10/30) > >>

eltone:

--- Quote from: Juanito on January 11, 2014, 03:42:44 AM ---b43-fwcutter updated to the latest version.

To cut your own firmware:
--- Code: ---$ wget -c http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
$ tar xf broadcom-wl-5.100.138.tar.bz2
$ sudo mkdir -p /usr/local/lib/firmware
$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o
--- End code ---

--- End quote ---

hi,
TCP 4.73 LiveUSB trapped this error while attempting to cut firmware, using the 5.1 protocol:


--- Code: ---tc@box:~/b43fw$ tar xf broadcom-wl-5.100.138.tar.bz2
tc@box:~/b43fw$ sudo mkdir -p /usr/local/lib/firmware
tc@box:~/b43fw$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.1
38/linux/wl_apsta.o
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum e1b05e268bcdbfef3560c28fc161f30e.
tc@box:~/b43fw$

Q: Why would TCP 5.1 overlook this obvious problem TCP 4.73 reports?
eltone


--- End code ---
:

Juanito:
tc-4.x uses an earlier version of the firmware cutter, maybe this is the reason for the error?

Juanito:

--- Quote from: eltone on January 14, 2014, 06:39:09 PM ---Once the WLAN framework is stable, I'd be happy to do further beta  . . .

--- End quote ---
As mentioned earlier, due to the fact that a lot of wifi hardware is closed source, getting wifi working under linux is often a matter of trial and error to find a working driver and/or firmware.

The above being said, yours is the first case I've seen where wifi is disabled in software on boot.

Wifi works in tc-5.x for me and others with broadcom hardware and I believe it will work for you once we find the right method.

Given that you reported earlier that the wifi extension displayed several wireless access points, you cannot be that far from success.

I suggest you make an extension of the cut firmware and try the following:

* remove any "blacklist" boot codes
* remove any firmware/wireless extensions from "onboot"
* reboot
* load the firmware extension
* load the wireless-KERNEL extension
* load the rfkill and wifi extensions
* unblock the wifi software switch with rfkill
* run the wifi.sh script

..and let us know how you get on.

eltone:

--- Quote from: Juanito on January 15, 2014, 01:51:05 AM ---
I suggest you make an extension of the cut firmware
--- End quote ---

Dear Juanito:

Better yet, have your TCP 5.1 team recompile this extension:

http://repo.tinycorelinux.net/4.x/x86/tcz/b43-tools.tcz

Once completed, I hope it's all down-hill \
                                                                 \.
eltone

Juanito:
You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?

Navigation

[0] Message Index

[#] Next page

[*] Previous page