Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 31 Oct 2014, 05:54
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
How to use GMYLE USB wireless 11N adapter in Lucid 5.2.8?
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 1 of 1 Posts_count  
Author Message
karm2865


Joined: 20 Mar 2011
Posts: 57

PostPosted: Thu 19 Jul 2012, 13:27    Post_subject:  How to use GMYLE USB wireless 11N adapter in Lucid 5.2.8?  

RTL8192CU_8188CUS_8188CE-VAU_linux_v3
for
Kernel Linux 2.6.33.2 (i686) lucid puppy 5.2.8

My house mate gave me this USB wireless 11N USB adapter i have searched for the driver for a wile i have gotten close found some for other Kernels but not for the one i am using

so far my attempts at installing it my self have not worked


RTL8192CU_8188CUS_8188CE-VAU_linux_v3
it can be found here:
http://driverscollection.com/?aid=43572587289319e911d6511c913


Computer [because some one always ask if i don't include this]:

Processor 2x AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
Memory 3114MB (332MB used)
User Name root (root)
Date/Time Thu 19 Jul 2012 11:33:03 AM CDT
Display
Resolution 1440x900 pixels
OpenGL Renderer Software Rasterizer
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter CA0106 - CA0106
Audio Adapter HDA-Intel - HD-Audio Generic
Input Devices
AT Translated Set 2 keyboard
Power Button
Power Button
HP WMI hotkeys
PC Speaker
Logitech Trackball
Belkin Belkin n52te
Belkin Belkin n52te
Printers (CUPS)
CUPS-PDF
pdf_writer Default
SCSI Disks
ATA ST3200826AS
HL-DT-ST DVDRAM GH22NS50
ATA ST380815AS
Generic External
Generic USB SD Reader
Generic USB CF Reader
Generic USB SM Reader
Generic USB MS Reader
Operating System
Version
Kernel Linux 2.6.33.2 (i686)
Compiled #1 SMP Thu May 27 10:56:32 EST 2010
C Library GNU C Library version 2.12.1 (stable)
Default C Compiler GNU C Compiler version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Current Session
Computer Name puppypc
User Name root (root)
Home Directory /root
Desktop Environment Unknown (Window Manager: )
Misc
Uptime 41 minutes
Load Average 0.07, 0.06, 0.07
Kernel Modules
Loaded Modules
r8192s_usb Linux driver for Realtek RTL8192 USB WiFi cards
nls_utf8
joydev Joystick device interfaces
ohci_hcd USB 1.1 'Open' Host Controller (OHCI) Driver
ssb Sonics Silicon Backplane driver
wl
lib80211 common routines for IEEE802.11 drivers
iptable_mangle iptables mangle table
iptable_nat
nf_nat
ipt_REJECT Xtables: packet "rejection" target for IPv4
nf_conntrack_ftp ftp connection tracking helper
nf_conntrack_irc IRC (DCC) connection tracking helper
iptable_filter iptables filter table
xt_state ip[6]_tables connection tracking state match module
nf_conntrack_ipv4
nf_conntrack
nf_defrag_ipv4
ip_tables IPv4 packet filter
fbcon
tileblit Tile Blitting Operation
font Console Fonts
bitblit Bit Blitting Operation
softcursor Generic software cursor
serio_raw Raw serio driver
snd_hda_codec_atihdmi ATI HDMI HD-audio codec
snd_hda_intel Intel HDA driver
snd_hda_codec HDA codec core
snd_ca0106 CA0106
snd_ac97_codec Universal interface for Audio Codec '97
ac97_bus
snd_pcm_oss PCM OSS emulation for ALSA.
snd_mixer_oss Mixer OSS emulation for ALSA.
snd_pcm Midlevel PCM code for ALSA.
snd_seq_dummy ALSA sequencer MIDI-through client
snd_seq_oss OSS-compatible sequencer module
snd_seq_midi Advanced Linux Sound Architecture sequencer MIDI synth.
snd_rawmidi Midlevel RawMidi code for ALSA.
snd_seq_midi_event MIDI byte <-> sequencer event coder
snd_seq Advanced Linux Sound Architecture sequencer.
snd_timer ALSA timer interface
snd_seq_device ALSA sequencer device management
snd Advanced Linux Sound Architecture driver for soundcards.
soundcore Core sound module
snd_page_alloc Memory allocator for ALSA system.
tg3 Broadcom Tigon3 ethernet driver
pcspkr PC Speaker beeper driver
sg SCSI generic (sg) driver
k8temp AMD K8 core temperature monitor
hwmon hardware monitoring sysfs/class support
i2c_piix4 PIIX4 SMBus driver
i2c_core I2C-Bus main module
shpchp Standard Hot Plug PCI Controller Driver
pci_hotplug PCI Hot Plug PCI Core
ati_agp
agpgart AGP GART driver
hp_wmi HP laptop WMI hotkeys driver
rfkill RF switch support
wmi ACPI-WMI Mapping Driver
ppdev
parport_pc PC-style parallel port driver
parport
thermal ACPI Thermal Zone Driver
evdev Input driver event char devices
button ACPI Button Driver
processor ACPI Processor Driver
fuse Filesystem in Userspace
aufs aufs -- Advanced multi layered unification filesystem
nls_iso8859_1
nls_cp437
usbhid USB HID core driver
usb_storage USB Mass Storage driver for Linux
squashfs squashfs 4.0, a compressed read-only filesystem
ehci_hcd USB 2.0 'Enhanced' Host Controller (EHCI) Driver
usbcore
floppy
Boots
Boots

Languages
Available Languages
Filesystems
Mounted File Systems
rootfs / 37.83 % (5.7 GiB of 9.1 GiB)
/dev/sdb2 /initrd/mnt/dev_save 91.84 % (997.3 MiB of 11.9 GiB)
/dev/loop1 /initrd/pup_rw 37.83 % (5.7 GiB of 9.1 GiB)
/dev/loop0 /initrd/pup_ro2 100.00 % (0.0 B of 287.4 MiB)
/dev/loop4 /initrd/pup_ro4 100.00 % (0.0 B of 156.8 MiB)
/dev/loop5 /initrd/pup_ro5 100.00 % (0.0 B of 49.6 MiB)
/dev/loop6 /initrd/pup_ro6 100.00 % (0.0 B of 49.4 MiB)
/dev/loop7 /initrd/pup_ro7 100.00 % (0.0 B of 26.8 MiB)
unionfs / 37.83 % (5.7 GiB of 9.1 GiB)
tmpfs /tmp 0.06 % (759.9 MiB of 760.3 MiB)
shmfs /dev/shm 0.02 % (681.1 MiB of 681.2 MiB)
/dev/sr0 /mnt/sr0 100.00 % (0.0 B of 44.6 MiB)
Display
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.7.6
Monitors
Monitor 0 1440x900 pixels
Extensions
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
RANDR
RECORD
RENDER
SECURITY
SGI-GLX
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
OpenGL
Vendor Mesa Project
Renderer Software Rasterizer
Version 1.4 (2.1 Mesa 7.7.1)
Direct Rendering No
Environment Variables
Environment Variables
HOSTNAME puppypc
XDG_DATA_HOME /root/.local/share
SHELL /bin/bash
TERM xterm
HISTSIZE 1000
QT_XFT true
DEFAULTDRAW inkscapelite
XLIB_SKIP_ARGB_VISUALS 1
HISTFILESIZE 2000
USER root
LD_LIBRARY_PATH /lib:/usr/lib:/usr/X11R7/lib:/root/my-applications/lib
GDK_USE_XFT 1
RGBDEF /usr/share/X11/rgb.txt
DEFAULTIMAGEVIEWER viewnior
OOO_FORCE_DESKTOP gnome
DEFAULTPAINT mtpaint
MOZ_DISABLE_PANGO 1
MOZ_PLUGIN_PATH /usr/lib/mozilla/plugins
XDG_CONFIG_DIRS /etc/xdg
DEFAULTBROWSER chromium
PATH /bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin
DEFAULTMEDIAPLAYER gnome-mplayer
LC_COLLATE en_US
DEFAULTIMAGEEDITOR mtpaint
INPUTRC /etc/inputrc
PWD /root
EDITOR mp
LANG en_US
XFINANSDIR /root/.xfinans
HISTCONTROL ignoredups
DEFAULTSPREADSHEET gnumeric
DEFAULTHTMLEDITOR mozedit
SHLVL 1
HOME /root
XDG_CONFIG_HOME /root/.config
XDG_CACHE_HOME /root/.cache
G_FILENAME_ENCODING @locale
LOGNAME root
PREFIX /usr
XDG_DATA_DIRS /usr/share:/usr/local/share
PKG_CONFIG_PATH /usr/lib/pkgconfig
WINDOWPATH 4
DISPLAY :0
MM_RUNASROOT 1
DEFAULTWORDPROCESSOR abiword
DEFAULTTEXTEDITOR geany
Users
Users
root root
daemon
nobody
spot Linux User
bin bin
messagebus Linux User
ftp Linux User
haldaemon Hardware abstraction layer
uucp uucp
sshd sshd
webuser Linux User
Devices

Processor
Processors
AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ 2393.77MHz
AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ 2393.77MHz
Memory
Memory
Total Memory 3114352 kB
Free Memory 1976300 kB
Buffers 56936 kB
Cached 806624 kB
Cached Swap 0 kB
Active 341188 kB
Inactive 740892 kB
Active(anon) 223104 kB
Inactive(anon) 0 kB
Active(file) 118084 kB
Inactive(file) 740892 kB
Unevictable 0 kB
Mlocked 0 kB
High Memory 2235108 kB
Free High Memory 1205776 kB
Low Memory 879244 kB
Free Low Memory 770524 kB
Virtual Memory 0 kB
Free Virtual Memory 0 kB
Dirty 96 kB
Writeback 0 kB
AnonPages 218532 kB
Mapped 62816 kB
Shmem 4588 kB
Slab 42196 kB
SReclaimable 28448 kB
SUnreclaim 13748 kB
KernelStack 1104 kB
PageTables 4072 kB
NFS_Unstable 0 kB
Bounce 0 kB
WritebackTmp 0 kB
CommitLimit 1557176 kB
Committed_AS 2025272 kB
VmallocTotal 122880 kB
VmallocUsed 4260 kB
VmallocChunk 111372 kB
DirectMap4k 8184 kB
DirectMap4M 901120 kB
PCI Devices
PCI Devices
Host bridge ATI Technologies Inc RS480 Host Bridge (rev 10)
PCI bridge ATI Technologies Inc RS480 PCI-X Root Port (prog-if 00 [Normal decode])
PCI bridge ATI Technologies Inc RS480 PCI Bridge (prog-if 00 [Normal decode])
SATA controller ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
USB Controller ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10 [OHCI])
USB Controller ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10 [OHCI])
USB Controller ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10 [OHCI])
USB Controller ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10 [OHCI])
USB Controller ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10 [OHCI])
USB Controller ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20 [EHCI])
SMBus ATI Technologies Inc SBx00 SMBus Controller (rev 13)
IDE interface ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
ISA bridge ATI Technologies Inc SB600 PCI to LPC Bridge
PCI bridge ATI Technologies Inc SBx00 PCI to PCI Bridge (prog-if 01 [Subtractive decode])
Host bridge Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Host bridge Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Host bridge Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Host bridge Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
VGA compatible controller ATI Technologies Inc Manhattan [Mobility Radeon HD 5430 Series] (prog-if 00 [VGA controller])
Audio device ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
Multimedia audio controller Creative Labs CA0106 Soundblaster
Ethernet controller Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)


