1004: The time has come.

[ladekribs]

Hi,

Question, I get "hum" over HDMI sometimes after stopping music or video, feels like a software problem.

anyone else have the same experience?



BR Stefan

[JaseP]

Hum's not software (almost never is),... what you are likely getting is the kind of ground loop effect that they were describing, but perhaps due to the way the manufacturer of your PC configured the sound system,... So very possibly, it's internal to your PC,... But process of elimination, try changing what power source (what outlet/breaker the machine is on versus to speakers/AMP/TV) the things are pulling from,... ya know,... moving them all to the same, or making them all different, etc.

[l3mce]

Off topic, and you will probably get MORE attention in its own thread anyway.



But JaseP is right.

[Sigg3.net]

If anyone has a capture card in their core, which is headless, I would be very curious if you were able to setup mythtv. I would expect that to be a problem

I have a TechniSat CableStar HD2 (DVB-C) so I'm not sure whether I would want to use VDR or MythTV, but I will be running the latest snapshot soon. Headlessly, as KVM on an openSUSE system. I wouldn't mind running any tests.

[jamo]

I also just had a problem with the USB-gamepad install. I recently updated my system and reran DisklessCreate_TBZ.sh and then re-installed all my media directors. My Compaq HP6710b notebook got into a USB-gamepad device install loop where it just kept adding the device and incremmenting the device number. Sarah in the background asking if I can see and hear her while in the top-left I keep getting "detected gamepad device number 3283", "downloading software...", "detected gamepad device number 3284", "downloading software...", etc etc until I manually powered off the MD. I had to then go into web admin, delete gamepad device (there was only one) in device tree and then remove the reference on the media director wizard to the gamepad as remote. Then, before booting the MD again, I did the fix mentioned below in the detect gamepad script on the /usr/pluto/diskless/xxx/usr/pluto/bin script.

Then booted up the media director again and all worked swimmingly.

As mentioned by Karel, the gamepad detect script is clearly returning false positives in some instances. Should I open a trac ticket for this?

Incidentally, if it is installed, it also plays havoc with trying to use a wiimote.

Something is triggering the gamepad install script.
In my case it was my logitech universal receiver.

Got this from another thread...
http://forum.linuxmce.org/index.php/topic,12297.0.html

Karel

[tschak909]

The USB Game Pad driver needs work for certain cases. I would love for somebody to take a look at the code, to see what they can fix, given their unique installs.

-Thom

[jamo]

The USB Game Pad driver needs work for certain cases. I would love for somebody to take a look at the code, to see what they can fix, given their unique installs.

-Thom

I'll try and have a look at the detection side.... since DragonK and I have both had issues and we both use wiimotes I think it's likely that is where the confusion is being introduced. I'll open a trac ticket for it.

Edit: Oh, I see you have a trac ticket already for the gamepade device http://svn.linuxmce.org/trac.cgi/ticket/1228
I'm thinking the issues are in the AVWizard_Gamepad_Detect.sh and AVWizard_Remote_Detect.sh that are picking up stuff from the wiimote install. If I find anything I'll chat directly to you and/or put a comment on the ticket.

[tschak909]

You should also look at the source code for the gamepad device, as well:

http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-1004/src/USB_Game_Pad/USB_Game_Pad.cpp

-Thom

[jamo]

Carrying on the gamepad discussion in the following thread.

http://forum.linuxmce.org/index.php/topic,12645.0.html

Have gone around in circles a few times but I think I'm getting there.... at least detecting the problem. Fixing is another issue ;-)

[Dap-P]

I tried snap LMCE-1004-20120623013626110.iso
But it didn't boot, not from USB and not from DVD

It could not find the boot image

Now i am installing 1 snap earlier, and this one does boot.
LMCE-1004-20120621232326106.iso

[l3mce]

Did you check the md5sum of the image?

There are some good changes on the newer snaps, that handle directory ownership correctly, fixing things like floorplans.

[Viking]

Hi,

tried the LMCE-1004-20120623013626110 - here it booted.

It is probably a bad idea to change the names of the rooms while in the setup wizard , at least it crashed here and started over. That means that MythTV was not installed and maybe other things are not OK.

What I did. Keyboard language danish, selected two rooms "linving room" and "garage". Tried to rename garage to "Work room", pressed shift W on the screen keyboard and the "ork" fast on the keyboard. Then I only had a small video on the screen and after some time the wizard started all over, but remembering my choises.
Another thing, while entering the letters with the on-screen keyboard offen i did get letters from another row on the keyboard. Meaning instaed of "k" i woul get an "i" and so on.

Later I discovered that MythTV was not installed.


Regards
Viking

[l3mce]

That is not at all normal. Changing names should not do any of this, and has not when I rename. The only thing that has ever crashed the wizard for me was zwave a while back, but that was resolved a long time ago.

The Danish keyboard is the only thing that seems different. I will see if someone can try and reproduce this error... otherwise it was a fluke/related to some other hardware being discovered and locking once a room was created.

This is why Sarah says "Don't start plugging in your devices just yet" for the record. Can you tell me what else was attached once you created rooms? I lean towards that as an answer.

[jamo]

This is not going to be particularly helpful because I can't remember the exact circumstances (can't even remember if it was 8.10 or 10.04 although it was certainly this year, probably a few months ago) but I have had the same experience once- the room naming restarting in the middle exactly as described. The only thing that might be helpful is to say that I definitely didn't have a Danish keyboard. As suggested by l3... quite possibly some hardware quirk triggering something else.

Sorry I can't remember more details but I just wanted to mention that it has happened before to me. Again, it didn't seem to cause any trouble apart from the inconvenience.

[Viking]

That is not at all normal. Changing names should not do any of this, and has not when I rename. The only thing that has ever crashed the wizard for me was zwave a while back, but that was resolved a long time ago.

The Danish keyboard is the only thing that seems different. I will see if someone can try and reproduce this error... otherwise it was a fluke/related to some other hardware being discovered and locking once a room was created.

This is why Sarah says "Don't start plugging in your devices just yet" for the record. Can you tell me what else was attached once you created rooms? I lean towards that as an answer.

Hi,

this is on my test system, where there is only an DVB-s av7110 card in it besides the normal Nvidia card and two gigabit network cards.

No remote control or anything else.

Regards Viking