Re: NanoBSD install phase failing for releng/11

2016-08-26 Thread Bryan Drewery 
On 8/24/2016 10:46 AM, Bryan Drewery wrote:
> On 8/24/16 7:55 AM, Bryan Drewery wrote:
>> On 8/22/2016 4:08 AM, Guido Falsi wrote:
>>> Hi,
>>>
>>> While building a NanoBSD image using releng/11 sources I got this error
>>> message:
>>>
>>> ===> lib/libc++ (install)
>>> install  -C -o root -g wheel -m 444   libc++.a
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/
>>> install  -s -o root -g wheel -m 444 libc++.so.1
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/
>>> install  -S -C -o root -g wheel -m 444   libc++.ld
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/libc++.so
>>> ===> lib/libcxxrt (install)
>>> install  -C -o root -g wheel -m 444   libcxxrt.a
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/
>>> install  -s -o root -g wheel -m 444 libcxxrt.so.1
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/lib/
>>> install -l rs  /usr/local/nanobsd/rr-trunk/obj/_.w/lib/libcxxrt.so.1
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib/libcxxrt.so
>>> install: symlink ../../lib/libcxxrt.so.1 ->
>>> /usr/local/nanobsd/rr-trunk/obj/_.w/usr/lib: File exists
>>> *** Error code 71
>>>
>>> Stop.
>>>
>>> I'm not sure what's happening, I already tried reverting locally
>>> r301880, thinking it could be related, but this changed nothing.
>>>
>>> Anyone has some insight? It was working fine up to August 4th.
>>>
>>> Thanks in advance to anyone giving me some hint!
>>>
>>
>> Is this still reproducible for anyone?  I have theories but need it in
>> its broken state to debug it further.
>>
> 
> I've created a trivial reproducibility on it and am working on a fix.
> So far it appears to be purely an issue in head with dirname(3) compat.
> 

This is fixed in head r304860 by ed@. It requires updating the host.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: Digi Watchport/T temperature sensor as /dev/ttyU

2016-08-26 Thread O. Hartmann 
Am Fri, 26 Aug 2016 15:53:55 +0200
Hans Petter Selasky  schrieb:

> On 08/26/16 15:38, O. Hartmann wrote:
> > It is a USB interface PCB with an AT90USB162 microcontroler chip.
> > Attached to a FreeBSD 12-CURRENT system, it reports itself as a UHID device.
> > there is also a software package available - for Windows and Linux, but it
> > doesn't work for FreeBSD, the package compiles and produces a cmdline 
> > binary,
> > but it fails reading the sensor data - the uhid driver seems to be unloaded
> > during the call. I have no skills in writing low-level USB software, so my
> > explanation is slopy, sorry. But there is hope I can use this one.  
> 
> Hi,
> 
> Could you send a link to this Linux software?
> 
> It should work basically!
> 
> Is your libusb up-to-date?
> 
> You can trace USB activity using "usbdump -i usbusX -f Y -s 65536 -vvv".
> 
> Maybe some command failed.
> 
> Did you try "usbhidaction" to decode the data received?
> 
> --HPS
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Hello,

I would already have, but the site was offline due to maintenance cycles this 
noon. It is
in German ;-)

The software can be downloaded via

http://www.led-genial.de/mediafiles//Sonstiges/TempSensorTester.zip

Please do not misunderstand me: I just did a dirty test and it worked half way, 
but never
got values from the temperature sensor.

Since the device is recognized by FreeBSD as a UHID device, I guess there is a 
much more
convenient and standardized way to look for the device and pick up data for, 
say ICINGA-2
or other measurements. The software provided works well on Linux. On FreeBSD, 
running the
binary as root, firt unloads the uhid kernel module. So I guess the procedure is
Linux'ish and needs to be rewritten for proper *BSD usage.

Anyway - this part is more bringing up my personal thoughts and intentions and 
not so
much related to the initial stuff I asked the list for - this PCB in question 
is much to
expensive for a simple temp sensor via 1-wire protocol, so I'm looking for 
something much
cheaper. There are offerings for very small Arduino PCBs with USB port and I2C 
or 1-wire
connectors for approx. 3 - 5 EUR. For a server-based USB attached DS18B20 
sensor which
could be simply interrogated by some simple C code via tty/uhid or something 
high level
would be very nice. The digi Watchport provided this with Linux - the access 
was done via
Perl.

Looking for a small and autonomous sensor station I stumbled over a lot of 
useful Linux
stuff realized via Raspberry Pi. There is very little for FreeBSD and I 
hesitate buying a
nice RaspberryPi 3 B or ODROID-C2 for that purpose. For autonomous monitoring 
of a server
room we use very expensive (~300 EUR each) web based devices. It is a little 
box with a
DS18B20, I guess and fancy LEDs as well as a NIC. attached to the network, you 
can
configure the device and there is some rrdtool-like graphical output. 

