All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: Islam Amer <pharon@gmail.com>
Cc: Rezwanul_Kabir@dell.com, mjg59@srcf.ucam.org,
	linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: Dell Studio 1555 eject key does not work ( small patch to fix included )
Date: Fri, 11 Jun 2010 08:08:24 -0600	[thread overview]
Message-ID: <4C124358.8020007@canonical.com> (raw)
In-Reply-To: <AANLkTinoWK4uSL2KOhgF-EVWuBhgCeAqWwL9cJKeGRD1@mail.gmail.com>

Islam Amer,

You could try a vanilla stable kernel from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.15.5-lucid/ to see 
if we've borked the dell-wmi code.

rtg

On 06/11/2010 07:28 AM, Islam Amer wrote:
> Rezwanul,
>
> I've updated my bios to A11 and installed a new unmodified kernel. The
> issue still persists that the eject key produces "dell-wmi: Unknown
> key 0 pressed" in the dmesg output and it doesn't work.
>
> It is possible that Ubuntu is including patches to fix stuff. The
> latest patch for the Lucid kernel at
> http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux_2.6.32-22.36.diff.gz
> does include patches that touch wmi and dell-wmi code, but I can't
> find a specific change that would fix this issue.
>
> I might try to selectively apply patches from it and see if it gets fixed.
>
> Thanks.
>
>
> On Fri, Jun 11, 2010 at 3:15 AM,<Rezwanul_Kabir@dell.com>  wrote:
>> Islam Amer
>>
>>    Please try the new BIOS A11 and eliminate any potential BIOS issues. The BIOS team confirmed that
>>    they weren't able to reproduce the issue with Ubuntu 10.04 and A11.
>>
>> Thanks..
>>    --rez
>>
>>
>>
>>
>> Rezwanul Kabir
>> Dell Linux Development
>> 512-725-0766
>>
>>
>>> -----Original Message-----
>>> From: Islam Amer [mailto:pharon@gmail.com]
>>> Sent: Thursday, June 10, 2010 6:52 PM
>>> To: Matthew Garrett
>>> Cc: Kabir, Rezwanul; linux-kernel@vger.kernel.org;
>>> platform-driver-x86@vger.kernel.org; akpm@linux-foundation.org
>>> Subject: Re: Dell Studio 1555 eject key does not work ( small
>>> patch to fix included )
>>>
>>> Hello all,
>>>
>>> My bios version is A08 , I see that A11 was recently released
>>> but the changelog doesn't say much.
>>>
>>> Which is better, upgrade and hope the problem goes away, or
>>> wait until we have a fix that is agreed upon ?
>>>
>>> Thanks.
>>>
>>> On Thu, Jun 10, 2010 at 9:40 PM, Matthew Garrett
>>> <mjg59@srcf.ucam.org>  wrote:
>>>> On Thu, Jun 10, 2010 at 01:36:56PM -0500,
>>> Rezwanul_Kabir@Dell.com wrote:
>>>>> Hi Islam Amer
>>>>>
>>>>>     I got report that "Ubuntu 10.04 + BIOS A11" was tested and the
>>>>> "Eject CD" key is working
>>>>>     as expected. Sorry, I couldn't find any Studio 1555 to
>>> test myself
>>>>> and cannot provide you
>>>>>     with more details.
>>>>>
>>>>>      Also, you may try acpi_osi="Windows 2009" kernel
>>> parameter and see if there is any difference.
>>>>
>>>> That's the default on any kernel that has this support in dell-wmi.
>>>> Rez, could you let me know if the proposed patch breaks the spec in
>>>> ways that are likely to cause problems?
>>>>
>>>> --
>>>> Matthew Garrett | mjg59@srcf.ucam.org
>>>>
>>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
Tim Gardner tim.gardner@canonical.com

  reply	other threads:[~2010-06-11 14:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 21:14 Dell Studio 1555 eject key does not work ( small patch to fix included ) Islam Amer
2010-06-02 21:14 ` Islam Amer
2010-06-02 21:34 ` Matthew Garrett
2010-06-03  1:57   ` Rezwanul_Kabir
2010-06-03  1:57     ` Rezwanul_Kabir
2010-06-03 20:16     ` Islam Amer
2010-06-03 20:16       ` Islam Amer
2010-06-08 10:57       ` Islam Amer
2010-06-08 10:57         ` Islam Amer
2010-06-08 16:33         ` Rezwanul_Kabir
2010-06-08 16:33           ` Rezwanul_Kabir
2010-06-10 18:36         ` Rezwanul_Kabir
2010-06-10 18:36           ` Rezwanul_Kabir
2010-06-10 18:40           ` Matthew Garrett
2010-06-10 23:51             ` Islam Amer
2010-06-10 23:51               ` Islam Amer
2010-06-11  0:15               ` Rezwanul_Kabir
2010-06-11  0:15                 ` Rezwanul_Kabir
2010-06-11 13:28                 ` Islam Amer
2010-06-11 13:28                   ` Islam Amer
2010-06-11 14:08                   ` Tim Gardner [this message]
2010-06-11 14:23                     ` Islam Amer
2010-06-11 14:23                       ` Islam Amer
2010-06-11 18:02                       ` Islam Amer
2010-06-11 18:02                         ` Islam Amer
2010-06-11 18:35                         ` Tim Gardner
2010-06-12  1:26                           ` Islam Amer
2010-06-12  1:26                             ` Islam Amer
2010-06-15 17:23                             ` Rezwanul_Kabir
2010-06-15 17:23                               ` Rezwanul_Kabir
2010-06-15 17:28                               ` Matthew Garrett
2010-06-24 15:09 ` Matthew Garrett
2010-09-06 19:12 ` Kyle McMartin
2010-09-23 18:43   ` [stable] " Greg KH

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=4C124358.8020007@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=Rezwanul_Kabir@dell.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pharon@gmail.com \
    --cc=platform-driver-x86@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.