Extra drivers for Puppy 4.1 with 2.6.25.16 kernel

For drivers and kernel modules.
Message
Author
evgeniy
Posts: 5
Joined: Thu 21 May 2009, 18:54

#181 Post by evgeniy »

Thanks a lot, tempestuous! Worked great :)

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#182 Post by tempestuous »

Here is the acerhdf driver for fan control of the Aspire ONE.
Apparently it doesn't work for other Acer models.
Instructions are in a separate post; "Acer Aspire ONE fan control"
http://www.murga-linux.com/puppy/viewtopic.php?t=42818
Attachments
acerhdf-0.2.2-2-k2.6.25.16.pet
for Puppy 4.1-4.2
(4.92 KiB) Downloaded 1193 times
Last edited by tempestuous on Tue 26 May 2009, 02:38, edited 1 time in total.

evgeniy
Posts: 5
Joined: Thu 21 May 2009, 18:54

#183 Post by evgeniy »

Hello,
I know that is maybe off-topic. I boot from live-cd and want directly remaster it, and as far as I know remaster script allows you to customize only /root and /etc. But is it possible remaster puppy with new kernel modules added to /lib/modules? I could not find if it possible on this forum so far.
Regards, Evgeniy.

UPD: Seems remaster script do right job - it has put modules in new sfs itself.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#184 Post by mikeb »

Hello,
I know that is maybe off-topic. I boot from live-cd and want directly remaster it, and as far as I know remaster script allows you to customize only /root and /etc. But is it possible remaster puppy with new kernel modules added to /lib/modules? I could not find if it possible on this forum so far.
Regards, Evgeniy.
as you found any changes are carried over except in certain areas...eg /var /tmp /dev...even changing kernels can be done via a remaster :)

mike

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

B43 module loading problem with kernel 2.6.28.5

#185 Post by Barburo »

I previously reported solved the problem of getting b43 to load.
I am using Lighthouse 4.1.2 RC2 that uses Xorg7.4 and the SMP kernel 2.6.28.5 from Newyearspup02.
I have successfully connected twice to wireless but most of the time the kernel reports an error with the firmware files.
The B43 module is the only one that successfully loads and identifies the wifi interface wlan0. To make b43 load correctly it needs the correct version of the firmware.
I copied the B43 firmware lib folder from puppy 4.1.1 into /lib/firmware from as suggested by tempestuous. The first boot was successful. Subsequent boots however complain about the firmware: 'ERROR: Firmware file "b43/b0g0initvals5.fw" not found'. But the file is there! I have changed nothing.
Each boot I check the log and I occasionally b43 is loaded successfully. Last time it happened I copied the entries from bootkernel.log so I could compare.
Log when b43 loads correctly:
b43-phy0: Broadcom 4311 WLAN found
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
nvidia 0000:00:05.0: power state changed by ACPI to D0
ACPI: PCI Interrupt Link [LK3E] enabled at IRQ 17
nvidia 0000:00:05.0: PCI INT A -> Link[LK3E] -> GSI 17 (level, high) -> IRQ 17
nvidia 0000:00:05.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86 Kernel Module 180.29 Wed Feb 4 23:44:25 PST 2009
phy0: Selected rate control algorithm 'minstrel'
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
eth0: no link during initialization.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
b43-phy0: Radio turned on by software
eth0: no link during initialization.
Here's what usually happens (b43 errors)
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'minstrel'
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
eth0: no link during initialization.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43-phy0 ERROR: Firmware file "b43/b0g0initvals5.fw" not found
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
eth0: no link during initialization.b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'minstrel'
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
eth0: no link during initialization.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43-phy0 ERROR: Firmware file "b43/b0g0initvals5.fw" not found
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
eth0: no link during initialization.
or sometimes this:
b43-phy0: Broadcom 4311 WLAN found
phy0: Selected rate control algorithm 'minstrel'
Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
eth0: no link during initialization.
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
firmware ssb0:0: firmware_loading_store: unexpected value (0)
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 ERROR: Initial Values Firmware file-format error.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
b43-phy0 ERROR: Microcode not responding
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
eth0: no link during initialization.
Same firmware files! Any ideas why things work sometimes (rarely) but not others? I'm thinking a timing issue maybe, but just grasping at straws right now.

B.
[i]Laptop[/i]: Acer Aspire 5810TZ

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#186 Post by tempestuous »

Yes, I remember that there were similar problems when the bcm43xx driver was first officially used in Puppy around version 2.13.
The solution should be to unload/reload the driver late in the boot sequence.

EDIT: Oops no, don't do this from rc.local, that may mess up network configuration.

I suggest unloading/reloading the b43 driver just before the network configuration script is run. So open /etc/rc.d/rc.sysinit and around line 317 you will see this line -

Code: Select all

/etc/rc.d/rc.network &
Insert the following 4 lines before that line:

Code: Select all

rmmod b43
sleep 1
modprobe b43
sleep 1
Reboot.

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

#187 Post by Barburo »

@tempestuous
Thanks for the suggestions. I tried (both) but same result as before - unable to get a wifi connection.
Here's the output from /var/log/messages
May 27 10:56:10 (none) user.info kernel: b43-phy0: Broadcom 4311 WLAN found
May 27 10:56:10 (none) user.debug kernel: phy0: Selected rate control algorithm 'minstrel'
May 27 10:56:10 (none) user.info kernel: Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
May 27 10:56:12 (none) user.info kernel: eth0: no link during initialization.
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
May 27 10:56:12 (none) user.err kernel: firmware ssb0:0: firmware_loading_store: unexpected value (0)
May 27 10:56:12 (none) user.err kernel: b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
May 27 10:56:12 (none) user.err kernel: b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
May 27 10:56:12 (none) user.notice firmware.sh[5606]: udev firmware loader misses sysfs directory
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
May 27 10:56:12 (none) user.err kernel: firmware ssb0:0: firmware_loading_store: unexpected value (0)
May 27 10:56:12 (none) user.err kernel: firmware ssb0:0: firmware_loading_store: unexpected value (0)
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
May 27 10:56:12 (none) user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
May 27 10:56:12 (none) user.notice firmware.sh[5650]: udev firmware loader misses sysfs directory
May 27 10:56:13 (none) daemon.notice ntfs-3g[5695]: Version 1.2812 integrated FUSE 27
May 27 10:56:13 (none) daemon.notice ntfs-3g[5695]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1)
May 27 10:56:13 (none) daemon.notice ntfs-3g[5695]: Cmdline options: umask=0,no_def_opts
May 27 10:56:13 (none) daemon.notice ntfs-3g[5695]: Mount options: relatime,fsname=/dev/sda1,blkdev,blksize=4096
May 27 10:56:14 (none) user.err kernel: b43-phy0 ERROR: Microcode not responding
May 27 10:56:14 (none) user.err kernel: b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drive ... cefirmware and download the latest firmware (version 4).
May 27 10:56:14 (none) user.info kernel: eth0: no link during initialization.
May 27 10:56:15 (none) user.info kernel: b43-phy1: Broadcom 4311 WLAN found
May 27 10:56:15 (none) user.debug kernel: phy1: Selected rate control algorithm 'minstrel'
May 27 10:56:15 (none) user.info kernel: Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
May 27 10:56:15 (none) auth.info login[5793]: root login on 'tty1'
May 27 10:56:18 (none) user.info kernel: lp: driver loaded but no devices found
The last few lines (I think) relate to the rmmod b43 and modprobe b43 lines I inserted (line 371) as you suggested.
Does the line
user.notice firmware.sh[5650]: udev firmware loader misses sysfs directory
have any significance?
B.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#188 Post by tempestuous »

Barburo wrote:

Code: Select all

user.notice firmware.sh[5650]: udev firmware loader misses sysfs directory
Ah, I think that's an error message produced by the "standard" version of udev, via the firmware.sh script.
But Puppy uses a customised version of udev (pupevent) where firmware.sh has been replaced by pup_event_backend_firmware.

You should raise this with the developers of Lighthouse 4.1.2 RC2. I suspect they may have inadvertently added some udev components when they added KDE.

Some troubleshooting you could do:
- Check whether firmware.sh exists

Code: Select all

cd /
find -name firmware.sh
If it exists, there will almost certainly be a conflict with pup_event_backend_firmware.

- Have a look in /etc/udev/rules.d
and check what rule is calling firmware.sh, because this is wrong.
There should be a udev rule called 50-udev-puppy-basic.rules which calls /sbin/pup_event_backend_firmware

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

#189 Post by Barburo »

@Tempestuous
I will pass on your observations to TazOC.
I find that most times on boot there is no wi-fi connection, but if I unload and load the b43 module several times and use Pwireless after each attempt, eventually the scan works and shows available nodes that I can connect to. If I can make it work somehow I'll take it.

With computing I expect things to be repeatable, so the variable nature of this bug has me a bit stumped.

TazOC is still ironing out the bugs in Lighthouse 4rc2, but I like it because the new SMP kernel boots properly on my hp tx1000, whereas the kernels for 4.1.1 and 4.1.2 do not boot very well and cause problems. Plus 4rc2 has a compiz-fusion .sfs file available that works great.
I use his Lighthouse301g (based on Puppy 3.01) as my day-to-day puppy - It's rock solid.

Again, thanks for your help.
B.
[i]Laptop[/i]: Acer Aspire 5810TZ

User avatar
Barburo
Posts: 298
Joined: Thu 14 Jun 2007, 18:49

#190 Post by Barburo »

tempestuous wrote: Some troubleshooting you could do:
- Check whether firmware.sh exists

Code: Select all

cd /
find -name firmware.sh
If it exists, there will almost certainly be a conflict with pup_event_backend_firmware.

- Have a look in /etc/udev/rules.d
and check what rule is calling firmware.sh, because this is wrong.
TazOC suggested
Try deleting '/etc/udev/rules.d/50-udev-default.rules'. and rebooting. This does call firmware.sh.
... and as soon as I did this and rebooted, all was well and my wi-fi connected automatically.
Thanks for your insight and (hopefully) final resolution of this b43 problem.
B.
[i]Laptop[/i]: Acer Aspire 5810TZ

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#191 Post by 01micko »

A big thank you tempestuous, from me and my little machine.

I just acquired an EEE701SD and I am running Puppy 4.2.1. I installed your pets for wifi, sound and hotkeys and it works like a little beauty.

Now to get my huwei 169 going.. I'll let you know how I get on later.

Cheers
Puppy Linux Blog - contact me for access

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#192 Post by mikeb »

Ok the nfs/nfsd kernel driverset is incomplete in 2.6.25.16

lib/kernel/fs/exportfs/exportfs.ko
lib/kernel/fs/nfsd/nfsd.ko

are needed

mike

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#193 Post by tempestuous »

mikeb wrote:Ok the nfs/nfsd kernel driverset is incomplete in 2.6.25.16

exportfs.ko
nfsd.ko

are needed
Yes, that's strange. The kernel configuration for 2.6.25.16 enables those modules, but it appears that Barry didn't include them in the zdrv driver collection.

So I now attach the missing NFS modules. Modules included:

nfsd
sunrpc
auth_rpcgss
lockd
exportfs

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#194 Post by mikeb »

So I now attach the missing NFS modules. Modules included:
I am now dutifully kissing your freshly washed feet.

regards

mike

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#195 Post by tempestuous »

Here is the genericv4l driver, which provides a Video4linux 1 and 2 interface to video capture capabilities of ATi Mach64 and Rage 128 cards. The source code is from here
http://www.rulerofearth.com/
and is based on earlier "km" source code from the Gatos project
http://gatos.sourceforge.net/v4l2.php

This means that you can use the video input connections on your (old) ATi Mach64/Rage128 card, and also access the analogue TV tuner which is built into "All-In-Wonder" models.
Attachments
genericv4l-k2.6.25.16.pet
for Puppy 4.1/4.2
(27.84 KiB) Downloaded 991 times

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#196 Post by BarryK »

tempestuous wrote:
mikeb wrote:Ok the nfs/nfsd kernel driverset is incomplete in 2.6.25.16

exportfs.ko
nfsd.ko

are needed
Yes, that's strange. The kernel configuration for 2.6.25.16 enables those modules, but it appears that Barry didn't include them in the zdrv driver collection.
Yes, in all puppies from 4.21 back, the Unleashed build script took out some "exotic" modules that I thought would not be needed, to save space.

However, in the new Woof 4-series builds, including the latest "415 alpha", there is virtually no pruning of modules, quite the contrary I have added lots from this thread. So, those nfs modules are retained: I am running 415+ right now, just checked they are there.
[url]https://bkhome.org/news/[/url]

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#197 Post by mikeb »

However, in the new Woof 4-series builds, including the latest "415 alpha", there is virtually no pruning of modules, quite the contrary I have added lots from this thread. So, those nfs modules are retained: I am running 415+ right now, just checked they are there.
Well that's good to here. For linux to linux file sharing nfs provides a solid lightweight solution. It seems to me that catering for the variety of wireless adaptors out there is bulking up the kernel modules demand for space.

regards

mike


Benboom
Posts: 31
Joined: Thu 02 Jul 2009, 16:10

TP-Link WN322G problems

#199 Post by Benboom »

tempestuous wrote: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.
Hi;

On the strength of this post I picked up one of these TP-Link WN322G USB modems (incredibly cheap!) and installed the pet, rebooted and ran the Connect program. It recognized the WLAN and went through the whole process fine and what's more, it showed a signal strength of 100%, which had me jumping for joy as the old USB modem I've been using has poor performance, to say the least. Everything goes well...until I open a browser and try to connect, when I get file not found errors from Seamonkey and Opera 9.64 and 10 beta. Although the system says I have a connection (and the little blinky monitors in the bottom right panel are blinking), plainly I don't.

I'm new to Puppy and almost as new to linux itself. I would be happy to run any shell commands and post their output if it would help debug this; I'd love to be able to use this old laptop more than a few feet away from the router.

Thanks!

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#200 Post by mikeb »

Hi tim , still got simple pup on here...popped it into the 2.xx wrapper just for fun :)

regards

mike

Post Reply