linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Guillermo Bonvehi <gbonvehi@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: dmidecode
Date: Fri, 13 Jul 2007 15:39:00 -0400	[thread overview]
Message-ID: <200707131539.00276.lenb@kernel.org> (raw)
In-Reply-To: <835b805b0707120457l72ba2a5cmb5970418d771dabe@mail.gmail.com>

On Thursday 12 July 2007 07:57, Guillermo Bonvehi wrote:
> As requested on dmesg, I hope it helps you.
> Thanks for all the work you're doing.
> 
> # dmidecode 2.9
> SMBIOS 2.4 present.
> 17 structures occupying 649 bytes.
> Table at 0x000E3810.
..
> System Information
> 	Manufacturer: Hewlett-Packard
> 	Product Name: Presario C500 (GB125LA#AC8)
> 	Version: F.24
> 	Serial Number: CND7150Z69
> 	UUID: 03154D10-DE14-11DB-9A51-0016D4E68708
> 	Wake-up Type: Power Switch
> 	SKU Number: GB125LA#AC8
> 	Family: 103C_5335KV
> 
> Handle 0x0002, DMI type 2, 8 bytes
> Base Board Information
> 	Manufacturer: Hewlett-Packard
> 	Product Name: 30C6
> 	Version: 78.10
> 	Serial Number: CND7150Z69

Thanks, this is because of the acpi_osi=!Linux message?
Did you try acpi_osi=!Linux and notice any difference?

If you send along the output from acpidump, or better yet,
attach it to a bug report (say this one 
http://bugzilla.kernel.org/show_bug.cgi?id=7787

then i can peek at what HP is doing on this box and get a good idea
if they should be on the white-list or on the blacklist.

thanks,
-Len

  reply	other threads:[~2007-07-13 19:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 11:57 dmidecode Guillermo Bonvehi
2007-07-13 19:39 ` Len Brown [this message]
     [not found]   ` <835b805b0707131312x7ea74f3frf4db47a56f07b358@mail.gmail.com>
2007-07-13 20:15     ` dmidecode Guillermo Bonvehi
  -- strict thread matches above, loose matches on Subject: below --
2008-04-22 20:03 dmidecode Mehturt
2008-04-12 13:09 dmidecode Mauricio Mudado
2008-03-02 17:11 dmidecode Miro Jakubovsky
2008-02-10 14:26 dmidecode Mateu Soler
2008-02-10 13:29 dmidecode catworld
     [not found] <184fd4090801170441r6d93157gfa1548b737a796c4@mail.gmail.com>
2008-01-17 12:43 ` dmidecode Yurij Perepelytsia
2008-01-18 19:52   ` dmidecode Len Brown
2008-01-07 13:14 dmidecode "Alexander Dähn"
2008-01-18 20:36 ` dmidecode Len Brown
2008-01-07 11:47 DMIDECODE Cleri Aloisio Azevedo
2008-01-18 20:33 ` DMIDECODE Len Brown
2008-01-06  1:22 dmidecode meister
2008-01-06  1:16 dmidecode meister
2007-12-28 21:01 dmidecode Ulrich Ivens
2007-11-21  9:06 dmidecode Alain Pollidoro
2008-01-18 22:12 ` dmidecode Len Brown
2007-11-19  4:40 dmidecode Ricardo Rivera
2007-11-18 12:56 Dmidecode Piet
2007-11-14  9:08 dmidecode Philippe
2007-11-04 23:01 dmidecode Dimitri Michaux
2007-11-01  5:05 dmidecode Perry G
2007-10-13 17:29 dmidecode Virus Q
2007-10-13  7:31 dmidecode Siegfried Lösch
2007-10-09  8:30 dmidecode Marco De Felice
     [not found] <413515090710060238x4af5f54fsd558841153480b42@mail.gmail.com>
2007-10-06 16:05 ` dmidecode Samae
2007-09-22 11:07 dmidecode Alexander Zabolotny
2007-09-12 11:20 dmidecode Lexington Luthor
2007-09-02 22:41 dmidecode Anne-Simone
2007-08-14  6:24 dmidecode Jason Wood
2007-06-20 22:04 dmidecode Martin Tamme

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=200707131539.00276.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=gbonvehi@gmail.com \
    --cc=linux-acpi@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;
as well as URLs for NNTP newsgroup(s).