LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Suse/Novell (http://www.linuxquestions.org/questions/suse-novell-60/)
-   -   Add/blacklist kernel modules in YaST2? (http://www.linuxquestions.org/questions/suse-novell-60/add-blacklist-kernel-modules-in-yast2-561244/)

General 06-12-2007 01:32 PM

Add/blacklist kernel modules in YaST2?
 
YaST2 seems to like one to use its interface rather than editing config files. Is there some way I can add kernel module ndiswrapper and then blacklist another kernel module with this program called YaST2?

shadowdancer 06-12-2007 01:44 PM

Don't know how to that using YaST. But you can blacklist modules easily by editing file /etc/modprobe/blacklist

just add:
blacklist bcm43xx

for blacklisting module bcm43xx, etc.

General 06-12-2007 02:16 PM

Quote:

Originally Posted by shadowdancer
Don't know how to that using YaST. But you can blacklist modules easily by editing file /etc/modprobe/blacklist

just add:
blacklist bcm43xx

for blacklisting module bcm43xx, etc.

Does the command `modprobe ndiswrapper` make it so that module will always be loaded...or will it not be loaded after I shutdown, then reboot the computer, until I type `modprobe ndiswrapper` again?

emg 06-13-2007 10:27 AM

as root in terminal type
Code:

ndiswrapper -m
that will load ndiswrapper on boot ... just curious as to what card your using ndiswrapper for?? The native bcm43xx driver works fine now ... even gets "G" performance too ... I have a broadcom 4306 chip in my dell laptop and tried/used both drivers, bcm43xx and ndiswrapper, I stayed with the bcm43xx driver because I got tired of re-compiling/configuring ndiswrapper everytime I upgraded the kernel ...

General 06-13-2007 11:35 AM

Quote:

Originally Posted by emg
as root in terminal type
Code:

ndiswrapper -m
that will load ndiswrapper on boot ... just curious as to what card your using ndiswrapper for?? The native bcm43xx driver works fine now ... even gets "G" performance too ... I have a broadcom 4306 chip in my dell laptop and tried/used both drivers, bcm43xx and ndiswrapper, I stayed with the bcm43xx driver because I got tired of re-compiling/configuring ndiswrapper everytime I upgraded the kernel ...

I have the bcm4318 "airforce one" on a pcmcia. I am using ndiswrapper because some instructions I found told me how to install the card using ndiswrapper...and the instructions worked: I got connected to the internet. I didn't know that the bcm43xx module that I had to blacklist was actually a driver that might work...I just knew bcm43xx was something that the instructions told me to blacklist. I have never used anything wifi before so I dont' know about performance or what "G" versus "B" means, or what encryption stuff I should have activated.

shadowdancer 06-13-2007 03:04 PM

Probably General's wireless device is same with me.

Mine is Broadcom AirForce One xxx...(i forgot)

I used ndiswrapper with bcmwl5.inf(windows's driver) and works fine. Though I cannot use kismet with this device.

For me, the importance of blacklisting bcm43xx is because ndiswrapper will use that as alternate driver if I didn't do so, and the device is not working.

emg 06-13-2007 03:19 PM

Quote:

Originally Posted by General
I have the bcm4318 "airforce one" on a pcmcia. I am using ndiswrapper because some instructions I found told me how to install the card using ndiswrapper...and the instructions worked: I got connected to the internet. I didn't know that the bcm43xx module that I had to blacklist was actually a driver that might work...I just knew bcm43xx was something that the instructions told me to blacklist. I have never used anything wifi before so I dont' know about performance or what "G" versus "B" means, or what encryption stuff I should have activated.

G=54Mb and B=11Mb throughput as far as encryption goes ... thats a personal choice. I live out in the sticks so I only use WEP encryption. If you live in the city or have neighbors close bye then I would suggest using WPA encryption... As for the drivers, the bcm43xx is slightly harder to setup (install a package with yasr and then a couple of commands) but once its done you can upgrade the kernel without having to re-configure the wireless ... ndiswrapper is good but you'll need to uninstall/re-install your driver if you upgrade your kernel... If you want to try the native driver (bcm43xx) let me know and I'll walk ya through it ....

shadowdancer 06-14-2007 05:46 AM

emg,
Please walk me trough it. I will be really happy using native driver. And I hope kismet will also work.

Thank you very much...

emg 06-14-2007 09:55 AM

Quote:

Originally Posted by shadowdancer
emg,
Please walk me trough it. I will be really happy using native driver. And I hope kismet will also work.

Thank you very much...


Lets start from the begining ...open a terminal and change to root and type
Code:

rmmod ndisrapper
if you've blacklisted the bcm43xx driver then you have to UN-blacklist it. If you installed ndiswrapper via yast then use yast and uninstall it, if you compiled ndiswrapper and installed it then you can uninstall it by going to the dir you installed it from and as root type
Code:

make uninstall
now we go back to yast and install the package bcm43xxfw_cutter ... I'm not positive on the package name (I'm at work right now on a winblows box) but if you use the search box in yast it'll find the package ... once thats installed you can close yast and open a terminal and switch to root. Then type
Code:

install_bcm43xx_firmware
(again not sure of the exact command but if you type
Code:

install
then hit the tab key 2 times you should see a list ... one will be the firware install command) that should download and install the firware for you. Now in that same root terminal type
Code:

modprobe bcm43xx
all should go smooth .... now open yast > network devices > network card and edit your wireless card. Remember where you told yast to use the ndiswrapper module? (under hardware details) you now have to tell yast to use the bcm43xx module. Set any other options. Now close yast and go back to the root terminal and type
Code:

rcnetwork restart
this should stop and restart your network and you should see your wireless card get activated. You should now be running on the bcm driver, check connectivity to the internet/home network and you should be good to go .... let me know if this works out for you, if not you can always go back to the ndiswrapper method.

shadowdancer 06-15-2007 06:16 AM

Thank you very much for the effort, emg.

But, I got error, here:
Code:

linux-g9i9:/home/shadow # install_bcm43xx_firmware
Downloading firmware

curl: (22) The requested URL returned error: 404
Downloading firmware (alternative file)

curl: (22) The requested URL returned error: 404
/home/shadow
linux-g9i9:/home/shadow #

and when I check my device using lspci, I got info:
Code:

00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
and, when I check here:
http://bcm43xx.berlios.de/?go=devices

it said:
Quote:

4318 PCI/Cardbus Unstable (transmission power issues, work in progress)
is there any solution?

again, thank you very much for the effort.

emg 06-15-2007 07:57 AM

Quote:

Originally Posted by shadowdancer
Thank you very much for the effort, emg.

But, I got error, here:
Code:

linux-g9i9:/home/shadow # install_bcm43xx_firmware
Downloading firmware

curl: (22) The requested URL returned error: 404
Downloading firmware (alternative file)

curl: (22) The requested URL returned error: 404
/home/shadow
linux-g9i9:/home/shadow #

and when I check my device using lspci, I got info:
Code:

00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
and, when I check here:
http://bcm43xx.berlios.de/?go=devices

it said:


is there any solution?

again, thank you very much for the effort.


I guess you'll have to stick with ndiswrapper then for a little while longer .... at least it says that its a work in progress ... :)


All times are GMT -5. The time now is 09:45 PM.