Linux IA64 platform development
 help / color / mirror / Atom feed
From: Jonathan_Kwahk@Dell.com
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] ACPI problems in 2.4.2-ia64-010228
Date: Wed, 07 Mar 2001 19:38:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005261@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005246@msgid-missing>

Yes, for Big Sur there is a more recent BIOS build than 89B (I currently
have 99 PAL 6.6.19).
I believe the EFI version is 12.33 based on the EFI spec. rev. 1.02.
SAL revision is 1.01 based on SAL spec. rev. 2.9.

I would try to get my hands on the 99 build since it supports many missing
SMBIOS structure types, MCA (i think it's memory correction algorithm), and
other fixes.

J

-----Original Message-----
From: Keith Owens [mailto:kaos@melbourne.sgi.com]
Sent: Wednesday, March 07, 2001 1:12 AM
To: davidm@hpl.hp.com; Grover, Andrew; linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] ACPI problems in 2.4.2-ia64-010228


On Tue, 06 Mar 2001 12:30:55 +1100, 
Keith Owens <kaos@melbourne.sgi.com> wrote:
>BugSur 2 B1 cpus.  PAL 2213, BIOS W460GXBS2.86E.0070.B.200008150911.
>Kernel 2.4.2 + ia64-010228.  I am getting semi-random data in the acpi
>tables which more often than not will hang the machine during boot.

Upgraded to PAL 2215, W460GXBS2.86E.0084.P02.200010271750.  Still
getting the ACPI problems.  Currently EFI 0.99, is there a more recent
version version of EFI for BigSur?


_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


      parent reply	other threads:[~2001-03-07 19:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06  1:30 [Linux-ia64] ACPI problems in 2.4.2-ia64-010228 Keith Owens
2001-03-06 18:49 ` Mallick, Asit K
2001-03-06 23:06 ` Keith Owens
2001-03-07  7:11 ` Keith Owens
2001-03-07 11:01 ` Keith Owens
2001-03-07 19:38 ` Jonathan_Kwahk [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=marc-linux-ia64-105590693005261@msgid-missing \
    --to=jonathan_kwahk@dell.com \
    --cc=linux-ia64@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