public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lehmann <aaronl@vitelus.com>
To: Ryan Sizemore <ryan831@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with ATX halt
Date: Sat, 30 Dec 2000 17:55:25 -0800	[thread overview]
Message-ID: <20001230175524.C3914@vitelus.com> (raw)
In-Reply-To: <NEBBIFHONDNEGJDKODONAEIDCDAA.ryan831@usa.net>
In-Reply-To: <NEBBIFHONDNEGJDKODONAEIDCDAA.ryan831@usa.net>; from ryan831@usa.net on Thu, Dec 28, 2000 at 11:59:06PM -1000

[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]

On Thu, Dec 28, 2000 at 11:59:06PM -1000, Ryan Sizemore wrote:
>    I have a comp. running mandrake 7.2, and when i go to power it down, it
> gives me a screen full of errors, including a stackdump. It happens as the
> very last thing (including being after the file system is unmounted, so I
> highly doubt that the error is recorded somewhere. But i will hand-copy the
> stack for whomever thinks it may be useful. The error is reproduced every
> time, without equivication. Any insight or questions are much apriciated.
> The motherboard is a Soyo 5EMA+ r1.0 w/ ETEQ EQ82C6638 Chipset, and it has
> an Award BIOS.

A BIOS upgrade fixes this, as well as some major problems
with large IDE drives. I have the same motherboard and had
the same problem until I updated the BIOS. Their ChangeLog
even says "Systems running Linux can now properly shutdown."
http://www.soyo.com.tw/cgi-bin/prodinfo.exe?track=regular&board586=5EMAFamily&bios=1 will get you to the page, and get the latest file
for the 5EMA+. In fact, I'll even be kind enough to provide the
disk image I used with DOS and the bios image and updater on
it. Put in a blank 1.4MB floppy disk, download this file from
http://vitelus.com/aaronl/biosdisk.img, and run as root:

  dd if=biosdisk.img of=/dev/fd0 bs=512 conv=sync ; sync

Then boot of the floppy and run the updater with the bios file as an
argument. I forget which is which but the updater ends in .EXE and the
bios image ends in .BIN.

Let it finish and reboot into Linux. Good luck.

Software piracy nazis, M$: No flames, please.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      parent reply	other threads:[~2000-12-31  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-29  9:59 Problem with ATX halt Ryan Sizemore
2000-12-29 12:20 ` Erik Mouw
2000-12-29 17:41 ` Coy A Hile
2000-12-31  1:55 ` Aaron Lehmann [this message]

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=20001230175524.C3914@vitelus.com \
    --to=aaronl@vitelus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan831@usa.net \
    /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