[Kernel-packages] [Bug 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee

2022-12-26 Thread Chris Guiver 
> Any help is greatly appreciated! I will keep the system as is, without
applying any updates for now.

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/2000491

Title:
  Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-
  recoverable after screen lock and screen completely fades to black or
  after system goes into sleep

Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390.

  The system is non-recoverable after it goes into sleep. Or after the
  screen is locked by the user and after it fades to complete black.
  System becomes unresponsive, no mouse or keypress will get the system
  back on to work.

  If the systemctl suspend is issued, the system will not wake up again.
  Hard reset is needed.

  If Ubuntu 18.04.6 is booted from live USB, the same is happening.

  Sometimes, when the system is rendered unresponsive as a result of any
  of the above, the power led is sending the message of "processor
  failure" (2 x amber blinks followed by 1 x white blink).

  Any help is greatly appreciated! I will keep the system as is, without
  applying any updates for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 27 01:13:12 2022
  InstallationDate: Installed on 2022-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/2000491/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

2022-12-26 Thread AceLan Kao 
** Tags added: originate-from-1988823

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1996048

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  The patch is not finalized, so submit SRU to OEM kernels only, and
  will submit to other series kernels once the patch is accepted by
  upstream.

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee

2022-12-26 Thread Attila 
Having Ubuntu 22.10 and 22.04 booted from a live USB will freeze before
or little after the graphical interface is displayed. Hence, I tried an
older version, namely 18.04.6.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/2000491

Title:
  Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-
  recoverable after screen lock and screen completely fades to black or
  after system goes into sleep

Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390.

  The system is non-recoverable after it goes into sleep. Or after the
  screen is locked by the user and after it fades to complete black.
  System becomes unresponsive, no mouse or keypress will get the system
  back on to work.

  If the systemctl suspend is issued, the system will not wake up again.
  Hard reset is needed.

  If Ubuntu 18.04.6 is booted from live USB, the same is happening.

  Sometimes, when the system is rendered unresponsive as a result of any
  of the above, the power led is sending the message of "processor
  failure" (2 x amber blinks followed by 1 x white blink).

  Any help is greatly appreciated! I will keep the system as is, without
  applying any updates for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 27 01:13:12 2022
  InstallationDate: Installed on 2022-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/2000491/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2000491] [NEW] Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into sl

2022-12-26 Thread Attila 
Public bug reported:

This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390.

The system is non-recoverable after it goes into sleep. Or after the
screen is locked by the user and after it fades to complete black.
System becomes unresponsive, no mouse or keypress will get the system
back on to work.

If the systemctl suspend is issued, the system will not wake up again.
Hard reset is needed.

If Ubuntu 18.04.6 is booted from live USB, the same is happening.

Sometimes, when the system is rendered unresponsive as a result of any
of the above, the power led is sending the message of "processor
failure" (2 x amber blinks followed by 1 x white blink).

Any help is greatly appreciated! I will keep the system as is, without
applying any updates for now.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 27 01:13:12 2022
InstallationDate: Installed on 2022-12-26 (0 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/2000491

Title:
  Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-
  recoverable after screen lock and screen completely fades to black or
  after system goes into sleep

Status in linux-signed-hwe-5.4 package in Ubuntu:
  New

Bug description:
  This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390.

  The system is non-recoverable after it goes into sleep. Or after the
  screen is locked by the user and after it fades to complete black.
  System becomes unresponsive, no mouse or keypress will get the system
  back on to work.

  If the systemctl suspend is issued, the system will not wake up again.
  Hard reset is needed.

  If Ubuntu 18.04.6 is booted from live USB, the same is happening.

  Sometimes, when the system is rendered unresponsive as a result of any
  of the above, the power led is sending the message of "processor
  failure" (2 x amber blinks followed by 1 x white blink).

  Any help is greatly appreciated! I will keep the system as is, without
  applying any updates for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 27 01:13:12 2022
  InstallationDate: Installed on 2022-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/2000491/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882968] Re: ath10k_pci failed to wake target for write32

2022-12-26 Thread Kai-Heng Feng 
Does mainline kernel have this issue? Does the issue only happen when
system come out of suspend?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882968] Re: ath10k_pci failed to wake target for write32

