linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elmar Stellnberger <estellnb@elstel.org>
To: linux-fbdev@vger.kernel.org
Subject: making uvesafb work on i586
Date: Mon, 12 Dec 2022 13:12:36 +0100	[thread overview]
Message-ID: <560b51c6-a6b8-a315-f5b5-307e393f6ef8@elstel.org> (raw)

   I am debugging/testing glx and suspend issues on an i586 computer. 
With the vesa driver suspend works and there are no glx problems (since 
it does not support glx). However it only allows for 800x600 instead of 
1024x768 and no external monitor. Now I thought that a framebuffer based 
solution would work best on this computer. However if I want to

> modprobe uvesafb
uvesafb: failed to execute /sbin/v86d
uvesafb: getting VBE info block failed (eax=0x4f00, err=-2)
uvesafb: vbe_init failed with -22

   However there is no sense to have an v86d on an i586 system since you 
would not like to emulate code that is running natively on this machine!
What about a fix for this issue?

   Secondly I have discovered that echo 0 
 >/sys/class/vtconsole/vtcon1/bind hangs my system if nouveau is loaded 
and modesettting isn´t disabled. I was working on the console without 
running an X-server. That seems to be a bug and a regression, too, since 
I remember that having worked in order to switch to another console 
graphics mode driver.


see also: https://sourceforge.net/p/linux-fbdev/bugs/10/
regarding my debugging/testing efforts you may want to have a look at:
https://bugs.mageia.org/show_bug.cgi?id=31227


                 reply	other threads:[~2022-12-12 12:21 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=560b51c6-a6b8-a315-f5b5-307e393f6ef8@elstel.org \
    --to=estellnb@elstel.org \
    --cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).