Messages

121

Installation issues / Re: keeping test systm updated with Alpha2 weekly builds

« on: May 22, 2009, 05:36:21 am »

Hi Pigdog,

I had thought I was getting updates when doing it, but only the KUBUNTU updates were being processed.
I have a 64bit system and noticed that all athe updates are only i386.
How can I get the 64bit updates.

gadget

122

Installation issues / Re: can't get MD on Alpha 2 to start

« on: April 28, 2009, 04:52:38 pm »

Hi Pigdog,

I have resolved my issue and now have a working MD. After running the script(Used Web Admin) to create MDś I think I missed the quick reload router as it now works. I did not have to set the MD to i386 so have an amd64 MD.

Will now install some TV cards to into test system and continue playing.

Thanks for the help.

gadget

123

Installation issues / Re: can't get MD on Alpha 2 to start

« on: April 27, 2009, 01:16:20 am »

I am using UI1.

124

Installation issues / can't get MD on Alpha 2 to start

« on: April 26, 2009, 11:54:36 am »

Hi All,

I have gone through all steps for creating diskless MD and everything is fine untill the prompt_user_window comes up with the message "The UI is being regenerated. This will take 15-30 minutes. ...."

I have left it running overnight but still MD wont start. I have also checked output on TTY1 and there is no activity.

gadget

125

Installation issues / Re: keeping test systm updated with Alpha2 weekly builds

« on: April 20, 2009, 03:32:54 pm »

Thanks. I assumed that only did the Kububtu part.

126

Installation issues / keeping test systm updated with Alpha2 weekly builds

« on: April 20, 2009, 10:58:18 am »

I have a test system with Alpha 2 from march and want to be able to get latest weekly build without doing a fresh Kubuntu install. 

127

Installation issues / Re: Recurrent media freezes while watching or listening to media on MD

« on: April 10, 2009, 12:46:00 am »

I had similar problem with watching TV on MD. lots of freezing and also couldn't copy large files to/from core. I had to disable APIC in mobo BIOS and that fixed the problem for me. Check your system log file there will probably be a persistent eth0 warning.

128

Installation issues / Capture Cards change order after reboot

« on: April 06, 2008, 09:01:37 am »

I have 2 x captue cards in my Core
1 x Winfast DTV2000H for HDTV.
1 x Genius Videowonder for Cable using the analogue imput.

I have everything working in MythTV, but when I reboot the cards change their order and MythTV needs to be reconfigured.
How can I force the cards to be detected in a specific order.

gadget

129

Installation issues / Re: Serial IR Blaster setup

« on: April 05, 2008, 03:09:32 am »

Thom,

I have been doing further setup with the GC100 and think I have found the reason for it not working in BETA4.
The reason that the TX-SR304 keeps detaching itself from the GC100 IR port is that the ports get a new number everytime the gc100 is reset.

This is the log for the gc100 after a device reset.

========= NEW LOG SECTION ==========
1   04/05/08 09:50:25   37 (spawning-device)   Starting... 1
1   04/05/08 09:50:25   37 (spawning-device)   Found /usr/pluto/bin/LaunchGC100.sh
05   04/05/08 9:50:26.684      Connect() failed, Error Code 111 (Connection refused)) <0x2ae656770ad0>
05   04/05/08 9:50:27.684      Connect() failed, Error Code 111 (Connection refused)) <0x2ae656770ad0>
05   04/05/08 9:50:28.696      Connect() failed, Error Code 111 (Connection refused)) <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Creating child 110 <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Creating child 111 <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Creating child 112 <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2ae656770ad0>
05   04/05/08 9:50:29.795      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2ae656770ad0>
05   04/05/08 10:31:47.321      Got a reload command from 0  <0x41001950>
05   04/05/08 10:31:48.236      void ClientSocket::Disconnect() on this socket: 0x647230 (m_Socket: 7) <0x2ae656770ad0>
Return code: 2
2   04/05/08 10:31:48   37 (spawning-device)   Device requests restart... count=1/50 dev=37
Sat Apr  5 10:31:48 EST 2008 Restart
========== NEW LOG SECTION ==========
1   04/05/08 10:31:56   37 (spawning-device)   Starting... 1
1   04/05/08 10:31:56   37 (spawning-device)   Found /usr/pluto/bin/LaunchGC100.sh
05   04/05/08 10:31:56.438      Creating child 117 <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Creating child 118 <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Creating child 119 <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b07a7429ad0>
05   04/05/08 10:31:56.438      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b07a7429ad0>
05   04/05/08 10:53:44.024      Got a reload command from 0  <0x41001950>
05   04/05/08 10:53:44.936      void ClientSocket::Disconnect() on this socket: 0x647230 (m_Socket: 7) <0x2b07a7429ad0>
Return code: 2
2   04/05/08 10:53:44   37 (spawning-device)   Device requests restart... count=1/50 dev=37
Sat Apr  5 10:53:45 EST 2008 Restart
========== NEW LOG SECTION ==========
1   04/05/08 10:53:53   37 (spawning-device)   Starting... 1
1   04/05/08 10:53:53   37 (spawning-device)   Found /usr/pluto/bin/LaunchGC100.sh
05   04/05/08 10:53:54.222      Creating child 120 <0x2b2faa61cad0>
05   04/05/08 10:53:54.222      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b2faa61cad0>
05   04/05/08 10:53:54.222      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b2faa61cad0>
05   04/05/08 10:53:54.222      Creating child 121 <0x2b2faa61cad0>
05   04/05/08 10:53:54.223      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b2faa61cad0>
05   04/05/08 10:53:54.223      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b2faa61cad0>
05   04/05/08 10:53:54.223      Creating child 122 <0x2b2faa61cad0>
05   04/05/08 10:53:54.223      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b2faa61cad0>
05   04/05/08 10:53:54.223      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b2faa61cad0>
05   04/05/08 11:01:49.662      Got a reload command from 0  <0x41001950>
05   04/05/08 11:01:50.555      void ClientSocket::Disconnect() on this socket: 0x647230 (m_Socket: 7) <0x2b2faa61cad0>
Return code: 2
2   04/05/08 11:01:50   37 (spawning-device)   Device requests restart... count=1/50 dev=37
Sat Apr  5 11:01:50 EST 2008 Restart
========== NEW LOG SECTION ==========
1   04/05/08 11:01:58   37 (spawning-device)   Starting... 1
1   04/05/08 11:01:58   37 (spawning-device)   Found /usr/pluto/bin/LaunchGC100.sh
05   04/05/08 11:01:58.752      Creating child 120 <0x2b936a2e3ad0>
05   04/05/08 11:01:58.752      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b936a2e3ad0>
05   04/05/08 11:01:58.752      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b936a2e3ad0>
05   04/05/08 11:01:58.752      Creating child 121 <0x2b936a2e3ad0>
05   04/05/08 11:01:58.752      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b936a2e3ad0>
05   04/05/08 11:01:58.752      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b936a2e3ad0>
05   04/05/08 11:01:58.753      Creating child 122 <0x2b936a2e3ad0>
05   04/05/08 11:01:58.753      Note: Device manager has attached a device of type 1912 that this has no custom event handler for.  It will not fire events. <0x2b936a2e3ad0>
05   04/05/08 11:01:58.753      Note: Device manager has attached a device of type 1912 that this has no custom handler for.  This is normal for IR. <0x2b936a2e3ad0>


