How do i find what device to use for a character something plugged in to USB

There are so many system information tools i figure that this one would be
in the set. I just can’t seen to find it.

I can understand your question very clearly, but it is better to send me the output of this command

lsusb

On Wed, 27 Apr 2011 17:06:01 GMT, stamostolias
<stamostolias@no-mx.forums.opensuse.org> wrote:

>
>I can understand your question very clearly, but it is better to send me
>the output of this command
>
>Code:
>--------------------
> lsusb
>--------------------

Why sure.

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 174c:5106 ASMedia Technology Inc.
Bus 001 Device 005: ID 152d:2338 JMicron Technology Corp. / JMicron USA
Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
Bus 001 Device 004: ID 04b8:0005 Seiko Epson Corp. Stylus D88+
Bus 001 Device 003: ID 0409:0058 NEC Corp. HighSpeed Hub
Bus 001 Device 002: ID 152d:2329 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I can also send lsusb -v if that helps but it is a lot of lines.

Just curious what a “character something” is…

Nowadays, USB devices can be mounted a few ways, often auto-recognized and auto-mounted by the udev subsystem which supports listing by using the command lsusb.

But, still not sure what is meant by the original question.

Tony

On 2011-04-27 18:26, josephkk wrote:
>
> There are so many system information tools i figure that this one would be
> in the set. I just can’t seen to find it.

What is " a character something plugged in to USB"?


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On Fri, 29 Apr 2011 23:38:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2011-04-27 18:26, josephkk wrote:
>>
>> There are so many system information tools i figure that this one would be
>> in the set. I just can’t seen to find it.
>
>What is " a character something plugged in to USB"?

*nix supports 3 basic classes for devices, display, block and character.
Streaming devices are usually character, display or a compound of both.
And of course block devices store streams for later reuse.

For character somethings (devices) see lines 2 and 8 (ignoring the wrap)
of the results of lsusb (in my reply to Stamos). Block devices are at
lines 6, 7 and 10.

I am trying to get the character something device from line 2 integrated
properly. To do so, i need to find out where it shows up in /dev/.

On Fri, 29 Apr 2011 20:06:03 GMT, tsu2 <tsu2@no-mx.forums.opensuse.org>
wrote:

>
>Just curious what a “character something” is…
>
>Nowadays, USB devices can be mounted a few ways, often auto-recognized
>and auto-mounted by the udev subsystem which supports listing by using
>the command lsusb.
>
>But, still not sure what is meant by the original question.
>
>Tony

It would be something connected as a character device. See line 2 in the
output of lsusb.

You will find the character device at /dev/bus/usb/003/005. It may be aliased to another name under /dev by udevd. If not you can create a rule to do so.

On 2011-04-30 03:55, josephkk wrote:
> On Fri, 29 Apr 2011 23:38:06 GMT, “Carlos E. R.” <> wrote:
>
>> What is " a character something plugged in to USB"?
>
> *nix supports 3 basic classes for devices, display, block and character.
> Streaming devices are usually character, display or a compound of both.
> And of course block devices store streams for later reuse.

Ah, that.

> I am trying to get the character something device from line 2 integrated
> properly. To do so, i need to find out where it shows up in /dev/.

This?

Bus 003 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

That’s a good question :slight_smile:

It will probably show as an emulated serial port.

One trick to find out is to list /dev before and after plugging the device,
see what is new. I actually did that with mine just to try… and gnome
crashed on me! I found a bug in devkit, I think, not worth reporting as the
version is old.

I made such two listings, then compare:

diff -y --suppress-common-lines lista.sin lista.con | less -S

> drwxr-xr-x 17 root root 4760 Apr 30 04:47 ./ | drwxr-xr-x 18 root root 4800 Apr 30 04:46 ./
> drwxr-xr-x 6 root root 140 Apr 30 04:49 .udev/ | drwxr-xr-x 6 root root 140 Apr 30 04:11 .udev/
> drwxr-xr-x 2 root root 3880 Apr 30 04:47 char/ | drwxr-xr-x 2 root root 3940 Apr 30 04:46 char/
> > crw-rw---- 1 root root 252, 0 Apr 30 04:46 hidraw0
> crw-rw-rw- 1 root tty 5, 2 Apr 30 04:50 ptmx | crw-rw-rw- 1 root tty 5, 2 Apr 30 04:47 ptmx
> drwxrwxrwt 2 root root 300 Apr 30 04:50 shm/ | drwxrwxrwt 2 root root 380 Apr 30 04:30 shm/
> crw–w---- 1 root tty 4, 10 Apr 30 04:49 tty10 | crw–w---- 1 root tty 4, 10 Apr 30 04:47 tty10
> crw–w---- 1 cer tty 4, 2 Apr 30 04:48 tty2 | crw–w---- 1 cer tty 4, 2 Apr 23 16:14 tty2
> > drwxr-xr-x 2 root root 60 Apr 30 04:46 usb/

