[mythtv-users] Re:nForce2 motherboards

[Sean]

With the exception of LIRC, I have everything working now.

First, the audio wasn't not working because of Linux. Yesterday, I installed
WinXP to see if it was possible that I had hardware problems. I did - total
OE. Since my system had front panel audio, I hooked it up on first system
build. Either I did something wrong (likely) or the Shuttle wasn't liking my
Enermax case. (To those with the MN31/N, make SURE the front panel jumpers
are covered like they are in the manual). Upon Redhat reload, OSS did indeed
sense the audio card properly and I heard my first audio from the box.

All the apt-get stuff went as expected though I have found that it is wise
to apt-get update several times throughout install. Thanks for the explict
naming of the kernel tip when loading the KMDL modules from apt...I had just
stumbled onto that myself.

I did have an issue with MySQL that was different to the prior install, but
I am not sure if it made any difference to Myth. I also noticed that Myth
0.12 is out, any word on when it will be available via apt? How difficult is
it to upgrade?

So... Thank you all for the advice you have given me specifically and for
the extremely  helpful guides (Jarod, you rock) you have made available.
This past week has been a huge learning experience for me and I am sure that
I have a lot of tweaking to do before I am happy...but such is the path of a
noob :)

Have a great day everyone!

-Sean



> On Saturday, Oct 18, 2003, at 20:16 US/Pacific, Ian Forde wrote:
> 
>> On Sat, 2003-10-18 at 19:45, Sean wrote:
>>> There is NO sound. Not from the system. Not from mplayer. Not from the
>>> notifications panel. Nowhere. Technically this should all be Kool &
>>> the
>>> Gang, but it isn't. That is why I was asking about the 2.4.22 kernel.
>> 
>> Okay - so the question is, which kernel are you currently using?  A
>> kernel upgrade won't really do much of anything if sound wasn't working
>> before...
> 
> Agreed.
> 
>>> The first 4 times I installed Redhat (noobish, I know installing from
>>> the ground up) I went for the ALSA drivers through apt-get. The
>>> trouble
>>> is that apt-get seems to call for an older kernel version for one of
>>> the
>>> ALSA pieces and the install does not conclude, nor can apt-get install
>>> anything else after the case (how do you "reset" apt-get? ).
> 
> You must explicitly tell apt what kernel module you want, and it should
> be the one for the kernel you are running, otherwise, potential chaos
> ensues...
> 
>>> I have
>>> seen several mentions of this around the internet leading me away from
>>> using apt-get for this install (boy does it rock for everything else
>>> though...).
>> 
>> Here's how I usually install RH9 boxes.  It may not be the most
>> optimal,
>> but I can tell you it's relatively safe...
>> 
>> 1. Install RH9 from CD (or Network install or whatever...).  Let the
>> box
>> reboot when finished.
>> 2. download rcd and rug from ftp.ximian.com and install them
>> 3. Using rug/rcd, subscribe to the redhat-9-i386 and redcarpet channels
>> 4. Do a "rug up" to install updates.
>> 5. Download the latest RH kernel update (along with kernel-source,
>> since
>> it is usually part of the default install) and install them manually
>> using rpm or rug.  (rug/rcd doesn't do kernel updates automatically.)
>> Reboot the box when finished.
>> 
>> Now you've got an updated RH9 box.  At this point you're probably
>> asking, "why use red carpet when I'm going to install apt-get anyway?"
>> Because I like to keep the redhat parts of the box as stock as possible
>> (and using rcd to do it because, IMHO, up2date... well... sucks.)
> 
> But remember, you can do that part w/apt also. Oh, and I'm a convert
> also. up2date sucks.
> 
>> So now we continue...
>> 6. Follow Jarod's and Axel's directions by installing the apt tools.
>> 7. Installing Axel's kernel via apt.  Current version is 2.4.20-20_9, I
>> believe.
> 
> Almost. 2.4.20-20_29.rh9.at is the current one. (There are also
> Rawhide/2.4.22-based kernels available from ATrpms, one of which I'm
> about to install myself).
> 
>> 8. Install the atrpms alsa rpms.  The ones I have installed are
>> alsa-kmdl, alsa-driver, alsa-lib, alsa-lib-devel, alsa-utils.
> 
> Some actually pull from FreshRPMs, but same difference.
> 
>> Note that by using Jarod's HOWTO, you'll be installing the entire
>> mythtv
>> suite.  I haven't tried it so I don't know if it includes alsa.
> 
> I presume you mean mythtv with native alsa support? No, to date, native
> alsa support isn't enabled in the rpms. It *might* be in the 0.12
> release...
> 
>> But I
>> can tell you that by going through steps 6-9 above, you *should* have
>> sound, assuming that your cabling is correct...
> 
> Agreed.
> 
>>> I am not married to Redhat in the least. I would gladly use another
>>> distro, but the easier to setup the better. Is there an updated
>>> release
>>> of Redhat that includes the 2.4.22 kernel? If I update to 2.4.22
>>> successfully, can I merely load the config file from the Axel's kernel
>>> to the new one?
>> 
>> Stick with RedHat if you're new to Linux.  You'll find more people
>> willing to help with RH problems of most types...
> 
> And once you have things going, if you still really want to go to a
> 2.4.22 kernel:
> 
> http://atrpms.physik.fu-berlin.de/dist/rawhide/kernel-bleeding/
> 
> As I said, I'm installing one myself right now...
> 
> --Jarod