gadget

130

Installation issues / Re: Serial IR Blaster setup

« on: March 31, 2008, 12:33:16 pm »

peteK--

when I am talking about the link breaking i mean in the device tree of the web admin page. I do have the gc100 serial port available but I haven't bothered configuring it yet as i can't get the IR port to control the receiver/amp.

gadget

131

Installation issues / Re: Serial IR Blaster setup

« on: March 29, 2008, 11:41:14 pm »

Hi Thom,

Thanks for the remote support last weekend. As you noticed the TX-SR304 was no longer controlled by the gc100 2:1 transmitter which I had definitely setup. I found that everytime i rebooted the core the link broke and I was always getting new hardware being detected on startup.

Did a re-install of core yesterday from dvd x64 but still have same issues.
1. always detects new hardware on startup
2. tx-sr304 and gc100 loose link
3. cant transmit IR ( probably because the link isnt working)  When I go to the help me choose page I can't select the output device. always goes back to 'please select'.

How do i find out which hardware is always being detected ie which log should i check.

gadget

132

Installation issues / Re: Serial IR Blaster setup

« on: March 23, 2008, 07:18:22 am »

I have setup the onkyo receiver as the device to be controlled by the GC100 but cant get anything to send to the GC100 port.  Doing a test with simpleirclient from global cache I can see the lights on the GC100 working but I cannot get similar results from LinuxMCE.

I have found pronto codes(I think) that are for the Onkyo but when sending them with simpleirclient the lights on the GC100 flash but nothing happens on the receiver. Is there any specific way to place the IR emitter. I am assuming the white sticky paper is the back of the emitter and should face away from the device.

133

Installation issues / Re: Serial IR Blaster setup

« on: March 13, 2008, 01:33:35 pm »

Well I finally have my GC100 and have had to upgrade the core to BETA4 to get it to detect as it is a v3.0 GC100 with DHCP support. I can see the GC100 in the devices and have tried to add an AV Device to it but can't seem to get it to work.
There are 3 devices under the GC100 for each of the IR ports but not the serial port.
I can't see the lights flashing on the GC100 when using the AV device but can see them when using the simpleirclient.

I am not sure what to do next.
I would like to use the GC100 ir port to control an ONKYO TX-DS787 Amp and the serial port for an Infocus IN74 projector

134

Users / Re: Beta3 to 4 upgrade

« on: March 12, 2008, 12:15:54 pm »

I attempted a beta3 to 4 upgrade using the DVD's(64 Bit) but had problems when the core was starting up. It kept cycling through the orbiter generation. System is recently installed and all data is on secondary drive so did a fresh install. Initial findings are that it is much more stable than beta3 but i am having lots of issues with orbiters on PDA devices, which were running fine on Beta3.

135

Installation issues / Re: Serial IR Blaster setup

« on: February 17, 2008, 10:35:24 am »

Thanks. I will get either that or a GC100.  Once I do is there is there an easy way for adding the Pace dc420 cable box as an AV device.