ideapad_laptop.mod not fixed for all models in latest release

Bug #1341296 reported by wyatt earp
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Fix Released
Medium
Unassigned
Utopic
Fix Released
Medium
Unassigned

Bug Description

The fix for the ideapad_laptop having issues with the wireless is not complete for all lenovo yoga laptops. This release:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324095

Includes the fix to linux-3.16.0/drivers/platform/x86/ideapad-laptop.c around lines here:

--- BEGIN ORIGINAL PATCH ---

@@ -819,6 +821,19 @@
  }
 }

+/* Blacklist for devices where the ideapad rfkill interface does not work */
+static struct dmi_system_id rfkill_blacklist[] = {
+ /* The Lenovo Yoga 2 11 always reports everything as blocked */
+ {
+ .ident = "Lenovo Yoga 2 11",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
+ DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Yoga 2 11"),
+ },
+ },
+ {}
+};
+
--- END ORIGINAL PATCH ---

The Lenovo Yoga 2 13" models report as "Lenovo Yoga 2" or "Lenovo Yogo 2 Pro" without the size identifier. Fedora has incorporated their version of the patch here:

https://bugzilla.redhat.com/show_bug.cgi?id=1021036

This also affects issue where the same information is shown:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324095

The above needs to be adjusted to include the line:

DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Yoga 2"),
DMI_MATCH(DMI_PRODUCT_VERSION, "Lenovo Yogo 2 Pro"),

Revision history for this message
wyatt earp (wyatt-hackerforhire) wrote :
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1341296

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
wyatt earp (wyatt-hackerforhire) wrote :

Unable to collect this information as there is only a wireless connection on the device and I have no way of performing an apt-get install of python-apport from the live distro (a required dependency). Status is "Confirmed."

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc6-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
GOESSEL Guillaume (guillaume-goessel) wrote :

Hi
I own a Lenovo Yoga 2 13 and it is also affected by this issue
I've found this patch :

tags: added: patch
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Has there been any response from upstream regarding the patch mentioned in comment #5?

tags: added: kernel-da-key trusty
Revision history for this message
GOESSEL Guillaume (guillaume-goessel) wrote :

Message from Hans de Goede (the creator of this patch):

>Yes I've submitted this upstream. But it seems that the platform/x86
>maintainer (Matthew Garret) has not send a pull-req for 3.17
>(yet I hope).
>
>Regards,
>
>Hans

Revision history for this message
wyatt earp (wyatt-hackerforhire) wrote :

Thanks for pushing upstream, does it have an associated commit chain that I can go update the actual kernel bug with?

Revision history for this message
GOESSEL Guillaume (guillaume-goessel) wrote :

I don't really understand what you mean here ^^ (quite new to bug reports)
By commit chain you mean a string chain to ID the commit ?

Revision history for this message
wyatt earp (wyatt-hackerforhire) wrote :

Sorry about that, sometimes the fingers are faster than the brain. "commit chain" is my accidental smashing of two thoughts.

I assumed that by being pushed upstream that it was going to go to either 1) a git/svn commit that is waiting to be folded into the ubuntu kernel package or 2) the email chain / link that people submit patches to when they are trying to get a fix rolled into the linux kernel and not just the kernel maintained by ubuntu.

I was really wonder if there was the latter so I could see if I could close out the linux kernel bug I've filed (trying to keep everything neat and tidy if possible).

Revision history for this message
Kévin Commaille (zekeco) wrote :

The patch has been commited and is now in 3.17-rc1 and I'm using it in 3.16 on my Lenovo Yoga 2 13 so I think you can consider it fixed upstream. A backport for ubuntu 14.04 would be nice though.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

cherry picked from commit ce363c2bcb2303e7fad3a79398db739c6995141b (ideapad-laptop: Change Lenovo Yoga 2 series rfkill handling)

Changed in linux (Ubuntu Utopic):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.3 KiB)

This bug was fixed in the package linux - 3.16.0-11.16

---------------
linux (3.16.0-11.16) utopic; urgency=low

  [ Mauricio Faria de Oliveira ]

  * [Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el
    - LP: #1358920

  [ Peter Zijlstra ]

  * SAUCE: (no-up) mmu_notifier: add call_srcu and sync function for listener to delay call and sync
    - LP: #1361300

  [ Tim Gardner ]

  * [Config] CONFIG_ZPOOL=y
    - LP: #1360428
  * Release Tracking Bug
    - LP: #1361308

  [ Upstream Kernel Changes ]

  * Revert "net/mlx4_en: Fix bad use of dev_id"
    - LP: #1347012
  * net/mlx4_en: Reduce memory consumption on kdump kernel
    - LP: #1347012
  * net/mlx4_en: Fix mac_hash database inconsistency
    - LP: #1347012
  * net/mlx4_en: Disable blueflame using ethtool private flags
    - LP: #1347012
  * net/mlx4_en: current_mac isn't updated in port up
    - LP: #1347012
  * net/mlx4_core: Use low memory profile on kdump kernel
    - LP: #1347012
  * Drivers: scsi: storvsc: Change the limits to reflect the values on the host
    - LP: #1347169
  * Drivers: scsi: storvsc: Set cmd_per_lun to reflect value supported by the Host
    - LP: #1347169
  * Drivers: scsi: storvsc: Filter commands based on the storage protocol version
    - LP: #1347169
  * Drivers: scsi: storvsc: Fix a bug in handling VMBUS protocol version
    - LP: #1347169
  * Drivers: scsi: storvsc: Implement a eh_timed_out handler
    - LP: #1347169
  * drivers: scsi: storvsc: Set srb_flags in all cases
    - LP: #1347169
  * drivers: scsi: storvsc: Correctly handle TEST_UNIT_READY failure
    - LP: #1347169
  * namespaces: Use task_lock and not rcu to protect nsproxy
    - LP: #1328088
  * net: xgene: Check negative return value of xgene_enet_get_ring_size()
  * mm/zbud: change zbud_alloc size type to size_t
    - LP: #1360428
  * mm/zpool: implement common zpool api to zbud/zsmalloc
    - LP: #1360428
  * mm/zpool: zbud/zsmalloc implement zpool
    - LP: #1360428
  * mm/zpool: update zswap to use zpool
    - LP: #1360428
  * ideapad-laptop: Change Lenovo Yoga 2 series rfkill handling
    - LP: #1341296
  * iommu/amd: Fix for pasid initialization
    - LP: #1361300
  * iommu/amd: Moving PPR fault flags macros definitions
    - LP: #1361300
  * iommu/amd: Drop oprofile dependency
    - LP: #1361300
  * iommu/amd: Fix typo in amd_iommu_v2 driver
    - LP: #1361300
  * iommu/amd: Don't call mmu_notifer_unregister in __unbind_pasid
    - LP: #1361300
  * iommu/amd: Don't free pasid_state in mn_release path
    - LP: #1361300
  * iommu/amd: Get rid of __unbind_pasid
    - LP: #1361300
  * iommu/amd: Drop pasid_state reference in ppr_notifer error path
    - LP: #1361300
  * iommu/amd: Add pasid_state->invalid flag
    - LP: #1361300
  * iommu/amd: Don't hold a reference to mm_struct
    - LP: #1361300
  * iommu/amd: Don't hold a reference to task_struct
    - LP: #1361300
  * iommu/amd: Don't call the inv_ctx_cb when pasid is not set up
    - LP: #1361300
  * iommu/amd: Don't set pasid_state->mm to NULL in unbind_pasid
    - LP: #1361300
  * iommu/amd: Remove change_pte mmu_notifier call-back
    - LP: #1361300
  * iommu/amd: Fix device_state reference counting
    - LP: #1361300...

Read more...

Changed in linux (Ubuntu Utopic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.