public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	Shaun Jackman <sjackman@telus.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Hang after "BIOS data check successful" with DVI
Date: Tue, 17 Aug 2004 17:58:31 +0100	[thread overview]
Message-ID: <20040817165831.GC19243@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408170950470.22078@montezuma.fsmlabs.com>

On Tue, Aug 17, 2004 at 09:51:55AM -0400, Zwane Mwaikambo wrote:
 > On Tue, 17 Aug 2004, Petr Vandrovec wrote:
 > 
 > > On 16 Aug 04 at 16:55, Shaun Jackman wrote:
 > > > When I have a DVI display plugged into my Matrox G550 video card the
 > > > boot process hangs at "BIOS data check successful". I am running Linux
 > > > kernel 2.6.6. This problem does not affect Linux kernel 2.4.26. If I
 > > > boot without the DVI display plugged in, I can plug it in after the
 > > > boot process and the display works.
 > >
 > > Try disabling CONFIG_VIDEO_SELECT and/or comment out call to store_edid
 > > in arch/i386/boot/video.S. Also which bootloader you use? From
 > > quick glance at bootloaders, grub1 seems to set %sp to 0x9000, while
 > > LILO to 0x0800. And I think that 2048 byte stack (plus something already
 > > allocated by loader) might be too small for DDC call, as MGA BIOS first
 > > creates EDID copy on stack...
 > 
 > Urgh, this bug is still around :(
 > 
 > http://bugme.osdl.org/show_bug.cgi?id=1458

sidenote: A number of the int 10h calls in arch/i386/boot/video.S either
don't check the return code, and blindly assume everything went ok,
or do the wrong thing with them.

Example..

# get video mem size
    leaw    modelist+1024, %di
    movw    $0x4f00, %ax
    int $0x10
    xorl    %eax, %eax
    movw    18(%di), %ax
    movl    %eax, %fs:(PARAM_LFB_SIZE)

Checking http://www.ctyme.com/intr/rb-0273.htm shows that on return
from the int 10h, we should check al==4f before doing anything with
the results. Instead we not only ignore the return code, but trash it 8-)

Same story with function 4f0a a few lines below.

I did have a patch to change this a looong time ago (early 2.5)
but I don't know what became of it. Even google doesn't seem to turn it
up, so its possible I never got around to posting it.

		Dave


  reply	other threads:[~2004-08-17 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 10:57 Hang after "BIOS data check successful" with DVI Petr Vandrovec
2004-08-17 13:51 ` Zwane Mwaikambo
2004-08-17 16:58   ` Dave Jones [this message]
2004-08-17 19:07 ` Shaun Jackman
2004-08-17 19:08 ` Shaun Jackman
  -- strict thread matches above, loose matches on Subject: below --
2004-08-17 14:23 Petr Vandrovec
2004-08-16 23:55 Shaun Jackman
2004-08-16 19:07 ` Aaron Michael Bauman

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=20040817165831.GC19243@redhat.com \
    --to=davej@redhat.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjackman@telus.net \
    --cc=zwane@linuxpower.ca \
    /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