1 |
from dmesg i can see that you get no firmware error so your chip loads it |
2 |
well. |
3 |
from pci id and chip detection i can see that your chip is: |
4 |
4306 PCI/Cardbus Supported |
5 |
for what i've seen it seems that you have an amilo1650 which has an annoying |
6 |
radio switch to turn on. the fsaa1655g does the trick for mine laptop. but i |
7 |
think that you would use that radio switch with ndiswrapper too. if it's not |
8 |
the case then i'd need to have some more info. do a dmesg > dmesg.txt and |
9 |
append it. then do a cat /var/log/messages > message.txt and append it too. |
10 |
it seems that there's something happening when loading the module. |
11 |
the wext module is a misunderstood. i should have define it better: its not |
12 |
a kernel module, but it stands for linux Wireless EXTenensions. i've called |
13 |
it module doing a bad thing for you've nisunderstood. so you won't see it in |
14 |
the lsmod simply because it's not a kernel module. |
15 |
the wlan0 has wireless extensions but you have some problems with the core |
16 |
going up. so the interface you'd use is wlan0. the problem is that bcm43xx |
17 |
module fails to startup the core and keeps the wireless channel off. so we |
18 |
have to first see what happens when it tries to load the module and know why |
19 |
it doesn't start. |
20 |
and there would also be a good thing doing a lspci and then find the slot of |
21 |
your broadcom board and do a lspci -vs the slot number. |
22 |
here i give you an example: |
23 |
this is part of lspci output: |
24 |
|
25 |
> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. |
26 |
> RTL-8139/8139C/8139C+ (rev 10) |
27 |
> |
28 |
and this is lspci -vs 08:0d.0 output: |
29 |
|
30 |
> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. |
31 |
> RTL-8139/8139C/8139C+ (rev 10) |
32 |
> Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10a4 |
33 |
> Flags: bus master, medium devsel, latency 64, IRQ 17 |
34 |
> I/O ports at a000 [size=256] |
35 |
> Memory at c0210800 (32-bit, non-prefetchable) [size=256] |
36 |
> Capabilities: [50] Power Management version 2 |
37 |
|
38 |
|
39 |
i'd like to know if lspci detects the same board as does the bcm driver. |
40 |
so, in conclusion: i need a full dmesg output, the kernel log, lspci verbose |
41 |
on the slot of your broadcom board and to know if you have some software |
42 |
wireless switch (that normally were included into fujitsu notebooks). |
43 |
|
44 |
|
45 |
|
46 |
2007/10/11, Mark Haney <mhaney@××××××××××××.org>: |
47 |
> |
48 |
> Beso wrote: |
49 |
> > i think that you've forgottonen to install the firmware.... remember |
50 |
> that |
51 |
> > you have to download the firmware (i've appended it to this email), then |
52 |
> > install bcm43xx-fwcutter from portage, cut the firmware with the |
53 |
> command: |
54 |
> > bcm43xx-fwcutter wl_apsta.o and then copy the files with the extension |
55 |
> .fw |
56 |
> > that you can you'll have in the directory that contains wl_apsta.o into |
57 |
> the |
58 |
> > /lib/firmware directory. this directory is protected so you'll need root |
59 |
> > priviledges to copy the files in there. after you've copied the .fw |
60 |
> files |
61 |
> > into the directory do this: |
62 |
> > |
63 |
> >> chmod +r+x /lib/firmware/*.fw |
64 |
> |
65 |
> I did have the firmware included I just neglected to mention it. Sorry |
66 |
> about that. |
67 |
> > |
68 |
> > |
69 |
> > do a dmesg | grep bcm43xx and see if it gives you errors or similar |
70 |
> things |
71 |
> > and then do a iwconfig that will list all your network interfaces. now |
72 |
> > search for wlan or eth interfaces and see which one of them has wireless |
73 |
> > extensions. the interface that has wireless extensions is the one you're |
74 |
> > searching for. |
75 |
> > broadcom module uses the wext (linux wireless extensions) so if you need |
76 |
> to |
77 |
> > configure the wireless you'll do it through the wext module. |
78 |
> > |
79 |
> > |
80 |
> When I look at dmesg I get this: |
81 |
> |
82 |
> octavian Mark # dmesg | grep bcm43xx |
83 |
> bcm43xx driver |
84 |
> bcm43xx: Chip ID 0x4306, rev 0x3 |
85 |
> bcm43xx: Number of cores: 5 |
86 |
> bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 |
87 |
> bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 |
88 |
> bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 |
89 |
> bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 |
90 |
> bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 |
91 |
> bcm43xx: PHY connected |
92 |
> bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 |
93 |
> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) |
94 |
> bcm43xx: Radio turned off |
95 |
> bcm43xx: Radio turned off |
96 |
> bcm43xx driver |
97 |
> bcm43xx: Chip ID 0x4306, rev 0x3 |
98 |
> bcm43xx: Number of cores: 5 |
99 |
> bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 |
100 |
> bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 |
101 |
> bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 |
102 |
> bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 |
103 |
> bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 |
104 |
> bcm43xx: PHY connected |
105 |
> bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 |
106 |
> bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) |
107 |
> bcm43xx: Radio turned off |
108 |
> bcm43xx: Radio turned off |
109 |
|
110 |
And when I do iwconfig I get this: |
111 |
> |
112 |
> octavian Mark # iwconfig |
113 |
> lo no wireless extensions. |
114 |
> |
115 |
> eth0 no wireless extensions. |
116 |
> |
117 |
> sit0 no wireless extensions. |
118 |
> |
119 |
> wlan0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4306" |
120 |
> Mode:Managed Access Point: Invalid |
121 |
> RTS thr:off Fragment thr:off |
122 |
> Encryption key:off |
123 |
> Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm |
124 |
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 |
125 |
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 |
126 |
> |
127 |
> But when I do 'iwlist wlan0 scanning' I get: |
128 |
> |
129 |
> wlan0 Interface doesn't support scanning : No such device |
130 |
> |
131 |
> Now, you meantion the wext module, that isn't one I"m familiar with and |
132 |
> one I don't have loaded. These are the ones I /do/ have loaded relevant |
133 |
> to this: |
134 |
> |
135 |
> bcm43xx 441888 0 |
136 |
> ieee80211softmac 35328 1 bcm43xx |
137 |
> ieee80211 51188 2 bcm43xx,ieee80211softmac |
138 |
> ieee80211_crypt 7680 1 ieee80211 |
139 |
> |
140 |
> |
141 |
> I'm obviously close, but not close enough. Thoughts? |
142 |
> |
143 |
> |
144 |
> |
145 |
> -- |
146 |
> Recedite, plebes! Gero rem imperialem! |
147 |
> |
148 |
> |
149 |
> Mark Haney |
150 |
> Sr. Systems Administrator |
151 |
> ERC Broadband |
152 |
> (828) 350-2415 |
153 |
> |
154 |
> Call (866) ERC-7110 for after hours support |
155 |
> -- |
156 |
> gentoo-amd64@g.o mailing list |
157 |
> |
158 |
> |
159 |
|
160 |
|
161 |
-- |
162 |
dott. ing. beso |