From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Renato S. Yamane" <yamane@diamondcut.com.br>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org,
Christopher Desjardins <cddesjardins@gmail.com>
Subject: Re: Lenovo 3000 N100 i8042 problems
Date: Tue, 9 Sep 2008 00:42:55 -0300 [thread overview]
Message-ID: <20080909034255.GB1999@khazad-dum.debian.net> (raw)
In-Reply-To: <48C5EEE4.6090209@diamondcut.com.br>
On Tue, 09 Sep 2008, Renato S. Yamane wrote:
> Daniel Barkalow wrote:
>> Renato S. Yamane wrote:
>>> Henrique de Moraes Holschuh wrote:
>>>> I fell I need to warn you guys that you are likely breaking machines that
>>>> match that DMI info but have a newer BIOS, unless they use different BIOSes
>>>> (not enough data without a full dmidecode output from the other machine).
>>>
>>> dmidecode just from 3000-N100?
>>> Attached a dmidecode from a Lenovo Thinkpad T61.
>>> I have a Lenovo 3000-V200 too. You want a dmidecode from it?
>>
>> It's almost certainly only 3000 series that's interesting; I think they
>> test the Thinkpads with Linux and wouldn't ship with a quirky BIOS
>> there.
>
> Here is the dmidecode from a Lenovo 3000-V200.
> I hope this help something.
> Let me know if you need more info.
Well, does that box suffer either of the issues (breaks either with the
patch or without the patch)?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-09-09 3:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 21:46 Daniel Barkalow
2008-09-01 23:29 ` Jiri Kosina
2008-09-02 0:23 ` Daniel Barkalow
2008-09-02 9:23 ` Jiri Kosina
2008-09-02 12:43 ` Henrique de Moraes Holschuh
2008-09-02 12:51 ` Dmitry Torokhov
2008-09-02 12:43 ` Dmitry Torokhov
2008-09-02 16:16 ` Daniel Barkalow
2008-09-03 14:26 ` Dmitry Torokhov
2008-09-03 17:16 ` Daniel Barkalow
2008-09-03 19:06 ` Dmitry Torokhov
2008-09-03 20:03 ` Jiri Kosina
2008-09-05 0:05 ` Daniel Barkalow
2008-09-05 0:46 ` Dmitry Torokhov
2008-09-05 3:27 ` Daniel Barkalow
2008-09-03 11:50 ` Jiri Kosina
2008-09-03 14:20 ` Dmitry Torokhov
2008-09-03 17:18 ` Daniel Barkalow
2008-09-03 19:07 ` Dmitry Torokhov
2008-09-04 23:57 ` Daniel Barkalow
2008-09-03 21:32 ` Henrique de Moraes Holschuh
2008-09-03 21:36 ` Jiri Kosina
2008-09-03 22:03 ` Daniel Barkalow
2008-09-08 19:41 ` Renato S. Yamane
2008-09-08 19:55 ` Daniel Barkalow
2008-09-09 3:35 ` Renato S. Yamane
2008-09-09 3:42 ` Henrique de Moraes Holschuh [this message]
2008-09-09 13:37 ` Renato S. Yamane
2008-09-08 20:24 ` Henrique de Moraes Holschuh
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=20080909034255.GB1999@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=barkalow@iabervon.org \
--cc=cddesjardins@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=yamane@diamondcut.com.br \
/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®