osmc@osmc:~$ sudo modprobe cp210x

modprobe: FATAL: Module cp210x not found.

I will begin the Google quest.   Thanks for the direction and I will update 
more as I find it...

On Saturday, August 27, 2016 at 8:35:24 PM UTC-4, Tom Keffer wrote:
>
> OK, maybe you are missing the device driver.
>
> It looks like your USB uses a CP210x controller (all Davis loggers seem to 
> use this chip), so you want the cp210x driver. Try
>
> lsmod
>
>
> and see if it has been loaded. If not, you can see if it is available on 
> your system:
>
> grep cp210x /lib/modules/$(uname -r)/modules.dep
>
>
> If it is available, load it with
>
> sudo modprobe cp210x
>
>
> If it is not available, you will have to do some Googling to see if it's 
> available for your machine. Chances are it's out there somewhere. Then 
> you'll have to build and install. I'm not an expert on this, but if you get 
> stuck, I will try to help you out. Others in the user's group have much 
> more experience at this...
>
> -tk
>
>
>
> On Sat, Aug 27, 2016 at 5:12 PM, Bill Unger <[email protected] 
> <javascript:>> wrote:
>
>> I only get 2 lines:
>>
>> [ 1917.999902] usb 2-1: USB disconnect, device number 2
>>
>> [ 1938.976526] usb 2-1: new full-speed USB device number 4 using uhci_hcd
>>
>>
>> Oddly, it never seems to mount anything.
>>
>>
>> running the lsusb command returns:
>>
>>
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> Bus 002 Device 003: ID 05ac:8241 Apple, Inc. Built-in IR Receiver
>>
>> Bus 002 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x 
>> UART Bridge / myAVR mySmartUSB light
>>
>> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>
>>
>> That third line is the USB logger, so the system sees it...  it just 
>> doesn't seem to do anything with it.
>>
>>
>>
>> On Saturday, August 27, 2016 at 7:19:41 PM UTC-4, Tom Keffer wrote:
>>>
>>> It's possible that some usb driver is missing on the Apple Tv.
>>>
>>> Another possibility is that you simply have the wrong port. It may be 
>>> something else besides /dev/ttyUSB0 on the Apple TV. Try unplugging you 
>>> logger, then plug it back in. Then type
>>>
>>> dmesg | tail
>>>
>>> This may give you a hint what port is being used. If this doesn't work, 
>>> then we can worry about the driver.
>>>
>>> -tk
>>>
>>>
>>>
>>>
>>> On Sat, Aug 27, 2016 at 3:53 PM, Bill Unger <[email protected]> wrote:
>>>
>>>> Quick summary:
>>>>
>>>> WEATHER HARDWARE:  Davis Vantage Vue
>>>> CONNECTION:  WeatherLink USB Data Logger
>>>> OPERATING SYSTEM:  Debian 8.5  on an Apple TV Gen 1 ( originally 
>>>> installed using OSMC ).
>>>>
>>>> I have installed WeeWX and when launching, it throws these messages in 
>>>> syslog:
>>>>
>>>> Aug 27 18:44:32 osmc weewx[1510]: engine: Loading station type Vantage 
>>>> (weewx.drivers.vantage)
>>>>
>>>> Aug 27 18:44:32 osmc weewx[1510]: engine: Unable to load driver: could 
>>>> not open port /dev/ttyUSB0: [Errno 2] No such file or directory: 
>>>> '/dev/ttyUSB0'
>>>>
>>>>
>>>> My thoughts are that the driver for the WeatherLink USB is not 
>>>> installed.  I originally had it installed on a Mac and had to install the 
>>>> SILABS USB to UART Bridge driver and am wondering if something similar is 
>>>> required on Debian?
>>>>
>>>>
>>>> Thanks in advance for any help!!
>>>>
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to