On Monday 08 September 2008 23:21:46 Bob Williams wrote:
On Monday 08 September 2008 19:18:52 Ciro Iriarte wrote:
Did you install the windows driver? (output from ndiswrapper -l), you didn't state if you're running i386 or x86_64 version of Opensuse, I guess you should use 64bits driver on 64bit Opensuse....
It's on the lspci output, so, it's "seen", the device will be created dynamically once the kernel module is loaded (ls -l /proc/net/ndiswrapper)
CI.-
Many thanks for your help, Ciro, but I'm pretty sure I've got a hardware problem here. I've reinstalled Windows Vista on a 30Gb partition, and even that doesn't offer wifi! There may be a problem with the wifi on/off switch, which doesn't seem to stick in the on position.
Do Dell have a good reputation as far as build quality goes, or do they just chuck 'em out as fast as they can build them?
Currently reinstalling opensuse 11.0 64bit as second OS. Posting from my trusty old desktop workhorse ;)
Bob
After doing some investigating, I discovered that the wifi card in my Dell Inspiron 1525 is a Dell Wireless 1395 WLAN Minicard, which can use the Broadcom bcm4311 drivers. I downloaded the 64bit version of the driver from http://www.broadcom.com/support/802.11/linux_sta.php together with the readme.txt at the same place. I followed the instructions in the readme.txt, and the wifi indicator duly lit up when I reached the end. What's more, there was an entry under Yast
Network Devices > Network Settings for a BCM4310 USB Controller, which wasn't there before. However, the module name, under the hardware tab, is blank, and I'm not sure what to put there. I've tried wl and wl.ko but still no connection with my router.
I've reproduced to readme.txt below, in case it gives someone an idea of what I should try next... DISCLAIMER ---------- This is an OFFICAL-RELEASE of Broadcom's hybrid Linux driver for use with Broadcom BCM4312 based hardware (device ID 4315). IMPORTANT NOTE AND DISCUSSION OF HYBRID DRIVER ---------------------------------------------- There are different tar's for 32 bit and 64 bit x86 CPU architectures. Make sure you use the appropriate tar, as the hybrid binary must be of the appropriate architectural type. Otherwise the hybrid binary is agnostic to the specific version of Linux kernel because it is designed to perform all interactions with the OS through OS specific files (wl_linux.c, wl_iw.c) and an OS abstraction layer file (osl_linux.c). All of these interactions are done through functions which make the hybrid binary OS version independent. All Linux OS specific code is provided in source form allowing re-targeting to different kernel versions and fixing OS related issues. BUILD AND INSTALLATION INSTRUCTIONS ----------------------------------- hybrid-portsrc.tar.gz hybrid-portsrc-x86_64.tar.gz On the target machine, setup the source/hybrid/build directory 1. Create a new directory: mkdir hybrid_wl 2. Go to that directory: cd hybrid_wl 3. Untar the appropriate 32/64 bit file to that directory 32 bit: tar -xzf <path>/hybrid-portsrc.tar.gz 64 bit: tar -xzf <path>/hybrid-portsrc-x86_64.tar.gz After untar'ing you should have a src and lib sub directory plus a Linux 2.6 "kbuild" external makefile (Makefile). The lib sub directory has the pre-built binary, wlc_hybrid.o_shipped. You use the standard Linux 2.6 kernel build system as follows to make a Linux loadable kernel module (LKM): On the target machine, and cd'ed to the directory that contains the Makefile (fragment) 4. Cleanup (optional): make -C /lib/modules/<2.6.xx.xx>/build M=`pwd` clean 5. Build the LKM, i.e. wl.ko: make -C /lib/modules/<2.6.xx.xx>/build M=`pwd` You should now have a LKM, wl.ko inside this directory. On this or a machine with the same kernel version, install the driver. 1. Validate you don't have loaded (or built into the kernel) the Linux community provided driver for Broadcom hardware. This exists in two forms: either "bcm43xx" or a split form of "b43" plus "b43legacy". If these modules were loaded you would either a) rmmod bcm43xx or b) rmmod b43; rmmod b43legacy 2. Make available 802.11 TKIP crypto module: modprobe ieee80211_crypt_tkip 3. Insert the Broadcom wl module: insmod <path>/wl.ko Some kernel come with pre-installed Broadcom driver that support Broadcom 4312 family of PCIE cards. If the kernel support one of those pre-installed driver, you must remove it in order to install the new driver. Some of existing driver provided by the Linux community that supports Broadcom hardware are b43/b43legacy/bcm43xx. There is also a ssb driver that is loaded along with b43. This ssb driver also must to be remove. If the kernel supports blacklist, you can add those drivers to the blacklist file so that it will not be loaded on next reboot. -- Bob Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.11-0.1-default, KDE 4.1.1 Intel Celeron 2.53GB, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org