On Mon, 8 Sep 2008, Renato S. Yamane wrote:

quoted text
> 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. 
The 3000 series only officially supports Windows, and so there can be 
problems (evidently, mine does something odd with the legacy mux, and 
newer ones do something odd with the active mux).

You might want to poke at the quirk in the patch in this thread and see if 
one or the other mode works better, or if they're the same on your 
machines. In any case, neither the patch that got into 2.6.25 nor the 
narrowing patch in this thread would affect either of your machines.

	-Daniel
*This .sig left intentionally blank*
--
unsubscribe notice
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/