9front - general discussion about 9front
 help / color / mirror / Atom feed
From: covertusername967@gmail.com
To: 9front@9front.org
Subject: Kernel panic when setting screen resolution on machine with i810 chipset
Date: Sat, 28 Sep 2019 20:15:28 -0500	[thread overview]
Message-ID: <4917D3F7013C68C4954F2DDCF94874DE@gmail.com> (raw)

What I did: 
I added an entry to /lib/vgadb to match the monitor I was using, then attempted to
set the screen resolution using this new entry. I also tried using the regular 'lcd'
setting in /lib/vgadb, and got a similar panic.

What I expected to happen:
I expected a 1024x768x24 framebuffer to become visible.

What happened instead:
The kernel panicked. Panic screen is here: http://okturing.com/src/6959/body

Make and model:
Gateway Profile 3. I would send it back to the manufacturer to have a VESA bios
installed, but as the machine is 20 years old I don't think that will work.

% sysinfo -p:
Panic when retreiving the VGA information. Partial output recovered from serial
console is here: http://okturing.com/src/6963/body
I do not know why the kernel did not output a stack trace this time.

Additional details:
I am using the kernel i810 driver, as this machine does not have a VESA bios. This
kernel is not quite stock Skin of Evil on 386, as I have updated to the latest hg
sources as well as adding a minor change to the sdiahci driver to support the SATA
controller I am using in my file server. I can provide the kernel binary and driver
source if needed, though I do not believe that is the cause of this error as a
similar panic occurs when using the unmodified Skin of Evil iso.



                 reply	other threads:[~2019-09-29  1:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4917D3F7013C68C4954F2DDCF94874DE@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).