b43-fwcutter-013-i486-1pw.txz + SLKBUILD for b43-firmware

[zAchAry]

Haha, thank you

I'll uninstall my current installation of b43, restart the machine, use the brand new SLKBUILD (and the bash script) and I'll let you know the results. (I'll do it tomorrow or the day after tomorrow).

edit:
The shell script is really cool, so far

Code: Select all

+---------------------------+
| b43-firmware installation |
+---------------------------+

Please remove the following package(s) and try again:


b43-firmware-4.178.10.4-fw-1pw

-------------------------------------------
would it be safe if there will be a text says:

remove the... by entering "spkg --remove b43-firmware-4.178.10.4-fw-1pw" (or "spkg --remove b43-firmware")
Or guiding the user to Gslapt to remove an existing b43-firmware?
-------------------------------------------
Never mind, it'll be added to the Wiki if needed.

+ I've studied all day and I'm very sleepy...

never try to do anything while you are sleepy

source: http://www.salixos.org/forum/viewtopic.php?p=8382#p8382

[pwatk]

Is this kind of nannying really necessary?

If you've managed to install the b43-fwcutter package and a previous version of the b43-firmware package then I'm sure you can remove it again!

FYI, if you have an ethernet connection available you really don't need to reboot. The b43-firmware package will reload the kernel modules anyway!

[zAchAry]

Sorry for the extra and unnecessary suggestion Never mind, it'll be added to the Wiki if needed.

FYI, if you have an ethernet connection available you really don't need to reboot. The b43-firmware package will reload the kernel modules anyway!

Revision, just "to be on the safe side".

[pwatk]

Revision, just "to be on the safe side".

Edit: Nearly forgot... I've uploaded the new SLKBUILD.

[zAchAry]

I uninstalled ALL b43 stuff here
WiFi still worked
I restarted the machine
WiFi is not working at all
# slapt-get -i b43-fwcutter
# sh <your_bash_script>

All is working awesome!

[pwatk]

I've updated the b43-fwcutter package here.

The install-b43-firmware script and an archive (b43-firmware.tar.gz) containing the SLKBUILD rc.b43 and b43.txt files required to compile the b43-firmware package are now included under /usr/share/b43-fwcutter.

You'll notice I've abandoned downloading the SLKBUILD from my ftp space at people.salixos.org. Instead, I'll update the b43-firmware scripts with a new release of the b43-fwcutter.

I've made some changes to the install-b43-firmware script so I'd appreciate it if you could give the whole thing a spin before I submit it on the bugtracker.

Thanks.

[zAchAry]

Edit: I'm using SalixOS 32-bit and your package seem to be a 64-bit package

You'll notice I've abandoned downloading the SLKBUILD from my ftp space at people.salixos.org. Instead, I'll update the b43-firmware scripts with a new release of the b43-fwcutter.

Very good, I was hoping that you'll do such thing without me asking (bugging) you

I've made some changes to the install-b43-firmware script so I'd appreciate it if you could give the whole thing a spin before I submit it on the bugtracker.

I'm going to uninstall all b43 stuff that I got and I'll use b43-fwcutter-013-x86_64-2pw.txz.

Edit:
I uninstalled ALL b43 stuff here
WiFi still worked
I turned off b43 (System services box)
WiFi is not working at all
I turned on b43 (System services box)
WiFi is not working at all
I restarted the machine
WiFi is not working at all
# installpkg b43-fwcutter-013-x86_64-2pw.txz

Code: Select all

root[~]# install-b43-firmware.sh
bash: install-b43-firmware.sh: command not found
root[~]# /usr/share/b43-fwcutter/install-b43-firmware.sh


b43-firmware installer:

This script will download, compile and install the b43-firmware package.

If you have a device with a low-power PHY (LP-PHY) e.g. BCM4312 then
select version 4.178.10.4 else select version 4.150.10.5.

1. 4.150.10.5
2. 4.178.10.4

Please select firmware version [1-2]: 2

You have selected version `4.178.10.4'

Do you wish to continue [Y/n]: y

Downloading broadcom-wl-4.178.10.4.tar.bz2

--2010-09-18 19:51:59--  http://downloads.openwrt.org/sources/broadcom-wl-4.178.10.4.tar.bz2
Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177
Connecting to downloads.openwrt.org (downloads.openwrt.org)|78.24.191.177|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5986780 (5.7M) [text/plain]
Saving to: “broadcom-wl-4.178.10.4.tar.bz2”

100%[======================================>] 5,986,780    278K/s   in 21s     

2010-09-18 19:52:21 (274 KB/s) - “broadcom-wl-4.178.10.4.tar.bz2” saved [5986780/5986780]

rc.b43 found in current directory
b43.txt found in current directory
Settings option nosrcpack
Setting option noautodotnew
build-b43-firmware.sh has been created
tar -xf broadcom-wl-4.178.10.4.tar.bz2
./build-b43-firmware.sh: line 183: /usr/bin/b43-fwcutter: cannot execute binary file
ERROR: Package file does not exist. (b43-firmware-4.178.10.4-fw-*pw.t?z)
ERROR: Package installation failed!
root[~]# 

2) why is there a lock icon in gslapt? (Edit: because it's a 64-bit package and 64-bit is listed in my blacklist)



3) Consider me as one who knows nothing about where the installation bash script should be located at, but can you please consider to make a file that is a shortcut to /usr/share/b43-fwcutter/install-b43-firmware.sh and this shortcut will be named as b43-firmware b43 or install-b43 or install-b43 or something else and will be located at /usr/bin or maybe at /usr/sbin. what I mean is that it would be easier to:

Code: Select all

# slapt-get -i b43-fwcutter
# <name of the shortcut>

[pwatk]

Edit: I'm using SalixOS 32-bit and your package seem to be a 64-bit package

Sorry, you'll have to compile the b43-fwcutter yourself.

You'll notice I've abandoned downloading the SLKBUILD from my ftp space at people.salixos.org. Instead, I'll update the b43-firmware scripts with a new release of the b43-fwcutter.

Very good, I was hoping that you'll do such thing without me asking (bugging) you

Glad to see we agree on this .

2) why is there a lock icon in gslapt? (Edit: because it's a 64-bit package and 64-bit is listed in my blacklist)

I was about to say I was unsure until I noticed your edit.

./build-b43-firmware.sh: line 183: /usr/bin/b43-fwcutter: cannot execute binary file

This is explained by the fact your trying to execute a 64bit binary on a 32bit system.

3) Consider me as one who knows nothing about where the installation bash script should be located at, but can you please consider to make a file that is a shortcut to /usr/share/b43-fwcutter/install-b43-firmware.sh and this shortcut will be named as b43-firmware b43 or install-b43 or install-b43 or something else and will be located at /usr/bin or maybe at /usr/sbin. what I mean is that it would be easier to:

Code: Select all

# slapt-get -i b43-fwcutter
# <name of the shortcut>

I've placed the install-b43-firmware.sh outside of the system path deliberately so the user has to execute the script manually and it can't be run by accident. I've also mentioned it in the slack-desc.
When I submit this new package I'll see how the devs feel about it.

Thanks for testing though and I hope everything goes without a hitch with a 32bit package.

[zAchAry]

Sorry, you'll have to compile the b43-fwcutter yourself.

So how can I assist you then?

[pwatk]

Uninstall the 64bit package you've installed, download the SLKBUILD and slkbuild -X as usual. Then everything should work fine.

The only binary required is the b43-fwcutter, the firmware itself has no architecture!

FYI, I am considering compiling 32bit packages in VirtualBox and then uploading both in future, I just don't know when .