Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: eltone on January 08, 2014, 05:44:18 PM
-
Re: TCP 5.1 LiveUSB
BCM4318 WLAN chipset
Hi,
I just did a fresh TCP 5.1 install.
WiFi cannot scan/find cells:
[root@box: dmesg
Adding 261116k swap on /dev/sdb2. Priority:-2 extents:1 across:261116k
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
8139too 0000:06:06.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
root@box:~# microcode: AMD CPU family 0xf not supported
sh: microcode:: not found
root@box:~# microcode: AMD CPU family 0xf not supported
sh: microcode:: not found
root@box:~# microcode: AMD CPU family 0xf not supported
sh: microcode:: not found
root@box:~# microcode: AMD CPU family 0xf not supported
sh: microcode:: not found
root@box:~# microcode: AMD CPU family 0xf not supported
sh: microcode:: not found
root@box:~# dmesg
This problem appears to be a carrie-over from TCP 4.73, where the work-around was to use
wicd network manager and rfkill.
Q: Is there a fix coming?
Also, wicd and rfkill needs to be TCP 5.1 recompiled.
Kind Regards,
eltone
-
There's nothing in your dmesg that indicates a problem with rfkill, or any other problem with wifi.
Adjustments were made to the base for tc-5.x to change the rfkill permissions - could you confirm that your wireless does not work with the wifi extension (tested with your wired connection disconnected/disabled).
-
- could you confirm that your wireless does not work with the wifi extension (tested with your wired connection disconnected/disabled).
Dear Juanito:
Without wired ethernet, clicking the Wbar wifi icon:
Select Wifi Network
ESSID Enc Qual Channel Type
Enter selection ( 1 - 0 ) or (q)uit:
Cheatcodes used:
UI vesamenu.c32
MENU TITLE Tiny Core Bootloader
TIMEOUT 100
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet tce=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" waitusb=9:UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" restore=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" home=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" opt=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" local=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7" showapps vga=788 xsetup lang=en kmap=us pause blacklist=wl blacklist=bcma
LABEL windows
KERNEL chain.c32
APPEND hd0 1
*****************
Please note that wifi extension did find one cell yesterday that I did not recognize, while there are many in the vacinity. Also, the hp dv8000 WLAN LED does get enabled and turned off w/wifi extension.
Q: Any plans to add wicd extension to TCP 5.1?
Sincerely,
eltone
-
Honestly I'm not sure why you'd blacklist wl proprietary driver if you are using the in-tree b43 driver with bcma and ssb ?? possibly bmca doesn't need to be blacklisted either
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
Given this I'd say that the driver b43 is loaded, but no mention of the firmware?
I'd start over, uninstall the wl-modules if installed and remove all the unnecessary blacklist boot codes
blacklist=wl (is this proprietary module installed?)
blacklist=bcma (first try with this and ssb modules and firmware loaded)
Am curious of the reasons for these boot codes?
restore=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7"
local=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7"
xsetup
pause
-
Honestly I'm not sure why you'd blacklist wl proprietary driver if you are using the in-tree b43 driver with bcma and ssb ?? possibly bmca doesn't need to be blacklisted either
I have always used 'modprobe -r wl' in the past, but not 'modprobe -r bmca'
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
Given this I'd say that the driver b43 is loaded, but no mention of the firmware?
I'd start over, uninstall the wl-modules if installed and remove all the unnecessary blacklist boot codes
The two firmware extensions required for the BCM4318 chipset appear to be bundled w/TCP 5.1
b43-fwcutter.tcz
firmware-openfwwf.tcz
Q: Please list all WLAN modules required for the BCM4318 chipset?
All others should be removed!
blacklist=wl (is this proprietary module installed?)
blacklist=bcma (first try with this and ssb modules and firmware loaded)
I'm not sure about 'bcma' but 'wl' must be blacklisted when using b43 and ssb kernel modules.
Am curious of the reasons for these boot codes?
restore=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7"
local=UUID="de54793e-5803-4242-87af-27fbbdcb2bb7"
xsetup
pause
This was used to add TCP 5.1 LiveUSB stability between two computers. It shouldn't effect wifi's ability to scan for cells.
eltone
-
You have two choices to get your hardware working:
b43 kernel module with firmware, but no blacklist required (do not load wl-modules-KERNEL)
or
wl-modules-KERNEL without firmware, but blacklist the bcma, ssb and b43 modules
With the first option you may need to follow the instructions here:
http://wireless.kernel.org/en/users/Drivers/b43
..to cut your own firmware.
-
You have two choices to get your hardware working:
b43 kernel module with firmware, but no blacklist required (do not load wl-modules-KERNEL)
Juanito,
I agree with your first choice and dmesg now mentions it:
root@box:~#
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
microcode: AMD CPU family 0xf not supported
8139too 0000:06:06.0 eth0: link down
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
microcode: AMD CPU family 0xf not supported
------------[ cut here ]------------
WARNING: at drivers/net/wireless/b43/main.c:2574 0xf85ce129()
Hardware name: Pavilion dv8000 (ET831UA#ABA)
Modules linked in: cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative b43 mac80211 bcma cfg80211 squashfs loop hp_wmi sparse_keymap powernow_k8 video backlight 8139cp sdhci_pci sdhci ac battery mmc_core tifm_7xx1 wmi 8139too tifm_core ssb pcspkr
Pid: 5344, comm: ifconfig Not tainted 3.8.13-tinycore #2511
Call Trace:
[<c012b5dd>] ? 0xc012b5dd
[<f85ce129>] ? 0xf85ce129
[<f85ce129>] ? 0xf85ce129
[<c012b60b>] ? 0xc012b60b
[<f85ce129>] ? 0xf85ce129
[<f85cf02e>] ? 0xf85cf02e
[<f853a235>] ? 0xf853a235
[<f8538acb>] ? 0xf8538acb
[<c0143bea>] ? 0xc0143bea
[<c0429b7f>] ? 0xc0429b7f
[<c0429af2>] ? 0xc0429af2
[<c0429d6b>] ? 0xc0429d6b
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c0429e3f>] ? 0xc0429e3f
[<c046dca0>] ? 0xc046dca0
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c014654c>] ? 0xc014654c
[<c041945b>] ? 0xc041945b
[<c0419283>] ? 0xc0419283
[<c01b67a0>] ? 0xc01b67a0
[<c01b7239>] ? 0xc01b7239
[<c012263e>] ? 0xc012263e
[<c041a2be>] ? 0xc041a2be
[<c041afc0>] ? 0xc041afc0
[<c01b72ac>] ? 0xc01b72ac
[<c04c63d8>] ? 0xc04c63d8
---[ end trace 41743691ca79d3f4 ]---
b43-phy0: Loading firmware version 410.2160 (2015-15-255 15:32:10)
b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
net_ratelimit: 5 callbacks suppressed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
root@box:~#
I have never downloaded any firmware or needed a wired connection on other distros.
Q: Why not bundle it with TCP 5.1?
The b43 kernel module is but it's firmware is not.
eltone
-
Hundreds of unused firmware files would be a waste of memory.
Just load the extension containing the ones you need.
-
Q: Why not bundle it with TCP 5.1?
The b43 kernel module is but it's firmware is not.
broadcom does not make its drivers available to the open source community so the b43 module is reverse-engineered. This is why the linux wireless page provides the firmware cutter and points you towards where you can find the firmware to cut - it is OK for an individual to do this, but a distro cannot neccessarily make the firmware available.
if you don't want to cut your own firmware, then you can use the closed source broadcom wl module provided by the wl-modules-KERNEL extension. Since the wl module is provided by broadcom the firmware is included.
-
Hi,
'wl-modules-3.8.13-tinycore.tcz' is non-functional, therefore, please confirm accuracy:
I. Cut your own firmware w/TCP 5.1
If you are using the b43 driver from 3.2 kernel or newer:
1) Make sure b43-fwcutter.tcz is installed
2) Download version 5.100.138 of Broadcom's proprietary driver and extract the firmware from it:
a. export FIRMWARE_INSTALL_DIR="/lib/firmware"
b. wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
c. tar xjf broadcom-wl-5.100.138.tar.bz2
d. sudo b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o
root@box:/home/tc/b43fw# wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5
.100.138.tar.bz2
Connecting to www.lwfinger.com (173.254.28.119:80)
broadcom-wl-5.100.13 100% |*******************************| 13197k 0:00:00 ETA
root@box:/home/tc/b43fw# tar xjf broadcom-wl-5.100.138.tar.bz2
root@box:/home/tc/b43fw# sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-w
l-5.100.138/linux/wl_apsta.o
This file is recognised as:
filename : wl_apsta.o
version : 666.2
MD5 : e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
ucode time: 01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
ucode date: 2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
failed to open file: Read-only file system
root@box:/home/tc/b43fw#
THX!
eltone
-
Hi,
Win32 WLAN driver is non-functional:
root@box:/# ndiswrapper -i /home/tc/ndiswrsp/*.inf
couldn't open /home/tc/ndiswrsp/*.inf: No such file or directory at /usr/local/sbin/ndiswrapper line 219.
root@box:/#
-
Just at a glance, and w/o any experience with ndis wrapper, I wonder is that a typo in "/home/tc/ndiswrsp/*.inf"?
-
Just at a glance, and w/o any experience with ndis wrapper, I wonder is that a typo in "/home/tc/ndiswrsp/*.inf"?
Lee,
Correction:
root@box:~# ndiswrapper -i /home/tc/ndiswrap/bcmwl5.inf
installing bcmwl5 ...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
root@box:~# ndiswrapper -m
modprobe: invalid option -- 'c'
BusyBox v1.20.2 (2012-08-07 01:31:01 UTC) multi-call binary.
Usage: modprobe [-alrqvsDb] MODULE [symbol=value]...
-a Load multiple MODULEs
-l List (MODULE is a pattern)
-r Remove MODULE (stacks) or do autoclean
-q Quiet
-v Verbose
-s Log to syslog
-D Show dependencies
-b Apply blacklist to module names too
adding "alias wlan0 ndiswrapper" to /etc/modprobe.conf ...
root@box:~# modprobe ndiswrapper
root@box:~# ndiswrapper -l
modprobe: invalid option -- 'c'
BusyBox v1.20.2 (2012-08-07 01:31:01 UTC) multi-call binary.
Usage: modprobe [-alrqvsDb] MODULE [symbol=value]...
-a Load multiple MODULEs
-l List (MODULE is a pattern)
-r Remove MODULE (stacks) or do autoclean
-q Quiet
-v Verbose
-s Log to syslog
-D Show dependencies
-b Apply blacklist to module names too
bcmwl5 : driver installed
device (14E4:4318) present
root@box:~#
wifi.tcz remains unable to scan for cells.
eltone
PS. Need a WLAN Guru, to resolve.
http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Broadcom_BCM4318 (http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Broadcom_BCM4318)
-
b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
pcm5.fw is not listed as available in any firmware extension available for tc-5.x, except possibly firmware-broadcom_bcm43xx.tcz which may be worth trying if there is confusion over the actual chip ID, though looks like only recent devices are supported.
Realistically one solution is use the b43-fwcutter to extract the firmware then create an extension, I'm not sure of the legality to provide (bundle) this fw in any distro.
Another solution, acquire a better supported adapter (it's always an option)
'wl-modules-3.8.13-tinycore.tcz' is non-functional, therefore, please confirm accuracy:
according to http://wireless.kernel.org/en/users/Drivers/b43 (http://wireless.kernel.org/en/users/Drivers/b43) the wl-modules-3.8.13-tinycore.tcz driver might not support your specific hardware though with Broadcom it always seems worth trying. wl is also not provided in-tree so is not required to be blacklisted. wl is provided in extension wl-modules-3.8.13-tinycore.tcz, since it might not support your specific hardware should ideally be either uninstalled or be removed from onboot.lst
AFAIK for ndiswrapper to function properly, you might need to blacklist bcm,ssb and b43 modules with this boot code
blacklist=bcma,ssb,b43
-
b43-fwcutter updated to the latest version.
To cut your own firmware: $ 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
-
Win32 WLAN driver is non-functional:
$ sudo ndiswrapper -i /mnt/sdb1/drivers/ndiswrapper/E6220/xp/bcmwl5.inf
$ ndiswrapper -l
bcmwl5 : driver installed
$ sudo modprobe ndiswrapper
$ dmesg | tail -10
...
ndiswrapper version 1.58 loaded (smp=yes, preempt=no)
ndiswrapper: driver bcmwl5 (Broadcom,10/26/2011, 5.100.82.112) loaded
ndiswrapper 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
ndiswrapper 0000:02:00.0: setting latency timer to 64
ndiswrapper: using IRQ 17
wlan0: ethernet device 64:27:37:22:ab:51 using NDIS driver: bcmwl5, version: 0x5645270, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4359.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2-PSK; AES/CCMP with WPA, WPA2, WPA2-PSK
usbcore: registered new interface driver ndiswrapper
-
Greetings!
Q: If the WLAN BCM4318 chipset is this finicky w/TCP, why not eliminate all the wireless/firmware extensions from ever being installed. Now, using a wired connection, download only the needed ones from the 5.1 repo?
e.g.,
1) wireless-tools.tcz
2) b43-fwcutter.tcz & cut firmware as reported in thread.
3) wifi.tcz
4) firmware-openfwwf.tcz
5) firmware-broadcom_bcm43xx.tcz
Using this concept, blacklisting should never be needed.
Sincerely,
eltone
PS. NO bloat!
* for reference only *
-
I may be wrong, but in your case, I don't believe you need firmware-openfwwf or firmware-broadcom_bcm43xx
The blacklist is only needed if you use wl-modules-KERNEL or ndiswrapper.
..and all this because broadcom do not make their driver information freely available to linux.
-
Greetings!
Q: If the WLAN BCM4318 chipset is this finicky w/TCP, why not eliminate all the wireless/firmware extensions from ever being installed. Now, using a wired connection, download only the needed ones from the 5.1 repo?
e.g.,
1) wireless-tools.tcz
2) b43-fwcutter.tcz & cut firmware as reported in thread.
3) wifi.tcz
Hi,
Just did this barebones wireless/firmware install:
tc@box:~$ cd b43fw
tc@box:~/b43fw$ wget -c http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.1
38.tar.bz2
Connecting to www.lwfinger.com (173.254.28.119:80)
broadcom-wl-5.100.13 100% |*******************************| 13197k 0:00:00 ETA
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
This file is recognised as:
filename : wl_apsta.o
version : 666.2
MD5 : e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
ucode time: 01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
ucode date: 2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
ucode time: 01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/n0initvals11.fw
Extracting b43/lcn0initvals25.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/sslpn1initvals20.fw
Extracting b43/lcn1bsinitvals26.fw
Extracting b43/n0initvals22.fw
Extracting b43/ht0bsinitvals29.fw
tc@box:~/b43fw$
tc@box:~$ dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.13-tinycore (tc@box) (gcc version 4.7.2 (GCC) ) #2511 SMP Fri Oct 18 14:41:31 UTC 2013
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
8139too 0000:06:06.0 eth0: link down
tc@box:~$
WLAN BCM4318 has incorrect firmware! Also, wifi has NO dialog and simply vanishes!
eltone
-
b43/ucode5.fw is in firmware-openfwwf.tcz.
-
. . .download only the needed ones from the 5.1 repo?
e.g.,
1) wireless-tools.tcz
2) b43-fwcutter.tcz & cut firmware as reported in thread.
3) wifi.tcz
4) firmware-openfwwf.tcz
5) firmware-broadcom_bcm43xx.tcz
Hi,
Added 4 & 5. NO fw errors:
tc@box:~$ dmesg
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
microcode: AMD CPU family 0xf not supported
8139too 0000:06:06.0 eth0: link down
tc@box:~$
Wifi still has NO dialog/vanishes!
Q: What's the missing extension{s}?
eltone
-
Looks like you need 3 + 4 only
-
Looks like you need 3 + 4 only
coreplayer2,
Q: Then why would 1,2 & 5, being installed, cause wifi to fail?
Suspect wifi is dependent on another repo 5.1 extension{s}.
eltone
-
It's really not that difficult we're not trying to confuse you. Broadcom has been slow in providing any Linux support for their hardware. As a result the available options may sound a little confusing, though with each of these combinations it's a case of either one or the other not both/all.
There are distro's which provide a means to download and install the required proprietary firmware for you, but the end user has to initiate this.
Noting which driver and firmware is used in a system where the wifi worked for you would have been useful information.
Wifi extension will load all normally required dep's, your hardware's driver is provided within Kernel modules, all you should need in addition (in this case) is firmware which looks as if it's located within openfwwf otherwise use the b43fwcutter.
Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
-
It's really not that difficult we're not trying to confuse you. Broadcom has been slow in providing any Linux support for their hardware. As a result the available options may sound a little confusing, though with each of these combinations it's a case of either one or the other not both/all.
There are distro's which provide a means to download and install the required proprietary firmware for you, but the end user has to initiate this.
Noting which driver and firmware is used in a system where the wifi worked for you would have been useful information.
Wifi extension will load all normally required dep's, your hardware's driver is provided within Kernel modules, all you should need in addition (in this case) is firmware which looks as if it's located within openfwwf otherwise use the b43fwcutter.
Dear coreplayer2:
We both arrived at the same conclusion!
Forget about TCP 5.1 wireless/firmware original settings and only install two extensions:
1) wifi.tcz
2) firmware-openfwwf.tcz
Two thumb drive TCP installs have been cooked in the process and must start over with a fresh install w/o its WLAN original settings. Thread indicated b43-fwcutter.tcz is flawed.
Thanks for replying to my post.
Sincerely,
eltone.
-
WLAN BCM4318 has incorrect firmware!
eltone
b43/ucode5.fw is in the cut firmware, did you cut it/load it before you loaded the wireless-KERNEL extension (which would load the b43 module, which expects to find the firmware when it is loaded)?
-
Thread indicated b43-fwcutter.tcz is flawed.
I don't think so, but the firmware probably needs to be installed before the b43 module (contained in the wireless-KERNEL extension) is loaded.
-
Thread indicated b43-fwcutter.tcz is flawed.
I don't think so, but the firmware probably needs to be installed before the b43 module (contained in the wireless-KERNEL extension) is loaded.
hi,
Please translate, so a digital analyzer is not required.
Everything is installed at the factory (original factory settings). The end-user's job is to cut/install firmware. No-wonder it fails.
eltone
-
check wireless is enabled in bios and any hardware wireless switch is set to "on"
reboot your machine without any firmware or wireless extensions loaded
cut and install the b43 firmware as detailed above
load the wireless-KERNEL extension
paste the results of "dmesg | tail -20" or similar
-
check wireless is enabled in bios and any hardware wireless switch is set to "on"
reboot your machine without any firmware or wireless extensions loaded
cut and install the b43 firmware as detailed above
load the wireless-KERNEL extension
paste the results of "dmesg | tail -20" or similar
hi,
paste data:
tc@box:~$ dmesg | tail -20
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
usb 2-3.3: new full-speed USB device number 3 using ohci_hcd
input: ImPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8
usb 2-3.4: new full-speed USB device number 4 using ohci_hcd
loop: module loaded
Adding 250072k swap on /dev/zram0. Priority:-1 extents:1 across:250072k SS
usb 4-1: new low-speed USB device number 2 using ohci_hcd
squashfs: version 4.0 (2009/01/31) Phillip Lougher
input: Kensington Kensington USB Wireless Mouse as /devices/pci0000:00/0000:00:14.4/0000:06:04.0/0000:07:00.0/usb4/4-1/4-1:1.0/input/input9
hid-generic 0003:047D:1039.0001: input,hidraw0: USB HID v1.00 Mouse [Kensington Kensington USB Wireless Mouse] on usb-0000:07:00.0-1/input0
Adding 1023996k swap on /dev/sdb2. Priority:-2 extents:1 across:1023996k
microcode: AMD CPU family 0xf not supported
8139too 0000:06:06.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
tc@box:~$
The balls in your court . . .
eltone
-
check wireless is enabled in bios and any hardware wireless switch is set to "on"
reboot your machine without any firmware or wireless extensions loaded
cut and install the b43 firmware as detailed above
load the wireless-KERNEL extension
paste the results of "dmesg | tail -20" or similar
Dear Juanito:
I had important business interrupt solving this problem, so machine was shut down following previous post.
Now, paste data following reboot:
tc@box:~$ dmesg
mitc@box:~$ crocode: AMD CPU family 0xf not supported
8139too 0000:06:06.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
tc@box:~$
The cut/install firmware step appears transient.
Q: How can all this be made persistant, so it eliminates manual setup following every reboot?
Sincerely,
eltone
-
You need to make an extension out of it or add the b43 directory to your /opt/.filetool.lst and do a backup.
-
You need to make an extension out of it or add the b43 directory to your /opt/.filetool.lst and do a backup.
hi,
Followed #28 recipe that resulted in the following wifi dialog:
wlan0 interface doesn't support scanning
This dialog then vanishes! It is much too early to consider another b43 extension/backup, etc. Wifi previously controlled the hardware LED and suspect missing dependencies remain.
eltone
root@box:~# lsmod
Module Size Used by Not tainted
b43 278528 0
mac80211 155648 1 b43
bcma 24576 1 b43
cfg80211 110592 2 b43,mac80211
ntfs 73728 3
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
squashfs 24576 89
loop 20480 178
hp_wmi 12288 0
sparse_keymap 12288 1 hp_wmi
powernow_k8 16384 0
sdhci_pci 12288 0
pcspkr 12288 0
sdhci 24576 1 sdhci_pci
8139cp 20480 0
mmc_core 53248 1 sdhci
tifm_7xx1 12288 0
video 16384 0
ssb 36864 1 b43
8139too 20480 0
tifm_core 12288 1 tifm_7xx1
backlight 12288 1 video
ac 12288 0
battery 16384 0
wmi 12288 1 hp_wmi
root@box:~#
-
wlan0 interface doesn't support scanning
I usually see something like this when the wifi hardware switch on my laptop is set "off".
I copied the rfkill extension to the 5.x repo, could you check that you get something like this: $ rfkill list wifi
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no
Wifi previously controlled the hardware LED and suspect missing dependencies remain
I no longer have hardware that uses b43, but using my laptop with both ndiswrapper and wl-modules-KERNEL, the hardware LED comes on when the driver is loaded.
-
hi,
For comparison, I just loaded the TCP 5.1 LiveUSB onto my vintage 1998 hp desktop, w/256MB RAM:
root@box:~# ndiswrapper -i /mnt/sdb1/drivers/wxptpl/net8185.inf
installing net8185 ...
root@box:~# modprobe ndiswrapper
root@box:~# iwlist scan
ip_vti0 Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Network is down
dummy0 Interface doesn't support scanning.
lo Interface doesn't support scanning.
tunl0 Interface doesn't support scanning.
root@box:~# dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 3.8.13-tinycore (tc@box) (gcc version 4.7.2 (GCC) ) #2511 SMP Fri Oct 18 14:41:31 UTC 2013
microcode: CPU0 sig=0x665, pf=0x10, revision=0x1
Adding 58188k swap on /dev/zram0. Priority:-1 extents:1 across:58188k SS
squashfs: version 4.0 (2009/01/31) Phillip Lougher
ppdev: user-space parallel port driver
microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter O ruba
Adding 1023996k swap on /dev/sdb2. Priority:-2 extents:1 across:1023996k
cfg80211: Calling CRDA to update world regulatory domain
rtl8180 0000:00:0a.0: enabling device (0014 -> 0017)
ieee80211 phy0: Selected rate control algorithm 'pid'
ieee80211 phy0: hwaddr 002719dac50f, RTL8185vD + rtl8225z2
Disabling lock debugging due to kernel taint
ndiswrapper version 1.58 loaded (smp=yes, preempt=no)
usbcore: registered new interface driver ndiswrapper
root@box:~# ndiswrapper
The WLAN chipset is RTL8185L, mdl # TL-WN353G, PCI adapter w/NO hardware switch.
The same error is trapped on this machine:
wlan0 Interface doesn't support scanning : Network is down
Suspect bug in scan lib . . .
eltone
-
maybe we could stick to the bcm4318 :)
What does rfkill show after cutting/installing the broadcom firmware and loading the wireless-KERNEL extension?
-
wlan0 interface doesn't support scanning
I usually see something like this when the wifi hardware switch on my laptop is set "off".
I copied the rfkill extension to the 5.x repo, could you check that you get something like this:
Hey Juanito!
Just did an extension update and found NO rfkill.tcz
Q: Where did you copy rfkill to?
eltone
-
maybe it didn't propagate to all of the mirrors yet:
http://repo.tinycorelinux.net/5.x/x86/tcz/rfkill.tcz
-
wlan0 interface doesn't support scanning
I usually see something like this when the wifi hardware switch on my laptop is set "off".
I copied the rfkill extension to the 5.x repo, could you check that you get something like this: $ rfkill list wifi
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no
BCM4318:
tc@box:~$ rfkill list wifi
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
tc@box:~$
-
Ah-ha so your wifi is blocked in software somehow - is it enabled in bios?
Could you try something like: $ sudo rfkill unblock wifi..and see if that helps
-
Ah-ha so your wifi is blocked in software somehow - is it enabled in bios?
Could you try something like: $ sudo rfkill unblock wifi..and see if that helps
Juanito,
BIOS is correct and:
sudo rfkill unblock wifi
did get wifi to display expected cells, BUT failed to connect to my_network using my 10 digit WEP key! WPA_Supplicant is NEW territory for me.
Thanks
eltone
-
WPA_Supplicant is for WPA.
iwconfig is for WEP.
http://wiki.tinycorelinux.net/wiki:setting_up_wifi
-
WPA_Supplicant is for WPA.
iwconfig is for WEP.
http://wiki.tinycorelinux.net/wiki:setting_up_wifi
hi,
I'd prefer using wicd.tcz that functioned w/TCP 4.73, but it has not been 5.1 recompiled.
wifi.tcz could then be removed, along with its deps.
eltone
* NO bloat *
-
You could test wicd in tc-5.x and let us know if it works..
-
You could test wicd in tc-5.x and let us know if it works..
Dear Juanito:
My fifteen minutes of TCP 5.1 fame surfaced enough ammo for your support team to address:
1) rfkill
2) cutting/installing firmware w/persistance
3) connecting to a ten digit WEP cell
Once the WLAN framework is stable, I'd be happy to do further beta . . .
Connecting to the WEP cell, using extensions mentioned in thread, should be a piece-of-cake:
tc@box:~$ dmesg
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
8139too 0000:06:06.0 eth0: link down
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0: Radio hardware status changed to DISABLED
b43-phy0: Radio turned on by software
b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
b43-phy0: Radio hardware status changed to ENABLED
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
tc@box:~$
I'm stumped!
Thanks for replying to my post,
eltone
PS. I design hardware and am not a 'nix programmer
-
b43-fwcutter updated to the latest version.
To cut your own firmware: $ 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
hi,
TCP 4.73 LiveUSB trapped this error while attempting to cut firmware, using the 5.1 protocol:
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
:
-
tc-4.x uses an earlier version of the firmware cutter, maybe this is the reason for the error?
-
Once the WLAN framework is stable, I'd be happy to do further beta . . .
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.
-
I suggest you make an extension of the cut firmware
Dear Juanito:
Better yet, have your TCP 5.1 team recompile this extension:
http://repo.tinycorelinux.net/4.x/x86/tcz/b43-tools.tcz (http://repo.tinycorelinux.net/4.x/x86/tcz/b43-tools.tcz)
Once completed, I hope it's all down-hill \
\.
eltone
-
You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?
-
You would need to pm the maintainer and request an update, but I'm not sure how this extension is going to help?
Juanito,
Extension's complete, cutter, firmware & installer:
Title: b43-tools.tcz
Description: Tools for the Broadcom 43xx series WLAN chip.
Version: 20110514
Author: Michael Buesch and others
Original-site: bu3sch.de/gitweb?p=b43-tools.git;a=summary
Copying-policy: GPL2
Size: 76K
Extension_by: Jason W
Tags: Tools Broadcom 43xx series WLAN chip.
Comments: This extension is PPI compatible.
This extension also contains b43-fwcutter that is also
in the b43-fwcutter.tcz extension.
Change-log: --------
Current: 2011/05/14 First version 20110514
Enough said.
eltone
-
The version of b43-fwcutter in this extension is out of date and superseded by the latest version in the 5.x repo.
The rest of the tools in this extension seem to be (I may be mistaken) intended for developers to aid in reverse engineering and related tasks.
-
author=Juanito link=topic=16474.msg98195#msg98195 date=1389670198]
You could test wicd in tc-5.x and let us know if it works..
hi,
Trace w/wicd on TCP 4.73 at the point where 5.1 fails access point connection:
tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-32 (1 cpu cores) (ve rsion 2.20.00)
powernow-k8: fid 0xa (1800 MHz), vid 0x4
powernow-k8: fid 0x8 (1600 MHz), vid 0x6
powernow-k8: fid 0x0 (800 MHz), vid 0x16
8139too 0000:06:06.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
8139too 0000:06:06.0: eth0: link down
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
tc@box:~$
Files that were altered by wicd setup, please confirm accuracy:
/opt/.filetool.lst:
opt
home
opt/eth0.sh
usr/local/etc/wicd
var/lib/wicd/configurations
/opt/bootlocal.sh:
#!/bin/sh
# put other system startup commands here
/opt/eth0.sh &
/usr/local/etc/init.d/dbus restart
/usr/local/etc/init.d/wicd start
/mnt/sdb1/tce/onboot.lst:
Xvesa.tcz
Xlibs.tcz
Xprogs.tcz
wbar.tcz
fluxbox.tcz
wifi.tcz
iw.tcz
pci-utils.tcz
ndiswrapper.tcz
firmware.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwlwifi.tcz
firmware-libertas.tcz
firmware-openfwwf.tcz
firmware-wimax.tcz
firmware-zd1211.tcz
tc-install.tcz
b43-tools.tcz
wicd.tcz
Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points. The trick is to get them both to reliably connect to my WEP encrypted cell!
eltone
PS. Posted w/TCP 4.73 LiveUSB/wicd
-
Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.
Are you using rfkill to unblock your wifi hardware (ref "Soft blocked: yes")?
iw.tcz, ndiswrapper.tcz, firmware-ipw2100.tcz, firmware-ipw2200.tcz, firmware-iwlwifi.tcz, firmware-libertas.tcz, firmware-wimax.tcz, firmware-zd1211.tcz and b43-tools.tcz are not required "onboot"
As per "Hardware crypto acceleration not supported by firmware" from dmesg, you might be better off using the cut oem firmware rather than the firmware/firmware-openfwwf extensions.
The trick is to get them both to reliably connect to my WEP encrypted cell!
Did you try this from the command line rather than using wifi.sh/wicd?
Did you try wicd in tc-5.x?
-
I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:
$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
-
Whats interesting is that both wifi & wicd have NO problem enabling the hardware LED or finding neighborhood access points.
Are you using rfkill to unblock your wifi hardware (ref "Soft blocked: yes")?
hi,
This evening, to turn on the WLAN LED w/wicd, I tried 'rfkill unblock wifi' first, after wicd did not. Then I decided to click wifi in wbar, which got it to turn on and immediately closed wifi.
iw.tcz, ndiswrapper.tcz, firmware-ipw2100.tcz, firmware-ipw2200.tcz, firmware-iwlwifi.tcz, firmware-libertas.tcz, firmware-wimax.tcz, firmware-zd1211.tcz and b43-tools.tcz are not required "onboot"
Q: To remove this bloat, 'Apps > Maintenance > Dependencies And Deletions' is the one and only route to delete them?
As per "Hardware crypto acceleration not supported by firmware" from dmesg, you might be better off using the cut oem firmware rather than the firmware/firmware-openfwwf extensions.
I'm using TCP 4.73 LiveUSB, the b43 driver w/wicd to post this note. The original firmware install settings have not been altered and there is no need for b43-fwcutter, as prescribed for 5.1.
The trick is to get them both to reliably connect to my WEP encrypted cell!
Did you try this from the command line rather than using wifi.sh/wicd?
CLI has never been successful, only the wicd network-manager has!
Did you try wicd in tc-5.x?
It is not in the tc-5.1 repo, but tried 4.73's wicd in 5.1 that trapped MANY errors!
Todays dmesg showing a functional b43/wicd:
tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
ieee80211 phy0: Selected rate control algorithm 'pid'
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PMNL, Firmware-ID: FW13 ]
8139too 0000:06:06.0: eth0: link down
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
wlan0: deauthenticating from 00:21:1e:57:dc:60 by local choice (reason=3)
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 92:aa:9a:e9:10:81
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 5a:14:db:cc:d9:ae
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 7a:74:ca:f7:27:2e
b43-phy0: Loading OpenSource firmware version 410.31754
b43-phy0: Hardware crypto acceleration not supported by firmware
b43-phy0: QoS not supported by firmware
wlan0: authenticate with 00:21:1e:57:dc:60 (try 1)
wlan0: authenticated
wlan0: associate with 00:21:1e:57:dc:60 (try 1)
wlan0: RX AssocResp from 00:21:1e:57:dc:60 (capab=0x451 status=0 aid=1)
wlan0: associated
tc@box:~$
eltone
-
I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:
$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
Hey Juanito!
I think 'sudo modprobe -a b43' can replace the first two lines for 4.73.
Q: How would the 10 digit WEP key '6,7,8,9,a,b,c,d,e,f' be successfully entered in line four?
I will give this a try on the CLI once the syntax is clear in my head.
eltone
-
my troubleshooting suggestions assume that no firmware/wireless extensions are loaded on boot - I was also assuming that you were trying to get things working on tc-5.x
No, "sudo modprobe -a b43" cannot replace the first two lines - these two lines load the firmware for your hardware and then load the extension that contains the b43 module. Normally the b43 module should load automatically, but it would be good to check after "tce-load -i wireless_tools" that the b43 module is loaded and, if not, use "sudo modprobe b43" to load it.
I don't know how you would enter the WEP key '6,7,8,9,a,b,c,d,e,f' - maybe it would be a good idea to take a look at your wap browser admin page to see if there is a 26 digit code associated with it and, if so, use that.
It is not in the tc-5.1 repo, but tried 4.73's wicd in 5.1 that trapped MANY errors!
As suggested previously, please try the wicd extension from the 4.x repo with tc-5.x
-
I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me:
$ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
I will give this a try on the CLI once the syntax is clear . . .
hi,
This simple CLI indexing appeared to connect, once I made sure ssb and b43 got loaded:
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$
I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router. Also, the IP & dns address' looks syspicious.
When using wicd, static addresses are used. I have seen this anomaly with this particular dns address before and suspect that is the problem here.
eltone
-
Did you try wicd in tc-5.x?
hi,
Now that wicd.tcz has completed the burn-in phase on tc-4.73, it will be installed on tc-5.10 next go-around:
http://repo.tinycorelinux.net/4.x/x86/tcz/wicd.tcz (http://repo.tinycorelinux.net/4.x/x86/tcz/wicd.tcz)
Q: Shouldn't it be recompiled first?
eltone
-
I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router. Also, the IP & dns address' looks syspicious.
I get exactly that sort of output and everything works as expected: udhcpc (v1.21.1) started
Sending discover...
Sending select for 192.168.1.111...
Lease of 192.168.1.111 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.1.1
Now that wicd.tcz has completed the burn-in phase on tc-4.73, it will be installed on tc-5.10 next go-around:
...
Q: Shouldn't it be recompiled first?We'll know that once you've tested it :P
-
We'll know that once you've tested it :P
hi,
'wicd.tcz' was just dounloaded into 5.1's /mnt/sdb1/tce/optional directory.
Errors trapped:
root@box:~# wicd
/usr/local/sbin/wicd: exec: line 3: /usr/local/bin/python: not found
root@box:~# wicd
Traceback (most recent call last):
File "/usr/local/share/wicd/daemon/wicd-daemon.py", line 46, in <module>
import gobject
ImportError: No module named gobject
root@box:~#
Installed python to resolve line 2 glitch and the ImportError is up for grabs . . .
Dependencies are unclear, going this route.
eltone
-
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$
I had to launch the browser and note that the home page timed out, before learning this CLI indexing failed to connect to router.
Would you not have succeeded to connect to router in the first place, then you could never have gotten above output...
::)
Also, the IP & dns address' looks syspicious.
When using wicd, static addresses are used. I have seen this anomaly with this particular dns address before and suspect that is the problem here.
Looks like expected.
If you want a static address, then why exactly do you run udhcpc?
-
Installed python to resolve line 2 glitch and the ImportError is up for grabs . . .
Dependencies are unclear, going this route.
Dependencies are as per wicd.tcz.dep updated for tc-5.x, i.e.: pygtk.tcz
dbus-python.tcz
urwid.tcz
wpa_supplicant-dbus.tcz
dhcpcd.tcz
net-tools.tcz
ncurses-utils.tcz
shared-mime-info.tcz
hicolor-icon-theme.tcz
jlslegalise has just submitted an update for wpa_supplicant-dbus, take care that you do not have wpa_supplicant loaded at the same time as wpa_supplicant-dbus
Edit: wicd seems to work, copied to 5.x repo.
-
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
SIOCDELRT: No such process
adding dns 192.168.0.1
tc@box:~$
If you want a static address, then why exactly do you run udhcpc?
hi,
I'm sure the dns server address needs to be changed to surf the net.
On a similar problem distro, 'nameserver 192.168.0.1' was changed to 'nameserver 8.8.8.8' to fix!
CFG locaton:
/etc/resolv.conf
Q: How can the TCP nameserver assignment be altered?
eltone
-
Using the search function of this forum often reveals that questions have already been answered ;)
http://forum.tinycorelinux.net/index.php/topic,8019.0.html
-
I looked back to when I used to have broadcom wifi hardware that worked with b43 and a wap that used wep and this worked for me: $ tce-load -i b43_firmware [oem cut firmware]
$ tce-load -i wireless_tools
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
hi,
CLI BCM4318 indexing to scan/connect to cell using TCP 5.1 is at a stalemate:
[To cut your own firmware]
$ 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
[w/firmware installed, load b43 kernel module]
$ tce-load -i wireless-3.8.13-tinycore
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo rfkill unblock wifi
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
tc@box:~$
tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
8139too 0000:06:06.0 eth0: link down
Suspect bug in 'cut your own firmware', which wasn't needed w/TCP 4.73.
eltone
-
I've used the linux wireless b43 instructions from tc-1.x to tc-5.x without problems.
Up to you which firmware (cut or firmware-openfww) you'd like to use :)
-
Using the search function of this forum often reveals that questions have already been answered ;)
http://forum.tinycorelinux.net/index.php/topic,8019.0.html
Hey tinypoodle!
Followed links instructions, which states to backup:
Control Panel > Maintenance > Backup/Restore > (device:sdb1/tce) > Action:Backup > Go
I must plead ignorance using this Backup/Restore indexing, shouldn't it be done automatically?
Now this error is trapped in the 'backup_status' log, blocking a reboot/shutdown::
tar: removing leading '/' from member names
Q: How can a normal reboot/shutdown be restored?
CLI is the only way now.
eltone
-
I've used the linux wireless b43 instructions from tc-1.x to tc-5.x without problems.
Up to you which firmware (cut or firmware-openfww) you'd like to use :)
Dear Juanito:
Please post the CLI indexing w/firmware-openfww instead of :
[To cut your own firmware]
$ 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
[w/firmware installed, load b43 kernel module]
$ tce-load -i wireless-3.8.13-tinycore
[at this point you would need to load rfkill and use it to unblock your hardware]
$ sudo rfkill unblock wifi
$ sudo iwconfig wlan0 essid "342rju1656"
$ sudo iwconfig wlan0 key restricted 7D:3A:7C:72:F7:9A:6F:91:DF:CF:C9:AD:CE
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
THX!
eltone
-
Hi eltone
Now this error is trapped in the 'backup_status' log, blocking a reboot/shutdown::
Code: [Select]
tar: removing leading '/' from member names
You probably have one or more entries in your filetool.lst file that begin with a /
Lines in filetool.lst should not begin with a /
-
Hi eltone
Now this error is trapped in the 'backup_status' log, blocking a reboot/shutdown::
Code: [Select]
tar: removing leading '/' from member names
You probably have one or more entries in your filetool.lst file that begin with a /
Lines in filetool.lst should not begin with a /
hi,
Traced bug here:
http://forum.tinycorelinux.net/index.php/topic,8019.0.html
(http://forum.tinycorelinux.net/index.php/topic,8019.0.html)
eltone
-
Hi eltone
Now this error is trapped in the 'backup_status' log, blocking a reboot/shutdown::
Code: [Select]
tar: removing leading '/' from member names
You probably have one or more entries in your filetool.lst file that begin with a /
Lines in filetool.lst should not begin with a /
hi,
Traced bug here:
http://forum.tinycorelinux.net/index.php/topic,8019.0.html
(http://forum.tinycorelinux.net/index.php/topic,8019.0.html)
eltone
Uhmm, traced bug how exactly?
Could you please be more specific/detailed/factual?
???
-
Hi eltone
Now this error is trapped in the 'backup_status' log, blocking a reboot/shutdown::
Code: [Select]
tar: removing leading '/' from member names
You probably have one or more entries in your filetool.lst file that begin with a /
Lines in filetool.lst should not begin with a /
hi,
Traced bug here:
http://forum.tinycorelinux.net/index.php/topic,8019.0.html
(http://forum.tinycorelinux.net/index.php/topic,8019.0.html)
eltone
Uhmm, traced bug how exactly?
Could you please be more specific/detailed/factual?
???
hi,
contents of filetool.lst:
ACTUAL:
opt
home
opt/eth0.sh
/usr/share/udhcpc/default.script
EXPECTED:
opt
home
opt/eth0.sh
usr/share/udhcpc/default.script
Following the links dialog generated an extra forward slash that remains a MYSTERY of its origin!
eltone
-
That is not a bug. As usual, you did not properly follow the instructions.
-
Please copy and paste the command from forum to a terminal - verbatim et literatim - and then show the content of filetool.lst.
-
TCP 5.1 Team,
It appears that there's a bug unique to tc-5x on this hardware while cutting the BCM4318 firmware:
tc@box:~$ dmesg
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
------------[ cut here ]------------
WARNING: at drivers/net/wireless/b43/main.c:2574 0xf8566129()
Hardware name: Pavilion dv8000 (ET831UA#ABA)
Modules linked in: b43 mac80211 bcma cfg80211 cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace squashfs loop hp_wmi sparse_keymap powernow_k8 video backlight battery 8139cp ac sdhci_pci sdhci mmc_core wmi 8139too tifm_7xx1 tifm_core ssb pcspkr
Pid: 3864, comm: ifconfig Not tainted 3.8.13-tinycore #2511
Call Trace:
[<c012b5dd>] ? 0xc012b5dd
[<f8566129>] ? 0xf8566129
[<f8566129>] ? 0xf8566129
[<c012b60b>] ? 0xc012b60b
[<f8566129>] ? 0xf8566129
[<f856702e>] ? 0xf856702e
[<f84f0235>] ? 0xf84f0235
[<f84eeacb>] ? 0xf84eeacb
[<c0143bea>] ? 0xc0143bea
[<c0429b7f>] ? 0xc0429b7f
[<c0429af2>] ? 0xc0429af2
[<c0429d6b>] ? 0xc0429d6b
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c0429e3f>] ? 0xc0429e3f
[<c046dca0>] ? 0xc046dca0
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c014654c>] ? 0xc014654c
[<c041945b>] ? 0xc041945b
[<c0419283>] ? 0xc0419283
[<c01b67a0>] ? 0xc01b67a0
[<c01b7239>] ? 0xc01b7239
[<c012263e>] ? 0xc012263e
[<c01b72ac>] ? 0xc01b72ac
[<c04c63d8>] ? 0xc04c63d8
---[ end trace 0899dba7c56a2a0b ]---
b43-phy0: Loading firmware version 410.2160 (2015-15-255 15:32:10)
b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
net_ratelimit: 5 callbacks suppressed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
8139too 0000:06:06.0 eth0: link down
b43-phy0 ERROR: MAC suspend failed
usb 2-3.4: USB disconnect, device number 4
hub 2-3:1.0: unable to enumerate USB device on port 4
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
tc@box:~$
TCP 4.73 handled this function OK.
eltone
-
Please copy and paste the command from forum to a terminal - verbatim et literatim - and then show the content of filetool.lst.
Dear tinypoodle:
There are NO stupid questions, only answers. All forward slashes confirmed OK.
The subject of this thread needs to be addressed by the TCP 5.1 team. Adding TCP 4.73 to the mix adds a baseline functionality incentive for lowest common denominator resolution ASAP!
Sincerely,
eltone
~no offense
-
No, the forward slashes are NOT OK. You have included a leading slash NOT in the instructions.
Your repeated return to your previous mistakes after things have been demonstrated as working properly will ensure that you never
will have a functioning system.
-
Please copy and paste the command from forum to a terminal - verbatim et literatim - and then show the content of filetool.lst.
Dear tinypoodle:
There are NO stupid questions, only answers.
Well, often you seem not to provide accurate/specific answers to what is requested from you by all those trying to support you...
All forward slashes confirmed OK.
Not sure what to make out of this, I think the request (which you even quoted!) was as simple, specific and detailed as possible, you shout "bug" every somesuch, but are not really helping if you don't follow up with further investigation.
You have been pointed to the exact same "How to" more than one year ago, in a thread in where you had similar complaints and requests and claimed similar bugs as in this one, none of which has been proven to be a bug ever since.
http://forum.tinycorelinux.net/index.php/topic,14622.msg83308.html#msg83308
So, if you claim to have found a bug in a "How to" more than one year after you have been pointed to it, while in over 3 years none of the more than 4000 users having viewed the same have reported anything, you are not convincing at all when you are not following up and provide necessary evidence.
Generally speaking, bug reports about bugs which cannot be reliably reproduced most likely end up with status "Closed. Can not reproduce." - except in the rare case where there would be indications of a heisenbug.
The subject of this thread needs to be addressed by the TCP 5.1 team. Adding TCP 4.73 to the mix adds a baseline functionality incentive for lowest common denominator resolution ASAP!
This sentence leaves me puzzled, not understanding what any of it could possibly mean...
???
-
No, the forward slashes are NOT OK. You have included a leading slash NOT in the instructions.
Your repeated return to your previous mistakes after things have been demonstrated as working properly will ensure that you never
will have a functioning system.
hi,
WLAN on TCP 5.1 has never functioned properly on this hardware, only TCP 4.73/wicd has, as w/other distros.
e.g., Slackware 14.0, Porteus-XFCE 2.0
eltone
-
1. There is nothing specific to "WLAN on TCP 5.1" in what you quoted gerald_clark, but it's entirely specific to 'tar', i.e. how to add files to Core's backup in general.
2. Testing a specific piece of hardware with different distros could only provide for anecdotal evidence.
My anecdotal evidence with testing a specific wireless radio with dozens of distros over a timespan of many years has shown that it would only ever work out of the box under CorePlus and Slackware 9.0, while OTOH it took me 2 hours of fiddling under Ubuntu and I gave up after a few days of trying with Backtrack (oh the irony!).
-
Maybe it's time to re-state what you'd like to achieve.
I understand you'd like to get wifi working with your bcm-4318 hardware using an installed x86 tc-5.x, but is your aim to have it working from the cli, with the wifi extension or with the wcid extension?
In addition, do you wish it to work with freely available firmware or with the broadcom firmware as described in linux wireless b43?
-
Maybe it's time to re-state what you'd like to achieve.
I understand you'd like to get wifi working with your bcm-4318 hardware using an installed x86 tc-5.x, but is your aim to have it working from the cli, with the wifi extension or with the wcid extension?
Dear Juanito:
No bloat means CLI. I have NO faith in wifi extension w/WEP and wicd extension has too much bloat to pursue any 5.1 usage. You enlightened me on this WLAN CLI indexing avenue that thread feedback shows optimism. Also, going with a frugal install to thumb drive w/no wifi/firmware installation. Just add the essentials one by one.
In addition, do you wish it to work with freely available firmware or with the broadcom firmware as described in linux wireless b43?
Hindsight is twenty-twenty, so whatever was used successfully w/TCP 4.73, I'm for, where b43-fwcutter was ignored.
Sincerely,
eltone
-
So:
* boot tc-5.x with no firmware/wireless extensions "onboot" and no wireless modules blacklisted.
* load firmware-openfwwf extension
* load wireless-KERNEL extension
* check dmesg to see if b43 module has loaded and found the firmware it requires
paste relevant dmesg output here
-
So:
* boot tc-5.x with no firmware/wireless extensions "onboot" and no wireless modules blacklisted.
* load firmware-openfwwf extension
* load wireless-KERNEL extension
* check dmesg to see if b43 module has loaded and found the firmware it requires
paste relevant dmesg output here
tc@box:~$ sudo lsmod
Module Size Used by Not tainted
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
squashfs 24576 58
loop 20480 116
hp_wmi 12288 0
sparse_keymap 12288 1 hp_wmi
powernow_k8 16384 0
video 16384 0
pcspkr 12288 0
backlight 12288 1 video
battery 16384 0
sdhci_pci 12288 0
sdhci 24576 1 sdhci_pci
ac 12288 0
mmc_core 53248 1 sdhci
8139cp 20480 0
ssb 36864 0
tifm_7xx1 12288 0
tifm_core 12288 1 tifm_7xx1
8139too 20480 0
wmi 12288 1 hp_wmi
tc@box:~$ tce-load -i firmware-openfwwf
/etc/sysconfig/tcedir/optional/firmware-openfwwf.tcz: OK
tc@box:~$ tce-load -i wireless-3.8.13-tinycore
/etc/sysconfig/tcedir/optional/wireless-3.8.13-tinycore.tcz: OK
tc@box:~$ sudo lsmod
Module Size Used by Not tainted
b43 278528 0
mac80211 155648 1 b43
bcma 24576 1 b43
cfg80211 110592 2 b43,mac80211
cpufreq_stats 12288 0
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
squashfs 24576 60
loop 20480 120
hp_wmi 12288 0
sparse_keymap 12288 1 hp_wmi
powernow_k8 16384 0
video 16384 0
pcspkr 12288 0
backlight 12288 1 video
battery 16384 0
sdhci_pci 12288 0
sdhci 24576 1 sdhci_pci
ac 12288 0
mmc_core 53248 1 sdhci
8139cp 20480 0
ssb 36864 1 b43
tifm_7xx1 12288 0
tifm_core 12288 1 tifm_7xx1
8139too 20480 0
wmi 12288 1 hp_wmi
tc@box:~$ dmesg | tail -33
sdb: sdb1 sdb2 sdb3 sdb4
sd 2:0:0:0: [sdb] No Caching mode page present
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
excluding 0x870-0x87f
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
excluding 0xc00-0xc07 0xc10-0xc17 0xc50-0xc57 0xc68-0xc6f 0xcd0-0xcdf
pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
excluding 0xc0000-0xfffff
pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
clean.
pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
clean.
loop: module loaded
Adding 250300k swap on /dev/zram0. Priority:-1 extents:1 across:250300k SS
usb 2-3.3: new full-speed USB device number 3 using ohci_hcd
squashfs: version 4.0 (2009/01/31) Phillip Lougher
input: ImPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8
usb 2-3.4: new full-speed USB device number 4 using ohci_hcd
usb 4-1: new low-speed USB device number 2 using ohci_hcd
Adding 262140k swap on /dev/sdb4. Priority:-2 extents:1 across:262140k
input: Kensington Kensington USB Wireless Mouse as /devices/pci0000:00/0000:00:14.4/0000:06:04.0/0000:07:00.0/usb4/4-1/4-1:1.0/input/input9
hid-generic 0003:047D:1039.0001: input,hidraw0: USB HID v1.00 Mouse [Kensington Kensington USB Wireless Mouse] on usb-0000:07:00.0-1/input0
EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
8139too 0000:06:06.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
microcode: AMD CPU family 0xf not supported
cfg80211: Calling CRDA to update world regulatory domain
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
b43-phy0: Found PHY: Analog 3, Type 2 (G), Revision 7
Broadcom 43xx driver loaded [ Features: PMNL ]
ieee80211 phy0: Selected rate control algorithm 'pid'
tc@box:~$
HTH
eltone
-
OK, that looks OK (except I might have expected to see "wlan0 somewhere), now I guess you can try:
$ sudo iwconfig wlan0 essid "eltonenetwork"
$ sudo iwconfig wlan0 key 6789abcdef
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
BTW, "lsmod" is OK, "sudo lsmod" is not required.
-
OK, that looks OK (except I might have expected to see "wlan0 somewhere), now I guess you can try: $ sudo iwconfig wlan0 essid "eltonenetwork"
$ sudo iwconfig wlan0 key 6789abcdef
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
BTW, "lsmod" is OK, "sudo lsmod" is not required.
hi,
CLI line one is missing a component:
tc@box:~$ tce-load -i firmware-openfwwf
/etc/sysconfig/tcedir/optional/firmware-openfwwf.tcz: OK
tc@box:~$ tce-load -i wireless-3.8.13-tinycore
/etc/sysconfig/tcedir/optional/wireless-3.8.13-tinycore.tcz: OK
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
sudo: iwconfig: command not found
tc@box:~$
Suspect there's a better firmware choice w/missing component.
eltone
-
tce-load -i wireless_tools.tcz
-
tce-load -i wireless_tools.tcz
hi,
'b43' firmware remains NON-functional:
tc@box:~$ tce-load -i firmware-openfwwf
/etc/sysconfig/tcedir/optional/firmware-openfwwf.tcz: OK
tc@box:~$ tce-load -i wireless_tools
wireless-3.8.13-tinycore.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
tc@box:~$ dmesg | tail -33
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c0429e3f>] ? 0xc0429e3f
[<c046dca0>] ? 0xc046dca0
[<c04263d2>] ? 0xc04263d2
[<c01b1ed2>] ? 0xc01b1ed2
[<c014654c>] ? 0xc014654c
[<c041945b>] ? 0xc041945b
[<c0419283>] ? 0xc0419283
[<c01b67a0>] ? 0xc01b67a0
[<c01b7239>] ? 0xc01b7239
[<c012263e>] ? 0xc012263e
[<c01b72ac>] ? 0xc01b72ac
[<c04c63d8>] ? 0xc04c63d8
---[ end trace 470a5bf9db3a765a ]---
b43-phy0: Loading firmware version 410.2160 (2015-15-255 15:32:10)
b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
net_ratelimit: 5 callbacks suppressed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
b43-phy0 ERROR: MAC suspend failed
tc@box:~$
WLAN LED does get enabled is about all.
Q: Any fresh ideas?
eltone
-
1. Nothing can be said about that trace without seeing the preceding lines.
2. I suggest you add boot code syslog and then post or attach /var/log/messages
3. There is no sense in running udhcpc without first being associated with AP which could be checked e.g. with
iwconfig
-
1. Nothing can be said about that trace without seeing the preceding lines.
2. I suggest you add boot code syslog and then post or attach /var/log/messages
syslog attached . . .
eltone
-
3. There is no sense in running udhcpc without first being associated with AP which could be checked e.g. with
iwconfig
iwconfig:
tc@box:~$ tce-load -i firmware-openfwwf
/etc/sysconfig/tcedir/optional/firmware-openfwwf.tcz: OK
tc@box:~$ tce-load -i wireless_tools
wireless-3.8.13-tinycore.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
tc@box:~$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~$ sudo iwconfig
ip_vti0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"eltonenetwork"
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:6789-abcd-ef
Power Management:on
dummy0 no wireless extensions.
lo no wireless extensions.
eth0 no wireless extensions.
tunl0 no wireless extensions.
tc@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
tc@box:~$
eltone
-
syslog attached . . .
It appears like the kernel spits out a warning and call trace when udhcpc is executed while expected firmware is missing.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
If I were you I would try to pursue the path of above instructions.
-
Access Point: Not-Associated
Exactly what I meant ;)
Tx-Power=0 dBm
That looks wrong, possibly caused by missing firmware.
-
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
If I were you I would try to pursue the path of above instructions.
Hey tinypoodle!
Those instructions have nothing etched-in-stone for TCP 5.1.
Dry run:
$ 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
$ tce-load -i b43-fwcutter
$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o
No firmware cutting was required w/TCP 4.73. 'b43-tools' had a script to install it automatically.
eltone
-
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: No "pcm5.fw" firmware file found. Hardware accelerated cryptography is disabled.
Jan 22 15:49:41 box user.warn kernel: b43-phy0 warning: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
If I were you I would try to pursue the path of above instructions.
Dear TCP 5.x Team:
WLAN is functional:
[ctc@box:~/b43fw$ sudo mkdir -p /usr/local/lib/firmware
tc@box:~/b43fw$ tce-load -i b43-fwcutter
/etc/sysconfig/tcedir/optional/b43-fwcutter.tcz: OK
tc@box:~/b43fw$ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.1
This file is recognised as:
filename : wl_apsta.o
version : 666.2
MD5 : e1b05e268bcdbfef3560c28fc161f30e
Extracting b43/lp0initvals14.fw
Extracting b43/lcn0bsinitvals25.fw
Extracting b43/n0bsinitvals25.fw
Extracting b43/n0bsinitvals17.fw
Extracting b43/ucode17_mimo.fw
Extracting b43/ucode16_lp.fw
Extracting b43/sslpn1initvals27.fw
Extracting b43/lp2bsinitvals19.fw
Extracting b43/sslpn3bsinitvals21.fw
Extracting b43/ucode16_sslpn.fw
ucode time: 01:15:07
Extracting b43/ucode25_lcn.fw
Extracting b43/ucode21_sslpn.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/ucode20_sslpn.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/lp1initvals20.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp2initvals19.fw
Extracting b43/n2bsinitvals19.fw
Extracting b43/sslpn4bsinitvals22.fw
Extracting b43/ucode16_sslpn_nobt.fw
ucode date: 2011-02-23
Extracting b43/n1bsinitvals20.fw
Extracting b43/n1initvals20.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/ucode22_sslpn.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/ht0initvals26.fw
Extracting b43/ucode33_lcn40.fw
Extracting b43/sslpn1bsinitvals20.fw
Extracting b43/lcn400bsinitvals33.fw
Extracting b43/ucode14.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/lp1bsinitvals22.fw
Extracting b43/n16initvals30.fw
Extracting b43/lp0bsinitvals16.fw
Extracting b43/lcn1bsinitvals25.fw
Extracting b43/lcn400initvals33.fw
Extracting b43/n0bsinitvals24.fw
Extracting b43/lcn2bsinitvals26.fw
Extracting b43/lcn1initvals26.fw
Extracting b43/n0bsinitvals22.fw
Extracting b43/n18initvals32.fw
Extracting b43/lcn2initvals26.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/lcn2initvals24.fw
Extracting b43/lcn0initvals26.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/ucode21_sslpn_nobt.fw
ucode time: 01:15:07
Extracting b43/ucode26_mimo.fw
Extracting b43/n2initvals19.fw
Extracting b43/sslpn3initvals21.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/sslpn4initvals22.fw
Extracting b43/pcm5.fw
Extracting b43/ucode22_mimo.fw
Extracting b43/ucode9.fw
Extracting b43/lcn2initvals25.fw
Extracting b43/lp1initvals22.fw
Extracting b43/sslpn1bsinitvals27.fw
Extracting b43/lcn0initvals24.fw
Extracting b43/ucode32_mimo.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/n18bsinitvals32.fw
Extracting b43/n0initvals24.fw
Extracting b43/n0initvals25.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/ucode24_lcn.fw
Extracting b43/n0initvals17.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/lp0initvals15.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/ucode20_sslpn_nobt.fw
Extracting b43/lcn1initvals24.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp1bsinitvals20.fw
Extracting b43/sslpn2initvals19.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/lcn1bsinitvals24.fw
Extracting b43/ucode5.fw
Extracting b43/lcn2bsinitvals24.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/n0initvals16.fw
Extracting b43/ucode19_sslpn_nobt.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/ucode11.fw
Extracting b43/lp0initvals16.fw
Extracting b43/ucode16_mimo.fw
Extracting b43/lcn0bsinitvals26.fw
Extracting b43/ht0initvals29.fw
Extracting b43/lcn2bsinitvals25.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode29_mimo.fw
Extracting b43/lcn0bsinitvals24.fw
Extracting b43/ucode19_sslpn.fw
Extracting b43/lcn1initvals25.fw
Extracting b43/ucode30_mimo.fw
Extracting b43/n16bsinitvals30.fw
Extracting b43/ucode25_mimo.fw
Extracting b43/ucode24_mimo.fw
Extracting b43/ucode27_sslpn.fw
Extracting b43/lp0initvals13.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/ht0bsinitvals26.fw
Extracting b43/ucode13.fw
Extracting b43/sslpn2bsinitvals19.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/n0initvals11.fw
Extracting b43/lcn0initvals25.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/sslpn1initvals20.fw
Extracting b43/lcn1bsinitvals26.fw
Extracting b43/n0initvals22.fw
Extracting b43/ht0bsinitvals29.fw
tc@box:~/b43fw$ tce-load -i wireless_tools
wireless-3.8.13-tinycore.tcz: OK
libiw.tcz: OK
wireless_tools.tcz: OK
tc@box:~/b43fw$ sudo iwconfig wlan0 essid "eltonenetwork"
tc@box:~/b43fw$ sudo iwconfig wlan0 key 6789abcdef
tc@box:~/b43fw$ sudo iwconfig
ip_vti0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"eltonenetwork"
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:6789-abcd-ef
Power Management:on
dummy0 no wireless extensions.
lo no wireless extensions.
eth0 no wireless extensions.
tunl0 no wireless extensions.
tc@box:~/b43fw$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending select for 135.79a.0.ce...
Lease of 135.79a.0.ce obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 123.456.7.89
adding dns 8.8.4.4
adding dns 987.654.3.21
adding dns 8.8.8.8
tc@box:~/b43fw$ode]
Please note:
Tx-Power=0 dBm
Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?
Thanks,
eltone
PS. First post using TCP 5.1 LiveUSB w/WLAN b43
-
PHEW!!
;D
Does Tx-Power still after 0 dBm after connection has become fully functional?
Also, are you sure you want 4 DNS resolver entries?
-
Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?
Thanks,
eltone
I answered that back on page 3.
-
Does Tx-Power still after 0 dBm after connection has become fully functional?
Also, are you sure you want 4 DNS resolver entries?
tinypoodle,
WLAN burn-in appears more stable than the hard wired ethernet connection!
If it works, don't fix it, but why question the DNS?
tc@box:~$ sudo iwconfig
ip_vti0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"eltonenetwork"
Mode:Managed Frequency:2.427 GHz Access Point: 00:21:1E:57:DC:60
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:6789-abcd-ef
Power Management:off
Link Quality=70/70 Signal level=-38 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:10 Invalid misc:139 Missed beacon:0
dummy0 no wireless extensions.
lo no wireless extensions.
eth0 no wireless extensions.
tunl0 no wireless extensions.
tc@box:~$
eltone
-
Q: How can firmware cutting/installing survive reboot, so it's a one-shot setup?
I sent you a pm offering to help with this about 10 days ago :P
-
Now that looks all perfect, I would guess the interface was not up before you ran udhcpc, making for the difference in output.
Such a DNS mix is just not very common, but if that's how you want it and are aware of the potential consequences, ok.
-
YAY!!! :P
I gotta say, those DNS server addresses are weird..
-
Now that wicd.tcz has completed the burn-in phase on tc-4.73, it will be installed on tc-5.10 next go-around:
...
Q: Shouldn't it be recompiled first?We'll know that once you've tested it :P
hi,
wicd tested OK on TCP 5.1 today. The only problem was that the firmware has to be reinstalled following each boot!
Apparently the driver gets loaded before the firmware folder is restored during the boot phase.
FILETOOL.LST:
opt
home
usr/share/udhcpc/default.script
usr/local/lib/firmware/b43
opt/wlan0.sh
usr/local/etc/wicd
var/lib/wicd/configurations
opt/eth0.sh
BOOTLOCAL.SH:
#!/bin/sh
# put other system startup commands here
/opt/wlan0.sh &
/usr/local/etc/init.d/dbus restart
/usr/local/etc/init.d/wicd start
/opt/eth0.sh &
ONBOOT.LST:
Xlibs.tcz
Xprogs.tcz
Xvesa.tcz
aterm.tcz
fltk-1.1.10.tcz
flwm_topside.tcz
freetype.tcz
imlib2.tcz
libICE.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz
libXrender.tcz
libXt.tcz
libfontenc.tcz
libjpeg-turbo.tcz
libpng.tcz
libxcb.tcz
libXft.tcz
libXinerama.tcz
libXcursor.tcz
liblzma.tcz
libffi.tcz
gdk-pixbuf2.tcz
libtiff.tcz
glib2.tcz
imlib2-bin.tcz
wbar.tcz
fluxbox.tcz
wicd.tcz
Q: How can the b43 driver get loaded after the firmware gets restored during boot?
eltone
-
Remember that extension deps are recursive, there is no need to have most of those extensions named in onboot.lst
It would be better to make a personal extension out of a large amount of static data like the b43 firmware rather than making it part of your backup.
Once you've made a personal extension out of the b43 firmware, you can place it before wicd in onboot.lst
-
hi,
'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros. Please help.
sudo udhcpc -S -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
The '-S' switch was enabled to ammend attached syslog . . .
Excellent CLI Network Configuration Article:
http://ubuntuforums.org/showthread.php?t=684495 (http://ubuntuforums.org/showthread.php?t=684495)
THX4HLP!
eltone
* udhcpclg.txt FAILED
udhcpcl2.txt PASSED
-
It would be better to make a personal extension out of a large amount of static data like the b43 firmware rather than making it part of your backup.
Once you've made a personal extension out of the b43 firmware, you can place it before wicd in onboot.lst
tc-5.x Guru's,
I have researched HOW2 make a personal extension for someone that's cutting-their-teeth w/tc-5.1 and find nothing but outdated material. Any help from those that have done this before?
I hate to reinvent the . . .
eltone
-
Hi eltone
This doesn't look outdated to me:
http://wiki.tinycorelinux.net/wiki:extension_for_settings
-
The wiki is a great place to learn and source of reference..
Meanwhile, try creating your extension in /tmp
For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz
start by creating your directory structure, at the command line
mkdir -p /tmp/pkg/usr/local/lib/firmware/b43cut
mkdir -p /tmp/pkg/usr/local/tce.installed
create a file (in this case a udevadm trigger)
touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut
open file "/tmp/pkg/usr/local/tce.installed/firmware-b43cut" and enter on the first two lines
the following, then save it
#!/bin/sh
udevadm trigger
copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/
set permissions (note the own/perm. of tce.installed)
sudo chmod 644 /tmp/pkg/usr/local/lib/firmware/b43cut/b43cut.img
sudo chown -R root:root /tmp/pkg/usr
sudo chown -R root:staff /tmp/pkg/usr/local/tce.installed
sudo chmod -R 775 /tmp/pkg/usr/local/tce.installed
Now you're ready to squash it
cd /tmp
tce-load -i squashfs-tools-4.x.tcz && mksquashfs pkg/ firmware-b43cut.tcz
then copy the new extension to tce/optional dir, load it
tc@box:/$ tce-load -i firmware-b43cut.tcz
firmware-b43cut.tcz: OK
and test it
see also http://wiki.tinycorelinux.net/wiki:creating_extensions (http://wiki.tinycorelinux.net/wiki:creating_extensions)
-
'udhcpc' passed burn-in on PC #2, BUT now is NON-functional, just like what was reported earlier!
This malfunction does NOT occur on other distros. Please help.
Hundreds of tinycore users are using udhcpc every day without problems - the problem is not with udhcpc, but with what comes before the the udhcpc command. Several users, myself included, have tried to help, but you need to follow what is suggested in the order it is suggested for things to work.
I sent you a pm two or three weeks ago offering to make a firmware extension for you, but (so far) you've ignored it.
Again, the order to do things is:
1. Load firmware
2. Load wireless module
3. Associate with wap
4. Run udhcpc
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
-
Again, the order to do things is:
1. Load firmware
2. Load wireless module
3. Associate with wap
4. Run udhcpc
hi,
Your instructions have been followed at the CLI level:
I. To cut/install your own firmware:
a) $ sudo mkdir -p /home/tc/b43fw
b) $ cd b43fw
c) $ sudo wget -c http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
d) $ sudo tar xf broadcom-wl-5.100.138.tar.bz2
e) $ sudo mkdir -p /usr/local/lib/firmware
f) $ tce-load -i b43-fwcutter
g) $ sudo b43-fwcutter -w /usr/local/lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o
II. Load wireless module:
a) $ tce-load -i wireless_tools
III. Associate with WEP
a) $ tce-load -i rfkill
b) $ sudo rfkill unblock wifi
c) $ sudo iwconfig wlan0 essid eltonenetwork
d) $ sudo iwconfig wlan0 key 6789abcdef
e) # sudo iwconfig
f) $ sudo ifconfig wlan0 up
IV. Run udhcpc
a) $ sudo udhcpc -S -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
Suspect root cause is prior to your instructions mentioned above, in the boot phase.
The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'
Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.
eltone
-
e) # sudo iwconfig
f) $ sudo ifconfig wlan0 up
I didn't mention either of these and believe that they are probably not necessary.
Suspect root cause is prior to your instructions mentioned above, in the boot phase.
I doubt it - I haven't seen anything so far that would suggest this is the case.
The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'
That is so most wired connections work automatically, but it has no effect on wireless connections.
Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.
The udhcpc command sets wlan0/dhcp, but you can also associate with your wap and then use the cpanel network gui if you wish. If you load the firmware, load the wireless extension and use rfkill to enable your hardware, the wifi extension will also work.
The fact that eth0 is always enabled does not affect anything to do with wifi.
-
e) # sudo iwconfig
f) $ sudo ifconfig wlan0 up
I didn't mention either of these and believe that they are probably not necessary.
I did recommend e)
but:
1. That makes only sense after the interface is already up
2. This serves the purpose to verify if a link with WAP is established before attempting to run dhcp client, i.e. check fields:
Access Point:
Link Quality=
Signal level:
-
Suspect root cause is prior to your instructions mentioned above, in the boot phase.
The Control Panel 'Network' is always set to 'ethernet eth0/NO DHCP'
Q: How can Network be set to 'wlan0/use DHCP broadcast'??
'eth0' is always enabled, even without being hard-wired to machine.
eltone
hi,
The one clue that udhcpc will/might function is when the ethernet cable is hard-wired to notebook AND I see the dns server addresses flash on the screen during boot, similar to when udhcpc desides to function. Removing ethernet cable and entering your posted CLI instructions is what worked to post this note (see syslog attachment)!
Please help resolve this elusive, but interesting problem . . .
eltone
PS. the path is getting warmer.
-
The wiki is a great place to learn and source of reference..
1
Meanwhile, try creating your extension in /tmp
2
For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz
3
start by creating your directory structure, at the command line
mkdir -p /tmp/pkg/usr/local/lib/firmware/b43cut
mkdir -p /tmp/pkg/usr/local/tce.installed
4
create a file (in this case a udevadm trigger)
touch /tmp/pkg/usr/local/tce.installed/firmware-b43cut
5
open file "/tmp/pkg/usr/local/tce.installed/firmware-b43cut" and enter on the first two lines
the following, then save it
#!/bin/sh
udevadm trigger6
copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/
set permissions (note the own/perm. of tce.installed)
sudo chmod 644 /tmp/pkg/usr/local/lib/firmware/b43cut/b43cut.img
sudo chown -R root:root /tmp/pkg/usr
sudo chown -R root:staff /tmp/pkg/usr/local/tce.installed
sudo chmod -R 775 /tmp/pkg/usr/local/tce.installed
Now you're ready to squash it
cd /tmp
tce-load -i squashfs-tools-4.x.tcz && mksquashfs pkg/ firmware-b43cut.tcz
then copy the new extension to tce/optional dir, load it
tc@box:/$ tce-load -i firmware-b43cut.tcz
firmware-b43cut.tcz: OK
and test it
see also http://wiki.tinycorelinux.net/wiki:creating_extensions (http://wiki.tinycorelinux.net/wiki:creating_extensions)
hi,
Indexing to #5, no problem, then #6 states:
copy (your firmware file) to /tmp/pkg/usr/local/lib/firmware/b43cut/
Your instructions say to call the firmware 'b43cut.img'
Q1: Is this IMG file what goes into the 'b43cut' directory?
Q2: If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?
Suspect an extension is needed.
eltone
PS. keep the pile to a minimum
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
hi,
'dhcpcd' does not follow udhcpc Standards. Also, tc5.x man pages has nothing on it either:
tc@box:~$ dhcpcd --help
usage: dhcpcd [-dgknpqwxyADEGHJKLOTV] [-c script] [-f file] [-e var=val]
[-h hostname] [-i classID ] [-l leasetime] [-m metric] [-o option]
[-r ipaddr] [-s ipaddr] [-t timeout] [-u userclass]
[-F none|ptr|both] [-I clientID] [-C hookscript] [-Q option]
[-X ipaddr] <interface>
tc@box:~$
Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?
Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html (http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html)
eltone
-
For this example we'll call the firmware b43cut.img, and
the extension firmware-b43cut.tcz
Your instructions say to call the firmware 'b43cut.img'
Q1: Is this IMG file what goes into the 'b43cut' directory?
Q2: If correct, how are the numerous FW files made into an IMG file w/TCP 5.1?
They're not exactly instructions to be followed to the letter, more of an example (though the example does in fact work as advertised).. If they were instructions it would say rename the file to this, etc etc. if that were necessary. I believe the original file name should remain unchanged, I simply didn't know the final cut file name is all. the dir name in this case is less important though ought to reflect the contents. Similar for the extension name which additionally should not conflict with any in the repo (name could be myb43, whatever..)
Rarely are two extensions alike, they differ greatly due to their contents.
better to examine how a similar extension is constructed, sometimes names and permissions are important, use
this to examine an extension
unsquashfs -d extension_name extension_name.tcz
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
hi,
'dhcpcd' does not follow udhcpc Standards. Also, tc5.x man pages has nothing on it either:
Huh?? ???
Both udhcpc and dhcpcd follow dhcp protocol as described in the relevant RFC's.
The manpage of dhcpcd could be found within less than a minute on the web, like almost all manpages... ::)
Q1: Has anyone been able to get dhcpcd to find a valid IP address & with what syntax?
Q2: Could dhcpcd be compiled from source w/TCP 5.1, following this protocol:
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html (http://www.linuxfromscratch.org/blfs/view/svn/basicnet/dhcpcd.html)
eltone
dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...
-
dhcpcd.tcz is already in 5.x repo, I checked that before even suggesting so...
My Dear Friend!
Q: Shouldn't ALL remnants of udhcpc be completely removed before installing the .TCZ?
It appears to be original settings of TCP 5.1 . . .
'udhcpc' has no .TCZ and suspect it to be part of the OS Standards.
Faithfully,
eltone
* FIX what's BROKEN *
:)
-
udhcpc is an applet of busybox, like most commands in Core Base.
There is no conflict whatsoever, if that's what you meant to ask.
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
hi,
Current revision == 6.21.0
dhcpcd.tcz rev. == 5.2.12
Title: dhcpcd.tcz
Description: A RFC2131 compliant DHCP client.
Version: 5.2.12
Author: Roy Marples
Original-site: http://roy.marples.name/projects/dhcpcd
Copying-policy: BSD
Size: 44K
Extension_by: Arslan S.
Tags: RFC2131 compliant DHCP client.
Comments: This extension is PPI compatible.
Change-log: 2010/07/05 First Version 5.2.5
2010/11/06 Updated to 5.2.8
2011/02/03 Updated to 5.2.10
2011/03/14 Updated to 5.2.11
Current: 2011/04/10 Updated to 5.2.12
Please update . . .
eltone
PS. Like/dislike udhcpc; it's broken and needs to be fixed :)
-
Please stop this - udhcpc is not broken and does not need to be fixed - way back in this thread you even posted from a wifi connection made with udhcpc.
If you'd like dhcpcd to be updated, please pm the maintainer
-
Please stop this - udhcpc is not broken and does not need to be fixed - way back in this thread you even posted from a wifi connection made with udhcpc.
If you'd like dhcpcd to be updated, please pm the maintainer
CORRECTION!
Dear Juanito:
'dhcpcd' was/is not in this threads original intent. It was a suggestion by someone else!
'udhcpc' is VERY unstable on two machines. PC #2 has a WLAN adapter that has it's driver compiled into the 3.8.13 Kernel. There is no need to cut it's firmware like PC #1 AND it still fails to get a consistant IP address just like PC #1. I would like to start a new thread when I find time to troubleshoot PC #2.
Sincerely,
eltone
PS. no offense :)
Current udhcpc revision == 1.22.1
TCP 5.1 udhcpc version == 1.20.2
-
Do not start a new thread for an existing discussion. It merely deprives readers from understanding what has already been discussed.
-
This thread now being 125 posts long, I have not noticed any evidence that udhcpc would be "broken" or "unstable".
In your log attached to Reply #114 everything appears to be perfect to me, not sure what your issue is.
In case you attempt to run any dhcp client on an interface without first having established a fully functional net link, of course there will be no response from any server, that is only expected!
-
This thread now being 125 posts long, I have not noticed any evidence that udhcpc would be "broken" or "unstable".
In your log attached to Reply #114 everything appears to be perfect to me, not sure what your issue is.
In case you attempt to run any dhcp client on an interface without first having established a fully functional net link, of course there will be no response from any server, that is only expected!
Dear tinypoodle:
The only CLI instructions needed by PC #2 to post this note:
$ tce-load -i wireless_tools
$ sudo iwconfig wlan0 essid eltonenetwork
$ sudo iwconfig wlan0 key 6789abcdef
$ sudo iwconfig
$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
Q: If udhcpc fails to fetch an IP address following a cold boot, using the same CLI indexing, what's the cause? This occurs frequently on two separate PC's!
Sincerely,
eltone
-
Did you check parameters of your link as advized in Reply #113?
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
hi,
Current revision == 6.21.0
dhcpcd.tcz rev. == 5.2.12
Title: dhcpcd.tcz
Description: A RFC2131 compliant DHCP client.
Version: 5.2.12
Author: Roy Marples
Original-site: http://roy.marples.name/projects/dhcpcd
Copying-policy: BSD
Size: 44K
Extension_by: Arslan S.
Tags: RFC2131 compliant DHCP client.
Comments: This extension is PPI compatible.
Change-log: 2010/07/05 First Version 5.2.5
2010/11/06 Updated to 5.2.8
2011/02/03 Updated to 5.2.10
2011/03/14 Updated to 5.2.11
Current: 2011/04/10 Updated to 5.2.12
Please update . . .
eltone
PS. Like/dislike udhcpc; it's broken and needs to be fixed :)
Why do you think an update would solve the problem? If you are unhappy with udhcpc you can try dhcp.tcz the official ISC client. But trust others, it IS NOT an udhcp issue!
-
Remember that extension deps are recursive, there is no need to have most of those extensions named in onboot.lst
hi,
I just established udhcpc finding an IP address fiasco linked to invalid extensions named in onboot.lst!
Q: How can invalid onboot.lst extensions get blacklisted from ever existing in onboot.lst?
eltone
-
Use "apps" for extension maintenance.
-
Hi eltone
You are attempting take a quote by gerald_clark and use it out of context.
The existing discussion is about wireless network connections. You are now starting a new topic and that should be in a
separate thread.
-
Why do you think an update would solve the problem? If you are unhappy with udhcpc you can try dhcp.tcz the official ISC client. But trust others, it IS NOT an udhcp issue!
Dear bmarkus:
Here is the problem, if I take the functional LiveUSB w/udhcpc to another PC, udhcpc freezes 80% and fully functions the other 20% of the time!
'dhcp.tcz' is not in the tc-4.x repo, so I just installed the 'dhcpcd.tcz' DHCP client on my stable 4.77 LiveUSB, to test:
tc@box:~$ sudo dhcpcd wlan0 -X 192.168.0.64 -h box
dhcpcd[2266]: version 5.2.12 starting
dhcpcd[2266]: wlan0: waiting for carrier
dhcpcd[2266]: wlan0: carrier acquired
dhcpcd[2266]: wlan0: broadcasting for a lease
dhcpcd[2266]: wlan0: offered 192.168.0.64 from 192.168.0.1
dhcpcd[2266]: wlan0: acknowledged 192.168.0.64 from 192.168.0.1
dhcpcd[2266]: wlan0: checking for 192.168.0.64
dhcpcd[2266]: wlan0: leased 192.168.0.64 for 86400 seconds
dhcpcd[2266]: forked to background, child pid 2303
tc@box:~$
It appears dhcpcd accepted the static IP address, but NO AP connection, yet NO errors were trapped!
To post this note, udhcpc was used:
c@box:~$ sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc (v1.20.2) started
Sending discover...
Sending select for 192.168.0.64...
Lease of 192.168.0.64 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 205.171.9.25
adding dns 8.8.4.4
adding dns 205.171.6.25
adding dns 8.8.8.8
tc@box:~$
This dialog indicates dhcpcd didn't add the dns server addresses!
Q: How can the essential dns servers be functional w/dhcpcd?
Sincerely,
eltone
-
Do you have the same problem connecting to other AP/router or just this one?
-
Your claims do not match your evidence.
You could not get an IP address if you were not associated to an access point.
I don't know how you are specifying 4 dns servers. Only 3 can be used.
-
Do you have the same problem connecting to other AP/router or just this one?
hi,
I went from dial-up to DSL is 2010 and am still using the original Motorola 3347 router.
'udhcpc' has never failed w/TCP 4.77 on this hp notebook, but freezes OS every attempt on the hp desktop.
On TCP 5.1/5.2, it's more likely to fail most of the time, no matter the hardware.
eltone
-
Your claims do not match your evidence.
You could not get an IP address if you were not associated to an access point.
I don't know how you are specifying 4 dns servers. Only 3 can be used.
Dear gerald_clark:
Both APPS & FF are NON functional! In the past, my ISP dns server addresses needed to be plugged into another linux network-manager, to get FF on-the-net.
4 dns servers were specified when posting this note w/TCP 4.77 w/o a problem.
eltone
-
Your claims do not match your evidence.
You could not get an IP address if you were not associated to an access point.
I don't know how you are specifying 4 dns servers. Only 3 can be used.
hi,
Your post initiated some detective 'dhcpcd' work and found:
tc@box:~$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 304 0 0 wlan0
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
192.168.0.0 0.0.0.0 255.255.255.0 U 304 0 0 wlan0
tc@box:~$ cat /etc/resolv.conf
# Generated by dhcpcd from wlan0
# /etc/resolv.conf.head can replace this line
nameserver 192.168.0.1
# /etc/resolv.conf.tail can replace this line
tc@box:~$
192.168.0.1 looks suspicious! Any help, please?
eltone
-
Not suspicious.
Your dhcp server is 192.168.0.1.
It also sent itself as the nameserver and router.
- edit -
Do you by any chance have two dhcp servers running?
That would result in havoc.;
-
Do you by any chance have two dhcp servers running?
That would result in havoc.;
hi,
Today's 'dhcpcd' data posts have the 'udhcpc' DHCP client still enabled!
Q: How is 'udhcpc' uninstalled? Isn't It part of TCP's original settings . . .
eltone
-
Udhcpc is part of busybox. You disable it by using the nodhcp boot option.
My questions was about having more than one dhcp server on your network.
You got your IP address, router and nameserver form 192.168.0.1.
Were you expecting to get them from a different server?
Having more than one dhcp server on your network may result in random lockups due to IP collisions and incorrect router and dns assignments.
-
Udhcpc is part of busybox. You disable it by using the nodhcp boot option.
My questions was about having more than one dhcp server on your network.
You got your IP address, router and nameserver form 192.168.0.1.
Were you expecting to get them from a different server?
Having more than one dhcp server on your network may result in random lockups due to IP collisions and incorrect router and dns assignments.
hi,
Boot code 'nodhcp' is whats been used. My ISP provided the 192.168.0.1 address to plug into the browser for configuring the router and their two nameserver addresses. Having more than one dhcp server on eltonenetwork should be traced in some way, but HOW?
eltone
-
192.168.0.1 is a private IP, not a public IP.
Your ISP did not provide it, though it may be the default for your router.
-
My wild guess would be that DNS server running on gateway device is configured to retrieve DNS from ISPs server, which may be ideal for most use cases and default configuration for most consumer gateways provided by ISPs.
-
And if you still don't like udhcpc, you could always use the dhcpcd.tcz extension as in repo instead ;)
ATT: tc-5.x Support
Re: TCP Current (5.2)
Functioned w/4.x
tc@box:$ sudo dhcpcd -h box -X 192.168.0.64 wlan0
dhcpcd[3528]: version 5.2.12 starting
dhcpcd[3528]: wlan0: waiting for carrier
dhcpcd[3528]: timed out
dhcpcd[3528]: allowing 8 seconds for IPv4LL timeout
dhcpcd[3528]: timed out
tc@box:$
Firmware installed ok, suspect 5.x compile is required.
eltone
PS. static IP CLI WLAN route's worth investigating
-
Topic marked SOLVED. So what is the issue?
-
Nota bene: Marked solved since around 17 days resp. 44 posts ago :o