public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
To: Simon Richard Grint <rgrint@compsoc.man.ac.uk>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Rajesh Shah <rajesh.shah@intel.com>
Subject: Re: arch/i386/boot/video.S hang
Date: Thu, 16 Jun 2005 10:33:41 -0700	[thread overview]
Message-ID: <20050616103340.A4951@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050615220554.GA1911@srg.demon.co.uk>; from rgrint@compsoc.man.ac.uk on Wed, Jun 15, 2005 at 11:05:54PM +0100

On Wed, Jun 15, 2005 at 11:05:54PM +0100, Simon Richard Grint wrote:
> 
> I'm trying to upgrade an old AMD K6-2 machine (aladdin bios/gigabyte GA-5AX
> motherboard, latest version of the bios) to 2.6.11. Unfortunately kernels later 
> than 2.6.9 hang very early in the boot process just after the vga= mode selection, 
> but before the kernel announces "uncompressing linux".
> 
> I have narrowed the problem down to the store_edid function in
> arch/i386/boot/video.S where the edid block is obtained and stored before
> entering protected mode.  The exact patch which seems to cause me problems
> is http://www.ussg.iu.edu/hypermail/linux/kernel/0409.3/1786.html
> 
> Storing the edid block at 0x140 causes this machine to hang, whereas backing
> this patch out and instead using 0x440 (or even 0x160) seems to work fine.
> 
> Is this problem just because of an old and buggy bios or is there another
> reason?
> 

What boot loader are you using. grub/lilo?

Does it work with CONFIG_VIDEO_SELECT disabled in your kernel CONFIG?

Thanks,
Venki

  reply	other threads:[~2005-06-16 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 22:05 arch/i386/boot/video.S hang Simon Richard Grint
2005-06-16 17:33 ` Venkatesh Pallipadi [this message]
2005-06-16 17:58   ` Simon Richard Grint
2005-06-18  0:25     ` Venkatesh Pallipadi

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=20050616103340.A4951@unix-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajesh.shah@intel.com \
    --cc=rgrint@compsoc.man.ac.uk \
    /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