I sometimes see a similar issue on my laptop after suspend-to-ram.
On resume, often times the internal wireless card (an ipw2200) will be renamed to eth0_clashed (when it is normally eth0). My /etc/iftab looks pretty sane to me (contents below).
eth0 mac 00:12:f0:74:ae:f9
eth1 mac 00:12:3f:80:06:e7
....ae:f9 is indeed the mac of my ipw2200 card.
When this happens, hal completely forgets about the card. That is, "lshal | grep eth0" does not output anything. However, ifconfig and iwconfig still show it. Sometimes these symptoms also occur without the interface being renamed.
I have come to believe that this is a bug in the ipw2200 driver's suspend functions, rather than a problem with udev or hal. I wonder what card the original bug reporter is using?
I sometimes see a similar issue on my laptop after suspend-to-ram.
On resume, often times the internal wireless card (an ipw2200) will be renamed to eth0_clashed (when it is normally eth0). My /etc/iftab looks pretty sane to me (contents below).
eth0 mac 00:12:f0:74:ae:f9
eth1 mac 00:12:3f:80:06:e7
....ae:f9 is indeed the mac of my ipw2200 card.
When this happens, hal completely forgets about the card. That is, "lshal | grep eth0" does not output anything. However, ifconfig and iwconfig still show it. Sometimes these symptoms also occur without the interface being renamed.
I have come to believe that this is a bug in the ipw2200 driver's suspend functions, rather than a problem with udev or hal. I wonder what card the original bug reporter is using?