[iwl4965] [Gutsy] wireless-connection not ready on start

[slamdunk]

Binary package hint: linux-source-2.6.22

Hardware: Dell XPS M1330
System: Gutsy Gibbon Tribe 4

When I launch system, wireless-connection is not ready on log in, and so I need to launch from root-shell:

iwconfig wlan0 essid XXXXXX
dhclient wlan0

but sometimes I need to repeat that command many times, because essid is automatically reset to ""

[exactt (giesbert)]

have you tried the latest tribe (5)?
what chipset are you talking about?

[slamdunk (antongiulio05)]

Yes I'm using Tribe 5 (first message is a reposted message changing package from linux-kernel to nm)

lspci -vv:
......
0c:00.0 Network controller: Intel Corporation Unknown device 4229 (rev 61)
        Subsystem: Intel Corporation Unknown device 1121
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at f9ffe000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: <access denied>

kernel module is : iwl4965

[Alexander Sack (asac)]

this sounds similar to bug 128360 which is ipw3945 driver related though. Can you please attach your syslog/daemon.log to this report?

[slamdunk (antongiulio05)]

However I have reported this bug too around this driver:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133395

[Alexander Sack (asac)]

please stop nm and ifdown wlan0 ... then set essid to ANY and observe if iwconfig will auto associate to an access point:

 iwconfig wlan0 essid ANY

then run iwconfig wlan0 (a few times for some time) ... and observe if your driver automatically goes back to some AP.

Thanks,

 - Alexander

[Steve Alexander (stevea)]

Alexander, how do you want me to stop nm?

The rest of your instructions are clear.

[slamdunk (antongiulio05)]

@Steve Alexander:

# killall -9 NetworkManager

@Alexander Sack:

with essid ANY

# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:""

I need to pass manually name of my ap

and then I need to repeat few times:

dhclient wlan0

to get connection (and kill wpa_supplicant too)

[Steve Alexander (stevea)]

I killed NetworkManagerDispatcher and nm-applet.

There was no process NetworkManager.

I ran the commands:

  # iwconfig wlan0 essid ANY
  # watch "iwconfig wlan0 | grep Access"

I watched for 10 minutes, wlan0 did not associate itself with an access point.

Then I ran this, and manually reconnected:

# killall dhclient ; killall dhclient3 ; rmmod iwl4965 mac80211 cfg80211 ; modprobe iwl4965; modprobe mac80211 ; modprobe cfg80211 ; sleep 1 ; ifconfig wlan0 up ; sleep 1; iwconfig wlan0 essid ESSID-OF-AP ; dhclient wlan0

Then I added this comment :-)

[Alexander Sack (asac)]

there was an update of iwl4965 a few days ago. Can you please test and report back if you still see this issue?

Thanks,

 - Alexander

[slamdunk (antongiulio05)]

Actually I'm at work and I cannot use wireless.

However around 12 hours ago I made an upgrade (I do it 1 or more times in a day and so my Gutsy is aligned) and nothing is changed. Same problems above. However if it needed this evening I can report logs etc.

[Alexander Sack (asac)]

please provide fresh logs ... and please test the wpasupplicant preview package provided at:

 http://ppa.launchpad.net/asac/ubuntu/pool/main/w/wpasupplicant/

[slamdunk (antongiulio05)]

I have attached log: I got it using above version of wpa_supplicant and just upgrading system few minutes before

[slamdunk (antongiulio05)]

Curiosity:

I have reported 2 bugs regarding wireless: this and https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/133395

Are they an "ubuntu" problem (wpa_supplicant, networkmanager etc) or is it related to intel-driver-release?

[slamdunk (antongiulio05)]

Why this bug-report is considered "incomplete" now?
What's needed?

[slamdunk (antongiulio05)]

great! it's fixed now!

thank you very much!

I close this bug-report