From: covertusername967@gmail.com
To: 9front@9front.org
Subject: Re: [9front] Kernel panic when setting screen resolution on machine with i810 chipset
Date: Tue, 1 Oct 2019 21:57:06 -0500 [thread overview]
Message-ID: <F3270080E1F193E6F50DB88F6F375092@gmail.com> (raw)
In-Reply-To: 766E532698A9B0B19F2C631B243413E8@hera.eonet.ne.jp
>> i'd try different monitor settings and timings... maybe plug in
>> external vga monitor if there is a port...
>
> Yes, I agree with some problem in moniter settings.
>
> I had this kind of regular deformation once.
> As you see on the second image, bright zones are drawing arc shape,
> which means blank timing may have some shift regularly.
>
> Kenji
Sadly I have no clue how to do low-level programming like this - I'm afraid I'd fry the
chip or monitor. The most i've done with the kernel is add vid/did pairs to the sata
driver... A script kiddie could have done that.
If it helps, I did manage to find some ancient developer documentation on the chipset
itself, though documentation on the whole machine is long gone.
VGA docs: http://download.xskernel.org/docs/controllers/vga/29802601.pdf
Memory controller hub: http://www.clannad.co.uk/datasheets/chipsets/82810memcont.pdf
I/O controller hub: http://www.softelectro.ru/82801aa.pdf
Firmware hub: https://www.dataman.com/media/datasheet/Intel/82802Ax.pdf
When I get home this morning I'll poke around with the registers manually and see what comes
up.
>> i'd try different monitor settings and timings... maybe plug in
>> external vga monitor if there is a port...
There is no external monitor port, unfortunately. I got the settings I put in vgadb from
xvidtune on linux.
next reply other threads:[~2019-10-02 2:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 2:57 covertusername967 [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 5:56 covertusername967
2019-12-03 18:44 cinap_lenrek
2019-11-30 7:47 covertusername967
2019-12-03 6:35 ` k0ga
2019-10-02 4:18 kokamoto
2019-10-02 7:17 ` Steve Simon
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=F3270080E1F193E6F50DB88F6F375092@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).