Mailing List Archive

On Mon, Nov 11, 2002 at 12:24:12PM -0800, Jeremy Oddo wrote:

> Grand Newbie back again with a couple simple [multi-part] questions :)
>
> 1. Under mythfrontend, I don't have anything under the Setup option.
> Perhaps I missed something in the docs explaining this, or perhaps I
> goofed the install. What, if anything, is under "setup" from the
> mythfrontend?

This is not yet implemented.

> 2. I've been having no luck with getting 'mythtv' working. Many people
> believe it to be an audio problem. So, I need to get alsa. Does anyone
> have any points, suggestions, etc. for getting alsa up and running? Also,
> how can I tell if it _or_any_other_audio_app_ has taken control of my
> /dev/dsp? I've been told I need to kill anything that has control over
> /dev/dsp, but I don't know where to look!

Does audio work in other programs? If so, then the problem is likely not
with your sound driver, and you should not set about trying to use ALSA.

At least one other person on the list has already explained how to find out
if anything else is using the sound device. That is most likely the
problem.

--
- mdz

>
>> 2. I've been having no luck with getting 'mythtv' working. Many
>> people believe it to be an audio problem. So, I need to get alsa.
>> Does anyone have any points, suggestions, etc. for getting alsa up and
>> running? Also, how can I tell if it _or_any_other_audio_app_ has
>> taken control of my /dev/dsp? I've been told I need to kill anything
>> that has control over /dev/dsp, but I don't know where to look!
>
> Does audio work in other programs? If so, then the problem is likely
> not with your sound driver, and you should not set about trying to use
> ALSA.
>
Yeah, audio DOES work in other apps. I'm not too sure what could be
grabbing the audio. I even tried booting without running KDE or gnome for
the windows manager. I tried twm as it's way stripped down, but I got the
same problem (video no coming up).

One think that I really wish myth had was some verbose debugging info that
you could set via the command line. Yeah, I know, it's a lot of coding
overhead (just like commenting the code) but it would be really helpful to
have some verbose debugging info!

> At least one other person on the list has already explained how to find
> out if anything else is using the sound device.
>
Will that person(s) step forward and offer a few suggestions? ;)


Jer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 2. I've been having no luck with getting 'mythtv' working.

What distribution are you using, and what makes you think that mythtv
can't get to the audio device?

I've got mythtv running on Mandrake 9.0, and I don't need to kill
alsa. All I needed to do was to adjust the mixer and set the line-in
as my recording source.

Can you break it down step-by-step what works and what doesn't?

When you run mythfrontend, what happens?

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPdAhRPc1NpCTlP0JEQJkvwCfR6PoS7y5wWOeMb9oMebVsVN/3NMAn2nw
9ua08hxQfWlErKiZeT/3wxhr
=tX8i
-----END PGP SIGNATURE-----

On Monday, November 11, 2002, at 01:29 PM, Robert Kulagowski wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> 2. I've been having no luck with getting 'mythtv' working.
>>

on my redhat 8 system it turned out that plugging in to the "microphone
in" jack rather than the line in (as I would have thought) solved my
sound problems. In summary:

Plug into mic in rather than line in. turn up global volume and mic in
gain. Click mute on microphone. Click record on microphone. worked for
me.

>> 2. I've been having no luck with getting 'mythtv' working.
>
> What distribution are you using, and what makes you think that mythtv
> can't get to the audio device?
>
I donno...Isaac and a few others said that's where I should look. There's
not much info to go on, so I was taking some pointers from the pros! As
far as the distro, I'm using RedHat 8.0 (for better or worse).

>
> Can you break it down step-by-step what works and what doesn't?
>
Sure, see below....

> When you run mythfrontend, what happens?
>
mythfrontend works without a hitch. I can view the guide, schedule
recordings, etc. All the menu options work minus 'setup' (which isn't
implemented yet), and 'mythtv'. Here's what I get what I run 'mythtv'
(I'm running it from a different path, but it does the same under the
correct install path):

# gdb /var/src/try2/mythtv-0.7/programs/mythtv/mythtv
GNU gdb Red Hat Linux (5.2.1-4)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) run
Starting program: /var/src/try2/mythtv-0.7/programs/mythtv/mythtv
[New Thread 8192 (LWP 1300)]
Probed: /dev/video0 - Television
Probed: /dev/video0 - Composite1
Probed: /dev/video0 - S-Video
Probed: /dev/video0 - Composite3
[New Thread 16385 (LWP 1308)]
[New Thread 8194 (LWP 1309)]
[New Thread 16387 (LWP 1310)]
Changing from None to WatchingLiveTV
[New Thread 24580 (LWP 1314)]
[New Thread 32773 (LWP 1315)]
[New Thread 40966 (LWP 1316)]
[New Thread 49159 (LWP 1317)]
VIDIOCSYNC0: Interrupted system call
-------------------------------------------------------

but without doing the debugging trace, I usually get this in the shell:

Probed: /dev/video0 - Television
Probed: /dev/video0 - Composite1
Probed: /dev/video0 - S-Video
Probed: /dev/video0 - Composite3
Changing from None to WatchingLiveTV


Then it just hangs there. I *DID* notice that, although it appears to
just be sitting there, the file (forget the name right now) in /mnt/store
keeps growing and growing. It seems almost like it's recording live TV
but it's not able to show me what's going on.

I'm so lost!
Jeremy

>
>>> 2. I've been having no luck with getting 'mythtv' working.
>>>
>
> on my redhat 8 system it turned out that plugging in to the "microphone
> in" jack rather than the line in (as I would have thought) solved my
> sound problems. In summary:
>
> Plug into mic in rather than line in. turn up global volume and mic in
> gain. Click mute on microphone. Click record on microphone. worked for
> me.
>
*** OK, before I go on too much more, I guess I should say this (and I
feel stupid for not bringing it up earlier) I DON'T HAVE ANYTHING PLUGGED
INTO THE SOUND CARD EXCEPT SPEAKER OUT! Why? Well, I'm just doing
testing right now before I build a better box. I figured that I didn't
NEED to have an audio-in connection. Does MythTV check for a valid
connection before proceeding with showing the live video stream?

Perhaps I NEED to have something plugged into line-in or mic-in?!

Jeremy

On Monday 11 November 2002 04:58 pm, Jeremy Oddo wrote:
> Then it just hangs there. I *DID* notice that, although it appears to
> just be sitting there, the file (forget the name right now) in /mnt/store
> keeps growing and growing. It seems almost like it's recording live TV
> but it's not able to show me what's going on.
>
> I'm so lost!

You've been told to try ALSA. So, do that. Just sending new messages to the
list with the exact same information/questions isn't going to accomplish
anything.

Isaac

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, what does your settings.txt file look like? What's the height
and width setting?

Does xawtv work?

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPdAtuPc1NpCTlP0JEQLdxgCgqBjPFzDrK+vqNh7JN2661Q8QWnEAn1UC
Lj9JEBHyEZOw6ZjF7GqpYUA+
=e+R+
-----END PGP SIGNATURE-----

> On Monday 11 November 2002 04:58 pm, Jeremy Oddo wrote:
>> Then it just hangs there. I *DID* notice that, although it appears to
>> just be sitting there, the file (forget the name right now) in
>> /mnt/store keeps growing and growing. It seems almost like it's
>> recording live TV but it's not able to show me what's going on.
>>
>
> You've been told to try ALSA. So, do that. Just sending new messages
> to the list with the exact same information/questions isn't going to
> accomplish anything.
>
Don't get me wrong, I'm not trying to ruffle any feathers, I'm _trying_ to
get some more detailed info. mythtv doesn't send much to my shell so I
don't know where it's hanging. I keep bringing up the fact that the file
in /mnt/store keeps growing because I thought that might be useful info
(but up to this point nobody has commented on that). I'm also totally
unfamiliar with ALSA and I'm trying to get my head around it. I _DO_ have
audio in other packages so I wasn't sure if ALSA is a recommendation for
those that are getting NO audio from anywhere. I also asked how to find
out if other apps are grabbing /dev/dsp and, again up to this point, have
had no responses on how to track that down. I guess the reason I keep
asking the same questions is because most of the questions are going
unanswered.

BTW, I copied the "exact same information" to my last question is a
_response_ to someone asking me what I was getting after running
mythfrontend. Not knowing if he'd read my original post, I thought I'd
include it. I figured too much information is better than not enough.

Again, not trying to ruffle feathers. I think the MythTV project is
incredible, but with all new developments, finding answers to questions
isn't exactly the easiest thing to do and when I can only dedicate a
couple hours a week to the project, I was hoping to get a handful of
things to try.

I'm just trying to get as much info under my belt before I can go back
attack my problems.

I can get that getting newbie questions can be real frustrating, but I
honestly don't know where to turn for certain things. And I figure that,
because so many people on the mailing list are installing MythTV, they'd
be the best people to ask.

And so I'll ask it again...is there any way to get some verbose debugging
info? My backtrace didn't yield much.

Jeremy

P.S. The tone of this e-mail (if it is not obvious) is totally
apologetic. I know that Isaac et al are doing this in their free time and
_any_ documentation and help is really appreciated. I don't want to sound
like I'm whining or complaining.

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> OK, what does your settings.txt file look like? What's the height and
> width setting?
>
I've tried 800x600 and 640x480. Changing it didn't help any.

> Does xawtv work?
>
Yeah, quite well :)

Okay ... I believe I ran into the same exact problem
that you are facing. I am planning on compiling some
information on stuff that did and didn't work for me
with mythtv, but I haven't gotten to it yet. For now
here's a quick rundown.

My mythtv was freezing and spewing some error about
not being able to open the audio device /dev/dsp. I
followed everyone's advice to mute the input line and
set it to record. But for some reason the kernel
sound driver or mixer would not do it correctly. So I
went ahead and installed alsa drivers and switched to
using alsa and now sound and everything works.

This may not be your exact problem ... but I remember
somewhere in the docs it said Alsa is recommended ...
so you should do it.

Here's a few steps to get you on your way to using
alsa:

1. make sure that you are NOT using your old sound
drivers. If they are modules then make sure they are
not loaded. If they are built into the kernel then
change them to modules.

2. you SHOULD recompile your kernel to have sound
support as a module. This is from the alsa
documentation.

3. then just follow the instructions to get alsa
working on the gentoo site ... thats what I used. I
realize you don't have a Gentoo system ... but that
just means that the "emerge" steps will have to be
done manually by downloading the package ... no
biggie.

There is tons of documentation at www.tldp.org and
www.alsa-project.org ... that documentation should
answer 99% of the questions you need answering.

http://www.gentoo.org/doc/en/alsa-guide.xml

Once you have alsa up and running ... then test mythtv
again and see if you get the same problem ... if we
can search for the problem elsewhere ... but get alsa
working first.

good luck.

-- Allen

--- Jeremy Oddo <joddo@apixels.net> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > OK, what does your settings.txt file look like?
> What's the height and
> > width setting?
> >
> I've tried 800x600 and 640x480. Changing it didn't
> help any.
>
> > Does xawtv work?
> >
> Yeah, quite well :)
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2

On Mon, Nov 11, 2002 at 03:12:56PM -0800, Jeremy Oddo wrote:
> Don't get me wrong, I'm not trying to ruffle any feathers, I'm _trying_ to
> get some more detailed info. mythtv doesn't send much to my shell so I
> don't know where it's hanging. I keep bringing up the fact that the file
> in /mnt/store keeps growing because I thought that might be useful info
> (but up to this point nobody has commented on that).

Well, it sounds like it's recording but cannot playback at the same time.
What happens if you schedule a recording and go play it back later rather
than watching it live?