USB Devices
USB Devices
OHCI Host Controller
OHCI Host Controller
USB Reader
OHCI Host Controller
Trackball
OHCI Host Controller
OHCI Host Controller
EHCI Host Controller
[size=18]External
802.11n WLAN
Adapter [/size]
Printers
Printers (CUPS)
CUPS-PDF
pdf_writer Default
Battery
No batteries
No batteries found on this system
Sensors
Cooling Fans
Temperatures
temp1 34.00°C
Voltage Values
Input Devices
Input Devices
AT Translated Set 2 keyboard
Power Button
Power Button
HP WMI hotkeys
PC Speaker
Logitech Trackball

Storage
SCSI Disks
ATA ST3200826AS
HL-DT-ST DVDRAM GH22NS50
ATA ST380815AS
Generic External
Generic USB SD Reader
Generic USB CF Reader
Generic USB SM Reader
Generic USB MS Reader
DMI
BIOS
Date 04/18/2007
Vendor Hewlett-Packard (www.hp.com)
Version 786E3 v02.22
Board
Name 0A64h
Vendor Hewlett-Packard (www.hp.com)
Resources
I/O Ports
0000-001f dma1
0020-0021 pic1
0040-0043 timer0
0050-0053 timer1
0060-0060 keyboard
0064-0064 keyboard
0070-0077 rtc
0080-008f dma page reg
00a0-00a1 pic2
00c0-00df dma2
00f0-00ff fpu
0170-0177 ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
0170-0177 ahci
01f0-01f7 ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
01f0-01f7 ahci
0376-0376 ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
0376-0376 ahci
0378-037a parport0
03c0-03df vga+
03f2-03f2 floppy
03f4-03f5 floppy
03f6-03f6 ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
03f6-03f6 ahci
03f7-03f7 floppy
03f8-03ff serial
0400-041f pnp 00:0e
0420-043f pnp 00:0e
0440-045f pnp 00:0e
0460-047f pnp 00:0e
0480-048f pnp 00:0e
04d0-04df pnp 00:0d
0800-081f pnp 00:0e
0820-083f pnp 00:0e
0840-085f pnp 00:0e
0860-087f pnp 00:0e
0860-0861 ACPI PM1b_CNT_BLK
0c00-0c1f pnp 00:0e
0c50-0c6f pnp 00:0e
0cd0-0cdf pnp 00:0e
0cf8-0cff PCI conf1
1000-1fff PCI Bus 0000:07
1100-111f Creative Labs CA0106 Soundblaster
1100-111f CA0106
2000-2fff PCI Bus 0000:02
2100-21ff ATI Technologies Inc Manhattan [Mobility Radeon HD 5430 Series] (prog-if 00 [VGA controller])
3100-310f ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
3100-310f ahci
3120-312f ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
3120-312f pata_atiixp
3140-3147 ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
3140-3147 pata_atiixp
3148-314f ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
3148-314f pata_atiixp
3158-315b ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
3158-315b pata_atiixp
315c-315f ATI Technologies Inc SB600 IDE (prog-if 8f [Master SecP SecO PriP PriO])
315c-315f pata_atiixp
f800-f81f pnp 00:0e
f800-f803 ACPI PM1a_EVT_BLK
f804-f805 ACPI PM1a_CNT_BLK
f808-f80b ACPI PM_TMR
f810-f815 ACPI CPU throttle
f820-f83f pnp 00:0e
f828-f82f ACPI GPE0_BLK
f840-f85f pnp 00:0e
f860-f87f pnp 00:0e
fa00-fa3f pnp 00:0e
fc00-fc0f ATI Technologies Inc SBx00 SMBus Controller (rev 13)
fc00-fc07 piix4_smbus
fe00-fe7f pnp 00:0e
fe80-feff pnp 00:0e
Memory
00000000-0009fbff System RAM
0009fc00-0009ffff reserved
000a0000-000bffff Video RAM area
000c0000-000ce7ff Video ROM
000ce800-000cf7ff Adapter ROM
000cf800-000d13ff Adapter ROM
000d1400-000e3fff pnp 00:0f
000e8000-000fffff reserved
000f0000-000fffff System ROM
00100000-bfeb7eff System RAM
01000000-0128d935 Kernel code
0128d936-013c62df Kernel data
0141d000-0144c743 Kernel bss
bfeb7f00-bfffffff reserved
c0000000-d01fffff PCI Bus 0000:02
c0000000-cfffffff ATI Technologies Inc Manhattan [Mobility Radeon HD 5430 Series] (prog-if 00 [VGA controller])
d0000000-d001ffff ATI Technologies Inc Manhattan [Mobility Radeon HD 5430 Series] (prog-if 00 [VGA controller])
d0200000-d04fffff PCI Bus 0000:02
d0400000-d041ffff ATI Technologies Inc Manhattan [Mobility Radeon HD 5430 Series] (prog-if 00 [VGA controller])
d0420000-d0423fff ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
d0420000-d0423fff ICH HD audio
d0500000-d07fffff PCI Bus 0000:3f
d0500000-d050ffff Broadcom Corporation NetXtreme BCM5755 Gigabit Ethernet PCI Express (rev 02)
d0500000-d050ffff Broadcom Tigon3 ethernet driver
d0a04000-d0a04fff ATI Technologies Inc SB600 USB (OHCI0) (prog-if 10 [OHCI])
d0a04000-d0a04fff USB 1.1 'Open' Host Controller (OHCI) Driver
d0a05000-d0a05fff ATI Technologies Inc SB600 USB (OHCI1) (prog-if 10 [OHCI])
d0a05000-d0a05fff USB 1.1 'Open' Host Controller (OHCI) Driver
d0a06000-d0a06fff ATI Technologies Inc SB600 USB (OHCI2) (prog-if 10 [OHCI])
d0a06000-d0a06fff USB 1.1 'Open' Host Controller (OHCI) Driver
d0a07000-d0a07fff ATI Technologies Inc SB600 USB (OHCI3) (prog-if 10 [OHCI])
d0a07000-d0a07fff USB 1.1 'Open' Host Controller (OHCI) Driver
d0a08000-d0a08fff ATI Technologies Inc SB600 USB (OHCI4) (prog-if 10 [OHCI])
d0a08000-d0a08fff USB 1.1 'Open' Host Controller (OHCI) Driver
d0a09000-d0a093ff ATI Technologies Inc SB600 Non-Raid-5 SATA (prog-if 01 [AHCI 1.0])
d0a09000-d0a093ff ahci
d0a09400-d0a094ff ATI Technologies Inc SB600 USB Controller (EHCI) (prog-if 20 [EHCI])
d0a09400-d0a094ff USB 2.0 'Enhanced' Host Controller (EHCI) Driver
e0000000-efffffff reserved
e0000000-efffffff pnp 00:0f
e0000000-e40fffff PCI MMCONFIG 0000 [bus 00-40]
fec00000-fed3ffff reserved
fec00000-fec003ff IOAPIC 0
fec01000-fecfffff pnp 00:0f
fed00000-fed003ff HPET 0
fed00400-fed3ffff pnp 00:0f
fed45000-ffffffff reserved
fed45000-ffffffff pnp 00:0f
fee00000-fee00fff Local APIC
DMA
2 floppy
4 cascade
rtl8192_8188CU_linux_v3.0.1590.20110511.tar.gz
Description 
gz

 Download 
