On 2013-01-27 09:29, Warren Block wrote:
On Sun, 27 Jan 2013, dweimer wrote:
On 2013-01-26 16:40, Shane Ambler wrote:
On 27/01/2013 08:15, dweimer wrote:
I would like to lock down the USB serial port adapter used on the
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will
On 2013-01-27 08:48, dweimer wrote:
On 2013-01-26 16:40, Shane Ambler wrote:
On 27/01/2013 08:15, dweimer wrote:
I would like to lock down the USB serial port adapter used on the
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get
a
clean shutdown in event of a power f
On Sun, 27 Jan 2013, dweimer wrote:
On 2013-01-26 16:40, Shane Ambler wrote:
On 27/01/2013 08:15, dweimer wrote:
I would like to lock down the USB serial port adapter used on the UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get a
clean shutdown in event of a power fa
On 2013-01-26 16:40, Shane Ambler wrote:
On 27/01/2013 08:15, dweimer wrote:
I would like to lock down the USB serial port adapter used on the
UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get
a
clean shutdown in event of a power failure.
I believe that this requires
On 27/01/2013 08:15, dweimer wrote:
I would like to lock down the USB serial port adapter used on the UPS to
/dev/cuaU0, to make sure the UPS is always monitored and I will get a
clean shutdown in event of a power failure.
I believe that this requires setting a hint line of some sort in the
/bo
I have two USB Serial adapters I use on my web server, ones always
connected, to allow NUT to monitor my UPS. The other I use to view the
console of my pfSense firewall, however I sometimes disconnect this one
to use it with my laptop to configure switches.
Because this one is unplugged and p
try CURRENT and uchcom does not work
under 6.3
Yes! It works (I think). Identifies itself as:
ucom0: on uhub1
ucom0: CH340 detected
After this it can be accessed like any other usb-serial device. Found
this note about it
http://err.no/personal/blog/tech/2008-07-22-10-17_kernel_patches_TEMPer_therm
Oliver Fromme пишет:
Michael Lednev wrote:
> Warren Block wrote:
> > Michael Lednev wrote:
> >
> > > I've obtained USB thermometer and want to make it usable with
> > > FreeBSD. It identifies itself as:
> > > kernel: ugen0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2
> > >
> > > Und
Michael Lednev wrote:
> Warren Block wrote:
> > Michael Lednev wrote:
> >
> > > I've obtained USB thermometer and want to make it usable with
> > > FreeBSD. It identifies itself as:
> > > kernel: ugen0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2
> > >
> > > Under Windows it looks like
Warren Block ?:
On Fri, 8 Aug 2008, Michael Lednev wrote:
I've obtained USB thermometer and want to make it usable with
FreeBSD. It identifies itself as:
kernel: ugen0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2
Under Windows it looks like standard COM-port. When I try to use some
exi
On Fri, 8 Aug 2008, Michael Lednev wrote:
I've obtained USB thermometer and want to make it usable with FreeBSD. It
identifies itself as:
kernel: ugen0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2
Under Windows it looks like standard COM-port. When I try to use some
existing drivers like uc
Hello.
I've obtained USB thermometer and want to make it usable with FreeBSD.
It identifies itself as:
kernel: ugen0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 2
Under Windows it looks like standard COM-port. When I try to use some
existing drivers like ucycom or uplcom it gives no effect.
I have a Keyspan usb serial port connected to a FreeBSD 6.1 server and
wondering how I can connect to it. Using minicom from a connected Linux
box, do I connect to a COM port, and how do I know what COM port? This
is what I see in dmesg:
ugen0: Keyspan, a division of InnoSys Inc. Keyspan USA-19H,
Tried and failed. It detected the device, but didn't know what to do
with it. I was trying the Edgeport/4 and Edgeport/8s.
On 2/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Anybody ever tried to run one of the following usb-serial devices on a
> FreeBSD 5/6 box? Does it work
Hello,
Anybody ever tried to run one of the following usb-serial devices on a
FreeBSD 5/6 box? Does it work out of the box, not work at all, work with
some driver code adjustments?
There is something about ETHERPORT4 in /usr/src/sys/dev/usb/usb_quirks.c
and /usr/src/sys/dev/usb/usbdevs, but I'm n
15 matches
Mail list logo
