From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] figuring out what to add in vgadb?
Date: Sat, 6 Apr 2024 06:02:25 +0200 [thread overview]
Message-ID: <3fblqe5dcfbraaxv6mqjolrkb3dw2s4ftr33oya34zsfipylya@5a4ya2mcy6tn> (raw)
In-Reply-To: <A93C1DFACDDA0504BD759C25399280E3@wopr.sciops.net>
On Fri, Apr 05, 2024 at 11:58:36PM +0200, qwx@sciops.net wrote:
> On Fri Apr 5 13:38:17 +0200 2024, staal1978@gmail.com wrote:
> > Hi all,
> >
> > I am pretty happy with 9front on a cheap refurbished laptop, especially
> > now that ethernet over usb has been solved and I have built the latest
> > netsurf on it.
> >
> > One little annoyance still is that I run at crappy resolution and can
> > not set it with aux/vga (and setting vgasize in plan9.ini did nothing)
> > Sysinfo can be seen here:
> > http://sysinfo.9front.org/src/542/body
> >
> > Is there a similar trick to how usbtree could figure out what to do to
> > get nusb/ether to work but for graphics?
> >
> > this entry from pci -v probably relevant but is there a way to translate
> > that to a vgadb entry?
> >
> > 0.2.0: vid 03.00.00 8086/3185 255 0:a0000004 16777216 2:9000000c 268435456 4:0000f001 64
> > Intel Corporation GeminiLake [UHD Graphics 600]
>
> Your card is a gemini lake gen igfx, which we unfortunately don't yet
> support; our latest gen is broadwell, with work underway for skylake.
> For now, vesa or the uefi framebuffer you're handed are the best you
> could get. An external monitor may work with vesa as well (see vga(8)
> for example usage), but it's somewhat unlikely.
>
Thanks. Good to know that it is a driver issue and not "just" a
recognition issue (like nusb/ether). I will check if I can enhance it by
the UEFI framebuffer.
The resolution will be less of an issue when I got Sigrid's
riow/bar/theming set up. Especially having multiple work spaces will
definitely help.
> Hope that helps,
> qwx
next prev parent reply other threads:[~2024-04-06 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:42 Jens Staal
2024-04-05 21:58 ` qwx
2024-04-06 4:02 ` Jens Staal [this message]
2024-04-06 5:26 ` Jens Staal
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=3fblqe5dcfbraaxv6mqjolrkb3dw2s4ftr33oya34zsfipylya@5a4ya2mcy6tn \
--to=staal1978@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).