The candidate would be hidraw0 or something inside /dev/usb/.

Telcontar:~ # l /dev/usb/
total 0
drwxr-xr-x 2 root root 60 Apr 30 04:52 ./
drwxr-xr-x 18 root root 4800 Apr 30 04:52 …/
crw-rw-r-- 1 root daemon 180, 0 Apr 30 04:52 hiddev0

Mayor 252 is reserved for local/experimental use (!).
180,0 the list says it is a printer. hiddev0 should be minor 96.

The numbers do not match nowdays, it seems.

What I have under /dev/bus/usb/003/005 (it happens to be that one here,
too) is:

crw-rw-r-- 1 root daemon 189, 260 2011-04-30 04:52 /dev/bus/usb/003/005

but that doesn’t help much, does it?

Another source of information is the log. Mine shows, at the time of the
disconnect/reconnect:

> <0.6> 2011-04-30 04:46:12 Telcontar kernel - - - [407159.454045] usb 3-1: USB disconnect, address 2
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407183.382012] usb 3-1: new low speed USB device using uhci_hcd and address 3
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250000] usb 3-1: New USB device found, idVendor=0463, idProduct=ffff
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250020] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250028] usb 3-1: Product: ELLIPSE
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250033] usb 3-1: Manufacturer: EATON
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250039] usb 3-1: SerialNumber: 000000000
> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250157] usb 3-1: configuration #1 chosen from 1 choice
> <0.6> 2011-04-30 04:46:41 Telcontar kernel - - - [407188.835952] generic-usb 0003:0463:FFFF.0003: hiddev0,hidraw0: USB HID v1.00 Device [EATON ELLIPSE] on usb-0000:00:1a.0-1/input0
> <0.6> 2011-04-30 04:47:40 Telcontar kernel - - - [407247.954040] usb 3-1: USB disconnect, address 3

Now look the last line but one, the device name is listed there. Actually,
two names: “hiddev0,hidraw0”. The same two I found in the listing diff
above :slight_smile:

Funny, two devices.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On Sat, 30 Apr 2011 03:32:48 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2011-04-30 03:55, josephkk wrote:
>> On Fri, 29 Apr 2011 23:38:06 GMT, “Carlos E. R.” <> wrote:
>>
>>> What is " a character something plugged in to USB"?
>>
>> *nix supports 3 basic classes for devices, display, block and character.
>> Streaming devices are usually character, display or a compound of both.
>> And of course block devices store streams for later reuse.
>
>Ah, that.
>
>> I am trying to get the character something device from line 2 integrated
>> properly. To do so, i need to find out where it shows up in /dev/.
>
>This?
>
>Bus 003 Device 005: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
>
>That’s a good question :slight_smile:
>
>It will probably show as an emulated serial port.
>
>One trick to find out is to list /dev before and after plugging the device,
>see what is new. I actually did that with mine just to try… and gnome
>crashed on me! I found a bug in devkit, I think, not worth reporting as the
>version is old.
>
>I made such two listings, then compare:
>
>diff -y --suppress-common-lines lista.sin lista.con | less -S
>
>> drwxr-xr-x 17 root root 4760 Apr 30 04:47 ./ | drwxr-xr-x 18 root root 4800 Apr 30 04:46 ./
>> drwxr-xr-x 6 root root 140 Apr 30 04:49 .udev/ | drwxr-xr-x 6 root root 140 Apr 30 04:11 .udev/
>> drwxr-xr-x 2 root root 3880 Apr 30 04:47 char/ | drwxr-xr-x 2 root root 3940 Apr 30 04:46 char/
>> > crw-rw---- 1 root root 252, 0 Apr 30 04:46 hidraw0
>> crw-rw-rw- 1 root tty 5, 2 Apr 30 04:50 ptmx | crw-rw-rw- 1 root tty 5, 2 Apr 30 04:47 ptmx
>> drwxrwxrwt 2 root root 300 Apr 30 04:50 shm/ | drwxrwxrwt 2 root root 380 Apr 30 04:30 shm/
>> crw–w---- 1 root tty 4, 10 Apr 30 04:49 tty10 | crw–w---- 1 root tty 4, 10 Apr 30 04:47 tty10
>> crw–w---- 1 cer tty 4, 2 Apr 30 04:48 tty2 | crw–w---- 1 cer tty 4, 2 Apr 23 16:14 tty2
>> > drwxr-xr-x 2 root root 60 Apr 30 04:46 usb/
>
>
>The candidate would be hidraw0 or something inside /dev/usb/.
>
>Telcontar:~ # l /dev/usb/
>total 0
>drwxr-xr-x 2 root root 60 Apr 30 04:52 ./
>drwxr-xr-x 18 root root 4800 Apr 30 04:52 …/
>crw-rw-r-- 1 root daemon 180, 0 Apr 30 04:52 hiddev0
>
>
>Mayor 252 is reserved for local/experimental use (!).
>180,0 the list says it is a printer. hiddev0 should be minor 96.
>
>The numbers do not match nowdays, it seems.
>
>What I have under /dev/bus/usb/003/005 (it happens to be that one here,
>too) is:
>
>crw-rw-r-- 1 root daemon 189, 260 2011-04-30 04:52 /dev/bus/usb/003/005
>
>but that doesn’t help much, does it?
>
>Another source of information is the log. Mine shows, at the time of the
>disconnect/reconnect:
>
>> <0.6> 2011-04-30 04:46:12 Telcontar kernel - - - [407159.454045] usb 3-1: USB disconnect, address 2
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407183.382012] usb 3-1: new low speed USB device using uhci_hcd and address 3
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250000] usb 3-1: New USB device found, idVendor=0463, idProduct=ffff
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250020] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250028] usb 3-1: Product: ELLIPSE
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250033] usb 3-1: Manufacturer: EATON
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250039] usb 3-1: SerialNumber: 000000000
>> <0.6> 2011-04-30 04:46:36 Telcontar kernel - - - [407184.250157] usb 3-1: configuration #1 chosen from 1 choice
>> <0.6> 2011-04-30 04:46:41 Telcontar kernel - - - [407188.835952] generic-usb 0003:0463:FFFF.0003: hiddev0,hidraw0: USB HID v1.00 Device [EATON ELLIPSE] on usb-0000:00:1a.0-1/input0
>> <0.6> 2011-04-30 04:47:40 Telcontar kernel - - - [407247.954040] usb 3-1: USB disconnect, address 3
>
>
>Now look the last line but one, the device name is listed there. Actually,
>two names: “hiddev0,hidraw0”. The same two I found in the listing diff
>above :slight_smile:
>
>Funny, two devices.

