Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5032 Discussions

Intel i40e-2.25.9 Driver Unable to Compile on Ubuntu 20.04.6 LTS

huangtf
Beginner
700 Views

Hello IntelSupports,

 

 

 

Recently, we are encountering the following error:

 

 

 

root@ps:/# ethtool -i eno1

driver: i40e

version: 2.8.20-k

firmware-version: 4.11 0x80001da4 1.2527.0

expansion-rom-version:

bus-info: 0000:60:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# ethtool -i eno2

driver: i40e

version: 2.8.20-k

firmware-version: 4.11 0x80001da4 1.2527.0

expansion-rom-version:

bus-info: 0000:60:00.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# ethtool eno1

Settings for eno1:

       Supported ports: [ ]

       Supported link modes:   1000baseT/Full

       Supported pause frame use: Symmetric Receive-only

       Supports auto-negotiation: Yes

       Supported FEC modes: Not reported

       Advertised link modes:  1000baseT/Full

       Advertised pause frame use: No

       Advertised auto-negotiation: Yes

       Advertised FEC modes: Not reported

       Speed: Unknown!

       Duplex: Unknown! (255)

       Port: Other

       PHYAD: 0

       Transceiver: internal

       Auto-negotiation: off

       Supports Wake-on: g

       Wake-on: g

       Current message level: 0x00000007 (7)

                            drv probe link

       Link detected: no

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# ethtool eno2

Settings for eno2:

       Supported ports: [ ]

       Supported link modes:   1000baseT/Full

       Supported pause frame use: Symmetric Receive-only

       Supports auto-negotiation: Yes

       Supported FEC modes: Not reported

       Advertised link modes:  1000baseT/Full

       Advertised pause frame use: No

       Advertised auto-negotiation: Yes

       Advertised FEC modes: Not reported

       Speed: Unknown!

       Duplex: Unknown! (255)

       Port: Other

       PHYAD: 0

       Transceiver: internal

       Auto-negotiation: off

       Supports Wake-on: g

       Wake-on: g

       Current message level: 0x00000007 (7)

                            drv probe link

       Link detected: no

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# modinfo i40e

filename:       /lib/modules/5.4.0-186-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko

version:        2.8.20-k

license:        GPL v2

description:    Intel(R) Ethernet Connection XL710 Network Driver

author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>

srcversion:     FD9D26E4D59C9FAA886B58C

alias:          pci:v00008086d0000158Bsv*sd*bc*sc*i*

alias:          pci:v00008086d0000158Asv*sd*bc*sc*i*

alias:          pci:v00008086d00000D58sv*sd*bc*sc*i*

alias:          pci:v00008086d00000CF8sv*sd*bc*sc*i*

alias:          pci:v00008086d00001588sv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D3sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D2sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D1sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D0sv*sd*bc*sc*i*

alias:          pci:v00008086d000037CFsv*sd*bc*sc*i*

alias:          pci:v00008086d000037CEsv*sd*bc*sc*i*

alias:          pci:v00008086d0000104Fsv*sd*bc*sc*i*

alias:          pci:v00008086d0000104Esv*sd*bc*sc*i*

alias:          pci:v00008086d000015FFsv*sd*bc*sc*i*

alias:          pci:v00008086d00001589sv*sd*bc*sc*i*

alias:          pci:v00008086d00001586sv*sd*bc*sc*i*

alias:          pci:v00008086d00001585sv*sd*bc*sc*i*

alias:          pci:v00008086d00001584sv*sd*bc*sc*i*

alias:          pci:v00008086d00001583sv*sd*bc*sc*i*

alias:          pci:v00008086d00001581sv*sd*bc*sc*i*

alias:          pci:v00008086d00001580sv*sd*bc*sc*i*

alias:          pci:v00008086d00001574sv*sd*bc*sc*i*

alias:          pci:v00008086d00001572sv*sd*bc*sc*i*

depends:       

retpoline:      Y

intree:         Y

name:           i40e

vermagic:       5.4.0-186-generic SMP mod_unload modversions

sig_id:         PKCS#7

signer:         Build time autogenerated kernel key

sig_key:        3D:DE:1F:A2:01:D5:6F:06:6C:13:A3:D9:4F:4B:6D:82:EC:91:00:AD

sig_hashalgo:   sha512

