Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: QUick question about USB interfaces



        Hello.  Can you confirm that the USB library is compiled or linked
into the binary you built to support the non-APC UPS's?  

-Brian

On Oct 31, 12:47pm, Dave Burgess wrote:
} Subject: Re: QUick question about USB interfaces
} On 10/31/2012 12:38 PM, Paul Goyette wrote:
} > Hmm.  My APC UPS uses pkgsrc/apcupsd and it works just find when I 
} > specify "/dev/usb0" - no port needed.
} >
} > I would expect yours to work with /dev/usb0.04 if the port is needed.
} >
} > Do you have the appropriate entries in /dev ?
} 
} My APC use used that too.  These are different.  That's why 'nut' is 
} nice, it supports a BUNCH of UPS systems that aren't APC compatible.
} 
} Using ugen0.04 was my first thought, but that didn't help.  I tried all 
} of the ugen0.xx ports, just to see what would happen.
} 
} I tried usb0, but I don't think the ugen0 device gets tied into the usb0 
} device; besides, usb0 is my KVM switch.  I tried all of the other usbx 
} options, and they call fail with "not configured" error.
} 
} I double checked all of the devices in /dev - they all seem to be there.
} 
} Dave
} 
} 
} >
} >
} > On Wed, 31 Oct 2012, Dave Burgess wrote:
} >
} >> I know this isn't a question specifically about Current (at least, 
} >> not yet :-)
} >>
} >> Uname -a:  "NetBSD www.cynjut.net 6.0_BETA NetBSD 6.0_BETA (GENERIC) 
} >> amd64"
} >>
} >>
} >> I just had to replace the UPS that runs my systems at home.  I 
} >> installed a pair of CyberPower 1500s.  I've found the "nut" program 
} >> from "Network UPS Tools" (at networkupstools.org).  It compiles clean 
} >> and seems to work fine, with one exception:
} >>
} >> The UPSes connect to the server as ugen0 and ugen1.  From there, the 
} >> rest of the devices in the system will gather the status of the UPSes 
} >> through the NUT client services.
} >>
} >> This is the dmesg output from the first one:
} >>
} >> ehci0: handing over low speed device on port 4 to ohci0
} >> ugen0 at uhub0 port 4
} >> ugen0: CPS CP 1500C, rev 1.10/0.01, addr 4
} >>
} >> The software comes with a couple of different drivers that can 
} >> connect to the UPS, but both want to know the port.
} >>
} >> No matter what ugen0.xx device I specify, the programs cannot make 
} >> the connection to the UPS, so monitoring the UPS isn't happening.
} >>
} >> Can someone come to my rescue and tell me where I need to look next 
} >> to figure this out?
} >>
} >> -- 
} >> Dave Burgess
} >> Manager
} >> Cynjut Consulting Services, LLC
} >> ex-FAQ Maintainer, 386BSD FAQ
} >>
} >>
} >> !DSPAM:50915d2f127401109287848!
} >>
} >>
} >
} > -------------------------------------------------------------------------
} > | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
} > | Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
} > | Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
} > | Kernel Developer |                          | pgoyette at netbsd.org  |
} > -------------------------------------------------------------------------
} 
} 
} -- 
} Dave Burgess
} Manager
} Cynjut Consulting Services, LLC
} 
>-- End of excerpt from Dave Burgess




Home | Main Index | Thread Index | Old Index