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 Sat 02 Aug 2014, 04:47
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
Extra drivers for Puppy 4.1 with 2.6.25.16 kernel
Post new topic   Reply to topic View previous topic :: View next topic
Page 12 of 17 [249 Posts]   Goto page: Previous 1, 2, 3, ..., 10, 11, 12, 13, 14, 15, 16, 17 Next
Author Message
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sat 09 May 2009, 05:44    Post subject:  

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-pcmcia@lists.infradead.org/msg02001.html

After installing this dotpet, reboot.
pcnet_cs-FA411-k2.6.25.16.pet
Description  for Puppy 4.1.x
pet

 Download 
Filename  pcnet_cs-FA411-k2.6.25.16.pet 
Filesize  18.28 KB 
Downloaded  633 Time(s) 
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Sun 17 May 2009, 17:14    Post subject:  

@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:
Quote:
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[B] -> 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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware 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.

_________________
Laptop: Acer Aspire 5810TZ
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sun 17 May 2009, 20:24    Post subject:  

Barburo wrote:
It wants to load wl but it's "tainted" so falls back to B43xx driver

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.

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:
wl:bcm43xx
b43:bcm43xx
b43legacy:bcm43xx
ssb:bcm43xx

Now reboot and check that the bcm43xx driver loads.
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/Wifi/drivers-for-Puppy-2.12-to-2.14/bcm43xx-firmware.pet
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Mon 18 May 2009, 02:28    Post subject:  

@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.
Quote:
wl: no version for "struct_module" found: kernel tainted.
wl: module license 'unspecified' taints kernel.

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.
The next log lines are
Quote:
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PM, Firmware-ID: FW13 ]

Is this the bcm43xx driver or the b43 driver?
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
Quote:
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed.

I looked in /lib/firmware after runnig your .pet and there is no b43 folder there.
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?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Mon 18 May 2009, 04:06    Post subject:  

Quote:
wl: no version for "struct_module" found: kernel tainted.

"tainted" can simply mean that the driver is totally incompatible, and it cannot complete the load process.
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?

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

