public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Thomas Capricelli <tcaprice@logatique.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VESA Anybody out there
Date: Fri, 01 Feb 2002 17:53:24 +0100	[thread overview]
Message-ID: <3C5AC804.10605@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202011640070.2501-100000@unicef.org.yu> <3C5AC078.8010103@evision-ventures.com> <20020201163119.6ED6323CBB@persephone.dmz.logatique.fr>

Thomas Capricelli wrote:

>
>Do I have to understand that you're using : "vga=ask scan" ?
>this can't work, cause it doesn't mean anything.
>
>The syntax is "vga=ask" _or_ "vga=scan"
>
>Or, if you prefer, 'ask' is a special scan code you can put, that will ask 
>you (at boot time) which one you want (you'll get a list of scancode 
>supported by your graphic card to choose from)
>

I use vga=ask as kernel parameter
and type scan at the dialogue, which than hangs the system *allways*.




  reply	other threads:[~2002-02-01 16:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020131.162549.74750188.davem@redhat.com>
2002-02-01  0:42 ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Alan Cox
2002-02-01  0:30   ` David S. Miller
2002-02-01  3:46     ` Jeff Garzik
2002-02-01  4:25       ` David S. Miller
2002-02-01  4:48         ` Jeff Garzik
2002-02-01  5:59           ` David S. Miller
2002-02-01  5:10         ` Keith Owens
2002-02-01  5:12           ` Jeff Garzik
2002-02-01  5:18             ` Keith Owens
2002-02-01 13:42               ` Horst von Brand
2002-02-03 23:34                 ` Keith Owens
2002-02-04 20:14                   ` Horst von Brand
2002-02-01  6:01           ` David S. Miller
2002-02-01  6:11             ` Keith Owens
2002-02-01  6:26               ` David S. Miller
2002-02-01  6:43                 ` Keith Owens
2002-02-01 15:03                 ` Alan Cox
2002-02-01 14:55                   ` Jeff Garzik
2002-02-01 15:12                     ` Petr Vandrovec
2002-02-01 15:29                       ` VESA Anybody out there Martin Dalecki
2002-02-01 15:42                         ` Davidovac Zoran
2002-02-01 16:21                           ` Martin Dalecki
2002-02-01 16:33                             ` Thomas Capricelli
2002-02-01 16:53                               ` Martin Dalecki [this message]
2002-02-01 16:35                             ` Sergey S. Kostyliov
2002-02-01 16:37                           ` Anton Altaparmakov
2002-02-01 16:33                         ` Petr Baudis
2002-02-01 17:45                         ` The Candyman
2002-02-02 13:41                           ` Andreas Happe
2002-02-02 21:09                             ` Martin Dalecki
2002-02-05 17:05                         ` Pavel Machek
2002-02-01 16:08                     ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does David Woodhouse
2002-02-04 13:24                     ` Horst von Brand
2002-02-05  7:51                       ` Jeff Garzik
2002-02-01  4:18     ` H. Peter Anvin
2002-02-01  4:35       ` Jeff Garzik
2002-02-01 15:19     ` Alan Cox
2002-02-01 19:37     ` Rob Landley
2002-02-01 19:50       ` Jeff Garzik

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=3C5AC804.10605@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tcaprice@logatique.fr \
    /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