BigTubeOfKY wrote:Hmmm... Now that I've updated the drivers the rc.local trick doesn't seem to work anymore.
I can still get the driver to connect to my WPA network if I manually do the modprobe removal and restart.
Any ideas anyone?
Further to my earlier report, yesterday I needed to connect the Sammy to a WEP (unsecured) connection, and although it could "see" the connection it refused to complete the connection.
I ended up doing
sudo apt-get install samsung-wireless
and restarted the machine.
On restart, it immediately connected to the WEP connection.
As an experiment, I removed both the samsung-wireless and the samsung-wireless-2.6.35-22, reinstalled samsung-wireless and then samsung-wireless-2.6.35-22, rebooted, and although it still found and connected to the WEP without issue, it refused to connect to an adjacent WPA/WPA2 link.
I again removed both of the samsung-wireless connectors, and re installed the samsung-wireless-2.6.35-22 first, and then the samsung-wireless. Rebooted.
Now, the machines will connect to either the WEP or the WPA/WPA2.
Here, it seems that the order that the two samsung connectors are installed has an impact on connecting to either WEP or WPA/WPA2.
Hope these observations are of use!