mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: Yuval Hager <yuval@avramzon.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	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: Tue, 25 Nov 2008 08:18:18 +0100	[thread overview]
Message-ID: <20081125071818.9256.qmail@stuge.se> (raw)
In-Reply-To: <200811250745.22487.yuval@avramzon.net>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

Yuval Hager wrote:
> I played around with different video drivers and the results are:
> * If using the 'via' driver, I lose the PCIe card immediately upon 
>   initialization
> * Using the 'openchrome' (trunk version), It works well in the
>   beginning.
>   After first blanking the register reads are all 1's, and then
>   when the screen is blank I get a different read (some registers
>   are correct, some are wrong), and when the screen is unblanked, I
>   get 0xff's again. Very consistent and predictabe (same read every
>   time).
> * Using the 'vesa' driver I could not recreate the problem. I could
>   not get the screen to blank for some reason, but closing the lid,
>   going on standby/hibernate, restarting X - all didn't matter much
>   to the PCI and the wireless card kept on working.

Good work! You have beyond any doubt established that the X graphics
driver can cause this problem.

Were you using a kernel framebuffer driver when you saw the problem
also without running X at all? If not, the cause of trouble then is
still unidentified.


//Peter

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-11-25  7:18 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       ` 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 [this message]
2008-12-07  9:29                                       ` Yuval Hager
2008-12-07 16:15                                         ` Larry Finger
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=20081125071818.9256.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=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=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

all inboxes | Powered by JetHome®