madwifi not fully functional after resume?

[Stephan Rügamer]

Hi

after hibernating or suspend2ram the wifi interface (atheros, madwifi driver)
doesn't update correctly using dhclient.

ethernet works fine.

[Stephan Rügamer (sruegamer)]

well..

i don't think it has anything todo with the kernel, cause the interface is there
(ath0)
only dhcp renew doesn't work.

[Stephan Rügamer (sruegamer)]

Ok,

I think I have the mistake:

in /etc/acpi/resume.sh

# Bring up the interfaces (this should probably be left up to some policy
# manager, but at the moment we just bring back whatever we ifdowned)
#for x in $INTERFACES; do
# ifup $x;
#done

# Actually, we don't for the moment - we end up waiting for things to time out
# because multiple ifups want to write to the state file and it's locked. We
# need a better way of doing this - for now just bring back up whatever is
# flagged as auto

ifup -a &

my wifi device is not in /etc/network/interfaces and not flagged as auto...
so this is issue....
but this should not be the correct way of resuming.
I think we should save the state of the running devices and resume them later as
it was before suspend2ram or hibernating.

regards,

\sh

[Matt Zimmerman (mdz)]

(In reply to comment #1)
> well..
>
> i don't think it has anything todo with the kernel, cause the interface is there
> (ath0)
> only dhcp renew doesn't work.
>

Your report was rather terse. It sounded like you were saying that dhclient was
run, but wasn't successful.

This bug has been marked as a duplicate of bug 20769.