Salix Forums

Cleaned up doinst.sh.

This should be the last time I mess with this until there's version update.

pwatk wrote:This package has been updated to include an rc.b43 script. Please remove any references to the b43, ssb, wl or lib80211 kernel modules from the bottom of your /etc/rc.d/rc.modules or /etc/modprobe.d/blacklist files (if they exist) before installing any future packages.

I got the following files:

* /etc/rc.d/rc.modules which is a shortcut to /etc/rc.d/rc.modules-2.6.33.4-smp (link)
* /etc/modprobe.d/blacklist.conf (link)

Sorry. Yes those are the correct files I'll amend my post.

Your looking for this at the bottom of your rc.modules file:

Code: Select all

...
/sbin/modprobe ssb
/sbin/modprobe b43

...and this in your blacklist.conf file:

Code: Select all

...
blacklist wl
blacklist lib80211

I have non of those as you can see (two links above)
Is it safe to install the SLKBUILDs now?

I've installed your first (I think) SLKBUILDs that you've posted

Code: Select all

b43-firmware 4.178.10.4-fw-1pw
b43-fwcutter 013-i486-1pw

Your good to go

.

I'll try to remember to write a script to remove the relevant lines if they exist.

It only applies to anyone who installed more recent versions of the b43-firmware package i.e. in the last week.

pwatk wrote:I'll try to remember to write a script to remove the relevant lines if they exist.

DO NOT forget to create a .BAK (backup) files of the already existing ones if something will get messed up.
But I'm sure that you're savvy enough for both, making a backup and doing a perfect job.

Should there really be a backup?
I'm really paranoid when system files are involved... sorry about that.

Should there really be a backup?
I'm really paranoid when system files are involved... sorry about that.

So you should be. This problem wouldn't exist if I hadn't started writing to these files in the first place!

That said deleting those two files (and the rc.modules--2.6.33.4{,-smp}) and reinstalling the udev and kernel-modules{,-smp} packages would also solve the problem but thats a bit drastic.

pwatk wrote:This problem wouldn't exist if I hadn't started writing to these files in the first place!

What could you do instead? (curious)

dependencies:
You did not mentioned in your .dep files anything.
I've already forgot which depends on which. [Edit: b43-firmware requires b43-fwcutter]

md5sum:
I've finished to build the .txz packages with slkbuild -X and I'm wondering
why the md5sums of my .txz files aren't in accord with yours?

Your b43-fwcutter-013-i486-1pw.md5

Code: Select all

b0bb5d7e121552377cab16ec23662d41  b43-fwcutter-013-i486-1pw.txz

My b43-fwcutter-013-i486-1pw.md5

Code: Select all

48a38ac2579c60c2aa1c16b7d5c10769  b43-fwcutter-013-i486-1pw.txz

Your b43-firmware-4.178.10.4-fw-1pw.md5

Code: Select all

e8d4be09f56f51d8016db4bfec86d0b2  b43-firmware-4.178.10.4-fw-1pw.txz

My b43-firmware-4.178.10.4-fw-1pw.md5

Code: Select all

78e0a3f7d3e88ba9392203357ed4a37a  b43-firmware-4.178.10.4-fw-1pw.txz

I'm sorry for asking so many questions.

zAchAry wrote:
pwatk wrote:This problem wouldn't exist if I hadn't started writing to these files in the first place!
What could you do instead? (curious)

dependencies:
You did not mentioned in your .dep files anything.
I've already forgot which depends on which. [Edit: b43-firmware requires b43-fwcutter]

b43-fwcutter is a build dependency but it isn't required after that!
I can see your point though so I'll put it in the dep file later (or tomorrow now).

zAchAry wrote:md5sum:
I've finished to build the .txz packages with slkbuild -X and I'm wondering
why the md5sums of my .txz files aren't in accord with yours?

Your b43-fwcutter-013-i486-1pw.md5
Code: Select all
b0bb5d7e121552377cab16ec23662d41  b43-fwcutter-013-i486-1pw.txz
My b43-fwcutter-013-i486-1pw.md5
Code: Select all
48a38ac2579c60c2aa1c16b7d5c10769  b43-fwcutter-013-i486-1pw.txz
Your b43-firmware-4.178.10.4-fw-1pw.md5
Code: Select all
e8d4be09f56f51d8016db4bfec86d0b2  b43-firmware-4.178.10.4-fw-1pw.txz
My b43-firmware-4.178.10.4-fw-1pw.md5
Code: Select all
78e0a3f7d3e88ba9392203357ed4a37a  b43-firmware-4.178.10.4-fw-1pw.txz

Could be a difference in the rate of compression, I don't know. Compare the build logs.

zAchAry wrote:I'm sorry for asking so many questions.

Don't be, your the only person testing this so I appreciate the feedback.

I'm going to update this again (probably tomorrow now) so the removal of the aforementioned lines in blacklist.conf and rc.modules are handled by the package installation.

I also need to add in a command to remove the executable bit (chmod 644) from /etc/rc.d/rc.broadcom-sta (if it exists) as this could cause issues for people who install both packages whilst trying to get their wireless working.

Finally, from now on if I update the package I will increment the release number of the package.

Example:
b43-firmware-4.178.10.4-fw-1pw.txz
b43-firmware-4.178.10.4-fw-2pw.txz

I was doing this but I stupidly reset everything when I updated all the scripts before uploading to people.salix.org!

Salix Forums

b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware

Re: b43-fwcutter and b43-firmware