Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Installation issues / Re: 14.04 MythTV problems,All Tuners busy(solved)
« Last post by S4Howie on February 10, 2016, 09:02:28 pm »
phenigma thank you very much that made it work,changed the Input priority fom 0 to 1 made it work.
Thank you for the super fast responding and the absolute right awnser.

Just a hind now with a working Mythtv Backend <0.25 you are able to use Amazon Fire TV Stick with Kodi installed to connect as Myth Frontend and use ur hole PVR.
Also Kodi is running on windows and linux and android devices,what makes some simple TV Clients for ones Master Backend running under LinuxMCE.

Thank you
12
Installation issues / Re: 14.04 MythTV problems,All Tuners busy
« Last post by phenigma on February 10, 2016, 06:27:11 pm »
Thanks for the info about your success so far.

If I remember correctly you will need to go into mythtv-setup and set the live tv tuner priorities to fix this issue.  This is new in newer mythtv and not something that is being done automatically by lmce setup.

Good luck!

J.
13
Users / Re: The return of CDDB and CD-Ripping
« Last post by tschak909 on February 10, 2016, 06:19:08 pm »
Fantastic! Great work! :)

-Thom
14
Installation issues / [SOLVED]14.04 MythTV problems,All Tuners busy
« Last post by S4Howie on February 10, 2016, 05:55:54 pm »
Hi all,i am huge Fan of LinuxMCE since several years,i worked long time now with 7.10 cause i could grap a Firre Chief Remote in Europe some years ago and just fell in love with with it.

But now since the time of Smartphones and Pad´s,i decided to go with newer LinuxMCE version. I tested a lot in the last days with several version out there,i am impressed what you guys did the last years,many really good improvments i recognized so far. I need to say a BIG Thank You for all the work you done here Developers!!

Ok more to the point:
I ended up trying 14.04 until now,cause here i manged to get most things work i want to work.I am still testing hard and will try to help you further in next time as much as i can.
I have 14.04 installed over the Net,with Kubuntu 14.04.03 preinstalled and updated,after that i updated LinuxMCE aswell.So i am at Version 2.0.0.47.201601312359+296fdcd3 atm.

My WinTV Nexus-S DVB-S Card was recognized from LinuxMCE by pnp,but i had to copy the prober firmware files into /lib/firmware cause MythTV could not get a lock,it was seen but couldnt be open.After that i reboot,went back to MythTV setup and Card could be opened.So i setup the Video Sources and Input Connection and did a Channel Search,everything went fine all channels there,lock on all Transponders,no problems.

But here is the problem now,when i start to watch a channel MythTV Frontend Opens up and tries to Tune in but immidently tells me: All Tuners are currently Busy! it repeats and repeats and after serveral tries it want to reload the Backend,but a reset isnt helping much further in my case.
If i take a look at the Status page from Mythweb i can see 1 Encoder on the core currently not recording.So everything looks like prober installed,i could search for channels aswell in the setup.
I tried several things like deleting all the TV Tuners in MythTv Setup,and put them back in,i recognized sometimes LinuxMCE installs a Encoder again and shows up 2 or more after a reboot.So i deleted all Encoders again and just did a reboot and the encoder was installed again in MythTV.I just need to setup the LNB and it could work. But again in the Frontend i just receive All Tuners are Busy. I also tried several different IP for the Frontend to connect like 127.0.0.1/localhost/internal,external IP but the error still stays.

My Nexus Card worked well in all LinuxMCE releases up to 10.04,im still using it in a other install under 10.04 so the hardware is alive.

Can anyone help me further what causes the All Tuners busy error?

Thank you so far,
Howie
15
Installation issues / Re: Shutdown problem
« Last post by phenigma on February 10, 2016, 06:14:40 am »
This is by design and not a 'problem'.  Glad it's not.  ;)

J.
16
Installation issues / Re: [SOLVED] 12.04 Aeon Z-stick (Zwave) is not detected by PnP
« Last post by phenigma on February 10, 2016, 06:13:43 am »
It looks like your serial ports are not translating properly to actual /dev/tty devices all the time.  This looks to me like the device is dropping off the usb bus.  Sometimes the translate gets a result and other times not.  The only reason that would happen is if the device is not present anymore.  You might turn on LV_STATUS and LV_DEBUG loglevels and tail the HAL log to see if the device is disconnecting.

