LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 06-29-2008, 02:55 AM   #1
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Rep: Reputation: 30
"modprobe warning: not loading blacklisted module snd_ens1371" at boot


lspci="02:0b.0 Multimedia audio controller: Creative Labs Ectiva EV1938"
uname -r="2.6.18-6-686"

Audio works with OSS but would prefer ALSA so I can voice chat with Skype. Suspect this blacklist is keeping sound from working with ALSA.

When I run ALSACONF the results seem nominal but no sound. When I run ALSAMIXER everything is set correctly, but still no sound.

Any suggestions would be appreciated.

Thanks in advance,

bezdomny
 
Old 06-29-2008, 06:37 AM   #2
blackhole54
Senior Member
 
Registered: Mar 2006
Posts: 1,896

Rep: Reputation: 61
The blacklisting is probably taking place in /etc/modprobe.d/blacklist I suppose you can try unblacklisting it. Or, perhaps comments in that file will tell you why it is blacklisted and give you some clue what to do.
 
Old 06-29-2008, 07:33 AM   #3
forum1793
Member
 
Registered: May 2008
Posts: 312

Rep: Reputation: 34
If sound driver module was not loaded how would things be set correctly in alsamixer? Maybe (probably) module for sound card is loaded.

When you say OSS is working is this purely with OSS drivers or with OSS emulation via alsa?

Need more info. Does your kernel have sound drivers compiled in like the HUGE kernels or is it all modules? Look through your dmesg output for clues about the sound. Also look through lsmod output for lines with snd and soundcore.
 
Old 06-29-2008, 08:15 AM   #4
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
Thanks blackhole54, but no joy at /etc/modprobe.d/blacklist.

However, /etc/modprobe.d/alsa-base includes the following:

Quote:
install snd-ens1371 /sbin/modprobe --ignore-install snd-ens1371 $CMDLINE_OPTS && /lib/alsa/modprobe-post-install snd-ens1371
Intriguing. I wonder if it applies to the current issue.

Thanks again, and best regards, blackhole54.

bezdomny
 
Old 06-29-2008, 08:44 AM   #5
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
"modprobe warning: not loading blacklisted module snd_ens1371" at boot

Thanks, forum1793.

lsmod=
Quote:
snd_ens1371 23616 0
snd_seq_oss 28768 0
snd_seq_midi 8192 0
snd_seq_midi_event 7008 2 snd_seq_oss,snd_seq_midi
snd_seq 45680 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_rawmidi 22560 2 snd_ens1371,snd_seq_midi
snd_seq_device 7820 4 snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi
snd_ac97_codec 83104 1 snd_ens1371
snd_ac97_bus 2400 1 snd_ac97_codec
snd_pcm_oss 38368 0
snd_mixer_oss 15200 1 snd_pcm_oss
snd_pcm 68676 3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_timer 20996 2 snd_seq,snd_pcm
snd 47012 10 snd_ens1371,snd_seq_oss,snd_seq,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss, snd_pcm,snd_timer
snd_page_alloc 10184 1 snd_pcm
dmesg=
Quote:
es1371: version v0.32 time 22:12:03 Feb 10 2008
ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 23 (level, low) -> IRQ 185
es1371: found chip, vendor id 0x1102 device id 0x8938 revision 0x00
es1371: found es1371 rev 0 at io 0xde80 irq 185
es1371: Enabling internal amplifier.
ac97_codec: AC97 Audio codec, id: (Unknown)
gameport: ESS1371 Gameport is isa0218/gameport0, io 0x218, speed 1147kHz
If I read these outputs correctly, it would seem this is pure OSS. Do you agree?

As for your question
Quote:
Does your kernel have sound drivers compiled in like the HUGE kernels or is it all modules?
I don't know how to answer it (or if perhaps it is answered by the above output quotes).

Ironic. I just bought this card because it gets 100% favorable reviews at LQ HCL!

Thanks again and best regards, forum1793. If you can provide any advice based upon these output quotes, it would be much appreciated.

bezdomny
 
Old 06-29-2008, 02:17 PM   #6
forum1793
Member
 
Registered: May 2008
Posts: 312

Rep: Reputation: 34
From your dmesg the sound card is found. It's not clear to me if any drivers are also loaded for these in kernel but possible. The lsmod output obviously shows some are in modules.

Since drivers are loaded I would guess blacklisting is not an issue. I could be wrong.

The lsmod output does not, to me, obviously indicate oss. For example, my lsmod output for a 2.6.25.7 kernel using alsa is:

Code:
bash-3.1$ lsmod | grep snd
snd_seq_dummy           4100  0
snd_seq_oss            28828  0
snd_seq_midi_event      7168  1 snd_seq_oss
snd_seq                45860  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          7820  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            37792  0
snd_mixer_oss          15104  1 snd_pcm_oss
snd_hda_intel         190968  2
snd_pcm                67332  2 snd_pcm_oss,snd_hda_intel
snd_timer              21384  2 snd_seq,snd_pcm
snd                    48824  12 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
soundcore               7624  1 snd
snd_page_alloc         10248  2 snd_hda_intel,snd_pcm
I compiled with alsa and not the oss deprecated. Under alsa I enabled the oss options (mixer, pcm, and sequencer). My sound card is a realtek that is a component of hda-intel. So you can see why its not crystal clear regarding alsa/oss.

When I look at kernel options (after make xconfig) under alsa for (Creative) ensoniq AudioPCI 1371/1373, it states the module will be called snd-ens1371. For this kernel (2.6.25.7) I do not even see a specific card entry for the ensoniq under OSS.

I guess if alsamixer works you must have alsa drivers loaded. aplay is an alsa program from the alsa-utils package. Try:

Code:
aplay -l
aplay -L
My output for aplay -l is:

