Posted: Sat 23 May 2009, 16:39
Thanks a lot, tempestuous! Worked great
READ-ONLY Archive
https://oldforum.puppylinux.com/
as you found any changes are carried over except in certain areas...eg /var /tmp /dev...even changing kernels can be done via a remasterHello,
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.
Here's what usually happens (b43 errors)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.
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-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.
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.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.
Code: Select all
/etc/rc.d/rc.network &
Code: Select all
rmmod b43
sleep 1
modprobe b43
sleep 1
The last few lines (I think) relate to the rmmod b43 and modprobe b43 lines I inserted (line 371) as you suggested.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
have any significance?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.Barburo wrote:Code: Select all
user.notice firmware.sh[5650]: udev firmware loader misses sysfs directory
Code: Select all
cd /
find -name firmware.sh
TazOC suggestedtempestuous wrote: Some troubleshooting you could do:
- Check whether firmware.sh existsIf it exists, there will almost certainly be a conflict with pup_event_backend_firmware.Code: Select all
cd / find -name firmware.sh
- Have a look in /etc/udev/rules.d
and check what rule is calling firmware.sh, because this is wrong.
... and as soon as I did this and rebooted, all was well and my wi-fi connected automatically.Try deleting '/etc/udev/rules.d/50-udev-default.rules'. and rebooting. This does call firmware.sh.
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.mikeb wrote:Ok the nfs/nfsd kernel driverset is incomplete in 2.6.25.16
exportfs.ko
nfsd.ko
are needed
I am now dutifully kissing your freshly washed feet.So I now attach the missing NFS modules. Modules included:
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.tempestuous wrote: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.mikeb wrote:Ok the nfs/nfsd kernel driverset is incomplete in 2.6.25.16
exportfs.ko
nfsd.ko
are needed
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.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.
Hi;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.