J.
17
Installation issues / Re: [SOLVED] 12.04 Aeon Z-stick (Zwave) is not detected by PnP
« Last post by tompin2 on February 10, 2016, 06:03:59 am »
I added Manually the zstick for testing, this is the error I get

Code: [Select]
== FRESH START ==
1 02/09/16 20:05:16 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:05:16 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:05:16 267 (spawning-device) Starting... 1
1 02/09/16 20:05:16 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:05:16.758 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
05 02/09/16 20:05:16.758 The router must be reloaded before this device is fully functional <0xb6e83700>
05 02/09/16 20:05:16.759 void ClientSocket::Disconnect() on this socket: 0x946a610 (m_Socket: 5) <0xb6e83700>
05 02/09/16 20:05:16.811 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 20:06:55.412 Got a reload command from 0  <0xb5affb40>
05 02/09/16 20:06:55.664 void ClientSocket::Disconnect() on this socket: 0x946af18 (m_Socket: 6) <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveData 0x946a378 failed, bytes left -1 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e83700>
01 02/09/16 20:06:55.665 Lost connection device: 267 <0xb6e83700>
05 02/09/16 20:06:55.665 Handshake failed. Retrying in 5 seconds <0xb6e83700>
05 02/09/16 20:07:01.672 Connect() failed, Error Code 111 (Connection refused)) <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 268 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 269 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
01 02/09/16 20:07:04.790 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result /dev/ttyUSB0 <0xb6e83700>
05 02/09/16 20:13:09.968 Got a reload command from 0  <0xb46ffb40>
== ATTEMPT FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) 2017 Dev: 267; Already Running list: 15,33,
== FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:41:31 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:41:31 267 (spawning-device) Starting... 1
1 02/09/16 20:41:31 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:41:31.558 Creating child 268 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 20:41:31.559 Creating child 269 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 20:41:31.619 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 21:07:11.236 Got a reload command from 0  <0xb5affb40>
05 02/09/16 21:07:11.488 void ClientSocket::Disconnect() on this socket: 0x9699ef8 (m_Socket: 6) <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveData 0x969f2c0 failed, bytes left 0 start: 30000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e9c700>
01 02/09/16 21:07:11.489 Lost connection device: 267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Handshake failed. Retrying in 5 seconds <0xb6e9c700>
05 02/09/16 21:07:17.495 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:18.496 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 268 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 269 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 21:07:21.613 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>


What is this connection refused?

Regards,

TP
18
Installation issues / Re: 12.04 Aeon Z-stick (Zwave) is not detected by PnP
« Last post by tompin2 on February 10, 2016, 01:19:18 am »
PnpQueue::Process_Detect_Stage_Confirm_Possible_DT queue 7850 already unknown <0x8b9adb40>

^^ This line here indicates that the device is found in the Unknown Devices table.  Which means it has been told to Not be used and don't ever ask me again.  Hence why it is not adding the device.  Find the device in the webadmin -> advanced -> unknown devices list and remove it.  It should add itself the next time it is detected.

J.

Hi Phenigma,

Im Having more or less the same issue but in my case there is nothing under unknown devices.  How the issue was caused.  I wanted to do a fresh start of the zwave config, because I messed up one of my motion sensors and I was unable to remove it.  I used webadmin and removed zwave device, pull the stick out, reset the stick and the minimote and plug the zstick back again but it does not get detected by PNP.  Linux is detecting it and setting as ttyusb0

157645.840518] usb 1-1.6.2: cp210x converter now attached to ttyUSB0

But nothing happens later, there is no pnpqueue on the log registered neither. 
Any hints?

TP
19
Installation issues / Re: Shutdown problem
« Last post by posde on February 09, 2016, 11:11:51 pm »
Glad to be of help :)
20
Installation issues / Re: Shutdown problem
« Last post by maverick0815 on February 09, 2016, 10:48:38 pm »
 :) works
Pages: 1 [2] 3 4 ... 10