On Sat, 14 Feb 2004, Martin Braun wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hartmut Geissbauer wrote:
> | sorry for the question. Do you know, that the new module-init-tools
> | (former modutils) are using modprobe.conf instead of modules.conf? (for
> | kernel 2.6.x)
>
> hi,
>
Hi, Frank. Thanks a lot for your reply.
Looks like the part that I left out was the including the alsa-driver
stuff into the kernel directories. Thanks again. I'll give that a try.
Can't wait to use my new US-122. It's the first step to getting my
digital recording set up.
-Eric.
Frank Ba
Hallo,
Eric Berg hat gesagt: // Eric Berg wrote:
> I recently upgraded to a 2.6.1 kernel right before I bought a Tascam
> US-122. I've got Alsa working just fine as well as USB -- all good.
> However, I have had a bear of a time figuring out how to get the usx2y
> modules to build properly wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hartmut Geissbauer wrote:
| sorry for the question. Do you know, that the new module-init-tools
| (former modutils) are using modprobe.conf instead of modules.conf? (for
| kernel 2.6.x)
hi,
no, i didn't! That was exactly the problem. just copied my old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim McCloskey said on 2/14/2004 13:51:
>
> [2] To record from line input using this card (the Turtle Beach Santa
> Cruz, cs46xx driver), you have to set *all three* of:
>
> LINE CAPTURE ADC
>
> to Captur(e) (and also un-mut
On Sat, 14 Feb 2004, Joachim Feise wrote:
|> > I wanted to replace my aging sbawe (which works fine with Alsa)
|> > with a Turtle Beach Santa Cruz card.
|> > I can play sound, but recording from Line-In does not work.
|> > I just get silence.
|> > The recording sw (RealProducer 8.5)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Unruh said on 2/14/2004 12:44:
>>>a) Line in is muted
>>>b) Line in has its amplitude all the way down.
>>
>>Nope. Checked all that.
>>Using alsamixer, I unmuted line in, and set the amplitude to 100%.
>>
>
> On many cards the input amplitude is
> > a) Line in is muted
> > b) Line in has its amplitude all the way down.
>
> Nope. Checked all that.
> Using alsamixer, I unmuted line in, and set the amplitude to 100%.
>
On many cards the input amplitude is IGain, not linein. linein just
determines how much of the input goes to the output.
Hi Wolfgang,
Am Sam, den 14.02.2004 schrieb [EMAIL PROTECTED] um 19:04:
> Hi,
>
> it seems that the m-audio midisport devices now come with new drivers (both on t
> he
> supplied cd and on the website) that do no longer work with extractfirmware
>
> Any way to go further? (or maybe someone got c
Hi Martin,
Am Sam, den 14.02.2004 schrieb Martin Braun um 18:34:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> (list moderator: I apologize for sending this mail twice to the
> moderator queue).
>
> hi alsa-users,
>
> I recently upgraded from 2.4.24 (everything working fine) to 2.6.2, I
demudi-1.1.0 on Intel D845PEBT2 motherboard with on-board sound:
The mixer is NOT muted, and all the pots are open. An audio source is
plugged into the motherboard INPUT jack, and amplified speakers are
plugged into the motherboard LINE OUT jack.
As soon as Debian starts (but not before), th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[moderators: sorry for repost, I need to remember to set my email
to the one I registered with]
Bill Unruh said on 2/14/2004 11:08:
> On Sat, 14 Feb 2004, Joachim Feise wrote:
>
>
>>I wanted to replace my aging sbawe (which works fine with Alsa)
>>wi
On Sat, 14 Feb 2004, Randy Broman wrote:
> I have a Biostar system with Athlon board, VT8237 southbridge
> (includes audio) and C-Media CMI9739A AC97 Codec. The system
> has SuSE 8.1, but with custom 2.6.2 kernel. I compiled the kernel with
> soundcore and snd_via82xx as modules, updated /etc/mo
On Sat, 14 Feb 2004, Joachim Feise wrote:
> I wanted to replace my aging sbawe (which works fine with Alsa)
> with a Turtle Beach Santa Cruz card.
> I can play sound, but recording from Line-In does not work.
> I just get silence.
> The recording sw (RealProducer 8.5) uses the OSS emulation.
> It
I have a Biostar system with Athlon board, VT8237 southbridge
(includes audio) and C-Media CMI9739A AC97 Codec. The system
has SuSE 8.1, but with custom 2.6.2 kernel. I compiled the kernel with
soundcore and snd_via82xx as modules, updated /etc/modprobe.conf,
and the modules seem to load correctl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
System:
Slackware 9.0, upgraded to kernel 2.6.2, using devfs.
I wanted to replace my aging sbawe (which works fine with Alsa)
with a Turtle Beach Santa Cruz card.
I can play sound, but recording from Line-In does not work.
I just get silence.
The reco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(list moderator: I apologize for sending this mail twice to the
moderator queue).
hi alsa-users,
I recently upgraded from 2.4.24 (everything working fine) to 2.6.2, I
used the version of ALSA provided with the kernel.
The trouble is, ALSA works BUT onl
>= Original Message From Martin Herren <[EMAIL PROTECTED]> =
> > Date: Fri, 13 Feb 2004 17:56:48 -0600
> > From: gideon <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: [Alsa-user] trouble with ALSA 1.0.2c, Kernel 2.6.1
> >
> > However, when I run alsamixer
Hi,
I have installed 1.0.2c driver for Terratec Aureon 7.1 Space (ice1724).
Now, the aim is to play DVD with 24bit-96k sound. What configuration
steps must I do? Which player can do this job?
I have tried MPlayer (pre 2) with command "mplayer -srate 96000 /dev/scd1",
and have got "Too many audio
Hi,
it seems that the m-audio midisport devices now come with new drivers (both on t
he
supplied cd and on the website) that do no longer work with extractfirmware
Any way to go further? (or maybe someone got copies of the old driver files to s
hare)
Wolfgang Hamann
---
Hey,
I recently upgraded to a 2.6.1 kernel right before I bought a Tascam
US-122. I've got Alsa working just fine as well as USB -- all good.
However, I have had a bear of a time figuring out how to get the usx2y
modules to build properly with this kernel.
I looked at the 2.6.x build pages, b
FYI - This is informational only. It may or may not apply to your case.
The PCI spec does not require all latency timers are writable. Latency
Timers are only required to be writable for PCI bus masters, and then
only if they burst more than two data phases, however for any bus master
device that
However, when I run alsamixer to unmute my sound levels, I get:
alsamixer: function snd_ctl_open failed for default: No such device
And if I run amixer, I get:
amixer: Mixer attach default error: No such device
First thing, make sure /dev/dsp, /dev/mixer and anything like that are chmod
777ed
> Date: Fri, 13 Feb 2004 17:56:48 -0600
> From: gideon <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Alsa-user] trouble with ALSA 1.0.2c, Kernel 2.6.1
>
> However, when I run alsamixer to unmute my sound levels, I get:
>
> alsamixer: function snd_ctl_open failed for default: No such de
Hi all,
lspci -vv shows that the latency_timer of my nForce's AC97 function is
set to 0, but the device would really like more than that!
However, when I set it with setpci, nothing changes according to lspci.
Anyone know a workaround/fix?
I'm using a Gigabyte 7N400 Pro2 board.
I suspect that
25 matches
Mail list logo
