OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Applications => Topic started by: Martin Iturbide on August 16, 2018, 05:29:01 pm
-
Hi
I'm using lsusb-20130526.zip (https://www.dropbox.com/s/ef45b19aqrc6c95/lsusb-20130526.zip?dl=0) and it is not longer working on my ArcaOS 5 system. If I get the newer usb.ids from its web site (http://www.linux-usb.org/usb.ids) (2018-08-15), when I run lsusb I just get a blank return from the command.
When I wrote my "Extracting Hardware Information from ArcaOS and OS/2 (https://www.os2world.com/wiki/index.php/Extracting_Hardware_Information_from_ArcaOS_and_OS/2)" article, lsusb was working fine, it haven't been updated from that days, so my only guess is that the newer usb.ids file is producing that issue.
I have also libusb dll installed.
Directory of C:\usr\lib
6-17-16 5:24a 24,217 124 a--- libusb10.dll
Any ideas?
Regards
-
Hi Martin
Possibly you need a newer libusb10.dll - I have this version:-
7-12-16 8:49a 84,096 0 a--- libusb10.dll
I just downloaded and tested lsusb and it seems to be working fine with the above.
Not sure where I got this build from though, Sorry...
Using ANPM I see there is a libusb1 rpm available which contains a different build of libusb10.dll - might be worth trying.
Regards
Pete
-
Hi.
On the Netlabs RPM, on the libusb1 package, I can not find the libusb10.dll file.
Any other ideas?
Regards
-
Hi Martin
You should be looking in Available not Installed - see Captured1.png attached
Regards
Pete
-
Hi Martin
I've just realised that both packages have the same version number but are obviously different in contents.
You may have to uninstall your current libusb1 package in order to install the version containing libusb10.dll - looks like a bit of a cockup on the yum/rpm front.
Regards
Pete
-
Hi Pete
I just uninstalled libusb1 and installed the older version of libusb1 (1.0.16-1 and 2) , but it just insist to installs the libusb-legacy-0.
It looks to me that libusb10.dll got replaced by usb100.dll for newer releases. Maybe I should ask Paul if he has some time to update his lsusb port to support the newer DLL.
I don't know what other tools that uses libusb10.dll can be affected.
Regards
-
Hi Pete
I just uninstalled libusb1 and installed the older version of libusb1 (1.0.16-1 and 2) , but it just insist to installs the libusb-legacy-0.
It looks to me that libusb10.dll got replaced by usb100.dll for newer releases. Maybe I should ask Paul if he has some time to update his lsusb port to support the newer DLL.
I don't know what other tools that uses libusb10.dll can be affected.
Regards
just install what the rpm tells you. the legacy is a forwarder dll to the new usb dll. All should work with that. doing some stuff y hand will not do any good.
-
Hi Pete
Can you confirm if you "lsusb" works with the latest version of usb.ids (http://www.linux-usb.org/usb.ids).
Regards
-
Hi Martin
Yes, no problem, that is what I installed to test lsusb with.
I finally discovered where the libusb10.dll I am using came from - http://smedley.id.au/tmp/libusb-20161207.zip
May be worth trying if still having problems.
Regards
Pete
-
Hi Pete
You are right. The moment I replaced "libusb10.dll" with the older one from Paul (http://smedley.id.au/tmp/libusb-20161207.zip), lsusb worked fine.
Thanks. I'm opening a ticket to notify Paul on his mantis. (https://mantis.smedley.id.au/view.php?id=680)
Regards
-
Hi Martin
If the rpm libusb does not work maybe you should open a ticket about that as well.
Regards
Pete
-
Hey Martin,,
You are right. The moment I replaced "libusb10.dll" with the older one from Paul (http://smedley.id.au/tmp/libusb-20161207.zip), lsusb worked fine.
Thanks. I'm opening a ticket to notify Paul on his mantis. (https://mantis.smedley.id.au/view.php?id=680)
With all due respect, what would you like me to do? If the rpm guys want to break existing DLL's, let them rebuild lsusb.
As you've written, the DLL & exe I provide work.
Cheers,
Paul
-
Paul
+10
-
Hey Martin,,
You are right. The moment I replaced "libusb10.dll" with the older one from Paul (http://smedley.id.au/tmp/libusb-20161207.zip), lsusb worked fine.
Thanks. I'm opening a ticket to notify Paul on his mantis. (https://mantis.smedley.id.au/view.php?id=680)
With all due respect, what would you like me to do? If the rpm guys want to break existing DLL's, let them rebuild lsusb.
As you've written, the DLL & exe I provide work.
Cheers,
Paul
Hi Paul.
Also, with all due respect, I really do not know who is right and wrong. I don't have the skill to know who broke what or who is using an old code or doing the right thing.
The easy thing for the user will be for lsusb to work fine with the libraries installed from Netlabs (USB100.DLL and libusb10.dll), but I don't know if the choice to change libusb10.dll for usb100.dll was something from the source of the open source project itself, or was only a choice made by bitwise. If it was Bitwise choice, it will be interesting to hear from them.
The original source code source project for lsusb and libusb is https://github.com/gregkh/usbutils , right?
Regards
-
Hi
I'm using lsusb-20130526.zip (https://www.dropbox.com/s/ef45b19aqrc6c95/lsusb-20130526.zip?dl=0) and it is not longer working on my ArcaOS 5 system. If I get the newer usb.ids from its web site (http://www.linux-usb.org/usb.ids) (2018-08-15), when I run lsusb I just get a blank return from the command.
When I wrote my "Extracting Hardware Information from ArcaOS and OS/2 (https://www.os2world.com/wiki/index.php/Extracting_Hardware_Information_from_ArcaOS_and_OS/2)" article, lsusb was working fine, it haven't been updated from that days, so my only guess is that the newer usb.ids file is producing that issue.
I have also libusb dll installed.
Directory of C:\usr\lib
6-17-16 5:24a 24,217 124 a--- libusb10.dll
Any ideas?
Regards
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.
-
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
-
Works fine here with only the Netlabs libusb10.dll on the LIBPATH.
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
-
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
-
Hi Martin,
As by Silvan and Dave it's working for me fine, so maybe there is something wrong on you're site?
-
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
-
You need to install libusb1-legacy to get libusb10.dll, which I assume is a forwarder.
-
Hi Dave
Thanks - I was just pointing out a possible point of confusion due to a package contents listing being wrong.
Regards
Pete
-
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.
-
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
-
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.
-
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
-
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:
[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:
[G:\]lsusb
That is supposed to be a blank line, no output.
...executing 'lsusb -V' produces:
[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.
-
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.
-
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
-
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.
-
Ivan and Dave,
Guys, no worries, it is working fine...
-
Hi
I found my issue, it was very dumb. The libusb from the RPM library was always working fine for me.
It seems that Paul's libusb used to give more information when a device was not attached and gave more log information, the one on the RPM just gives me an empty field and does not says anything. So, it is not broken, it is just not saying anything if I don't have a device attached.
Regards
-
...the one on the RPM just gives me an empty field and does not says anything. So, it is not broken, it is just not saying anything if I don't have a device attached...
LOL, well, I'm actually glad to hear I was not the only one to get 'detoured' by that little experience...
-
resurrecting an old thread - I updated lsusb to the latest source.... https://smedley.id.au/tmp/lsusb-013.zip
-
I needed to move the usb.ids from \sys\bin to \mptn\etc, but lsusb 013 seems to work well here.
-
Yes, since I am currently updating libusb, I have contacted Paul to update "lsusb.exe" to work with usb100.dll to ensure I did not break existing things.
At the same time, I told him that ArcaNoae was heading for "usb.ids" being in the %ETC% directory. He was so kind to change that accordingly.
I think the only utility to expect usb.ids to be in its working directory is the good old USBRES.EXE.
-
resurrecting an old thread - I updated lsusb to the latest source.... https://smedley.id.au/tmp/lsusb-013.zip
Thanks Paul. It is working fine here.
Just a little question about the discussion, it is usb.ids hardcoded to "\mptn\etc" path ? or it is set with "SET ETC=" ?.
I'm complete fine that usb.ids goes into the "SET ETC=" path.
Regards
-
Speaking for Paul, I can see from the exec that it is looking for the environment variable.
-
Speaking for Paul, I can see from the exec that it is looking for the environment variable.
Lars is correct - it looks in %ETC%. I should enhance it to look in the same location is lsusb.exe in the event it can't be found in %ETC%....
-
Thanks Paul.
I want to upload lsusb to hobbes. Please let me know if you are ok with the readme file.
Regards
-
Thanks Paul.
I want to upload lsusb to hobbes. Please let me know if you are ok with the readme file.
No problems from me
-
Thanks Paul. I just uploaded it to hobbes.
-
Hi
I been trying lsusb further and I get this error:
[X:\]lsusb -d 17ef:608d -v >lenmou.txt
can't get device qualifier: No such file or directory
can't get debug descriptor: No such file or directory
I get the report on "lenmou.txt (https://www.os2world.com/wiki/index.php/Lenovo_Essential_Wired_Keyboard_and_Mouse_Combo_Hardware_Report#Mouse)", but I don't know if I'm missing something else.
Regards
-
Hi Lars
I also noticed that "hwman16.wpi" installer is also searching for usb.ids on the path or libpath. I think that for a future version it will need to be changed (or include) the %ETC% directory to maintain the same logic.
Regards
-
No. The install script checks in %ETC%,%DPATH% and in %PATH%, in that order. As does the DLL during runtime.
-
Hi Lars.
You are right. I was using the wrong VM withtout usb.ids and I let myself guide on the error message.
It worked now with usb.ids on /mptn/etc and it had installed.
Regards