> I'm also totally
> unfamiliar with ALSA and I'm trying to get my head around it. I _DO_ have
> audio in other packages so I wasn't sure if ALSA is a recommendation for
> those that are getting NO audio from anywhere.

Most apps don't need full duplex (record and play at the same time). Alsa
drivers generally seem better at that then the kernel drivers, at least with
some sound cards.

--
Ray

OK, I'm actually getting closer to getting 'mythtv' up (I think). MANY
thanks to Ray and Allen for their kind help. This morning I was actually
able to get a green-screen (obviously the wrong input channel). When I
hit 'c' to try and change to Composite3, my machine locked up.

Of course, this has spurred a few more questions for the experts (sorry
for the newbie questions, I really am trying here!):

1. Do I need oss support? I tried to look thru the archives, but the
lack of a search feature makes it a bit difficult.

2. Under KDE, I went to the kernel modification section. Do I need to
COMPLETELY turn off sound support, or just everything minus the top-level
sound support feature?

3. Again in KDE under the control console kernel modifications section, I
noticed that video4linux was NOT ENABLED, however, I have been able to run
xawtv. Do I need to enable it? Seems like I do, but it wasn't enabled
before.

4. I've found conflicting info on this. Under RH8, how do I find out
what /dev my new alsa driver is using? Is it /dev/snd/pcmC0D0c?

5. What's the easiest way to test if ALSA is working correctly? I DO
know that the alsa mod is loading up properly, I just don't hear anything!


Thanks in advance for not flamin' me :)
Jeremy

On Tue, Nov 12, 2002 at 11:55:50AM -0800, Jeremy Oddo wrote:
> OK, I'm actually getting closer to getting 'mythtv' up (I think). MANY
> thanks to Ray and Allen for their kind help. This morning I was actually
> able to get a green-screen (obviously the wrong input channel). When I
> hit 'c' to try and change to Composite3, my machine locked up.
>
> Of course, this has spurred a few more questions for the experts (sorry
> for the newbie questions, I really am trying here!):
>
> 1. Do I need oss support? I tried to look thru the archives, but the
> lack of a search feature makes it a bit difficult.

What do you mean? If you're talking about alsa's oss emulation then the
answer is yes. Even if you wern't using Mythtv you'd want that.

>
> 2. Under KDE, I went to the kernel modification section. Do I need to
> COMPLETELY turn off sound support, or just everything minus the top-level
> sound support feature?

I've never seen a kernel modification section under KDE, maybe that is a RH
or KDE3 feature? All I can tell you about sound under KDE is that you want
the sound server turned off. It may work with the sound server on with some
sound cards but off is the safe answer.


> 3. Again in KDE under the control console kernel modifications section, I
> noticed that video4linux was NOT ENABLED, however, I have been able to run
> xawtv. Do I need to enable it? Seems like I do, but it wasn't enabled
> before.
>
> 4. I've found conflicting info on this. Under RH8, how do I find out
> what /dev my new alsa driver is using? Is it /dev/snd/pcmC0D0c?

You'll be using the alsa oss emulation so it should be using the same device
that it would use with the regular oss drivers. On my Debian system it's
/dev/dsp or /dev/dsp0. I havn't used devfs (which you seem to have) but
maybe something like /dev/snd/dsp0?


> 5. What's the easiest way to test if ALSA is working correctly? I DO
> know that the alsa mod is loading up properly, I just don't hear anything!

Try playing some normal wave or mp3 files with a simple player app. I use
wavp (not sure what package it's part of) or mpg123. If your player app
acts like it's playing but you don't hear anything then probably 1 or more
of your mixer settings is muted. Please note that just turning the volume
up does NOT unmute it. Use alsamixer or amixer to unmute the sound.

--
Ray

I'd suggest compiling your own kernel if you haven't already, it's much
easier IMHO to compile 90% of the vfl/tuner support into the kernel and only
worry about bttv and tv card modules.

Are you up to compiling a fresh kernel? Its not hard.

Important things for my ATI TV wonder...
I2O device support --->
<*> I2O PCI support

Video For Linux --->
[*] V4L information in proc filesystem
<M> BT848 Video For Linux

Character devices --->
I2C support --->
<*> I2C support
<*> I2C bit-banging interfaces
<*> I2C /proc interface (required for hardware sensors) # not sure if
you need this

Sound --->
<*> Sound card support
<M> TV card (bt848) mixer support

Your milage may vary.

Cheers,
Oatz



----- Original Message -----
From: "Jeremy Oddo" <joddo@apixels.net>
To: <mythtv-dev@snowman.net>
Sent: Tuesday, November 12, 2002 2:55 PM
Subject: RE: [mythtv] Couple Newbie Questions -- One Step Closer


> OK, I'm actually getting closer to getting 'mythtv' up (I think). MANY
> thanks to Ray and Allen for their kind help. This morning I was actually
> able to get a green-screen (obviously the wrong input channel). When I
> hit 'c' to try and change to Composite3, my machine locked up.
>
> Of course, this has spurred a few more questions for the experts (sorry
> for the newbie questions, I really am trying here!):
>
> 1. Do I need oss support? I tried to look thru the archives, but the
> lack of a search feature makes it a bit difficult.
>
> 2. Under KDE, I went to the kernel modification section. Do I need to
> COMPLETELY turn off sound support, or just everything minus the top-level
> sound support feature?
>
> 3. Again in KDE under the control console kernel modifications section, I
> noticed that video4linux was NOT ENABLED, however, I have been able to run
> xawtv. Do I need to enable it? Seems like I do, but it wasn't enabled
> before.
>
> 4. I've found conflicting info on this. Under RH8, how do I find out
> what /dev my new alsa driver is using? Is it /dev/snd/pcmC0D0c?
>
> 5. What's the easiest way to test if ALSA is working correctly? I DO
> know that the alsa mod is loading up properly, I just don't hear anything!
>
>
> Thanks in advance for not flamin' me :)
> Jeremy
>
>
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>

I have RH 8 and was seeing this exact lockup until I switched to ALSA.
I couldn't seem to get the Full Duplex drivers that come with RH8 to work
with mythtv correctly. They "seemed" to work when I tested them manually.

Download the ALSA system from their website http://www.alsa-project.org

Mike


On Tue, 12 Nov 2002 11:55:50 -0800 (PST), "Jeremy Oddo" <joddo@apixels.net>
wrote :

> OK, I'm actually getting closer to getting 'mythtv' up (I think). MANY
> thanks to Ray and Allen for their kind help. This morning I was actually
> able to get a green-screen (obviously the wrong input channel). When I
> hit 'c' to try and change to Composite3, my machine locked up.
>
> Of course, this has spurred a few more questions for the experts (sorry
> for the newbie questions, I really am trying here!):
>
> 1. Do I need oss support? I tried to look thru the archives, but the
> lack of a search feature makes it a bit difficult.
>
> 2. Under KDE, I went to the kernel modification section. Do I need to
> COMPLETELY turn off sound support, or just everything minus the top-level
> sound support feature?
>
> 3. Again in KDE under the control console kernel modifications section, I
> noticed that video4linux was NOT ENABLED, however, I have been able to run
> xawtv. Do I need to enable it? Seems like I do, but it wasn't enabled
> before.
>
> 4. I've found conflicting info on this. Under RH8, how do I find out
> what /dev my new alsa driver is using? Is it /dev/snd/pcmC0D0c?
>
> 5. What's the easiest way to test if ALSA is working correctly? I DO
> know that the alsa mod is loading up properly, I just don't hear anything!
>
>
> Thanks in advance for not flamin' me :)
> Jeremy
>
>
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>
>
>

On Mon, Nov 11, 2002 at 02:02:26PM -0800, Jeremy Oddo wrote:

> *** OK, before I go on too much more, I guess I should say this (and I
> feel stupid for not bringing it up earlier) I DON'T HAVE ANYTHING PLUGGED
> INTO THE SOUND CARD EXCEPT SPEAKER OUT! Why? Well, I'm just doing
> testing right now before I build a better box. I figured that I didn't
> NEED to have an audio-in connection. Does MythTV check for a valid
> connection before proceeding with showing the live video stream?

So what sound device do you have mythtv configured to use? If it is trying
to get input from your sound card, and you have no inputs connected, that
will obviously not work.

--
- mdz

> On Mon, Nov 11, 2002 at 02:02:26PM -0800, Jeremy Oddo wrote:
>
>> *** OK, before I go on too much more, I guess I should say this (and I
>> feel stupid for not bringing it up earlier) I DON'T HAVE ANYTHING
>> PLUGGED INTO THE SOUND CARD EXCEPT SPEAKER OUT! Why? Well, I'm just
>> doing testing right now before I build a better box. I figured that I
>> didn't NEED to have an audio-in connection. Does MythTV check for a
>> valid connection before proceeding with showing the live video stream?
>
> So what sound device do you have mythtv configured to use?
>
/dev/dsp

> If it is
> trying to get input from your sound card, and you have no inputs
> connected, that will obviously not work.
>
Well, yeah, obviously. I know it won't "work" (as in, I won't HEAR
anything) but will it "work" (as in, will I see video and my machine won't
lock-up?). As Bill Clinton would say: "It all depends on what you mean
by the word 'work'? I did not have sexual relations with that woman."

I guess my question was: do I need to have a _physical_ audio connection
in order for MythTV to initialize properly and display a video feed?

However, none of that really matters right now as I'm _trying_ to get ALSA
set up properly. I *think* it's set up right but my machine keeps locking
up on me. Perhaps it's my on-board VIA audio. Don't know. That's the
best part...it could be almost anything!

I'm running RH8 but I'm thinking of going debian as it seems like the
install might be easier under that distro.

Oh well...

Jeremy

On Wed, Nov 13, 2002 at 06:23:33PM -0800, Jeremy Oddo wrote:

> I'm running RH8 but I'm thinking of going debian as it seems like the
> install might be easier under that distro.

The install will be much easier, but your problems with the sound device
will likely not be solved by switching distributions.

--
- mdz

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> However, none of that really matters right now as I'm
> _trying_ to get ALSA
> set up properly. I *think* it's set up right but my machine
> keeps locking
> up on me. Perhaps it's my on-board VIA audio. Don't know.
> That's the
> best part...it could be almost anything!
>
> I'm running RH8 but I'm thinking of going debian as it seems like
> the install might be easier under that distro.

If you're going to switch distro's to get ALSA support, then Mandrake
9.0 uses it out of the box. Like I said, I haven't had any problems
with sound.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPdMiUfc1NpCTlP0JEQLo1wCfWWMXrwY3pttMYt6PAEK7dwZoUykAnRtA
7Qgu88V0te6Mv0KLxG6V6RAt
=KFNY
-----END PGP SIGNATURE-----

You can add ALSA to Redhat 7.3 or 8.0 very simply with apt-get, which you
can get from http://freshrpms.net/apt/. All the goodness of apt without the
<insert explative> install of Debian.

apt-get install alsa-driver

Apt will automagically get the correct kernal with ALSA support as a
dependancy for the driver. You might also want alsa-lib, alsaplayer, and
alsa-xmms.



-----Original Message-----
From: mythtv-dev-admin@snowman.net
[mailto:mythtv-dev-admin@snowman.net]On Behalf Of Robert Kulagowski
Sent: Wednesday, November 13, 2002 8:11 PM
To: mythtv-dev@snowman.net
Subject: RE: [mythtv] Couple Newbie Questions



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> However, none of that really matters right now as I'm
> _trying_ to get ALSA
> set up properly. I *think* it's set up right but my machine
> keeps locking
> up on me. Perhaps it's my on-board VIA audio. Don't know.
> That's the
> best part...it could be almost anything!
>
> I'm running RH8 but I'm thinking of going debian as it seems like
> the install might be easier under that distro.

If you're going to switch distro's to get ALSA support, then Mandrake
9.0 uses it out of the box. Like I said, I haven't had any problems
with sound.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPdMiUfc1NpCTlP0JEQLo1wCfWWMXrwY3pttMYt6PAEK7dwZoUykAnRtA
7Qgu88V0te6Mv0KLxG6V6RAt
=KFNY
-----END PGP SIGNATURE-----

_______________________________________________
mythtv-dev mailing list
mythtv-dev@snowman.net
http://www.snowman.net/mailman/listinfo/mythtv-dev

damn amazing. I heard about apt for Red Hat, but was scared to try. Now
I think I might. I didn't realize that apt could do kernels too. One
question: How do I deal with the sound drivers that are already in RH8?
Will apt "automagically" deactivate/eradicate those too? Or do I have
to manually disable them?



cedar


On Wednesday, November 13, 2002, at 10:24 PM, Matthew wrote:

> You can add ALSA to Redhat 7.3 or 8.0 very simply with apt-get, which
> you
> can get from http://freshrpms.net/apt/. All the goodness of apt
> without the
> <insert explative> install of Debian.
>
> apt-get install alsa-driver
>
> Apt will automagically get the correct kernal with ALSA support as a
> dependancy for the driver. You might also want alsa-lib, alsaplayer,
> and
> alsa-xmms.
>
>
>
> -----Original Message-----
> From: mythtv-dev-admin@snowman.net
> [mailto:mythtv-dev-admin@snowman.net]On Behalf Of Robert Kulagowski
> Sent: Wednesday, November 13, 2002 8:11 PM
> To: mythtv-dev@snowman.net
> Subject: RE: [mythtv] Couple Newbie Questions
>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> However, none of that really matters right now as I'm
>> _trying_ to get ALSA
>> set up properly. I *think* it's set up right but my machine
>> keeps locking
>> up on me. Perhaps it's my on-board VIA audio. Don't know.
>> That's the
>> best part...it could be almost anything!
>>
>> I'm running RH8 but I'm thinking of going debian as it seems like
>> the install might be easier under that distro.
>
> If you're going to switch distro's to get ALSA support, then Mandrake
> 9.0 uses it out of the box. Like I said, I haven't had any problems
> with sound.
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
>
> iQA/AwUBPdMiUfc1NpCTlP0JEQLo1wCfWWMXrwY3pttMYt6PAEK7dwZoUykAnRtA
> 7Qgu88V0te6Mv0KLxG6V6RAt
> =KFNY
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-dev

On Wednesday 13 November 2002 09:23 pm, Jeremy Oddo wrote:
> Well, yeah, obviously. I know it won't "work" (as in, I won't HEAR
> anything) but will it "work" (as in, will I see video and my machine won't
> lock-up?). As Bill Clinton would say: "It all depends on what you mean
> by the word 'work'? I did not have sexual relations with that woman."
>
> I guess my question was: do I need to have a _physical_ audio connection
> in order for MythTV to initialize properly and display a video feed?

Nope. Since it doesn't, and you've pretty much confirmed that nothing else is
sitting on the dsp device, the most likely thing is a sound card driver that
doesn't do full duplex properly. If you ever get ALSA working, that _should_
fix it.

Isaac

On 13 Nov 2002 at 18:23, Jeremy Oddo wrote:

> me. Perhaps it's my on-board VIA audio. Don't know. That's the best
> part...it could be almost anything!

Are you using the onboard stuff for your audio or an add in sound card? If
the latter, then you should, actually pretty much MUST disable the onboard
stuff.


--
Harondel J. Sibble
Sibble Computer Consulting
Creating solutions for the small business and home computer user.
help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com
(604) 739-3709 (voice/fax) (604) 686-2253 (pager)