Resume from hibernate associates WiFi but doesn't run dhclient to get IP

Bug #64988 reported by Adam Porter on 2006-10-10
8
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: acpi-support

I have an old Compaq Presario 1690 laptop. Happily, hibernating and resuming works great with Edgy! However, one of the minor problems with resuming is that, while the WiFi card (D-Link DWL-650+) successfully reassociates with the access point automatically, dhclient is apparently never run, and the network interface doesn't get an IP address. If I simply run dhclient myself, it works fine.

I suppose it's possible that this is related to Bug#63286, but I suspect they're separate problems.

Revision history for this message
Daniel (elenius) wrote :

I can confirm this problem on Ubuntu 7.04, all the latest updates as of the time of this post.

I'm running on a Thinkpad z61m with an Atheros wireless card.

 uname -a
Linux ubuntu 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux

Shouldn't this be very easy to fix? Just put in dhclient in a script somewhere (if I only knew where...).

Revision history for this message
Daniel (elenius) wrote :

Forgot to say, the situation is the same whether i suspend or hibernate.

Revision history for this message
Daniel (elenius) wrote :

I fixed the problem by creating a file /etc/acpu/resume.d/64-dhclient.sh, with the following contents:

#!/bin/sh
dhclient

That's it. The wifi now works correctly on resume. I guess this should be put there automatically when the network settings are configured for dhcp.

Revision history for this message
mike hancock (javaiscoolmike) wrote :

i have a similar wifi card to the original submitter(D Link DWL-650 11Mbps WLAN Card Version 01.02 Identification: manf_id: x0156 card_id: 0x0002). I also have a similar problem to what he said. But I woudl like to note that the solution listed here does not work for me. if i only run "dhclient" that does not work right. if i run:

/etc/init.d/networking restart

that seems to work. It might have to do with my wifi network is 'hidden' and running just "dhclient" does not seem to try to connect the way I had it originally. Ideally some thing should really save the state of the all of ones network devices before a suspend/hibernation and then on resume: first try the old setting, then if any old settings fail put use the default settings.

Revision history for this message
Mackenzie Morgan (maco.m) wrote :

Are you all still having this problem with Hardy? If you are, can you test it out on Intrepid, and reply back as to whether it works properly there or not?

Daniel T Chen (crimsun) on 2008-09-18
Changed in acpi-support:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in acpi-support:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers