Yeah... whenever you fix something, all these people start popping up saying "we've also had that problem for ages", but they never bothered reporting/investigating it...tempestuous wrote:But does that mean that the other 35 people who downloaded iwl3945-iwl4965-aircrack-k2.6.25.16 dotpet would have failed to launch the aircrack utilities, too?
Extra drivers for Puppy 4.1 with 2.6.25.16 kernel
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
I only want to say THANKS to tempestuous for the job with the wireless drivers. Yo have compiled a lot of them and i couldn't make that job because i have a low knowledge in linux.tempestuous wrote:Well done guys.
But does that mean that the other 35 people who downloaded iwl3945-iwl4965-aircrack-k2.6.25.16 dotpet would have failed to launch the aircrack utilities, too?
If so, I'm stunned that people would download a driver for such a specific purpose, then not bother to report something as obvious as a missing wifi utility such as this! We get some strange behaviour on this forum.
A lot of thanks for your explanation. I like to learn to compile programs and to know why there is an error.Dougal wrote:The errors you got were from undeclared functions, which most likely meant you were missing the header files for libnl (they include a list of functions contained in the library, so the application knows what's there to use).caka wrote:I don't know why i can't compile iw in my system?
This was probably the result of not having libnl...
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is an updated version of the snd-hda-intel ALSA audio driver.
I specifically patched it to support the ALC663 variant of Intel HDA-based audio devices, using a patch from here
http://marc.info/?l=linux-kernel&m=121602662531525&w=2
but as you can see from that link, many more updates are included.
Also, I added this latest patch on top of earlier patches for the ALC269 device in recent ASUS Eee models, so this audio driver is now relatively up to date, albeit heavily patched.
If you have an HDA-based audio device which still does not work with this driver, I suggest that you should use a Puppy derivative with newer kernel and newer ALSA audio drivers, such as wow's "Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)"
http://www.murga-linux.com/puppy/viewtopic.php?t=36592
or kirk's "Fatdog 112"
http://www.murga-linux.com/puppy/viewtopic.php?t=41102
I specifically patched it to support the ALC663 variant of Intel HDA-based audio devices, using a patch from here
http://marc.info/?l=linux-kernel&m=121602662531525&w=2
but as you can see from that link, many more updates are included.
Also, I added this latest patch on top of earlier patches for the ALC269 device in recent ASUS Eee models, so this audio driver is now relatively up to date, albeit heavily patched.
If you have an HDA-based audio device which still does not work with this driver, I suggest that you should use a Puppy derivative with newer kernel and newer ALSA audio drivers, such as wow's "Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)"
http://www.murga-linux.com/puppy/viewtopic.php?t=36592
or kirk's "Fatdog 112"
http://www.murga-linux.com/puppy/viewtopic.php?t=41102
- Attachments
-
- snd-hda-intel-patchedApril09-k2.6.29.16.pet
- for Puppy 4.1.x
- (120.5 KiB) Downloaded 923 times
I'm not sure this is the proper place to post this but I was redirected here from another post so here goes...
I have an eBox 3300 but the NIC isn't being detected. I've downloaded the driver from the manufacturer's site but am not sure how to compile it. I'm using Puppy 4.0 but I think this is also an issue with newer versions as well.
Would anyone be able to help me out?
I've attached the source for the r6040 ethernet drivers.
Kind regards.
I have an eBox 3300 but the NIC isn't being detected. I've downloaded the driver from the manufacturer's site but am not sure how to compile it. I'm using Puppy 4.0 but I think this is also an issue with newer versions as well.
Would anyone be able to help me out?
I've attached the source for the r6040 ethernet drivers.
Kind regards.
Last edited by bondo08 on Mon 13 Apr 2009, 20:07, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I attached the source code for the drivers in my previous message and was hoping someone might be able to compile them for me.tempestuous wrote:Puppy 4.0 has an older kernel, and does not contain the "r6040" ethernet driver.
I would upgrade but that isn't an option right now. I've customized 4.0 quite a lot and am unable to upgrade to the newer version for a while.tempestuous wrote:I suggest you use Puppy 4.1.2.
I'm really hoping there is a way to get it working in Puppy 4.0. Thx.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Then your request should go in the forum thread which deals with that earlier kernel;bondo08 wrote:I'm really hoping there is a way to get it working in Puppy 4.0.
"Extras for Puppy 3.x and 4.0"
http://www.murga-linux.com/puppy/viewto ... 970#294970
r6040 driver now attached there.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is the "w35und" driver for the Winbond W89C35D wifi device, which is apparently found in certain Koshinja laptops.
The source code is from
http://code.google.com/p/winbondport/
After installing this dotpet, reboot.
Puppy should automatically load the w35und driver, but if not, you can load it from the Network Wizard.
The source code is from
http://code.google.com/p/winbondport/
After installing this dotpet, reboot.
Puppy should automatically load the w35und driver, but if not, you can load it from the Network Wizard.
- Attachments
-
- w35und-030408-k2.6.25.16.pet
- for Puppy 4.1.x
- (116.09 KiB) Downloaded 892 times
-
- Posts: 5
- Joined: Sun 05 Apr 2009, 17:25
Thank you so much Tempestuous, module loaded, seems to be working, but I cannot connect to internet via wireless. LAN ethernet works fine, as usual... what should I do to make it work? I'm so excited since I've been trying ti load the module since 6 months ago!
I will appreciate any suggestion.
Best.
I will appreciate any suggestion.
Best.
-
- Posts: 5
- Joined: Sun 05 Apr 2009, 17:25
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
thank you very much for this. i had been trying in vain for hours to get my BCM43xG card to work. this did the trick. thanks again.tempestuous wrote:Broadcom wifi devices.
Puppy 4.1.x contains the new b43 and b43legacy opensource wifi drivers, plus the older bcm43xx driver.
But some Broadcom wifi devices, especially those found in Dell and HP notebooks, are notorious for failing to work with these drivers.
For these troublesome devices the proprietary Broadcom hybrid driver will likely work better. Now attached.
This dotpet package contains a suitably modified PREFLIST so that the new driver will be used in preference to the other versions.
Also the networkmodules and wag-profiles.sh config files have been modified to accommodate the new driver.
After installing this dotpet, reboot. Puppy should automatically load the new driver, which is called "wl". Check with lsmod. If necessary you can load the wl module from the Network Wizard.
Feb 11 2009:
Driver updated to version 5.10.27.14
The source code is from here
http://www.broadcom.com/support/802.11/linux_sta.php
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is the zd1211rw wifi driver for Zydas chipsets, patched to support the TP-Link WN322/422G.
The patch is from
http://marc.info/?l=linux-wireless&m=12 ... 904294&w=2
After installing this dotpet, reboot.
UPDATE May 26 2009:
The driver was originally located in the wrong directory. Now fixed and re-attached.
The patch is from
http://marc.info/?l=linux-wireless&m=12 ... 904294&w=2
After installing this dotpet, reboot.
UPDATE May 26 2009:
The driver was originally located in the wrong directory. Now fixed and re-attached.
- Attachments
-
- zd1211rw-TPLink-k2.6.25.16.pet
- for Puppy 4.1.x
- (23.02 KiB) Downloaded 1372 times
Last edited by tempestuous on Tue 26 May 2009, 13:52, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is the pcnet_cs cardbus-ethernet driver, patched to fix a problem with recognition of the Netgear FA411 device.
The patch is from here
http://www.mail-archive.com/linux-pcmci ... 02001.html
After installing this dotpet, reboot.
The patch is from here
http://www.mail-archive.com/linux-pcmci ... 02001.html
After installing this dotpet, reboot.
- Attachments
-
- pcnet_cs-FA411-k2.6.25.16.pet
- for Puppy 4.1.x
- (18.28 KiB) Downloaded 902 times
@tempestuous
I have HP tx1000 laptop. It has the broadcomm bcm43xx wifi chip.
Wireless works with the retro kernel.
I loaded regular Puppy 4.1.2 and tried to use the wl driver per your instructions.
Downloaded broadcom-5.10.27.14-k2.6.25.16.pet
rebooted and B43 identifies wlan0 but won't connect.
Checked bootkernel.log and found these lines towars the end of the log:
It wants to load wl but it's "tainted" so falls back to B43xx driver, which gives the old warning messages about updating the firmware.
I tried that before but you've pointed out that it is futile.
Can you assist in any way so that I can get wireless working in 4.1.2?
Thanks,
B.
I have HP tx1000 laptop. It has the broadcomm bcm43xx wifi chip.
Wireless works with the retro kernel.
I loaded regular Puppy 4.1.2 and tried to use the wl driver per your instructions.
Downloaded broadcom-5.10.27.14-k2.6.25.16.pet
rebooted and B43 identifies wlan0 but won't connect.
Checked bootkernel.log and found these lines towars the end of the log:
forcedeth 0000:00:14.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1b:24:18:21:b8
forcedeth 0000:00:14.0: highdma pwrctl timirq gbit lnktim desc-v3
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 18
ACPI: PCI Interrupt 0000:00:10.1 -> Link [LAZA] -> GSI 18 (level, high) -> IRQ 18
PCI: Setting latency timer of device 0000:00:10.1 to 64
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:62c0)
input: USB 2.0 Camera as /devices/pci0000:00/0000:00:0b.1/usb2/2-2/2-2.1/2-2.1:1.0/input/input10
ieee80211_crypt: registered algorithm 'NULL'
wl: no version for "struct_module" found: kernel tainted.
usbcore: registered new interface driver uvcvideo
USB Video Class driver (SVN r238)
wl: module license 'unspecified' taints kernel.
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PM, Firmware-ID: FW13 ]
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
It wants to load wl but it's "tainted" so falls back to B43xx driver, which gives the old warning messages about updating the firmware.
I tried that before but you've pointed out that it is futile.
Can you assist in any way so that I can get wireless working in 4.1.2?
Thanks,
B.
[i]Laptop[/i]: Acer Aspire 5810TZ
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
No, it's not possible to fall back to the b43 driver, because the wl dotpet installation configures Puppy to exclude the b43, b43legacy, and bcm43xx drivers in favour of the wl driver.Barburo wrote:It wants to load wl but it's "tainted" so falls back to B43xx driver
It seems that the old bcm43xx driver may be best for your device. So go to -
Menu >
System >
BootManager configure bootup >
Give preference to one module over another:
And set preferences so that the bcm43xx will be used instead of all the other Broadcom drivers, like this -
Code: Select all
wl:bcm43xx
b43:bcm43xx
b43legacy:bcm43xx
ssb:bcm43xx
Unfortunately you may now get errors in your dmesg relating to firmware, because the firmware version in Puppy is correct for b43/legacy, not bcm43xx.
If so, install this -
http://puppyfiles.org/dotpupsde/dotpups ... rmware.pet
@Tempestuous
Thanks for your swift reply.
I tried your recommendations,maade the changes in the preferences file, installed the ,pet and had the same result as before.
Looking at the quoted text in my previous post it first tries to load WL but complains it is tainted.
The next log lines are
I tried all of the available Broadcom drivers in the connect wizard and the only one to create a wlan0 interface was b43, but of course it doesn't have the correct firmware. WL came up as "not found"when I tried to load it.
Next line is
I checked by looking inside the .pet that you recommended and it does not have that structure either, but loads files directly to the /lib/firmware folder.
I tried ndiswrapper too, but I got "invalid driver" when I pointed to the BCMWL5.inf file from XP.
Can you shed any further light on my predicament?
Thanks for your swift reply.
I tried your recommendations,maade the changes in the preferences file, installed the ,pet and had the same result as before.
Looking at the quoted text in my previous post it first tries to load WL but complains it is tainted.
I do not know what this means, but if a suitable WL driver that got around these "taint" objections was available I could perhaps get wireless again.wl: no version for "struct_module" found: kernel tainted.
wl: module license 'unspecified' taints kernel.
The next log lines are
Is this the bcm43xx driver or the b43 driver?b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PM, Firmware-ID: FW13 ]
I tried all of the available Broadcom drivers in the connect wizard and the only one to create a wlan0 interface was b43, but of course it doesn't have the correct firmware. WL came up as "not found"when I tried to load it.
Next line is
I looked in /lib/firmware after runnig your .pet and there is no b43 folder there.b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.
I checked by looking inside the .pet that you recommended and it does not have that structure either, but loads files directly to the /lib/firmware folder.
I tried ndiswrapper too, but I got "invalid driver" when I pointed to the BCMWL5.inf file from XP.
Can you shed any further light on my predicament?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
"tainted" can simply mean that the driver is totally incompatible, and it cannot complete the load process.wl: no version for "struct_module" found: kernel tainted.
Or it could mean that the driver was compiled under a different kernel ... I hope you're definitely using the official release of Puppy 4.20 ... not the unofficial SMP kernel?
Ah, that's a good start. You didn't mention this important information before.Barburo wrote:I tried all of the available Broadcom drivers in the connect wizard and the only one to create a wlan0 interface was b43
I've been told that firmware fails to automatically decompress in Puppy 4.2 (groan, another problem with 4.2) so the error message about wrong firmware may, in fact, relate to absent firmware.
So let's get the firmware decompressed and ready. Do this -
Code: Select all
cd /lib/modules/all-firmware
tar -zxvf b43.tar.gz
cp -a b43/* /
(the older bcm43xx firmware is located at /lib/firmware)
Now let's get your modules preference configuration back to the correct default state. Go to -
Menu >
System >
BootManager configure bootup >
Give preference to one module over another:
Here is the correct configuration -
Code: Select all
bcm43xx:ssb
wl:ssb