Filename  rtl8192_8188CU_linux_v3.0.1590.20110511.tar.gz 
Filesize  837.42 KB 
Downloaded  336 Time(s) 
Back to top
View user's profile Send_private_message 
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 11128
Location: Arizona USA

PostPosted: Thu 19 Jul 2012, 16:30    Post_subject:  

You need to tell us the brand and model of the USB adapter, as it is entirely possible that the drivers you list will not work with whatever it is.
Back to top
View user's profile Send_private_message 
karm2865


Joined: 20 Mar 2011
Posts: 57

PostPosted: Thu 19 Jul 2012, 18:48    Post_subject:  

it is a
GMYLE USB wireless 11N USB adapter

the manufacturer website page

http://www.gmyle.com/product_p/2827.htm

the driver i attached is the one that came with it there is a lot of info on the min DVD that don't understand. I have absolutely no ideal what i am doing i just fallow the instructions that came with the USB dongle thing and it dose not work.

so i looked on the web and did not find any thing that worked so before i throw it in the trash like the other wireless USB dongle i tried i decided to ask hear.

it works in windows XP so i know it is just something not right with the way i am trying to do it.

this is the instructions i got

===============================================================================
Software Package - Component
===============================================================================
1. ReleaseNotes.doc

2. document/

3. driver source code

