Had success last night, got connected at the place where I have
access to a fairly weak signal. I used iwconfig with an explicit
essid, which required a bit of being devious as the essid name is
"shutup!" getting that ! in there requires some trickery with
Linux. Could not connect to the other
So you don't see anything that would prevent it from associating with
an AP? Any suggestions on how to find out why it won't associate?
Looks like iwconfig doesn't have any verbose options.
jhhaynes at earthlink dot net
___
ath5k-users mailing list
Tonight I went to where there is an access point I can use and tried
again. This PC and wireless card have worked before under Linux, but
I'm not sure if it was the same driver version. First I verified
that it would work under Windows. It did, although the signal is
weak and it would drop out s
On Tue, 2 Mar 2010, Pavel Roskin wrote:
>
> You cannot expect association to a WPA enabled access point without
> using wpa_supplicant.
OK, that's just what was on the air in my home neighborhood. I'll have
to report again when I get a chance to test at the site where it should
have worked.
__
Thanks. NetworkManager is installed but is turned off - its daemon
does not run, and the network device is not marked as controlled
by Network Manager.
The access point I'm testing with is in a building across town, so
will take me a while to repeat the tests. But the exact error
message is "not
I have a laptop with an ath5k PCMCIA card. I don't use it very often,
but it has worked in the past. When I use it I do everything by hand:
ifconfig UP, iwlist scan, iwconfig, and dhclient.
Tonight I was trying to use it and iwlist scan would show an unencrypted
access point but when I would use
What I mean is, I tried the essid argument with a legitimate essid
and I tried the ap with a legitimate ap address.
I remember having to use ap one time because I was in a motel
with several access points that had the same essid, and if I
didn't specify the ap it would seem to connect to one that
It's been a year or so since I tried to get ath5k to work in a Ubuntu
system. I didn't use NetManager but tried to bring the network up by
hand. First ifconfig wlan0 up, then iwlist wlan0 scan, then
iwconfig wlan0 essid "name of the network" and that last command is
what failed - I would do iwc
I'm on a Fedora system, and I don't have wlanconfig, but my usual ritual
is
/sbin/ifconfig wlan0to see if it is there and UP
/sbin/iwconfig wlan0 essid "name" where name is the access point name
I got from scanning
/sbin/dhclient wlan0
and it comes up and works.
_
(in case anyone cares)
I'm on the way home from a trip where I used ath5k under Fedora 8 (two
different kernels) on a laptop with a D-Link PCMCIA card that lists as
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213
Multiprotocol MAC/baseband processor (rev 01)
I gave up hav
Thanks for telling me exactly what to do. I need that. The change
you suggested, changing /etc/sysconfig/network-scripts/ifcfg-wlan0
so the MODE is managed rather than master gets rid of the error message.
Now the next hurdle is getting it to work on bootup, if that is an
appropriate goal. Afte
System is Fedora 8, kernel is 2.6.24.5-85.fc8
lspci shows 03:00.0 Ethernet controller: Atheros Communications, Inc.
AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
If I bring up the wlan0 interface by hand: ifconfig, iwconfig, dhclient
then it works. If the system tries to bring it
On Thu, 17 Apr 2008, Bjørn Mork wrote:
Googling for the pci id got me http://madwifi.org/ticket/198 which seems
to suggest that it's a hardware compatibility problem. Is this an old
(pre PCI 2.2) PC?
I don't know - it's a second-hand (or more) machine, and has some kind
of Soyo motherboard -
This relates to the youngster I am trying to help get into Linux
and get networking going. I reported earlier we are using the
Netgear WPN311 wireless PCI card. Here is what lspci -vn -d 168c:
reports:
00:0c.0 0200: 168c:ff16 (rev 01)
Flags: busmaster, medium devsel, latency 32, IRQ11
Tonight I took my laptop with its D-Link WNA-2330 to a place where there
is a live access point. It's running Fedora 8 with all the updates, and
the ath5k module. It booted up and got an IP address and the network
worked.
I don't know what it would have done if there had been more than one
wifi
Working with my laptop running Fedora 8, latest kernel 2.6.24.4-64
and the D-Link wireless card.
During bootup it says
Bringing up interface wlan0
Determining IP information for wlan0
which fails because there isn't an access point at the moment.
The question is, what is it doing when
On Wed, 2 Apr 2008, Pavel Roskin wrote:
> On Tue, 2008-04-01 at 21:59 -0500, Jim Haynes wrote:
>> I'm trying to help a youngster get into Linux. The system is Fedora 8
...
Will check what you suggested, next time I get with him.
>> The router in his house is Belkin
>&g
I'm trying to help a youngster get into Linux. The system is Fedora 8
with all the current updates, kernel is 2.6.24.3-50. The wi-fi
hardware is Netgear WPN311. The router in his house is Belkin
something-or-other. We got it to come up under Windows 2000.
The ath5k module gets loaded and creat
18 matches
Mail list logo
