On 9/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > All, > > I find the bulk of information regarding wireless setup and > configuration a source of confusion in and of itself. There needs to be > a consolidated and streamed line manner of explaining how to do so. > Given the mired of distributions the one one sure way to alleviate > confusion is for configuration by the command line. I'd very much like > to personally receive instructions on how to get my Motorola WN825G > pcmcia wireless nic (command line and/or YaST). The system it is a > AMD64 R3000, running SuSe 10.0 RC1 x86-64. > > I have copied the drivers bcmwl5.inf and bcmwl5a.inf to my home > directory (/home/oprogue) > > I have ran: > ndiswrapper -i /home/oprogue/bcmwl5.inf > ndiswrapper -i /home/oprogue/bcmwl5a.inf > > linux:~ # ndiswrapper -l > Installed ndis drivers: > bcmwl5 driver present, hardware present > bcmwl5a driver present, hardware present > linux:~ # > > linux:~ # ndiswrapper -m > modprobe config already contains alias directive > > linux:~ # modprobe ndiswrapper > FATAL: Module ndiswrapper not found. > linux:~ # > > linux:~ # lspci -v > . > . > . > 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > Subsystem: Realtek Semiconductor Co., Ltd. RT8139 > Flags: bus master, medium devsel, latency 64, IRQ 185 > I/O ports at 7000 [size=256] > Memory at 00000000e0106800 (32-bit, non-prefetchable) [size=256] > Capabilities: [50] Power Management version 2 > > 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller > (rev 01) > Subsystem: Hewlett-Packard Company: Unknown device 006d > Flags: bus master, medium devsel, latency 168, IRQ 177 > Memory at 00000000e0104000 (32-bit, non-prefetchable) [size=4K] > Bus: primary=02, secondary=03, subordinate=06, sec-latency=176 > Memory window 0: 30000000-31fff000 (prefetchable) > Memory window 1: e0400000-e07ff000 > I/O window 0: 00003000-000030ff > I/O window 1: 00003400-000034ff > 16-bit legacy interface ports at 0001 > > 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller > (rev 01) > Subsystem: Hewlett-Packard Company: Unknown device 006d > Flags: bus master, medium devsel, latency 168, IRQ 185 > Memory at 00000000e0105000 (32-bit, non-prefetchable) [size=4K] > Bus: primary=02, secondary=07, subordinate=0a, sec-latency=176 > Memory window 0: 32000000-33fff000 (prefetchable) > Memory window 1: e0c00000-e0fff000 > I/O window 0: 00003800-000038ff > I/O window 1: 00003c00-00003cff > 16-bit legacy interface ports at 0001 > > 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading > Function (rev 01) > Subsystem: Hewlett-Packard Company: Unknown device 006d > Flags: bus master, medium devsel, latency 64 > I/O ports at 7400 [size=64] > Capabilities: [44] Power Management version 2 > > 03:00.0 Network controller: Broadcom Corporation BCM4306 802.11b/g > Wireless LAN Controller (rev 03) > Subsystem: Motorola WN825G > Flags: fast devsel, IRQ 177 > Memory at 00000000e0400000 (32-bit, non-prefetchable) [disabled] [size=8K] > > linux:~ # > > > so the system sees the nic ... BUT ... I do not see the nic listed in > YaST and can not configure it or turn it on. If someone can provide me > with some instructions it would be most appreciated. Do I need to do > something with the bcmwl5.sys file? > > > Thanks in advance! > > > > > > > Karol Krizka wrote: > > >On 8/23/05, Arfon Griffiths <[EMAIL PROTECTED]> wrote: > > > > > >>Use the Linuxant WLAN Driverloader. > >> > >>Works like a charm and is easy to install (and comes in a 64 flavor). > >> > >> > >>www.linuxant.com > >> > >> > >> > >Or just try ndiswrapper, it's free and easy to setup :P > > > >http://ndiswrapper.sf.net > > > > > >>_______________________________________________ > >>LinuxR3000 mailing list > >>[email protected] > >>http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 > >>Wiki at http://prinsig.se/weekee/ > >> > >> > >> > > > > > > > > > > _______________________________________________ > LinuxR3000 mailing list > [email protected] > http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 > Wiki at http://prinsig.se/weekee/ > Regarding and Easy to Follow Setup: You'll FInd no Better Example that on the wiki in the signature of this list.
It appears you may not have ndiswrapper installed, only the wireless tools, make sure you have an ndiswrapper.ko. if you do, modprobe it's full path. Also make usre tha tif you're using the PCMCIA slot that you've configured it correctly, though it seems that you haven't gotten to that problem yet. You may already be far past this information, but here's what I can tell you in terms of installing and configuring wireless on Suse: For spesific instructions for suse, perhaps reading sus's instructions on how to do so will be enlightening for you, I'm sure you can find same with google. Basically Setting up ndiswrapper is simple, and linuxant documents and supports their product. In the case of ndiswrapper, you should either use Yast to download the binary package, or get the source from http://ndiswrapper.souceforge.net. If a binary rpm is available from them, that will skip you along in the process. however, If they only have the source available, YOu will need to download from Suse: Your Kernel headers, The Compiler chain, including but perhaps not limited to: make, gcc, and glibc. There may be others, this would be a good time to make use of any support you could have possibly purchased with suse. If you are using a freely distributed copy, I suggest you search the archives of this list and contact someone using Suse directly, or, at the very least, by anem and ask them how they did it. Once you have ndiswrapper installed, you can get the rpm for the wireless-utils which will allow you to control your card. follow the instructions in the manpage for ndiswrapper on how to install your drivers in ndiswrapper, and then in sert the module using modprobe. you can then use iwconfig to select a network, iwlist to scan for new ones, etc. If. anywhere in this process, a step fails, go back to the previous step until you've made sure that it has been caried out in entireety certain pitfalls tend to occur: - Wrong Compiler version: this will silenetly fail, but you will need the same version of gcc as compiler your kernel. I don't know why, but you will. IF al else fails, seek instruction on compiling a new kernel and initrd - Wrong Driver:HAving the wrong bcmwla.inf will cause no end of problems, please use the driver provided by your hardware's manufacturer, or from the lists at either ndiswrapper.sourceforge.net, or from linuxant's site. I believe both list are freely accessible. Make Sure to Get the correct Version - Missing compiler chain members: these may indicate what you are missing. sometimes the compile will simply fail please feel free to use irc.freenode.net to find a support channel for suse, or post your error to this list, preferealy both. - On AMD64 using 64-bit suse, make sure you have the correct version of ndiswrapper. there shoulds be more information on the wiki. Good Luck, and I apologize if I have mistakenly misinformed. Ben West -- I use Gnome. It runs on linux. Gnome is the new Desktop competitor to M$ _______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