3.1 Makefile - to build the modules

3.2 Script and configuration for DHCP:
"wlan0dhcp"
"ifcfg-wlan0"

3.3 Example of supplicant configuration file:
"wpa1.conf"

3.4 Script to run wpa_supplicant
"runwpa"

3.5 Script to clean relative modules
"clean"

4. wpa_supplicant/wpa_supplicant-0.6.9_wps_patch_20100201.zip
The tool help the wlan network to communicate under the
protection of WPAPSK mechanism (WPA/WPA2) and add WPS patch

5. install.sh
Script to easy make 8192cu driver.

==================================================================================================================
User Guide(1) - connecting wireless networking using "Network Manager" GUI utility (For PC Linux)
==================================================================================================================
(1) Network Manager is a utility attempts to make use of wireless networking easy.

(2) Notes: if you want to use the following command-line method to connect wireless networking,
please disable the "Network Manager", because "Network Manager" will conflict with method of command line .

==================================================================================================================
User Guide(2) - Using the wpa_cli & wpa_supplicant tools (For embedded Linux)
==================================================================================================================

Please refer to the document/wpa_cli_with_wpa_supplicant_20091227.doc

==================================================================================================================
User Guide(3) - Set wireless lan MIBs in Command Line (Legacy command - Not recommend)
==================================================================================================================
This driver uses Wireless Extension as an interface allowing you to set
Wireless LAN specific parameters.

Current driver supports "iwlist" to show the device status of nic
iwlist wlan0 [parameters]
where
parameter explaination [parameters]
----------------------- -------------
Show available chan and freq freq / channel
Show and Scan BSS and IBSS scan[ning]
Show supported bit-rate rate / bit[rate]

For example:
iwlist wlan0 channel
iwlist wlan0 scan
iwlist wlan0 rate

Driver also supports "iwconfig", manipulate driver private ioctls, to set
MIBs.

iwconfig wlan0 [parameters] [val]
where
parameter explaination [parameters] [val] constraints
----------------------- ------------- ------------------
Connect to AP by address ap [mac_addr]
Set the essid, join (I)BSS essid [essid]
Set operation mode mode {Managed|Ad-hoc}
Set keys and security mode key/enc[ryption] {N|open|restricted|off}

For example:
iwconfig wlan0 essid "ap_name"
iwconfig wlan0 ap XX:XX:XX:XX:XX:XX
iwconfig wlan0 mode Ad-hoc
iwconfig wlan0 essid "name" mode Ad-hoc
iwconfig wlan0 key 0123456789 [2] open
iwconfig wlan0 key off
iwconfig wlan0 key restricted [3] 0123456789
Note: Better to set these MIBS without GUI such as NetworkManager and be sure that our
nic has been brought up before these settings. WEP key index 2-4 is not supportted by
NetworkManager.

===============================================================================
Getting IP address (For User Guide(2) & User Guide(3))
===============================================================================
After start up the nic and connect to AP successfully, the network needs to obtain an IP address
before transmit/receive data.
This can be done by setting the static IP via "ifconfig wlan0 IP_ADDRESS"
command, or using DHCP.

If using DHCP, setting steps is as below:
(1)check if the WiFi had connected to an AP via "iwconfig" command
$> iwconfig

(2)run the script which run the dhclient
$> ./wlan0dhcp
or
dhcpcd wlan0
(Some network admins require that you use the
hostname and domainname provided by the DHCP server.
In that case, use
dhcpcd -HD wlan0)


===============================================================================
WPAPSK/WPA2PSK - using wpa_supplicant (For User Guide(3))
===============================================================================

Wpa_supplicant helps to secure wireless connection with the protection of
WPAPSK/WPA2PSK mechanism. Please refer to the document/wpa_cli_with_wpa_supplicant_20091227.doc

===============================================================================
WPS - PIN & PBC methods
===============================================================================

(*) Please refer to the document/wpa_cli_with_wpa_supplicant_20091227.doc

===============================================================================
Power Saving Mode
===============================================================================

(*) Please refer to the document/HowTo enable the power saving functionality.doc


-------------------------------------------------------------------------------------------------------
To place our driver into kernel tree and build with kernel, for example, under the folder “drivers/net/wireless/”, you can do as followings:

Copy our driver into drivers/net/wireless/ and rename it as rtl8192cu, for example.
Add obj-$(CONFIG_RTL8192CU) += rtl8192cu/ into drivers/net/wireless/Makefile:
Add source "drivers/net/wireless/rtl8192cu/Kconfig" into drivers/net/wireless/Kconfig
Config kernel, for example, with “make menuconfig” command to select y or m for our driver
Build kernel with “make” command
--------------------------------------------------------------------------------------------------------


In the WPS (WiFi Protected Setup) specification, it supports PIN and PBC.
Basically, there are two modes for WPS PBC (Pusb Button Configuration): Software PBC and hardware PBC.
About the software PBC, the wpa_supplicant and wpa_cli had supported it by using the following command,
$> wpa_cli wps_pbc

About the hardware PBC, the wpa_supplicant and wpa_cli can't detect the hardware button because this doesn't
be standardized. In order to support the hardware PBC, the customer's utility must add some codes to know
the hardware button is pressed or not.

