Barry,
Thanks for the distro, works great, but I am using on really slow computer P3 500MHz 256MB RAM frugal installation, so the software is not as responsive as with with the little bigger but faster for old computers distro version, I am talking about version around 169 MB size of the iso. If there is no problem I prefer to use sfs with smaller compression ratio, it just works faster

mrokosz
P.S. Everything works great, Pemasu package problems not there any more. I guess it will replace Pemasu distro

P.S. Everything works great, Pemasu package problems not there any more. I guess it will replace Pemasu distro

Pemasu is a bit busy right now, see earlier post this Forum thread. But, he is a Puppy addict like the rest of us, and will be back to do another build from latest Woof -- so, whatever development we do with alpha3 will be going into Woof, and pemasu will pick up from there, the very latest. I mean, nothing will be lost here, it is all cumulative._________________http://bkhome.org/news/

jim3630, peebee, pemasu, Broadcom 43xx users,
I have attached my refined experimental package to select and load the appropriate Broadcom wifi driver for each variant of the 43xx devices -- b43, b43legacy, brcmsmac, wl, wl (older version). It is also intended to support b44 ethernet devices even with the wl loaded; but I cannot, myself, verify that that would be successful.

The logic ensures that only the wl driver is loaded even if a device is also supported by b43 or brcmsmac. As before, to avoid using the (default) wl driver, simply blacklist it in the BootManager. Also as before, if the wl driver cannot handle a device (device not detected), it will be automatically blacklisted so that another driver gets loaded at the next boot-up. (You can un-blacklist it in the BootManager.)

If you experience a problem with the main experiment-4 package, you can instead use either the 4a or 4b packages to ensure that only wl or brcmsmac (respectively) are available for use. That is to eliminate any influence by the main-package logic or the other drivers.

Note that brcmsmac cannot be used on an adhoc network, so please avoid doing that. Please send me a pmodemdiag file if you encounter a problem with these packages.

Note also that jim3630 has more success using frisbee as the network interface for his brcmsmac-using device. But I hope to also have SNS and the network wizard work with the newer (wl, brcmsmac) drivers, but need the expertise of those more familiar with the workings of wifi connection.

Thanks for any feedback you can provide.
Richard

UPDATE 6/15/2012: The "5delta" package is added to address the cases where the proprietary driver fails for some (BCM4312 - hardware ID 14e4:4312) models that can also use the open-source driver. In experiment-4, a reboot was necessary to get the open-source driver to take over. The new package makes the substitution during the first boot-up after its installation. Although the logic appears to function as intended, it must be tried with the target device installed, to verify whether the substitution is truly effective and allows immediate connection. Please send me a pmodemdiag file if you can run the test. You should see driver b43 used, instead of no detection during first boot-up. TIA.

UPDATE 7/13/2012: The "5-6delta" package is added for minor mods and to move the b43 firmware files from the b43 "tarball"/directory into /lib/firmware/b43, to avoid a shutdown hang related to the absence of the firmware during the first boot-up. With that change, the module is successfully changed from wl to b43 if wl fails, all during the first boot-up. This was verified with dpup-exprimo.

UPDATE 7/14/2012: Re-uploaded "5-6delta" after download number 6, to remove the moving of b43 firmware during the installation and to add a test so that the b43 driver is not loaded if the firmware is not in /lib/firmware (ready for use). This prevents the b43-firmware-related shutdown hang if the firmware is not ready, making the implementation safe no matter where the b43 firmware is.
Richard

precise_broadcom_experiment-5-6delta.pet

Description

Additional refinement to experiment-4 and 5delta, to switch driver wl to b43 during first boot-up.Applies to BCM4312 wifi device (which may be named BCM4311).No firmware relocation, but switches drivers immediately only if b43 firmware is ready.

Just been playing with the latest Precise Beta 5.2.38 released earlier today. Another li'l beaut. Like its Upup predecessors nice and snappy!

Just as with Ubuntu Precise Pangolin itself the ATI video card causes grief - nothing new here. With ATI graphics under Linux you have two choices. Either install the open source Radeon driver or the proprietary FGLRX driver. The current Radeon open source driver has been broken in recent kernel versions - so that just leaves the proprietary option.

You need to have both the devx and the kernel sources activated on your system. The bad news is that it does build - but with errors that result in an extremely slow frame rate performance.

The better news is that there is a tiny hack available that seems to work around the problem - see here:

Why is the module in /opt? Why can't it be inside /lib/modules/3.2.18?

It enables me to build multi kernel versions for puppies like slacko which come with 2 kernel flavours - and I like to keep the same template for all puppies I am supporting. The pinstall hard links the wl.ko to the correct version for the kernel.

shinobar uses a similar but I think less elegant technique for his nvidia sfs's which also support multi kernels but you end up with lots of surplus /lib/modules/ kernel specific directories.

If there is a better way to support multi-kernels with one pet when the drivers are kernel dependent then I'm ready and eager to learn.

[Later edit] - I have now extended the technique to make a single mutli-kernel version of the driver - this uses a base-driver and xdelta3 delta files to create the kernel specific drivers at install time. See here[/edit]

I just now discovered a minor bug in the experiment-4 package that modifies the firmware.dep file incorrectly, affecting 2 entries for Broadcom wifi and ethernet. I have re-uploaded experiment-4 with the correction to the relevant edit command.

The bug should not affect you unless your Broadcom device uses either of the b43legacy or b44 drivers. To correct the problem directly, please edit /etc/modules/firmware.dep.<kernel version>. The incorrect entries are

Just be sure that you have installed experiment-4, then 5delta, then 5-6delta. I am using multiple deltas because pemasu has been including each level in various exprimo versions. You need install only those of these packages not already installed.

We discovered that the b43 firmware needs to be in place in /lib/firmware before the first boot-up of a puppy. Otherwise, the driver failure due to the absence of the firmware seems to result in a serious hang during shutdown. If you have a Broadcom 4312 (aka, 4311) wifi device that produces a failure message (in dmesg), try making a remaster of a fresh puppy plus packages -4, -5delta and -5-6delta, to see the benefit of its connecting on the first boot-up.
Richard

I will try this with my BCM4311, great that you try to automate the setup

I have tried to get this chip working wireless for months now. Sometimes it is okay even for a couple of reboots, but most of the times the card isn't found at all when checking with 'lspci'.

What I have found out is what you wrote:
1). The card needs to be detected, probably with 'broadcom_wl-K3.1.10-slacko_4gA' and 'ssb' in the ADDLIST. But that only works sometimes (and I don't understand when the success happends)
2). When the card is detected, 'wl' has to be removed and instead 'b43' has to be activated (with 'modprobe')
3). Then I see the wireless networks and are able to connect.

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