lshw doesn't have logicalname, serial number, or size for nvme device

we need https://github.com/lyonel/lshw/pull/45

ppa for testing: https://launchpad.net/~ycheng-twn/+archive/ubuntu/lshw
TODO: change log need refine (might need to refine in patch file)

Status changed to 'Confirmed' because the bug affects multiple users.

Note that Fedora has patches in https://koji.fedoraproject.org/koji/buildinfo?buildID=1329140 that fix the NVME issue - maybe these could be used in the Ubuntu package builds too?

I tried building lshw from the master branch, including the above fix (comment #1), but it didn't work. However, I can confirm the patched Fedora version works.

I would be happy to help with fixing this as this problem has been a thorn in my side for a while.

Hamish

per check fedora repo. I think the patch used in fedora should be the same as the one mentioned in #1. [1] vs [2]

However, it seems the maintainer of lshw wants something better. Refer to [3]

IMHO, the existing one shall works for most cases for now. We might have certain in-compatibility in the future as the maintainer land something else. However something partially works still helps us, right?

[1] https://github.com/lyonel/lshw/pull/45/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc
[2] https://src.fedoraproject.org/rpms/lshw/blob/master/f/lshw-B.02.18-nvme.patch
[3] https://ezix.org/src/pkg/lshw/pulls/27

I upload 02.18.85-0.3ubuntu2~p1 (focal) to https://launchpad.net/~ycheng-twn/+archive/ubuntu/lshw and it works for me.

Also works for me. In my case, I ran the binary on Ubuntu 18.04 because that's what my real hardware is using.

If we can get this into Focal, that'd be great, but I wonder if we can backport into previous releases as well.

Don't know if someone should mark as fix committed in this case, seeing as there are fixes out there.

Focal still has lshw 02.18.85-0.3ubuntu1, I don't see 02.18.85-0.3ubuntu2 in proposed,

the last push to proposed was 01-30-2020

Is this going to be push to proposed?

nevermind my previous comment #9, wrong bug ...

Regardless, it'd be great for this to make it into the LTS release, but I don't know how to make that happen. It might also be too late, but I hope not.

Adding a note to say that either this has been fixed in a B02.19, or the patch must have made it into the Ubuntu package for 22.04 at least (and I think 20.04 too, but I don't have an easy way to verify that at the moment)