From: Joseph Pingenot <trelane@digitasaru.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
"Brown, Len" <len.brown@intel.com>,
bluefoxicy@linux.net, linux-kernel@vger.kernel.org
Subject: Re: ACPI -- Workaround for broken DSDT
Date: Tue, 17 Feb 2004 21:32:23 -0600 [thread overview]
Message-ID: <20040218033220.GA6756@digitasaru.net> (raw)
In-Reply-To: <20040217114755.GA392@elf.ucw.cz>
>From Pavel Machek on Tuesday, 17 February, 2004:
>Hi!
>> > For non-vendor supplied solutions, you might also follow the DSDT link
>> > here: http://acpi.sourceforge.net/
>> Len, this is a really good idea making this available. May I suggest
>> you also have people provide patches between the original and their
>> modified versions, so it's easy for everyone to see what was
>> changed?
>Patches are important because some DSDTs change with memory sizes,
>too, so its safer to patch than to replace.
I'm getting ready to contact Dell (after I work through my work and
homework backlog. Ugh).
Firt off, how do I determine what all is broken in the DSDT/BIOS? I know
that the kernel refuses to use the APIC due to a 'broken BIOS'
(Feb 16 14:38:31 petrus Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC.)
(Anyone know what I need to ask Dell to do to fix this?) I also know
that the fan isn't reported in ACPI, and that I've not gotten it to
suspend to RAM successfully (I've not gotten it to suspend to disk
successfully either, but I think that's due to software and/or my
issues, not the BIOS/DSDT).
Also, any pointers on *how* to ask? The above should cover the what;
who's successfully gotten a vendor (esp. Dell) to issue a fixed BIOS
and/or DSDT, and how did you go about it?
Thanks!
-Joseph
--
Joseph===============================================trelane@digitasaru.net
Graduate Student in Physics, Freelance Free Software Developer
next prev parent reply other threads:[~2004-02-18 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 4:33 ACPI -- Workaround for broken DSDT Brown, Len
2004-02-02 14:38 ` Matt Domsch
2004-02-17 11:47 ` Pavel Machek
2004-02-18 3:32 ` Joseph Pingenot [this message]
2004-02-03 1:03 ` Joseph Pingenot
2004-02-03 1:32 ` Stian Jordet
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 7:22 Brown, Len
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB5C@hdsmsx402.hd.intel.com>
2004-02-01 19:53 ` Len Brown
2004-02-02 6:04 ` Joseph Pingenot
2004-01-31 19:39 john moser
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=20040218033220.GA6756@digitasaru.net \
--to=trelane@digitasaru.net \
--cc=Matt_Domsch@dell.com \
--cc=bluefoxicy@linux.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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