From: sl@9front.org
To: 9front@9front.org
Subject: Re: [9front] new bounties: replace p9sk1; improve the tls(3) device
Date: Wed, 20 May 2015 17:31:40 -0400 [thread overview]
Message-ID: <396b34e8e65ece8957ab0ecf7e0c700b@u2.sfldmibb.det.wayport.net> (raw)
>> > Note: The VESA driver only works with whatever modes the VESA BIOS
>> > reports; unfortunately, we've found (for example) some laptops whose
>> > VESA BIOS does not contain a mode for its LCD screen's native
>> > resolution.
>> >
>> > sl
>>
>> I think this includes my w510.
>
> It includes my laptop. If I disable the internal display it lets me
> set the native resolution of that display fine. I would like to see a
> tool that sets resolutions via vesa that aren't in the bios. I know
> this is possible because the hackintosh fags do it, but I have no clue
> how it's done. They don't document anything.
There are several problems:
- every VESA BIOS is unique
- even cards with the same model number often contain
different chips and/or firmware
- some of them can be altered via software but there is no
documentation at all
- fucking up could explode your things
Based on prior experience with hackintosh, I also suspected that
tampering with VESA BIOS would be an option. A few years ago cinap
hacked a program, based on reports by hackintosh nerds:
https://plan9.stanleylieber.com/hardware/thinkcentre/m55/8810-d3u/vbt.c
that I used to try to manipulate the VESA BIOS in two of my cards:
nVidia GeForce 8400 GS
ATI X1300
I never managed to induce a fully working mode at 1920x1080x32,
but I did succeed in altering some of the modes reported. In one
case I was able to induce working 1920x1080 resolution, but the
colors were all garbled. After a while I gave up.
Again, though, every VESA BIOS is unique. The best hope is to
locate a card that someone already succeeded in altering and
hope that the card you actually receive happens to match the
card the person reported.
sl
next reply other threads:[~2015-05-20 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 21:31 sl [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 23:20 mveety
2015-05-20 23:00 mveety
2015-05-20 23:03 ` Jacob Todd
2015-05-20 21:04 sl
2015-05-20 23:08 ` Jacob Todd
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=396b34e8e65ece8957ab0ecf7e0c700b@u2.sfldmibb.det.wayport.net \
--to=sl@9front.org \
--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).