Author Topic: Problems with lsusb and usb.ids  (Read 2660 times)

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Thank You
  • -Given: 346
  • -Receive: 64
  • Posts: 2198
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Problems with lsusb and usb.ids
« Reply #15 on: August 20, 2018, 11:17:42 pm »
I just tried lsusb with latest usb.ids and all runs still with rpm libsb1. So I don't see any issues with it or I'm blind.

Hi Silvan.

Can you please confirm that you are using "lsusb-20130526.zip" ? or do you use a different release? I can not make it work with the Netlabs RPM libraries yet. I have an ArcaOS 5.0.1 VM and a different system on real hardware and both suffer from the same issue with the Netlabs RPM libusb1 and libusb-legacy-0.

Any other comments/Test from other people trying lsusb and the netlabs libusb is welcome. For the moment my only workarround is to use Paul's libusb.


Regards
« Last Edit: August 20, 2018, 11:19:46 pm by Martin Iturbide »
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 9
  • -Receive: 129
  • Posts: 1867
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #16 on: August 21, 2018, 03:15:43 am »
Works fine here with only the Netlabs libusb10.dll on the LIBPATH.
Code: [Select]
H:\tmp>which2 -la libusb*
k:/usr/lib/libusb10.dll (also k:/usr/lib/libusb10.dll) 2

H:\tmp>lsusb.exe
Bus 001 Device 001: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 413c:2010 Dell Computer Corp. Keyboard

[H:\tmp]dir k:\usr\lib\libusb10.dll

The volume label in drive K is RPM.
The Volume Serial Number is 57BF:35BF.
Directory of K:\usr\lib

 6-17-16  3:24a        24,217    124 a---  libusb10.dll
        1 file(s)      24,217 bytes used
                  173,097,349 K bytes free

[H:\tmp]dir

Volume in drive H has no label.
The Volume Serial Number is 4D14:4129.
Directory of H:\tmp

 8-20-18  8:09a         <DIR>      0 ----  .
 8-20-18  8:09a         <DIR>      0 ----  ..
 5-25-13  4:22p        97,368    124 a---  lsusb.exe
        3 file(s)      97,368 bytes used
                    794,549,760 bytes free

Silvan Scherrer

  • Full Member
  • ***
  • Thank You
  • -Given: 9
  • -Receive: 9
  • Posts: 165
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #17 on: August 21, 2018, 09:48:04 am »
I just tried lsusb with latest usb.ids and all runs still with rpm libsb1. So I don't see any issues with it or I'm blind.

Hi Silvan.

Can you please confirm that you are using "lsusb-20130526.zip" ? or do you use a different release? I can not make it work with the Netlabs RPM libraries yet. I have an ArcaOS 5.0.1 VM and a different system on real hardware and both suffer from the same issue with the Netlabs RPM libusb1 and libusb-legacy-0.

Any other comments/Test from other people trying lsusb and the netlabs libusb is welcome. For the moment my only workarround is to use Paul's libusb.


Regards
yes I used that version, as else the test would not make any sense. Of course I could build a new version of the utility, but I'm a bit lazzy to do so.

regards
Silvan
kind regards
Silvan
CTO bww bitwise works GmbH

Please help us with donations, so we can further work on OS/2 based projects. Our Shop is at https://www.bitwiseworks.com/shop/index.php

TeLLie

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 6
  • Posts: 61
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #18 on: August 23, 2018, 03:32:40 pm »
Hi Martin,

As by Silvan and Dave it's working for me fine, so maybe there is something wrong on you're site?

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 30
  • Posts: 742
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #19 on: August 27, 2018, 02:28:54 am »
Hi

Maybe Martin has bumped into the problem I have just experienced: The libusb1 rpm package shows libusb10.dll components included but after installation there is no libusb10.dll installed and the contents of the just installed libusb1 package do not list any libusb10 components.

This is illustrated by my previous screenshot captured1.png which shows the libusb1 contents listed as Aavailable for installation and Martins screenshot libusb1.png which shows the contents after installation.

Bit of a muckup on the rpm front by the looks of it...


Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 9
  • -Receive: 129
  • Posts: 1867
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #20 on: August 27, 2018, 07:28:46 am »
You need to install libusb1-legacy to get libusb10.dll, which I assume is a forwarder.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 30
  • Posts: 742
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #21 on: August 27, 2018, 02:46:28 pm »
Hi Dave

Thanks - I was just pointing out a possible point of confusion due to a package contents listing being wrong.

Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 9
  • -Receive: 129
  • Posts: 1867
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #22 on: August 27, 2018, 05:59:57 pm »
What's weird is that your screenshot showed 2 versions of libusb. Was this due to it not being installed? Here with it installed, it clearly only shows the content of the latest package, which has libusb100.dll in it.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 30
  • Posts: 742
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #23 on: August 27, 2018, 07:38:25 pm »
Hi Dave

What my screenshot shows is the Contents of libusb1 as Available. As you see it shows both libusb10 and libusb100 components.

What Martins screenshot shows - and you seem to have discovered after installation - is that the package only installs libusb100 components.


Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 9
  • -Receive: 129
  • Posts: 1867
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #24 on: August 27, 2018, 07:49:49 pm »
Yes, but it is clearly showing 2 different versions with only the old version containing libusb10. On a new install, libusb is installed as it is a dependency for cups and associated stuff.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 30
  • Posts: 742
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #25 on: August 27, 2018, 11:37:05 pm »
Hi Dave

Yes, I see what you mean about the 2 versions. Not being very "rpm savvy" I thought that was simply a package with a dll forwarder, libusb10.dll, to the included later (lib)usb100. A bit of a packaging error...

Not having installed cups via rpm/yum/ANPM on my ArcaOS system I did not realise that libusb would be installed as a dependency - and I would not need it anyway as I use wireless printing and scanning.


Regards

Pete

 

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 502
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #26 on: August 30, 2018, 04:32:12 pm »
I've never used this package, but given that it seems like a handy utility I thought I'd give it a try and report out on how the RPM package based install went:

I did the following:

1) downloaded "lsusb-20130526.zip" (per the link Martin provided)
2) installed libusb1, libusbcals (pre-req for libusb1)
3) installed libusb1-legacy-0
4) downloaded the latest usb.ids (per the link Martin provided)
5) re-booted

The following DLLs are now present in my \usr\lib:

Code: [Select]
[G:\usr\lib]dir *usb*

The volume label in drive G is OS2.
The Volume Serial Number is 45B6:75C3.
Directory of G:\usr\lib

 6-17-16   6:23a     22306         124  libusb10.dll
 3-03-17   1:49a     33908         124  usb100.dll

...executing 'lsusb' produces:

Code: [Select]
[G:\]lsusb


That is supposed to be a blank line, no output.

...executing 'lsusb -V' produces:

Code: [Select]
[G:\]lsusb -V
lsusb (usbutils) 006

So it appears something's not right, the utility seems to run, but clearly it's having a hard time getting info out of the system, whether that's from USB.IDS or actually hardware I can not tell.

Trying an older version of USB.IDS (Version: 2015.12.17) produces the same result, so I'm leaning towards ruling out USB.IDS file version as being the culprit.

Dariusz Piatkowski

  • Hero Member
  • *****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 502
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #27 on: August 30, 2018, 06:06:18 pm »
I've never used this package, but given that it seems like a handy utility I thought I'd give it a try and report out on how the RPM package based install went:
...
Trying an older version of USB.IDS (Version: 2015.12.17) produces the same result, so I'm leaning towards ruling out USB.IDS file version as being the culprit.

Sorry everyone, this was a bad test on my part. I missunderstood what this utility did. My expectation was that this would report on BOTH the built-in USB hardware as well as any connected devices. This was the wrong assumption.

Updated results are: my installation works correctly!!!

Having plugged in an old SandDisk card reader I now get the correct reporting.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 30
  • Posts: 878
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #28 on: August 30, 2018, 06:11:16 pm »
Hi Dariusz,

I doubt that the usb.ids file is the problem, the latest one works with USBRES.EXE and gives more details about some of my connected usb devices.

The last time I used lsusb it required the usb.ids to be in a specific directory - the dir was hard coded into it. This was in 2013 so things may have changed

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 9
  • -Receive: 129
  • Posts: 1867
    • View Profile
Re: Problems with lsusb and usb.ids
« Reply #29 on: August 31, 2018, 12:59:17 am »
Hi Dariusz,

I doubt that the usb.ids file is the problem, the latest one works with USBRES.EXE and gives more details about some of my connected usb devices.

The last time I used lsusb it required the usb.ids to be in a specific directory - the dir was hard coded into it. This was in 2013 so things may have changed

Exactly, on ArcaOS, it is x:\sys\bin that lsusb looks in.