[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Anthony Wong]

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in wireless-regdb source package in Xenial:
  Fix Released
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Released

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  ---

  wireless-regdb SRU Justification

  Impact: New regulatory requirements in the EU necessitate updating our
  wireless regulatory database.

  Fix: New upstream release.

  Test Case: Minimal testing would be to reload the regdb (can be done
  with iw built from git or by rebooting) and verifying that you are
  able to change regulatory domains (e.g., sudo iw reg set US; iw reg
  get).

  Regression Potential: Minimal. Biggest risk would be the inability to
  load the new database due to the changes in signing, however testing
  will confirm that appropriate key is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1757422] Re: Fix Runtime PM for r8169

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1757422

Title:
  Fix Runtime PM for r8169

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 stays in D0 even when no ethernet cable is plugged in. This drains
  lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0,
  1.8W when r8169 is in D3. The power saved is substantial.

  [Fix]
  Improved rumtime PM logic to let the device gets suspended (D3) when the
  port is not in used and the link is down.

  [Test Case]
  The chip version is 8168h/8111h.
  Test when no ethernet gets plugged.

  Powertop shows power consumption is roughly 5.5W.
  lspci shows the device is in D0.

  With the patch,
  The power consumption is reduced to 1.8W.
  lspci shows the device is in D3, PME# is correctly enabled.
  Plug ethernet cable can corretly wake up the device.
  Unplug the cable, the device gets suspended to D3 correctly.

  [Regression Potential]
  Medium.
  - r8169 is so ubiquitous, with lots of different chip versions. It's
hard to test all of them.
  - PCI D3 needs system firmware (ACPI) support, this might hit some
plaform bugs.
  - the code is still in v4.16-rc*, so it's not well tested by end users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1825958

Title:
  Screen freeze after resume from S3 when HDMI monitor plugged on Dell
  Precision 7740

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Summary]
  Screen freeze after resume from S3 when HDMI monitor plugged.
  This bug can be reproduced in both AC/DC mode.
  This bug can be reproduced after disabled TLP.

  In kernel log,
  [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13
  [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x08008001
  [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at 
page 81919507, read from 'TC2' (0x54433200) (8)
  [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from 'TC0' (0x54433000) (72)
  [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for 
process Xorg pid 2023 thread Xorg:cs0 pid 2025
  [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x
  [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 
0x0804800C
  [ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at 
page 0, read from '

[Group.of.nepali.translators] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1817518

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Disco:
  Fix Released

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]

[Anthony Wong]

** Changed in: hwe-next
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1818490

Title:
  Intel I210 Ethernet card not working after hotplug [8086:1533]

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  Summary:
  Intel I210 Ethernet card not working after hotplug

  Steps to reproduce:
  1. Power on system with ethernet cable on Intel I210
  2. Check ethernet is workable
  3. Unplug then plug the ethernet cable

  Expected result:
  Intel I210 Ethernet card is working, e.g. IP address acquired automatically 
if configured as DHCP.

  Actual result:
  Intel I210 Ethernet card not working after hotplug. dmesg has following error 
messages instead:
  [ 16.464321] [ cut here ]
  [ 16.464326] PCI PM: State of device not saved by 
igb_runtime_suspend+0x0/0x90 [igb]
  [ 16.464334] WARNING: CPU: 2 PID: 49 at 
/build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 
pci_pm_runtime_suspend+0x175/0x180
  [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel 
irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep 
ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 
snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi 
intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas 
snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd 
sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci 
intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456
  [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect 
i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi 
video
  [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem 
#37-Ubuntu
  [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 
01/14/2019
  [ 16.464369] Workqueue: pm pm_runtime_work
  [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180
  [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282
  [ 16.464372] RAX:  RBX: 8a2557aee0a0 RCX: 0006
  [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490
  [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373
  [ 16.464373] R10:  R11:  R12: 
  [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: 
  [ 16.464374] FS: () GS:8a257c48() 
knlGS:
  [ 16.464375] CS: 0010 DS:  ES:  CR0: 80050033
  [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0
  [ 16.464376] DR0:  DR1:  DR2: 
  [ 16.464376] DR3:  DR6: fffe0ff0 DR7: 0400
  [ 16.464376] Call Trace:
  [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464380] __rpm_callback+0xca/0x210
  [ 16.464381] ? __switch_to_asm+0x40/0x70
  [ 16.464382] ? __switch_to_asm+0x34/0x70
  [ 16.464382] rpm_callback+0x59/0x80
  [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0
  [ 16.464384] rpm_suspend+0x137/0x640
  [ 16.464385] ? __switch_to_asm+0x40/0x70
  [ 16.464386] pm_runtime_work+0x81/0xa0
  [ 16.464388] process_one_work+0x1de/0x410
  [ 16.464389] worker_thread+0x32/0x410
  [ 16.464390] kthread+0x121/0x140
  [ 16.464391] ? process_one_work+0x410/0x410
  [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70
  [ 16.464392] ret_from_fork+0x35/0x40
  [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b 
b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b 
e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53
  [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1818490/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : grou

[Group.of.nepali.translators] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1756700/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759188] Re: [8086:3e92] display becomes blank after S3

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759188

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  [   38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first 
message, retry
  [   38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 
0050 w(1)
  [   38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent 
adapter i915 gmbus dpd
  [   38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
HDMI ID: DP-HDMI ADAPTOR\004 (err 0)
  [   38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode 
adaptor ID: 44 (err 0)
  [   38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 
HDMI) detected (max TMDS clock: 165000 kHz)
  [   38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] 
[CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected

  [Fix]
  This commit pointed out by Timo fixes the issue.

  [Regression Potential]
  Should be low, although the change applies broadly.
  From the patch description, it explains it should be safe.
  > This workaround was designed to minimize the impact only
  > to save the bad case with that link rates. But HW engineers
  > indicated that it should be safe to apply broadly, although
  > they were expecting the DPLL0 link rate to be unchanged on
  > runtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759188/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

[Anthony Wong]

** Changed in: linux (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: hwe-next
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1730544

Title:
  AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  From vendor's suggestion, there are some patches in v4.14-rc6 are
  required to enable the 2 NICs

  417a3ae net: aquantia: Bad udp rate on default interrupt coalescing
  b82ee71 net: aquantia: Enable coalescing management via ethtool interface
  6849540 net: aquantia: mmio unmap was not performed on driver removal
  4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus
  93d87b8 net: aquantia: Fixed transient link up/down/up notification
  5d8d84e net: aquantia: Add queue restarts stats counter
  65e665e net: aquantia: Reset nic statistics on interface up/down

  And to avoid conflict, cherry pick 2 more commits

  3aec641 aquantia: Fix Tx queue hangups
  65e665e net: aquantia: Reset nic statistics on interface up/down

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1730544/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1806818

Title:
  Fix Intel I210 doesn't work when ethernet cable gets plugged

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Plugging ethernet cable cannot wake up Intel I210 when it's runtime
  suspended. It's because the PME is not enabled.

  [Fix]
  PCI core doesn't enable PME because the driver explicitly saves its PCI
  state before runtime suspend routine. Don't save PCI state fixes the
  issue. 

  [Test]
  PME is correctly enabled, and cable plugging starts to work.

  [Regression Potential]
  Minimal. The fix limits to on device, and it's specific to runtime power
  management. Other functionalities are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806818/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742094

Title:
  [16.04][classic] Redpine: wowlan feature doesn't work

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:

   1. Ensure WoWLAN is enabled in BIOS.
   2. Initiate connection to an AP (using nmcli)
   3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
   4. Enter S5/S4/S3 (using poweroff, etc.)
   5. From another computer on the same network run the following command:
  $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)

  Expected result: the device starts/resume

  This bug is only for tracking purporse, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address

[Anthony Wong]

** Changed in: hwe-next
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1785033

Title:
  GRUB needs to support 64-bit efi linear frame buffer address

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Fix Released
Status in grub2-signed source package in Trusty:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2-signed source package in Bionic:
  Fix Released
Status in grub2 source package in Cosmic:
  Fix Released
Status in grub2-signed source package in Cosmic:
  Fix Released

Bug description:
  [Rationale]
  More firmwares support above 4G mmio configureation and the EFI Graphics 
Output Protocol can return a 64-bit linear frame buffer address have been 
implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer 
base to kernel. The Linux kernel has already added support to handle 64-bit 
linear framebuffer address in the efifb driver now. So GRUB2 should support 
64-bit EFI linear frame buffer address.

  [Impact]
  Some machines block booting with firmware/bios implemented 64-bit EFI linear 
frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear 
frame buffer.

  [Test cases]

  Need Bios/Firmware support,
  1) Make sure the machine with the Bios implemented 64-bit EFI linear frame 
buffer address. some machine need to enable above 4G mmio on bios setup menu.
  2) Boot up.

  [Solution]
  A patch has been committed and accepted by maintainer
  
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f

  [Regression Potential]
  Minimal, it's unlikely completing the whole framebuffer address will affect 
those which hasn't used above 32-bits framebuffer address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)

[Anthony Wong]

** No longer affects: linux (Ubuntu Xenial)

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1804588

Title:
  Power consumption during s2idle is higher than long idle (Intel
  SSDPEKKF)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  On new systems that facilitate s2idle, we observed the power consumption 
raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF.

  Short idle: 6
  Long idle: 2
  S2I: 4.8

  [Fix]
  Windows doesn't put nvme to D3 in modern standby, and uses its own APST 
feature to do the power management. To leverage its APST feature during s2idle, 
we can't disable nvme device while suspending, too.
  So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. 
prevent nvme from being disabled when suspending.

  [Test]
  Verified on the new Intel NVMe, it fixes the power consumption issue with no 
regression. And the power consumption decreases to 2.8W during s2idle.

  [Regression Potential]
  Low, the patches only applied to specific nvme module, and from our test, the 
system is still stable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1804588/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

[Anthony Wong]

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
+ 
+ ==
+ 
+ The fix for the root cause of the hang is tracked in bug 1804604.

** Description changed:

  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs
  on boot.
  
  After blacklisting i2c_i801 everything works great again.
  
  I realize that this was a fix for bug 1786574, and that helps some other
  folks out.  I'm not sure what the right fix is but there's got to be
  something that works for everyone.
  
  ==
  
- The fix for the root cause of the hang is tracked in bug 1804604.
+ The fix for the root cause of this hang issue is tracked in bug 1804604.

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1802689

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

  ==

  The fix for the root cause of this hang issue is tracked in bug
  1804604.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1786574

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

[Anthony Wong]

Change linux to Fix Released for the same reason.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1802135

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

[Anthony Wong]

linux/Cosmic  should be Fix Released as the fix is already in 4.18 from
upstream.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1802135

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1796634] Re: [0cf3:e007] Can't turn on BT by Wireless hotkey

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1796634

Title:
  [0cf3:e007] Can't turn on BT by Wireless hotkey

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in Gaming Edition:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The issue has been found on new Dell laptop with DW1820 combo card(BT is 
[0cf3:e007])
  1) Use wireless hotkey to turn off WiFi/BT.
  2) Wait 5 minutes.
  3) Use wireless hotkey to turn on WiFi/BT.
  4) Wifi is back, but BT is still off
  5) Only reboot can recovery the BT state

  [Fix]
  Qualcomm releases a new firmware to fix it.

  [Regression Potential]
  Can't evaluate it, but from our verification and S3 stress test,
  there is no any issues result from the firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1796634/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

[Anthony Wong]

Opened "linux" task for investigating the real root cause of this
regression.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: kmod (Ubuntu)
 Assignee: AaronMa (mapengyu) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1802135

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on
  Lenovo 11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

[Anthony Wong]

I am opening a "linux" task for investigating the real root cause of
this in kernel.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => AaronMa (mapengyu)

** Changed in: kmod (Ubuntu)
 Assignee: AaronMa (mapengyu) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1802689

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1786574

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released
Status in kmod source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1722719] Re: HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1722719

Title:
  HID: multitouch: Correct ALPS PTP Stick and Touchpad devices ID

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Alps touchpad with ID 0x120A + trackpoint will not be used for mass 
production machines.
  Touchpad 0x120A w/o trackpoint still reports it has a trackpoint, this will 
confuse userspace apps.

  [Fix]
  Reverts commit fcaa4a07d2a4b541e91da7a55d8b3331f96d1865, so 0x120A device is 
no longer a MT_CLS_WIN_8_DUAL device.

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  Minimal.
  This patch is for a single device in a specific driver.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1722719/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759088] Re: can't record sound via front headset port on the Dell Precision 3630

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759088

Title:
  can't record sound via front headset port on the Dell Precision 3630

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  The Dell Precision 3630 is a desktop computer, it has only one front headset
  jack on it, after we plug a headset in it, we can't record sound via the
  headset-mic.

  And Realtek told us that "This platform was the fixed type headset only for
  iphone type. Fixed type headset was not run for default headset mode rule.
  It's hardware fixed type solution. Don't need to run software headset mode.
  Hardware layout not support UAJ functions."

  And Realtek submitted this patch to fix this problem.

  [Fix]
  With this patch, the driver only set pin 0x19 as the headset-mic and will not
  call alcxxx_headset_mode init function anymore since the circuit is hardware
  fixed to be iphone-type headset-mic.

  [Test Case]
  Boot up the system, and plug a iphone-type headset, record the sound via
  headset-mic, it can record the sound and sound quality is pretty good.

  [Regression Potential]
  Very low, this patch is only specific to precision 3930 (subsystem id:
  0x10280871 and 0x10280872).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759088/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1732206] Re: nvidia-graphics-drivers deferred DKMS feature does not work in xenial

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1732206

Title:
  nvidia-graphics-drivers deferred DKMS feature does not work in xenial

Status in HWE Next:
  Fix Released
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Zesty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Deferred module build was a feature that worked with Upstart and that was 
never updated to work with systemd.

  [Test Case]

  1) Enter the following command to create the temporary file:
  sudo touch /tmp/do_not_build_dkms_module

  2) Enable the -proposed repository, and install the new "nvidia-384"

  3) Check that DKMS didn't build the module (the "dkms status" will
  give you a clue).

  3) Restart your computer and see if the module is built correctly (you
  should be able to access the desktop session). Check that the module
  is there with the "dkms status" command.

  [Regression Potential]
  Low, as, currently, the feature doesn't work at all with systemd.

  _
  The nvidia-graphics-drivers 
(https://github.com/tseliot/nvidia-graphics-drivers/tree/375-xenial) deferred 
DKMS feature does not work in xenial.

  With upstart, doing a touch of the /tmp/do_not_build_dkms_module file
  indicates to defer building the kernel modules, then install the
  nvidia driver packages, which creates an upstart script to build the
  modules later. Upon reboot the upstart script would then do the DKMS
  build.

  This no longer works in xenial. The code was never updated for the
  transition from upstart to systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1732206/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1728523] Re: QCA6174A XR cannot find any WiFi AP

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1728523

Title:
  QCA6174A XR cannot find any WiFi AP

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  Atheros QCA6174 can't find any WiFi APs and got below message in dmesg

  [   16.158772] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   22.162575] ath10k_pci :02:00.0: could not suspend target (-11)
  [   27.533002] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   33.535958] ath10k_pci :02:00.0: could not suspend target (-11)
  [   38.890790] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   44.893968] ath10k_pci :02:00.0: could not suspend target (-11)
  [   46.358194] i2c_designware i2c_designware.0: controller timed out
  [   47.358231] i2c_designware i2c_designware.0: controller timed out
  [   48.358506] i2c_designware i2c_designware.0: controller timed out
  [   49.566240] i2c_designware i2c_designware.2: controller timed out
  [   50.566862] i2c_designware i2c_designware.2: controller timed out
  [   51.566307] i2c_designware i2c_designware.2: controller timed out
  [   52.670330] i2c_designware i2c_designware.3: controller timed out
  [   53.670775] i2c_designware i2c_designware.3: controller timed out
  [   54.670427] i2c_designware i2c_designware.3: controller timed out
  [   60.326619] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   66.327117] ath10k_pci :02:00.0: could not suspend target (-11)
  [   71.678943] ath10k_pci :02:00.0: failed to enable dynamic BW: -11
  [   77.679084] ath10k_pci :02:00.0: could not suspend target (-11)

  It requires updated firmwares to enable it.

  [Test Case]
  After applying the required firmwares, it can search APs and connect to the 
network.

  [Regression Potential]
  Although the new firmware overwrite the old one, considering it exists in 
linux-firmware git tree and didn't get any update for 3 month, it should be 
good with no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728523/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1731822] Re: system can't detect external microphone with the codec alc274

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1731822

Title:
  system can't detect external microphone with the codec alc274

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  After installing the latest artful kernel (Ubuntu-4.13.0-16.19), and
  boot up the system with this kernel, we plug a headset to the headset
  jack, then open the gnome-sound-setting, but we can not see the
  headset microphone in it, there is only one internal microphone in it,
  as a result we can't record the sound with the headset microphone.

  This Dell machine has audio codec alc274, it needs to apply a fixup
  like ALC269_FIXUP_DELL1_MIC_NO_PRESENCE.

  After applying this fixup in the kernel driver, the headset mic can be
  detected and works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1731822/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1738523] Re: [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1738523

Title:
  [SRU] External HDMI monitor failed to show screen on Lenovo X1 series

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Thinkpad X1 yoga:
  CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, 
stepping: 0xa)
  GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])

  Steps:
  1, Connect an external monitor
  2, Try to switch display modes in mirrored, extended, displayed on external 
or internal.

  [Impact]
  External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon

  [Fix]
  Add a workaround to bypass this TMDS_OE writing on identified laptop models.

  [Test Case]
  Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output
  OK.

  [Regression Potential]
  Low, it limits to ThinkPad specific laptops.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1738523/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1757584] Re: Let headset-mode initialization be called on Dell Precision 3930

[Anthony Wong]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1757584

Title:
  Let headset-mode initialization be called on Dell Precision 3930

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  There is only one audio jack on this machine (codename: zuma-p), so
  there is only one output device (headphone), then the driver will not generate
  auto-mute control on this machine, without auto-mute, the headset-mode
  initialization routine will not be called, as a result, all audio devices
  can't work (output and input). To fix it, add a dummy lineout on this
  machine, then there are two output devices (headphone + lineout), the
  driver will create auto-mute control on this machine finally.

  Due to the patch conflicts, I prepared two patches, one is for artful+oem,
  the other is for bionic.

  [Test Case]
  plug the headset and play or record the sound on this machine, both playing
  and recording work well.

  [Fix]
  one commit from mainline kernel.

  [Regression Potential]
  very low, since this patch only applies to the specific Dell machine 
Precision 3930.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757584/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

[Anthony Wong]

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1756700

Title:
  Ryzen/Raven Ridge USB ports do not work

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Triaged
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1756700/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1758829] Re: speaker can't output sound anymore after system resumes from S3 on a lenovo machine with alc257

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1758829

Title:
  speaker can't output sound anymore after system resumes from S3 on a
  lenovo machine with alc257

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  [Impact]
  After booting up, the speaker works well. If we suspend the machine then 
resume
  it back, the speaker can't output sound, even rebooting can't make the speaker
  work, we need to power off the machine then power up the machine, the speaker
  can work again.

  [Fix]
  We need to add the basic support for the codec alc257 first (0001-xxx.patch),
  then add hooking function for this codec and clear the bit of 15 for register
  0x57 (0002-xxx.patch). Both of these two patches come from mainline kernel.

  [Test Case]
  After booting up the system, suspend the machine, then resume the machine,
  test the speaker, the speaker can output sound. Repeat the testing steps many
  times, the speaker still can work.

  [Regression Potential]
  Very low, since the 1st patch just add the support for a new codec alc257, it
  will not affect other codecs. The 2nd patch just apply a fix for alc257, it
  doesn't affect other codecs too. And both of them come from mainline and
  realtek.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1758829/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759511] Re: Fix an issue that when system in S3, USB keyboard can't wake up the system.

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux-oem (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759511

Title:
  Fix an issue that when system in S3, USB keyboard can't wake up the
  system.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stays at D0 when system is in S3. Unfortunately D0 can't generate PME# 
wakeup event, so USB device can't wake the system.

  [Test]
  Intel NUC can't be waken up by USB keyboard when the system is in S3.
  With the patch, USB keyboard can wake up the system.

  [Regression Potential]
  Low.
  The issue starts appearing from Gemini Lake, older generation hardware 
shouldn't get affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759511/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1763271] Re: [8086:3e92] display becomes blank after S3

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1763271

Title:
  [8086:3e92] display becomes blank after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The display becomes black after S3 with the following error messages.

  dmesg:
  [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at 
link rate = 54, lane count = 4

  Xorg.0.log:
  [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument
  [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, 
tried resetting the current mode. You may be left with a black screen if this 
fails...

  [Fix]
  Looks like link training fallback fails sometimes with eDP, we need this 
commit to fix the issue.

  commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad)
  Author: Manasi Navare 
  Date: Thu Oct 12 12:13:38 2017 -0700

  drm/i915/edp: Do not do link training fallback or prune modes on
  EDP

  [Regression Potential]
  Should be low.
  To avoid conflicts, we introduce 4 commits, I'll try explaining them below

  a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP
     This is the fix commit and the behavior only changes when DP is eDP, it 
does nothing if DP is eDP. Should be fine to not do link training fallback and 
not emit Hotplug Uevent to userspace to start modeset, since its eDP, the 
display is fixed.

  1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp
  7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp
     Above 2 commits do function name renaming only.

  dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available.
     Change the prototype of function "intel_panel_init()" and adding one extra 
argument, should have small impact on the display.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1763271/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1764684] Re: Fix an issue that some PCI devices get incorrectly suspended

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1764684

Title:
  Fix an issue that some PCI devices get incorrectly suspended

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Some PCI device are not power managed by system firmware get runtime 
suspended incorrectly. In this case it's an xHC device, which can't be woken up 
by plugging USB device.

  [Test]
  With the patch, the xHC no longer get put to suspend incorrectly. USB devices 
can work on the xHC now.

  [Fix]
  We need to check if the device is power managed by system firmware, also if 
it supports PME from D3hot.

  [Regression Potential]
  Low.
  It fixes a regression caused by the PM core refactor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1764684/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766197] Re: Update btusb reset-resume quirk to decrease power usage

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766197

Title:
  Update btusb reset-resume quirk to decrease power usage

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  USB reset-resume quirk prevents the device from runtime suspending,
  which increases power usage.

  [Test]
  With the patch, the power consumption decreases 0.5W.
  The tested machine doesn't need the quirk to make btusb work.

  [Fix]
  Update the btusb reset-resume quirk with a DMI based version, which can
  be more specific.

  [Regression Potential]
  Low.
  Everthing is in mainline, and I haven't seen any new report about this
  issue for some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766197/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766398] Re: set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766398

Title:
  set PINCFG_HEADSET_MIC to parse_flags for Dell precision 3630

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On this Dell machine (codename: turtle bay), the microphone always shows up
  in the sound-setting even there is no microphone plugged in.

  [Fix]

  Without this fix, the pin will be regarded as microphone, and the jack name
  is "Mic Phantom", it is always on in the pulseaudio even nothing is plugged
  into the jack. So the UI is confusing to users since the microphone always
  shows up in the UI even there is no microphone plugged.

  After adding this flag, the jack name is "Headset Mic Phantom", then
  the pulseaudio can handle its detection correctly.

  
  [Test Case]
  After booting up the system, and without plugging anything in the audio combo
  jack, there is nothing in the input tab of sound-setting, then plug a headset
  in the jack, the what-did-you-plug-in dialogue pops up, users can select 
headset
  mic from UI, and headset-mic shows up in the sound-setting, we can record 
sound
  via headset-mic

  
  [Regression Potential]
  Very low, since this patch is specific for ALC255_FIXUP_DELL_HEADSET_MIC 
which is
  only used by Dell precision 3630 by now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766398/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1766477] Re: Change the location for one of two front mics on a lenovo thinkcentre machine

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1766477

Title:
  Change the location for one of two front mics on a lenovo thinkcentre
  machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On one of Lenovo thinkcenter machines we have, there are two microphone jacks
  on the front panel, but only one of them can work after we plug a micrphone in
  them.

  [Fix]
  Because two microphones are located in front panels, the alsa driver will 
assign
  the same jack name to them, but pulseaudio can't handle two jacks with the 
same
  name.

  After applying this FIXUP, they will have different mixer name,
  then pulseaudio can handle them correctly.

  
  [Test Case]
  After booting up, plug micrphone into any one of the two audio jacks, the 
microphone
  works very well.

  [Regression Potential]
  Very low, since this patch is specific to the thinkcenter machine with 
subsystem id
  0x17aa3138.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1766477/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1774306

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
  led on them, without this patch, the hotkey and led only works on M810z, if we
  want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
  since they use same codec with same pin conf, we use a better way than adding 
id.

  [Fix]
  With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.

  [Test Case]
  press mic-mute button, then check sound-setting, we found the input will mute 
or
  unmute as users press button, and led will on or off to indicate the input 
status.

  [Regression Potential]
  Very low, through the strictly match the pin conf, codec id and vendor id, 
this
  fix only apply to M810z, M820z and M920z.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1774306/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1771919] Re: Support Realtek Bluetooth [0bda:c024]

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771919

Title:
  Support Realtek Bluetooth [0bda:c024]

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  The driver rtk-btusb is already in ubuntu/rtl8821ce-bt. All we need to
  support this device is to add the ID to the driver and blacklist it in
  btusb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1771919/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1728547

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1746661] Re: [linux-oem] Use I2C transport for touchpad on Precision M5530

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746661

Title:
  [linux-oem] Use I2C transport for touchpad on Precision M5530

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact] 
  Touchpad on Precision M5530 uses PS/2 instead of I2C as its transport.

  [Test Case]
  The touchpad binds to psmouse instead of i2c_hid.
  With the patch, the touchpad uses i2c_hid instead.

  [Fix]
  LKML Link: https://lkml.org/lkml/2018/1/30/963
  The de facto standard, Windows, parse its DSDT as a term list. The DSDT
  table on Precision M5530 also designed that way, hence we should just
  respect that.
  Add a new quirk for this specific machine.
  I'll backport the patch for stable releases once it's upstreamed.

  [Regression Potential]
  Low. This fix is limited to XPS 15 9570/Precision M5530. Also it's the
  "correct" way to do for this machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1746661/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Anthony Wong]

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1750947

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736317] Re: ath10k: enhance rf signal strength

[Anthony Wong]

** Changed in: hwe-next
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736317

Title:
  ath10k: enhance rf signal strength

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware
  QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power
  to set transmission power. The tx power was about -50dbm, after applying this
  change, it become -32dbm.

  Signed-off-by: Alan Liu 
  Signed-off-by: Kalle Valo 

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7

  This fix already included in Zesty/Artful/Bionic kernels.

  This bug is for tracking purposes only, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1736317/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1747336] Re: need linux-firmware for rtl bt ( 0bda:b023)

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1747336

Title:
  need linux-firmware for rtl bt ( 0bda:b023)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==

  [Test Case]
  boot the system and connnect the bt devices, all works well

  [Fix]
  Backport the uptream patch

  [Regression Potential]
  This only adds new firmware files, so no potential for regressions with 
already working hardware.

  ---

  rtl8822b_config.bin
  rtl8822b_fw.bin

  in the /lib/firmware/rtl_bt/

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1747336/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1734278

Title:
  Grub2 cannot boot up when 8254 time function disable

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  New
Status in debian-installer source package in Artful:
  New
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2-signed source package in Bionic:
  Fix Released
Status in grub2 package in Debian:
  Fix Released
Status in grub2 package in Fedora:
  Fix Committed

Bug description:
  [Impact]
  Some Intel SoC-based systems.

  [Test cases]
  1) Boot an affected system.

  [Regression potential]
  Some systems may rely on the current state of the timer selection in order to 
be able to boot successfully, or to catch key presses before the end of a 
timeout in the menu.
  These systems may then fail to boot correctly, stuck in a timeout of crashing 
in grub. The new default, pmtimer, should be available on all ACPI-capable 
systems without being power-gated such as for the PIT, so the impact of this 
possible regression is minimal.

  ---

  Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer 
function is disabled.
  "8254 clock gating" is provided to disable 8254 timer to get rid of legacy 
and save power. The platforms with the firmware which disable the 8254 timer 
will fail to boot up and block on grub2 which uses the 8254 timer to calibrate 
the TSC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1732056] Re: Touchpad stops working after a few seconds in Lenovo ideapad 320

[Anthony Wong]

** Changed in: hwe-next
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1732056

Title:
  Touchpad stops working after a few seconds in Lenovo ideapad 320

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  === SRU Justifications ===

  [Impact]
  Touchpad freezes after a brief usage.

  [Fix]
  Quote from the commit log:
  "The stale cached value written at the final stage undoes the masking.
  Fix this by re-reading the register before clearing the interrupt.

  I also spotted that the interrupt-clearing code can race against
  amd_gpio_irq_mask() / amd_gpio_irq_unmask(), so add locking there.
  Presumably this race was leading to the loss of interrupts."

  [Test Case]
  Touchpad no longer freezes on ideapad 320-15ABR, a new Dell Latitude and
  a new Dell Inspiron.

  [Regression Potential]
  Low. It limits to AMD laptops

  === Original Bug Report ===

  I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
  stops working a few seconds after I log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rebeca 1440 F pulseaudio
   /dev/snd/controlC0:  rebeca 1440 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 20:03:41 2017
  InstallationDate: Installed on 2017-09-22 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
  MachineType: LENOVO 80XS
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1e55f665-bd98-4113-9ae8-ec766bfc424f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-11-14 (0 days ago)
  dmi.bios.date: 05/22/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5QCN16WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR:
  dmi.product.family: ideapad 320-15ABR
  dmi.product.name: 80XS
  dmi.product.version: Lenovo ideapad 320-15ABR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1732056/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1744041] Re: Firmware upgrade interface for CAC Reader BCM58102

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1744041

Title:
  Firmware upgrade interface for CAC Reader BCM58102

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  To support firmware upgrade for CAC Reader BCM58102, besides the user
  space tool, a kernel module is required to implement the interface for
  user space tool to work on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1744041/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1748807] Re: headset mic can't be detected on two Dell machines

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1748807

Title:
  headset mic can't be detected on two Dell machines

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==

  
  [Test Case]
  plug the headset and record the sound

  [Fix]
  two upstream commits

  [Regression Potential]
  low, since the 0001-xxx.patch just adds vendor id to existing driver to let
  them support headset mode, it doesn't change existing functions, the 
0002-xxx.patch
  adds a group of pin definition, it doesn't change existing funcitons too.

  Hui Wang (1):
ALSA: hda - Fix headset mic detection problem for two Dell machines

  Kailang Yang (1):
ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289

   sound/pci/hda/patch_realtek.c | 27 +++
   1 file changed, 27 insertions(+)

  
  ---

  One machine is with the codec alc289, the other one is with the codec
  alc256.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748807/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755954] Re: external mic not work on Dell OptiPlex 7460 AIO

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755954

