** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
** Tags removed: verification-needed-lunar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024134
Title:
[SRU]
Hi Talha & Pallav,
Could you verify the package on mantic-proposed and add the tag
"verification-done-mantic" if this package fixes the bug for you.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Timo,
AMD-xilinx has verified the package on -proposed (Please see comment#20).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024134
Title:
[SRU] IMX274 Probe failure
To manage notifications
** Tags added: originate-from-2058873
--
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:
Hi Timo,
I'm still waiting for the feedback from AMD-Xilinx. PM highlighted it to
AMD-Xilinx. But, unfortunately, there is still no feedback. Will keep highlight
it and get back to you as soon as possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Get it. Thanks~
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051199
Title:
Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
To manage notifications about this bug go to:
Verified packages on noble and mantic/jammy-proposed.
1. noble: mt7663 WiFi/BT firmware are removed.
2. noble/mantic/jammy:
a. SCAN: Pass
b. connect to AP: Pass
c. ping test: Pass
3. checksum: Pass
$ md5sum /lib/firmware/mediatek/WIFI_*
0a4d833efe94a56c502de8a38405d8fe
Verified packages on matnic and jammy-proposed.
Platforms: g510 (mt8370), g1200 (mt8395), and g700 (mt8390).
1. Headset Jack Playback: Pass
2. Audio (Speaker) Jack Playback: Pass
3. HDMI TX Playback: Pass
4. mt8395-evk: HDMI RX: Pass
** Tags removed: verification-needed-jammy
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1977713/+attachment/5595042/+files/jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977713
Public bug reported:
[Impact]
Backport 3.104ubuntu10 to jammy
[Where problems could occur]
Backport 3.104ubuntu10 to jammy
[Test Case]
System can boot to kernel without any problems.
jammy + Xilinx Kria KR260/KV260 boards: Pass
jammy + Xilinx zcu102/104/106 boards: Pass
[Regression Potential]
@Łukas
Bump libegl-mali-xlnx's version on kinetic from 9p0.01rel0-1ubuntu2 to
9p0.01rel0-1-0ubuntu2 and then backport it to jammy. Any concern about
it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I verified xlnx-firmware (2022.1-1-0ubuntu1~22.04.1) on my zcu102.
boot1021.bin, boot1041.bin, boot1021.bin, boot1061.bin, boot.bin in
/boot/firmware get updated after upgrading xlnx-firmware to
2022.1-1-0ubuntu1~22.04.1. System can boot without any problems with new
bootX.bin.
** Tags
@Łukas
Sorry. I didn't aware that the second field is . AMD-
Xilinx got libraries and header files from ARM. The version number is
9p0.01rel0. AMD-Xilinx updated one header file but the upstream version
number in github[1] is still the same. The header file was not modified
by Canonical. So, I
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/1976230/+attachment/5593945/+files/jammy.debdiff
** Patch removed: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/1976230/+attachment/5593764/+files/jammy.debdiff
--
Re-create debdiff based on 9p0.01rel0-1ubuntu2 for jammy
** Patch removed: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libegl-mali-xlnx/+bug/1976225/+attachment/5593725/+files/jammy.debdiff
** Patch added: "jammy.debdiff"
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/1976230/+attachment/5593764/+files/jammy.debdiff
** Tags added: oem-priority originate-from-1966171
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
[Impact]
Backport 2022.1-1-0ubuntu1 to jammy
Update firmware to tag v2022.1_22.04_1
https://github.com/Xilinx/ubuntu-firmware/tree/v2022.1_22.04_1
[Where problems could occur]
Update firmware to tag v2022.1_22.04_1 as AMD-Xilinx's request
[Test Case]
jammy + Xilinx
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libegl-mali-xlnx/+bug/1976225/+attachment/5593725/+files/jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Update libegl-mali-xlnx as per AMD-Xilinx's request
+ [Impact]
+ Update the EGL headers as per AMD-Xilinx's request
- AMD-Xilinx want to update libegl-mali-xlnx to
+ [Where problems could occur]
+ Update the EGL headers as per AMD-Xilinx's request
+
+ [Test Case]
+
** Patch added: "kinetic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libegl-mali-xlnx/+bug/1976225/+attachment/5593724/+files/kinetic.debdiff
** Tags added: oem-priority originate-from-1971665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Update libegl-mali-xlnx as per AMD-Xilinx's request
AMD-Xilinx want to update libegl-mali-xlnx to
https://github.com/Xilinx/mali-userspace-binaries/tree/xilinx_v2022.1
(tag: xilinx_v2022.1)
** Affects: libegl-mali-xlnx (Ubuntu)
Importance: Undecided
Status:
Tried flash-kernel (3.103ubuntu1~20.04.4) on my Mediatek AIoT i500
board. The system can boot without any problem with new fitmage
generated by flash-kernel (3.103ubuntu1~20.04.4)
$ apt-cache policy flash-kernel | grep Installed
Installed: 3.103ubuntu1~20.04.4
** Tags removed:
Public bug reported:
The boot architecture on jammy changes.
The dtb files for Kria comes from linux package instead of xlnx-kria-
firmware. Confirmed with AMD-Xilinx that xlnx-kria-firmware is
unnecessary on jammy and we can remove it from jammy.
** Affects: xlnx-kria-firmware (Ubuntu)
@Łukasz
I have verified linux-firmware-mediatek-aiot (1-0ubuntu0~20.04.1) on my
Mediatek AIoT boards.
Here are my steps:
1. install linux-firmware
2. install linux-firmware-mediatek-aiot
3. remove linux-firmware
4. install linux-firmware
5. remove linux-firmware-mediatek-aiot
** Tags added:
** Description changed:
[Impact]
Add Mediatek AIoT i500 support
[Test Plan]
Install the test flash-kernel package with the fix, a file in path
Boot-FIT-Path will be created, and the system should be able to boot.
Test cases:
1. jammy + Xilinx Kria board: Pass
2. focal + Mediatek
Public bug reported:
[Impact]
linux-firmware-mediatek-aiot (1-0ubuntu1) is required for Mediatek AIoT 20.04
classic image.
Need to backport it to focal
[Test Case]
Install linux-firmware-mediatek-aiot on a Mediatek AIoT device. Check if
it can be co-installed with linux-firmware.
[Regression
@Heinrich
My patch for MTK i500 board is based on a patch[1] for fitimage support.
[1] wasn't upstreamed to [2]. So, I didn't send the MP to [2].
---
[1] https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1931987
[2] https://salsa.debian.org/installer-team/flash-kernel
--
You received
@Loïc
I'm working on an image which will support multiple Medaitek AIoT
boards. The dtbo files are for some external components like cameras and
panels. Mediatek would like to have these dtbo files in the fitimage.
These components are optional. When end-users have it, they can enable
it by
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+attachment/5563658/+files/focal.debdiff
** Tags added: oem-priority originate-from-1946212
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
[Impact]
Add Mediatek AIoT i500 support
[Test Plan]
Install the test flash-kernel package with the fix, a file in path
Boot-FIT-Path will be created, and the system should be able to boot.
Test cases:
1. jammy + Xilinx Kria board: Pass
2. focal + Mediatek AIoT i500 board:
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1962289/+attachment/5563657/+files/jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962289
** Tags removed: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958484
Title:
Add Python support for Vitis AI v1.3.2 package in focal
To manage notifications about this
@Łukasz
I uploaded debdiff for jammy.
When I built the test package for jammy, I got the following error messages.
So, I created a patch called build-with-std-gnu++17.patch to fix build failure.
Here is the error message when building the package without -std=gnu++17:
@Łukasz
I'm waiting for the feedback from Xilinx. The only thing I know at this moment
is that we will upgrade the package to newer version (1.4 or 2.0) before 22.04
stock ubnutu is released formally. Xilinx doesn't intend to support v1.3.2
package in Jammy. The package in formal Xilinx 22.04
The patch in comment#1 and test packages have been reviewed and verified
by Xilinx.
Here is the feedback from Xilinx:
I think this is good to go - my tests are working, and another one of our apps
guys tested with their larger application and it is working. You can move
forward with the SRU
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1958484/+attachment/740/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958484
Public bug reported:
[Impact]
* Xilinx wants to add python support for Vitis AI v1.3.2 package
The following files will be added after applying the patch for python support.
/usr/lib/python3/dist-packages/runner.py
/usr/lib/python3/dist-packages/vart.cpython-38-aarch64-linux-gnu.so
@Chris @Robie
Not sure whether I didn't explain well. Let me take u-boot as an
example.
There are several u-boot packages. These packages are soc-dependent.
When we modify common codes, we need to take other platforms into account and
make sure there is no regression issue on other platforms.
@Chris
Xilinx classic focal images[1][2] is the only one image released by Canonical.
It includes xf86-video-armsoc-endlessm (1.4.1-0ubuntu6~20.04ppa1) and a meta
package. (1.4.1-0ubuntu6~20.04ppa1) didn't be upstreamed because of the tight
schedule. This package has dropped
The issue is fixed by latest snapd and intel-kernel.
$ snap info snapd | grep stable
latest/stable: 2.53.2 2021-11-24 (14066) 44MB -
$ snap info intel-kernel | grep stable
20/stable: 5.13.0-1007.7.3 2021-11-18 (10) 309MB -
--
You received this bug notification because you are a member of
The issue is fixed by latest snapd and intel-kernel.
$ snap info snapd | grep stable
latest/stable: 2.53.2 2021-11-24 (14066) 44MB -
$ snap info intel-kernel | grep stable
20/stable: 5.13.0-1007.7.3 2021-11-18 (10) 309MB -
--
You received this bug notification because you are a member of
** Changed in: intel/lookout-canyon
Status: Triaged => 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/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Fail to install Ubuntu Core
** Changed in: intel/lookout-canyon
Status: Triaged => Fix Committed
** Changed in: ubuntu
Assignee: ethan.hsieh (ethan.hsieh) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@Robie
The image[1] released by Canonical for Xilinx boards is the only one
image which pre-loads this package. The users I mentioned are Xilinx
board users. Sorry, I didn't use words precisely.
xf86-video-armsoc-endlessm was created for Xilinx boards (zcu102/104/106
and Kria) with mali GPU.
@Robie
The version of xf86-video-armsoc-endlessm in the GM image[1][2] delivered to
Xilinx is 1.4.1-0ubuntu6~20.04ppa1.
This package has dropped Implement-platform-Probe-driver-call.patch.
1.4.1-0ubuntu6~20.04ppa1 is same as 1.4.1-0ubuntu8~20.04.
It didn't be upstreamed because of the tight
Confirmed that ap1302_ar0144_single_fw.bin and ap1302_ar1335_single_fw.bin[1]
in the package are same as what Xilinx needs.
The test has done by Xilinx. I just checked if checksum is correct.
---
[1] https://github.com/Xilinx/ap1302-firmware/tree/xilinx_v2021.1_update1
** Tags added:
@Robie
In this MP, Implement-platform-Probe-driver-call.patch is dropped
because it has a side effect which system cannot pass suspend/resume
test.
Implement-platform-Probe-driver-call.patch was added for LP: #1921153.
This patch is the solution of LP: #1921153. It forces to use root as the user
** Description changed:
[Impact]
Fail to pass suspend/resume test
[Test Case]
### Run suspend/resume stress test on Xilinx ZCU boards.
#/bin/bash
for i in {1..30};
do
echo "Iteration $i"
sudo rtcwake -v -m no -s 240
sudo systemctl suspend
debdiff for focal
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-xilinx-ap1302/+bug/1951216/+attachment/5541379/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We released focal desktop image[1] to Xilinx.
There are no use-cases right now for any series other than focal.
So, the target series for the package is focal only.
---
[1] https://ubuntu.com/download/xilinx
** Affects: linux-firmware-xilinx-ap1302 (Ubuntu)
Importance:
** Attachment added: "debdiff.focal-1103"
https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1948764/+attachment/5537868/+files/debdiff.focal-1103
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Robie
I uploaded new debdiff to update the referenced bug to public one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948764
Title:
Fail to pass suspend/resume test
To manage notifications
** Attachment added: "debdiff.jammy-1103"
https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1948764/+attachment/5537867/+files/debdiff.jammy-1103
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [intel] [tgl-h][iotg] [hwe-tpm] Fail to install Ubuntu Core on TGL-H when SM3
256 is enabled
+ [intel] [tgl-h][iotg] [hwe-tpm] Fail to install Ubuntu Core on TGL-H when
BIOS supports SM3 256
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- [ehl] Fail to install Ubuntu Core on EHL when SM3 256 is enabled
+ [ehl] Fail to install Ubuntu Core on EHL when BIOS supports SM3 256
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H
+ [intel] [tgl-h][iotg] [hwe-tpm] Fail to install Ubuntu Core on TGL-H when SM3
256 is enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- [ehl] Ubuntu Core boot fails on EHL
+ [ehl] Fail to install Ubuntu Core on EHL when SM3 256 is enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939505
Title:
[ehl] Fail
[Regression potential]
1. Fail to login to Ubuntu desktop environment
The issue can be fixed by the config below
/etc/X11/Xwrapper.config: needs_root_rights = yes
2. Canonical QA has ran graphic related test cases without any regression issue.
** Description changed:
[Impact]
Fail to pass
debdiff for jammy
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1948764/+attachment/5536137/+files/jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff for focal
** Patch added: "focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xf86-video-armsoc-endlessm/+bug/1948764/+attachment/5536138/+files/focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue is caused by Implement-platform-Probe-driver-call.patch in the
package.
This issue is gone after removing Implement-platform-Probe-driver-call.patch.
Have to force Xorg running as root after removing this patch.
/etc/X11/Xwrapper.config: needs_root_rights = yes
--
You received this
Will install snap-store snap instead of hiding the "apps" page.
** Changed in: gnome-initial-setup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942993
Title:
Public bug reported:
[Impact]
Fail to pass suspend/resume test
[Test Case]
### Run suspend/resume stress test on Xilinx ZCU boards.
#/bin/bash
for i in {1..30};
do
echo "Iteration $i"
sudo rtcwake -v -m no -s 240
sudo systemctl suspend
sleep 120
done
[Expected
** Changed in: ubuntu
Assignee: ethan.hsieh (ethan.hsieh) => (unassigned)
** Changed in: intel/lookout-canyon
Status: New => Triaged
** Changed in: ubuntu
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bu
I dumped binary_bios_measurements on a production board (Aaeon EHL) and didn't
see "UEFI Debug Mode" from the log. With snapd (2.53.1) and patched kernel
snap, I can install UC20 with FDE enabled without any problem.
For detailed log, please see attached file.
---
Board: Aaeon UPN-EHL01
BIOS:
The last page is "apps". Its apply[1] function will call gis_driver_quit() for
application exit.
After I add "apps" into the skip list in vendor.conf, the last page becomes
"privacy".
The "privacy" page doesn't call gis_driver_quit() to exit gnome-initial-setup.
I tried to workaround the issue
** Attachment added: "page-privacy.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1942993/+attachment/5523717/+files/page-privacy.png
** Tags added: oem-priority originate-from-1941009
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "page-apps.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1942993/+attachment/5523716/+files/page-apps.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
For the images which only pre-load ubuntu-desktop-minimal, snap-store
snap package isn't installed by default. The page "apps" should be
skipped.
I add "apps" into the skip list. But, I cannot close the window by
clicking "Done" button" after adding "apps" into the skip
Three ethernet chips can be detected by checkbox.
Network Information of device 1 (enp0s30f4)
Network Information of device 2 (enp0s30f5)
Network Information of device 3 (enp0s31f6)
But, need to confirm with Intel
1. Does TGL-H board only has one physical port?
2. Is the following error
There are three ethernet interfaces after installing latest test kernel.
But, I still can see following error message.
Error message:
[ 93.198160] intel-eth-pci :00:1e.4 enp0s30f4: validation of sgmii with
support 000,,6280 and advertisement 000,,
** Attachment added: "checkbox-test-resuilt.txt"
https://bugs.launchpad.net/intel/+bug/1936903/+attachment/5520703/+files/checkbox-test-resuilt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are three ethernet chips, but I only find one physical port on the board.
See some error messages on [8086:43ac] and [8086:43a2].
(Please see comment#7 & #8 for detailed log)
1. 00:1e.4 Ethernet controller: Intel Corporation Device 43ac
Kernel driver in use: intel-eth-pci
** Description changed:
[Summary]Some networking tests fail
[Steps to reproduce]Run Manual Non-Device Networking Tests
+ $ sudo snap install checkbox20
+ $ sudo snap install cdts --classic --channel=20.04/stable
+ $ cdts.checkbox-cli
+ (X) Networking tests (manual)
+ [X] + Non-device
** Attachment added: "lspci-v.txt"
https://bugs.launchpad.net/intel/+bug/1936903/+attachment/5520676/+files/lspci-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903
Title:
CDTS Network
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/intel/+bug/1936903/+attachment/5520675/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903
Title:
CDTS Network
@Chris
The files in comment#42 and #43: I dumped them in Ubuntu classic desktop
** Attachment added: "binary_bios_measurements"
https://bugs.launchpad.net/intel/+bug/1938678/+attachment/5519433/+files/binary_bios_measurements
--
You received this bug notification because you are a member
** Attachment added: "tpm2_pcrread.log"
https://bugs.launchpad.net/intel/+bug/1938678/+attachment/5519432/+files/tpm2_pcrread.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
Summary:
1. Still can reproduce the issue (#31) after deleting PK and enrolling
db/KEK/custom PK vis BIOS settings.
For details, please refer to #38 and [1].
2. Can install the uc20 test image[2][3] with TPM and secure boot enabled on
other x86 machines (not TGL-H and EHL).
And, I only
@Chris
I used another x86 machine on which I can install uc20 successfully with same
test image.
I enrolled the key by mokutil and re-installed uc20.
I got following error message:
taskrunner.go: 271: [change 2 "Setup system for run mode" task] failed: cannot
make system runnable: cannot seal
@Chris
I deleted and re-enrolled PK on another intel platform, EHL, and still saw same
error message.
For details, please refer to [1].
---
[1] https://bugs.launchpad.net/intel/+bug/1939505/comments/3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tried to install UC20 with TPM enabled and saw same error message[1] as
TGL-H.
EHL's BIOS doesn't support hash algorithm SHA384 and SM3_256.
For deails, please refer to attached photo.
BIOS version: EHLSFWI1.R00.3162.A01.2104131432
Here are steps:
1. Remove key enrolled by mokutil
2. Re-flash
@Chris
Are deleting and re-enrolling PK necessary?
I installed test image on another x86 machine successfully and just enrolled
"KEK" and "Signature".
It looks like comment#31 is a BIOS issue.
Could you give me some guidance on where to add debug message for clarifying
this issue?
--
You
Enroll KEK and Signature via BIOS settings but still get the same error message
(comment#31).
But, I can install the test image on another x86 machine and FDE is enabled
successfully.
Here are steps:
1. Remove key enrolled by mokutil
2. Re-flash uc20 test image
3. Enroll KEK and Signature via
@sachinmokashi
Are steps in comment#32 the correct way to clear TPM?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
Still can reproduce the issue in comment#31 after cleaning TPM with
following steps:
1. Go to BIOS settings
2. [Intel Advanced Menu][TPM Configuration][TCG2 Configuration][TPM2 Operation]
3. Select [TPM2 ClearControl(NO) + Clear]
4. Press F4 to save changes
5. Reboot device
--
You received this
@Chris
The encrypted partition is created after I enroll the signing key by
mokutil and enable secure boot.
But, I get new error message (For details, please refer to attached photo):
taskrunner.go: 271: [change 2 "Setup system for run mode" task] failed: cannot
make system runnable: cannot
@Chris
I backported your patches to secboot[1] and go-tpm2[2] which are currently
used[3] by snapd.
With test image which includes your patches, I can install uc20 when the hash
algorithm SM3 is enabled in BIOS.
But, the encrypted partition is still not created successfully because the test
@chaoqin
Tried the latest BIOS and ubuntu desktop image[1].
But, I didnt' see 0x0c03fe in dmesg log.
Do I need to enable USB-dw3 in BIOS? How to enable it in BIOS settings?
$ dmesg | grep -e c0330 -e c03fe
[1.043065] pci :00:14.0: [8086:4b7d] type 00 class 0x0c0330
$ sudo dmidecode -s
Tried latest desktop image[1]. USB-dw3 is enabled.
Here is the log:
u@tgl:~$ dmesg | grep 3fe
[ 21.103681] pci :00:0d.1: [8086:9a15] type 00 class 0x0c03fe
[ 21.199707] pci :00:14.1: [8086:43ee] type 00 class 0x0c03fe
u@tgl:~$ sudo modprobe dwc3_pci
u@tgl:~$ lspci -v
...
00:0d.1 USB
@sachinmokashi
I see. I'm trying to enable SM3 on go-tpm2.
Fixing the issue on crypto package, go-tpm2, and secboot is the right way to go.
But, It may take several weeks to enable it.
That is why I'm seeking for a short-term solution, having a BIOS option for
disabling SM3".
--
You received
** Description changed:
Installed focal-iotg-core-20210722.img on the TGL-H.
Boot process stops after it gets errors from TPM and fails to start an
emergency shell (see screen shot.)
I also tried to go into the BIOS to clear TPM, as this worked for the
EHL board but it still
@sachinmokashi
There are two fields in BIOS:
1. Hash Algorithm Bitmap
2. Active PCR Banks
The one you mentioned in comment#21 is "Active PCR Banks".
But, what I want to disable is "Hash Algorithm".
Current BIOS doesn't has an option to disable Hash Algorithm SM3 256.
Could Intel build a BIOS
@sachinmokashi
Could Intel build a BIOS with an option for disabling hash algorithm SM3
256?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Ubuntu
** Attachment added: "error_message.jpg"
https://bugs.launchpad.net/intel/+bug/1938678/+attachment/5517831/+files/error_message.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678
Title:
** Patch added: "0001-Add-support-for-hash-algorithm-SM3-256.patch"
https://bugs.launchpad.net/intel/+bug/1938678/+attachment/5517830/+files/0001-Add-support-for-hash-algorithm-SM3-256.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The latest go-tpm2[1] seems to support SM3_256.
I tried to build test snapd and kernel snaps but got a dependency issue.
The latest secboot[2] still uses old go-tpm2 API.
I applied the attached patch in comment#17 to go-tpm2[3] which is currently
used by snapd.
And, I built a test image with
** Description changed:
Installed focal-iotg-core-20210722.img on the TGL-H.
Boot process stops after it gets errors from TPM and fails to start an
emergency shell (see screen shot.)
I also tried to go into the BIOS to clear TPM, as this worked for the
EHL board but it still
https://github.com/canonical/go-
tpm2/commit/bd7cad4936577a496ebfca7272fef34c32e3bc0b
commit bd7cad4936577a496ebfca7272fef34c32e3bc0b
Author: Chris Coulson
Date: Tue Aug 10 17:46:55 2021 +0100
Use HashAlgorithmId instead of crypto.Hash in various places
Some recent commits
** Description changed:
Installed focal-iotg-core-20210722.img on the TGL-H.
Boot process stops after it gets errors from TPM and fails to start an
emergency shell (see screen shot.)
I also tried to go into the BIOS to clear TPM, as this worked for the
EHL board but it still
1 - 100 of 220 matches
Mail list logo
