public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Konecny <pekon@informatics.muni.cz>
To: jmerkey@vger.timpanogas.org
Cc: dominik.kubla@uni-mainz.de, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18-25 DELL Laptop Video Problems
Date: 14 Dec 2000 03:29:11 +0100	[thread overview]
Message-ID: <qww1yvbivm0.fsf@decibel.fi.muni.cz> (raw)

On Wed, Dec 13, 2000 at 01:34:46AM +0100, Dominik Kubla wrote:
> On Mon, Dec 11, 2000 at 11:11:41AM -0700, Jeff V. Merkey wrote:
> ...
> > Then this is the vga=271 stuff?
> >
> > Jeff
>
> No, that's just selecting the VGA resolution. I am referring to the
> video parameter:
>
> video=<driver>:<option>[,<option>,...]
>
> Look at linux/Dokumentation/fb/modedb.txt.
>
It's not in my tree (2.2.18), the only documentation I could find was
the source code. Anyway, it seems that atyfb gets a precendence over
vesafb and screws up the LCD. Right now I use the following kernel params:
video=atyfb:off video=vesa:mtrr vga=795

For reference this is Dell Inspiron 5000, lspci -vv says this:
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M Mobility AGP 2x (rev 64) (prog-if 00 [VGA])
        Subsystem: Dell Computer Corporation: Unknown device 009f
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 66 (2000ns min), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at fd000000 (32-bit, non-prefetchable)
        Region 1: I/O ports at 2000
        Region 2: Memory at fc000000 (32-bit, non-prefetchable)
        Capabilities: [50] AGP version 1.0
                Status: RQ=255 SBA+ 64bit- FW- Rate=x1,x2
                Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
        Capabilities: [5c] Power Management version 1
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


                                                Regards, Petr
-- 
Snow Day -- stay home.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-14  3:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14  2:29 Petr Konecny [this message]
2000-12-14  7:20 ` 2.2.18-25 DELL Laptop Video Problems Dominik Kubla
  -- strict thread matches above, loose matches on Subject: below --
2000-12-09 22:49 Jeff V. Merkey
2000-12-09 22:03 ` Bob Lorenzini
2000-12-09 22:29   ` Alan Cox
2000-12-09 23:00   ` Jeff V. Merkey
2000-12-09 22:16     ` Bob Lorenzini
2000-12-10  1:12       ` Jeff V. Merkey
2000-12-09 22:34     ` Alan Cox
2000-12-10  1:13       ` Jeff V. Merkey
2000-12-10 16:49         ` Dominik Kubla
2000-12-10 22:50           ` Jeff V. Merkey
2000-12-11  7:26             ` Dominik Kubla
2000-12-11 18:11               ` Jeff V. Merkey
2000-12-13  0:34                 ` Dominik Kubla
2000-12-13  1:41                   ` Jeff V. Merkey

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=qww1yvbivm0.fsf@decibel.fi.muni.cz \
    --to=pekon@informatics.muni.cz \
    --cc=dominik.kubla@uni-mainz.de \
    --cc=jmerkey@vger.timpanogas.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox