From: Buddy Lucas <buddy.lucas@gmail.com>
To: Dave Jones <davej@redhat.com>,
Brian McGrew <brian@doubledimension.com>,
linux-kernel@vger.kernel.org
Subject: Re: Probing for System Model Information
Date: Tue, 28 Sep 2004 16:23:18 +0200 [thread overview]
Message-ID: <5d6b657504092807233fe32310@mail.gmail.com> (raw)
In-Reply-To: <20040928134705.GA11916@redhat.com>
Works for my Inspiron 5150. Thanks, didn't know that.
Cheers,
Buddy
On Tue, 28 Sep 2004 14:47:05 +0100, Dave Jones <davej@redhat.com> wrote:
> On Tue, Sep 28, 2004 at 06:32:31AM -0700, Brian McGrew wrote:
> > Good morning All!
> >
> > We exclusively ship Dell boxes with our hardware. However, we use several different models, 1400's, 1600's, 2350's, 4600's and so on. I need to write a small program to probe the system for the model information since I don't seem to find it in the logs anywhere.
> >
> > I know the model info is in there somewhere and it's accessible because if I look on the default factory installed version of Windows, it's listed.
> >
> > Does anyone know how to do this or can you point me to one that's already done or some samples?
>
> You can find this info in the DMI tables assuming Dell filled
> them in with sensible data (which they usually do).
>
> dmidecode will read these tables from userspace.
>
> Dave
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-09-28 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 13:32 Brian McGrew
2004-09-28 13:47 ` Dave Jones
2004-09-28 14:06 ` Matt Domsch
2004-09-28 14:23 ` Buddy Lucas [this message]
2004-09-28 13:51 ` Jesper Juhl
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=5d6b657504092807233fe32310@mail.gmail.com \
--to=buddy.lucas@gmail.com \
--cc=brian@doubledimension.com \
--cc=davej@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®