Title:
  external mic not work on Dell OptiPlex 7460 AIO

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  == SRU Justification ==
  We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't
  detect external mic and can't record sound via external mic. After applying
  the fixup of ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, the problem can be fixed.

  == Fix ==
  40e2c4e5("iALSA: hda/realtek - Add headset mode support for Dell laptop")

  == Regression Potential ==
  very low, since this patch only applies to specific Dell machines which have 
subsystem id: 1028084b and 1028084e.

  
  == Test Case ==
  plug the headset and record the sound on this machine, we can see the
  external mic in the sound-setting and can record sound through this mic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1755954/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1754216] Re: Display screen blinks on black screen periodically on some wyse system

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1754216

Title:
  Display screen blinks on black screen periodically on some wyse system

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  Screen will blink on black screen periodically when connecting with 4K
  monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1754216/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1786574] Re: remove i2c-i801 from blacklist

[Anthony Wong]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1786574

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  New
Status in kmod source package in Xenial:
  New
Status in kmod source package in Bionic:
  New
Status in kmod source package in Cosmic:
  New

Bug description:
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742090] Re: Redpine: Wifi/BT not functioning after s3 resume

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742090

Title:
  Redpine: Wifi/BT not functioning after s3 resume

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  System cannot be waked by wowlan, but sometimes works.
  When the wowlan not works and system waked by other wakeup sources, after 
resume the wifi and BT would not functioning until reload driver.

  The driver/FW info:
  [ 395.217187] ven_rsi_91x:  RSI Version Info ==
  [ 395.217188] ven_rsi_91x: 
  [ 395.217192] ven_rsi_91x: FW Version : 1.5.4
  [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2
  [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL]
  [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps
  [ 395.217202] ven_rsi_91x: 

  Kernel version: 4.4.0-98-generic
  Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58
  BIOS version: 01.00.05 (Also tested with 01.00.03)
  Tested SKU: T, Media, GPA

  The reproduce steps:
  1. Enable Wowlan and Wol in BIOS
  2. Boot up Ubuntu core
  3. Connect to Wifi AP
  $ nmcli d wifi connect  password 
  4. Enable wowlan
  $ sudo iw phy phy0 wowlan enable magic-packet
  5. Enter suspend or hibernate
  $ sudo systemctl suspend
  or
  $ sudo systemctl hibernate
  6. Send wake signal from another machine
  # wakeonlan 
  or
  # sudo etherwake 
  7. If system not waked, try to wol or other wake source
  # wakeonlan 
  8. After resume, check the wifi/BT function, but not functioning.
  $ nmcli dev
  DEVICE TYPE STATE CONNECTION
  eth0 ethernet connected Wired connection 1
  wlan0 wifi disconnected --
  eth1 ethernet unavailable --
  cdc-wdm0 gsm unavailable --
  lo loopback unmanaged --
  $ nmcli dev wifi rescan
  $ nmcli dev wfii list
  No wifi APs found

  $ sudo bluetoothctl
  [NEW] Controller 00:23:A7:EA:65:64 0225399 [default]
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  The not functioning issue can be fixed by reload driver.
  Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still 
functioning which could be the FW is reloaded by driver.

  This bug is only for tracking purporse, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742090/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1759303] Re: Update Aquantia driver to fix various issues

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759303

Title:
  Update Aquantia driver to fix various issues

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  According to commit log, there are lots of issues got fixed for Aquantia 
driver since v4.13.

  [Test]
  It's a request from costumer.
  Unless Aquantia provides a reproducer, we need Aquantia to verify it.

  [Fix]
  Update Aquantia driver to 2.0.2.1, basically keep the driver in sync with 
Linux kernel v4.16.

  [Regression Potential]
  Low. The driver is the same one as in v4.16, so it should be well tested by 
Aquantia.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1759303/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in Dell Sputnik:
  New
Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  UVC1.5 Realtek webcam on XPS 9370 does not work.

  [Test]
  Both the bug reporter and I can confirm the patch from Realtek works.

  [Fix]
  Use correct version control length for UVC1.5.

  [Regression Potential]
  Low. This only affects UVC1.5 webcams, which is quite rare in the wild.

  ===Original Bug Report===
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1770565

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1770565/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1752507] Re: add i915/glk_dmc_ver1_04.bin

[Anthony Wong]

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1752507

Title:
  add i915/glk_dmc_ver1_04.bin

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact: New firmware is needed to fix issues with S3 for i915 on
  Geminilake hardware.

  Fix: Add the mising firmware.

  Test Case: Test S3 on affected hardware.

  Regression Potential: Limited as the firmware is only loaded for
  specific hardware. Regressions are possible, but none are known, and
  the new firmware does fix a known problem.

  ---

  Intel Gemini Lake needs DMC firmware to fix some S3 issues on xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1752507/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1725154] Re: mwifiex cannot connect to wifi AP when keeping wireless connection idle for more than 60 seconds

[Anthony Wong]

Bionic kernel has the fix already.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux (Ubuntu Artful)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1725154

Title:
  mwifiex cannot connect to wifi AP when keeping wireless connection
  idle for more than 60 seconds

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  Issue happens every time we get connected to any WPA network and stay
  idle for more than 60 seconds.

  We are working with upstream for a real fix:
  https://www.spinics.net/lists/linux-wireless/msg167017.html, please
  don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1725154/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Anthony Wong]

** Changed in: hwe-next
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in wireless-regdb source package in Xenial:
  Fix Released
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in wireless-regdb source package in Bionic:
  Fix Released

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  ---

  wireless-regdb SRU Justification

  Impact: New regulatory requirements in the EU necessitate updating our
  wireless regulatory database.

  Fix: New upstream release.

  Test Case: Minimal testing would be to reload the regdb (can be done
  with iw built from git or by rebooting) and verifying that you are
  able to change regulatory domains (e.g., sudo iw reg set US; iw reg
  get).

  Regression Potential: Minimal. Biggest risk would be the inability to
  load the new database due to the changes in signing, however testing
  will confirm that appropriate key is present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1755705] Re: CFL systems are not responsive to TB16 DP/HDMI (un)plugging event.

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1755705

Title:
  CFL systems are not responsive to TB16 DP/HDMI (un)plugging event.

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  CFL systems do not respond to Dell TB16 Dock DP/HDMI plugging event.

  [Test]
  Connect Dell TB16 to a CFL system and Enable runtime PM. DP/HDMI ports
  on TB16 do not function. 

  [Fix] 
  Don't disable AUX IO power well.

  [Regression Potential]
  Low. These patches are in upstream for a while and I don't see any new
  commits try to fix them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1755705/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Anthony Wong]

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Xenial)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Xenial)
 Assignee: Anthony Wong (anthonywong) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Bionic)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  In Progress
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.

  [Regression Potential]
  As this is a new file, no regression should happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Anthony Wong]

** Changed in: crda (Ubuntu Xenial)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

  == SRU Justification for crda ==
  [Impact]
  We need crda to include Seth Forshee's public key to support wireless-regdb's 
new format.

  [Test Case]
  Check the key is installed at /lib/crda/pubkeys/sforshee.key.pub.pem.

  [Regression Potential]
  As this is a new file, no regression should happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

[Anthony Wong]

** Also affects: crda (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: crda (Ubuntu)
   Status: New => Invalid

** Changed in: crda (Ubuntu Bionic)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769980

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in crda package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in crda source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  New
Status in wireless-regdb source package in Xenial:
  New
Status in crda source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in wireless-regdb source package in Bionic:
  New

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

  ---
  == SRU Justification for linux-firmware ==
  [Impact]
  Intel released these firmware updates to support the new ETSI 5GHz Adaptivity 
Requirement, OEM has to meet it in order to ship.

  [Test Case]
  Check dmesg to confirm the correct firmware is loaded, make sure the revision 
is correct, and check wifi can functions properly.

  [Regression Potential]
  It is possible that there is regression introduced by Intel's firmware, so 
should make sure wifi still works properly after the new firmware is used. We 
have verified the new firmwares of 7260 and 7265D on 4.4
  and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions 
and will need to confirm with subsequent driver changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1769980/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1752044] Re: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive)

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1752044

Title:
  Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio
  Emissions Directive)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: New ath10k firmware is needed for compliance with CE-RED.

  Fix: Updated firmware files.

  Regression Potential: This update has been in upstream linux-firmware
  for a while now. While regressions are possible, the firmware should
  have seen a lot of use by now.

  ---

  To comply with CE-RED (Radio Emissions Directive),
  ath10k/QCA6174/hw3.0/board-2.bin and
  ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated.

  The commits are:

  commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update board-2.bin

  Signed-off-by: Kalle Valo 

  commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update firmware-6.bin to
  WLAN.RM.4.4.1-00079-QCARMSWPZ-1

  Signed-off-by: Kalle Valo 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1752044/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1734243] Re: Intel 9260/9462/9560 firmware support

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1734243

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux-firmware source package in Zesty:
  Won't Fix
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734243/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1762693

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  115.022823]

[Group.of.nepali.translators] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1745081/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1727228] Re: ath9k can't connect to wifi AP

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727228

Title:
  ath9k can't connect to wifi AP

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  iwlist scan can search the available wifi APs, but can't get connected.

  On new Intel platforms like ApolloLake, legacy interrupt mechanism
  (INTx) is not supported, so WLAN modules are not working because
  interrupts are missing.

  The affected and listed platforms are
  Dell Inspiron 24-3460
  Dell Inspiron 14-3473
  Dell Inspiron 3472
  Dell Inspiron 3576
  Dell Vostro 3262
  Dell Vostro 15-3572
  Dell Vostro 3578

  [Fix]
  Qualcomm provided a MSI patch for ath9k, and it fixes the issue.

  [Test Case]
  Tested on the machines mentioned above, and they all work well.

  [Regression Potential]
  There shouldn't  be any regression potential. These are newly enabled 
machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on 
such machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1727228/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742613] Re: Add support for Realtek Bluetooth device [0bda:b00a]

[Anthony Wong]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Won't Fix => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742613

Title:
  Add support for Realtek Bluetooth device [0bda:b00a]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  These two devices are supported by the same rtk-btusb module, share
  the same firmware, while they have different config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742613/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1748345

Title:
  QCA9377 requires more IRAM banks for its new firmware

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment 
Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't 
fit the new BDF and firmware.

  [Fix]
  Change the bank number from 4 to 9.

  [Regression Potential]
  Low, increasing the number of IRAM banks should be no harm.

  [Misc]
  Currently, both driver patch and new firmware do not upstream yet. For the 
sake of avoiding dkms package, we can change t
  he IRAM bank number before their patch is ready.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748345/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

[Anthony Wong]

** Tags added: originate-from-1659177 somerville

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1664602

Title:
  Using an NVMe drive causes huge power drain

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1664602/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1748853] Re: Intel 9462 A370:42A4 doesn't work

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1748853

Title:
  Intel 9462 A370:42A4 doesn't work

Status in HWE Next:
  Fix Released
Status in Linux:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 
with that ID won't work.

  [Fix]
  Adding the ID to the list fix the issue

  [Regression Potential]
  No regression could be happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1748853/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1745081] Re: Add support for Realtek WiFi device [10ec:b822]

[Anthony Wong]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1745081

Title:
   Add support for Realtek WiFi device [10ec:b822]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged

Bug description:
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:b822]
Subsystem: Lenovo Device [17aa:b023]
Flags: fast devsel, IRQ 255
I/O ports at c000 [disabled] [size=256]
Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
Capabilities: [158] Latency Tolerance Reporting
Capabilities: [160] L1 PM Substates

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1745081/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

[Anthony Wong]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Also affects: hwe-next/bb
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1740231

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740231/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742613] Re: Add support for Realtek Bluetooth device [0bda:b00a]

[Anthony Wong]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Xenial)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Jesse Sung (wenchien)

** Also affects: hwe-next/bb
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742613

Title:
  Add support for Realtek Bluetooth device [0bda:b00a]

Status in HWE Next:
  Fix Released
Status in HWE Next bionic series:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  These two devices are supported by the same rtk-btusb module, share
  the same firmware, while they have different config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742613/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1742613] Re: Add support for Realtek Bluetooth device [0bda:b00a]

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742613

Title:
  Add support for Realtek Bluetooth device [0bda:b00a]

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  These two devices are supported by the same rtk-btusb module, share
  the same firmware, while they have different config files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742613/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1740231] Re: Add support for Realtek WiFi device [10ec:c821]

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1740231

Title:
  Add support for Realtek WiFi device [10ec:c821]

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  PCI ID: 10ec:c821

  The off-tree driver is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740231/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1736393

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1736393/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1734020] Re: QCA Rome bluetooth connection cannot be established after S3

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1734020

Title:
  QCA Rome bluetooth connection cannot be established after S3

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  SRU justification:

  [Impact]
  QCA Rome Bluetooth hosts (btusb) failed to search/pair after S3.

  [Fix]
  The device may loses its power under S3, hence doing a USB reset upon resume 
can solve the issue.

  [Test Case]
  With this patch, bluetooth connection always gets established after S3.

  [Regression Potential]
  Minimal, only QCA Rome needs this quirk. Also, reset-resume is kinda 
mandatory for tons of USB devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734020/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:

[Group.of.nepali.translators] [Bug 1708372] Re: The Precision Touchpad(PTP) button sends incorrect event code

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1708372

Title:
  The Precision Touchpad(PTP) button sends incorrect event code

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The touchpad right button should send 273(BTN_RIGHT),
  and the left button should send 272(BTN_LEFT)
  But the touchpad right button sends 274(BTN_MIDDLE),
  and the left button sends 273 (BTN_RIGHT)

  [Fix]
  The fix is pretty simple to just decrease the event code by 1.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  The patch has strict if statement, so it won't affect other touchpad devices.
  And no more rework on this code snip after this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1708372/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1695216] Re: Can't disable USB port from BIOS

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1695216

Title:
  Can't disable USB port from BIOS

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  From BIOS, there is front USB port disable function. It is supposed the 
option in BIOS can
  disable USB port and due to AMD chip limitation, it need OS’s cowork.
  Otherwise the USB disable function will be invalid when resuming from S3 or 
reinsert USB device.

  === SRU Justification ===

  [Impact]
  In BIOS, there is front USB port disable function.
  It is supposed the option in BIOS can disable USB port, but due to AMD chip's
  limitation, it needs OS’s cowork. Otherwise the USB disable function will
  be invalid when resuming from S3 or reinsert USB device.

  [Fix]
  After checking with Windows, we found there are 2 bits that are default on
  in Ubuntu is disabled in Windows. They are
  #define PORT_WKOC_E (1<<22) /* wake on overcurrent 
(enable) */
  #define PORT_WKCONN_E   (1<<20) /* wake on connect (enable) */
  So, this patch introduce a quirk to not setup the wakeup bits only for
  AMD USB chips.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  This patch only affects the listed USB ID, and we don't cert this kind of
  wakeup method, so should have no regression concerns.
  Wake up from USB device is still working, and the patch behavior is confirmed 
by
  the project lead, Tsai, Nicholas, from AMD in the discussion thread[1].

  [Misc]
  This patch is accepted by the maintainer but still not shown up in any git 
tree
  yet. The discussion thread can be found here[1]. To fit the project schedule,
  we need this commit in our kernel as soon as possbile, and can't wait to
  next SRU release cycle.

  1. https://www.spinics.net/lists/linux-usb/msg157789.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1695216/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1712481] Re: HID: multitouch: Support ALPS PTP Stick and Touchpad devices

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1712481

Title:
  HID: multitouch: Support ALPS PTP Stick and Touchpad devices

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Support to ALPS PTP Stick and Touchpad devices found on latest Dell Latitude 
systems.

  [Fix]
  This fix in two parts:
  1. Requires cherry-pick of patch submitted by ALPS in upstream kernel 4.13
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.13-rc6&id=504c932c7c47a6b4c572302a13873f7d83af1ff3

  2. Additional sauce patch adds the device-id of the new PTP stick. This
  patch is already submitted to linux-input and is pending review.
  See: http://marc.info/?l=linux-input&m=150235885218076&w=2

  [Test Case]
  Verified on the systems affected with this issue and confirmed that this 
solution works.

  [Regression Potential]
  The patch adds new device ids to hid multi-touch driver. With strict 
conditional filtering based on these device-ids, regression potential is 
minimal.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1712481/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1693126] Re: Keyboard backlight control does not work on some dell laptops.

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1693126

Title:
  Keyboard backlight control does not work on some dell laptops.

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  There's no sysfs node for some Dell laptop keyboard backlight control.

  Two issues here:
  1. No sysfs "/sys/devices/platform/dell-laptop/leds/dell::kbd_backlight"
  The patch fixes the issue by adding necessary DMI string to dmi whitelist 
table:

  commit 8d2c4538dbc7154c4aed1364db127a0e51dbd459
  Author: Alex Hung 
  Date:   Thu Feb 16 20:58:03 2017 +0800

  platform/x86: dell-laptop: Add Latitude 7480 and others to the DMI
  whitelist

  2. The sysfs exits, but backlight cannot be controlled by "brightness" 
attribute.
  The patch fixes the issue by updating timeout AC, if the model supports it:
  commit 9216e0dcb5533a999d544d0af8661118e0588e1d
  Author: Pali Rohár 
  Date:   Sun Apr 23 21:40:47 2017 +0200

  platform/x86: dell-laptop: Add keyboard backlight timeout AC
  settings

  [Test Case]
  On Dell Precision 3250 (Kabylake generation), the backlight cannot be 
controlled in sysfs, because it does not exist.
  With these two patches, keyboard backlight can be controlled in 
"/sys/devices/platform/dell-laptop/leds/dell::kbd_backlight".

  [Regression Potential] 
  The regression potential is low. Only newer Dell laptops will be affected, 
and it only applies to limited models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1693126/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1699651] Re: KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1699651

Title:
  KILLER1435-S[0489:e0a2] BT cannot search BT 4.0 device

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Steps:
  1. Install Ubuntu 16.04
  2. Search BT 4.0 devices

  Expected results: KILLER1435-S BT can search BT 4.0 devide normally

  Actual results: KILLER1435-S BT cannot search BT 4.0 devide

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1699651/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

[Anthony Wong]

** Changed in: hwe-next
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1667198

Title:
  gpu-manager should also support using custom xorg.conf files for
  Nvidia

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Released
Status in ubuntu-drivers-common source package in Zesty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Different GPUs may require different options in the xorg.conf file. Currently 
this is not possible, since the options have been hardcoded in gpu-manager to 
configure the system automatically.

  This new (backported) feature allows users to tell gpu-manager to use
  their own custom xorg.confs for their NVIDIA GPUs.

  [Test Case]
  1) Enable the xenial-proposed repository, and install the 
ubuntu-drivers-common and the nvidia-prime packages.

  2) Install the nvidia driver.

  3) Place your configuration file(s) in the /usr/share/gpu-manager.d
  directory.

  If you are using a non-hybrid system, you can create the /usr/share
  /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
  specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
  /gpu-manager.d/hybrid-power-saving, depending on the power profile you
  intend to apply your settings to.

  4) Restart the system and see if it boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  5) Make sure that the /etc/X11/xorg.conf matches the file you
  specified in 3)

  [Regression Potential]
  Low, the above mentioned changes are already in Artful, and will not affect 
the system's behaviour unless new configuration files are put in the 
/usr/share/gpu-manager.d/ directory.

  __
  This feature has been implemented for Intel (ex. gpumanager_uxa), which is 
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).

  And now Nvidia also need this feature to add Option
  "nvidiaXineramaInfo" "off" to fix some issues.

  Btw, I'm thinking it might be a more flexible to have a config file
  which user could add all options as they want so that we could prevent
  keeping change gpu-manager when some more options are needed in the
  future.

  Needed by LP: #1653592

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1706531] Re: ath10k doesn't report full RSSI information

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1706531

Title:
  ath10k doesn't report full RSSI information

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  ASA (Active Steering Antenna) requires per chain RSSI info. Intel WLAN driver 
has full support for per-chain RSSI information, but ath10k doesn't.

  [Fix]
  The fix is pretty simple just fills up RSSI value to the structure.

  [Test Case]
  RSSI information can be polled from userspace using NL80211 wireless stack.

  [Regression Potential]
  No any regression concern.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1706531/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1705378] Re: ideapad_laptop don't support v310-14isk

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1705378

Title:
  ideapad_laptop don't support v310-14isk

Status in HWE Next:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  we found the wireless and bluetooth can't work, the device had driver
  already, just wereo blocked by ideapad_laptop module. After remove it,
  it works fine.

  $ sudo rfkill list
  0: ideapad_wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
  1: ideapad_bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: yes
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
  3: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  SRU Justification
  =

  [Impact]
  wireless and bluetooth were blocked by ideapad_laptop module.

  [Fix]
  Fix it by adding those models to no_hw_rfkill_list.

  [Test Case]
  Wireless and BT works fine.

  [Regression Potential]
  This patch add several dmi entry in struct.
  Regression Potential is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1705378/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1686815] Re: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1686815

Title:
  Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact: Missing firmware causes Intel 8265 wireless to not work in
  16.04.2 installs on new hardware.

  Fix: Backport upstream linux-firmware commits to add the firmware and
  subsequent changes which fix some issues with the firmware.

  Regression Potential: The bug fix commits also fix the same issue in
  another Intel bluetooth firmware file. Regressions are possible but
  not expected since it's a bug fix update.

  Test Case: This is difficult to test since the bluetooth module only
  fails to work if it has never had firmware loaded to it previously.
  Three different users have confirmed that the test package fixed the
  issue.

  ---

  Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265
  wireless modules that haven't yet had firmware loaded onto them.
  dmesg reports the following:

    Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed
  with error -2

  This could be difficult for many people to reproduce, since installing
  a later version of Ubuntu once will load the necessary firmware, which
  will persist through reinstalling the operating system.  So installing
  Ubuntu 17.04 just once, will leave Bluetooth in a working state
  forever.

  I was able to consistently produce the issue on a *brand new* Kabylake
  Meerkat 3.  With Ubuntu 16.04.2, bluetooth didn't work.  I copied the
  ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted.
  After this point, Bluetooth worked (and continued to work after
  reinstalling Ubuntu 16.04.2 and *not* copying the firmware files
  again).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1686815/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS

[Anthony Wong]

** Changed in: linux (Ubuntu Yakkety)
   Status: Won't Fix => New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1666742

Title:
  Ath10k to read different board data file if specify in SMBIOS

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  New
Status in linux source package in Zesty:
  New

Bug description:
  Board Data File (BDF) is loaded upon driver boot-up procedure. The right
  board data file is identified, among others, by device and sybsystem ids.

  The problem, however, can occur when the (default) board data file cannot
  fulfill with the vendor requirements and it is necessary to use a different
  board data file.

  To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name
  Extension to specify the extension/variant name. The driver will take the
  extension suffix into consideration and will load the right (non-default)
  board data file if necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS

[Anthony Wong]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1666742

Title:
  Ath10k to read different board data file if specify in SMBIOS

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  New

Bug description:
  Board Data File (BDF) is loaded upon driver boot-up procedure. The right
  board data file is identified, among others, by device and sybsystem ids.

  The problem, however, can occur when the (default) board data file cannot
  fulfill with the vendor requirements and it is necessary to use a different
  board data file.

  To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name
  Extension to specify the extension/variant name. The driver will take the
  extension suffix into consideration and will load the right (non-default)
  board data file if necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1692836] Re: Dell XPS 9360 wifi 5G performance is poor

