Install and boot into the 6.11.0-1012.12 kernel and test with:
1. Running "bluetoothctl list" shows bluetooth controller exists
2. In the bluetoothctl shell, run "scan on". The controller is able to scan.
Turning off scanning show no errors. Neither does the device hang.
** Tags removed: verific
Tested the noble, oracular, plucky -proposed package with:
1. Download the deb from -proposed and install
2. Test built-in speakers and headphone by the "Sound->Test..." in the gnome
control center.
3. Test built-in mics and headphone mics by recording sound and replay.
For all -proposed packag
** Also affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Assignee: (unassigned) => Leo Lin (0xff07)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Description changed:
[ Impact ]
On some machine with Mediatek USB bluetooth controller, activate
scanning will lead to system hang. This is due to unexpected null
pointer dereference in the set up flow.
[ Fix ]
Cherry-pick one commit from mainline linux:
- 61c5a3def9
** Changed in: linux-oem-6.11 (Ubuntu)
Assignee: (unassigned) => Leo Lin (0xff07)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092473
Title:
[SRU] Fix system hang issue caused by the bt
** Summary changed:
- [SRU] Fix system hang issue caused by the MT7920 driver
+ [SRU] Fix system hang issue caused by the btmtk driver
** Tags added: jira-delta-107 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Public bug reported:
[ Impact ]
On some machine with Mediatek USB bluetooth controller, activate
scanning will lead to system hang. This is due to unexpected null
pointer dereference in the set up flow.
[ Fix ]
Cherry-pick one commit from mainline linux:
61c5a3def90a (Bluetooth: btmtk: adj
Tested on the machine where this issue originally happened. The error
message no longer show.
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Boot into an ARL machine with this kernel. The previously non-existent
/sys/kernel/debug/pmc_core directory appears.
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a member of
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092001
Title:
[SRU] Add Arrow Lake U/H support to the intel_pmc_core driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/hw
Tested on one of the said AMD platforms. Boot into the platform and the
PMF driver probe function will return early as expected, showing the
expected message in the kernel log.
** Summary changed:
- Prefer BIOS over PMF on some AMD platforms
+ [SRU] Prefer BIOS over PMF on some AMD platforms
**
** Tags added: jira-stella-369 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092384
Title:
[SRU] Introduce support for RTL8125BPH 2.5 GbE controller.
To manage notifications about thi
Public bug reported:
[ Impact ]
RTL8125BPH 2.5 GbE controller is not functional.
[ Fix ]
This introduce support for RTL8125BPH 2.5 GbE controller by adding:
1. linux-firmware (already upstreamed[1]).
2. Driver patch[2], which is expected to have an v2.
[ Test ]
1. Install the linux-firmware
** Description changed:
[ Impact ]
This patch series introduce support for Arrow Lake U/H platforms.
[ Test ]
1. Boot the kernel on Arrow Lake platforms
2. The /sys/kernel/debug/pmc_core directory should exist.
3. Running the S0ixSelftest Tool. The tool should report tha
Public bug reported:
[ Impact ]
This patch series introduce support for Arrow Lake U/H platforms.
[ Test ]
1. Boot the kernel on Arrow Lake platforms
2. The /sys/kernel/debug/pmc_core directory should exist.
3. Running the S0ixSelftest Tool. The tool should report that:
1) "The pmc_core
** Summary changed:
- [SRU] Fix error messages during optional AMDGPU firmware load
+ [SRU] Fix unnecessary error messages during optional AMDGPU firmware load
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
[ Impact ]
Currently, when the amdgpu driver tries to load firmware that is
optional and fails, it emits error:
Direct firmware load for amdgpu/%s.bin failed with error -2
In the situations where the firmware is optional, this should be treated
as false alarm. The d
** Also affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
[ Impact ]
Some AMD platforms prefer letting BIOS handling what are supposed to be
done by the PMF kernel driver. On those platforms, the BIOS should take
full control over the relevant functions, without the interference from
the PMF driver. To achieve this, add quirks that
Tested by ODM on their machines. Built-in speakers and built-in
microphones function normally on the 6.11.0-1010.10 kernel.
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a memb
Both FE and ODM verified that with the 6.11.0-1010.10 kernel there's no
beep sound on boot.
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Also affects: linux-oem-6.11 (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.11 (Ubuntu Plucky)
Status: New => Invalid
** Changed in: linux-oem-6.11 (Ubuntu
** Description changed:
[ Impact ]
- Some platforms with cs42l43 need new match entries to make audio
- function normally. Add those entries accordingly.
+ Some platforms with cs42l43 need new match entries and linux-firmware to
+ make audio function normally. Add those entries accordingly.
The firmware has already landed in upstream linux-firmware. Switch
status of Plucky to fix released:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/cirrus?id=3f08f27090e214b2c61ce43caffccf3802cde14a
** Also affects: linux-firmware (Ubuntu)
Importance: Undec
Tested under both Intel and AMD platforms, with the following procedure:
1. Check speaker playback by playing video using firefox.
2. Make sure left and right channel function normally with gnome control center.
3. Record sound with speaker and playback. Confirm that it can record.
4. Reproduce th
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Status: Won't Fix => New
** Changed in: linux-oem-6.11 (Ubuntu Plucky)
Status: Invalid => New
** Changed in: linux (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
B
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089644
Title:
Support cs42l43 on some platforms
To manage notifications a
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu
** Tags added: jira-wtn-131 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089811
Title:
Set PCBeep to default value for ALC274
To manage notifications about this bug go to:
https://bu
Public bug reported:
[ Impact ]
Some machines with ALC274 may play out extremely loud beep noise on
boot, due to the fact that the BIOS enables the PC beep path and leave
it into the OS.
[ Fix ]
Cherry-pick the following commit:
155699ccab7c78cb (ALSA: hda/realtek: Set PCBeep to default value
Public bug reported:
[ Impact ]
Some platforms with cs42l43 need new match entries to make audio
function normally. Add those entries accordingly.
[ Test ]
Install the test kernel
Install proper linux-firmware and firmware-sof
Confirm the audio function normally on the DUT:
* Checkbox a
** Description changed:
[ Impact ]
This patch series introduce soundwire support for AMD platform, as well
as code reorganization in preparation for that.
[ Test ]
1. Install the test kernel
2. Install proper alsa-ucm-confs
3. Confirm the audio function normally on the DUT w
** Description changed:
- Add non-sof soundwire support to AMD platforms
-
[ Impact ]
This patch series introduce soundwire support for AMD platform, as well
as code reorganization in preparation for that.
[ Test ]
1. Install the test kernel
2. Install proper alsa-ucm-confs
Public bug reported:
Add non-sof soundwire support to AMD platforms
[ Impact ]
This patch series introduce non-sof soundwire support for AMD platform,
as well as code reorganization in preparation for that.
[ Test ]
1. Install the test kernel
2. Install proper alsa-ucm-confs
3. Confirm the aud
** Summary changed:
- Add non-sof soundwire support to AMD platforms
+ Add soundwire support for AMD platforms
** Description changed:
Add non-sof soundwire support to AMD platforms
[ Impact ]
This patch series introduce non-sof soundwire support for AMD platform,
as well as code r
I obeserved the dbus method call on Noble with:
$ sudo dbus-monitor --system "type='method_call'"
For g-c-c, it simply powers on the adapter:
method call time=1727343233.473107 sender=:1.134 -> destination=:1.9 serial=69
path=/org/bluez/hci0; interface=org.freedesktop.DBus.Properties; member
** Description changed:
[Description]
Since Noble, turning Bluetooth slider on ON after toggling it OFF for
~1min seems to only power on and unblock rfkill on the controller, but
not enable scanning. This makes the "Devices" list shows no devices, as
if the controller wasn't functioni
** Description changed:
- Since Noble, toggling the Bluetooth slider repeatedly and leaving at the
- ON state seems to only power on and unblock rfkill on the controller,
- but not enable scanning. This makes the "Devices" list shows no devices,
- as if the controller wasn't functioning.
+ [Descri
** Tags added: jira-wtn-5 oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081672
Title:
Scanning not enabled by the Bluetooth slider
To manage notifications about this bug go to:
https:
Public bug reported:
Since Noble, toggling the Bluetooth slider repeatedly and leaving at the
ON state seems to only power on and unblock rfkill on the controller,
but not enable scanning. This makes the "Devices" list shows no devices,
as if the controller wasn't functioning.
This is observable
Tested on a previous failed HP machine with both Noble and Jammy.
Installed the proposed linux-firmware and run the obex_send test case.
Both can pass the test now.
** Tags added: verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ub
[ Regression Test Plan - Nvidia+LUKS ]
Tested on a HP desktop machine with Nvidia graphic card with 550.107.02
driver
1. Install the stock 24.04.1 image fresh (with the additional drivers option
selected) and enabled disk encryption.
2. Install the proposed ubuntu-drivers-common after booting in
Hi @zorro-zhang. Could you share how you tested it? I tried on both Dell
and HP platforms on Noble, and none of them seemed to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966635
Title:
can'
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072858
Title:
Fix L2CAP/LE/CPU/BV-02-C bluetooth certific
Enable -proposed on the same machine and install the 6.8.0-43 kernel. It
passed both L2CAP/LE/CPU/BV-02-C and GAP/CONN/CPUP/BV-05-C.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Ubu
L2CAP/LE/CPU/BI-02-C should be corrected as L2CAP/LE/CPU/BV-02-C. The
former one is not included in the test scope.
** Summary changed:
- Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure
+ Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
** Description changed:
SRU Jusitifica
** Description changed:
SRU Jusitification for Kernel
[Impact]
Noble failed the L2CAP/LE/CPU/BI-02-C test in the Porfile Tuning Suite
- (PTS), which Jammy could pass.
+ (PTS), which Jammy previously could pass.
This is due to new behavior introduced in
e4b019515f950b4e6e5b74b2e1
** Tags added: jammy noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072858
Title:
Fix L2CAP/LE/CPU/BI-02-C bluetooth certification failure
To manage notifications about this bug go to:
https:
buntu)
Importance: Undecided
Assignee: Leo Lin (0xff07)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Leo Lin (0xff07)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Tags added: oem-priority originate-from-2071758 stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia drive
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this
My bad not realizing that non-LTS versions are not maintained on salsa.
This is the debdiff for mantic.
** Patch added: "libfprint_1.94.6+tod1-0ubuntu3.1~testing1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2058193/+attachment/5772864/+files/libfprint_1.94.6+tod1-0ubuntu3
With snapd 2.61.3 now in -update, this issue no longer appear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go
Tested on the machines with the said fingerprint hardware using the
following procedures:
1. Enable the -proposed channel
2. Install 1:1.94.3+tod1-0ubuntu2~22.04.07 version of libfprint-2-2, which is
the one in the -proposed channel
3. Reboot the machine
4. After the reboot, confirm that fingerpr
** Tags added: originate-from-2058698
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
https://bugs.launchp
Installed the 2.0-1ubuntu4.7 version of firmware-sof-signed on the
previously failed HP platform. Confirmed that now the LEDs can toggle
accordingly.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member o
** Tags added: originate-from-2058620
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
https://bugs.launchp
@mschiu77 the firmware-sof provided in your PPA works! The LEDs can
toggle accordingly after installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Del
** Tags added: originate-from-2058002
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
https://bugs.launchp
The firmware-sof-signed in -proposed doesn't seem to fix the LEDs at
least on one HP platform. Reading the file from /sys/class/sound/ctl-
led/mic/card0/list shows nothing.
The md5sum of sof-ace-tplg/sof-hda-generic-2ch.tplg also doesn't match
the one in upstream v2023.12.1 release.
# From upstre
Public bug reported:
[Impact]
LEDs on both mute and mic-mute key are not working on a HP platform.
[Fix]
The quirk in the commit b2d6a1fd0e3e513f5ebfc152d6fedae093df8e21 (ALSA:
hda/realtek: Add quirks for HP G11 Laptops using CS35L56) in linux-next can
make it work.
[Test]
1. Install the v2023
Salsa MP: https://salsa.debian.org/ubuntu-dev-
team/libfprint/-/merge_requests/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058193
Title:
Support Synaptics fingerprint device with ID [06CB:0106
` and enable `Fingerprint Login`
* Enroll finger and then logout
* Login system with enrolled finger
[Where problems could occur]
* If the vendor uses the same ID for other devices, the new device may
not work properly.
** Affects: oem-priority
Importance: Critical
Assignee: Leo Lin
** Tags added: originate-from-2057727
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
https://bugs.launchp
** Tags added: originate-from-2057476 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
https://b
** Tags added: oem-priority originate-from-2057436 stella
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057491
Title:
debsums for snapd 2.61.2 failed
To manage notifications about this bug go to:
** Attachment added: "oemlogs-ubuntu-20240313104942+0800.apport.gz"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2057491/+attachment/5755407/+files/oemlogs-ubuntu-20240313104942+0800.apport.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Running the debsums over snapd:
$ debsums snapd
will show the file io.snapcraft.Prompt.service missing:
debsums: missing file
/usr/share/dbus-1/services/io.snapcraft.Prompt.service (from snapd
package)
The snapd versions:
$ snap version
snap2.61.2
Verified that the GAP/CONN/CPUP/BV-05-C could pass on 5.15.0-102.112
kernel using the following procedure:
1. On PTS, switch to the LE-only dongle
2. On the IUT, run bluetoothctl
3. On PTS, start the test case.
4. On the IUT, in the bluetoothctl shell, start scanning by entering "scan on".
5. Whe
** Changed in: oem-priority
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049838
Title:
Mute/mic LEDs no function on HP ZBook
To manage notifications abou
70 matches
Mail list logo
