Extras for Puppy 4.3 with 2.6.30.5 kernel
tempestuous
He, he....I searched the forum for the ati-driver and found it was patriots work I just combined you with any driver update........strange
The advice I search is to choose which drivers (wifi and others) to include include in Puppy Stardust. Many of these are 'huge' and including them all would blow the iso.....
Thanks for your help
Sigmund
He, he....I searched the forum for the ati-driver and found it was patriots work I just combined you with any driver update........strange
The advice I search is to choose which drivers (wifi and others) to include include in Puppy Stardust. Many of these are 'huge' and including them all would blow the iso.....
Thanks for your help
Sigmund
My first test of Stardust 003 tells that Dell inspiron 500m with bc43legazy is not detected with jrls remastered Puppy 4.3.1.tempestuous wrote: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.
Sigmund
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
w35und wireless driver (winbond)
@tempestuous
In your earlier post here:
http://www.murga-linux.com/puppy/viewto ... 294#295294
You had posted a pet for the "w35und" driver for the Winbond W89C35D wifi device for Puppy 4.1
Do you have an updated version for 4.3? I am trying to get a Amtek T700 UPMC working with puppy and WiFi would be a big help!
The source code is from
http://code.google.com/p/winbondport/
In your earlier post here:
http://www.murga-linux.com/puppy/viewto ... 294#295294
You had posted a pet for the "w35und" driver for the Winbond W89C35D wifi device for Puppy 4.1
Do you have an updated version for 4.3? I am trying to get a Amtek T700 UPMC working with puppy and WiFi would be a big help!
The source code is from
http://code.google.com/p/winbondport/
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well that source code fails to compile against the 2.6.30.5 kernel in Puppy 4.3.x,
but fortunately the driver now appears in the "staging" section of the official kernel source.
So here is the w35und driver for the 2.6.30.5 kernel,
compatible with the Winbond/ISSC W89C35D wifi chipset, as found in certain Kohjinsha laptops.
In addition to WEP encryption, this driver also supports WPA encryption.
NOTE: the default frequency settings for this driver are the USA standard.
If you connect to European wifi access points, you must run this command each time before running the Network Wizard:
but fortunately the driver now appears in the "staging" section of the official kernel source.
So here is the w35und driver for the 2.6.30.5 kernel,
compatible with the Winbond/ISSC W89C35D wifi chipset, as found in certain Kohjinsha laptops.
In addition to WEP encryption, this driver also supports WPA encryption.
NOTE: the default frequency settings for this driver are the USA standard.
If you connect to European wifi access points, you must run this command each time before running the Network Wizard:
Code: Select all
iwpriv wlan0 set_region Europe
- Attachments
-
- w35und-k2.6.30.5.pet
- for Puppy 4.3.x
- (48.85 KiB) Downloaded 1144 times
@tempestuous
Thanks for compiling the module. It sucessfully installed and loaded and I now have wlan0 visible in the network wizard.
However, I am in Europe and the wlan scan comes up empty.
When I do the iwpriv command to set Europe region it returns the following:
Getting closer....
Is there another way to set the wlan in 'European' mode?
Thanks for compiling the module. It sucessfully installed and loaded and I now have wlan0 visible in the network wizard.
However, I am in Europe and the wlan scan comes up empty.
When I do the iwpriv command to set Europe region it returns the following:
Code: Select all
#iwpriv wlan0 set_region Europe
>wlan0 no private ioctls
Is there another way to set the wlan in 'European' mode?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
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:
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:
or to be more accurate regarding frequency, you would do this instead:
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: Select all
ifconfig wlan0 down
rmmod w35und
modprobe w35und
ifconfig wlan0 up
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: Select all
iwconfig wlan0 channel 5
Code: Select all
iwconfig wlan0 freq 2.432G
"dmesg" output, reloading the driver gives the same:
"iwconfig wlan0" returns:
"iwlist wlan0 channels" returns:
"iwconfig wlan0 channel 3" fails with the error message:
Not suprising given the "iwlist" result from above.
Do you have a link to the sources?
Code: Select all
w35und: module is from the staging directory, the quality is unknown, you have been warned.
usbcore: registered new interface driver w35und
Code: Select all
wlan0 IEEE 802.11b ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Code: Select all
wlan0 1 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Current Frequency:2.412 GHz (Channel 1)
Code: Select all
SET failed on device wlan0 ; Invalid argument.
Do you have a link to the sources?
Some progress.
I managed to find a w35und.sys driver for win9x which works with ndiswrapper.
found here:
http://www.megasphera.cz/upgrade/prg_up ... ver/Win9X/
Now I can see my network but not connect as the wifi here is WPA2 encrypted, it seems Win9x drivers do not support WPA2.
I managed to find a w35und.sys driver for win9x which works with ndiswrapper.
found here:
http://www.megasphera.cz/upgrade/prg_up ... ver/Win9X/
Now I can see my network but not connect as the wifi here is WPA2 encrypted, it seems Win9x drivers do not support WPA2.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Mmm. That's odd. It looks like the w35und driver is locked to channel 1.t-bon3 wrote:"dmesg" output, reloading the driver gives the same:"iwlist wlan0 channels" returns:Code: Select all
w35und: module is from the staging directory, the quality is unknown, you have been warned.
"iwconfig wlan0 channel 3" fails with the error message:Code: Select all
wlan0 1 channels in total; available frequencies : Channel 01 : 2.412 GHz Current Frequency:2.412 GHz (Channel 1)
Not suprising given the "iwlist" result from above.Code: Select all
SET failed on device wlan0 ; Invalid argument.
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.
Standard 2.6.30.5 kernel source. It's in the "staging" section.t-bon3 wrote:Do you have a link to the sources?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
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/viewto ... 450#346450
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/viewto ... 450#346450
Last edited by tempestuous on Thu 15 Apr 2010, 06:58, edited 2 times in total.
I really appreciate all that you do to make these PETs available and hate to always be bringing up problems, but ...
I just discovered that the r8192s_usb module does not support WPA.
Is there any chance there has been an update from Realtek which upgrades it to handle WPA, please?
Our device is a Belkin N Wireless USB Adapter F5D8053 v6 identified as a RTL81915 WLAN Adapter.
I just discovered that the r8192s_usb module does not support WPA.
Is there any chance there has been an update from Realtek which upgrades it to handle WPA, please?
Our device is a Belkin N Wireless USB Adapter F5D8053 v6 identified as a RTL81915 WLAN Adapter.
tempestuous wrote: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.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
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.edoc wrote:I just discovered that the r8192s_usb module does not support WPA.
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:
To help solve this problem, I need you to plug in your USB wifi device, and please report the results of this command:Note: The interface you have selected uses the r8192s_usb module, which is not included in our list of modules supporting WPA encryption.
Code: Select all
readlink /sys/class/net/wlan0/device/driver
Code: Select all
../../../../../../bus/usb/drivers/
The first one is the internal nic, the second is the Belkin N USB.# readlink /sys/class/net/wlan0/device/driver
../../../../bus/pci/drivers/ath5k
# readlink /sys/class/net/wlan1/device/driver
../../../../../../bus/usb/drivers/rtl819xSU
I am experimenting with the Belkin as the internal (a/b/g) nic seems to slowing down the whole Wifi network.
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Thanks. As you can see, the r8192s_usb driver identifies itself as rtl819xSU.edoc wrote:../../../../../../bus/usb/drivers/rtl819xSU
Such cases demonstrate why it's difficult for me to contribute drivers for hardware which I don't own, myself.
Now attached is a hotfix which should allow Puppy's Network Wizard to configure the r8192s_usb driver for WPA encryption. Please let me know if it works.
Also be aware that you must be clear about whether your wifi router has been set for WPA encryption, or WPA2 encryption. The Network Wizard requires you to specify one or the other.
EDIT: hotfix tested successfully. Realtek drivers updated in earlier post.
Last edited by tempestuous on Sun 28 Feb 2010, 01:30, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
OK, both Realtek driver packages have been updated with the WPA fix in the earlier post.
http://www.murga-linux.com/puppy/viewto ... 457#346457
http://www.murga-linux.com/puppy/viewto ... 457#346457
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia