Ha Ha - good one.

I'd have to say I believe that 40Gb should suffice, granted you can live with purging caches and running out of space frequently...

-Tony

Your reply was useless, too.  Mocking inexperienced users has got to be the single best way to destroy the LinuxMCE community.  Keep it up and watch the damned project crash and burn because its users are all going to flock to XBMC, if they haven't already started to, if this type of shit keeps up.

A question gets asked. A detailed answer provided. Answer doesn't fit. Ask again. Interesting.

Look, dude, I got one reply from a very helpful user for which I'm thankful.  But, it's just one reply.  Don't you think it's fucking reasonable for me to ask for more people's thoughts on this?  How the FUCK am I supposed to know if what joakimL said is actually fact?  Oh, I know!  Ask more people if they experienced the SAME FUCKING THING!  And, did I say the answer didn't fit? NO!  You did because you fucking ASSUMED that's what I was thinking.  THANKS!!!

I'm not a LinuxMCE expert.  I don't use Ubuntu - I'm a RHEL / CentOS / Fedora guy.  LinuxMCE is is all new to me.  Frankly, getting my damned hardware working (i.e. HDMI audio) has been THE SINGLE FUCKING BIGGEST WASTE OF MY TIME ever.  FUCK!

LinuxMCE is plug and play?  My ass it is!!  I finally pieced together information from all over the Internet, including the uber helpful XBMC forums and wiki, and got my Jetway minitop working with HDMI sound.  I was happy.  I was elated.  I managed to watch a couple of movies, and ignoring the fact LinxMCE's media interface is BUTT FUCKING UGLY, it worked.  I was looking forward to submitting a wiki article explained exactly how to get a Jetway minitop with an ION chipset working under LinuxMCE 10.04.   I was looking forward to making my LinuxMCE install permanent and finally moving on to the ZWave integration. That is, until you posted your bullshit here.  Your single post is the reason why LMCE is floundering while XBMC is jumping by leaps and bounds every day.  Yes, they serve different purposes, but man, talk about handling community relationships completely differently.

Your reply was completely useless and offensive.  Why did you even bother posting in here?  If you didn't like me asking for more people's input, you should have stayed out of the thread.

You've helped me the best that you could in the past, and for that I'm grateful.  But, your stupid, useless reply in this thread was not appreciated.  Keep that crap to yourself, and don't fucking piss off other users of this software.  LinuxMCE needs more users, not less.

Yes, I'm pissed.

BTW, clearing your apt cache will help get back some space.

So, does anyone else have any thoughts on this?  Is the 40GB drive too small for what I'm planning?

A clean Core install allocate 5-7 GB, but grows over time.
My Core + 1 MD takes 20 GB after running 6 months (no media files), so your 40 GBs is OK for you short term plans, but too small for the long term goals.

Thanks for your experience.

I have to say 20GB for the CORE and 1 MD is pretty extreme.  You sure you haven't included some extraneous files in that total?

I picked up an Intel 40GB SSD to use as the boot drive for my 10.04 Core.  At the moment I'm using an old 80GB IDE drive.  I want to make the drive swap because my testing of the Core is complete and since I'm mostly pleased with the results, I think it's time to move the OS bits to a better HD.

Before I rip open the box and install the SSD, I want to be sure the 40GB SSD is big enough.  My plans:

1. I'm going to have a separate md RAID 5 set (going to use an existing one from a Fedora 15 box) for media storage
2. Core + 2 MDs to start
3. Will add five more MDs down the road, maybe more

Can 40 GB accommodate that or should I get a bigger SSD?

What I had to do was connect my video card to my SPDIF sound connector on my Mother board. set the mother board up for spdif pass-through or something like that(i'm not in front of my system.) then during the setup wizard I had to full the system to think it was passing video through DVI, after I could see what I was doing I changed it to HDMI. Then during the sound setup I changed the sound settings to SPDIF optical or SPDIF Coaxial (not in front of system). Sound and Video over HDMI worked after that.
I hope this helps you.

That's utterly insane.  Why do you have to jump through so many hoops just to get HDMI audio to work? I can't believe I'm having so many problems: it has to be because of the old version of Ubuntu being used as a base for the current LinuxMCE release.

I haven't tested my changes yet.  As soon as I do, I will report back here.

Note: I'm really starting to dislike this project.  I may just abandon it and my home automation goals and revist when the next LinuxMCE version is released (the one based on 1010).

LMCE attempts to "self-repair" as much as possible, and as such most config files are regenerated at boot. usually all you need to do is make sure settings are correct on the various devices in the web admin, but for more customizing you may need to modify the scripts that write the config files. these are generally in various .sh files in /usr/pluto/bin.

Last time I asked this (which was recently), I was told to edit files in the MD's template dir.  So, I did.  It didn't help. I cried...lots.

Now I'm supposed to edit the scripts that generate the config files.  This sounds to me like a non-permanent solution, too.  What will happen if there's an upgrade that includes the very file I changed?  Won't it be over written?

This is the file I'm looking to change now: /usr/pluto/bin/SetupAudioVideo.sh.  This is the section I believe I should change:

Code:

Setup_AsoundConf()
{
        local AudioSetting="$1"
        local SoundCard

        SoundCard=$(GetDeviceData "$PK_Device" "$DEVICEDATA_Sound_Card"|cut -f2 -d";")
        SoundCard=$(TranslateSoundCard "$SoundCard")
        if [[ -z "$SoundCard" ]]; then
                SoundCard=0
        fi
        sed -r "s,%MAIN_CARD%,$SoundCard,g" /usr/pluto/templates/asound.conf >/etc/asound.conf

        case "$AudioSetting" in
                *[CO]*)
                        # audio setting is Coaxial or Optical, i.e. S/PDIF
                        echo 'pcm.!default asym_spdif' >>/etc/asound.conf
                        EnableDigitalOutputs
                ;;
                *H*)
                        # audio setting is HDMI
                        echo 'pcm.!default asym_hdmi' >>/etc/asound.conf
                        EnableDigitalOutputs
                ;;
                *)
                        # audio setting is Stereo or something unknown
                        echo 'pcm.!default asym_analog' >>/etc/asound.conf
                ;;
        esac
}

I think if I change the "*H*)" case to the following, audio over HDMI will start working on every boot.:

Code:

*H*)
                        # audio setting is HDMI
                        echo -e 'pcm.!default {\n\ttype hw\n\tcard 0\n\tdevice 7\n}' >> /etc/asound.conf
                        EnableDigitalOutputs

Will that work? Should I do something else?  Maybe I should try updating the nvidia drivers before messing with the setup scripts.

there is often a better way of doing whatever it is that you are trying to accomplish though, and in particular if its a bug in something, others might appreciate the contribution of proper patch.

I have a Jetway Ecomini. It has a nvidia chipset, which appears to be detected correctly.  But, the asound.conf that gets created doesn't give me ANY sound over HDMI.  In the other thread I started, I explain what I've tried (http://forum.linuxmce.org/index.php/topic,12082.0.html).

I edited asound.conf in /usr/pluto/diskless/29/usr/pluto/templates, rebooted my MD, and still don't get any sound via the HDMI connection.  This is what the MD's asound.conf looks like now:

Code:

pcm_slave.spdif_convert48k {
pcm "spdif:%MAIN_CARD%"
rate 48000
}

pcm.spdif_playback {
type plug
slave spdif_convert48k
}

pcm_slave.hdmi_convert48k {
pcm "hdmi:%MAIN_CARD%"
rate 48000
}

pcm.hdmi_playback {
type plug
slave hdmi_convert48k
}

pcm.asym_spdif {
type asym
playback.pcm "spdif_playback"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.asym_hdmi {
type asym
playback.pcm "hdmi_playback"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.asym_analog {
type asym
playback.pcm "plug:dmix:%MAIN_CARD%"
capture.pcm "plughw:%MAIN_CARD%"
}

pcm.hdmi {
type hw
card 0
device 7
}

Can someone PLEASE tell what the hell to do?  Which file am I supposed to edit?  WTH am I supposed to put in it?  I can't find shit on the wiki, and nothing in the forums gives me a fix that survives reboot.

I admin massive Linux systems running a huge variety of applications and services, and yet LinuxMCE has completely stumped me.  WTF. 

There is a template file that is used to generate it. If you change the template (it is only for that MD) then it will generate the working one each time.

Can't remember filenames and locations and I am at work at the moment so I can't check. But if you have trouble finding it let me know and I will look up on the MD that I changed at home.

Looks like a similar change to what I had to do. What sort of machine?

I changed the template file for the MD in question, but the generated config file didn't change.  I'm not sure what to do next.   Could you tell me which file you edited for your MD and what you did?

Any tips for my newest dilemma?

I have no idea what I'm doing.  I know next to nothing about LinuxMCE and making any custom changes is extremely confusing.  I wish I could spend more time learning, but these days I don't have a lot of free time.

So, with that said, I guess editing /usr/pluto/templates/asound.conf was a mistake because after the MD booted up, /etc/asound.conf on the MD hadn't changed at all. Just great.

I then looked on the core in /usr/pluto/diskless/29/usr/pluto/templates, and found the MD's asound.conf.  It has some macros in it for automagically finding the card number.  Can I put the lines I mentioned before straight into this file?  Also, I don't see the "default" line.  Can I manually put that in here too, or will something else come along and add another default line?

There is a template file that is used to generate it. If you change the template (it is only for that MD) then it will generate the working one each time.

Can't remember filenames and locations and I am at work at the moment so I can't check. But if you have trouble finding it let me know and I will look up on the MD that I changed at home.

Found it in /usr/pluto - thanks posde!

I added the following to it:

Code:

pcm.nvidia_hdmi {
type hw
card 0
device 7
}

pcm.!default pcm.nvidia_hdmi

Funny thing is, I don't see the line, "pcm.!default asym_hdmi", like I did when the MD was up and running.  I'm going to guess something else sets the default, so I'm not sure if I should put the default in manually.  I will be testing this out tonight.

Looks like a similar change to what I had to do. What sort of machine?

This, though I'm not 100% sure my version has the exact same specs:

http://www.jetway.com.tw/jw/Barebone_view.asp?productid=760&proname=JBC600C99352W-BW%20%28Mini-top%29

After sound over HDMI is working 100%, my next task is going to be getting the remote working.  Right now, only a few of the buttons work.  The MD doesn't see the remote as a remote.  I think right now it's just being recognized as a mouse (based on its current behaviour).  Anyway, I'll leave this remote stuff to a new thread.

Gah!  I'd really like some help on this.  Does anyone know how I could make my changes stick?

How do I customize /etc/asound.conf on my MDs so that the changes survive reboots?

The auto generated asound.conf doesn't give my any sound over HDMI.  This is what it looks like:

Code:

pcm_slave.spdif_convert48k {
pcm "spdif:0"
rate 48000
}

pcm.spdif_playback {
type plug
slave spdif_convert48k
}

pcm_slave.hdmi_convert48k {
pcm "hdmi:0"
rate 48000
}

pcm.hdmi_playback {
type plug
slave hdmi_convert48k
}

pcm.asym_spdif {
type asym
playback.pcm "spdif_playback"
capture.pcm "plughw:0"
}

pcm.asym_hdmi {
type asym
playback.pcm "hdmi_playback"
capture.pcm "plughw:0"
}

pcm.asym_analog {
type asym
playback.pcm "plug:dmix:0"
capture.pcm "plughw:0"
}
pcm.!default asym_hdmi

If I comment the "pcm.!default asym_hdmi" and put the following default lines in, sound over HDMI works:

Code:

pcm.!default {
type hw
card 0
device 7
}

So, how do I make that change stick?

FYI: Got hdmi working by doing this (after trying everything else in the wiki/forums):

First I updated alsa using this method: http://forum.linuxmce.org/index.php/topic,11932.0.html
and installed nvidia update

Then I followed the HDMI Output Does Not Work instructions on: https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#HDMI_Output_Does_Not_Work to find my card number and device number

Then i wrote those numbers down and created the ~/.asoundrc file in /root and /home/<kubuntu user directory>

Then I edited /etc/pluto/xine.conf and set:

audio.driver:alsa
audio.alsa_front_device:plughw:1,9 (1 being your card number and 9 being the device number you found with aplay)

Hope this helps someone.

Creating the ~/.asoundrc files didn't help me.  I had to put the following into /etc/asound.conf:

plug pcm.!default {
   type hw
   card 0
   device 7
}

After rebooting the MD (reloading the alsa modules didn't work and I didn't want to waste time figuring out why), HDMI sound finally works!

I know /etc/asound.conf can be overwritten, so I would lose my custom config in that event.  But, I my changes will survive MD reboots.  So, if I rebuild the MD image, I'll likely lose the customization.  Am i right?