SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had similar issues. the only way I can get ndis to work on my DV9007 was to compile the newest version and run screaming away from the one provided by yast. I don't know which way you did it, but it made a world of difference for me.
hey man thanks for the advice, im still having a problem though.
What i did was
- Downloaded ndiswrapper-1.37.tar.gz
- I uncompressed the tarball
- Used the make command
- Used Make Install
- I go into the directory in which i have the drivers
- In terminal after su i did ndiswrapper -i
- Now from before it said the driver is already installed
- I go to remove it it said no such file or directory
- So anyways i just look at ndiswrapper -l and it says, driver installed, Device name (XXXX:XXXX) hardware present.
- I do iwconfig and there was no wlan0 listed. Baisically thats where i stopped
I did remove the old ndiswrapper nd i checked the version it is the new 1 so i dont know whats going on please help me out
I agree with what you've done so far. Make sure you do >make distclean for your first build command and be sure you have completely removed the installed driver previously. Mine did the same thing...showed hardware present, but no results with iwconfig. I usually go into Yast, search for ndiswrapper and if it's listed there select it for removal. Then proceed to the new build. Here was my steps (just did it today)
yast remove ndiswrapper if shows there
then extract source to home directory
go to directory with drivers (making sure I have .inf and .sys files present)
>ndiswrapper -i bcmwl5.in
>ndiswrapper -l to see installed and hardware present
Then go to yast to setup new netork device being sure to list "ndiswrapper" as the "module"
yast2->network devices->Network Card->Next->Add->select wireless under device type->place ndiswrapper in 'module'->next fill out remaining information about your connection->finish.
I then restart to be sure ndiswrapper module is loaded properly.
its critical that before you start this, you test and be sure ndiswrapper has been completely removed from you system. I just type ndiswrapper from terminal to see if I get any results or not. If not, you're good to proceed on.
I'm not going to lie, I don't even have my own wifi router... I just use whatever I can get from campus. Consequently, I just leave most of the fields blank other than "module" or things that are already filled in. I also give it a config name (I used wlan0).
Here's the thing... the wireless connection works just fine in XP, though it's often pretty weak. Still, I can get steady 150k/sec downloads without too much trouble. Since I just use Windows' built-in network finder thingy that automatically finds any nearby networks, I'm wondering if it's even going to be possible for me to use wifi under linux without knowing everything about where I'm getting the signal from.
I've followed all steps given in these pages... first I did the OP's steps, then I used the drivers for windows 2000 like the other guy said.
Sometimes, when I do iwconfig or ifconfig, it'll show "promising-looking stuff" where my wifi device should be. I say "sometimes" because I often end up deleting said devices since they never work anyway... KNetworkManager, when it's not ignoring my goddamn wifi devices entirely and insisting that I'm connected to eth1 (a lan line... which I'm not connected to. The only line to my laptop is my power supply...), will always get stuck at 28%, "Configuring devices" or some such crap when I type in the name of the network I'm trying to connect to.
I dunno, I used the drivers from my vendor's website originally. I'm thinking of giving the ones linked in this thread a go before I just give up and uninstall the millionth distro that doesn't like playing nice with my wireless (no games + no internet = no point in using the damn thing).
hey i just reinstalled my linux nd put kde on. so i put ndiswrapper from scratch. I downloaded 64bit drivers from http://www.linuxant.com/driverloader/drivers.php since ndiswrapper wiki stated to do so. I got the ones for my broadcomm. I installed the driver everything good. i go to list the driver and all it said was bcmwl5.inf driver installed. nd thats it there no hardware present or n e thing, what should i do??
N.B. I like to live dangerously ... but I do have a backup using dd to an exactly same-sized partition on a 120GB Western Digital Passport USB2 hdd, before I start to play ...
However, and this was all done sitting on a boat in a harbor/harbour somewhere in the south of England trying to attach myself to the local hot-spot.
My Ferrari laptop has a Broadcom 4306 802.11b/g Wireless LAN Controller chipset although it is variously reported as an 'Acer Travelmate 290E WLAN Mini-PCI Card' and/or a 'Wistron NeWeb Acer Travelmate 290E WLAN Mini-PCI Card' and I installed a pristine new version of 64-bit openSUSE 10.2 from a DVD+R that I had downloaded and burnt using K3b.
Well I knew that the card worked on my home wireless access point using the netbc564.inf (part of a file called "64-bit_Broadcom_54g_Drivers.zip" that I found by Google) on a suse 10.1 x86_64 installation on this same machine (different partition), so I imported that by mounting the drive and copying it across. Then I downloaded Ndiswrapper-1.37.tar.gz, did a quick search for ndiswrapper and found ndiswrapper.ko in /lib/modules/220.127.116.11-34-default/updates/ndiswrapper.ko
However this didn't work for me ... it appears that suse 10.2 comes with a bcm43xx module that was already installed during my setup BUT it was setup in Yast - Network Devices - Network Card as eth1 and was not attached to my 'static-0' device, which appears to be the device name of my wlan0 card. ifconfig -a showed no wlan0, and ifup wlan0 returned a message to indicate that there was no wireless interface. So using lsmod, I find that the bcm43xx module is loaded automatically in each boot or restart. So i learn about /etc/modprobe.d/blacklist from the man modprobe.d file. I edit the blacklist and add at the end 'blacklist bcm43xx' save and exit. Just for luck I also ran # modprobe -r bcm43xx and lo and behold it has never blackened my doorstep again.
So ... using a Super User Mode File Manager I renamed this update_ndiswrapper.ko (and it appears to be a 1.25 version according to Yast - Software Management). When I untarred my downloaded version 1.37 - make uninstall - make - make install it appeared in /lib/modules/18.104.22.168-34-default/misc/.
I cd'd to the directory/folder with my netbc564.inf file and did a ndiswrapper -i netbc564.inf, and a ndiswrapper -l showed the driver present. Then a modprobe ndiswrapper installed? the module and he presto ifconfig showed a wlan0 - admittedly I had been playing with my Network Devices - Network Card disabling the eth0 wired interface and adding such things as the MAC address of the Hot-spot's AP (access point) although ultimately the wlan0 on static-0 device is dchp for everything now. If you are wondering how I knew such things as the hotspot's MAC address I also have a tablet PC running XP SP1. Which would of course find the hotspot but not at the same time as my linux box.
from the link above did u use the first 1 or the second. I used the first 1 all it sayd was that the driver was installed, im a lil shakey on how u switched it to using that. can someone explain to me alil. Im still a newb user on suse 10.2
SickNick: run 'lsmod' as root or 'sudo root' if that works for you, and let us know whether a bcm.... or netbc... or bcmwl5 or bcm45xx and/or ndiswrapper appears in the list -- just so we know what modules you have loaded.
Also please note that I ran 'make uninstall' as instructed by the INSTALL in my untarred ndiswrapper directory. Did you do so?
Also please tell us ... from running a 'lspci' command, the exact name of the wlan card/chipset you have on your machine -- since I don't seem to be able to find my chipset mentioned on the linuxant site that you say you downloaded your driver from. Since I don't have a DV2000 to hand perhaps you can confirm. I just looked at http://www.linux-on-laptops.com/hp.html and scrolled down to (and clicked on a Gentoo install which lists all its chipsets for a DV2000 as coming from intel rather than Broadcom. Your response will be interesting.
sorry for the delayed response, i just ran lsmod none of what u asked for is listed in there. I did not make uninstall. The issue ur looking at with broadcom, is that broadcom comes with the dv2000 with the amd turions, the intel chipsets which people have no problem configuring are the dv2000s with the core 2 duos. Now like i said i get driver installed but thats it, suggestions??
Point taken about the intel versus amd wireless chipsets ... it appears that, if I am reading your post correctly, that your lsmod listing did not have an ndiswrapper module loaded. If so then I suggest that you try installing again. If I am wrong (i.e. misreading your most recent post) then I would suggest that you run: ndiswrapper -i bcmwl5.inf
Since you may well have done the above, the next step is to see if the interface is up (i.e. exists) this is reported by: # ifconfig -a
The # signifies root or sudo and the -a shows all existing interfaces with the LAN or web.
If you don't have a wlan0 then you will have to venture into Yast -> Network Devices -> Network Card and set up a new interface ('add', there should already be an eth0 for your Cat5 cable/wire NIC. I would set up everything as DHCP, incidentally I use the traditional method rather than the new NetworkManager. Click away at the bottom right hand corner until you have restarted the network.
Now you should see the wlan0 interface when you run: # ifconfig and/or # ifconfig -a .... if only the latter run:# ifup wlan0 then try running: # iwlist wlan0 scan
this should show if there are any available wifi points in your vicinity whether encrypted or not.
Please note that I may have skipped some steps in the Network Card setup ... for instance my hardware name is called static-0 on the Configuration Name wlan0 (found on the Network Address Setup -> Advanced -> Hardware Details tab.
I did what you told me and i ran into a few errors while doing it, i coppied my whole console input and output so you can see it. Sorry for the length of it but at least youll have plently of info to refer to.
Is there any way i could attatch a txt file cuz its too long to post it wont let me
I'm just one more person having troubles with a BCM wireless card in Suse. Just switched over after an unsuccessful installation (well, no wireless at least!) install of Mandriva, and Debian before that; none of which i was able to get the wireless working on. On the other hand, my first ever install of linux (Fedora core 4) i was able to successfully get ndiswrapper & wireless working... But i'll also be the first to admit that with the other distro's i did not dedicate nearly enough time to the task. That said, i'm very interested in getting it working with Suse 10.2, and will be dedicated as much time as i can to the task.
So far, i've installed the included version of ndiswrapper (1.9). From there i installed my bcmwl5.inf files from my windoze partition (which i'm on right now), and ran ndiswrapper -l to verify, then -m to write the modprobe configuration. After rebooting, with fingers crossed i opened up network configuration tool in Gnome. There, both my wired and wireless connections were listed, but the problem is that my wireless card is listed as wired! It has been that way since installing Suse actually, and i've tried configuring it, changing it, deleting it, all to no avail.
After browsing around on this forum and hitting google results for a bit, i haven't had any more luck. I went back to try rewriting the modprobe configuration, and got this result:
linux:~ # ndiswrapper -m
module configuration contains directive install pci:v000014E4d00004301sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 459.
module configuration contains directive install pci:v000014E4d00004301sv000012F3sd0000103Cbc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 460.
module configuration contains directive install pci:v000014E4d00004320sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 461.
module configuration contains directive install pci:v000014E4d00004320sv000000E7sd00000E11bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 462.
module configuration contains directive install pci:v000014E4d00004320sv000012F4sd0000103Cbc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 463.
adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper ...
couldn't add module alias: at /usr/sbin/ndiswrapper line 705.
Now most of it is OK, i understand i'm telling it to write something that already exists.. but the last line (couldn't add module alias: at /usr/sbin/ndiswrapper line 705) is something that came up when i first wrote the module in. Does anyone know what this means and / or what i should do?
Also, reading some of the posts in this (and other) threads, it sounds like some of the newer versions of ndiswrapper are maybe more buggy than the older ones; would it make sense to try and older version? If thats the case, what are the proper guidelines for uninstalling & removing all traces of the current version?
Edit: oh.. btw, this is a 32-bit system; sorry if i shouldn't be posting about it in this thread? let me know if you want me to move it and i will
Oh, maybe i should also mention that i've tried the blacklisting technique listed both here and here without any luck.. as with the other techniques i've tried
Last edited by ultimatenoob; 03-21-2007 at 01:18 AM.
Well, like I said in my first post (at least I think I did) I'm sort of a linux noob, so if it's not about the specific topic I posted about, I'm just blowing hot air at you. Perhaps someone else watching can help, or maybe you could start your own topic for help in the appropriate forum?
dont you need to blacklist the bcm43xx? and how do i do it. everyone says its simple but my wireless still wont work. i change the module name to ndiswrapper, but every time i restart its back to the bcm43xx.