I've also switched my office machine over to linux after years of enduring Windows. Simultaneously, I've moved to a new office where the internet connection is through a wireless access point. We're all given US Robotics USR5420 802.11g wireless USB adapters. I managed to get this thing going with Linuxant's driverloader software, but there are a few issues. One that seems obviously related to driverloader is that everytime I shut the system down, the shutdown stops at trying to unload the driverloader module, and I have to do a hard reset, which I'm not happy about. I've verified that the driverloader rpm is for the correct kernel version, etc. The other problem is of unknown origin, but basically the connection drops from time to time. The hardware seems to be communicating with the access point fine, but I lose my IP lease and routing information, and nothing I do (except rebooting, which then entails a hard reset) can bring it up again. I'm using WPA-PSK to encrypt the wireless signal, but all the XP computers are using a protocol that SuSE 9.3 doesn't support. Are there any bright ideas as to what the problem here might be? I'm thinking of just going out and getting a wireless card that is better supported. Any recommendations? Corvin __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
Corvin Russell wrote:
I've also switched my office machine over to linux after years of enduring Windows. Simultaneously, I've moved to a new office where the internet connection is through a wireless access point. We're all given US Robotics USR5420 802.11g wireless USB adapters. I managed to get this thing going with Linuxant's driverloader software, but there are a few issues. One that seems obviously related to driverloader is that everytime I shut the system down, the shutdown stops at trying to unload the driverloader module, and I have to do a hard reset, which I'm not happy about. I've verified that the driverloader rpm is for the correct kernel version, etc.
The other problem is of unknown origin, but basically the connection drops from time to time. The hardware seems to be communicating with the access point fine, but I lose my IP lease and routing information, and nothing I do (except rebooting, which then entails a hard reset) can bring it up again. I'm using WPA-PSK to encrypt the wireless signal, but all the XP computers are using a protocol that SuSE 9.3 doesn't support. Are there any bright ideas as to what the problem here might be?
I'm thinking of just going out and getting a wireless card that is better supported. Any recommendations?
Corvin
__________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
Not a bad idea to additionally send this to support@linuxant.com Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
I emailed support@linuxant.com and they claimed to be unaware of the problem (although a quick google shows they've replied to emails outlining this problem since SuSE 9.1 at least) and didn't really give much in the way of helpful suggestions. So I uninstalled Linuxant, and installed ndiswrapper 1.5. The new problem: ndiswrapper compiled and installed fine. When I try to load the module, system messages show that it loads, then fails with an error that it doesn't match the installed driver, 1.1. I am guessing this might be because I had originally installed the SuSE 9.3 ndiswrapper 1.1 rpm, although I later uninstalled it with Yast. Does this seem to be a reasonable hypothesis? If so, what can I do about it? Unfortunately, since that machine is not connected to the network, I can't send the exact message text. Thanks Corvin __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com
On Wed, 2005-11-02 at 21:55 -0800, Corvin Russell wrote:
I emailed support@linuxant.com and they claimed to be unaware of the problem (although a quick google shows they've replied to emails outlining this problem since SuSE 9.1 at least) and didn't really give much in the way of helpful suggestions. So I uninstalled Linuxant, and installed ndiswrapper 1.5.
The new problem: ndiswrapper compiled and installed fine. When I try to load the module, system messages show that it loads, then fails with an error that it doesn't match the installed driver, 1.1. I am guessing this might be because I had originally installed the SuSE 9.3 ndiswrapper 1.1 rpm, although I later uninstalled it with Yast. Does this seem to be a reasonable hypothesis? If so, what can I do about it?
Unfortunately, since that machine is not connected to the network, I can't send the exact message text.
Is there any reason you are not using the ndiswraper package that came with the SuSE version you installed (you don't say what it is). -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
participants (3)
-
Corvin Russell -
Ken Schneider -
Sid Boyce