All of lore.kernel.org
 help / color / mirror / Atom feed
From: AnMaster <anmaster@tele2.se>
Cc: linux-acpi@vger.kernel.org
Subject: Re: DSDT problems with Asus K8V-X SE
Date: Sun, 06 Jan 2008 11:07:06 +0100	[thread overview]
Message-ID: <4780A84A.6090903@tele2.se> (raw)
In-Reply-To: <200801060037.24499.carlos@strangeworlds.co.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Carlos Corbacho wrote:
> On Saturday 05 January 2008 16:58:50 AnMaster wrote:
>> My problem is a broken DSDT, I have tried to fix it, but I don't know if I
>> did it the right way, nor how to solve the warning that remains when the
>> errors are gone.
> 
> What exactly is broken about your DSDT that requires you to 'fix' it? 
> 
> Yes, lots of vendor DSDTs won't compile with the Intel compiler - this is 
> because the Microsoft compiler is far more 'generous' than Intel's, and will 
> allow a lot of spec breaking rubbish in.
> 
> However, the ACPI interpreter in Linux can handle most of these just fine; and 
> if it can't, then that's a bug that needs to be fixed in Linux (since Linux 
> should be able to handle unmodified MS compiled DSDTs out of the box).
> 
> -Carlos

I get lots of lock ups (no kernel oopes or other useful info, just everything locks up) that goes
away when I disable ACPI. Someone on IRC said that I should try to fix the DSDT to see if that helps.

Regards,

Arvid Norlander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHgKhIWmK6ng/aMNkRCp7zAKDDEn8Deif0QuW6v8IP42VS/2fLuwCfRG9M
QYCXQ3eJrwj+gw2O7Kaydso=
=xOEK
-----END PGP SIGNATURE-----

      reply	other threads:[~2008-01-06 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 16:58 DSDT problems with Asus K8V-X SE AnMaster
2008-01-06  0:37 ` Carlos Corbacho
2008-01-06 10:07   ` AnMaster [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=4780A84A.6090903@tele2.se \
    --to=anmaster@tele2.se \
    --cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.