LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 08-17-2005, 10:49 AM   #1
username-inuse
LQ Newbie
 
Registered: Apr 2005
Location: Kent, England, UK
Distribution: Red Hat 9, Knoppix HD install, Gentoo (Just about installed :P)
Posts: 12

Rep: Reputation: 0
ACX100 with a U.S.Robotics Model 5410


Ok, I have researched my new wi-fi card (U.S. Robotics Model 5410) and I know its chipset and it is meant to be supported by the acx100 driver. So after downloading the .tar.bz2 and compiling I go to run the ./start_net. I am greeted by all the write messages until association. Here is what is printed out...

Quote:
linux:/home/Modzilla/acx100-0.2.0pre8_plus_fixes_57/scripts # ./start_net
wlan0 deconfigured, module unloaded.
using wlan0.
Module successfully inserted.
Setting rate to 11M auto.
Setting channel 6.
Going to try to join or setup ESSID any.
Setting mode to Managed.
Waiting for association...10 9 8 7 6 5 4 3 2 1 FAILED.
Error: wlan0 failed to associate, can't use DHCP for IP address.
Interface has been set up successfully.
Setting mtu down to 576. NOTE that e.g. IPv6 would need >= 1280, so make sure you're doing the right thing here!
linux:/home/Modzilla/acx100-0.2.0pre8_plus_fixes_57/scripts #
My distro is Suse 9.0 and has a kernel version of 2.41.21. These are the variables in my start_net script:

Quote:
#!/bin/bash

#########################################
# start_net script #
# acx100 project #
# acx100.sourceforge.net #
# edited by arnie <urnotwelcome@gmx.de> #
#########################################
# with modifications by craig #
# summary at end of file #
#########################################

# Please edit below

# syntax is: VARIABLENAME=VALUE, with _no_ spaces in between
# make sure to _preserve_ any double-quotes (")
# text beginning with the comment delimiter (#) is ignored
# make sure to _preserve_ at least one space before any
# comment delimiters (#) that do not begin a line
# "uncommenting" a line means to remove it's leading "#" character

ESSID=any # THIS IS CASE SeNsItIvE!! any == associate to any ESSID
# Default rate configured as 11Mbps to not cause speed problems (while
# using auto rate) or connection problems (while not using auto rate)
# with non-22Mbps hardware...
RATE=11M
AUTORATE=1 # only disable auto rate if you know what you're doing...
CHAN=6 # it's useful to try to stick to channels 1, 6 or 11 only, since these don't overlap with other channels
#SHORTPREAMBLE=1 # set a value of 1 in order to force "Short Preamble" (incompatible with very old WLAN hardware!) instead of peer autodetect
#TXPOWER=20 # 0..20 (dBm) (18dBm is firmware default) overly large setting might perhaps destroy your radio eventually!
MODE=Managed # Managed for infrastructure, Ad-hoc for peer-to-peer. NOTE: Auto mode is not supported any more, you HAVE to select a specific mode!
DEBUG=0xb # 0xffff for maximum debug info, 0 for none

# WEP Key(s)
# ascii keys (passphrase) should look like this: KEY="s:asciikey"
# hex keys should look like this: KEY="4378c2f43a"

# most wep users will want to use this line
#KEY=""

# alternatively, you can uncomment and use these lines to
# set all 4 possible WEP keys
#KEY1="1234567890" #WEP64
#KEY2="1234567890"
#KEY3="1234567890"
#KEY4="1234567890"
# you must select which of the 4 keys above to use here:
#KEY="[1]" # for KEY1, "[2]" for KEY2, etc

ALG=open # open == Open System, restricted == Shared Key

#IP address

USE_DHCP=1 # set to 1 for auto configuration instead of fixed IP setting

IP=192.168.1.98 # set this if you did not set USE_DHCP=1
NETMASK=255.255.255.0 # set this if you did not set USE_DHCP=1
GATEWAY=192.168.1.254 # set this if you did not set USE_DHCP=1

LED_OFF=0 # set to 1 to turn off the power LED to save power

MTU_576=1 # set to 1 if you have buffer management problems

# DO NOT EDIT BELOW THIS LINE
##################################################################
Installation went with no problems, just untarred the archive, then make and make install (as su). Then checked the setting with my router.

I checked the HCL here and got this specific card up but the guide it suggests reading doesnt really help now I have this problem.

I got the firmware from the guide, I cant find one for this specific card so I assume this was a generic one.

My current network layout is a router (so its a managed network and the router has a dhcpd) that assignes my IP through DHCP. Then its to this laptop.

Any help would be appreciated!
Thanks!
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ndiswrapper doesn't work for US Robotics USR 5410 and Linksys WPC 54G dangolrk Linux - Wireless Networking 10 05-16-2005 05:45 PM
suse 9.2 and U.S Robotics 5410 problems serefarikan Linux - Wireless Networking 1 01-04-2005 08:12 AM
U.S. Robotics 5410 Wireless PCMCIA card Redhat 9 support sg47 Linux - Wireless Networking 1 04-20-2004 01:03 PM
US Robotics model 0701 If6was9 Linux - Hardware 0 08-10-2003 01:42 PM
External US Robotics model 5668 alrawab Linux - Hardware 2 01-03-2003 05:17 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 02:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration