From: Bruce Guenter <bruceg@em.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Broadcom 4401 problem
Date: Mon, 23 Aug 2004 09:57:12 -0600 [thread overview]
Message-ID: <20040823155712.GA21840@em.ca> (raw)
In-Reply-To: <20040822221734.GA10372@ee.oulu.fi>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
On Mon, Aug 23, 2004 at 01:17:34AM +0300, Pekka Pietikainen wrote:
> Could you try the driver from http://www.ee.oulu.fi/~pp/b44-095-2.tgz ,
> which has some fixes that have been submitted but not yet merged.
Thanks. This source has some problems. When compiling, I get multiple
errors regarding PCI_DEVICE_ID_BCM4713 being undefined:
/root/b44/b44.c:94: error: `PCI_DEVICE_ID_BCM4713' undeclared here (not in a function)
etc Is this missing a header file or some other update?
In order to try to get it to compile, I removed the PCI table entry for
the BCM4713 and made every conditional that depends on it false (by
removing the appropriate code). However, when trying to ifconfig the
interface I get:
SIOCSIFFLAGS: Cannot allocate memory
SIOCSIFFLAGS: Cannot allocate memory
> If that
> doesn't help, the broadcom driver
> ( http://www.broadcom.com/drivers/downloaddrivers.php ) might be
> worth a try.
The Broadcom Linux driver version 3.0.7 also locks up on me, but it
doesn't support "ethtool -A", so I have to stop and start the interface
completely to get it working again.
> Also if you have more than 1Gb of memory, booting with mem=1024m
> might help
Nope. 512MB RAM.
--
Bruce Guenter <bruceg@em.ca> http://em.ca/~bruceg/ http://untroubled.org/
OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-23 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 20:53 Broadcom 4401 problem Bruce Guenter
2004-08-22 22:17 ` Pekka Pietikainen
2004-08-23 15:57 ` Bruce Guenter [this message]
2004-08-23 19:34 ` Pekka Pietikainen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040823155712.GA21840@em.ca \
--to=bruceg@em.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.