signature:      A0:2D:EE:39:91:A8:5E:BD:36:4C:3A:BF:7B:DB:D1:E1:26:04:0D:39:

              52:92:64:C9:48:1C:2E:EF:2C:3D:DA:65:CE:CC:03:34:5E:CC:46:C5:

              5F:E4:7F:81:8F:A9:55:45:E3:7E:93:A6:39:47:CE:25:3C:29:9B:55:

              B9:12:92:28:30:66:82:EC:FF:14:B5:B7:F1:B9:0E:1C:09:0A:82:BD:

              28:8B:66:75:77:DF:EF:6D:59:E2:1B:D5:F4:CE:1E:BA:F2:48:2C:A2:

              20:E0:27:C9:13:BF:6C:0B:17:4D:B0:1F:2D:29:A4:83:C3:98:6A:2A:

              E4:E3:B4:56:77:D3:4A:30:00:2D:7A:40:96:A0:B6:5C:7F:CE:9A:12:

              AB:15:A0:C4:9B:1F:CC:96:51:A8:40:2F:BB:9F:CC:F9:EC:DD:2B:44:

              7A:88:66:F6:26:C2:2A:29:AE:DB:ED:62:68:1F:C6:41:69:CC:67:AE:

              3D:9B:2D:2D:CC:1E:8F:95:90:3B:80:E8:F2:85:85:94:57:48:E5:E7:

              F4:9F:0B:B5:E9:52:F9:C8:44:28:E7:4C:C6:18:28:F7:AB:77:F9:EC:

              99:DB:6F:11:DF:CC:A0:EB:5D:FC:FF:E3:80:FF:09:EF:9D:54:2B:B7:

              75:39:5F:65:52:10:A8:08:F5:74:40:5F:68:0C:D1:D1:BF:47:CD:75:

              B3:17:1C:2B:3A:BD:8C:2E:E3:A5:0B:07:83:34:60:35:54:28:A5:23:

              18:EB:CA:6C:87:92:9D:B2:DE:B6:08:88:8F:B2:44:DE:95:1A:42:6C:

              B2:5E:B3:0E:8C:73:2E:63:87:C0:3B:3E:D4:67:E5:C6:00:16:99:AD:

              6C:34:3C:AE:84:BF:36:06:6A:4C:42:2F:11:51:90:13:8A:91:98:6B:

              E5:70:E5:E1:03:40:7F:4D:47:31:B1:D9:8F:12:14:7B:FC:E8:F2:44:

              B2:9A:45:7C:C8:79:D6:36:79:A6:D1:CD:65:A3:67:8C:5B:7D:04:CF:

              35:5D:4B:EF:FB:80:9D:B3:3B:29:32:56:E0:14:70:A9:5F:8C:CE:B9:

              19:7B:95:D8:A4:92:7D:BA:63:F5:2C:EA:3B:C3:E9:8E:C3:68:F8:40:

              AA:4E:A9:4E:EA:34:B1:3E:10:3A:A0:2E:86:10:AE:CF:51:5C:2E:F7:

              15:A7:8B:99:87:DD:D4:5F:DB:E5:CC:7E:88:A6:6D:CD:93:48:79:C9:

              CF:8E:10:0E:B2:C2:62:91:AB:1E:04:26:9D:5D:D6:F1:86:F1:2C:C6:

              AE:7A:CF:44:D6:96:75:F1:A5:D8:F9:A8:DB:B0:2D:DD:EA:AC:D7:61:

              53:24:E0:2E:0B:29:8A:4D:12:0B:56:C9

parm:           debug:Debug level (0=none,...,16=all), Debug mask (0x8XXXXXXX) (uint)

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# lspci -k | grep Ethernet -A2

60:00.0 Ethernet controller: Intel Corporation Ethernet Connection X722 for 1GbE (rev 09)

       Subsystem: Super Micro Computer Inc Ethernet Connection X722 for 1GbE

       Kernel driver in use: i40e

       Kernel modules: i40e

60:00.1 Ethernet controller: Intel Corporation Ethernet Connection X722 for 1GbE (rev 09)

       Subsystem: Super Micro Computer Inc Ethernet Connection X722 for 1GbE

       Kernel driver in use: i40e

       Kernel modules: i40e

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000

    link/ether 3c:ec:ef:83:80:3a brd ff:ff:ff:ff:ff:ff

3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000

    link/ether 3c:ec:ef:83:80:3b brd ff:ff:ff:ff:ff:ff

root@ps:/#

root@ps:/#

root@ps:/#

root@ps:/# nmcli dev status

DEVICE  TYPE      STATE        CONNECTION

eno1    ethernet  unavailable  --        

eno2    ethernet  unavailable  --        

lo      loopback  unmanaged    --        

root@ps:/#

 

 

 