Thanks. Between you and Ken i may find it yet.

That happens. For example a USB dongle on the market here is a 3G modem and also a “CDROM”. The “CDROM”, which is actually some flash storage in the dongle, holds the firmware to talk to the modem. Since any number of logical devices can be put on the bus by the physical device, B stands for bus after all, some mfrs have found a use for the feature.

On Sun, 01 May 2011 00:06:03 GMT, ken yap
<ken_yap@no-mx.forums.opensuse.org> wrote:

>
>robin_listas;2332497 Wrote:
>> Funny, two devices.
>
>That happens. For example a USB dongle on the market here is a 3G modem
>and also a “CDROM”. The “CDROM”, which is actually some flash storage in
>the dongle, holds the firmware to talk to the modem. Since any number of
>logical devices can be put on the bus by the physical device, B stands
>for bus after all, some mfrs have found a use for the feature.

Using the syslog method i positively identified it as /dev/hidraw0.

Now i get this error:

CODE

$ /usr/lib/ups/driver/upsdrvctl start > upsdrvctl.txt 2>&1
tcgetattr(/dev/hidraw0): Inappropriate ioctl for device
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.23
(2.2.2)
Warning: This is an experimental driver.
Some features may not function correctly.

Driver failed to start (exit status=1)
Network UPS Tools - UPS driver controller 2.2.2

Does either of you have any additional advice to offer? It looks like i
will have to go to the nut (network UPS tools) developers.

I wonder of the current version of nut {2.6} has a better driver.
Since this is being done on an 11.1 - KDE3 machine it does not seem
reasonable to ask for a package to be built.

On 2011-05-03 08:26, josephkk wrote:
> Does either of you have any additional advice to offer? It looks like i
> will have to go to the nut (network UPS tools) developers.

In my case the “driver” takes more than a minute to initialize, reading
things from the unit. But it times out before that, so I had to increase
the timeout manually to a minute and a half.

> I wonder of the current version of nut {2.6} has a better driver.
> Since this is being done on an 11.1 - KDE3 machine it does not seem
> reasonable to ask for a package to be built.

You should not be using 11.1.
You may try the nut package from 11.4 and compile/build it yourself.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On Tue, 03 May 2011 14:20:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2011-05-03 08:26, josephkk wrote:
>> Does either of you have any additional advice to offer? It looks likei
>> will have to go to the nut (network UPS tools) developers.
>
>In my case the “driver” takes more than a minute to initialize, reading
>things from the unit. But it times out before that, so I had to increase
>the timeout manually to a minute and a half.
>
This error is almost immediate.
>
>> I wonder of the current version of nut {2.6} has a better driver.
>> Since this is being done on an 11.1 - KDE3 machine it does not seem
>> reasonable to ask for a package to be built.
>
>You should not be using 11.1.

