I'm pretty new to Linux, but have had a bit of functional tutoring...

...i'm triple booting my old Dimension 8400. Have been running with Jackalope and XP for some time now and wanted to install Lynx and get a good handle on it before i completely wipe my other machine (Win7/Jackalope) and install it there.

Installed Lynx from a USB stick and all seems well, it recognises the UBS wireless and all available connections but just sits and spins on the password login and never connects...hmmm. I have tried all possible combinations of rebooting with the USB connected/disconnected/connecting after... to no avail.

The wireless seems to "work out of the box" just as seamlessly as it did for Jackalope, all the steps are similar, it just never connects...

...and i'm at a total loss. Any help would be greatly appreciated. Thanks.

Using the usb stick - enter

iwconfig

and copy the bit about your wireless thing here.

not sure exactly what you mean by using the USB wireless, i assume having it plugged in is what you mean... when i enter the "iwconfig" into terminal it tells me ...

lo: no wireless extensions
etho: no wireless extensions
wlano: IEEE 802.11BGN ESSID: "Hood Hub"
mode: managed
frequency: 2.437 GHz
access point: not associated
Tx-power 13dbm
retry limit: 7
RTS thr: off
fragment thr: off
power management: on

Hood Hub is the wireless connection i'm trying to connect to... late yesterday i was monkeying with it and changed the security from WPA & WPA2 personal (was set to this default in Lynx and is also the setting i use for Jackalope) to WEP 128-bit passphrase on a whim. The connection "connected" and said 100% and all, but the browser wouldn't open a page. When i go in to edit connections and view the wireless connections it states that it was connected yesterday as opposed to "never" as it said before... frustrating.

Hi,

'Wireless Drivers in Ubuntu Linux & Linux Mint How-to setup Tutorial' is a video tutorial that may help.

Trial the connection without wpa or wep of any kind.

Please confirm that etho and wlano are correct or typos :- they are usually eth0 and wlan0

same thing without wpa or wep at all. Yes eth0 and wlan0 are corerect, lazy fingers, sorry.

What? Same as:???

Presumably you don't get the password part?

Then you'll want to look at dmesg output right after you have failed a connection.