The Intel Corporation Ethernet Connection X722 is not driven successfully, and thus the wired network can’t be used. We deduce that it may be due to the LOWER_VERSION (2.8.20-k) i40e driver. However, we meet the error “The target kernel has CONFIG_MODULE_SIG_ALL enabled, but the signing key cannot be found. Module signing has been disabled for this build.” during the “make” operation in command line.

 

 

 

user@ps:~/i40e-2.25.9/src$ make

*** The target kernel has CONFIG_MODULE_SIG_ALL enabled, but

*** the signing key cannot be found. Module signing has been

*** disabled for this build.

make[1]: Entering directory '/usr/src/linux-headers-5.4.0-186-generic'

/home/user/i40e-2.25.9/src/Makefile:39: 2

  CC [M]  /home/user/i40e-2.25.9/src/i40e_main.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_ethtool.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_xsk.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_adminq.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_common.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_hmc.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_lan_hmc.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_nvm.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_debugfs.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_diag.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_txrx.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_ptp.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_filters.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_ddp.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_client.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_virtchnl_pf.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_dcb.o

  CC [M]  /home/user/i40e-2.25.9/src/i40e_dcb_nl.o

  CC [M]  /home/user/i40e-2.25.9/src/kcompat.o

  CC [M]  /home/user/i40e-2.25.9/src/kcompat_vfd.o

  LD [M]  /home/user/i40e-2.25.9/src/i40e.o

  CC [M]  /home/user/i40e-2.25.9/src/auxiliary.o

  LD [M]  /home/user/i40e-2.25.9/src/intel_auxiliary.o

/home/user/i40e-2.25.9/src/Makefile:39: 2

  Building modules, stage 2.

  MODPOST 2 modules

  CC [M]  /home/user/i40e-2.25.9/src/i40e.mod.o

  LD [M]  /home/user/i40e-2.25.9/src/i40e.ko

  CC [M]  /home/user/i40e-2.25.9/src/intel_auxiliary.mod.o

  LD [M]  /home/user/i40e-2.25.9/src/intel_auxiliary.ko

make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-186-generic'

user@ps:~/i40e-2.25.9/src$

 

 

 

Please help us to compile i40e-2.25.9 and let Intel Ethernet Connection X722 driven successfully. Thanks a lot!

 

 

 

Regards,

 

huangtf

 

China

0 Kudos
1 Solution
Ragulan_Intel
Employee
348 Views

Hi HuangTf,


Good day to you.


Please be informed that compiling the driver is done by the usage of "make install", this will create the .ko module and Kernel-devel is for RedHat based distros.


Besides that, we have found these instructions for the headers in Ubuntu: https://www.tecmint.com/install-kernel-headers-in-ubuntu-and-debian/


Installing the headers should fill in the necessary information for "/lib/modules/'uname -r'/build" automatically and libelf may not be necessary, it is only needed on some Kernel/Architecture combinations.


We hope this clarifies.


Regards,

Ragulan_Intel


View solution in original post

0 Kudos
11 Replies
Ragulan_Intel
Employee
647 Views

Hi Huangtf,


Hope you are doing well.


Thank you for reaching out to Intel Community.


As pertaining your issue, kindly please take note that this release includes the Intel public key to allow you to authenticate the signed driver in secure boot mode. To authenticate the signed driver, you must place Intel's public key in the UEFI Secure Boot key database.


Besides that, make sure the package "kernel-devel" with the same kernel version installed and also let us know whether are you using Intel server?


Regards,

Ragulan_Intel


0 Kudos
huangtf
Beginner
553 Views

Hi Ragulan_Intel,

 

 

Hope you are doing well.

 

 

Thank you very much for your last reply! Your words enlighten us to read the readme file carefully, and we have six questions.

 

 

Question 1:

Words (line 18 ~ line 23) from readmefirst.txt on the i40e-2.25.9 download web page:

    18  This release includes RPM packages that contain:

    19  * Device driver signed with Intel's private key in precompiled kernel module

    20  form

    21  * RDMA driver

    22  * Complete source code for above drivers

    23  * Intel's public key

 

 

Words from your last reply:

Besides that, make sure the package "kernel-devel" with the same kernel version installed and also let us know whether are you using Intel server?

 

 

Our operations in command line:

 