I tried 11.2 and 11.3 both with KDE4. Seriously unstable on my machine
with all the eye heroin turned off. I kind of lost interest in KDE4 at
that point. I have one machine with 11.3 and KDE3.5, it is ok.

>You may try the nut package from 11.4 and compile/build it yourself.

I will consider it. Does it include full sources, state all development
dependencies, and include a spec file?

On 2011-05-05 07:24, josephkk wrote:
> On Tue, 03 May 2011 14:20:06 GMT, “Carlos E. R.” <> wrote:

> This error is almost immediate.

I meant that I had to carefully look till I found the cause, and I posted
it so you could see how weird it is. You will have to search for yours.

>>> I wonder of the current version of nut {2.6} has a better driver.
>>> Since this is being done on an 11.1 - KDE3 machine it does not seem
>>> reasonable to ask for a package to be built.
>>
>> You should not be using 11.1.
>
> I tried 11.2 and 11.3 both with KDE4. Seriously unstable on my machine
> with all the eye heroin turned off. I kind of lost interest in KDE4 at
> that point. I have one machine with 11.3 and KDE3.5, it is ok.

11.1 is EOL, and 11.2 will be in days.

>> You may try the nut package from 11.4 and compile/build it yourself.
>
> I will consider it. Does it include full sources, state all development
> dependencies, and include a spec file?

Of course.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On Thu, 05 May 2011 09:50:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2011-05-05 07:24, josephkk wrote:
>> On Tue, 03 May 2011 14:20:06 GMT, “Carlos E. R.” <> wrote:
>
>
>> This error is almost immediate.
>
>I meant that I had to carefully look till I found the cause, and I posted
>it so you could see how weird it is. You will have to search for yours.
>
OK.
>
>>>> I wonder of the current version of nut {2.6} has a better driver.
>>>> Since this is being done on an 11.1 - KDE3 machine it does not seem
>>>> reasonable to ask for a package to be built.
>>>
>>> You should not be using 11.1.
>>
>> I tried 11.2 and 11.3 both with KDE4. Seriously unstable on my machine
>> with all the eye heroin turned off. I kind of lost interest in KDE4 at
>> that point. I have one machine with 11.3 and KDE3.5, it is ok.
>
>11.1 is EOL, and 11.2 will be in days.
>
I am aware of that. I still have old machines on 10.3 because i haven’t
the time to get 11.X installed on them. I have a substantial case of
“It’s working, DON’T fix it.” It gets especially aggravated when the
“NEW” system is still flaky. My experience with oS 10.0, 10.1, 10.2,
11.0, 11.2, 11.3 are that they were/are flaky. And yes, i am seriously
considering switching to SLED and SLES.
>
>>> You may try the nut package from 11.4 and compile/build it yourself.
>>
>> I will consider it. Does it include full sources, state all development
>> dependencies, and include a spec file?
>
>Of course.

I guess i will go looking for it. I expect to find it in source.

On 2011-05-06 04:06, josephkk wrote:
> My experience with oS 10.0, 10.1, 10.2,
> 11.0, 11.2, 11.3 are that they were/are flaky. And yes, i am seriously
> considering switching to SLED and SLES.

All versions have problems for some people. For me, 11.1 was very
problematic. I find the lifetime of the distro too short: 11.2 is very
stable for me, 11.4 still has problems, and 11.2 will be EOL in days. But
SLED is too expensive for a home user.

>> >Of course.
> I guess i will go looking for it. I expect to find it in source.

Yes, the sources repo. Everything you need should be there, but… in its
own way.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On Sat, 07 May 2011 00:50:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2011-05-06 04:06, josephkk wrote:
>> My experience with oS 10.0, 10.1, 10.2,
>> 11.0, 11.2, 11.3 are that they were/are flaky. And yes, i am seriously
>> considering switching to SLED and SLES.
>
>All versions have problems for some people. For me, 11.1 was very
>problematic. I find the lifetime of the distro too short: 11.2 is very
>stable for me, 11.4 still has problems, and 11.2 will be EOL in days. But
>SLED is too expensive for a home user.
>
Probably for quite a few, not for all. US $120 for a single seat with
some support for 1 year is not out of my reach.

http://shop.novell.com/store/novell/DisplayCategoryProductListPage/categoryID.9621900?resid=TcoW2AoBAlUAAD2xMiQAAAAI&rests=1305089751975

>
>>> >Of course.
>> I guess i will go looking for it. I expect to find it in source.
>
>Yes, the sources repo. Everything you need should be there, but… in its
>own way.

Now all i have to do is find “nut” in the 11.4 source repos. Back in a
few days.