From: "Kathy Frazier" <kfrazier@mdc-dayton.com>
To: <arjanv@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [APM] CPU idle calls causing problem with ASUS P4PE MoBo
Date: Thu, 7 Aug 2003 16:44:39 -0500 [thread overview]
Message-ID: <PMEMILJKPKGMMELCJCIGOEAECEAA.kfrazier@mdc-dayton.com> (raw)
In-Reply-To: <1060285402.24858.0.camel@laptop.fenrus.com>
>dmidecode is an application that comes in the kernel-utils rpm that
>dumps a bunch of BIOS information
Here you go, here's the top part. If you need anything else, let me know.
Regards,
Kathy Frazier
SMBIOS 2.3 present.
DMI 2.3 present.
56 structures occupying 1482 bytes.
DMI table at 0x000F0040.
Handle 0x0000
DMI type 0, 20 bytes.
BIOS Information Block
Vendor: Award Software, Inc.
Version: ASUS P4PE ACPI BIOS Revision 1006
Release: 07/15/2003
BIOS base: 0xF0000
ROM size: 448K
Capabilities:
Flags: 0x000000007FCBDE80
Handle 0x0001
DMI type 1, 25 bytes.
System Information Block
Vendor: System Manufacturer
Product: System Name
Version: System Version
Serial Number: EVAL
Handle 0x0002
DMI type 2, 8 bytes.
Board Information Block
Vendor: ASUSTeK Computer INC.
Product: P4PE
Version: REV 1.xx
Serial Number: xxxxxxxxxxx
Handle 0x0003
DMI type 3, 17 bytes.
Chassis Information Block
Vendor: Chassis Manufacture
Chassis Type: Tower
Version: Chassis Version
Serial Number: EVAL
Asset Tag: Asset-1234567890
Handle 0x0004
DMI type 4, 32 bytes.
Processor
Socket Designation: PGA 478
Processor Type: Central Processor
Processor Family:
Processor Manufacturer: GenuineIntel
Processor Version: Intel(R) Pentium(R) 4
prev parent reply other threads:[~2003-08-07 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 16:08 Kathy Frazier
2003-08-07 15:10 ` Mike Dresser
2003-08-07 16:40 ` Kathy Frazier
2003-08-07 15:38 ` Herbert Pötzl
2003-08-07 16:57 ` Arjan van de Ven
2003-08-07 19:46 ` Kathy Frazier
2003-08-07 19:43 ` Arjan van de Ven
2003-08-07 21:44 ` Kathy Frazier [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=PMEMILJKPKGMMELCJCIGOEAECEAA.kfrazier@mdc-dayton.com \
--to=kfrazier@mdc-dayton.com \
--cc=arjanv@redhat.com \
--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
all inboxes | Powered by JetHome®