mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danny Tholen <danny@mailmij.org>
To: kernellist <linux-kernel@vger.kernel.org>
Subject: no visible screen with console driver.
Date: Sat, 27 Jul 2002 17:20:34 +0200	[thread overview]
Message-ID: <200207271720.41657.danny@mailmij.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I think there is a small problem in the linux console driver, although it could also just be my hardware.
Anyway, I have a problem on 2 machines with an A7V-266E motherboard, an IIyama HM704 monitor
and 2 different nvidia cards.
The problem is rather simple: when the console driver starts, the screen turns black. X starts normally
and is visible. And than when I go back to a virtual console it suddenly appears correctly. Apperently X
resets the console better than the kernel:)
The vesa driver also doesn't give a visible screen. But either the rivafb or vga16fb switch the screen back
to visible after a few seconds. 
Horizontal and vertical refresh rates as indicated by the monitor info are similar; when I have a visible
screen or not. The problem also is in the 2.2 kernels that I tested.

Anyone any idea where to look for the problem, or what is the difference between switching from X and the normal
initisialization of the console?

Danny




- -- 
"I teleported home one night
With Ron and Sid and Meg.
Ron stole Meggie's heart away
And I got Sidney's leg."

- -- A poem about matter transference beams. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9QrpHaeiN+EU2vEIRAqSrAKCU5vnbVwwvi1d8gDjCHywQHUVKTQCcCtuu
h5QyGnekikDHOuw/TopYnRA=
=GqpX
-----END PGP SIGNATURE-----


                 reply	other threads:[~2002-07-27 15:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200207271720.41657.danny@mailmij.org \
    --to=danny@mailmij.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

all inboxes | Powered by JetHome®