The question is then whether the b43/b43legacy modules (which are needed for older Broadcom devices) can also co-exist with the wl module without problems. Give me a day or two and I will give you an accurate answer.

My first test of Stardust 003 tells that Dell inspiron 500m with bc43legazy is not detected with jrls remastered Puppy 4.3.1.

Some troubleshooting is in order.
Run the "dmesg" command and look for anything relating to the w35und module. Report the exact text here if necessary.
It might simply be that the driver failed to load properly, and just needs to be unloaded/reloaded, as such:

Code:

ifconfig wlan0 down
rmmod w35und
modprobe w35und
ifconfig wlan0 up

But it's also possible that since the driver has entered the official kernel, maybe the "iwpriv" parameters have been removed?

If so, you may need to set the exact freq/channel parameters manually.
Refer to a list of 802.11 wifi frequencies/channels here
http://www.topbits.com/wi-fi-80211.html
I don't fully understand this, myself, but I think that if you want to force your wifi adaptor to channel 5, for example, you would do this:

Code:

iwconfig wlan0 channel 5

or to be more accurate regarding frequency, you would do this instead:

Mmm. That's odd. It looks like the w35und driver is locked to channel 1.
Since the "staging" driver in the 2.6.30 kernel seems to be misbehaving, it may be worth going back to Puppy ver 4.2 with the 2.6.25.16 kernel.

EDIT April 15 2010
The Buffalo WLI-UC-GN USB wifi device, USB ID 0411:015d
is now confirmed to work with the modified rt3070sta driver,
available in the third post in this thread -
http://www.murga-linux.com/puppy/viewtopic.php?p=346450#346450Last edited by tempestuous on Thu 15 Apr 2010, 02:58; edited 2 times in total

Realtek seems to release new wifi (and ethernet) devices quite regularly.
The most recent Realtek wifi chipsets are the N-mode RTL819x series. And in Realtek's usual style, they write a Linux driver immediately, but they don't release it for public download. Individual developers must ask for it.
I managed to obtain the source code from various private download sites. Now attached are the PCI/PCIe version of the driver: r8192se_pci, and the USB versions of the driver: r8192s_usb

After installing either of these dotpets, reboot. Puppy should automatically load the new driver, and you will see the new driver in the Network Wizard.

A WPA connection failure may be due to a range of configuration problems. To say that the driver does not support WPA is a big call. To have any chance of accuracy, your diagnostic process would need to include an analysis of the output of wpa_supplicant, after running the relevant wifi connections commands manually.
Since you have not revealed this information, I will make a guess that when entering WPA settings in the Network Wizard, you received this prompt:

Quote:

Note: The interface you have selected uses the r8192s_usb module, which is not included in our list of modules supporting WPA encryption.

To help solve this problem, I need you to plug in your USB wifi device, and please report the results of this command:

Code:

readlink /sys/class/net/wlan0/device/driver

The result should be in this form:

Code:

../../../../../../bus/usb/drivers/

but it's the very last characters I need to see; this will be the name by which the driver identifies itself.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum