From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bob Lorenzini <hwm@ns.newportharbornet.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.2.18-25 DELL Laptop Video Problems
Date: Sat, 9 Dec 2000 18:13:51 -0700 [thread overview]
Message-ID: <20001209181351.C15531@vger.timpanogas.org> (raw)
In-Reply-To: <20001209160027.A15007@vger.timpanogas.org> <E144sZd-0005q5-00@the-village.bc.nu>
In-Reply-To: <E144sZd-0005q5-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Dec 09, 2000 at 10:34:30PM +0000
On Sat, Dec 09, 2000 at 10:34:30PM +0000, Alan Cox wrote:
> > Id there a workaround for this for DELL laptops. Frame buffer needs
> > to be enabled because you don't really know what system you are on
> > until after it installs, and the X probing stuff needs it enabled in
> > order to properly detect the hardware. Any ideas?
>
> Hard to be sure. Without knowing precisely which board they have and which
> options you used I can't guess which code path changed
I will get this information on Monday when the testing person at Canopy
is in. We wer testing with their equipment. I'll get you the info.
Jeff
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-10 0:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 22:49 2.2.18-25 DELL Laptop Video Problems Jeff V. Merkey
2000-12-09 22:03 ` Bob Lorenzini
2000-12-09 22:29 ` Alan Cox
2000-12-09 23:00 ` Jeff V. Merkey
2000-12-09 22:16 ` Bob Lorenzini
2000-12-10 1:12 ` Jeff V. Merkey
2000-12-09 22:34 ` Alan Cox
2000-12-10 1:13 ` Jeff V. Merkey [this message]
2000-12-10 16:49 ` Dominik Kubla
2000-12-10 22:50 ` Jeff V. Merkey
2000-12-11 7:26 ` Dominik Kubla
2000-12-11 18:11 ` Jeff V. Merkey
2000-12-13 0:34 ` Dominik Kubla
2000-12-13 1:41 ` Jeff V. Merkey
-- strict thread matches above, loose matches on Subject: below --
2000-12-14 2:29 Petr Konecny
2000-12-14 7:20 ` Dominik Kubla
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=20001209181351.C15531@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hwm@ns.newportharbornet.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