From: Brian Masney <masneyb@onstation.org>
To: Ike Panhc <ike.pan@canonical.com>
Cc: Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ideapad-laptop: Add Lenovo Yoga 910-13IKB to no_hw_rfkill dmi list
Date: Wed, 19 Oct 2016 21:18:14 -0400 [thread overview]
Message-ID: <20161020011814.GA11359@basecamp.onstation.org> (raw)
In-Reply-To: <a848d067-25af-26a8-7f4c-d785b73232c3@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Thu, Oct 20, 2016 at 08:58:53AM +0800, Ike Panhc wrote:
> On 10/12/2016 04:17 PM, Darren Hart wrote:
> > On Tue, Oct 11, 2016 at 07:28:02PM -0400, Brian Masney wrote:
> >> The Lenovo Yoga 910-13IKB does not have a hw rfkill switch, and trying
> >> to read the hw rfkill switch through the ideapad module causes it to
> >> always report as blocked.
> >>
> >> This commit adds the Lenovo Yoga 910-13IKB to the no_hw_rfkill dmi list,
> >> fixing the WiFI breakage.
> >>
> >> Signed-off-by: Brian Masney <masneyb@onstation.org>
> >
> > Thanks Brian,
> >
> > Queued to testing.
> >
>
> Hi Brian,
>
> Could you post output of acpidump and `cat /sys/class/dmi/id/modalias` for record please?
>
> I would like to see if there is anyway to short the growing blacklist.
Hi Ike,
I attached the compressed output from acpidump. Here is the contents
of my /sys/class/dmi/id/modalias:
dmi:bvnLENOVO:bvr2JCN28WW:bd09/09/2016:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA910-13IKB:
Let me know if you need anything else.
Brian
[-- Attachment #2: lenovo-yoga-910-acpidump.txt.bz2 --]
[-- Type: application/octet-stream, Size: 213362 bytes --]
next prev parent reply other threads:[~2016-10-20 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 23:28 Brian Masney
2016-10-12 8:17 ` Darren Hart
2016-10-20 0:58 ` Ike Panhc
2016-10-20 1:18 ` Brian Masney [this message]
2016-10-20 15:46 ` Mika Westerberg
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=20161020011814.GA11359@basecamp.onstation.org \
--to=masneyb@onstation.org \
--cc=dvhart@infradead.org \
--cc=ike.pan@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome