From: covertusername967@gmail.com
To: 9front@9front.org
Subject: Re: [9front] Kernel panic when setting screen resolution on machine with i810 chipset
Date: Sat, 30 Nov 2019 01:47:20 -0600 [thread overview]
Message-ID: <7A81763CEAD2B3FFE12007D2AD091175@gmail.com> (raw)
In-Reply-To: 4D4D892F-6E2C-4AEE-9478-9FBC49BC65CC@quintile.net
I hope I'm not necroposting by waiting too long, but I only just now found the time to get back to this.
> hi,
>
> years and years ago (before vga bioss where common) russ wrote a unix app that could dump the registers under x windows. that is probably in the 9fans archives somewhere.
>
> maybe you could re-awaken that to get a starting point for register settings?
>
> -Steve
I DID find something in russ's old contrib on 9p.io:
9fs 9pio
/n/9pio/contrib/rsc/vga.tgz
Unfortunately, I was not able to get that windows executable to run (Windows ME probably didn't help much), and I even have issues getting linux to run correctly on this machine, so I haven't tried it there yet.
> On 2 Oct 2019, at 6:19 am, kokamoto@hera.eonet.ne.jp wrote:
>
>>
>>
>> 1024x768x16: http://okturing.com/src/6976/body
>
> If you exchange your display entry in /lib/vgadb to like:
> ------
> raptop=1024x768
> clock=65
> include=1024x768
> ------
> <raptop can be your name of display>
>
> What will happen?
Sadly, the exact same arc drawing issue happened using those settings.
> By the way, 24 depth is not supported in Plan9.
> If you want it, it should be 32 depth.
>
> Kenji
Ah, good to know.
> PS. I forgot the result of xvidtune, however, I have faint memory of
> it did not help me... It was long long ago, and I got too many age now.☺
Well, it was worth a shot... I imagine that xvidtune was more useful in the days of the CRT anyway.
next reply other threads:[~2019-11-30 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 7:47 covertusername967 [this message]
2019-12-03 6:35 ` k0ga
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 5:56 covertusername967
2019-12-03 18:44 cinap_lenrek
2019-10-02 4:18 kokamoto
2019-10-02 7:17 ` Steve Simon
2019-10-02 2:57 covertusername967
2019-10-02 0:17 kokamoto
2019-10-02 0:08 cinap_lenrek
2019-10-01 23:31 covertusername967
2019-10-01 23:02 cinap_lenrek
2019-10-01 15:45 cinap_lenrek
2019-10-01 12:21 covertusername967
2019-10-01 2:09 kokamoto
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=7A81763CEAD2B3FFE12007D2AD091175@gmail.com \
--to=covertusername967@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).