[Anthony Wong]

** Changed in: hwe-next/xenial
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1692836

Title:
  Dell XPS 9360 wifi 5G performance is poor

Status in HWE Next:
  Fix Released
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  TX throughput is not good in Ubuntu in IEEE 802.11ac mode.

  Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu
  Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and 
Tx 62MBit/s using the same hardware setup.
  Same result with WPA2 disabled in unencrypted mode.

  Steps to Reproduce:
  1. connect to Wifi
  2. copy a large file from XPS 13 to a share on a 2nd system

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1692836/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update

[Anthony Wong]

** Description changed:

  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found 
on Ubuntu 17.04 with fwupdate 9-1.
  
  The newer version of capsule flashing tools in Ubuntu 17.04 supports the
  reset type from some querycapsuleinfo call：
  
  
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722
  
- fwupdate 9-1 has other bugfixes that are important too:
-  - some memory leaks (eg: 
https://github.com/rhinstaller/fwupdate/commit/765bb7221af37ac56b11ef2253bf1bb3230ef589)
-   - some inconsistent behaviors due to ambiguous UEFI spec behavior (eg 
https://github.com/rhinstaller/fwupdate/commit/ba48ac4ed7329ae5beb44063dcbd3c424e11fc46)
-   - some other features that are going to be needed to be able to support 
newer fwupd (eg: 
https://github.com/rhinstaller/fwupdate/commit/64b4cd53baa57352fa9b2459e804c4ea50d40299)
- 
  [Test Case]
  
  == fwupdate ==
  On a system with a capsule update available, perform capsule update using 
fwupdate.  Verify the system works properly after the update.
- 
- == fwupd ==
- The soname version of libfwup has been increased to 1 in fwupdate 9. Since 
the current fwupd depends on libfwup0 so fwupd has to be rebuilt against the 
new libfwup1.
- 
- To test, perform firmware update with fwupdmgr and see if it works.
  
  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its 
reverse-dependencies.
  
  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm 
reset rather than querying for reset types) may have problems.  This is 
actually a BIOS
  problem in those situations.
  
  It's unlikely that this should happen though because querying for reset
  types more closely aligns to the implementations that other OSes use
  when applying capsule updates.

** No longer affects: fwupd (Ubuntu)

** No longer affects: fwupd (Ubuntu Xenial)

** No longer affects: fwupd (Ubuntu Yakkety)

** No longer affects: fwupd (Ubuntu Zesty)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  In Progress
Status in fwupdate-signed source package in Xenial:
  In Progress
Status in fwupdate source package in Yakkety:
  In Progress
Status in fwupdate-signed source package in Yakkety:
  In Progress
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found 
on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  
https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using 
fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its 
reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm 
reset rather than querying for reset types) may have problems.  This is 
actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1512997] Re: Support Edge Gateway's WIFI LED

[Anthony Wong]

** Changed in: hwe-next/xenial
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1512997

Title:
  Support Edge Gateway's WIFI LED

Status in HWE Next:
  Fix Released
Status in HWE Next vivid series:
  Fix Released
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The WIFI LED of Marvell 88W8897 is not enabled by default (there's no
  code for controlling LED in mwifiex). It is requested to be ON and OFF
  when the radio is on and off accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1512997/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1560835] Re: Enable multitouch function on precision touchpad for Vivid

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: linux (Ubuntu Wily)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1560835

Title:
  Enable multitouch function on precision touchpad for Vivid

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Multitouch feature is not enabled on some platforms with new Win8
  precision touchpad because it can't fetch the report from the device.
  In worst case it can even break the multitouch device.

  [Fix]

  There's one commit to fix this issue:
  commit 171202b6fee80d777d18bb8a53b3e4361d97f389
  Author: Mika Westerberg 
  Date:   Wed Oct 7 15:33:43 2015 +0300

  HID: multitouch: Fetch feature reports on demand for Win8 devices

  In addition, this commit may cause some issue on ELAN touchpad, and
  there's another commit to improve the fix:

  commit e47b1e449ea70d76c38a50c04cde60a72bc7ebde
  Author: Benjamin Tissoires 
  Date:   Tue Dec 1 12:41:38 2015 +0100

  HID: multitouch: fix input mode switching on some Elan panels

  Both commits can be clean picked, and are already in Xenial.

  [Test]

  The patched Vivid kernel is tested on two platforms and both worked
  before and after suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1560835/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1578305] Re: Stoney powerplay support

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1578305

Title:
  Stoney powerplay support

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1578305/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1616318

Title:
   System hang when plug/pull USB 3.1 key via thunderbolt port over 5
  times

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Steps:
  1) Install Ubuntu 16.04
  2) Enter to Dekstop.
  3) Insert the USB 3.1 key in the thunderbolt port.
  4) Remove the USB 3.1 key from the thunderbolt port.
  5) Insert the USB 3.1 key in the thunderbolt port.

  Expected results: Can detect the USB 3.1 key and system will not hang.

  Actual results: System Hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616318/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1609606] Re: Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1609606

Title:
  Mic mute hotkey does not work on usb keyboard [03f0:2f4a]

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Press the MIC mute function key on the USB keyboard [03f0:2f4a]
  doesn't emit any keyevent nor acpi event.

  T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 23 Spd=1.5 MxCh= 0
  D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
  P:  Vendor=03f0 ProdID=2f4a Rev=00.10
  S:  Manufacturer=Chicony
  S:  Product=HP Business Slim Keyboard
  C:  #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
  I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1609606/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1617900] Re: Headset mic detection on some variants of Dell Inspiron 5468

[Anthony Wong]

** Changed in: hwe-next
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1617900

Title:
  Headset mic detection on some variants of Dell Inspiron 5468

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On some Dell Inspiron 5468 variants, headset mic device is not
  detected.

  This bug is used for tracking purposes, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1617900/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1650054] Re: Dell Precision 5520 & 3520 freezes at login screent

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1650054

Title:
  Dell Precision 5520 & 3520 freezes at login screent

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When Precision 5520 & 3520 run on iGPU (Intel video only) mode, they
  hang at login screen, i.e. bbswitch tries to turn off the dGPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1650054/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1664809] Re: [0bda:0328] Card reader failed after S3

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1664809

Title:
  [0bda:0328] Card reader failed after S3

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Summary: [0bda:0328] Card reader failed after S3

  Steps:
  1. Check card reader can be used before S3
  2. Enter into S3
  3. Resume from S3
  4. Insert SD/MMC/SDHC into the card reader

  Expected results: Card reader passed after S3

  Actual results: Card reader failed after S3
  The card reader device is gone from lsusb
  Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1664809/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1606147] Re: [APL][SAUCE] Slow system response time due to a monitor bug

[Anthony Wong]

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1606147

Title:
  [APL][SAUCE] Slow system response time due to a monitor bug

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.
  From upstream it is caused by following reason:

  "Monitored cached line may not wake up from mwait on certain Goldmont
  based CPUs. This patch will avoid calling
  current_set_polling_and_test() and thereby not set the TIF_ flag. The
  result is that we'll always send IPIs for wakeups."

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606147/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1616781] Re: DINO2M - System hangs with a black screen during s4 stress test

[Anthony Wong]

** Changed in: hwe-next
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1616781

Title:
  DINO2M - System hangs with a black screen during s4 stress test

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  System hangs with a black screen during s4 stress test

  Keyboard backlight LED is still on and adjustable, but tty1 is not avalible 
to switch to.
  System needs to be hardware shutdown.

  Steps:
  1. install Ubuntu 16.04 and boot to OS
  2. run s4 stress test (30 cycles)
  3. check if the test can be completed

  Expected results: Test should be able to be completed

  Actual results: System hangs with a black screen

  Additional information:
  BIOS: 99.2.22

  CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 5916
  (rev 02)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1616781/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp