** Tags added: 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/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage notifications about this bug go to:
** Changed in: fwts (Ubuntu)
Status: Triaged => 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/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
** Changed in: fwts (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
** Changed in: oem-priority
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
** Changed in: fwts (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
There is only one other check can be done for type 41 - Device Type
Instance must be unique for a device type.
However, it's going to be ugly code to support this in the current fwts
dmicheck implementation. I am not sure whether this is worthwhile as it
is a small feature and there aren't any
https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf
7.42 Onboard Devices Extended Information (Type 41)
The information in this structure defines the attributes of devices that
are onboard (soldered onto) a system element, usually the baseboard.
Table 114 provides
Please help to provide the output of `sudo dmidecode -t 10`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
There are a few things can be checked to type 41 in fwts. I am looking
into it. It may not be solve this bug but it is still worthwhile to add
more sanity checks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@cktenn,
fwts has no way to know it is an onboard device unless it is reported to
be so. A computer can has a PCIe inserted without having a antry in
table 41. From fwts's (or spec's) viewpoint, there is nothing wrong
here.
--
You received this bug notification because you are a member of
>From the lscpi out, the ethernet is on PCi 02:00.0. It is not in DMI
type 41 table.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1855420/+attachment/5313971/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
There are packages like systemd relies on SMBIOS type 41 information to
determine the onboard network interface renaming mechanism. However,
manufacturers don't always offer the
There are no ways to get from 2:00.0 to SMBIOS type 41, as it is not
possible to know whether 2:00.0 is a onboard from software's viewpoint.
>From the output type 41, it seems nothing wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It seems that SMBIOS doesn't ask type instance to start from 1 - it was
only an example.
==
Device Type Instance is a unique value (within a given onboard device type)
used to indicate the order the device is designated by the system. For example,
a system
** Description changed:
+
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
+
There are packages like systemd relies on SMBIOS type 41 information to
determine the onboard network interface renaming mechanism. However,
manufacturers don't always offer the
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Che Cheng (cktenn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
There are packages like systemd relies on SMBIOS type 41 information to
determine the onboard network interface renaming mechanism. However,
- manufacturers don't always offer the correct information.
+ manufacturers don't always offer the correct information, so the
+
17 matches
Mail list logo