Ah, that's a good start. You didn't mention this important information before.
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:
cd /lib/modules/all-firmware
tar -zxvf b43.tar.gz
cp -a b43/* /

The correct firmware for the b43 driver should now be in /lib/firmware/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:
bcm43xx:ssb
wl:ssb

Reboot and you should be ready to load the b43 driver in the Network Wizard.
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Tue 19 May 2009, 14:36    Post subject:  

..accidental double post - deleted
Last edited by Barburo on Tue 19 May 2009, 14:43; edited 2 times in total
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Tue 19 May 2009, 14:40    Post subject:  

Thanks Tempestuous for pointing me in the right direction.
I got connected in 4.1.2 (that's the 2.6.26. kernel I believe) as soon as I copied the B43 library to firmware.
I tried the same B43 lib with the 2.6.28 SMP kernel that unnamed pup and Lighthouse RC2 are using but it failed (only just though). As you pointed out
Quote:
... I hope you're definitely using the official release of Puppy 4.20 ... not the unofficial SMP kernel?

the B43 firmware probably needs compiling against that kernel for wireless to work on my tx1000.

I visited the Broadcom website and read their instructions.
I find the "make" command doesn't work on my puppies (--> because it probably needs a development environment?).
Any information about how I can proceed to get these B43 libraries compiled for 2.6.28 ?
B.

_________________
Laptop: Acer Aspire 5810TZ
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Tue 19 May 2009, 20:58    Post subject:  

Barburo wrote:
I got connected in 4.1.2

Great. That confirms that the b43 driver works ...
but clearly some or all of the Puppy 4.1/4.2 versions fail to decompress the b43 firmware as they should.

Barburo wrote:
I got connected in 4.1.2 (that's the 2.6.26. kernel I believe)

No. Like all official 4.1 and 4.2 releases it has kernel 2.6.25.16.

Barburo wrote:
the B43 firmware probably needs compiling against that kernel for wireless to work on my tx1000.

No. firmware is just a binary chunk of code.
If the b43 driver undergoes any significant change in the future then yes, updated firmware will likely be required. But the latest version of b43 firmware is compatible with all kernels from 2.6.25 to the latest 2.6.29. And this is what Puppy includes. It's from
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware

When you copy the firmware from Puppy 4.2 across to BoxPup make sure you locate it at /lib/firmware/b43

My concerns about kernel version related only to the proprietary wl Broadcom driver, since I compiled this driver specifically for k2.6.25.16, non-SMP. This driver has its firmware built-in.
DON'T attempt to obtain firmware from the Broadcom site. Broadcom do not provide the opensource b43 driver, and their firmware should only be used after the b43 developers have tested it.
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Wed 20 May 2009, 15:10    Post subject:  

@Tempestuous
Thanks for your patience and commitment to helping us Puppy users
After spending many hours in fruitless experimentation I can now get wifi connected in 4.1.2 plus later variants.

When I can't get things to work it's usually operator error, or some other dumb mistake. This time all that was needed to make the Broadcom chip work in my HP Tx1000 was the correct set of b43 firmware files which you pointed me at.

In the end this source for b43_patch.tar.gz http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=17806 provided b43 firmware that worked for the SMP 2.6.28 kernel Puplets and allowed me to get connected.

This source for b43.zip http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=18072 worked OK for regular 4.1.2 but reported a corrupted firmware file b43/b0g0bsinitvals5.fw on other puplets.

I hope this may help others with a similar problem.

Thanks again!
B.
Back to top
View user's profile Send private message 
evgeniy

Joined: 21 May 2009
Posts: 5

PostPosted: Fri 22 May 2009, 05:13    Post subject:  watchdog drivers  

Hello
I use Puppy 4.1.2 (barebone) on computer with hardware watchdog which I have to use (for some project). Computer is based on intel 915 chipset and probably iTCO_wdt driver should work. I had also Ubuntu 9.04 installed on another computer and it has /lib/modules/2.6.28-11-generic/kernel/drivers/watchdog directory with all drivers, but on Puppy there is no even softdog driver... Is there any way to add these drivers to Puppy?
Thank you in advance.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 22 May 2009, 10:06    Post subject:  

evgeniy wrote:
hardware watchdog ...
Is there any way to add these drivers to Puppy?

No, not easily. The Puppy 4.1.x kernel (2.6.25.16) does not have "Watchdog Timer Support" enabled.
Back to top
View user's profile Send private message 
evgeniy

Joined: 21 May 2009
Posts: 5

PostPosted: Fri 22 May 2009, 14:36    Post subject:  

tempestuous wrote:
evgeniy wrote:
hardware watchdog ...
Is there any way to add these drivers to Puppy?

No, not easily. The Puppy 4.1.x kernel (2.6.25.16) does not have "Watchdog Timer Support" enabled.


Is it possible to do by recompiling kernel from kernel-src-2.6.25.16-patched-puppy4.1.sfs?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 22 May 2009, 20:28    Post subject:  

Sure.
Make sure you start with the correct kernel configuration - it's at /etc/modules/DOTconfig-K2.6.25.16
Copy it across to /usr/src/linux-2.6.25.16 and rename it ".config"

Also you must install lzma-458.pet from
http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/
otherwise the last stage of the kernel image build will fail.
Back to top
View user's profile Send private message 
evgeniy

Joined: 21 May 2009
Posts: 5

PostPosted: Sat 23 May 2009, 08:06    Post subject:  

tempestuous wrote:
Sure.
Make sure you start with the correct kernel configuration - it's at /etc/modules/DOTconfig-K2.6.25.16
Copy it across to /usr/src/linux-2.6.25.16 and rename it ".config"

Also you must install lzma-458.pet from
http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/
otherwise the last stage of the kernel image build will fail.

Thanks!
And last question.
Should I use default sequence after copying config file:
Code:
#make menuconfig
#make bzImage
#make modules
#make install
#make modules_install

Or there is something special for Puppy?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sat 23 May 2009, 08:47    Post subject:  

Yes, but of course there are other steps, too. When you run "make menuconfig" you are presented with the kernel configuration as defined by the Puppy configuration file. Obviously you need to change this configuration, specifically at -

Device Drivers > Watchdog Timer Support > Intel TCO Timer/Watchdog

After "make bzImage" you will need to rename the new kernel image "vmlinuz", and boot to this new kernel instead of the existing one.

Since this new kernel will be very similar to the existing kernel (just one extra feature enabled) you could probably get away with not compiling all the modules ... but of course, you still need to generate the iTCO_wdt module, so you will need to do the whole "make modules" process just for this module.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 12 of 17 [249 Posts]   Goto page: Previous 1, 2, 3, ..., 10, 11, 12, 13, 14, 15, 16, 17 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1082s ][ Queries: 13 (0.0089s) ][ GZIP on ]