Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co
!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.co
!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 06 Feb 2007 13:21:43 -0600
From: "Stephen J. Rush"
Subject: Re: Ndiswrapper - fixing one error at a time
Date: Tue, 06 Feb 2007 14:21:35 -0500
User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux))
Message-Id:
Newsgroups: alt.os.linux.ubuntu
References: <12see2
j3qg9466@corp.supernews.com> <6fnfs29o5v2bi6qu72vrqh2jgl8po2b3dc@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Lines: 49
NNTP-Posting-Host: 24.98.130.42
X-Trace: sv3-WONbeHcf9nkY5urtChsC9fGN0zb9d9qRLMp98ipK34jmlqPKlhV
hp+4QZPV+18QNFiDCFc9u+W2pHU!kDrruNdzWkfHq1VcIEzWrO08Vp7naLt7YjGx
LKsTg3CqpITiIXlxCSixzBe8o1cHQxcKYwGNUVY!8Emhljo/U7rcMA==
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
properly
X-Postfilter: 1.3.32
Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:9842
On Tue, 06 Feb 2007 08:04:45 -0500, Derspankster wrote:
> The Etobian wrote:
>> On Mon, 05 Feb 2007 08:59:30 -0500, Juzme wrote:
>>
>>> You keep spinning your wheels following god knows what procedures.
>>> You've got another thread in this group on essentially this same
>>> subject. Follow in detail, slowly, the exact steps in my last post to
>>> your other thread and you will get online. The procedure I've written
>>> for you there has worked for me and many others for these Broadcom chips
>>> literally dozens of times. I'm now online because of that procedure.
>>> If you can't follow the outline in that thread then there is a good one
>>> at the location to which I've already given you a link. It's only
>>> slightly more complicated. See ya 'round.
>>
>> I changed the subject because it morphed to an NDISwrapper discussion.
>>
>> I did follow your instructions, plus the linked procedure. Apparently
>> I had omitted editing modules to add ndiswrapper at the end, so I did
>> that. And rebooted.
>>
>> Unfortunately, when I went into System -> Networking, my card is no
>> longer there, just a modem. The only network interface I have is
>> "lo". There is no wlan0.
> Wireless has been the most frustrating aspect of using Ubuntu Linux that
> I've come across. The OS is a failure at wireless at this time. I'm not
> sure why this is since I'm obviously no expert. I sympathize with you
> Etobian but I can't lend a hand because I've been down the same sorry
> road you have and am no closer to connecting wirelessly.
The problem seems to be Broadcom (May hogs root up their bones!), which
builds WiFi chips that require a boot-time firmware load. The firmware
(which should be useless with anyone else's hardware) is Utter Top Secret
Proprietary Data, available only to Microsoft. So even if you have a
kernel-mode driver for Broadcom's chips (as is provided with the latest
Linux kernel), you still have to load the firmware to make the chip work.
The only (legal) place to get the firmware is to rip it from a Windows
installation that came with your computer. This is really no easier than
installing ndiswrapper and loading the Windows driver itself, and the
process changes a little with each kernel update.
There are other WiFi chipsets that Just Work with Ubuntu. I've read good
things about Atheros. Unfortunately, I'm still struggling with a Broadcom
(May they rot in a Hindu hell!) chip. I had it working under Dapper
Drake, but after the latest distro upgrade, none of my old incantations
and none of the procedures I've found on line will make it work. I may
have to do my first distribution rollback to make my laptop connect
without having to reboot into (Ugh!) Windows.
--- Platinum Xpress/Win/WINServer v3.0pr5
* Origin: Omicron Theta BBS (1:261/20)
|
