(old)Puppy Linux Discussion Forum

pemasu wrote:Here is that previously posted link to b43 firmware rpm package as pet.
It installs the whole 117 firmwares to /lib/firmware/b43/

Thanks as always pemasu.

I loaded the "new" firmware onto a pristine, manual, frugall install of 5.3.1.4 - all OK with my B43

But its definitely much newer firmware than is currently in woof:

New: Old: Can we update???

Cheers
peebee

These firmware packages are kernel version spesific. The one 01micko posted a link to rpm which I packaged as pet is meant to kernel 3.2.X and and then there is firmware package for older kernels.

So...I wouldnt make firmware update request for woof....since Barry posted that he wants to stick with 3.0.17 due to unionfs support for it.
01micko and I have used aufs with our 3.1.X and 3.2.X experiments...so there is no kernel version restriction like with unionfs.

pemasu wrote:These firmware packages are kernel version spesific.

Hi pemasu

I realise that you know much more about such things than me - but I'm pretty sure the firmware has been the same version over many different kernels and puppies at least in the k2 kernel series.....

Should I try the "new" firmware in say wary522 - I think I will just for interest -

It didn't work - wary522 with the "new" firmware couldn't detect any networks - I'll try it with other k3 puppies as I get chance.

Cheers
Peebee

I dont know much more than you. I just noticed that there are two different downloadable firmware packages:
http://linuxwireless.org/en/users/Drive ... oned_above

What is the practical difference, I dont know...
But of course you can experiment.

I just can speculate, that there are newer supported hw with newer kernel...so there is need for new firmware package and maybe due to b43 driver update...not all older firmwares does work optimally, but as I said....just my speculation.

Oh...I have forgotten to post my test feelings. Nothing much to tell. My troublesome touchpad works like charm, wlan connection with no problem. Installing pets...extracting stuff with rox right click pet stuff....downloaded latest woof2 commit, updated my building platform...posting....using...all works what I have needed.

So....Mostly harmless....

Hi all

drblock2, good you found a work-around, kernel source is in the main post.

mavrothal, wl is only compiled for Slacko with 2.6.37 (MAIN), you could try it. I can do it for later kernels, already have the latest source.

lol a@ u pemasu

...Mostly harmless....

. Also I have the woof patch ready, just doing a build for sanity check. Compiled 3.2.2 too in the hope it solves Jim1911's logitech wireless mouse. Only manual step is to insert the b43 firmware in the kernel pet so that will be a sanity check too making sure it overwrites the woof firmware.

Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

pemasu wrote:Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

I wonder why a symlink is needed? Perhaps ask Iguleder if it can be done without the symlink.

I am not happy with grump and pemasu .....

Cos they finally got my Hell wireless to work.

>>> Dell Studio XPS 1340

Many...many thanks gents.

""""""""""

I saw grump's post.

" BINGO!

After getting that rpm (from another site and on my other lappy) and finding how to un-rpm an rpm I had the contents of lib/firmware/b43. First try was with a pfix=ram start, then copy the firmware into the original spot. This did not bring up the wireless.

2nd try was also with a pfix=ram,

but this time renamed the original ././b43 to b43_old,

then copied the new one in.

Then in the network wizard unloaded the b43 module,

then reloaded it.

When I tried scanning for a wireless network the blue status light
came on, and then I was called to dinner so I shutdown with save.
After a normal boot the blue light came on and I was able to set up
the wireless in the usual way.

Thanks for all the work and knowledge - and straightforward advice.

So - steps are:
- get the right firmware files
- rename the old firmware files
- copy in the new ones
- unload the b43 module (has rwong firmware)
- reload the b43 module (now has right FW)
- configure wireless. "

"""""""""""""

Then I saw that lurker >> pemasu ....post his
b43-firmware-5.100.138.pet

""""""""""

A one time moment of knowledge came upon me.
Do a combo of the 2 fixes above.

So I renamed >> b43 to b43_old

in >> /lib >> /firmware

now unload the >> b43 module >>(which has the wrong firmware)

Go back to >>> /lib >> /firmware

and add a new folder b43....
you probably should have done it before....

Now load the >>> b43-firmware-5.100.138.pet
from the mighty >> pemasu

Look in your new b43 folder....there are all the new 117 firmware files

Use the network wizard...not simple network wizard

with the usual steps....and it's all go for Broadcom wireless.

Once again you 2....bloody brilliant.

micko....seamonkey works great.

::::::

Despite contrary advice...I'm going to test this in Saluki
and others.

Cheers.....Chis.

BarryK wrote:

pemasu wrote:Just testing 3.2.1 kernel, compiled in dpup. Seems to work. I think it is that symlink from 3.2.1-dpup to 3.2.1 in /lib/modules/ which gives hiccup for me at 3builddistro stage. It did when I last used Iguleders vanilla kernel kit.

But...thank you of this updated kernel kit. It didnt demand much editing. And it worked oob. Great stuff. Almos as good as chocolate.

I wonder why a symlink is needed? Perhaps ask Iguleder if it can be done without the symlink.

I don't know why it's there either.. I'm just going to delete it and forget the woof patch. Should still work ok.. although I wonder if it's there for the kernel source? I'll test that too.

Edit: Bummer.. the link is there for the kernel source.. and I discrded my patch! Easy enough though.

No... the src is no good, script error, will fix soon, orig 3build distro is fine.

Barry, I put the symlink there for users who don't know about uname and want the exact kernel version - nothing more, nothing less. You can remove it - no harm done.

Iguleder.. have you got homebank-4.4 src somewhere? I can't find it and the site is down (and your build script would be cool too )

I do miss also those numerous build scripts, which were uploaded in www.iguleder.info

Hi

mavrothal wrote:...My iMac has an 432B chip and it would appear that only the broadcom-wl driver can handle it.
Did you say you compiled it?...

Attached is one i built using these sources: hybrid-portsrc_x86_32-v5_100_82_112.tar.gz

I used the pinstall.sh script from one of 01micko's earlier packages: broadcom_wl-K2.6.37.6-spup.pet
When installing it gives the following message:

• module 'wl' is installed.
  You may need to blacklist
  b43 broadcom wireless driver.
  You will need to reboot.

but i found that i did not need to do either.

My test machine is an Acer Aspire 5552
which has a Broadcom Corporation BCM43225 802.11b/g/n (rev 01) wireless adapter.

When you run the Network Wizard,
click to add it to the list of modules supporting WPA encryption. (see pics)

Hope this helps
CatDude
.

01micko and pemasu - here's the whole thing. That's the exact kit used to build all packages for Guy Dog; you can use it with pretty much any Puppy.

I'm currently working on a "version 2" of this thingy, so this is just a raw dump of the old kit.

I'm also working on my own distro (which is a Puppy 6 concept of mine), which utilizes both the new implementation and a Woof implementation I wrote on my own

pemasu, I'll attach the latest 3.2x build kit. Where I want to go with this is make it so you can choose version, suffix etc instead of hacking the script and download and install FWs.

We have a sane build now and kernel source! Works fine with stock woof 3builddistro.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Alpha 5 is out


See main post







.

Rather than wait for the next Alpha, I downloaded the kernel sources and compiled the nvidia 173.14.31 driver.

It installed easily. The run script gives you the option of automatically changing xorg.conf.

Much improved performance, ca. 1270 fps with glx-gears as compared to ca.140 fps with vesa-mesa.

This is quite a relief as I was afraid my old friend AMD Athlon XP/MP (Barton) with an nvidia GeForce FX 5200 was not going to make the transition to kernel 3x.

I did a manual frugal install to a 4GB flash drive.
I installed mesa from slickpet + devx + kernelsource sfs and compiled amd-driver-installer-12-1-x86.x86_64.run

Fri 27 Jan 2012 Operating System: Slacko Puppy-5.3.1.5 Linux 3.2.2-slacko_4g
5.0 VGA compatible controller:ATI Technologies Inc M880G[MobilityRadeonHD4200]
oem: ATI ATOMBIOS product: RS880M 01.00

X Server: Xorg Driver: # vesa
X.Org version: 1.9.5
dimensions: 1024x600 pixels (270x158 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: ATI
server glx version string: 1.4
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4200 Series
OpenGL version string: 3.3.11399 Compatibility Profile Context

AMD Athlon(tm) II Neo K125 Processor
Core 0: 800 MHz

# glxgears
8137 frames in 5.0 seconds = 1627.331 FPS
8172 frames in 5.0 seconds = 1634.341 FPS
8170 frames in 5.0 seconds = 1633.971 FPS

Network controller Broadcom Corporation BCM43225 802.11b/g/n

No problems at all so far on this netbook.

Nvidia pc report later.

Equipment:

AMD Athlon XP/MP (Barton), 2GHz
nvidia GeForce FX 5200

Alpha 5, like Alpha 4, boots to a screen without menus. Downloaded and installed the mesa-7.10.2-s.pet as suggested and then attempted to switch to vesa via xorgwizard as I had before in Alpha 4.

This time the experiment was not successful. Selecting vesa in the xorgwizard produced a black screen. Rebooting installed vesa, but no menus!

I copied my Alpha 4 mesa-vesa save file to the Alpha 5 directory and rebooted. The save file updated nicely and produced fine menus.

I installed the Alpha 5 devx and kernel source sfs-files and successfully compiled the nvidia 173.14.31 driver. Under Alpha 5, the card is considerably faster: glx-gears ca. 2490 fps as compared to 1270 fps with Alpha 4, but the situation remains rather problematic.

I'm running from the live dvd with a save file.
I installed mesa from slickpet.
I installed the devx+kernelsource+compiled NVIDIA-Linux-x86-275.43.run
I installed some other sfs files too.

Fri 27 Jan 2012 Operating System: Slacko Puppy-5.3.1.5 Linux 3.2.2-slacko_4g
0.0 VGA compatible controller:nVidia Corporation G84[GeForce 8600 GT] (rev a1)
oem: NVIDIA product: G84 Board - p402h00 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.9.5
dimensions: 1440x900 pixels (373x231 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8600 GT/PCI/SSE2
OpenGL version string: 3.3.0 NVIDIA 275.43

Intel(R) Core(TM)2 Quad CPU Q6600
Core 0: 1603 1: 1603 2: 1603 3: 1603 MHz

# glxgears
49458 frames in 5.0 seconds = 9891.580 FPS
49480 frames in 5.0 seconds = 9895.856 FPS
49475 frames in 5.0 seconds = 9894.807 FPS

Ethernet controller Intel Corporation 82566DC-2 Gigabit Network Connection

No problems so far.