From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Compaq Presario 2100 (2133AC)
Date: Thu, 3 Jul 2003 12:53:19 +0200 [thread overview]
Message-ID: <20030703105319.GA832@enigma.daemon.sh> (raw)
In-Reply-To: <3F0306B3.4070803-Pm7dQxmfFcgpAS55Wn97og@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
hi andrew...
* Andrew Eager <andrew.eager-Pm7dQxmfFcgpAS55Wn97og@public.gmane.org> [2003-07-03 09:35 +0200]:
>
> I have just got a Compaq Presario 2100 (2133AC or DF975A) and found that
> the 2.4.21 kernel just hung when booting.
> After a day of reading howtos and learning how to use the iasl compiler
> (& language... yuk), I have managed to get the machine to work by:
> - Getting original DSL, debug & recompile
> - Removing the "PTLTD" from blacklist.c (not sure if this is right or not)
> - Loading the AML code from initrd.
>
> I now have everything working **except** that running hwclock will cause
> the kernel to crash.
> (I have to comment hwclock out of rc.sysinit in order for it to boot)
>
> Any ideas where to look?
> Assuming I get this thing to work, any use providing the new dsl code to
> the list?
you might have a look at http://acpi.sourceforge.net/dsdt/view.php?id=76
and compare your DSDTs and perhaps update that one or upload your own.
cheers,
sebastian
--
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-03 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 16:22 Compaq Presario 2100 (2133AC) Andrew Eager
[not found] ` <3F0306B3.4070803-Pm7dQxmfFcgpAS55Wn97og@public.gmane.org>
2003-07-02 18:15 ` liste-9nAOAgdJVo4b1SvskN2V4Q
2003-07-03 10:53 ` Sebastian Henschel [this message]
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=20030703105319.GA832@enigma.daemon.sh \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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