iwl3945 can't set parameters for ad-hoc network

Bug #222302 reported by MattJ
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Using Hardy and linux-backports-modules-hardy, see attached for modinfo.

With NetworkManager running, using iwconfig results in:

$ sudo iwconfig wlan0 mode ad-hoc essid mynetwork channel 10
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Device or resource busy.

After disabling wireless in NM, or killing it, I get:

$ sudo iwconfig wlan0 mode ad-hoc channel 10 essid mynetwork
Error for wireless request "Set Frequency" (8B04) :
    SET failed on device wlan0 ; Input/output error.

Separately:

iwconfig wlan0 mode ad-hoc # <-- works

After that, setting essid or channel both fail with the same error above. iwevent shows the mode change, but not channel or essid change.

'ifconfig' does not show wlan0. 'ifconfig wlan0' shows:

$ ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:19:d2:5e:56:34
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:576 (576.0 B)

Gutsy (which had ipw3945) worked fine with this network setup.

Tags: cft-2.6.27
Revision history for this message
MattJ (mwild1) wrote :
Revision history for this message
krom (krom) wrote :

confirm this bug.
Dell Inspiron 1525
iwl3945 driver v. 1.2.25 from backports

Revision history for this message
Psy[H[] (vovik-wfa) wrote :

Confirmed on Asus A8Sr, Intel PRO/Wireless 3945ABG, latest updates from backports now!

Revision history for this message
thiago (pereirats) wrote :

Confirmed on HP Pavilion dv6000, intel PRO/Wireless 3945ABG

Revision history for this message
Kasper Peeters (kasper-peeters) wrote :

Confirmed for Thinkpad t60 with iwl3945 version 1.2.25. In the rare cases that it does work,
no other machine is able to connect to the ad-hoc network. This worked fine with ipw3945 in Dapper.

Is there any workaround as of yet?

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

There hasn't been any recent activity in this bug report and we were wondering if this is still an issue? The Ubuntu kernel team is actively working on the upcoming Intrepid Ibex 8.10 release. If you could please test the latest Alpha release for Intrepid it would be much appreciated - http://www.ubuntu.com/testing . Please let us know your results. If the issue still exists, please also provide the appropriate debugging information as outlined at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance.

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

sibidiba (sibidiba)
Changed in linux:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.