I noticed that /etc/modprobe.d/ipw3945 still existed after upgrade from gutsy to hardy, while now the driver should be iwl3945 (ipw3945 is obsolete). I renamed the file to /etc/modprobe.d/ipw3945_old and rebooted. After manually selecting the wireless AP, it connected after a minute or so.
So, one of the problems for gutsy->hardy upgraders may be that 2 drivers for 3945 are present. This may be a clue.
BTW, I still get the "dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason" error.
I guess that there must be a more elegant way to get it right, so I will keep an eye on this
I noticed that /etc/modprobe. d/ipw3945 still existed after upgrade from gutsy to hardy, while now the driver should be iwl3945 (ipw3945 is obsolete). I renamed the file to /etc/modprobe. d/ipw3945_ old and rebooted. After manually selecting the wireless AP, it connected after a minute or so.
So, one of the problems for gutsy->hardy upgraders may be that 2 drivers for 3945 are present. This may be a clue. dhcp/eth1 for sub-path eth1.dbus. get.reason" error.
BTW, I still get the "dhcdbd: message_handler: message handler not found under /com/redhat/
I guess that there must be a more elegant way to get it right, so I will keep an eye on this