linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Yuval Hager <yuval@avramzon.net>
Cc: Peter Stuge <peter@stuge.se>,
	wireless <linux-wireless@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Michael Buesch <mb@bu3sch.de>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: BCM4312 Fails when xdm is started
Date: Sun, 07 Dec 2008 10:15:38 -0600	[thread overview]
Message-ID: <493BF6AA.7030602@lwfinger.net> (raw)
In-Reply-To: <200812071129.32113.yuval@avramzon.net>

Yuval Hager wrote:
> 
> This issue has been tracked down to be at the openchrome driver. It appears 
> that somehow it corrupted the PCI bus, and damaged the device right after the 
> video card - the wireless card. 
> 
> The current workaround for this is here - 
> http://wiki.openchrome.org/pipermail/openchrome-devel/2008-November/000139.html - 
> but this is just a quick hack, not a fix, although it works great for me. The 
> openchrome team is working on a patch based on this.
> 
> Thanks for all the help - I am a very happy HP2133 user, and a very happy 
> community member. This was an amazing opensource support experience, which 
> I'll remember for a long time. Thank you all!

Thanks for the feedback. The community may struggle a bit on some problems, and
the approach to a solution may look like a drunken sailor's walk, but we usually
get there.

Larry


  reply	other threads:[~2008-12-07 16:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200811151801.02369.yuval@avramzon.net>
     [not found] ` <491EFB9D.3040002@lwfinger.net>
     [not found]   ` <200811151907.05636.yuval@avramzon.net>
     [not found]     ` <20081115174623.27321.qmail@stuge.se>
2008-11-21 16:25       ` BCM4312 Fails when xdm is started Larry Finger
2008-11-21 17:42         ` Michael Buesch
2008-11-21 18:28           ` Larry Finger
2008-11-22  6:39             ` Yuval Hager
2008-11-22 15:13               ` Michael Buesch
2008-11-22 15:32                 ` Larry Finger
2008-11-22 15:54                   ` Michael Buesch
2008-11-23  7:26                     ` Yuval Hager
2008-11-23 11:49                     ` Yuval Hager
2008-11-23 12:20                       ` Michael Buesch
2008-11-23 15:42                         ` Larry Finger
2008-11-23 17:42                           ` Michael Buesch
     [not found]                             ` <200811231955.41722.yuval@avramzon.net>
2008-11-23 18:08                               ` Michael Buesch
2008-11-23 20:46                         ` Peter Stuge
2008-11-23 21:09                           ` Larry Finger
2008-11-24  8:49                             ` Yuval Hager
2008-11-24 10:55                               ` Michael Buesch
2008-11-24 16:11                                 ` Larry Finger
2008-11-25  5:43                                   ` Yuval Hager
2008-11-25  7:18                                     ` Peter Stuge
2008-12-07  9:29                                       ` Yuval Hager
2008-12-07 16:15                                         ` Larry Finger [this message]
2008-11-25 11:05                                     ` Michael Buesch

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=493BF6AA.7030602@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=peter@stuge.se \
    --cc=yuval@avramzon.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).