1 |
maybe you were trying to use bcm with ndiswrapper module enabled or it had |
2 |
something that prevented the driver from loading. |
3 |
for what it's written in the bcm43xx.berlios.de supported boards your's it's |
4 |
one of the one fully supported. so you can experience a full working |
5 |
wireless experience. if you need more help just ask for it. |
6 |
|
7 |
|
8 |
2007/10/12, Mark Haney <mhaney@××××××××××××.org>: |
9 |
> |
10 |
> Beso wrote: |
11 |
> > from dmesg i can see that you get no firmware error so your chip loads |
12 |
> it |
13 |
> > well. |
14 |
> > from pci id and chip detection i can see that your chip is: |
15 |
> > 4306 PCI/Cardbus Supported |
16 |
> > for what i've seen it seems that you have an amilo1650 which has an |
17 |
> annoying |
18 |
> > radio switch to turn on. the fsaa1655g does the trick for mine laptop. |
19 |
> but i |
20 |
> > think that you would use that radio switch with ndiswrapper too. if it's |
21 |
> not |
22 |
> > the case then i'd need to have some more info. do a dmesg > dmesg.txtand |
23 |
> > append it. then do a cat /var/log/messages > message.txt and append it |
24 |
> too. |
25 |
> > it seems that there's something happening when loading the module. |
26 |
> > the wext module is a misunderstood. i should have define it better: its |
27 |
> not |
28 |
> > a kernel module, but it stands for linux Wireless EXTenensions. i've |
29 |
> called |
30 |
> > it module doing a bad thing for you've nisunderstood. so you won't see |
31 |
> it in |
32 |
> > the lsmod simply because it's not a kernel module. |
33 |
> > the wlan0 has wireless extensions but you have some problems with the |
34 |
> core |
35 |
> > going up. so the interface you'd use is wlan0. the problem is that |
36 |
> bcm43xx |
37 |
> > module fails to startup the core and keeps the wireless channel off. so |
38 |
> we |
39 |
> > have to first see what happens when it tries to load the module and know |
40 |
> why |
41 |
> > it doesn't start. |
42 |
> > and there would also be a good thing doing a lspci and then find the |
43 |
> slot of |
44 |
> > your broadcom board and do a lspci -vs the slot number. |
45 |
> > here i give you an example: |
46 |
> > this is part of lspci output: |
47 |
> > |
48 |
> >> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. |
49 |
> >> RTL-8139/8139C/8139C+ (rev 10) |
50 |
> >> |
51 |
> > and this is lspci -vs 08:0d.0 output: |
52 |
> > |
53 |
> >> 08:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. |
54 |
> >> RTL-8139/8139C/8139C+ (rev 10) |
55 |
> >> Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10a4 |
56 |
> >> Flags: bus master, medium devsel, latency 64, IRQ 17 |
57 |
> >> I/O ports at a000 [size=256] |
58 |
> >> Memory at c0210800 (32-bit, non-prefetchable) [size=256] |
59 |
> >> Capabilities: [50] Power Management version 2 |
60 |
> > |
61 |
> > |
62 |
> > i'd like to know if lspci detects the same board as does the bcm |
63 |
> driver. |
64 |
> > so, in conclusion: i need a full dmesg output, the kernel log, lspci |
65 |
> verbose |
66 |
> > on the slot of your broadcom board and to know if you have some software |
67 |
> > wireless switch (that normally were included into fujitsu notebooks). |
68 |
> > |
69 |
> > |
70 |
> > |
71 |
> |
72 |
> Well, I gotta tell ya, I don't know if somehow I missed this, or I tried |
73 |
> this command in the wrong place orwhat, but it works now. I had tried |
74 |
> 'iwconfig wlan0 up' and that didn't work and I was almost certain I had |
75 |
> tried 'ifconfig wlan0 up' and THAT didn't work either. |
76 |
> |
77 |
> However, I re-tried the ifconfig command and it worked this time. I can |
78 |
> now scan the wireless network in my office and everything looks really |
79 |
> good at this point. I do appreciate the help you've given me, Beso, I |
80 |
> certainly hope I can return the favor in the future. |
81 |
> |
82 |
> |
83 |
> -- |
84 |
> Recedite, plebes! Gero rem imperialem! |
85 |
> |
86 |
> |
87 |
> Mark Haney |
88 |
> Sr. Systems Administrator |
89 |
> ERC Broadband |
90 |
> (828) 350-2415 |
91 |
> |
92 |
> Call (866) ERC-7110 for after hours support |
93 |
> -- |
94 |
> gentoo-amd64@g.o mailing list |
95 |
> |
96 |
> |
97 |
|
98 |
|
99 |
-- |
100 |
dott. ing. beso |