Messages

I'm sorry I can't be of assistance right now, I don't have LMCE installed, just regular ubuntu with a heavily modified VDR for my DVB-S card

No, it will not work "out of the box" with MythTV or VDR.

To get them to work, you need the latest multiproto drivers, which I have not been able to get to work in LMCE, because lots of API changes happened in the new drivers, so they have no clue what VDR or mythtv is telling them. There are patches, though, but you'd have to recompile VDR or mythtv anyway. Should the new drivers work, I still don't know how you can do this AND keep linuxmce working as it should.

I added a VDR tutorial on my blog too, but it's not as polished as my others, unfortunately

I actually bought an LG especially because of it's RS-232 support

But, once you have a serial port, you're not out of the woods yet!
I just bought a serial to usb converter, only to find out it's a male USB out and a male serial-out! But these televisions also only have a male out. Joy!

Even finding a male-to-male usb cable (for the TV's service port) is impossible in Belgium, I've only found usb extension cables or, when both ends are male, they're never the same type (those mini usb connectors for camera, those square connectors for devices) As long as they can squeeze money out of us for every product we buy..

Excellent! I just wanted to say; thank you for the language file

I searched for totallymaxed's posts and I saw someone was also pointing to the UI-Alpha mode, but I don't completely get what's so special about this mode...

(I have all the vsyncing options turned on) I run compiz on another computer, with a newer card, but I don't have any tearing there. I also tried mythbuntu for a few days (for my DVB-S card) on the HTPC and I didn't have any tearing there, either! I even copied the monitor & screen related sections from the mythbuntu xorg.conf but still nothing.

Are the drivers in 0710 older then in Ubuntu 8.04?

I believe the problem to  be some kind of incompatibility between the latest drivers and LinuxMCE's kernel version.
I created my own tutorial to get around this (by compiling from a specific, older, revision)

http://skerit.kipdola.com/?p=5&language=en

Please note, LinuxMCE tries to load its own modules for this card, if you want to get it to work without a reboot you need to unload every DVB module! (including tt_pci and such)

Choppy? Do you mean the tearing-problem?

Probably if you have an nvidia card - I'm still baffled about this one.

My only complaint is the unsynchronized releases, because it makes a lot of stuff harder to fix.

Other then that, I agree LinuxMCE is much more then a regular media center like Mythbuntu. It has a much more massive code base with a lot more features, so it'll take a while, but we'll get there.

I had to remove LinuxMCE 0710 from my HTPC a few days ago because I needed to test my Technotrend DVB-s2 S2-3200 card, using Mythbuntu, and I do miss LinuxMCE!

To be honest, I don't have a single clue.

The multiproto drivers are very unstable, I followed the same tutorial (http://wilco.bercot.org/debian/s2-3200.html) on LinuxMCE and on Mythbuntu, and all I know is it worked on Mythbuntu.

Don't get me wrong though, the modules loaded without a problem! I compiled them without a single hitch, I just would not be able to get a /dev/dvb folder, nor would anything show up in my dmesg. For some reason the modules wouldn't "attach" to my device.

I've found out it's probably because of the older Linux kernel that the drivers don't work. On Mythbuntu 8.04 everything loads smoothly - but I don't want Mythbuntu, I want LinuxMCE

I have the same problem.

I tried the "vsync" option (which was already on, actually) but it didn't help at all..

Hey all,

I've finally installed my Technotrend S2-3200 DVB-S2 card (My satellite dish is getting installed tomorrow)
I followed these instructions to install the driver to the letter: http://wilco.bercot.org/debian/s2-3200.html

But for some completely unknown reason the modules do nothing when I load them. I get no /dev/dvb
There are *no* compilation errors! So I don't know what could be the problem

Some console output:

lspci
04:01.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)

dmesg | grep saa
[   37.931073] Audiowerk 2 sound card (saa7146 chipset) detected and managed
[   38.332543] saa7146: register extension 'budget_ci dvb'.

I should be getting a lot more from that dmesg message!

Did anything change between the RC1 and the final release? Because I never upgraded my core, and when I try to do it now it says nothing needs updating ...

As the patch wasn't in the RC, I just couldn't wait anymore - but my compile is failing at one point:

Code Select Expand

linuxmce@dcerouter:/mnt/device/29/Orbiter Test/lmce-source/lmce/src/BD$ sudo make libBDCommon.so
g++ -c -I./ -I../../ -I../ -I/usr/include/mysql -I.. -I../DCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DMULTI_THREADED -DUSE_MYSQL -DVIPSERVER -DXBTSOCKET -DBLUETOOTH_DONGLE -DMULTI_THREADED -fPIC -Wall -g -D_GNU_SOURCE BDCommandProcessor_Linux_Bluetooth.cpp -o BDCommandProcessor_Linux_Bluetooth.o
[b]sdpbrowse.h: In function 'int sdp_lookup_pluto_rfcomm_channel(bdaddr_t)':
sdpbrowse.h:122: error: redefinition of 'int sdp_lookup_pluto_rfcomm_channel(bdaddr_t)'
sdpbrowse.h:18: error: 'int sdp_lookup_pluto_rfcomm_channel(bdaddr_t)' previously defined here
BDCommandProcessor_Linux_Bluetooth.cpp: In constructor 'BDCommandProcessor_Linux_Bluetooth::BDCommandProcessor_Linux_Bluetooth(std::string, std::string, PhoneDevice*)':
BDCommandProcessor_Linux_Bluetooth.cpp:64: warning: unused variable 'req'
make: *** [BDCommandProcessor_Linux_Bluetooth.o] Error 1[/b]


I followed rafik24's instructions (Well, after realizing I had to install the bluetooth-sources, but anyway) Now I can't find my mistake.

I'm using a Samsung SGH-U600 to get JavaMO working on the new RC but I'm running in to these problems:

* Getting the hybridcore & the U600 paired up is quite difficult. My hybridcore recognized the bluetooth phone immediately but, when it was trying to connect, my phone asked for a pin code. I tried all the default ones (1111, 1234, 0000, 9999, ...) but they didn't work. I also was not able to define a pin code in the hybridcore.
I did manage to pair them by going into KDE and messing about with the Kbluetooth-tools.

* Unfortunately, even though I finally did get them to "pair", it didn't do much, the JavaMO program still shows the message "Waiting for connection" constantly. Is it possible hari's bluetooth-dongle patch still isn't incorporated in the RC? (Or do I need to change something extra in the "LinuxMCE Admin"? By the way, what does "VMC" stand for in "Resend VMC to phone")
Eventually, when bluetooth is enabled on my phone, the hybridcore will keep on displaying this message "Done with new device bluetooth_hci Added: Bluetooth Dongle" - over and over again.

* Reconnecting a device is quite hard. First up the hybridcore asked what type of phone I had, but this screen popped up while I was in another screen (setting up my samba shares) so I accidentally added it as a windows-mobile phone. I then had to go to the "LinuxMCE Admin" to delete it, but after that it didn't care about the phone anymore. Even though he was seeing it, he didn't ask what type it was or so.

Thank you for your time!