Author Topic: SOLVED WLAN Out to Lunch (Read 26639 times)

Rich · « **Reply #15 on:** January 11, 2013, 12:30:17 AM »

Hi eltone
See here:
http://forum.tinycorelinux.net/index.php/topic,12910.msg71013.html#msg71013
for BCM4312.

gerald_clark · « **Reply #16 on:** January 11, 2013, 01:00:39 AM »

The BMC4311 works with firmware-openfwwf.tcz.

Juanito · « **Reply #17 on:** January 11, 2013, 01:53:03 AM »

OK, but in this instance I'm reasonably sure the problem is that the user has not "cut" and loaded the broadcom firmware to use with the b43 driver.

tinypoodle · « **Reply #18 on:** January 11, 2013, 02:41:16 AM »

Quote from: eltone on January 11, 2013, 01:38:49 AM

What I have found unique to TCP is that NO RFKill app exists!
eltone

Not sure what makes you say so, it appears to be in repo.

Rich · « **Reply #19 on:** January 11, 2013, 09:40:04 AM »

Hi eltone
Yes, it's called rfkill.tcz.

Juanito · « **Reply #20 on:** January 11, 2013, 10:10:00 AM »

You just need to follow the instructions on the Linux wireless b43 page I referenced previously and then make your own personal extension of the firmware

eltone · « **Reply #21 on:** January 11, 2013, 07:28:36 PM »

How is Appbrowser launched?

gerald_clark · « **Reply #22 on:** January 11, 2013, 08:00:21 PM »

tce-ab

Rich · « **Reply #23 on:** January 11, 2013, 08:06:59 PM »

Hi eltone

Quote

inet addr:192.168.0.71 Bcast:192.168.0.1 Mask:255.255.255.0

Bcast should be 192.168.0.255

Rich · « **Reply #24 on:** January 11, 2013, 10:43:37 PM »

Hi eltone

Quote

How can software turn the wifi LED completely OFF??

Maybe:

Code: [Select]

sudo rfkill unblock wifiMan page for rfkill:
http://linux.die.net/man/1/rfkill
The man pages for rfkill are also included with the extension. If you install the man extension, you can view
them locally.

tinypoodle · « **Reply #25 on:** January 11, 2013, 11:03:03 PM »

Code: [Select]

sudo modprobe -r modulename

curaga · « **Reply #26 on:** January 12, 2013, 03:01:47 PM »

That's your DNS not working. Double-check /etc/resolv.conf.

tinypoodle · « **Reply #27 on:** January 12, 2013, 06:42:49 PM »

- What do you refer to by "loop"?

- How did you configure each interface - statically or dynamically?

- Please post output of "route -n"

eltone · « **Reply #28 on:** January 12, 2013, 07:52:49 PM »

Quote from: tinypoodle on January 12, 2013, 06:42:49 PM

- How did you configure each interface - statically or dynamically?

- Please post output of "route -n"

Quote

tc@box:~$ sudo 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 0 0 0 wlan0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
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 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
tc@box:~$

tinypoodle · « **Reply #29 on:** January 12, 2013, 10:48:49 PM »

Please search this forum for posts about how to configure multiple net interfaces.
For simplicity and to stay on the safe side, you might for now stay with 1 interface being up at a time only.

Tiny Core Linux

News: