 Show Posts
|
|
Pages: [1] 2 3 ... 5
|
|
5
|
General / General topics / Re: Pardus End of Life
|
on: December 21, 2011, 15:17:00 PM
|
|
All this EoL appears to be hoax. do u think if there is any such thing happening it will not be announced?
In the Turkish forum I saw discussion on P2012!
|
|
|
|
|
6
|
General / General topics / Re: Pardus End of Life
|
on: December 21, 2011, 11:25:16 AM
|
I hope everything remains stable as I just installed it on a friend's PC with a lot of praise for it  3 or 4 devs leaving should not be an issue, especially if this is being sponsored by a govt entity. I am definitely NOT going to Windows, come what may! Windows is one of the worst OSes on this planet.  |
|
|
|
|
11
|
General / As seen on the internet / Re: helpful wireless how-to for Broadcom chipsets
|
on: December 14, 2011, 07:55:54 AM
|
Looking at what is already available in Pardus, I see a utility called, b43-fwcutter. You can read about it in terminal doing: man b43-fwcutter "DESCRIPTION
b43-fwcutter can extract the firmware for your Broadcom 43xx hardware from different closed source drivers. The b43 driver depends on this firmware files and can't work without them.
Currently b43-fwcutter supports Apple MacOS X, Microsoft Windows 98/ME/2000/XP and Linux drivers, but keep in mind that b43-fwcutter doesn't support all driver versions.I've never used it. Here is what I get with this terminal command: $ b43-fwcutter -l
b43-fwcutter version 015
Extracting firmware is possible from these binary driver files.
Please read http://linuxwireless.org/en/users/Drivers/b43#devicefirmware
<driver> <filename> <microcode> <MD5 checksum>
b43legacy wl_apsta.o 295.14 e08665c5c5b66beb9c3b2dd54aa80cb3
b43 wl_apsta.o 351.126 9207bc565c2fc9fa1591f6c7911d3fc0
b43 wl_apsta_mimo.o 351.126 722e2e0d8cc04b8f118bb5afe6829ff9
b43 wl_apsta_mimo.o 410.2160 cb8d70972b885b1f8883b943c0261a3c
b43 wl_apsta.o 478.104 bb8537e3204a1ea5903fe3e66b5e2763
b43 wl_prebuilt.o 508.1084 490d4e149ecc45eb1a91f06aa75be071
b43 wl_apsta.o 508.1107 f06c8aa30ea549ce21872d10ee9a7d48
b43 wl_apsta.o 508.10872 e413c0017b99195f3231201c53f314d1
b43 wl_apsta.o 508.154 023fafbe4918e384dd531a046dbc03e8
b43 wl_apsta.o 644.1001 68f38d139b1f69f3ea12393fb645c6f9
b43 wl_apsta.o 666.2 e1b05e268bcdbfef3560c28fc161f30e i have both b43-fwcutter and b43-firmware installed, however, if i understand correctly from the arch wiki link, b43 is not for the chip set i have. |
|
|
|
|
12
|
General / As seen on the internet / Re: helpful wireless how-to for Broadcom chipsets
|
on: December 14, 2011, 07:50:04 AM
|
I have used the first method for now. let's hope that this remains future proof  and Solution 1: (as suggested)
Comes from atolboo@wind-pardus ~ $ pisi sf local.start
Zoekt naar local.start
Pakket baselayout bevat bestand /etc/conf.d/local.start
This means that /etc/conf.d/local.start will almost certainly be overwritten with an update of baselayout. Unless this is prevented in one of the the comar-script of baselayout. If /etc/rc.conf is doing the required job, I would go for that solution because Solution 4:
atolboo@wind-pardus ~ $ ls -l /etc/rc.conf
ls: kan geen toegang krijgen tot /etc/rc.conf: Bestand of map bestaat niet <<< does not exist And thus not from any package. And if this ^^^^ is OK, a feedback will be highly appreciated  I got your point, but since there is no rc.conf, maybe pardus does not need it? I picked it up from arch wiki. maybe i should try creating this file? let me see I created rc.conf in /etc and put modprobe wl in it, but it had no effect |
|
|
|
|
13
|
General / Wish list / Re: Teamviewer
|
on: December 13, 2011, 08:33:48 AM
|
well, i tried to read the translated text . so, there is no 64 bit teamviewer at the moment. what are the alternatives: can we download .tar.gz file and run? or we should go for web based teamviewer. |
|
|
|
|
14
|
General / As seen on the internet / Re: helpful wireless how-to for Broadcom chipsets
|
on: December 13, 2011, 08:22:35 AM
|
I would think that altering /etc/conf.d/local.start is the best way to go as this file is made just for personalizing and I would think updates for modprobe rules would not effect it.
One can always change it back to default to check in future if this is resolved, especially after modprobe, udev, module and kernel updates.
The file. /etc/rc.conf, is a Debian distro file, which I think I have also seen it in Fedora, but not sure. I think it's equivelant in Pardus are the files under /etc/conf.d .
Lisa Marie
Thanks Lisa, I have used the first method for now. You are right abt the 4th solution. i was searching on the net and found this on arch wiki. arch wiki is a very well documented site. they suggested to use 'wl' as a last resort and try other drivers first. https://wiki.archlinux.org/index.php/Broadcom_wirelessmy chip was [14e4:4727] BCM4313. i tried to install module 'bcma' but there is no such module so finally i went with 'wl'. let's hope that this remains future proof |
|
|
|
|
15
|
General / As seen on the internet / Re: helpful wireless how-to for Broadcom chipsets
|
on: December 12, 2011, 12:48:46 PM
|
|
Yesterday, i installed Pardus on a friend's laptop. However, since it had a broadcom wifi chip, it did not work automatically. I tried modprobe wl and it worked.
Now, after reading this thread and searching on the net, i was thinking of making this permanent and also future proof (so that it survives version upgardes of pardus).
Solution 1: (as suggested)
putting modprobe wl in /etc/conf.d/local.start
Solution 2:
putting wl in /etc/modules.autoload.d/kernel-2.6 (this does not seem to be future proof to me as kernels will be upgraded in future)
Solution 3:
In /etc/modprobe.d, modify broadcom-wl.conf file
There is a line which tells to install wl and remove b43 and then ignores install. probably removing the second part should be enough?
Solution 4:
add wl in /etc/rc.conf file in the modules array
Which of the above is more future-proof?
QUESTION 2:
In case more than one drivers support a chipset (e.g., b43 and wl), which one to use.
|
|
|
|
|
|
