From: Dave Jones <davej@codemonkey.org.uk>
To: Nicolas Turro <Nicolas.Turro@sophia.inria.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: any brand recomendation for a linux laptop ?
Date: Thu, 16 Jan 2003 11:38:25 +0000 [thread overview]
Message-ID: <20030116113825.GB21239@codemonkey.org.uk> (raw)
In-Reply-To: <200301161100.45552.Nicolas.Turro@sophia.inria.fr>
On Thu, Jan 16, 2003 at 11:00:45AM +0100, Nicolas Turro wrote:
>
> Hi,
> I am software engineer at a french research institute, in charge of the linux
> support on about 600 computers. I am looking for laptops whith linux
> support/certification. I couln't find any recent laptop model on your
> certification page. Would you recomend me any brand of computer ?
> We curently buy Compaq Evos laptops, but enabling linux on those laptops
> is terrible :
> - power management seems to be ACPI only (which linux barely supports)
> - sound is hard or impossible to setup correctly.
I have an Evo 1015v, which is a bit of a pain to get working.
You need a very recent kernel just to be able to boot the thing, or
it'll lock up during hardware detection. Installer kernels typically
need to be booted with 'nomce', or probing causes a machine check.
The ATi Xserver locks up with a pretty display of garbage, (use
the vesa driver). Sound is currently not working afaik.
Power management: ACPI worked on it. Up until recently. Latest
2.5 seems to lock up very early in the boot.
Native Athlon Powernow support for cpufreq I'm working on, and am
making progress. IDE is a bit hit and miss. It works, but it's
no screamer in the performance dept. (Likely because no-one has
the relevant info from ATi on their south bridge).
AGP support is also lacking due to missing docs. DRI support
for that onboard Radeon mobility is afaik also missing.
Vesafb works.
So.. it's not that bad when you know the pitfalls, and it gets a good
3hrs or so on battery. (Which is pretty good for a 1300MHz CPU & large
display).
The key to why this one was such a pain was very likely the
"Designed for Windows XP" logo stuck to it.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-01-16 11:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 10:00 any brand recomendation for a linux laptop ? Nicolas Turro
2003-01-16 10:41 ` jw schultz
2003-01-16 14:14 ` Andrew Walrond
2003-01-16 14:40 ` Larry McVoy
2003-01-16 15:37 ` Jan-Benedict Glaw
2003-01-16 15:40 ` Larry McVoy
2003-01-16 15:56 ` K.R. Foley
2003-01-17 3:38 ` daveman
2003-01-17 19:32 ` Panu Matilainen
2003-01-18 22:59 ` Jan-Benedict Glaw
2003-01-18 23:08 ` J.A. Magallon
2003-01-16 16:14 ` Daniel Egger
2003-01-16 17:18 ` Richard B. Johnson
2003-01-17 13:54 ` Henning P. Schmiedehausen
2003-01-18 11:31 ` Daniel Egger
2003-01-17 16:17 ` Gianni Tedesco
2003-01-18 10:49 ` Daniel Egger
2003-01-23 13:19 ` Pavel Machek
2003-01-24 17:01 ` Gianni Tedesco
2003-01-26 23:26 ` Daniel Egger
2003-01-27 10:23 ` Gianni Tedesco
2003-01-16 16:05 ` Matthew J. Fanto
2003-01-16 11:38 ` Dave Jones [this message]
2003-01-28 16:00 ` Serguei Miridonov
2003-01-30 16:30 ` Hirling Endre
2003-01-30 17:41 ` Serguei Miridonov
2003-01-30 18:20 ` Alan Cox
2003-01-16 13:32 ` Tim Walberg
2003-01-16 13:45 ` Ducrot Bruno
2003-01-16 16:32 ` Kent Borg
2003-01-16 18:19 ` Andreas Jellinghaus
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=20030116113825.GB21239@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=Nicolas.Turro@sophia.inria.fr \
--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