Closing as fix released based on most recent comments.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed = Fix Released
--
ipw3945 doesn't reassociate after suspend
https://bugs.launchpad.net/bugs/56421
You received this bug notification because you are a member of Ubuntu
I can confirm that re-associating with an AP post suspend is now working
again on Feisty.
--
ipw3945 doesn't reassociate after suspend
https://bugs.launchpad.net/bugs/56421
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Been working with this issue for some time now and the fix seems to be
the ipw3945 daemon not running.
On my T60 wireless stops working after a couple of suspends/hipernations
(never counted how many times though). Not until I read this bug did I
see the connection between the daemon not running
just added a simple change to the script to make it more flexible.
Instead of:
echo Killing dhclient3 and ipw3945d
killall dhclient3
killall /sbin/ipw3945d-2.6.19-7-generic
I made it:
echo Killing dhclient3 and ipw3945d
killall dhclient3
killall /sbin/ipw3945d-`uname -r`
--
ipw3945 doesn't
I just would like to be known that after the latest-est feisty update, my card
has been reassociating completely fine - no need for the script.
Can everybody else confirm this?
Merc.
--
ipw3945 doesn't reassociate after suspend
https://bugs.launchpad.net/bugs/56421
You received this bug
Hi,
Also, this bug seems to be a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83235
If so, it would be better to mark it as a duplicate - even better,
aduplicate where the main one is apparently fixed!
Merc.
--
ipw3945 doesn't reassociate after suspend
Matthew, what Ubuntu release are you running? Would it be possible for
you to test with Feisty? (Warning - development release, please be sure
to backup all valuable data before testing.)
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
I'm currently running a fully-updated Edgy. Unfortunately, it's not
possible to test with Feisty at the moment. How else could I help?
On 2/13/07, Peter Whittaker [EMAIL PROTECTED] wrote:
Matthew, what Ubuntu release are you running? Would it be possible for
you to test with Feisty? (Warning -
Matthew, there are a couple of possible paths. For maximum risk
avoidance, wait for the new ipw3945 to be include in Edgy; if you feel
like living on the Edge, upgrade your kernel outside of the normal
channels (refer to bug #63418 for more information on both cases).
I lean toward the wait path,
Ok - any indications on how long until a new ipw3945 driver arrives?
On 2/13/07, Peter Whittaker [EMAIL PROTECTED] wrote:
Matthew, there are a couple of possible paths. For maximum risk
avoidance, wait for the new ipw3945 to be include in Edgy; if you feel
like living on the Edge, upgrade your
On Tue, 2007-02-13 at 17:57 +, Matthew Whitworth wrote:
any indications how long until a new ipw3945 driver arrives?
I think the best we can say is it's in the queue, and the best we can
do is adopt patience as our byword...! (Crossing fingers and wishing
good karma on the kernel devs
I can report the same thing happening with my Acer Aspire 5610 laptop.
The ipw3945 driver fails to reconnect after resuming, even after
switching the wireless off and on again.
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
Please review bug #63418 - it may match your problems, and there is a
new ipw3945 coming for Feisty (and Edgy). If the new ipw3945 addresses
the problems in this bug, please mark it as a dupe. Otherwise, well,
we'll burn that bridge when we get there...!
** Changed in: linux-source-2.6.15
Then this is surely a userspace problem.
...is anybody dealing with this?
My script now reads:
#!/bin/bash
echo Killing dhclient3 and ipw3945d
killall dhclient3
killall /sbin/ipw3945d-2.6.19-7-generic
echo Wait 2 secs...
sleep 2
echo Taking the modules out
rmmod ipw3945
rmmod ieee80211
** Description changed:
On my old laptop (ThinkPad T40p, ipw2100) if I had the following in
/etc/network/interfaces then after a suspend/resume cycle the network
card had re-associated with the AP and network was usable again:
auto eth0
iface eth0 inet dhcp
name home
Hiya,
I am not sure this is gonna help.
However, I found that ifdown/ifup doesn't actually do the trick.
What you _actually_ need to do is this:
#!/bin/bash
#echo Killing the DHCP client...
killall dhclient3
rm /var/run/dhclient.eth1.pid
#echo Restarting the DHCP client...
dhclient3 -pf
Hi,
Sorry, I should have said...
You should save the script as:
/etc/acpi/resume.d/99-tony.sh
And remember to set it as executable (chmod 755)
Merc.
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Sat, 2006-12-16 at 17:51 +, merc wrote:
Hiya,
I am not sure this is gonna help.
However, I found that ifdown/ifup doesn't actually do the trick.
What you _actually_ need to do is this:
#!/bin/bash
#echo Killing the DHCP client...
killall dhclient3
rm
I have exactly the same bug running Ubuntu 6.06 on a Thinkpad X60.
After applying some changes in /etc/default/acpi-support (according to this
page: https://wiki.ubuntu.com/LaptopTestingTeam/ThinkpadX60s), I was finally
able to get suspend work (didn't work out of the box).
But when resuming
Don't know if it is relevant to this bug report, but Suspend/Hibernate should
work out of the box on 6.06 too.
Hoping some improvements in 6.06.2 maybe ?
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Damn, I forgot to change the distribution. Can the Baltix distribution
be removed? (I suggest launchpad shouldn't pre-fill that field)
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Rejecting accidental baltix task
** Changed in: Baltix
Status: Unconfirmed = Rejected
--
ipw3945 doesn't reassociate after suspend
https://launchpad.net/bugs/56421
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
22 matches
Mail list logo
