Devon Harding wrote:
On Sat, Aug 23, 2008 at 1:13 PM, max <maximilianbianco@xxxxxxxxx> wrote:
Devon Harding wrote:
On Sat, Aug 23, 2008 at 12:58 PM, max <maximilianbianco@xxxxxxxxx> wrote:
Devon Harding wrote:
2008/8/23 Anne Wilson <cannewilson@xxxxxxxxxxxxxx>
On Saturday 23 August 2008 16:26:06 Devon Harding wrote:
On Fri, Aug 22, 2008 at 11:44 PM, Brian Powell <bpowell01@xxxxxxxxx>
wrote:
Devon,
Make sure you have the wpa_supplicant package installed.
The wpa_supplicant package is installed (and the update). When I
select
my
wireless from the drop down list, it still asks for a WEP key instead
of
a
WPA key.
Do I need the wpa_supplicant_gui package too?
I see the same behaviour on my EeePC. It does no harm, but it's
b******
annoying. (I presume that, like me, you can use the drop-down arrow to
select WPA then manually give it the passphrase?)
Anne
The thing is, WPA is not one of the choices. I only have the
following:
WEP 128-bit Passphrase
WEP 40/128-bit Hexadecimal
WEP 40/128-bit ASCII
LEAP
Dynamic WEP (802.1x)
Have you tried an older kernel? I have seen some weird stuff with
wireless on the latest but it may be something else going on there.
What kind of wireless device are you working with?
--
Fortune favors the BOLD
--
I tried Ubuntu (Hardy) and got the same thing. If I choose 'Connect to
other wireless network' I do see the option for WPA, but it doesn't seems
to connect to my access point.
-Devon
But what wireless card are you using? I suspect your problem may be
there, its a possibility to explore anyway.
from a terminal as root:
root@localhost# lspci -v
it will produce a lot of output , look for the wireless device it should be
obviously labeled
Here's the output:
00:12.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
Subsystem: Fujitsu Limited. Unknown device 1169
Flags: medium devsel, IRQ 9
Memory at e8013000 (32-bit, prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: hostap_pci
Kernel modules: orinoco_pci, hostap_pci
Some googling around shows you are not the only one with an issue with
this particular chipset.
It says its using the hostap_pci driver but lists orinco_pci and
hostap_pci as modules. I am thinking that perhaps both are getting
loaded and its unclear to me if you actually need both it could be that
hostap_pci depends on the orinco_pci. Lets see if we can find out.
Try this as root:
lsmod | grep orinco_pci
lsmod | grep hostap_pci
A generic example of what I mean:
[root@localhost ~]# lsmod | grep sata_nv
sata_nv 31624 3
libata 149664 4 pata_amd,sata_nv,pata_acpi,ata_generic
libata is used by sata_nv and others so if I tried to unload libata I
would run into a dependency issue
See what the commands return and post here. You may also want to check
dmesg for output related to your wireless device. Something like this
from a terminal as root:
dmesg
Will dump more than you need or you can refine your search with grep
dmesg | grep <your search term>
dmesg | grep -i <your search term> * the -i option makes it case
insensitive see man page for more detail or the info page
dmesg | grep 00:12.0 *may provide us with meaningful output
--
Fortune favors the BOLD
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
