I have a cyberpower cp1200avr connected via usb to a computer. When I look at hardware info in YAST, I can see the device as sysfs_bus_id: 1-2:1.0 If I look in the /var/log/messages file, I see it as hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:1.0-2 I check /dev/usb/hiddev and I only have 0 thru 15. I need to add the dev path to a configuration file and I have not been able to determine it. Can anyone tell me how I can find the real /dev/usb/devicefile for this or what it would be from the above information? Art
Art Fore wrote:
I have a cyberpower cp1200avr connected via usb to a computer. When I look at hardware info in YAST, I can see the device as sysfs_bus_id: 1-2:1.0
If I look in the /var/log/messages file, I see it as hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:1.0-2
I check /dev/usb/hiddev and I only have 0 thru 15.
I need to add the dev path to a configuration file and I have not been able to determine it.
Can anyone tell me how I can find the real /dev/usb/devicefile for this or what it would be from the above information?
Art
I don't know if this will help, but if the normal device progression applies then 96+95=191, "mknod c 180 191 /dev/hiddev96". I would like to see a feature in SuSE's udev that clears out the device tree on shutdown/reboot, so you can see exactly which devices are available when the system is booted. In the early days of testing udev from source on 9.1, I ran into a problem where /dev/console and the ttys were not being created by udev, so I created those devices manually, stopped udev clearing out /dev and it showed only those that were available at boot plus the ones I created, a true picture and no clutter. Testing was done by moving /dev and creating an empty /dev, so it was easy to boot from rescue, make the devices or move the original /dev back, then reboot. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Mon, 2005-07-25 at 03:17 +0100, Sid Boyce wrote:
Art Fore wrote:
I have a cyberpower cp1200avr connected via usb to a computer. When I look at hardware info in YAST, I can see the device as sysfs_bus_id: 1-2:1.0
If I look in the /var/log/messages file, I see it as hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:1.0-2
I check /dev/usb/hiddev and I only have 0 thru 15.
I need to add the dev path to a configuration file and I have not been able to determine it.
Can anyone tell me how I can find the real /dev/usb/devicefile for this or what it would be from the above information?
Art
I don't know if this will help, but if the normal device progression applies then 96+95=191, "mknod c 180 191 /dev/hiddev96". I would like to see a feature in SuSE's udev that clears out the device tree on shutdown/reboot, so you can see exactly which devices are available when the system is booted. In the early days of testing udev from source on 9.1, I ran into a problem where /dev/console and the ttys were not being created by udev, so I created those devices manually, stopped udev clearing out /dev and it showed only those that were available at boot plus the ones I created, a true picture and no clutter. Testing was done by moving /dev and creating an empty /dev, so it was easy to boot from rescue, make the devices or move the original /dev back, then reboot. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
When I enter the mknod c 180 191 /dev/hiddev96mknod c 180 191 /dev/hiddev9 as root, I get invalid device type '180'. Art
On Sun, 2005-07-24 at 20:15 -0700, Art Fore wrote:
On Mon, 2005-07-25 at 03:17 +0100, Sid Boyce wrote:
Art Fore wrote:
I have a cyberpower cp1200avr connected via usb to a computer. When I look at hardware info in YAST, I can see the device as sysfs_bus_id: 1-2:1.0
If I look in the /var/log/messages file, I see it as hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:1.0-2
I check /dev/usb/hiddev and I only have 0 thru 15.
I need to add the dev path to a configuration file and I have not been able to determine it.
Can anyone tell me how I can find the real /dev/usb/devicefile for this or what it would be from the above information?
Art
I don't know if this will help, but if the normal device progression applies then 96+95=191, "mknod c 180 191 /dev/hiddev96". I would like to see a feature in SuSE's udev that clears out the device tree on shutdown/reboot, so you can see exactly which devices are available when the system is booted. In the early days of testing udev from source on 9.1, I ran into a problem where /dev/console and the ttys were not being created by udev, so I created those devices manually, stopped udev clearing out /dev and it showed only those that were available at boot plus the ones I created, a true picture and no clutter. Testing was done by moving /dev and creating an empty /dev, so it was easy to boot from rescue, make the devices or move the original /dev back, then reboot. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
When I enter the mknod c 180 191 /dev/hiddev96mknod c 180 191 /dev/hiddev9 as root, I get invalid device type '180'.
Art
Entered the command as mknod /dev/usb/hiddev96 c 180 191 then it worked. Art
Art Fore wrote:
On Sun, 2005-07-24 at 20:15 -0700, Art Fore wrote:
<STUFF DELETED>
When I enter the mknod c 180 191 /dev/hiddev96mknod c 180 191 /dev/hiddev9 as root, I get invalid device type '180'.
Art
Entered the command as mknod /dev/usb/hiddev96 c 180 191 then it worked.
Art
Pardon me, I put the cart before the horse -- it was late. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
participants (2)
-
Art Fore -
Sid Boyce