The Realtek WiFi Linux driver is able to detect the hardware button status. First of all, the customer has
to develop an application to capture the signal sent from Realtek WiFi driver. In this package, we had provided
a sample code named "signal_handle_ex.c" for this application. In the main function of this sample code, it will
pass its pid (process id) to Realtek WiFi driver so that the driver will know the target process which it wants to
send the signal when the hardware button is pressed.

In the sample code, it registers a callback function named "HWPBC_SignalHandler" by using the signal system. When
the hardware button is pressed and the driver had detected it, the HWPBC_SignalHandler function will be called.
In the HWPBC_SignalHandler function, it should inform the wpa_supplicant to do thw WPS procedure by using the
software PBC command described above.

===================================================================================================================
Note: The Realtek WiFi driver will go to check the hardware button status per 2 seconds. So, we suggest the hardware
button should be pressed for 2 seconds to make sure the driver can detect this behavior.

--------------------------------------------------------------------------------------------------------


There are two methods to let driver into WIFI certification testing mode. Depending on your needs, you can choose one of them. The WIFI certification testing mode is only for WIFI certification.


(1) Method 1: Entering WIFI certification testing mode when you execute “insmod” command.

Adding the “wifi_spec=1” parameter when inserting driver module.

$> insmod 8192cu.ko wifi_spec=1



(2) Method 2: Modifying the configuration in the Makefile when
you compile the driver.

Editing the Makefile and set the “CONFIG_WIFI_TEST” to y, then recompiling the driver.

A Brief Introduction to RTL8192C driver Power Saving

1.) RTL8192C consists of two power modes:
A). Minimum Power Saving mode.
In this PS mode, RTL8192C wakes up every beacon interval. Figure 1 shows the RTL8192C power consumption under Minimum Power Saving mode.


Figure 1. Minimum Power Saving mode (Associated idle)















B). Maximum Power Saving mode:
When driver be set to maximum power saving mode, which means RTL8192C wake up to receive beacon when DTIM count of beacon is zero.
If DTIM period of beacon is 3 RTL8192C would wake up every 3 bacon interval. Figure 2 illustrates RTL8192C power consumption under Maximum Power Saving mode:


Figure 2. Maximum Power Saving mode (Associated idle)














2.) The following document will describe the way to let this driver to enable the power saving functionality.
===========================================================
A-1.) Power Saving Mode – by modify Makefile
===========================================================
You can easy set the power saving to Min-PS (rtw_power_mgnt=1) by modify the CONFIG_POWER_SAVING to y, at the line 20 of Makefile file.
Ex:
CONFIG_POWER_SAVING = y

===========================================================
A-2.) Power Saving Mode – by change load-time parameters
===========================================================
(1) In order to enter PS Mode, you need to add the parameter of "rtw_power_mgnt=1" when executing "insmod 8192cu.ko" :
$>insmod 8192cu.ko rtw_power_mgnt=1
or
$>insmod 8192cu.ko rtw_power_mgnt=2

(2)Parameter Notes:
rtw_power_mgnt=1 ;//enable PS, MIN_PS Mode
rtw_power_mgnt=2 ;//enable PS, MAX_PS Mode

===========================================================
B-1.) USB Autosuspend - by modify Makefile
===========================================================
You can turn on USB autosuspend function by modify the CONFIG_USB_AUTOSUSPEND to y, at the line 21 of Makefile file.
Ex:
CONFIG_USB_AUTOSUSPEND = y

===========================================================
B-1.) USB Autosuspend - by change load-time parameters
===========================================================
(1) In PS mode, you can turn on or turn off the USB autosuspend functionality by adding the following parameter.
$>insmod 8192cu.ko rtw_power_mgnt=1 enusbss = 1
or
$>insmod 8192cu.ko rtw_power_mgnt=1 enusbss = 0
or
$>insmod 8192cu.ko rtw_power_mgnt=2 enusbss = 1
or
$>insmod 8192cu.ko rtw_power_mgnt=2 enusbss = 0

(2)Parameter Notes:
enusbss = 1; // enable USB autosuspend
enusbss = 0; // default, disable USB autosuspend

===========================================================
C-1.) RF on/off detection – by modify Makefile
===========================================================
You can turn on this function by modify the CONFIG_HW_PWRP_DETECTION to y, at the line 22 of Makefile file.
Ex:
CONFIG_HW_PWRP_DETECTION = y

===========================================================
C-2.) RF on/off detection – by change load-time parameters
===========================================================
(1) If you want turn on this function in load time, you need to add the parameter of " hwpwrp_detect =1" when executing "insmod 8192cu.ko" :
$>insmod 8192cu.ko hwpwrp_detect =1

(2)Parameter Notes:
hwpwrp_detect =1 ;//enable hw power pin detection
hwpwrp_detect =0 ;//disable hw power pin detection


3.) Power consumption example
Scenario (unit: mA) @5V
RTL8188CUS
Associated Idle
85.6
Unassociated Idle
80.2
Associated Idle (enable power save) - LPS
34.5
Unassociated Idle (enable power save) - IPS
18.9
Unassociated Idle (enable selective suspend)
0.72

-------------------------------------------------------------------------------------------------------

   The current Realtek WiFi USB Linux driver had supported lots more than 10 vip/pid USB WiFi devices. However, some customers want to add new vid/pid(s) into the Realtek WiFi USB Linux driver by themselves. This document will describe the way to let the driver to support the devices with new vid/pid.

The line 62 of os_dep\linux\usb_intf.c file describes all the vid/pids which the Realtek WiFi USB Linux driver supports currently. For the new vid/pid(s) which want to be supported, they can be added into the USB id table named “rtw_usb_id_tbl” array variable.

