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.

(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 .

===============================================================================
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)

(*) 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:

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.

(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

===========================================================
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

===========================================================
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

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.

/****** 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.

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 adding your own platform CONFIG Name and CONFIG section, this linux driver has to be compiled again and it will support your new platform.
--------------------------------------------------------------------------------------------------------

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.

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

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.

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.

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

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.2 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.

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.