I think, with the fancy framework of FreeBSD it should be possible to adapt 
NanoBSD with
small nginx or reduced Apache to perform the stuff ...

So, sorry for listening to my little-boy's dreaming

Kind regards,

Oliver


pgpZ1Ez9m8C9N.pgp
Description: OpenPGP digital signature

Re: Digi Watchport/T temperature sensor as /dev/ttyU

2016-08-26 Thread Hans Petter Selasky 

On 08/26/16 15:38, O. Hartmann wrote:

It is a USB interface PCB with an AT90USB162 microcontroler chip.
Attached to a FreeBSD 12-CURRENT system, it reports itself as a UHID device.
there is also a software package available - for Windows and Linux, but it
doesn't work for FreeBSD, the package compiles and produces a cmdline binary,
but it fails reading the sensor data - the uhid driver seems to be unloaded
during the call. I have no skills in writing low-level USB software, so my
explanation is slopy, sorry. But there is hope I can use this one.


Hi,

Could you send a link to this Linux software?

It should work basically!

Is your libusb up-to-date?

You can trace USB activity using "usbdump -i usbusX -f Y -s 65536 -vvv".

Maybe some command failed.

Did you try "usbhidaction" to decode the data received?

--HPS


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Digi Watchport/T temperature sensor as /dev/ttyU

2016-08-26 Thread O. Hartmann 
On Sun, 24 Jul 2016 13:12:35 -0600
Ian Lepore  wrote:

> On Sun, 2016-07-24 at 12:52 -0600, Warner Losh wrote:
> > On Sun, Jul 24, 2016 at 12:42 PM, Kevin Oberman 
> > wrote:  
> > > There are several different USB serial drivers. Off-hand I see
> > > ubser, ubsa,
> > > uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom,
> > > usb_serial, uslcom, and uvscom. Whether any of these will support
> > > the TI
> > > chip, I can't say. Most have man pages, but a few, as has been
> > > noted, are
> > > lacking one.  
> > 
> > I tried to automate discovery of these things. However, the only way
> > you can really know for sure about the TI chip is to read it's
> > datasheet
> > and compare that with extant drivers. It's actually easier than it
> > sounds.
> > 
> > I've often thought of unification of the TTY USB drivers, since they
> > are
> > most (but not all) based on the standard plus extra bits.
> > 
> > Warner  
> 
> To reiterate:  we do not have a driver for TI 5052 chips.
> 
> It's not much like other usb-serial chips.  In fact it's not strictly a
> usb-serial chip, it's a multifunction chip that includes a software
> -controllable usb hub, 2 serial ports, gpio, an i2c bus master, an MCU
> interface, a multichannel DMA controller, and apparently even has the
> ability to download your own 8052-compatible microcontroller code into
> the 5052 and have it take over from the built-in rom code.
> 
> It would be reasonable enough to write a driver that initially
> supported only the uart part of the chip.
> 
> -- Ian

It is me again.

I opened one of those digi watchports since I read that Ti has discontinued the
TI5052 chip and encourage developers to use a newer one. The print on the chip
itself residing on the PCB is TUSB3410I and this refers to a Ti TUSB3410 as it
is referred to by the TI 5052 page:
 
http://www.ti.com/product/TUSB3410

I never wrote a driver my own, so starting from scratch would be inefficient,
but for the long shot, it might be an idea.

Thanks anyway for the efford taken to look into it. I hope we will see at least
some manpage for ugensa.

I'm still looking for simple sensor devices which could be attached to FreeBSD
for monitoring temperature and/or humidity - as it was intended by using the
digi watchport. I'm now with an experimental piece of hardware with two DALLAS
DS18B20 temperature sensors.

It is a USB interface PCB with an AT90USB162 microcontroler chip.
Attached to a FreeBSD 12-CURRENT system, it reports itself as a UHID device.
there is also a software package available - for Windows and Linux, but it
doesn't work for FreeBSD, the package compiles and produces a cmdline binary,
but it fails reading the sensor data - the uhid driver seems to be unloaded
during the call. I have no skills in writing low-level USB software, so my
explanation is slopy, sorry. But there is hope I can use this one.

Kind regards,

Oliver 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

r304844: compiler error: fastpath.c:1088:39: error: too few arguments to function call, expected 4, have 3

2016-08-26 Thread O. Hartmann 
Recent CURRENT as of r304844 fails to compile a kernel due to the error shown
below.

[...]
===> syscons/snake (all)
--- all_subdir_tcp/fastpath ---
cc_ack_received(tp, th, CC_ACK);
~~~   ^
/usr/src/sys/netinet/tcp_var.h:786:1: note: 'cc_ack_received' declared here
voidcc_ack_received(struct tcpcb *tp, struct tcphdr *th,
^
/usr/src/sys/modules/tcp/fastpath/../../../netinet/tcp_stacks/fastpath.c:1088:39:
error: too few arguments to function call, expected 4, have 3
cc_ack_received(tp, th, CC_DUPACK);

[...]



regards,

oh
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"