Ex:
static struct usb_device_id rtw_usb_id_tbl[] ={
//92CU
// Realtek demoboard*/
{USB_DEVICE(0x0bda, 0x8176)},//8188cu 1*1
{USB_DEVICE(0x0bda, 0x8177)},//8191cu 1*2
{USB_DEVICE(0x0bda, 0x8178)},//8192cu 2*2
{USB_DEVICE(0x0bda, 0x8191)},

/****** 8188CU ********/
{USB_DEVICE(0x07B8, 0x8189)},//Funai - Abocom
{USB_DEVICE(0x2019, 0xED17)},//PCI - Edimax
{USB_DEVICE(0x0DF6, 0x0052)}, //Sitecom - Edimax
{USB_DEVICE(0x7392, 0x7811)},//Edimax - Edimax
{USB_DEVICE(0x07B8, 0x8188)},//Abocom - Abocom
{USB_DEVICE(0x0EB0, 0x9071)},//NO Brand - Etop
{USB_DEVICE(0x06F8, 0xE033)},//Hercules - Edimax
{USB_DEVICE(0x103C, 0x1629)},//HP - Lite-On
//{USB_DEVICE(0x0DF6, 0x0052)},//Sitecom - Edimax V18
// {USB_DEVICE(0x0EB0, 0x9071)},//NO Brand - Etop V18
// {USB_DEVICE(0x06F8, 0xE033)},//Hercules - Edimax V18
{USB_DEVICE(0x2001, 0x3308)},//D-Link - Alpha

/****** 8192CU ********/
{USB_DEVICE(0x07b8, 0x8178)},//Funai -Abocom
{USB_DEVICE(0x2001, 0x3307)},//D-Link-Cameo
{USB_DEVICE(0x2001, 0x330A)},//D-Link-Alpha
{USB_DEVICE(0x2001, 0x3309)},//D-Link-Alpha
{USB_DEVICE(0x0586, 0x341F)},//Zyxel -Abocom
{} <- the new vid/pid can be added here
};
After adding the new vid/pid into the rtw_usb_id_tbl table, the driver has to be re-compiled. The new driver image will be created and it can support the device with the new vid/pid.
--------------------------------------------------------------------------------------------------------
Customers can port this Realtek WiFi linux driver to specific platform for their products including Android. This document will describe the way to let this driver to support the specific platform with Linux operation system. Basically, the driver Makefile file is the only file we have to modify.

First of all, you can look at the following section of Makefile file:

CONFIG_PLATFORM_I386_PC = y
CONFIG_PLATFORM_ANDROID_X86 = n
CONFIG_PLATFORM_ARM_S3C2K4 = n
CONFIG_PLATFORM_ARM_PXA2XX = n
CONFIG_PLATFORM_ARM_S3C6K4 = n
CONFIG_PLATFORM_MIPS_RMI = n
CONFIG_PLATFORM_RTD2880B = n
CONFIG_PLATFORM_MIPS_AR9132 = n
CONFIG_PLATFORM_MT53XX = n
CONFIG_PLATFORM_RTK_DMP = n

If the platform which you want to support is already in the list, just modify the CONFIG_PLATFORM_I386_PC to n and modify your platform item to y.
Ex:
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ANDROID_X86 = y

After this modification, it is necessary to check the corresponding section and content. You may change the compiler flag, arch, tool chain…etc.
※ For Android platform, We need to add CONFIG_PLATFORM_ANDROID into EXTRA_CFLAGS
Ex:
ifeq ($(CONFIG_PLATFORM_ANDROID_X86), y)
EXTRA_CFLAGS += -DCONFIG_LITTLE_ENDIAN -DCONFIG_PLATFORM_ANDROID
SUBARCH := $(shell uname -m | sed -e s/i.86/i386/)
ARCH := $(SUBARCH)
CROSS_COMPILE := i686-unknown-linux-gnu-
KSRC := /usr/src/froyo-x86/out/target/product/eeepc/obj/kernel
endif

If the platform which you want to support is NOT in the list, you can add your own CONFIG Name and CONFIG section.
Ex:
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_NEW_SUPP = y

ifeq ($(CONFIG_PLATFORM_NEW_SUPP), y)
EXTRA_CFLAGS += -DCONFIG_BIG_ENDIAN
ARCH:=
CROSS_COMPILE:=
KVER:=
KSRC:=
endif

After adding your own platform CONFIG Name and CONFIG section, this linux driver has to be compiled again and it will support your new platform.
--------------------------------------------------------------------------------------------------------

Wireless extension tools porting guide

export PATH=$PATH:/toolchain/bin/

(A)openssl-0.9.8k.tar.gz
(1)tar zxvf openssl-0.9.8k.tar.gz
(2)cd openssl-0.9.8k
(3)./Configure linux-generic32 --prefix=$(pwd)/ssh_install shared
(4)vim crypto/bio/bss_file.c
line 82:
#define _FILE_OFFSET_BITS 64 (-)
#define _FILE_OFFSET_BITS 32 (+)

(5)vim Makefile
line 62:
CC= mipsel-linux-gcc
line 69:
AR= mipsel-linux-ar $(ARFLAGS) r
line 70:
ARD= mipsel-linux-ar $(ARFLAGS) d
(6)make
(7)make install
(8)in "ssh_install" folder
lib/libcrypto.a
lib/libcrypto.so.0.9.8 (copy to target platform)
lib/libssl.a
lib/libssl.so.0.9.8 (copy to target platform)


(B)wpa_supplicant-0.6.9.tar.gz
(1)tar zxvf wpa_supplicant-0.6.9.tar.gz
(2)cd wpa_supplicant-0.6.9\wpa_supplicant
(3)cp defconfig .config
(4)vim .config
line 15:
CFLAGS += -I/openssl-0.9.8k/ssh_install/include
line 16:
LIBS += -L/openssl-0.9.8k/ssh_install/lib
line 184:
#CONFIG_WPS=y (-)
CONFIG_WPS=y (+)


(5)vim Makefile
added:
CC = mipsel-linux-gcc
(6)make

(7)copy "wpa_supplicant" and "wpa_cli" to target platform
(8)edit & copy "wpa1.conf" file to target platform
(9)./wpa_supplicant -iwlan0 -Dwext -c wpa1.conf -dd &
(10)./wps_cli (for wps in Interactive mode)
(11) > help
> wps_pbc
> wps_pin any 12345678



(C)wireless_tools.29.tar.gz
(1)tar zxvf wireless_tools.29.tar.gz
(2)cd wireless_tools.29
(3)vim Makefile
line 12:
CC = mipsel-linux-gcc
line 14:
AR = mipsel-linux-ar
RANLIB = ranlib
(4)make
(5)copy "iwconfig" and "iwlist" to target platform \usr\bin
(6)copy "iwlib.so" to target platform \lib or \usr\lib

--------------------------------------------------------------------------------------------------------

