0810alpha2 USB-UIRT, HA-22 ZWave stick not detected

[jhammond]

I've done a fresh install of 0810alpha2 following the wiki and installed the pluto-zwave-lighting package, however neither my usb-uirt nor Intermatic HA-22 stick are recognized and used. Both work plug and play in 0710 (after replacing the ZWave driver) however I can't even add them manually in 0810. A thumb drive with a movie on it was detected and used automatically so HAL seems to be working. Surely someone else with a usbuirt or zwave stick has done a fresh install with the new alpha and either gotten these working or run into a similar problem?

jhammond

[totallymaxed]

I've done a fresh install of 0810alpha2 following the wiki and installed the pluto-zwave-lighting package, however neither my usb-uirt nor Intermatic HA-22 stick are recognized and used. Both work plug and play in 0710 (after replacing the ZWave driver) however I can't even add them manually in 0810. A thumb drive with a movie on it was detected and used automatically so HAL seems to be working. Surely someone else with a usbuirt or zwave stick has done a fresh install with the new alpha and either gotten these working or run into a similar problem?

jhammond

Hi,

Well this is an Alpha... and the purpose of Alpha builds is to allow these types issues to be caught. If you choose to install the Alpha's then you will bump into this kind of 'gap'... our hope is that some of you will fix the issue and then post the fix to the Forum.

If you can't fix it yourself or do no have the time... then you'll just have to put up with these issues until someone else fixes them.

All the best

Andrew

[jhammond]

totallymaxed, I'm aware that this is just an alpha and that there are issues with it, which is why I'm posting this in the first place. Asking around in the irc channel, everyone is saying that both the usbuirt and zwave stick should be pnp in 0810 (they both are in 0710), however, I can't seem to get them to even work manually.

So, since no one else has complained about this and I've experienced it on several installs with different hardware: ISSUE: Caught.

Now, if someone with more experience than I wants to help me track down why this is happening, I'd love the help.
After a fresh install of kubuntu 8.10, I do:

Code: [Select]

apt-get update && apt-get dist-upgradethen reboot, which gives me an updated system running the 2.6.27-11-generic kernel. After the reboot, I install the nvidia 180.44 drivers from the nvidia site, then follow the alpha wiki:

Code: [Select]

sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh

However, before rebooting, I install id-my-disc from 0710, along with pluto-mythtv-player, pluto-mythtv-plugin, libdvdcss2, w32codecs and pluto-zwave-lighting. Following another reboot, the system starts the A/V Wizard, then the house setup and will eventually get to the lmce main screen. Media works just fine (about the only thing I've really messed with at this point).

Now, in 0710 (once I replaced the ZWave driver), both the USB-UIRT and my Intermatic HA-22 Zwave stick trigger alerts on the orbiter and walk through the setup. However, when I plug either in in 0810, nothing happens. I can plug a thumb-drive in and it's recognized and I'm asked if I want to use it, so it looks like HAL is running. Here are the relevant portions of the logs:

For Zwave stick:
    DCERouter.log: http://pastebin.com/f2ae2d2d5
   
    /var/log/syslog:

Code: [Select]

Apr  8 18:52:30 dcerouter kernel: [ 5199.356183] usb 1-3: new full speed USB device using ohci_hcd and address 10
Apr  8 18:52:30 dcerouter kernel: [ 5199.572178] usb 1-3: configuration #1 chosen from 1 choice
Apr  8 18:52:30 dcerouter kernel: [ 5199.780506] usbcore: registered new interface driver usbserial
Apr  8 18:52:30 dcerouter kernel: [ 5199.781724] usbserial: USB Serial support registered for generic
Apr  8 18:52:30 dcerouter kernel: [ 5199.782206] usbcore: registered new interface driver usbserial_generic
Apr  8 18:52:30 dcerouter kernel: [ 5199.782215] usbserial: USB Serial Driver core
Apr  8 18:52:30 dcerouter kernel: [ 5199.802966] usbserial: USB Serial support registered for SPCP8x5
Apr  8 18:52:30 dcerouter kernel: [ 5199.807798] spcp8x5 1-3:1.0: SPCP8x5 converter detected
Apr  8 18:52:30 dcerouter kernel: [ 5199.809878] usb 1-3: SPCP8x5 converter now attached to ttyUSB0
Apr  8 18:52:30 dcerouter kernel: [ 5199.814255] usbcore: registered new interface driver spcp8x5
Apr  8 18:52:30 dcerouter kernel: [ 5199.814280] spcp8x5: SPCP8x5 USB to serial adaptor driver v0.04


For USB-UIRT:
      DCERouter.log:

Code: [Select]

07 04/08/09 19:19:22.677 Event #65 has no handlers <0x85bc9b90>
07 04/08/09 19:19:22.678 Received Message from 16 (HAL / Bedroom (Master)) to -1001 (unknown / ), type 2 id 65 Event:Device Detected, retry none, parameters: <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 5(Mac Address):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 13(Text):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 28(IP Address):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 49(PK_DeviceTemplate): 0 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 51(VendorModelID): 0403f850 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 52(PK_CommMethod): 4 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 53(PK_PnpProtocol): 0 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 54(PNP Serial Number): /org/freedesktop/Hal/devices/usb_device_403_f850_noserial <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 55(DeviceData):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 56(Category):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 59(Signature): 16,HAL <0x85bc9b90>

     /var/log/syslog:

Code: [Select]

Apr  8 19:19:22 dcerouter kernel: [ 6811.413416] usb 1-8: configuration #1 chosen from 1 choice
Apr  8 19:19:22 dcerouter kernel: [ 6811.802171] usbserial: USB Serial support registered for FTDI USB Serial Device
Apr  8 19:19:22 dcerouter kernel: [ 6811.809704] ftdi_sio 1-8:1.0: FTDI USB Serial Device converter detected
Apr  8 19:19:22 dcerouter kernel: [ 6811.811227] ftdi_sio: Detected FT232RL
Apr  8 19:19:22 dcerouter kernel: [ 6811.813520] usb 1-8: FTDI USB Serial Device converter now attached to ttyUSB1
Apr  8 19:19:22 dcerouter kernel: [ 6811.814634] usbcore: registered new interface driver ftdi_sio
Apr  8 19:19:22 dcerouter kernel: [ 6811.814648] ftdi_sio: v1.4.3:USB FTDI Serial Converters Driver
I'm not sure of what I'm looking at or for exactly, but to me, it looks like the kernel sees both devices (as per syslog) and the DCERouter even does since it fires off events right when they're connected, but the HAL log doesn't show anything except the HAL service starting and stopping, so I'm not sure of what's happening there.

There is nothing about USBUIRT or ZWave in Wizard->Devices->Interfaces or in the device tree following a quick-reload of the router and running UpdateAvailableSerialPorts.sh, so my next step is to try adding them manually. If I go through Wizard->Devices->Interfaces and add either the USB-UIRT 0038 or USB-UIRT Embedded Transmit, the "Device Data" section is blank. This prevents me from putting in the Com Port and the device working as it should. 
I did just notice that even if I add the device via the Wizard and the "Device Data" section is empty, if I go through the Devices Tree and to the USBUIRT as a child of the Core/Hybrid, the "Device Data" section is available.

jhammond

[totallymaxed]

totallymaxed, I'm aware that this is just an alpha and that there are issues with it, which is why I'm posting this in the first place. Asking around in the irc channel, everyone is saying that both the usbuirt and zwave stick should be pnp in 0810 (they both are in 0710), however, I can't seem to get them to even work manually.

So, since no one else has complained about this and I've experienced it on several installs with different hardware: ISSUE: Caught.

Now, if someone with more experience than I wants to help me track down why this is happening, I'd love the help.
After a fresh install of kubuntu 8.10, I do:

Code: [Select]

apt-get update && apt-get dist-upgradethen reboot, which gives me an updated system running the 2.6.27-11-generic kernel. After the reboot, I install the nvidia 180.44 drivers from the nvidia site, then follow the alpha wiki:

Code: [Select]

sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz
tar xvf new-installer-alpha-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh

However, before rebooting, I install id-my-disc from 0710, along with pluto-mythtv-player, pluto-mythtv-plugin, libdvdcss2, w32codecs and pluto-zwave-lighting. Following another reboot, the system starts the A/V Wizard, then the house setup and will eventually get to the lmce main screen. Media works just fine (about the only thing I've really messed with at this point).

Now, in 0710 (once I replaced the ZWave driver), both the USB-UIRT and my Intermatic HA-22 Zwave stick trigger alerts on the orbiter and walk through the setup. However, when I plug either in in 0810, nothing happens. I can plug a thumb-drive in and it's recognized and I'm asked if I want to use it, so it looks like HAL is running. Here are the relevant portions of the logs:

For Zwave stick:
    DCERouter.log: http://pastebin.com/f2ae2d2d5
   
    /var/log/syslog:

Code: [Select]

Apr  8 18:52:30 dcerouter kernel: [ 5199.356183] usb 1-3: new full speed USB device using ohci_hcd and address 10
Apr  8 18:52:30 dcerouter kernel: [ 5199.572178] usb 1-3: configuration #1 chosen from 1 choice
Apr  8 18:52:30 dcerouter kernel: [ 5199.780506] usbcore: registered new interface driver usbserial
Apr  8 18:52:30 dcerouter kernel: [ 5199.781724] usbserial: USB Serial support registered for generic
Apr  8 18:52:30 dcerouter kernel: [ 5199.782206] usbcore: registered new interface driver usbserial_generic
Apr  8 18:52:30 dcerouter kernel: [ 5199.782215] usbserial: USB Serial Driver core
Apr  8 18:52:30 dcerouter kernel: [ 5199.802966] usbserial: USB Serial support registered for SPCP8x5
Apr  8 18:52:30 dcerouter kernel: [ 5199.807798] spcp8x5 1-3:1.0: SPCP8x5 converter detected
Apr  8 18:52:30 dcerouter kernel: [ 5199.809878] usb 1-3: SPCP8x5 converter now attached to ttyUSB0
Apr  8 18:52:30 dcerouter kernel: [ 5199.814255] usbcore: registered new interface driver spcp8x5
Apr  8 18:52:30 dcerouter kernel: [ 5199.814280] spcp8x5: SPCP8x5 USB to serial adaptor driver v0.04


For USB-UIRT:
      DCERouter.log:

Code: [Select]

07 04/08/09 19:19:22.677 Event #65 has no handlers <0x85bc9b90>
07 04/08/09 19:19:22.678 Received Message from 16 (HAL / Bedroom (Master)) to -1001 (unknown / ), type 2 id 65 Event:Device Detected, retry none, parameters: <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 5(Mac Address):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 13(Text):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 28(IP Address):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 49(PK_DeviceTemplate): 0 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 51(VendorModelID): 0403f850 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 52(PK_CommMethod): 4 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 53(PK_PnpProtocol): 0 <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 54(PNP Serial Number): /org/freedesktop/Hal/devices/usb_device_403_f850_noserial <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 55(DeviceData):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 56(Category):  <0x85bc9b90>
07 04/08/09 19:19:22.679   Parameter 59(Signature): 16,HAL <0x85bc9b90>

     /var/log/syslog:

Code: [Select]

Apr  8 19:19:22 dcerouter kernel: [ 6811.413416] usb 1-8: configuration #1 chosen from 1 choice
Apr  8 19:19:22 dcerouter kernel: [ 6811.802171] usbserial: USB Serial support registered for FTDI USB Serial Device
Apr  8 19:19:22 dcerouter kernel: [ 6811.809704] ftdi_sio 1-8:1.0: FTDI USB Serial Device converter detected
Apr  8 19:19:22 dcerouter kernel: [ 6811.811227] ftdi_sio: Detected FT232RL
Apr  8 19:19:22 dcerouter kernel: [ 6811.813520] usb 1-8: FTDI USB Serial Device converter now attached to ttyUSB1
Apr  8 19:19:22 dcerouter kernel: [ 6811.814634] usbcore: registered new interface driver ftdi_sio
Apr  8 19:19:22 dcerouter kernel: [ 6811.814648] ftdi_sio: v1.4.3:USB FTDI Serial Converters Driver
I'm not sure of what I'm looking at or for exactly, but to me, it looks like the kernel sees both devices (as per syslog) and the DCERouter even does since it fires off events right when they're connected, but the HAL log doesn't show anything except the HAL service starting and stopping, so I'm not sure of what's happening there.

There is nothing about USBUIRT or ZWave in Wizard->Devices->Interfaces or in the device tree following a quick-reload of the router and running UpdateAvailableSerialPorts.sh, so my next step is to try adding them manually. If I go through Wizard->Devices->Interfaces and add either the USB-UIRT 0038 or USB-UIRT Embedded Transmit, the "Device Data" section is blank. This prevents me from putting in the Com Port and the device working as it should. 
I did just notice that even if I add the device via the Wizard and the "Device Data" section is empty, if I go through the Devices Tree and to the USBUIRT as a child of the Core/Hybrid, the "Device Data" section is available.

jhammond

Well you could do an lsusb find the manufacturer/deviceid for the HA-22 then look at device template 1754 and see if the HA-22 is one of the listed, and therefore detectable, devices...

Andrew

[jhammond]

Bus 001 Device 008: ID 04fc:0204 Sunplus Technology Co., Ltd
Bus 001 Device 007: ID 0403:f850 Future Technology Devices International, Ltd

The top device is the Intermatic Stick, which is included in the PNP section of the ZWave driver (#1754). To me, from looking at the logs, it looks like the device is seen by HAL and DCERouter, but I don't know enough to figure out where the next place it could fail is. I also saw events being added to the PnpQueue in pluto_main, but I'm not sure what to do with that info.

jhammond

[totallymaxed]

Bus 001 Device 008: ID 04fc:0204 Sunplus Technology Co., Ltd
Bus 001 Device 007: ID 0403:f850 Future Technology Devices International, Ltd

The top device is the Intermatic Stick, which is included in the PNP section of the ZWave driver (#1754). To me, from looking at the logs, it looks like the device is seen by HAL and DCERouter, but I don't know enough to figure out where the next place it could fail is. I also saw events being added to the PnpQueue in pluto_main, but I'm not sure what to do with that info.

jhammond

Which ZWave driver binary are you using? The original LinuxMCE-0710 ZWave driver or the newer Open ZWave driver by Hari?

Andrew

[tschak909]

It's 0810, so it's Hari's driver.

Can someone else please try to reproduce the problem with this week's build?

-Thom

[jhammond]

It is the newer, open, ZWave driver included in 0810, however, I don't think that it's specifically a z-wave problem since the USBUIRT isn't recognized either. Honestly I don't know nearly as much as I'd like to about things in general, but in my mind, both the HA-22 and USBUIRT are USB devices with serial converters and there's not a lot of similarity between them other than that, so, it seems to me that the problem is with recognizing Serial->USB connections (there's a trac ticket about devices with multiple serial interfaces only recognizing one, but I don't think it's the same thing).

I've seen this behaviour since I started messing with 0810, so at least since alpha 2.2

A little off-topic, but would be helpful regardless: is there a chart showing data-flow through LMCE in regards to DCE and all of it's devices? I guess I'm asking for something that would allow me to visually trace what happens when I plug in a new device, regardless of what it is, or say, execute a scenario from an orbiter.

jhammond

[tschak909]

You may want to start with the developers guide in the wiki.

-Thom

[totallymaxed]

It's 0810, so it's Hari's driver.

Can someone else please try to reproduce the problem with this week's build?

-Thom

Good spot on the driver ;-)

Its a public holiday weekend here...but I will test the Seluxit and the Tricklestar ZWave interfaces on the latest 0810 build on Tuesday.

Andrew

[jhammond]

Any update on this yet? I haven't had a chance to build a fresh system in a few days and am now waiting for the 04/19 updated install scripts. I'd love to find out if I'm just crazy or not.

jhammond

[jhammond]

I just saw that. Yeah, it can be hard to get responses here for the alpha releases, but, this at least tells me that there is a problem. I've been holding off of filing a bug (this is a release-stopper if multiple people can't get 2 of the most common interfaces to work), but I might have to just go ahead and hope someone else deals with it. I'd be happy to help anyone who wants to work on this and Thom has given me some advice, but other than yourself, no one else seems to have this issue. Can you try installing with the 0710 release and verifying that both your usb-uirt and MS MCE dongle work as they should? Also, can you post the syslog from when you plug in both devices? So far, the only thing I can find in common between my devices that aren't working is that they use a USB-SERIAL converter. My pure usb devices (mouse, keyboard, thumbdrive) all work without an issue, so I'm still of the belief that it has something to do with the USB-SERIAL conversion.

Surely somebody else has to have done a fresh install using the 0810 scripts and come up against this?
I fully understand that there is no support for the alpha releases, but I've seen multiple people trying to help the effort shut-down with "There is no support for the alpha"-type answers when they bring up issues. I don't think rodercot and I are having "You didn't follow the instructions"-problems, as I'm positive that I have followed the instructions to the letter. However, 2 of the devices that are supposed to be plug and play (and control a good bit of the impressive features of LMCE) are not. Don't take this as bitching or whining, I'm just trying to sort out an issue that is very frustrating to have everyone else say: "Well, it should work" only for it to not work. It worked in 0710 and I've managed to get it going, with the same hardware as I'm trying to use now, so, the only difference is 0810. I don't doubt that other people have them up and running, however, I'm wondering if anyone who does, has done a fresh install from one of the recent builds, or if they started an install a while back and have tweaked it to work over time.

jhammond

[itspac]

on my alpha install that i installed a couple weeks ago, usbuirt and my MCV zwave stick isnt recognized.  On previous alpha tries usbuirt and intermatic ha22 didnt work.
i just wrote these items off as being an alpha release and byt time it gets to beta, if it still didnt work ( which is when all installed features should be mostly working as most release cycles go) I would speak up. 

[qball4]

I'm having the same problem on the latest 0810 build with the MCV Z-Wave dongle and the UIRT. If I add the MCV dongle manually in the webadmin it works fine, but I'm stuck on the UIRT for now. I'm reinstalling 0810 for the third time tonight and if it still doesn't work I'll post some the syslog.

:Matt

[tschak909]

The Fiire Remote will not work, until HIDRemote.cpp in Orbiter gets a major rewrite.

The 8.10 kernel has facilities for parsing raw HID packets, which are now interfering with the libusb calls that Orbiter needs to make to control and bind to the remote. I am looking for a solution, but as of now, priority of adding support for the GYR3101US and a Generic kernel input device decoder takes precedent.

-Thom