2022-12-26 Thread Robin 
Crashed. :(

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro text 
pcie_aspm=off pcie_port_pm=off

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

2022-12-26 Thread Swastik Harish 
Apologies, to be more precise: sound works in exactly the same way as 
kernel 5.15, 5.19 and 6.0, that is, headphones and mic work fine, 
speakers do not.

In case it helps, I am attaching some info from Windows, where these 
Dolby Atmos speakers work.


On 26/12/22 19:30, Swastik Harish wrote:
> I can confirm that sound still does NOT work in Manjaro 22 with kernel 
> 6.1.1...
>
> Still waiting for a fix.
>
> On 26/12/22 13:41, dog soup wrote:
>> A few random notes - seems like the issue is definitely related to the
>> ALC294 for many different laptops, and apparently there are issues
>> getting Dolby Atmos to work in Ubuntu as well (not sure if related).
>> According to this reddit article, a fix might be within kernel 6.1,
>> which apparently is only available in Manjaro as of now:
>> https://www.reddit.com/r/Ubuntu/comments/zrfmgc/bug_no_sound_on_asus_ux3402za/
>>  
>>
>>

** Attachment added: "sysinfo-audio.txt"
   
https://bugs.launchpad.net/bugs/1981433/+attachment/5637813/+files/sysinfo-audio.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

2022-12-26 Thread Swastik Harish 
I can confirm that sound still does NOT work in Manjaro 22 with kernel 
6.1.1...

Still waiting for a fix.

On 26/12/22 13:41, dog soup wrote:
> A few random notes - seems like the issue is definitely related to the
> ALC294 for many different laptops, and apparently there are issues
> getting Dolby Atmos to work in Ubuntu as well (not sure if related).
> According to this reddit article, a fix might be within kernel 6.1,
> which apparently is only available in Manjaro as of now:
> https://www.reddit.com/r/Ubuntu/comments/zrfmgc/bug_no_sound_on_asus_ux3402za/
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882968] Re: ath10k_pci failed to wake target for write32

2022-12-26 Thread Robin 
Interesting. Yes `pcie_aspm=off` is already in the grub parameters but
not `pcie_port_pm=off`. I will add that now, wait for the daily crash
and then report back in due course.

Thanks.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882968

Title:
  ath10k_pci failed to wake target for write32

Status in linux package in Ubuntu:
  Expired

Bug description:
  Wifi card stopped working. I use Lubuntu 20.04.

  Wifi card info:

*-network 
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:3a:00.0
 logical name: wlp58s0
 version: 32
 serial: 9c:b6:d0:d4:9b:33
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.6.11-050611-generic firmware=WLAN.RM.4.4.1-00151-QCARMSWPZ-2 
ip=192.168.0.87 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:135 memory:dc00-dc1f

  Releveant journal log attached. In brief,

  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt blocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ACPI: EC: interrupt unblocked
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
receive control response completion, polling..
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
wake target for write32 of 0x0001 at 0x00034430: -110
  ...
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: ctl_resp 
never came in (-110)
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_pci :3a:00.0: failed to 
connect to HTC: -110
  Jun 10 15:54:41 user-XPS-13-9360 kernel: ath10k_warn: 122 callbacks suppressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-11 (29 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  Tags:  focal
  Uname: Linux 5.6.11-050611-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2000465] Re: rt715-sdca codec cannot record audio with internal microphone

2022-12-26 Thread Andy Chi 
Upload debdiff for Jammy.

** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000465/+attachment/5637762/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.2.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2000465

Title:
  rt715-sdca codec cannot record audio with internal microphone

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]
  rt715-sdca codec cannot record audio with internal microphone

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal microphone should work propoerly.

  [Where problems could occur]
  Only fix for DUT with rt715-sdca device

  [Other Info]
  Upstream bug:
  https://github.com/alsa-project/alsa-ucm-conf/issues/255
  Fix:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2000465/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2000465] [NEW] rt715-sdca codec cannot record audio with internal microphone

2022-12-26 Thread Andy Chi 
Public bug reported:

[Impact]
rt715-sdca codec cannot record audio with internal microphone

[Test Plan]
1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
3. reboot system
4. Internal microphone should work propoerly.

[Where problems could occur]
Only fix for DUT with rt715-sdca device

[Other Info]
Upstream bug:
https://github.com/alsa-project/alsa-ucm-conf/issues/255
Fix:
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

** Affects: oem-priority
 Importance: Critical
 Assignee: Andy Chi (andch)
 Status: New

** Affects: alsa-ucm-conf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1997690 somerville

** Tags added: oem-priority originate-from-1997690 somerville

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

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2000465

Title:
  rt715-sdca codec cannot record audio with internal microphone

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]
  rt715-sdca codec cannot record audio with internal microphone

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Internal microphone should work propoerly.

  [Where problems could occur]
  Only fix for DUT with rt715-sdca device

  [Other Info]
  Upstream bug:
  https://github.com/alsa-project/alsa-ucm-conf/issues/255
  Fix:
  
https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2000465/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992435] Re: sof-hda-dsp Dmic0 not initial correctly

2022-12-26 Thread Andy Chi 
** Changed in: oem-priority
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1992435

Title:
  sof-hda-dsp Dmic0 not initial correctly

Status in OEM Priority Project:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Device use sof-hda-dsp driver will not able to initial the Dmic0 status 
correctly

  [Test Plan]
  1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service"
  2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state"
  3. reboot system
  4. Dmic should be on and volume set to 70%

  [Where problems could occur]
  Only fix for Dmic0 control and upstream already merged the code. The risk 
will be low

  [Other Info]
  Pull Request in upstream 
https://github.com/alsa-project/alsa-ucm-conf/pull/132

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1992435/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1997946] Re: Support soundwire speaker AMP-ALC1318 codec

2022-12-26 Thread Kai-Chuan Hsieh 
** Description changed:

  [ Impact ]
  
   * Add ALC1318 speaker codec ucm file
+  * Make internal speaker working on platform with the codec
  
  [ Test Plan ]
  
   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu
  
  [ Where problems could occur ]
  
   * The config only be executed on the platform with the codec exported
  
   * It needs add codec configuration to the machine driver to make the
  function work
  
  [ Other Info ]
  
   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

** Description changed:

  [ Impact ]
  
   * Add ALC1318 speaker codec ucm file
-  * Make internal speaker working on platform with the codec
+  * Make internal speaker working on the platform with the codec
  
  [ Test Plan ]
  
   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu
  
  [ Where problems could occur ]
  
   * The config only be executed on the platform with the codec exported
  
   * It needs add codec configuration to the machine driver to make the
  function work
  
  [ Other Info ]
  
   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1997946

Title:
  Support soundwire speaker AMP-ALC1318 codec

Status in OEM Priority Project:
  Triaged
Status in alsa-ucm-conf package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * Add ALC1318 speaker codec ucm file
   * Make internal speaker working on the platform with the codec

  [ Test Plan ]

   * On platform with the codec, the internal speaker should work after
     boot into Ubuntu

  [ Where problems could occur ]

   * The config only be executed on the platform with the codec exported

   * It needs add codec configuration to the machine driver to make the
  function work

  [ Other Info ]

   * Upstream commit soundwire speaker AMP-ALC1318 codec.
     
https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997946/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2000030] Re: Soundwire support for the Intel RPL Gen platforms -- follow-ups

2022-12-26 Thread You-Sheng Yang 
Removed staging https://github.com/thesofproject/linux/pull/4116 for
it's replaced by https://github.com/alsa-project/alsa-ucm-
conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa in alsa-ucm-conf
instead.

** Description changed:

  This is a follow-up to bug 1997944 that supports more RPL gen platforms.
  
  Staging fixes:
  * 
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
  * 
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
- * https://github.com/thesofproject/linux/pull/4116 ("ASoC: SOF: set switch 
default value to On")
+ * ~~https://github.com/thesofproject/linux/pull/4116~~ ("ASoC: SOF: set 
switch default value to On")

** Description changed:

  This is a follow-up to bug 1997944 that supports more RPL gen platforms.
  
  Staging fixes:
  * 
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
  * 
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
- * ~~https://github.com/thesofproject/linux/pull/4116~~ ("ASoC: SOF: set 
switch default value to On")
+ * ~https://github.com/thesofproject/linux/pull/4116~ ("ASoC: SOF: set switch 
default value to On")

** Description changed:

  This is a follow-up to bug 1997944 that supports more RPL gen platforms.
  
  Staging fixes:
  * 
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
  * 
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
- * ~https://github.com/thesofproject/linux/pull/4116~ ("ASoC: SOF: set switch 
default value to On")

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/230

Title:
  Soundwire support for the Intel RPL Gen platforms -- follow-ups

Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  New
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  New
Status in firmware-sof source package in Lunar:
  New
Status in linux source package in Lunar:
  Incomplete
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  This is a follow-up to bug 1997944 that supports more RPL gen
  platforms.

  Staging fixes:
  * 
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
  * 
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

2022-12-26 Thread dog soup 
A few random notes - seems like the issue is definitely related to the
ALC294 for many different laptops, and apparently there are issues
getting Dolby Atmos to work in Ubuntu as well (not sure if related).
According to this reddit article, a fix might be within kernel 6.1,
which apparently is only available in Manjaro as of now:
https://www.reddit.com/r/Ubuntu/comments/zrfmgc/bug_no_sound_on_asus_ux3402za/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981433

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp