All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Bugla <uwe.bugla@gmx.de>
To: Maximilian Engelhardt <maxi@daemonizer.de>
Cc: linux-wireless@vger.kernel.org,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	"Buesch, Michael" <mb@bu3sch.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
Date: Fri, 25 May 2007 21:40:22 +0200	[thread overview]
Message-ID: <200705252140.22635.uwe.bugla@gmx.de> (raw)
In-Reply-To: <200705252048.11931.maxi@daemonizer.de>

Am Freitag, 25. Mai 2007 20:48 schrieben Sie:
> On Fri, 25 May 2007 17:59:29 +0200, Uwe Bugla wrote:
> > Perhaps someone reading this could try to reproduce that problem on his
> > machine.
> > Now who of the readers owes a Broadcom 4401 NIC and can please try to
> > test kernel 2.6.22-rc2-mm1?
> >
> > Those NICs have been used very very often as onboard controllers,
> > especially on ASUS boards.
>
> I've been using 2.6.22-rc2 for some time and now I compiled 2.6.22-rc2-
> mm1 and both work fine with the BCM4401 in my laptop.
>
> Maxi

Hello Maxi,

That may be true for your Laptop, but it unfortunately isn't true for my ASUS 
mainboard onboard controller.

Unfortunately I cannot confirm this:

My broadcom 4401 driver is not part of a notebook, but instead part of an ASUS 
P4PE mainboard.

At my second attempt I went the conventional path (i. e. ignoring the fact 
that
"Broadcom 4400 ethernet support appears twice in section "Network device 
support":

Whether you leave out "EISA, VLB, PCI and on board controllers" or not it 
simply appears twice in kernel config! This is bug number 1.

Conventional path means:

EISA, VLB, PCI and on board controllers Y

Broadcom 4400 ethernet support m

Broadcom 4400 PCI device support Y

This configuration binds:

Sonics Silicon Backplane Support m

Support for SSB on PCI-bus host

SSB PCI core driver

This time I do get a "good" interrupt: IRQ 21 for the the device.

BUT:

Trying to ping another machine fails saying:

"destination host unreachable"


That means, Although the interrupt is fine now, the device is still not 
functionable.

This is bug number 2.

Cheers

Uwe

P. S.: Michael, Andrew, if you need additional information to resolve that 
issue please tell / ask me.

  reply	other threads:[~2007-05-25 19:45 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 19:56 BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400) Uwe Bugla
2007-05-24 20:06 ` Andrew Morton
2007-05-24 21:16   ` Uwe Bugla
2007-05-25 13:16     ` Michael Buesch
2007-05-25 13:12   ` Michael Buesch
2007-05-25 13:20     ` Michael Buesch
2007-05-25 13:59     ` Uwe Bugla
2007-05-25 14:52       ` Michael Buesch
2007-05-25 15:59         ` Uwe Bugla
2007-05-25 16:23           ` Michael Buesch
2007-05-25 18:48           ` Maximilian Engelhardt
2007-05-25 19:40             ` Uwe Bugla [this message]
2007-05-26  5:00               ` Michael Buesch
2007-05-26  9:39                 ` Maximilian Engelhardt
2007-05-26 10:40                 ` Uwe Bugla
2007-05-26 15:36                   ` Michael Buesch
2007-05-26 15:52                     ` Uwe Bugla
2007-05-26 15:50                   ` Michael Buesch
2007-05-26 16:13                     ` Andrew Morton
2007-05-26 16:20                       ` Uwe Bugla
2007-05-26 16:46                         ` Francois Romieu
2007-05-26 16:21                       ` Michael Buesch
2007-05-26 16:26                         ` Uwe Bugla
2007-05-26 16:40                           ` Michael Buesch
2007-05-26 17:04                             ` Uwe Bugla
2007-05-26 17:18                               ` Michael Buesch
2007-05-26 17:24                                 ` Uwe Bugla
2007-05-26 18:03                                   ` Michael Buesch
2007-05-26 18:19                                     ` Andrew Morton
2007-05-26 19:38                                       ` Uwe Bugla
2007-05-26 19:57                                         ` Larry Finger
2007-05-26 20:22                                           ` Francois Romieu
2007-05-26 20:33                                           ` Uwe Bugla
2007-05-26 21:00                                             ` Michael Buesch
2007-05-26 18:41                                 ` Benoit Boissinot
2007-05-26 18:46                                   ` Michael Buesch
2007-05-26 18:58                                   ` Uwe Bugla
2007-05-26 19:14                                     ` Michael Buesch
2007-05-26 19:19                                     ` Michael Buesch
2007-05-26 19:39                                       ` Uwe Bugla
2007-05-26 19:49                                         ` Michael Buesch
2007-05-26 21:32                                           ` Uwe Bugla
2007-05-26 21:52                                             ` Dan Williams
2007-05-26 22:16                                               ` Uwe Bugla
2007-05-26 21:58                                             ` Michael Buesch
2007-05-26 19:04                       ` Michael Buesch
2007-05-28 12:12                       ` Michael Buesch
2007-05-26 16:14                     ` Uwe Bugla
2007-05-26 22:42                   ` David Miller
2007-05-25 16:56         ` Andrew Morton
2007-05-25 18:42           ` Uwe Bugla
2007-05-27 20:02 ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2007-05-27 10:46 Uwe Bugla
2007-05-27 13:41 ` Kyle Moffett

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=200705252140.22635.uwe.bugla@gmx.de \
    --to=uwe.bugla@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maxi@daemonizer.de \
    --cc=mb@bu3sch.de \
    /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.