user@ps:~/user$ uname -r
5.4.0-186-generic
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$ lscpu | head -15
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
Address sizes:                      46 bits physical, 48 bits virtual
CPU(s):                             96
On-line CPU(s) list:                0-95
Thread(s) per core:                 2
Core(s) per socket:                 24
Socket(s):                          2
NUMA node(s):                       2
Vendor ID:                          GenuineIntel
CPU family:                         6
Model:                              85
Model name:                         Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
Stepping:                           4
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$ tar zxf i40e-2.25.9.tar.gz
user@ps:~/user$ cd i40e-2.25.9
user@ps:~/i40e-2.25.9$ find -name *.der
user@ps:~/i40e-2.25.9$ find -name *.cer
user@ps:~/i40e-2.25.9$
user@ps:~/i40e-2.25.9$
user@ps:~/i40e-2.25.9$

 

 

 

Intel's public key should be .der or .cer file, however, such file can’t be found in the i40e-2.25.9 directory. Why?

 

 

Question 2:

Words (line 18 ~ line 23) from readmefirst.txt on the i40e-2.25.9 download web page:

    18  This release includes RPM packages that contain:

    19  * Device driver signed with Intel's private key in precompiled kernel module

    20  form

    21  * RDMA driver

    22  * Complete source code for above drivers

    23  * Intel's public key

 

 

Words from your last reply:

Besides that, make sure the package "kernel-devel" with the same kernel version installed and also let us know whether are you using Intel server?

 

 

Words (line 303 ~ line 313) from README file in the i40e-2.25.9 directory:

   303  To build a binary RPM package of this driver

   304  --------------------------------------------

   305

   306  Note:

   307

   308    RPM functionality has only been tested in Red Hat distributions.

   309

   310  1. Run the following command, where "<x.x.x>" is the version number

   311     for the driver tar file:

   312

   313        rpmbuild -tb i40e-<x.x.x>.tar.gz

 

 

Our operations in command line: 

 

user@ps:~/user$ rpmbuild -tb i40e-2.25.9.tar.gz
error: Failed build dependencies:
	kernel-devel is needed by i40e-2.25.9-1.x86_64
user@ps:~/user$
user@ps:~/user$
user@ps:~/user$

 

 

 

We should install the "kernel-devel" package, make sure the package "kernel-devel" with the same kernel version installed, and then, build RPM package. Do you think so?

 

 

Question 3:

Words (line 18 ~ line 23 and line 38 ~ line 41) from readmefirst.txt on the i40e-2.25.9 download web page:

    18  This release includes RPM packages that contain:

    19  * Device driver signed with Intel's private key in precompiled kernel module

    20  form

    21  * RDMA driver

    22  * Complete source code for above drivers

    23  * Intel's public key

 

    38  - If you decide to recompile the .ko module from the provided source files, the

    39  new .ko module will not be signed with any key. To use this .ko module in

    40  Secure Boot mode, you must sign it yourself with your own private key and add

    41  your public key to the UEFI Secure Boot key database.

 

 

Words (line 220 and line 303) from README file in the i40e-2.25.9 directory:

   220  To manually build the driver

   303  To build a binary RPM package of this driver

 

 

Words from your last reply:

As pertaining your issue, kindly please take note that this release includes the Intel public key to allow you to authenticate the signed driver in secure boot mode. To authenticate the signed driver, you must place Intel's public key in the UEFI Secure Boot key database.

 

 

There are two pathways to install the i40e-2.25.9.tar.gz, “make” or “rpm”, to us, Ubuntu 20.04.6 LTS, 5.4.0-186-generic, and Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz, which is better?

 

 

Question 4:

If choose “make”, it is puzzled that whether we should install the "kernel-devel" package, make sure the package "kernel-devel" with the same kernel version installed?

 

 

Question 5:

If choose “make”, it means that we decide to recompile the .ko module from the provided source files, the new .ko module will not be signed with any key. To use this .ko module in Secure Boot mode, we must sign it ourselves with our own private key and add our public key to the UEFI Secure Boot key database. Do you think we get it?

 

 

Question 6:

Words (line 38 ~ line 41) from readmefirst.txt on the i40e-2.25.9 download web page:

    38  - If you decide to recompile the .ko module from the provided source files, the

    39  new .ko module will not be signed with any key. To use this .ko module in

    40  Secure Boot mode, you must sign it yourself with your own private key and add

    41  your public key to the UEFI Secure Boot key database.

 

 

If “make” means that we decide to recompile the .ko module from the provided source files, would you like to give us some operation commands to complete the operations “sign it yourself with your own private key and add your public key to the UEFI Secure Boot key database.”?

 

 

Regards,

 

Huangtf

 

 

0 Kudos
Ragulan_Intel
Employee
535 Views

Hi HuangTf,


Warm greetings and good day to you.


Thanks for your feedback. As for your queries, kindly allow us some time to check this internally and we will get back to you as soon as possible.


Regards,

Ragulan_Intel


0 Kudos
Subhashish
Employee
462 Views

Hello HuangTf,


Greetings!!


If you go to the download center for this driver:

https://www.intel.com/content/www/us/en/download/18026/intel-network-adapter-driver-for-pcie-40-gigabit-ethernet-network-connections-under-linux.html

You can download the key (intel-public-key-i40e-ko.zip), it is a .rsa file.


The rpm files provided are for RHEL only, and the instructions in the README that is in the tar file download say that RPM has only been tested on RHEL.


You will likely need to compile the driver to a .ko module.

The README has instructions for this as well and shows this note...


NOTES:


- To compile the driver on some kernel/arch combinations, you may need to


install a package with the development version of libelf (e.g. libelf-dev,


libelf-devel, elfutils-libelf-devel).


- When compiling an out-of-tree driver, details will vary by distribution.


However, you will usually need a kernel-devel RPM or some RPM that provides the


kernel headers at a minimum. The RPM kernel-devel will usually fill in the link


at /lib/modules/'uname -r'/build.




Here are some instructions I found on signing:

https://ubuntu.com/blog/how-to-sign-things-for-secure-boot



Hope this information helps!




Regards,

Subhashish_Intel.


0 Kudos
Subhashish
Employee
406 Views

Hello  HuangTf,


Greetings!!


This is just a follow up on the ongoing issue reported with us. We just wanted to know if you got the opportunity to review the information shared in our last post and if you have any doubts/queries regarding the same.


Looking forward to hear from you.




Regards,

Subhashish.


0 Kudos
huangtf
Beginner
376 Views

Hello Subhashish_Intel,

 

 

Warm greetings and good day to you.

 

 

Thanks a lot for your last reply! We have read your words carefully, and have two questions to consult.

 

 

Question 1:

 

"You will likely need to compile the driver to a .ko module." means we need to:

 

(1) build the driver manually with the usage of “make install”.

 

(2) install a package with the development version of libelf (e.g. libelf-dev, libelf-devel, elfutils-libelf-devel).

 

(3) install kernel-devel package.

 

Do you think so?

 

 

Question 2:

The RPM kernel-devel will usually fill in the link at "/lib/modules/'uname -r'/build".

 

Is it means that kernel-devel package will be automatically put in the "/lib/modules/'uname -r'/build" directory?

 

 

Regards,

 

HuangTf

 

0 Kudos
Simon-Intel
Employee
368 Views

Hi HuangTf,


Thank you for your response.


Please allow us some time to check this with the internal team, and we will get back to you as soon as we have an update.


Best regards,

Simon


0 Kudos
Ragulan_Intel
Employee
349 Views

Hi HuangTf,


Good day to you.


Please be informed that compiling the driver is done by the usage of "make install", this will create the .ko module and Kernel-devel is for RedHat based distros.


Besides that, we have found these instructions for the headers in Ubuntu: https://www.tecmint.com/install-kernel-headers-in-ubuntu-and-debian/


Installing the headers should fill in the necessary information for "/lib/modules/'uname -r'/build" automatically and libelf may not be necessary, it is only needed on some Kernel/Architecture combinations.


We hope this clarifies.


Regards,

Ragulan_Intel


0 Kudos
Ragulan_Intel
Employee
266 Views

Hi HuangTf,


Hope you are doing well.


This is a gentle follow up on this case. We would appreciate if you could let us know if your concerns have been addressed.


If all is good from your end, we would like to obtain your approval to archive this case from our end.


Regards,

Ragulan_Intel


0 Kudos
Ragulan_Intel
Employee
235 Views

Hi HuangTF,


Greetings!


Kindly note that as we have not received any response from our previous follow-ups, we will be closing this request. 

 

You can still re-open the case by logging into your web portal or replying to this email or talk to Intel Customer support and provide the case number.

 

Please note that if the case is re-opened more than 15 days after closure, a new case will be created with a reference to the original case.

 

You may receive an invitation to take a survey in a few days. We value your feedback and look forward to hearing about your support experience.


Regards,

Ragulan_Intel


0 Kudos
huangtf
Beginner
209 Views

Hello IntelSupports,

 

 

Thanks a lot for all of you!

 

 

Our problem has been solved with the help of you.

 

 

Words from Subhashish_Intel are very helpful, too.

 

“Here are some instructions I found on signing:

 

https://ubuntu.com/blog/how-to-sign-things-for-secure-boot”

 

 

 

Regards,

 

HuangTf

 

 

0 Kudos
Reply