This document had described the way to inform the wpa_supplicant to do the WiFi connection by using the wpa_cli. The wpa_supplicant had supported all kinds of security connections and WPS defined in the 802.11 specification. So, we suggest use the wpa_supplicant to do the WiFi connection rather than the iwconfig wireless tool.

(A) WPA_SUPPLICANT + WPA_CLI User Guide

1.start wpa_supplicant in the background
wpa_supplicant -Dwext -iwlan0 -c /tmp/net/wpa.conf -B

2.Scaning AP and See Results
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results

3.Connect to AP
a.OPEN
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant select_network 0

b.WEP40 with open system
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 1234567890
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant select_network 0

c.WEP40 with shared key mode
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 1234567890
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli –p/var/run/wpa_supplicant set_network 0 auth_alg SHARED
wpa_cli -p/var/run/wpa_supplicant select_network 0

d.WEP104 with open system
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 12345678901234567890123456
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant select_network 0

e.WEP104 with shared key mode
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 12345678901234567890123456
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli –p/var/run/wpa_supplicant set_network 0 auth_alg SHARED
wpa_cli -p/var/run/wpa_supplicant select_network 0

#If wep key is ASCII type,use the following cmd:
#WEP40: wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"12345"'
#WEP104: wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 '"1234567890123"'

#WEP key index is X from 0 to 3, change X for other key index and select it.
#wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_keyX 12345678901234567890123456
#wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx X


f.TKIP and AES
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 1
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"dlink"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 psk '"12345678"'
wpa_cli -p/var/run/wpa_supplicant select_network 0


4.Ad-hoc mode
a.OPEN
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 2
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"Adhoc_test"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 mode 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant select_network 0

b.WEP40
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 2
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"Adhoc_test"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 mode 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 1234567890
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant select_network 0

c.WEP104
wpa_cli -p/var/run/wpa_supplicant scan
wpa_cli -p/var/run/wpa_supplicant scan_results
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant ap_scan 2
wpa_cli -p/var/run/wpa_supplicant add_network
wpa_cli -p/var/run/wpa_supplicant set_network 0 ssid '"Adhoc_test"'
wpa_cli -p/var/run/wpa_supplicant set_network 0 mode 1
wpa_cli -p/var/run/wpa_supplicant set_network 0 key_mgmt NONE
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_key0 12345678901234567890123456
wpa_cli -p/var/run/wpa_supplicant set_network 0 wep_tx_keyidx 0
wpa_cli -p/var/run/wpa_supplicant select_network 0


5.Save the Current Connection AP configuration file
wpa_cli -p/var/run/wpa_supplicant save_config


6.WPS Connection
Push Button:
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant wps_pbc any
Pin Code:
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant wps_pin any 12345670
or
wpa_cli -p/var/run/wpa_supplicant remove_network 0
wpa_cli -p/var/run/wpa_supplicant wps_pin any

7.Get Current Status of wpa_supplicant
wpa_cli -p/var/run/wpa_supplicant status


8.Disable current network connection
wpa_cli -p/var/run/wpa_supplicant disable_network 0



(B) WPA_SUPPLICANT + WPA_CLI - Control interface commands

Following commands can be used with wpa_cli

PING
This command can be used to test whether wpa_supplicant is replying to the control interface commands.
The expected reply is PONG if the connection is open and wpa_supplicant is processing commands.

STATUS
Request current status information. The output is a text block with each line in
variable=value format. For example:
bssid=02:00:01:02:03:04
ssid=test network
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA-PSK
wpa_state=COMPLETED

LIST_NETWORKS
List configured networks.
network id / ssid / bssid / flags
0 example network any [CURRENT]
(note: fields are separated with tabs)

SCAN
Request a new BSS scan.

SCAN_RESULTS
Get the latest scan results.
bssid / frequency / signal level / flags / ssid
00:09:5b:95:e0:4e 2412 208 [WPA-PSK-CCMP] jkm private
02:55:24:33:77:a3 2462 187 [WPA-PSK-TKIP] testing
00:09:5b:95:e0:4f 2412 209 jkm guest
(note: fields are separated with tabs)

ADD_NETWORK
Add a new network. This command creates a new network with empty configuration. The new network is
disabled and once it has been configured it can be enabled with ENABLE_NETWORK command. ADD_-
NETWORK returns the network id of the new network or FAIL on failure


SELECT_NETWORK <network id>
Select a network (disable others). Network id can be received from the LIST_NETWORKS command
output.

ENABLE_NETWORK <network id>
Enable a network. Network id can be received from the LIST_NETWORKS command output.


DISABLE_NETWORK <network id>
Disable a network. Network id can be received from the LIST_NETWORKS command output. Special
network id all can be used to disable all network.
.
REMOVE_NETWORK <network id>
Remove a network. Network id can be received from the LIST_NETWORKS command output. Special
network id all can be used to remove all network.


SET_NETWORK <network id> <variable> <value>
Set network variables. Network id can be received from the LIST_NETWORKS command output.
This command uses the same variables and data formats as the configuration file.

• ssid (network name, SSID)
• psk (WPA passphrase or pre-shared key)
• key_mgmt (key management protocol, NONE, WPA-PSK, WPA-EAP)
• proto ( WPA WPA2)
• pairwise ( CCMP TKIP)
• group ( CCMP TKIP WEP40 WEP104)
• wep_key0 ( set wep key for key index 0)
• wep_tx_keyidx ( select wep key index)





GET_NETWORK <network id> <variable>
Get network variables. Network id can be received from the LIST_NETWORKS command output.

SAVE_CONFIG
Save the current configuration.


AP_SCAN <ap_scan value>
Change ap_scan value: 0 = no scanning, 1 = wpa_supplicant requests scans and uses scan results to select
the AP, 2 = wpa_supplicant does not use scanning and just requests driver to associate and take care of AP
selection

no idea what 99% of this is hope it helps some one who dose
--------------------------------------------------------------------------------------------------------
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5275
Location: Australia

PostPosted: Thu 19 Jul 2012, 21:13    Post_subject:  

karm2865, that's an incredible amount of information you have provided ...
but you never actually told us whether you ran the Network Wizard, and what the Network Wizard told you!!??


karm2865 wrote:
Loaded Modules
r8192s_usb Linux driver for Realtek RTL8192 USB WiFi cards

