From: Anders Karlsson <anders@trudheim.com>
To: Martin List-Petersen <martin@list-petersen.dk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Centrino
Date: 02 May 2003 09:53:08 +0100 [thread overview]
Message-ID: <1051865588.3599.20.camel@marx> (raw)
In-Reply-To: <1051860638.24115.13.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
On Fri, 2003-05-02 at 08:30, Martin List-Petersen wrote:
> I've got the Dell Latitude D600 (Centrino, ATI Radeon Mobility 9000 32
> MB)
The X31 has an ATI Mobility Radeon as well, but I don't think it is a
9000. I will double check that when I get home tonight though.
> The Wlan card is unsupported yet (if you've got that). The AGP drivers
> of the Kernel work fine (radeon driver loads without complaining) on
> 2.4.21-rc1. X needs a tweak, since the Radeon 9000 first will be
> supported in 4.3.0. I've started documenting my setup at
> http://www.marlow.dk/dell_d600
I do have the Wlan card and I e-mailed Scott McLaughlin about it. His
response at the time was that Intel was still pondering what they would
do about the drivers. I assume that a gentle stream of plesant e-mails
to the appropriate place at Intel asking nicely for the drivers could
result in the drivers coming available.
The SuSE 2.4.20 kernel does not appear to get along with the X31's
graphics card. I will grab the latest 2.4.21-* kernel and give that a
try. Oh, and the GATOS drm drivers had a decidedly negative impact when
I tried them. I stopped X, removed radeon.o, copied the new radeon.o in
place, started X and experienced a hard hang. Interesting side-effect.
I have bookmarked that page, and I will look in on it now and then. I
should perhaps perform similar documentation for the X31 in case others
try to get Linux working on one.
> A lot of the PCI devices are still unknown though (Host Bridge, PCI
> Bridge, ISA Bridge, IDE, CardBus Bridge) on lspci
Have you seen things like 'hdparm -d1 -X69' failing and telling you that
the actions fail and/or are not allowed? Would you agree that this could
be a side-effect of things you listed not being known to the kernel?
Regards,
/Anders
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-05-02 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 4:53 Centrino Anders Karlsson
2003-05-02 7:30 ` Centrino Martin List-Petersen
2003-05-02 8:53 ` Anders Karlsson [this message]
[not found] ` <20030502085720.GA629@localhost.localdomain>
2003-05-02 15:31 ` Centrino Anders Karlsson
2003-05-02 15:46 ` Centrino Balram Adlakha
2003-05-02 16:03 ` Centrino Anders Karlsson
2003-05-02 22:09 ` Centrino dean gaudet
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 18:32 centrino Jeffrey Baker
2003-05-03 15:21 ` centrino Alan Cox
2003-05-03 20:29 ` centrino Anders Karlsson
2003-05-02 20:05 centrino Grover, Andrew
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=1051865588.3599.20.camel@marx \
--to=anders@trudheim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@list-petersen.dk \
/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