All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: linux-kernel@vger.kernel.org
Subject: acpi_backlight=vendor no longer working around buggy laptop from hell
Date: Sat, 27 Jul 2013 13:19:16 -0400	[thread overview]
Message-ID: <51F40114.9060607@opensuse.org> (raw)

Hi:

I have a DELL XPS 15z laptop with the latest BIOS (A12).

This piece of crap have never worked properly without special boot 
parameters. Up to kernel 3.10, passing acpi_backlight=vendor was enough 
to allow the machine to complete boot and be usable.

Now with 3.11 rc2 (also with today's linus tree) unbootable machine 
problem is back.

In the past I spent many hours figuring out workarounds and they go 
_now_ as the following.

Booting with:

"nox2apic" --> machine works, flawless.

"x2apic_phys acpi_backlight=vendor" --> machine works, except for the 
big problem that the laptop keyboard and touchpad are unresponsive, I 
have to plug USB keyboard/mouse to get anything done.

With no boot parameters the machine hangs at random points in the boot 
sequence either:

-Very early at boot and there is no way to retrieve any useful debug 
info. [OR]

- Somehow it looses "connection" with the ATA controller and the 
filesystems cannot be mounted. [OR]

- In very few ocassions, the boot proceeds with no keyboard or touchpad 
then the iwlwifi wireless card does something stupid (firmware error...)

The only possible hint in the logs I could ever find is:

[    3.844586] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS


I tried in the past to obtain any debug information, with no luck.

Help is appreciated to get to the bottom of the problem. ;)



             reply	other threads:[~2013-07-27 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 17:19 Cristian Rodríguez [this message]
2013-07-29  1:05 ` acpi_backlight=vendor no longer working around buggy laptop from hell Aaron Lu
2013-07-29  1:05   ` Aaron Lu
2013-07-29  1:28   ` Cristian Rodríguez

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=51F40114.9060607@opensuse.org \
    --to=crrodriguez@opensuse.org \
    --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 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.