@Aaron,
I found there are 2 firmwares with BCM54716 string, could you help to confirm
which one is the correct one?
And is there any readme about how to proceed the fw update?
Broadcom P210tep NetXtreme-E Dual-port 10GBASE-T Ethernet BCM57416 PCIe Adapter
Firmware Image
Broadcom NetXtreme-E 2Px
** Tags removed: verification-needed-jammy-linux-gkeop
verification-needed-noble-linux-gke
** Tags added: verification-done-jammy-linux-gkeop
verification-done-noble-linux-gke
** Tags removed: verification-done-jammy-linux-gkeop
verification-done-noble-linux-gke verification-needed-jammy-linux-
Public bug reported:
[Summary]
iwlwifi Microcode SW error detected during the SRU testing on some xps 13 9430
machines.
[Expected result]
No failures
[Actual result]
Oct 23 13:33:56 ubuntu kernel: iwlwifi :56:00.0: Microcode SW error
detected. Restarting 0x0.
Oct 23 13:33:56 ubuntu kernel:
After the verification, linux-firmware 20220329.git681281e4-0ubuntu3.35 has
resolved the issue.
Test result cat be found at
https://certification.canonical.com/hardware/202312-33275/submission/400323/.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Tested successfully focal:linux-gcp 5.4.0-1139.148 on c4-standard-4. C6
duration increases.
** Tags removed: verification-needed-focal-linux-gcp
** Tags added: verification-done-focal-linux-gcp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags removed: verification-needed-noble-linux-gcp
** Tags added: verification-done-noble-linux-gcp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2048183
Title:
Don't pr
** Tags removed: verification-needed-noble-linux-gcp
** Tags added: verification-done-noble-linux-gcp
--
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/2077306
Title:
Remove obsolete build
Boot testing passed on focal/jammy/noble gcp kernels.
** Tags removed: verification-needed-focal-linux-gcp
verification-needed-jammy-linux-gcp verification-needed-noble-linux-gcp
** Tags added: verification-done-focal-linux-gcp
verification-done-jammy-linux-gcp verification-done-noble-linux-gcp
sev-guest.ko is built-in in linux-modules for noble/linux-gcp
6.8.0-1017.19 and jammy/linux-gcp-6.8 6.8.0-1017.19~22.04.1.
** Tags removed: verification-needed-noble-linux-gcp
** Tags added: verification-done-noble-linux-gcp
--
You received this bug notification because you are a member of Kerne
mlx5_ib.ko is found in linux-modules for noble/linux-gcp 6.8.0-1017.19
and jammy/linux-gcp-6.8 6.8.0-1017.19~22.04.1.
** Tags removed: verification-needed-noble-linux-gcp
** Tags added: verification-passed-noble-linux-gcp
** Tags removed: verification-passed-noble-linux-gcp
** Tags added
Public bug reported:
[Summary]
During the SRU testing, I found many laptops displayed a black screen after
booting. Those machines are still alive and able to access via ssh, just
nothing displayed on the screen.
After a brief check, those affected machines that I inspected are all
Meteor Lake
** Changed in: linux-realtime (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: linux-realtime (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-realtime
Status: Fix Committed => Fix Released
--
You received this bug notification because
** Changed in: ubuntu-realtime
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-realtime in Ubuntu.
https://bugs.launchpad.net/bugs/2081779
Title:
Oracular real-time patch set: v6.11-rt7
** Changed in: linux-aws-6.8 (Ubuntu)
Status: New => Fix Committed
** Tags removed: verification-needed-jammy-linux-aws-6.8
** Tags added: verification-done-jammy-linux-aws-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
Fixed in jammy/linux-aws-6.8 6.8.0-1016.17~22.04.2 by compiling with
gcc12. The fix has been committed but still needs to undergo testing.
** Changed in: linux-aws-6.8 (Ubuntu)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
--
You received this bug notification because you ar
** Changed in: linux-realtime (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: ubuntu-realtime
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-realtime in Ubuntu.
https://bugs.
** Also affects: linux-realtime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-realt
Rerun the cert-testing on the impacted systems that mentioned in the
description, both of them complete the test.
https://certification.canonical.com/hardware/202306-31696/submission/392825/packages/?term=linux-firmware
https://certification.canonical.com/hardware/202306-31695/submission/396179/pa
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2077490
Title:
Error: out of memory while bootin
@Atlas, thanks for pointing out that, after checking that HP platform
has 4 configs in the cert lab, which are sku2, sku4, sku6 and sku10,
only sku2 has this issue. So it indeed looks like a single hardware
issue.
@Acelan, I think we still need to figure out why only this single
hardware won't wor
Public bug reported:
trying to install nvidia-driver-545
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidi
@Aaron
I just checked that it also happened on -40 kernel which is already in the
update.
I only can confirm 6.5.0-1013-oem which is the GM kernel is good, since we
always do restoring the system then dist-upgrade while testing.
Full dmesg log is attached.
** Attachment added: "dmesg"
https
Public bug reported:
[Summary]
During the SRU testing, I found a Lenovo workstation has multiple NICs
installed that failed to wake up from cold-reboot by rtc event. After
some investigations, I found that it's because too many kernel message
appear and slow down the power off.
We don't have any
Public bug reported:
[Summary]
During the SRU testing, I found a hp laptop always timeout after suspend
test, after checking I found that the NIC didn't link up.
Part of journal log as follows:
Sep 12 11:13:01 ubuntu kernel: PM: suspend entry (s2idle)
...
...
Sep 12 11:13:10 ubuntu kernel: PM: s
** Tags removed: verification-needed-jammy-linux-realtime-6.8
verification-needed-noble-linux
** Tags added: verification-done-jammy-linux-realtime-6.8
verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I saw this with jammy:linux-realtime 5.15.0-1071.79 on scobee-kernel. I
think this was the first time this test used scobee-kernel in a while,
so that's probably why we didn't see it before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
[Summary]
During the SRU testing, I found at least 2 DUTs always timeout after
suspend test, after checking I found that both of them only detect 10
Mbps speed on their NIC and can't get IP from DHCP.
Part of journal log as follows:
Sep 02 10:55:00 ubuntu kernel: PM: suspend
** Summary changed:
- kernel oops in aafs_create in 6.8.1-1002-realtime kernel
+ kernel oops in aafs_create in noble/oracular
--
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/2068602
Title:
Just tested the linux-firmeware in proposed, it fixed the problem.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2077490
Title:
Error: o
Public bug reported:
I found that there are some machines in cert lab can't boot after
installing the linux-frimware in proposed with 6.8.0-40 kernel.
After selecting booting with the 6.8.0-40 kernel, it shows error: out of
memory on the screen then freeze.
There aren't any journal logs availabl
Testing complete on jammy:linux-realtime 5.15.0-1070.78
** Tags removed: verification-needed-jammy-linux-realtime
** Tags added: verification-done-jammy-linux-realtime
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-realtime in Ubun
** Also affects: linux-realtime (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-realtime (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ubuntu-realtime
Status: New => Fix Committed
** Changed in: linux-realtime (Ubuntu)
Status:
This was fixed in 6.8.1-1006.6 realtime on Noble and 5.15.0-1068.76
realtime on Jammy.
** Changed in: ubuntu-realtime
Status: Fix Committed => Fix Released
** Changed in: linux-realtime (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-realtime (Ubuntu Jammy)
Testing passes for jammy:linux-realtime/5.15.0-1068.76 and noble:linux-
realtime/6.8.1-1006.6.
** Tags removed: verification-needed-jammy-linux-realtime
verification-needed-noble-linux-realtime
** Tags added: verification-done-jammy-linux-realtime
verification-done-noble-linux-realtime
--
You
With realtime access enabled via Ubuntu Pro (either via `sudo pro enable
realtime-kernel` or `sudo pro enable realtime-kernel --access-only`),
you can run the following command to download the source:
sudo apt-get source --only-source linux-realtime
--
You received this bug notification because
** Description changed:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
- The last messages displayed on the screen are:
+ The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID
Public bug reported:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
The
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2043811
Title:
AWS: arm64: pauth: don't sign leaf fu
Confirmed as working by Amazon.
** Tags removed: verification-needed-jammy-linux-aws
** Tags added: verification-done-jammy-linux-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/204
** Also affects: linux-intel-iotg-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2056383
Title:
Audio turned to
Updated to target Jammy since we're not fixing this in Lunar.
** Also affects: linux-aws (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Jammy)
Status: New => In Progress
** No longer affects: linux-aws (Ubuntu Lunar)
--
You received this bug
Patches sent to mailing list:
Jammy: https://lists.ubuntu.com/archives/kernel-
team/2024-February/148619.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2043811
Title:
AWS: arm6
** Summary changed:
- linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55
+ linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with
linux-kvm/5.15.0-1050.55
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in
Public bug reported:
This is a scripted bug report about ADT failures while running linux-kvm
tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
amd64:
https://autopkgtest.ubunt
Public bug reported:
During the 6.5-hwe migration test, I found that there was a missing dkms which
is tp_smapi.
I just randomly picked some test results for your reference.
https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/
https://certificat
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Some machine
Public bug reported:
During the jammy-hwe migration test, I found some machines failed to run
the pm-graph.
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)
One of machine when I rerun it locally, it passed, but others are still
failed.
Following ar
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
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/2043197
Title:
USB bus error after upgrading
** Summary changed:
- USB bus error after upgrading to proposed kernel on lunar and jammy
+ USB bus error after upgrading to proposed kernel on lunar, jammy and focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
@smb @kaihengfeng
I also found this regression on 5.4.0-168-generic
Following is the journal log.
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: device descriptor
read/8, error -71
Nov 22 20:22:56 dell-inspiron-5480-c26321 kernel: usb 2-2: new SuperSpeed Gen 1
USB device number 7 usi
** Tags added: regression-proposed
--
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/2043197
Title:
USB bus error after upgrading to proposed kernel on lunar and jammy
Status in linux pack
** Tags removed: verification-needed-done-linux
** Tags added: verification-done-jammy-linux
--
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/2043197
Title:
USB bus error after upgrading t
gekit role='install-packages'
Requested-By: kevin (1000)
Install: gnome-metronome:amd64 (1.3.0-0ubuntu4)
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-10-24 (19 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Description changed:
[Summary]
Some of machines in cert lab after upgrading to proposed kernel on jammy and
lunar, all usb devices were gone.
- I found this issue on linux-image-6_2_0-38-generic an
Public bug reported:
[Summary]
Some of machines in cert lab after upgrading to proposed kernel on jammy and
lunar, all usb devices were gone.
I found this issue on linux-image-6_2_0-38-generic and linux-
image-5_15_0-90-generic on some specific machines.
Since some of machines are using usb eth
We are impacted by this as well, and all our new VMs that were spun up
in Azure were failing due to mount issues. We were able to mitigate by
adding the following to our cloud-init:
bootcmd:
- apt update
- apt-mark hold linux-image-6.2.0-1016-azure
- apt-mark hold linux-cloud-tools-6.2.0-101
** Also affects: linux-signed-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2040948
Title:
USB stick can't
** Tags added: cert-sru
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2040948
Title:
USB stick can't be detected
Status in linux-signed-oem-6.1 package in Ubuntu:
New
Public bug reported:
[Summary]
During SRU testing, I found some of devices failed to run the usb test,
when I re-plugged the usb stick, it can be detected, but after
rebooting, usb stick is gone again.
I did some further checks and found that If I power cycle the device, it
can be detected again
It examines the blkio device tree and sums data as far as i know.
Removed devices do not get deleted from the blkio statistics tree and
are just marked as offline somehow.
In our case racadm lclog created and destroyed usb devices to pull data
and the blkio tree reached over 65000 leafs. It takes
Public bug reported:
I'm reviewing the SRU test result on this machine.
I found that this machine always fails to wifi test and also pop out a lot of
error message in dmesg.
It's not a regression, since according to previous test run it has failed
already.
Just because we missed reviewing it fo
the hardware does not seem to be relevant. Do you have anything calling
"racadm lclog" on fairly regular basis? it creates and destroys a usb
device over and over.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https
Do you have a lot of blkio devices coming and going? For example
iscsi/usb/etc. We currently believe it's tree bloat due to added/removed
devices. We are still digging into the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-m
yes. just confirms it takes a while.
** Attachment added: "flame2.html"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021571/+attachment/5700645/+files/flame2.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-met
Was the cause of this ever determined? I am seeing something similar on
some of my systems. Times are usually around 1s, sometimes slightly
higher.
# uname -r
4.15.0-193-generic
# time cat /sys/fs/cgroup/blkio/blkio.time_recursive
8:144 69349171178307
8:128 4718621058
8:112 4604996397
8:96 462537
I had a similar issue with a black screen after kernel update to
5.19.0-35. Kernel 5.19.0-32 still worked.
Updating NVIDIA drivers to 525.85.05 fixed 5.19.0-35 and broke 5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
No regression found.
Test result is available at
https://docs.google.com/spreadsheets/d/15x8EIBt60Wd2YemL0XrjQnw2VheC0FCbwDGZ37-IpVo/edit?usp=share_link
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
h
Public bug reported:
During the NV driver SRU testing, I found an issue on one dell
machine(https://certification.canonical.com/hardware/202004-27810/).
After installing the latest driver(525.85.05) in proposed, the system won't
auto login anymore.
I tried many times using reboot command.
Pleas
Public bug reported:
During the SRU testing, I found a dependency issue when running "ubuntu-drivers
install".
Although OEM image has preloaded nvidia driver already, but when user want to
install newer version of nvidia driver will hit this issue.
Using 202002-27718 as an example, after instal
Hi Alberto
Please find the log and console-log in our test job in the attachment.
** Attachment added: "截圖 2022-11-09 上午11.18.27.png"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629770/+files/%E6%88%AA%E5%9C%96%202022-11-09%20%E4%B8%8A%E5%8D%8811.1
** Attachment added: "ubuntu-drivers.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5629769/+files/ubuntu-drivers.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15
** Attachment added: "27810.logs.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628933/+files/27810.logs.tar.xz
** Summary changed:
- It seems not to auto login or get X session after installing Nvidia-driver
+ It seems to now login automatic
** Attachment added: "26941.logs.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+attachment/5628932/+files/26941.logs.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in
Public bug reported:
During SRU testing, I found some machines kept failing to run switching graphic
card test.
According to the output from the test run, those machines seem to not login
automatically or can't get X session somehow.
Now I can't check the status of machines directly, but my gu
The only upstream bug that seems potentially related is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024
. But that's more about ensuring that WPA auth has completed before
starting the DHCP renewal, and it's not clear to me how blocking ICMP
could avoid that problem. So
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework
laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device.
Every time wpa-supplicant chooses to associate with a different BSSID
(of the same SSID), the interface ends up being given a new IP address
by the DHCP server (usu
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939886
Title:
Network connection can't come ba
This broke a lot of our servers running Docker, which I all had to
restore by adding the root volume to a different instance and then
changing /boot/grub/grub.cfg in order to boot 5.13.0-1025-aws again.
So another "I can confirm this" from me.
--
You received this bug notification because you ar
Could you put together a simple instruction for how to perform this
workaround please? I am not sure, if this is what was supposed to be set
by editing dsdt.dsl with above suggestion or if this is a new fix.
In all cases a simple instruction would be much appreciated and I will
test this and get b
We have tested with 5.18.0-051800-generic now, unfortunately battery is
still not recognized :(
Anything else we can try? Seems like some has managed to solve this with
identical hardware, but then I must be missing some steps here. Any help
is much appreciated.
--
You received this bug notifica
Output of dmesg attached.
** Attachment added: "output dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593690/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Please find output of cat /proc/iomem attached.
** Attachment added: "output cat /proc/iomem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593426/+files/iomem.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATL
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATL returned object 09af25b3,
external buffer length 18
[Integer] =
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'
Evaluating \_SB_.PCI0.LPCB.EC0_.
Yes - Disabling Secureboot worked in order to get acpidbg working
(killed my touchpad mouse however that is another topic).
Output from both commands here:
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATD
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATD returned object
Unfortunately I get an "Operation not permitted" error when running sudo
acpidbg -b 'ex \_SB_.BAT1._STA' as well.
--
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/1956177
Title:
battery no
Hi,
I left the PC at the office. Will try the new command on Friday when I will be
there again. Thanks!
Br. Kevin
--
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/1956177
Title:
battery
Unfortunately I get an "Operation not permitted" error when I try to run
acpidbg here. Is above command exactly as it should be entered? 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/bu
ations
This will give you a dsdt.aml that should work.
I did that with: sudo iasl -ta dsdt.dsl and got the aml file just with
warnings.
11) Proceed as above
sudo cp dsdt.aml /boot/
sudo cp 01_acpi /etc/grub.d/
chmod 755 01_acpi
sudo update-grub
reboot
Still just the same :/
Can anyone point me in
Test results for 510 are available at
https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing
Test results for 390 are available at
https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing
No regression foun
Public bug reported:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
please see the attachment.
[Info]
I tried glxgear before, it will use nvidia-driver, I can see it by nvidia-smi.
Since we define our test scope using firefox to check, so I report this bug.
Or should I add firefox as impacted package and remove linux package.
--
You received this bug notification because you are a member of Kerne
** Summary changed:
- Jammy didn't use nvidia driver whne executing firefox
+ Jammy didn't use nvidia driver when executing firefox
--
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/1967456
Public bug reported:
[Reproduce step]
1. Install Jammy beta.
2. Install Nvidia driver by ubuntu-driver install.
3. Connect monitor to dGPU output port.
4. Run firefox, type "about:support" in url, and check column "GPU #1"
[Expected result]
should see nvidia driver info.
[Actual result]
still
Please find test results at
https://docs.google.com/spreadsheets/d/1VtJNgxFU4sO8foPgzP2Q-g-flo2sSELecOJnS9pGKXM/edit?usp=sharing.
No regressions were found.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Thanks for the solution. I removed "nomodeset" from grub config and now
it detects external monitor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1961596
Title:
Ubuntu 20.04 w
According to test result at
https://certification.canonical.com/hardware/202002-27718/submission/245770/test-results/pass/?term=media.
This problem has been solved.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because yo
Also same issue with Asus PN50 Ryzen 5 4500U Bios 0623 (latest Bios) and
Mint version 20.3
Everything fine using version 5.11.0.46 but can't shut down/restart with
5.13.0.25 (even after waiting over ten minutes). sudo shutdown -h now
also doesn't work. Seems to reach (message) [OK] Reached Target
Test results for 495 are available at
https://docs.google.com/spreadsheets/d/14Kc4yMyGIqUr6oMGzqddlVcMMoY4qpq99crILaH58Os/edit?usp=sharing
Test results for 470 are available at
https://docs.google.com/spreadsheets/d/1kAo_Y8LFIDYY6skpkPGDCrNErG8-rN_ziQ0eJwmYDZ4/edit?usp=sharing
No regression were
You can find test results at
https://docs.google.com/spreadsheets/d/1bjCjuBFXykVvCb_NuxepUjJthqSiiiDQY854-Tqffyw/edit?usp=sharing
No regression were found.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubu
** Summary changed:
- Can't read/write SD card after running CPU offline test in 5.11.0-41.45
+ Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Importance: High => Medium
** Changed in: linux-signed-hwe-5.13 (Ubuntu)
1 - 100 of 507 matches
Mail list logo