public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	George Bonser <george@gator.com>,
	Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Dale Amon <amon@vnl.com>, linux-kernel@vger.kernel.org
Subject: Re: Pentium mobo fails on upgrade from 2.2 to 2.4
Date: Mon, 11 Mar 2002 12:06:31 +0000	[thread overview]
Message-ID: <20020311120631.GO3296@vnl.com> (raw)
In-Reply-To: <20020309134540.GZ13355@vnl.com> <E16jm3j-0002Ew-00@the-village.bc.nu>
In-Reply-To: <E16jm3j-0002Ew-00@the-village.bc.nu>

Thanks to all who replied and offered suggestions.
Although the suggestions themselves didn't solve
the problem, they eventually led me to it by
suggesting that the BIOS was indeed faulty.

It appears that it was turned on in my 2.2.18 kernel
and it worked fine; but when I updated with oldconfig
it brought the old settings across. I assumed that
because the feature worked in the old kernel on that
MoBo, it was okay and the board didn't have the listed
chip sets anyway.

When at wits end, I disabled it anyway, just because
it said "buggy BIOS".

That solved the problem. So I'm sorted.

Does anyone keep track of what MoBo/chipset and 
kernel major version combinations have finicky
config requirements? I'd be happy to supply whatever
info you need.

-- 
------------------------------------------------------
    Nuke bin Laden:           Dale Amon, CEO/MD
  improve the global          Islandone Society
     gene pool.               www.islandone.org
------------------------------------------------------

  reply	other threads:[~2002-03-11 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 13:45 Pentium mobo fails on upgrade from 2.2 to 2.4 Dale Amon
2002-03-09 18:59 ` Alan Cox
2002-03-11 12:06   ` Dale Amon [this message]
2002-03-12  1:13     ` Dale Amon

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=20020311120631.GO3296@vnl.com \
    --to=amon@vnl.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=george@gator.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.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