9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Silas McCroskey <inkswinc@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bad opcode from vga/realemu on NUC7CJYH after UEFI boot
Date: Wed, 6 May 2020 11:21:39 -0700	[thread overview]
Message-ID: <CAHjwAuzeeAKS74B8y95Y1AEWf5vDLva7q0PuozzQpQGRFEJg5g@mail.gmail.com> (raw)
In-Reply-To: <2530F2E3B3291D21E005A15BDB444865@felloff.net>

Thanks, I'll take a look at those options. Think I'll start with
trying to get the native driver to work since I've never managed to
puzzle that out (always been content with vesa), so it'll be a good
exercise.

- sam-d

On Wed, May 6, 2020 at 10:08 AM <cinap_lenrek@felloff.net> wrote:
>
> there is no vesa bios on pure uefi systems (without CSM). so realemu
> traps when executing all zero bytes as instructions.
>
> bootx64.efi does not set any mode (yet). it queries the mode set up
> by uefi firmware (according to the standard it is supposed to give you
> the native resolution and it sais like at least 1024x768 but nope.
> this is all pure sabotage to force you to install the windows driver
> so they can stay resident on your machine and expose ther cooperate
> branding).
>
> anyway, your guessing is not too far off. we could actually add
> code to 9boot to try to set a specific mode and hope that it maybe
> work... i dont know how well this works or if they even let you do
> that.
>
> another way would be to use this grub operating system, which i think
> can set specific graphics mode and load the plan9 kernel from that
> as a multiboot kernel image.
>
> or try to get the native driver to work. intel graphics is supported
> (partially, not every models, but might not be hard to add support?)
>
> good luck.
>
> --
> cinap


      reply	other threads:[~2020-05-06 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:42 Silas McCroskey
2020-05-06 17:07 ` [9front] " cinap_lenrek
2020-05-06 18:21   ` Silas McCroskey [this message]

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=CAHjwAuzeeAKS74B8y95Y1AEWf5vDLva7q0PuozzQpQGRFEJg5g@mail.gmail.com \
    --to=inkswinc@gmail.com \
    --cc=9front@9front.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).