That tells us that Puppy has detected your USB wifi dongle, and automatically loaded the r8192s_usb driver.
There's not guarantee that this driver will actually work, but at least you should tell us whether you see a valid network interface in the Network Wizard ...
and if so, whether this interface will successfully connect.

I suggest you take this simple step before we delve into the complex world of compiling third-party drivers, especially from such a dubious source as a "GMYLE"-provided computer disk.
Back to top
View user's profile Send_private_message 
karm2865


Joined: 20 Mar 2011
Posts: 57

PostPosted: Fri 20 Jul 2012, 09:10    Post_subject:  

Yes I have tried the Network Wizard many many times and all the drivers that were close to my device. Tried the ones I found on the puppy & Ubuntu sites

Most of these couldn't detect the device.
The one that tempestuous  mentions is one i found that is right driver for a different puppy and kernel

i knew it was a long shot but I tried it anyway.
it sees the USB dongle but won't connect. 
that leads me to think the right one for the right kernel would probably work but my attempts at compiling one are a disaster I can never get them to work.
If some one could be generous and help me out please. compile it or point me to ware it is already compiled in a pet or something i would greatly appreciate it

what i have tried

I tried using the Ndiswrapper with the windows xp drivers that worked with windows XP With no luck.. Couldn't detect the device.

i use the same puppy on my lap top wireless so I know the net work accepts wpa/tkip

the steps i do
network connection wizard
network wizard
install the driver i want ti try

the following new module has bin loaded: 8192cu [or what ever the name is]
no new interfaces where detected
uninstall
try the next one

this is for the driver that is the right one “RTL8192CU USB” driver for the wrong kernel /Puppy so it almost works,

network connection wizard
network wizard
install the driver i want to try
module r8192cu has loaded successfully that dose not mean it will work though! after clicking OK see if a new interface has bin detected
OK
a new interface has bin detected
save
wlan1
wireless
scan
pick my wlan
set to wpa/tkip
set up profile
put key in
save
use this profile
unable to establish wpa connection
Back to top
View user's profile Send_private_message 
karm2865


Joined: 20 Mar 2011
Posts: 57

PostPosted: Fri 20 Jul 2012, 09:51    Post_subject:  

the one that almost works and sees the USB dongle is from
tempestuous

http://www.murga-linux.com/puppy/viewtopic.php?t=59000&start=15
8192cu-k2.6.33.2.pet
Description for Puppy 5.1.x
you don't say which kernel
Filename 8192cu-k2.6.33.2.pet


as you see it is for puppy 5.1X
i am using
lucid puppy 5.2.8 Kernel Linux 2.6.33.2 (i686)
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5275
Location: Australia

PostPosted: Fri 20 Jul 2012, 22:50    Post_subject:  

OK, let's get some basic facts straight:
karm2865 wrote:
The one that tempestuous mentions is one i found that is right driver for a different puppy and kernel.

No. The driver I mentioned is r8192s_usb, and it's standard in Puppy 5.28.


karm2865 wrote:
the one that almost works and sees the USB dongle is from tempestuous
http://www.murga-linux.com/puppy/viewtopic.php?t=59000&start=15
8192cu-k2.6.33.2.pet

as you see it is for puppy 5.1X
i am using
lucid puppy 5.2.8 Kernel Linux 2.6.33.2 (i686)

I cannot understand why you would think that Puppy 5.28 has a different kernel than 5.1.
They both have kernel 2.6.33.2, and their drivers (kernel modules) are 100% identical.
I explained that in the very first post of the thread that you refer to -
tempestuous wrote:
These drivers are only compatible with the 2.6.33.2 kernel introduced with Puppy 5.1 (Lucid).
At September 2011 that includes versions of Lucid Puppy up to 5.2.8.




karm2865 wrote:
the steps i do
network connection wizard
network wizard
install the driver i want ti try

Bad bad. Puppy will automatically load the correct driver it detects as being compatible with your device, based on the USB device ID.
You should never attempt to override this automatic process, and your problems might, in fact, be due to this. It's quite possible that the r8192s_usb driver (which is standard in Puppy 5.2Cool is compatible with your device, but you have also installed my third-party 8192cu driver - so now these two drivers will be competing to claim the device, and corrupting the wifi interface!!
You need to set the MODULES-PREFERENCES to define which one should be used ... or go back to a fresh install.

And just as important - did you test a wifi connection with all encryption disabled? This is a crucial test, as I mentioned in the very first post of the "Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel" thread.
You might, for example, find that the r8192s_usb/8192cu drivers won't play well with WPA/TKIP, but they work OK with WPA/AES.

Also, does your WPA passphrase have any spaces or special characters in it? Linux chokes on spaces and special characters - the solution is to enclose your passphrase in quotation marks.
Back to top
View user's profile Send_private_message 
karm2865


Joined: 20 Mar 2011
Posts: 57

PostPosted: Sat 21 Jul 2012, 10:32    Post_subject:  

I am a confused nube what else can i say?
I am not trying to build a better mouse trap just catch mice with the one i have.
i always try the standard out of the box automatic process method.
before i start trying do do the complex process of matching hardware and drivers. or getting programs to work.
I don't like messing with the coding, compiling and all that it confuses me badly i just don't understand it.

I tried all the automatic process with the standard r8192s_usb driver first thing.
It dose not see the USB dongle why? I don't know.
so i tried some others no luck.
so i went surfing the web hoping to find something that would work.
I tried to compile it my self using the cut and paste method diffident work.
so I asked hear.


I assumed that 5.1 and 5.2 where diffident Kernels I was under the impression that was the differences between the two I apologise for my mistake.

No i did not test my network encryption disabled not sure how i would do that it came from the ISP with all the security preset and they recommend i don't mess with it unless i Know what i am doing which i don't.

At the moment there are no spaces or special characters in the Key

if any one gets this POS to work on puppy Linux let me know.
i am sure you don't want to hear this but it all worked just fine with windows XP.
Back to top
View user's profile Send_private_message 
Flash
Official Dog Handler


Joined: 04 May 2005
Posts: 11128
Location: Arizona USA

PostPosted: Sat 21 Jul 2012, 10:36    Post_subject:  

karm2865 wrote:
...i am sure you don't want to hear this but it all worked just fine with windows XP.
It helps to know that there is nothing wrong with the hardware. Windows is useful for that. Laughing
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 1 of 1 Posts_count  
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2183s ][ Queries: 12 (0.0220s) ][ GZIP on ]