Code:
bash-3.1$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC882 Analog [ALC882 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC882 Digital [ALC882 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 0: ATI HDMI [ATI HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
If your output shows some cards I would guess alsa is loaded. If that is the case then your problem might be in how you choose the sound output. For example, for me in xine I had to use hw=1,0 to output to hdmi or hw=0,1 to output to the 2nd card 0 you see above which is optical output. So maybe you have similar situation where you need to tell the program what to use.

If you still think there is oss vs alsa problem consider compiling your own kernel and choose one probably at 2.6.25 or newer.

Last edited by forum1793; 06-29-2008 at 02:27 PM.
 
Old 06-29-2008, 05:18 PM   #7
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
"modprobe warning: not loading blacklisted module snd_ens1371" at boot

Thanks, forum1793.

aplay -l=
Code:
aplay: device_list:222: no soundcards found...
aplay -L=
Code:
PCM list:
hw {
        @args.0 CARD
        @args.1 DEV
        @args.2 SUBDEV
        @args.CARD {
                type string
                default {
                        @func getenv
                        vars {
                                0 ALSA_PCM_CARD
                                1 ALSA_CARD
                        }
                        default {
                                @func refer
                                name 'defaults.pcm.card'
                        }
                }
        }
        @args.DEV {
                type integer
                default {
                        @func igetenv
                        vars {
                                0 ALSA_PCM_DEVICE
                        }
                        default {
                                @func refer
                                name 'defaults.pcm.device'
                        }
                }
        }
        @args.SUBDEV {
                type integer
                default {
                        @func refer
                        name 'defaults.pcm.subdevice'
                }
        }
        type hw
        card $CARD
        device $DEV
        subdevice $SUBDEV
}
plughw {
        @args.0 CARD
        @args.1 DEV
        @args.2 SUBDEV
        @args.CARD {
                type string
                default {
                        @func getenv
                        vars {
                                0 ALSA_PCM_CARD
                                1 ALSA_CARD
                        }
                        default {
                                @func refer
                                name 'defaults.pcm.card'
                        }
                }
        }
        @args.DEV {
                type integer
                default {
                        @func igetenv
                        vars {
                                0 ALSA_PCM_DEVICE
                        }
                        default {
                                @func refer
                                name 'defaults.pcm.device'
                        }
                }
        }
        @args.SUBDEV {
                type integer
                default {
                        @func refer
                        name 'defaults.pcm.subdevice'
                }
        }
        type plug
        slave.pcm {
                type hw
                card $CARD
                device $DEV
                subdevice $SUBDEV
        }
}
plug {
        @args.0 SLAVE
        @args.SLAVE {
                type string
        }
        type plug
        slave.pcm $SLAVE
}
shm {
        @args.0 SOCKET
        @args.1 PCM
        @args.SOCKET {
                type string
        }
        @args.PCM {
                type string
        }
        type shm
        server $SOCKET
        pcm $PCM
}
tee {
        @args.0 SLAVE
        @args.1 FILE
        @args.2 FORMAT
        @args.SLAVE {
                type string
        }
        @args.FILE {
                type string
        }
        @args.FORMAT {
                type string
                default raw
        }
        type file
        slave.pcm $SLAVE
        file $FILE
        format $FORMAT
}
file {
        @args.0 FILE
        @args.1 FORMAT
        @args.FILE {
                type string
        }
        @args.FORMAT {
                type string
                default raw
        }
        type file
        slave.pcm null
        file $FILE
        format $FORMAT
}
null {
        type null
}
cards 'cards.pcm'
front 'cards.pcm.front'
rear 'cards.pcm.rear'
center_lfe 'cards.pcm.center_lfe'
side 'cards.pcm.side'
surround40 'cards.pcm.surround40'
surround41 'cards.pcm.surround41'
surround50 'cards.pcm.surround50'
surround51 'cards.pcm.surround51'
surround71 'cards.pcm.surround71'
iec958 'cards.pcm.iec958'
spdif 'cards.pcm.iec958'
modem 'cards.pcm.modem'
phoneline 'cards.pcm.phoneline'
default 'cards.pcm.default'
dmix 'cards.pcm.dmix'
dsnoop 'cards.pcm.dsnoop'
What do you make of this?

Compile my own kernel, eh? I've never done that before, but there's a first time for everything. Thanks again and best regards, forum1793,

bezdomny
 
Old 06-29-2008, 05:23 PM   #8
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
PS-- Dear forum1793,

ALSACONF=
Code:
Unloading ALSA sound driver modules: snd-ens1371 snd-seq-oss snd-seq-midi snd-seq-midi-event snd-seq snd-rawmidi snd-seq-device snd-ac97-codec snd-ac97-bus snd-pcm-oss snd-mixer-oss snd-pcm snd-timer snd-page-alloc.
This is important, right? Can you please interpret it for me?

Thank you,

bezdomny
 
Old 06-29-2008, 08:48 PM   #9
forum1793
Member
 
Registered: May 2008
Posts: 312

Rep: Reputation: 34
Based on what you're showing it would seem that alsa is not loaded/working. The messages you are getting I have not seen before. In your situation I would consider downloading a newer distribution. But, before you do that give it some time and perhaps others here will give you better guidance. You may wish to post more info on your hardware and linux distribution/version. If making any changes remember to backup all files you care about. I have had to relearn that lesson many times. Good luck.

PS - I still don't know how alsamixer is working if aplay is not showing any cards.

Last edited by forum1793; 06-29-2008 at 08:52 PM.
 
Old 06-29-2008, 10:58 PM   #10
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
"modprobe warning: not loading blacklisted module snd_ens1371" at boot

Thanks, forum1793. Best regards,

bezdomny
 
Old 06-30-2008, 12:20 AM   #11
blackhole54
Senior Member
 
Registered: Mar 2006
Posts: 1,896

Rep: Reputation: 61
OK, I'm kind of making a stab in the dark here in an area I don't have a great deal of experience, but ...

Code:
install snd-ens1371 /sbin/modprobe --ignore-install snd-ens1371 $CMDLINE_OPTS && /lib/alsa/modprobe-post-install snd-ens1371
The above entry from /etc/modprobe.d/alsa-base gives alternate instructions to modprobe. Instead of simply loading snd-ens1371, it is to load it with $CMDLLINE_OPTS and then run the command:

Code:
/lib/alsa/modprobe-post-install snd-ens1371
(The --ignore-install option just keeps modprobe from going in a viscious loop.)

So it might be worthwhile seeing if anything interesting shows up if you manually unload and then load snd-ens1371 from the command line (as root):

Code:
modprobe -r snd-ens1371
modprobe snd-ens1371
EDIT: After posting I did a search on "snd-ens1371" and etch and found this blog entry which might be useful.

Last edited by blackhole54; 06-30-2008 at 12:33 AM. Reason: spelling
 
Old 07-01-2008, 08:55 AM   #12
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
modprobe warning: not loading blacklisted module snd_ens1371" at boot

Thanks, blackhole 54. Ran modprobe -r snd-ens1371, and then ran modprobe snd-ens1371 with nominal results, no error messages. But still no sound. Upgraded to Lenny, still no sound.

New info-- /var/log/boot=
Code:
^[]R^[[9;30]^[[14;30]Setting up ALSA...warning: 'alsactl restore' failed with error message 'alsactl: load_state:1327: No soundcards found...'...done
Thanks again for your help, blackhole 54. hope we can find a solution.

Best regards,

bezdomny
 
Old 07-01-2008, 11:47 PM   #13
blackhole54
Senior Member
 
Registered: Mar 2006
Posts: 1,896

Rep: Reputation: 61
Quote:
Originally Posted by bezdomny View Post
Code:
^[]R^[[9;30]^[[14;30]Setting up ALSA...warning: 'alsactl restore' failed with error message 'alsactl: load_state:1327: No soundcards found...'...done
Take a look at this. I'm not sure what to make of it, but again, I didn't put much effort into it.
 
Old 07-02-2008, 08:39 AM   #14
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
modprobe warning: not loading blacklisted module snd_ens1371" at boot

Thanks, blackhole54. Still no joy. I think the only answer is to upgrade my kernel...I've tried twice but get the fatal boot error:
Code:
kernel panic- not syncing: vfs: unable to mount root fs on unknown-block (0,0)
Guess that's a topic for a new thread!

Thanks for all your help, blackhole54.
 
Old 07-02-2008, 09:39 AM   #15
bezdomny
Member
 
Registered: May 2006
Location: North-Central California
Distribution: Debian Lenny
Posts: 154

Original Poster
Rep: Reputation: 30
modprobe warning: not loading blacklisted module snd_ens1371" at boot

Successfully resolved kernel-panic error and am now running on latest kernel (2.6.25.9). Can hear "click" in headphones when ALSACONF loads the driver, but still no sound when running XMMS.

Old boot error messages gone, now /var/log/boot=
Code:
Wed Jul  2 07:22:33 2008: ^[]R^[[9;30]^[[14;30]Setting up ALSA...warning: 'alsactl restore' failed with error message 'alsactl: set_control:991
: warning: name mismatch (Master Mono Playback Volume/LFE Playback Switch) for control #4
Wed Jul  2 07:22:33 2008: alsactl: set_control:993: warning: index mismatch (0/0) for control #4
Wed Jul  2 07:22:33 2008: alsactl: set_control:1106: bad control.4.value.0 content'...done.
Will keep trying!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"FATAL: Module not found error" using modprobe naveen_highlander Linux - Newbie 8 05-07-2013 02:30 AM
lm-sensors "Warning: the required module is not currently installed" PeeCee-BW Linux - Newbie 1 06-29-2008 01:24 AM
lm-sensors "Warning: the required module is not currently installed" PeeCee-BW Linux - Hardware 2 06-27-2008 12:36 AM
Receive "modprobe: Canít locate module block-major-" and disconnects NFS mount car182 Linux - Hardware 1 05-25-2006 08:46 AM
"modprobe: can't locate module char-major-188"mesage eye Red Hat 4 10-23-2003 07:09 PM


All times are GMT -5. The time now is 02:29 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration