1 |
On 08/18/10 01:12, Jake Moe wrote: |
2 |
> On 18/08/10 09:04, CJoeB wrote: |
3 |
>> On 08/17/10 10:55, Jake Moe wrote: |
4 |
>>> On 08/17/10 11:55, Adam Carter wrote: |
5 |
>>>>> Hi, |
6 |
>>>>> |
7 |
>>>>> I'm biting the bullet here and asking for help. Yes! I've posted |
8 |
>>>>> before. And before anyone asks, I have read the responses to my |
9 |
>>>>> previous posts which helped little. I have read the documentation and |
10 |
>>>>> the wikis - ad nauseum. I'm still having problems with wireless. |
11 |
>>>>> |
12 |
>>>> I use wpa_supplicant to provide the wifi crypto. |
13 |
>>>>> So, I'm left with trying to use the iwl3945 driver in the kernel. I |
14 |
>>>>> followed the wiki for setting this up and thought I had succeeded. I |
15 |
>>>>> got to the point where I was told to type the following: |
16 |
>>>>> ifconfig wlan0 up (this does activate the wireless led on my computer) |
17 |
>>>>> iwlist wlan0 scan |
18 |
>>>>> iwconfig wlan0 essid "network name" (where the network name is the |
19 |
>>>>> essid that has been set) |
20 |
>>>>> |
21 |
>>>>> When I got this to work, I thought I was home free despite the "kludgy" |
22 |
>>>>> way of getting wireless working. However, I rebooted and now, when I |
23 |
>>>>> type iwlist wlan0 scan I get told that scanning is not supported. Yes, |
24 |
>>>>> I have iwl3945-ucode installed and yes, it was recompiled after the |
25 |
>>>>> kernel was rebuilt. |
26 |
>>>>> |
27 |
>>>>> I have no idea what I'm doing wrong. |
28 |
>>>> Forgetting to post up your configs :) eg /etc/conf.d/net etc |
29 |
>>> I've used the iwl3945 on a few HP laptops without much problem. The few |
30 |
>>> problems I had were related to switching the wireless on and off; I'd |
31 |
>>> have to rmmod and modprobe kernel modules to get it working again. |
32 |
>>> |
33 |
>>> Does "ifconfig" list the interface? If not, what does "ifconfig wlan0 |
34 |
>>> up" do? What about the output of "iwconfig"? And going for the obvious |
35 |
>>> here, any chance that the wireless is turned off? |
36 |
>>> |
37 |
>>> Jake Moe |
38 |
>>> |
39 |
>>> |
40 |
>> iwconfig lists the interface as wlan0 |
41 |
>> |
42 |
>> I discovered last night after sending my original message that my |
43 |
>> symlink was wrong - I used to have net.eth0 and net.eth1 pointing to |
44 |
>> net.lo. However, last night I removed the net.eth1 symlink and created |
45 |
>> the net.wlan0 symlink to net.lo. Now when I boot the computer, my |
46 |
>> wireless comes up and the LED comes on, but then it times out because (I |
47 |
>> assume) it can't establish a connection. |
48 |
>> |
49 |
>> This is my /etc/conf.d/net file. Note that the "any" used to work when |
50 |
>> I used the ipw3945 driver. I would scan for available networks. I |
51 |
>> tried last night to change the "any" to the essid printed on my Bell |
52 |
>> router, but that didn't work. |
53 |
>> |
54 |
>> |
55 |
>> # This blank configuration will automatically use DHCP for any net.* |
56 |
>> # scripts in /etc/init.d. To create a more complete configuration, |
57 |
>> # please review /etc/conf.d/net.example and save your configuration |
58 |
>> # in /etc/conf.d/net (this file :]!). |
59 |
>> |
60 |
>> #preup() { |
61 |
>> # if [[ ${IFACE} = "wlan0" ]]; then |
62 |
>> # sleep 3 |
63 |
>> # fi |
64 |
>> # return 0 |
65 |
>> #} |
66 |
>> |
67 |
>> modules=( "iwconfig" ) |
68 |
>> iwconfig_wlan0="mode managed" |
69 |
>> config_eth0=("dhcp") |
70 |
>> config_wlan0=("dhcp") |
71 |
>> wpa_timeout_wlan0=15 |
72 |
>> essid_wlan0="any" |
73 |
>> |
74 |
>> Regards, |
75 |
>> |
76 |
>> Colleen |
77 |
> This is the wireless part of mine: |
78 |
> |
79 |
> modules=( "iwconfig" ) |
80 |
> config_wlan0=( "noop" "dhcp" ) |
81 |
> dhcpcd_wlan0=( "-d -t 15" ) |
82 |
> associate_order=( "forcepreferredonly" ) |
83 |
> associate_timeout=( "5" ) |
84 |
> preferred_aps=( "firstessid" "secondessid" ) |
85 |
> key_firstessid=( "THIS-ISMY-KEY1-1234-5678-90AB-CD" ) |
86 |
> key_secondessid=( "THIS-ISMY-KEY2-ABCD-EFGH-IJKL-MN" ) |
87 |
> |
88 |
> |
89 |
> I've removed anything not having to do with the wireless for clarity. |
90 |
> >From memory, the only lines needed are "modules", "config_wlan0", and |
91 |
> "preferred_aps" (I have two because I also use wireless at my g/f's |
92 |
> mum's house). Oh, and I use "forcepreferredonly" so it'll try to |
93 |
> connect even though it can't find my essid by scanning (because I've |
94 |
> told my router to stop broadcasting the essid of my wireless network), |
95 |
> and it'll only try to connect to networks I specifically tell it to, no |
96 |
> others. If your essid is hidden as well, you'll probably need to add |
97 |
> either "forcepreferredonly" or "forceany" if you want it to auto-connect |
98 |
> to any it finds if it can't connect to yours. |
99 |
> |
100 |
> Reading through the wireless.example file, I came across this: |
101 |
> |
102 |
> ############################################################################## |
103 |
> # SETTINGS |
104 |
> ############################################################################## |
105 |
> # Hard code an ESSID to an interface - leave this unset if you wish |
106 |
> the driver |
107 |
> # to scan for available Access Points |
108 |
> # Set to "any" to connect to any ESSID - the driver picks an Access |
109 |
> Point |
110 |
> # This needs to be done when the driver doesn't support scanning |
111 |
> # This may work for drivers that don't support scanning but you need |
112 |
> automatic |
113 |
> # AP association |
114 |
> # I would only set this as a last resort really - use the preferred_aps |
115 |
> # setting at the bottom of this file |
116 |
> |
117 |
> Which is why I used perferred_aps instead of essid_wlan0. Give that a |
118 |
> try, perhaps? |
119 |
> |
120 |
> Jake Moe |
121 |
> |
122 |
> |
123 |
Haven't tried this yet - just got the e-mail and it's almost 11:00 p.m. |
124 |
and time for me to "hit the sack". However, I wanted to point this |
125 |
out. This test was copied from dmesg. Unless, I am misreading this, it |
126 |
looks like the driver is working. The problem is connecting to an |
127 |
access point. If my interpretation is wrong, let me know. |
128 |
|
129 |
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for |
130 |
Linux, in |
131 |
-tree:s |
132 |
iwl3945: Copyright(c) 2003-2010 Intel Corporation |
133 |
iwl3945 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 |
134 |
iwl3945 0000:0c:00.0: setting latency timer to 64 |
135 |
iwl3945 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels |
136 |
iwl3945 0000:0c:00.0: Detected Intel Wireless WiFi Link 3945ABG |
137 |
iwl3945 0000:0c:00.0: irq 29 for MSI/MSI-X |
138 |
phy0: Selected rate control algorithm 'iwl-3945-rs' |
139 |
|
140 |
|
141 |
Regards, |
142 |
|
143 |
Colleen |
144 |
|
145 |
-- |
146 |
|
147 |
Registered Linux User #411143 with the Linux Counter, http://counter.li.org |