16
Users / Re: Weird dhcp/routing issue
« on: March 07, 2008, 10:39:17 pm »
just the core's external nic
News:
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
LinuxMCE sponsor
open.home.automation
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
17
Users / Weird dhcp/routing issue
« on: March 07, 2008, 08:29:49 pm »
I lost all internal communication to the outside world this morning about 3 AM. I thought this was strange because I could ping yahoo.com with no problem. I discovered that something was up with routing on the internal network card. It's been working fine for about 2 weeks and suddenly it's not working.
I'm setup as this
Cable modem
Wireless Router
External NIC
Core
Internal NIC
Switch
Computers
Internal network gets 192.168.80.1
External network get 192.168.2.205
Running tcpdump from the router I see very little traffic coming from 192.168.2.205 other than ntp traffic to canonical.com and arp requests from the router
I see tons of traffic from all of my computers with in the 192.168.80. subnet sending traffic directly to the router which it should not be doing
Nothing is coming directly from 192.168.80.1 or 192.168.2.205
Shouldn't dhcp issue the default gateway of 192.168.80.1 instead of 192.168.2.1?
Also shouldn't I be able to connect to connect via ssh from the router to the core if I have port 22 open on iptables?
I'm setup as this
Cable modem
Wireless Router
External NIC
Core
Internal NIC
Switch
Computers
Internal network gets 192.168.80.1
External network get 192.168.2.205
Running tcpdump from the router I see very little traffic coming from 192.168.2.205 other than ntp traffic to canonical.com and arp requests from the router
I see tons of traffic from all of my computers with in the 192.168.80. subnet sending traffic directly to the router which it should not be doing
Nothing is coming directly from 192.168.80.1 or 192.168.2.205
Shouldn't dhcp issue the default gateway of 192.168.80.1 instead of 192.168.2.1?
Also shouldn't I be able to connect to connect via ssh from the router to the core if I have port 22 open on iptables?
18
Users / Re: DHCP woes
« on: March 07, 2008, 08:02:34 pm »
Have you tried swapping the interfaces on the admin page?
19
Users / Re: x10 CM11A support is now fixed!
« on: March 06, 2008, 07:29:47 pm »
It looks as if the web interface is indeed broken. I was able to turn on my x10 lights via the orbiter but not my x10 controlled ceiling fans. Non of this was logged to the CM11A log though. I'll play around with the templates but it currently looks like a non-dimmable light switch in the template refuses to be controlled via the CM11A. I'm not 100% certain but I will be able to test this out more this evening.
nswint -
I didn't do the precompiled modules (I was involved in patching the source)
However, I did upgrade to beta 4 myself and the x10 support did make it in. If I were you, I'd go that route - the torrent actaully went pretty fast for me.
Also, as pointed out in this thread, there is a bug in the web admin where you can test the x10 devices. This has been filed in mantis.
20
Users / Re: Mythweb Backend Status Error with clean 710 DL DVD install
« on: March 06, 2008, 07:13:51 pm »
Getting this message means that either the mythbackend and/or mysql has crashed. I got this on 710 Beta 3 but it went away when I upgraded to Beta 4.
Also check to see if your password for the mysql.txt password is the one that is generated during your install and not mythtv:mythtv
I personally think that is what is causing the crashes.
Also check to see if your password for the mysql.txt password is the one that is generated during your install and not mythtv:mythtv
I personally think that is what is causing the crashes.
21
Users / Dealing with cdc_acm usb devices
« on: March 06, 2008, 05:41:35 am »
How do I get linuxmce to deal with usb serial devices that register as ttyACM0 and ttyACM0 instead of ttyUSBx?
[ 49.480200] usbcore: registered new interface driver libusual
[ 49.480363] usbcore: registered new interface driver usbserial
[ 49.480387] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[ 49.480446] usbcore: registered new interface driver usbserial_generic
[ 49.480448] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial Driver core
[ 49.480686] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[ 49.480700] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device
[ 49.481949] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[ 49.481962] cdc_acm 1-4.1.4:1.0: ttyACM1: USB ACM device
[ 49.482867] usbcore: registered new interface driver cdc_acm
[ 49.482870] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 49.585660] usb 1-4.4: FTDI USB Serial Device converter now attached to ttyUS
B2
[ 49.480200] usbcore: registered new interface driver libusual
[ 49.480363] usbcore: registered new interface driver usbserial
[ 49.480387] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[ 49.480446] usbcore: registered new interface driver usbserial_generic
[ 49.480448] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/serial/usb-serial.c: USB Serial Driver core
[ 49.480686] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[ 49.480700] cdc_acm 1-4.2:1.0: ttyACM0: USB ACM device
[ 49.481949] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: This device cannot do calls on its own. It is no modem.
[ 49.481962] cdc_acm 1-4.1.4:1.0: ttyACM1: USB ACM device
[ 49.482867] usbcore: registered new interface driver cdc_acm
[ 49.482870] /build/buildd/linux-source-2.6.22-2.6.22/drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 49.585660] usb 1-4.4: FTDI USB Serial Device converter now attached to ttyUS
B2
22
Users / Re: x10 CM11A support is now fixed!
« on: March 05, 2008, 01:12:57 am »
Beta3. I downloaded your precompiled files. I'm about to upgrade to Beta 4 as soon as the torrent speeds up. I downloaded the DVD+R DL and it doesn't work 
What's not working is that it's not controlling x10 modules, it is not even sending out X10.
I have an x10 controller using Xtension on my mac and it picks up other x10 commands over the powerline so I know that it's not transmitting.
What's not working is that it's not controlling x10 modules, it is not even sending out X10.
I have an x10 controller using Xtension on my mac and it picks up other x10 commands over the powerline so I know that it's not transmitting.
nswint-
Are you using 0710 beta 4?
23
Users / Re: Gigabyte GA-73PVM-S2H Looks HOT!
« on: March 05, 2008, 01:06:17 am »
I started out with no playback with 7.10 and 8.04 Beta 4. It's set to ide, I'm having problem with it set to ahci.
A couple of quick questions
Did you start out with no playback devices at all after a fresh install (thus no alsa installed as well ...)
Your aplay -l output reads ALC662, while the only time I maneged to get something recognised it was ALC885 (tough it's supposed to be ALC889A ...) so are you strugling with the exact same board ?
What mode is your sata set to in the bios ?
Thnx
Itsik
24
Users / Re: x10 CM11A support is now fixed!
« on: March 04, 2008, 03:55:45 am »
Still a no-go for me
1 03/03/08 21:54:03 42 (spawning-device) Starting... 1
1 03/03/08 21:54:03 42 (spawning-device) Found /usr/pluto/bin/CM11A
10 03/03/08 21:54:03.291 Device: 42 starting. Connecting to: localhost <0xb790b6c0>
10 03/03/08 21:54:03.293 Setting timeout for socket 4 to 20 <0xb790b6c0>
10 03/03/08 21:54:03.377 Socket::SendMessage type 5 id 37 from 42 to -1000 <0xb790b6c0>
10 03/03/08 21:54:03.377 Requesthandler 0x806d7d8 (device: 42) runThread now running <0xb7109b90>
10 03/03/08 21:54:03.419 TranslateSerialUSB /dev/ttyS0 isn't serial usb <0xb790b6c0>
10 03/03/08 21:54:03.419 Using serial port: ttyS0. <0xb790b6c0>
10 03/03/08 21:54:03.419 Connect OK <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 43 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 45 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 46 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 47 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
10 03/03/08 21:54:03.419 Device Poll thread started. <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #43(I2) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #45(I3) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #46(K2) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #47(K3) Category:73 <0xb6908b90>
10 03/03/08 21:54:05.508 Receive string: <0xb7109b90>
10 03/03/08 21:54:05.508 Received 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:06.671 Receive string: <0xb7109b90>
10 03/03/08 21:54:06.671 Received 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:28.460 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:28.460 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:28.461 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:28.461 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:34.929 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:34.929 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:34.929 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:34.929 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:37.750 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:37.750 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:37.750 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:37.751 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:39.732 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:39.732 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:39.732 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:39.732 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
1 03/03/08 21:54:03 42 (spawning-device) Starting... 1
1 03/03/08 21:54:03 42 (spawning-device) Found /usr/pluto/bin/CM11A
10 03/03/08 21:54:03.291 Device: 42 starting. Connecting to: localhost <0xb790b6c0>
10 03/03/08 21:54:03.293 Setting timeout for socket 4 to 20 <0xb790b6c0>
10 03/03/08 21:54:03.377 Socket::SendMessage type 5 id 37 from 42 to -1000 <0xb790b6c0>
10 03/03/08 21:54:03.377 Requesthandler 0x806d7d8 (device: 42) runThread now running <0xb7109b90>
10 03/03/08 21:54:03.419 TranslateSerialUSB /dev/ttyS0 isn't serial usb <0xb790b6c0>
10 03/03/08 21:54:03.419 Using serial port: ttyS0. <0xb790b6c0>
10 03/03/08 21:54:03.419 Connect OK <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 43 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 45 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 46 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 38. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
05 03/03/08 21:54:03.419 Creating child 47 <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateEvent for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom event handler for. It will not fire events. <0xb790b6c0>
10 03/03/08 21:54:03.419 Got CreateCommand for unknown type 37. <0xb790b6c0>
05 03/03/08 21:54:03.419 Note: Device manager has attached a device of type 37 that this has no custom handler for. This is normal for IR. <0xb790b6c0>
10 03/03/08 21:54:03.419 Device Poll thread started. <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #43(I2) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #45(I3) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #46(K2) Category:73 <0xb6908b90>
10 03/03/08 21:54:03.419 Child device: #47(K3) Category:73 <0xb6908b90>
10 03/03/08 21:54:05.508 Receive string: <0xb7109b90>
10 03/03/08 21:54:05.508 Received 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:06.671 Receive string: <0xb7109b90>
10 03/03/08 21:54:06.671 Received 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:28.460 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:28.460 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:28.461 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:28.461 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:34.929 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:34.929 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:34.929 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:34.929 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:37.750 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:37.750 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:37.750 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:37.751 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
10 03/03/08 21:54:39.732 Receive string: MESSAGE 82 <0xb7109b90>
10 03/03/08 21:54:39.732 Received MESSAGE 82 0x806d7d8 device: 42 <0xb7109b90>
10 03/03/08 21:54:39.732 Received Message type 1 ID 760 from 0 to 42 (device: 42) resp 0 <0xb7109b90>
10 03/03/08 21:54:39.732 Could not find a handler for message - from 0 to 42 Type: 1 ID: 760 (device: 42) Command_Impl1 Dev #42 <0xb7109b90>
25
Users / Re: Gigabyte GA-73PVM-S2H Looks HOT!
« on: March 04, 2008, 03:37:05 am »
Check out
http://ubuntuforums.org/showpost.php?p=4298894&postcount=24
I think that it's working for me but I'm having sata reset probs now
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC662 Analog [ALC662 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC662 Digital [ALC662 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
http://ubuntuforums.org/showpost.php?p=4298894&postcount=24
I think that it's working for me but I'm having sata reset probs now
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC662 Analog [ALC662 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC662 Digital [ALC662 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
A quick update (and nt a very good one unfortunately ...)
So far nothing, and I mean NOTHING has been able to convince the onboard sound to work.
I've been working on it for 3 days now, tried anything I could find on the net, Realtek Drivers, Alsa 1.0.16 and anything else I could think of.
For the system the on board sound simply does not exist.
This is getting really annoying now...
God I hope B4 has had something done to it's sound drivers other wise I'm just about ready to give up...
Itsik
26
Users / Re: Gigabyte GA-73PVM-S2H Looks HOT!
« on: March 03, 2008, 06:21:26 pm »
That rocks. I was having problems with the audio as well. I will try beta 4 to see if the drivers are included else I will try downloading the Realtek Drivers. One should note that my motherboard has a small typo it does not have an onboard Gigabit NIC. It is only 10/100. I am currently involved with Fry's Marketing and Gigabit for selling products with the wrong specs on the packaging and in-store.
Well, I finally got to tinkering with this board and here's the first part of the report as promised...
I loaded it up with 2 gigs of ram and a Pentium Core2Duo 6550, a LG SATA dvd/rw and a WD 160 gb HDD, and decided to make a core/hybrid out of it.
0710B3 dvd install went smooth with special issues untill the AVwizard froze on the DTS test. I hit Ctrl+alt+F2 to try and unmute the spdif out, enter "alsamixer" and it's not there. I try to see what sound card I have just to discover the NO sound card was detected at all.
A quick google search tells me 2 things. What I have is a Realtek ALC889A HD Audio chipset and this thing has problems under windows as well.
A little more digging and I find that Realtek have released a set of linux drivers for this chipset. So I downloaded the driver and installed it, and now everything's working fine, including the AVwizard which does not freeze altough there's still no sound. I unmuted the spdif in alsamixer but still no sound. I might have a defected cable so I'm gonna buy one tomorow just to be on the safe side and continue from there.
More to come ...
Itsik
27
Users / Re: Gigabyte GA-73PVM-S2H Looks HOT!
« on: February 27, 2008, 03:53:14 am »
I have the GA-73VM-S2. Almost the same. It works with the Ubuntu 7.10 and 8.04 Beta 4 Live CD. I'm still running Fedora 8 until Linux MCE 7.10 is released and I'll reformat with it.
Looks promising as a core. I haven't connected it up to my tv. I could test and let you know how it goes.
Looks promising as a core. I haven't connected it up to my tv. I could test and let you know how it goes.
28
Users / Re: USBUIRT now what?
« on: February 06, 2008, 04:01:29 pm »
Are you using an ir emitter or serial cable to control your tv?
29
Developers / Re: Thinking about whole house multichannel audio solution in SW for LMCE ...
« on: January 28, 2008, 07:54:46 pm »
Off-hand I would say pulse audio is probably the easiest to incorporate without an entire schema change. It works with alsa, arts, and xine, and bluez. You can combine multiple soundcards into one. I would suspect low cost usb sound cards as the easiest way to add expansion and multiple sources. Then pipe that either over the tcp stack or back to the sound devices. I was really excited that Fedora implemented this. I've been playing around with this on Ubuntu 7.10 but I haven't been able to send audio to remote sources like a Squeezbox or another machine, but it does work with bluetooth. When Linuxmce 7.10 is released I will get to test it out further with multiroom audio.
http://www.pulseaudio.org/wiki/PerfectSetup#ThirdPartyApplications
Mythtv is on the list of patched applications that can work with Pulseaudio
Check out the diagram
http://upload.wikimedia.org/wikipedia/commons/1/14/Pulseaudio-diagram.png
http://www.pulseaudio.org/wiki/PerfectSetup#ThirdPartyApplications
Mythtv is on the list of patched applications that can work with Pulseaudio
Check out the diagram
http://upload.wikimedia.org/wikipedia/commons/1/14/Pulseaudio-diagram.png
30
Feature requests & roadmap / Re: W800RF/RFXCOMM Integration
« on: January 12, 2008, 05:09:24 pm »
Cool,
I'm thinking about it. I will keep Misterhouse around until there is native support for the W800RF. If I can find a Homepro Z-Wave Thermostat I won't need it, once the Insteon Thermostat Module over at Smarthome.com becomes available I'll make a determination.
I'm thinking about it. I will keep Misterhouse around until there is native support for the W800RF. If I can find a Homepro Z-Wave Thermostat I won't need it, once the Insteon Thermostat Module over at Smarthome.com becomes available I'll make a determination.