Beso wrote:
from dmesg i can see that you get no firmware error so your chip loads it
well.
from pci id and chip detection i can see that your chip is:
4306 PCI/Cardbus Supported
for what i've seen it seems that you have an amilo1650 which has an annoying
radio switch to turn on. the fsaa1655g does the trick for mine laptop. but i
think that you would use that radio switch with ndiswrapper too. if it's not
the case then i'd need to have some more info. do a dmesg > dmesg.txt and
append it. then do a cat /var/log/messages > message.txt and append it too.
it seems that there's something happening when loading the module.
the wext module is a misunderstood. i should have define it better: its not
a kernel module, but it stands for linux Wireless EXTenensions. i've called
it module doing a bad thing for you've nisunderstood. so you won't see it in
the lsmod simply because it's not a kernel module.
the wlan0 has wireless extensions but you have some problems with the core
going up. so the interface you'd use is wlan0. the problem is that bcm43xx
module fails to startup the core and keeps the wireless channel off. so we
have to first see what happens when it tries to load the module and know why
it doesn't start.
and there would also be a good thing doing a lspci and then find the slot of
your broadcom board and do a lspci -vs the slot number.
here i give you an example:
this is part of lspci output:
08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
and this is lspci -vs 08:0d.0 output:
08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10a4
Flags: bus master, medium devsel, latency 64, IRQ 17
I/O ports at a000 [size=256]
Memory at c0210800 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
i'd like to know if lspci detects the same board as does the bcm driver.
so, in conclusion: i need a full dmesg output, the kernel log, lspci verbose
on the slot of your broadcom board and to know if you have some software
wireless switch (that normally were included into fujitsu notebooks).
Well, I gotta tell ya, I don't know if somehow I missed this, or I tried
this command in the wrong place orwhat, but it works now. I had tried
'iwconfig wlan0 up' and that didn't work and I was almost certain I had
tried 'ifconfig wlan0 up' and THAT didn't work either.
However, I re-tried the ifconfig command and it worked this time. I can
now scan the wireless network in my office and everything looks really
good at this point. I do appreciate the help you've given me, Beso, I
certainly hope I can return the favor in the future.
--
Recedite, plebes! Gero rem imperialem!
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
--
[EMAIL PROTECTED] mailing list
