Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.hardware > #1121

Re: Cannot find multimedia device

From Haines Brown <haines@HistoricalMaterialism.info>
Newsgroups comp.os.linux.hardware
Subject Re: Cannot find multimedia device
References (3 earlier) <jk07le$en7$5@dont-email.me> <87limzts3o.fsf@engels.HistoricalMaterialism.info> <jk216h$4ef$3@dont-email.me> <87haxnt8cb.fsf@engels.HistoricalMaterialism.info> <jk2r63$tak$1@dont-email.me>
Date 2012-03-18 15:38 -0400
Message-ID <87d389u2c9.fsf@engels.HistoricalMaterialism.info> (permalink)

Show all headers | View raw


I cleared the situation up a bit by removing the line in the
/etc/modules file that was loading the emu10k1 for the SoundBlaster Live
card no longer in the system. I unloaded the snd_emu10k1 with
modprobe. I loaded the snd_ctxfi module required by my Creative Labs
X-Fi card and restarted the ALSA system.

A sound output test works. The Audacity application reports mike input
level with the playback and recording device specified as "Creative
X-Fi: Front/WaveIn (hw:0,0), but the application does not work if they
are specified as "default". Does NaturallySpeaking look for the default
mike. Any way to set my card to be the default?

NaturallySpeaking error also says it may not start because my sound card
lacks a wave-in component. I searched for a long time to find out what
"wave-in component" means, and as best I can make out it is Nuance
NaturallySpeaking jargon. I'll have to give them a call tomorrrow.

In alsamixer everything is un-muted and level set high. And the Gnome
gui configuration for sound displays the Capture devices as muted and
can't be un-muted. What is the explanation for this inconsistency, for
the gui application says it uses alsamixer? This might also hint that my
problem is not with NaturallySpeaking, but with my sound system set up.

>> Here's the entire file.
>
> No that is not the alsa.conf file from /etc/modprobe.d as requested.

I apologize for the inefficiency. 

There is no /etc/modprobe.d/alsa.conf, but rather
/etc/modprobe.d/alsa-base.conf. Here it is:

  # autoloader aliases
  install sound-slot-0 /sbin/modprobe snd-card-0
  install sound-slot-1 /sbin/modprobe snd-card-1
  install sound-slot-2 /sbin/modprobe snd-card-2
  install sound-slot-3 /sbin/modprobe snd-card-3
  install sound-slot-4 /sbin/modprobe snd-card-4
  install sound-slot-5 /sbin/modprobe snd-card-5
  install sound-slot-6 /sbin/modprobe snd-card-6
  install sound-slot-7 /sbin/modprobe snd-card-7
  # Cause optional modules to be loaded above generic modules
  install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd$
  install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modp$
  install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modp$

  # Prevent abnormal drivers from grabbing index 0
  options bt87x index=-2
  options cx88_alsa index=-2
  options snd-atiixp-modem index=-2
  options snd-intel8x0m index=-2
  options snd-via82xx-modem index=-2
  # Keep snd-pcsp from beeing loaded as first soundcard
  options snd-pcsp index=-2
  # Keep snd-usb-audio from beeing loaded as first soundcard
  options snd-usb-audio index=-2

Ouch. Although I removed the line from /etc/modules re emu10k1, and
rebooted, and lsmod says the snd_ctfi was automatically loaded, this
file shows that the module emu10k1 remains loaded as optional
module. No idea how that happens.

> So to repeat, I strongly urge you to make a backup of all of your
> personal data files and perhaps /etc for possible reference, remove
> the X FI card and replace it with either the SB Live or an Audigy 2
> (the version is important) and then do a CLEAN installation of Debian
> again, either Debian stable or if you want something more up to date
> and are prepared to do regular upgrades, Linux Mint Debian Edition
> (basically Debian testing).

I have to use a PCI-e 1x interface, so it limits the cards in hand that
I can use. I have a Creative Labs X-Fi Titanium, and it seems that my
Debian Squeeze supports it. Reinstalling Debian makes sense, but it is
hard to take a day off from work that is very pressing all my time. So
I'll initially just swap the cards to see how it goes.

Incidentally, I find that folks have exprienced trouble unmuting the
mike because the ALSA sound server is provided by pulse audio by
default. So it is necessary to set ALSA Sound System explicitly in gnome
sound settings. Another thing to do is set Log level for Pulse Audio in
/etc/pulse/daemon.conf:

        -log-level = normal
        +log-level = stderr

I don't understand this. In gnome Settings, Sound, the Creative X-Fi
card is the only device I can select.

Back to comp.os.linux.hardware | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-15 12:31 -0400
  Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-15 16:52 +0000
    Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-16 14:33 -0400
      Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-16 20:26 +0000
        Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-17 06:54 -0400
          Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-17 12:48 +0000
            Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-17 12:57 +0000
            Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-17 14:01 -0400
              Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-17 20:11 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-18 15:38 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-18 20:50 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-19 16:30 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-19 22:21 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-20 10:34 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-20 15:05 +0000
              Re: Cannot find multimedia device Clemens Ladisch <clemens@ladisch.de> - 2012-03-17 21:15 +0100
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-17 20:58 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-30 08:31 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-30 13:35 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-30 18:35 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-31 09:18 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-31 08:32 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-03-31 16:46 +0000
                Re: Cannot find multimedia device Haines Brown <haines@HistoricalMaterialism.info> - 2012-03-31 18:08 -0400
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-04-01 10:30 +0000
                Re: Cannot find multimedia device J G Miller <miller@yoyo.ORG> - 2012-04-01 13:06 +0000

csiph-web