[opensuse] Broadcom wireless and static address under ndiswrapper.
I just installed opensuse 10.1 on a new dell inspiron 9400 and the only way to get the wireless working was with the ndiswrapper. It is a broadcom bc44XX built in wireless chipset. The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers. Any thoughts, TIA John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 16 November 2006 21:20, John Pierce wrote:
The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers.
So set it in your router. Most routers have IP reservation capability and thats much easier than booting machines with statics anyway. Bummer about ndiswrapper. I thought there was a project for the bc44XX. -- _____________________________________ John Andersen
Bummer about ndiswrapper. I thought there was a project for the bc44XX.
I agree I will tinker with it more, I will eventually get it to work with the native driver. I just wanted to see this dual core run (actually I wanted to get it going for my wife). I have the rt2500 working on the pcmcia wireless belkin card in the ibm thinkpad. I will get this one going. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 2:27 am, John Andersen wrote:
On Thursday 16 November 2006 21:20, John Pierce wrote:
The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers.
So set it in your router. Most routers have IP reservation capability and thats much easier than booting machines with statics anyway.
Bummer about ndiswrapper. I thought there was a project for the bc44XX.
The bcm43xx driver was included in the mainline kernel in 2.6.18, which will be shipped in 10.2. If you're brave, you can run the kernel from Factory on 10.1, but you will need to pull some other packages as well: perl-Bootloader, mkinitrd, xen (if you use it), and possibly some others. RPM will tell you, if you decide to try. -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2006-11-17 at 15:18 -0400, James Oakley wrote:
On Friday 17 November 2006 2:27 am, John Andersen wrote:
On Thursday 16 November 2006 21:20, John Pierce wrote:
The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers.
So set it in your router. Most routers have IP reservation capability and thats much easier than booting machines with statics anyway.
Bummer about ndiswrapper. I thought there was a project for the bc44XX.
The bcm43xx driver was included in the mainline kernel in 2.6.18, which will be shipped in 10.2.
But it does not include the firmware which of course makes it useless. The firmware can be downloaded from Ubuntu ( but it still has issues ). Will this issue ( the firmware ) be cleared up when 10.2 goes GM? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 17 November 2006 12:10, Kenneth Schneider wrote:
On Fri, 2006-11-17 at 15:18 -0400, James Oakley wrote:
On Friday 17 November 2006 2:27 am, John Andersen wrote:
On Thursday 16 November 2006 21:20, John Pierce wrote:
The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers.
So set it in your router. Most routers have IP reservation capability and thats much easier than booting machines with statics anyway.
Bummer about ndiswrapper. I thought there was a project for the bc44XX.
The bcm43xx driver was included in the mainline kernel in 2.6.18, which will be shipped in 10.2.
But it does not include the firmware which of course makes it useless. The firmware can be downloaded from Ubuntu ( but it still has issues ). Will this issue ( the firmware ) be cleared up when 10.2 goes GM?
Can one yank the firmware off the windows driver disks in the meantime? -- _____________________________________ John Andersen
On Friday 17 November 2006 5:13 pm, John Andersen wrote:
The bcm43xx driver was included in the mainline kernel in 2.6.18, which will be shipped in 10.2.
But it does not include the firmware which of course makes it useless. The firmware can be downloaded from Ubuntu ( but it still has issues ). Will this issue ( the firmware ) be cleared up when 10.2 goes GM?
Can one yank the firmware off the windows driver disks in the meantime?
Yes, using bcm43xx-fwcutter, which is also included in 10.2. I'm surprised that Ubuntu distributes it, since it's not really legal unless they have explicit permission. That's why SUSE, and the driver maintainers are not distributing it. -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 18 November 2006 18:08, James Oakley wrote:
On Friday 17 November 2006 5:13 pm, John Andersen wrote:
The bcm43xx driver was included in the mainline kernel in 2.6.18, which will be shipped in 10.2.
But it does not include the firmware which of course makes it useless. The firmware can be downloaded from Ubuntu ( but it still has issues ). Will this issue ( the firmware ) be cleared up when 10.2 goes GM?
Can one yank the firmware off the windows driver disks in the meantime?
Yes, using bcm43xx-fwcutter, which is also included in 10.2.
I'm surprised that Ubuntu distributes it, since it's not really legal unless they have explicit permission.
I'm not so sure. a) You purchased the device. b) They provide free drivers on their web site. All bcm43xx-fwcutter does is put a and b together. Quote:----- This package contains the 'bcm43xx-fwcutter' tool which is used to extract firmware for the Broadcom network devices, from the official Windows, MacOS or Linux drivers. ------ It rips the firmware out of their published drivers and allows it to be used externally. I got the firmware for my Broadcom wifi when I purchased the machine. Just because I discarded the wrapper doesn't make me guilty. How is this different than selling scissors to cut recipes out of books or magazines to paste in your recipe book?
That's why SUSE, and the driver maintainers are not distributing it.
-- James Oakley jfunk@funktronics.ca
-- _____________________________________ John Andersen
As the original Op, back on topic. I pulled the latest firmware out of the driver file and placed it in /lib/firmware/. Removed the blacklisting from /etc/modprobe.d/blacklist. Removed the alias to ndiswrapper and set the alias to wlan0 bcm43xx modprobed bcm43xx and all dmesg would display was the single line bcm43xx I could never get it to initialize the device. I went back to ndiswrapper for now, I am going to download the 10.2 beta of opensuse and see what happens when the driver is included mainstream. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 November 2006 7:08 am, John Andersen wrote:
I'm surprised that Ubuntu distributes it, since it's not really legal unless they have explicit permission.
I'm not so sure.
a) You purchased the device. b) They provide free drivers on their web site.
All bcm43xx-fwcutter does is put a and b together.
I'm talking about the firmware, not bcm43xx-fwcutter. People have mentioned that Ubuntu distributes the *firmware*, which is not allowed without explicit permission. -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 November 2006 08:58, James Oakley wrote:
On Sunday 19 November 2006 7:08 am, John Andersen wrote:
I'm surprised that Ubuntu distributes it, since it's not really legal unless they have explicit permission.
I'm not so sure.
a) You purchased the device. b) They provide free drivers on their web site.
All bcm43xx-fwcutter does is put a and b together.
I'm talking about the firmware, not bcm43xx-fwcutter. People have mentioned that Ubuntu distributes the *firmware*, which is not allowed without explicit permission.
Yes, I understand that, but the firmware is freely available from the card manufacturer's website, and would be more current than anything SUSE or Ubuntu distributed anyway. Perhaps ubuntu HAS explicit permission, or a loophole in the law due to non US ownership. Selling you a card, but denying you software to run it MIGHT be considered illegal in some countries. Sadly, not the US. Side issue: ATI has rpms on their site. Inside these RPM it says they were built by SUSE. Yet you can't get them from opensuse, and you have to go fetch them. Probably the same with Nvidia, although I haven't checked. Yet you can get Acrobat directly off the SUSE disks (not-oss). Same with RealPlayer. There seems to be this strange division on what Suse chooses to include and what they don't. The end result is punitive to the end-user. -- _____________________________________ John Andersen
On Tuesday 21 November 2006 11:16 pm, John Andersen wrote:
Yes, I understand that, but the firmware is freely available from the card manufacturer's website, and would be more current than anything SUSE or Ubuntu distributed anyway.
It does not matter how you got something. If you do not have explicit permission to redistribute you cannot do it. That's applies to anything under copyright. One of the rights granted by the GPL is redistribution, which makes Linux distributions possible.
Perhaps ubuntu HAS explicit permission, or a loophole in the law due to non US ownership.
I doubt Broadcom would give permission to Ubuntu and nobody else. They do allow redistribution of the firmware for the 57xx cards however, which is included right in the Linux kernel.
Side issue: ATI has rpms on their site. Inside these RPM it says they were built by SUSE. Yet you can't get them from opensuse, and you have to go fetch them. Probably the same with Nvidia, although I haven't checked.
Those are binary kernel drivers. SUSE does not distribute them: "Novell's Official Position Most developers of the kernel community consider non-GPL kernel modules to be infringing on their copyright. Novell does respect this position, and will no longer distribute non-GPL kernel modules as part of future products. February 9, 2006"
Yet you can get Acrobat directly off the SUSE disks (not-oss). Same with RealPlayer.
Novell has made deals with those companies to allow redistribution.
There seems to be this strange division on what Suse chooses to include and what they don't.
They simply distribute what they are allowed to. -- James Oakley jfunk@funktronics.ca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 23 November 2006 05:49, James Oakley wrote:
t does not matter how you got something. If you do not have explicit permission to redistribute you cannot do it. That's applies to anything under copyright. One of the rights granted by the GPL is redistribution, which makes Linux distributions possible.
Perhaps ubuntu HAS explicit permission, or a loophole in the law due to non US ownership.
I doubt Broadcom would give permission to Ubuntu and nobody else.
On another thread it was suggested that ubuntu does not distribute the firmware, but does distribute a script to fetch it from broadcom's site (and perhaps other sources). I don't know it this is true. But it would certainly be compatible with the GPL, and not totally unlike what opensuse does with ATI drivers. The ATI RPMs appear to be built by the opensuse people on their build farm but only distributed from ATI's website and repository. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 16 November 2006 22:20, John Pierce wrote:
I just installed opensuse 10.1 on a new dell inspiron 9400 and the only way to get the wireless working was with the ndiswrapper. It is a broadcom bc44XX built in wireless chipset.
BTW, you can get Linux drivers for the 4401 chip (I don't know if that is what you have) directly from them... http://www.broadcom.com/support/ethernet_nic/4401.php
The Knetworkmanager connects to my wireless router just fine. However I run a local network and wish to use a static address and I cannot get it to allow me to set the address of wlan0 to be static and use my personal nameservers.
John - I use static in my local net as well. Where are you setting this? Are you going through Yast and setting it in the network card settings? -- kai www.perfectreign.com || www.4thedadz.com a turn signal is a statement, not a request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Yes, I have set it through yast->network cards and I define a wireless card named wlan0 and the driver to be ndiswrapper. I set it to load at boot but it does not come up. In /etc/modprobe.d/ndiswrapper is the line alias wlan0 ndiswrapper. I thought that would bring it up at boot time but it does not. After running yast I can look at /etc/sysconfig/network and I see the file ifcfg-wlan-wlan0 but still no joy. John -- Registered Linux User 263680, get counted at http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote: Anyway I got it to work by surfing on over to the dell site and downloading their new (11/2006) drivers which include a 64bit driver. File name is R140747.EXE (self extracting zip). You need precisely two files out of that zip: bcmwl5.inf bcmwl564.sys <--- for the Core 2 Dou machines. Purge /etc/ndiswrapper with the ndiswrapper -e command, rmmod ndiswrapper and then configure with ndiswrapper -i bcmwl5.inf ndiswrapper -m modprobe ndiswrapper and the wifi lite comes on. Havent got passphrase working yet with my router, but keying in the big fuzzy key did work in NetworkManager. ( update from John Andersen, to keep the thread going ) -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
James Oakley -
John Andersen -
John Pierce -
Kai Ponte -
Kenneth Schneider -
M Harris