iB::Topic::Broadcom native works with Puppy not with DSL?

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » Broadcom native works with Puppy not with DSL?

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (4) </ 1 2 [3] 4 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Broadcom native works with Puppy not with DSL?, BCM43xx configuration issue

< Next Oldest | Next Newest >

stevesr0

Group: Members
Posts: 32
Joined: July 2007

Posted: Sep. 17 2007,03:29

I tried to configure my wireless card with ndiswrapper, but no go.

When I did lspci, no broadcom card was detected (mine is usually declared as a 4306). I sought the info after booting with another distribution and the pci id was stated to be 00:0c.0 with the other info being 14e4:4320. I used this to try to identify the drivers that ndiswrapper recommended, but it was a tad confusing.

When running in Windows, I replaced the original Broadcom driver and inf because of a "serious" exploit possible with that version (v. 3.30.15.5) by downloading and installing a broadcom driver from the Linksys site (v. 4.100.15.5).

It is possible that this driver doesn't work with ndiswrapper; I didn't see any information about this.

However, when I tried to configure the driver using your miniscript, starting with sudo cat /opt/myndis.sh, the response was invalid no such file.

Later, after trying to configure with the ndiswrapper button in the DSL panel, I noted that there was an myndis file in the /ramdisk/home/dsl directory which contained the script you mentioned. However, ndiswrapper reported that the connection failed.

I appreciate further suggestions and will be happy to try the older driver if that seems likely to work better.

Steve

Juanito

Group: Members
Posts: 1601
Joined: Sep. 2005

Posted: Sep. 17 2007,03:50

Quote

However, when I tried to configure the driver using your miniscript, starting with sudo cat /opt/myndis.sh, the response was invalid no such file.

- that's because I made the file myself. I have two, this one and another without the WEP code that I use to connect in airports, etc.

I'm not sure if you realised this already, but you need both driver files - the *.inf and the *.sys for ndiswrapper to work. I remember that I had to try several drivers before I found one that would work (even though they all worked with winxp). I also found that it is better to reboot after each failed attempt - at least until you're sure you have a working driver.

Maybe the ndiswrapper site is the best place to start - they have many links to drivers for many different cards, see here for the list starting with "b"

stevesr0

Group: Members
Posts: 32
Joined: July 2007

Posted: Sep. 17 2007,13:03

I placed the .inf and the .sys files in the same directory as the instructions state (somewhere <g>) and put the path to the directory in the ndiswrapper window, which then constructed a myndis file whose contents matched the one you constructed manually.

Sure, it is possible that another .sys and .inf combo will work.

I will give it a try as I have time.

BTW, do you have a version, revision number, date and size for the .inf and .sys files that worked for you? I am curious; the listing at Ndiswrapper is kind of confusing - the one I saw was a serious of anecdotes. There is another listing that has a recommended list by item (such as manufacturer and model of laptop or card).

Thanks

Steve

Juanito

Group: Members
Posts: 1601
Joined: Sep. 2005

Posted: Sep. 17 2007,13:19

The files I have are:

bcmwl5.sys 335kb version 3.70.22.0 BCM 802.11g Network Adapter wireless driver
bcmwl5a.inf 44kb

Interestingly (or not) the same driver worked for my previous card (Dell Wireless 1350 WLAN Mini-PCI Card) as for this card (Dell Wireless 1450 Dual Band WLAN Mini-PCI Card) - both made by Broadcom