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 Mon 22 Sep 2014, 14:27
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 13 of 17 [249 Posts]   Goto page: Previous 1, 2, 3, ..., 11, 12, 13, 14, 15, 16, 17 Next
Author Message
evgeniy

Joined: 21 May 2009
Posts: 5

PostPosted: Sat 23 May 2009, 12:39    Post subject:    

Thanks a lot, tempestuous! Worked great Smile
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5260
Location: Australia

PostPosted: Mon 25 May 2009, 02:48    Post subject:  

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
acerhdf-0.2.2-2-k2.6.25.16.pet
Description  for Puppy 4.1-4.2
pet

 Download 
Filename  acerhdf-0.2.2-2-k2.6.25.16.pet 
Filesize  4.92 KB 
Downloaded  847 Time(s) 

Last edited by tempestuous on Mon 25 May 2009, 22:38; edited 1 time in total
Back to top
View user's profile Send private message 
evgeniy

Joined: 21 May 2009
Posts: 5

PostPosted: Mon 25 May 2009, 07:44    Post subject:  

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.
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 8253

PostPosted: Mon 25 May 2009, 11:37    Post subject:  

Quote:
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 Smile

mike
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Tue 26 May 2009, 15:10    Post subject: B43 module loading problem with kernel 2.6.28.5  

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:
Quote:
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)
Quote:
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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware and download the latest firmware (version 4).
eth0: no link during initialization.

or sometimes this:
Quote:
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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware 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.

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

Joined: 10 Jun 2005
Posts: 5260
Location: Australia

PostPosted: Tue 26 May 2009, 23:23    Post subject:  

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:
/etc/rc.d/rc.network &

Insert the following 4 lines before that line:
Code:
rmmod b43
sleep 1
modprobe b43
sleep 1

Reboot.
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Wed 27 May 2009, 15:33    Post subject:  

@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
Quote:
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/Drivers/b43#devicefirmware 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/Drivers/b43#devicefirmware 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
Quote:
user.notice firmware.sh[5650]: udev firmware loader misses sysfs directory
have any significance?
B.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5260
Location: Australia

PostPosted: Thu 28 May 2009, 03:20    Post subject:  

Barburo wrote:
Code:
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:
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
Back to top
View user's profile Send private message 
Barburo


Joined: 14 Jun 2007
Posts: 283

PostPosted: Mon 01 Jun 2009, 01:26    Post subject:  

@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.

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


Joined: 14 Jun 2007
Posts: 283

PostPosted: Mon 01 Jun 2009, 21:42    Post subject:  

tempestuous wrote:

Some troubleshooting you could do:
- Check whether firmware.sh exists
Code:
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
Quote:
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.

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


Joined: 11 Oct 2008
Posts: 7802
Location: qld

PostPosted: Fri 12 Jun 2009, 18:25    Post subject:  

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

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
mikeb


Joined: 23 Nov 2006
Posts: 8253

PostPosted: Tue 16 Jun 2009, 16:33    Post subject:  

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
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5260
Location: Australia

PostPosted: Mon 22 Jun 2009, 22:10    Post subject:  

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
NFS-modules-k2.6.25.16.pet
Description  for Puppy 4.1/4.2
pet

 Download 
Filename  NFS-modules-k2.6.25.16.pet 
Filesize  226.5 KB 
Downloaded  685 Time(s) 
Back to top
View user's profile Send private message 
mikeb


Joined: 23 Nov 2006
Posts: 8253

PostPosted: Tue 23 Jun 2009, 11:52    Post subject:  

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


I am now dutifully kissing your freshly washed feet.

regards

mike
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5260
Location: Australia

PostPosted: Fri 03 Jul 2009, 00:22    Post subject:  

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.
genericv4l-k2.6.25.16.pet
Description  for Puppy 4.1/4.2
pet

 Download 
Filename  genericv4l-k2.6.25.16.pet 
Filesize  27.84 KB 
Downloaded  697 Time(s) 
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 13 of 17 [249 Posts]   Goto page: Previous 1, 2, 3, ..., 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.1221s ][ Queries: 13 (0.0086s) ][ GZIP on ]