Skip to contentSkip to conversation

SoundBlaster Live! with kernel 2.5.x

DISCUSSION Udo Hoerhold 3 participants 6 messages Apr 16, 2003 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hello,

I've been running Debian woody with 2.4.20 kernel. I'm trying to switch to 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with 2.4.20), but I get only a lot of popping sounds from the sound card. I also tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and soundblaster with 2.5, but I haven't seen anyone else with the same problem. Does anyone know what this problem is?

Thanks,

Udo Hoerhold

#1 lore raw
Quoted 6 lines · Udo Hoerhold

I've been running Debian woody with 2.4.20 kernel. I'm trying to switch to 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with 2.4.20), but I get only a lot of popping sounds from the sound card. I also tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and soundblaster with 2.5, but I haven't seen anyone else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 21 lines · Robert Love
Quoted 7 lines · Udo Hoerhold

I've been running Debian woody with 2.4.20 kernel. I'm trying to switch to 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with 2.4.20), but I get only a lot of popping sounds from the sound card. I also tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and soundblaster with 2.5, but I haven't seen anyone else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y
Quoted 7 lines

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

I have the exact configuration you have above. The soundcard is detected, but I do get one error:

Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
Version 0.9.2 (Thu Mar 20$
Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
snd-card-0. error = -16
Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0
Apr 15 22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
Apr 15 22:17:45 hobbiton kernel: ALSA device list:
Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at

0xdf80, irq 10

I've been ignoring modprobe errors because I know there are some issues with 2.5 kernel and modules, and I'm compiling everything into the kernel. Could this be causing a problem, though?

Thanks,

Udo Hoerhold

#4 lore raw
Quoted 40 lines · Robert Love
Quoted 20 lines · Udo Hoerhold
Quoted 1 line

I've been running Debian woody with 2.4.20 kernel. I'm trying to switch

to 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with 2.4.20), but I get only a lot of popping sounds from the sound card. I also tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and soundblaster with 2.5, but I haven't seen anyone else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y
Quoted 7 lines

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

I have the exact configuration you have above. The soundcard is detected, but I do get one error:

Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
Version 0.9.2 (Thu Mar 20$
Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
snd-card-0. error = -16
Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr 15
22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
Apr 15 22:17:45 hobbiton kernel: ALSA device list:
Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at
Quoted 4 lines

0xdf80, irq 10

I've been ignoring modprobe errors because I know there are some issues with 2.5 kernel and modules, and I'm compiling everythiu10k and soundblaster with

2.5, but I haven't seen anyone

Quoted 33 lines
Quoted 14 lines

else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y
Quoted 7 lines

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

I have the exact configuration you have above. The soundcard is detected, but I do get one error:

Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
Version 0.9.2 (Thu Mar 20$
Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
snd-card-0. error = -16
Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr 15
22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
Apr 15 22:17:45 hobbiton kernel: ALSA device list:
Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at
Quoted 5 lines

0xdf80, irq 10

I've been ignoring modprobe errors because I know there are some issues with 2.5 kernel and modules, and I'm compiling everything into the kernel. Could this be causing a problem, though?

I don't think you need to be ignoring module problems now.

Do you have emu10k1 built as loadable module or in-kernel?

-16 error is saying that the IO region or the IRQ is busy so the driver can't allocate it.

Is /sbin/modprobe a current version (for 2.5.50++ and recent)?

~Randy

#5 lore raw
Quoted 90 lines · Randy.Dunlap
Quoted 41 lines
Quoted 22 lines · Udo Hoerhold
Quoted 2 lines

I've been running Debian woody with 2.4.20 kernel. I'm trying to switch

to 2.5. I built 2.5.67 with emu10k driver in the kernel (same as I had with 2.4.20), but I get only a lot of popping sounds from the sound card. I also tried 2.5.50 and 2.5.67-mm3, with the same result. I googled for emu10k and soundblaster with 2.5, but I haven't seen anyone else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y
Quoted 7 lines

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

I have the exact configuration you have above. The soundcard is detected, but I do get one error:

Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
Version 0.9.2 (Thu Mar 20$
Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
snd-card-0. error = -16
Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr
15 22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
Apr 15 22:17:45 hobbiton kernel: ALSA device list:
Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at
Quoted 5 lines

0xdf80, irq 10

I've been ignoring modprobe errors because I know there are some issues with 2.5 kernel and modules, and I'm compiling everythiu10k and soundblaster with

2.5, but I haven't seen anyone

Quoted 33 lines
Quoted 14 lines

else with the same problem. Does anyone know what this problem is?

Not sure. It seems to work fine here.

Are you using ALSA or OSS? Best bet is ALSA. You want something like:

        CONFIG_SND=y
        CONFIG_SND_SEQUENCER=y
        CONFIG_SND_OSSEMUL=y
        CONFIG_SND_MIXER_OSS=y
        CONFIG_SND_PCM_OSS=y
        CONFIG_SND_SEQUENCER_OSS=y
        CONFIG_SND_EMU10K1=y
Quoted 7 lines

And then do not include any of the OSS stuff.

Then a normal audio playback on /dev/audio or whatever should work fine.

If not, do you see any errors during boot?

Robert Love

I have the exact configuration you have above. The soundcard is detected, but I do get one error:

Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
Version 0.9.2 (Thu Mar 20$
Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
snd-card-0. error = -16
Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr
15 22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
Apr 15 22:17:45 hobbiton kernel: ALSA device list:
Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at
Quoted 5 lines

0xdf80, irq 10

I've been ignoring modprobe errors because I know there are some issues with 2.5 kernel and modules, and I'm compiling everything into the kernel. Could this be causing a problem, though?

I don't think you need to be ignoring module problems now.

Quoted 8 lines

Do you have emu10k1 built as loadable module or in-kernel?

-16 error is saying that the IO region or the IRQ is busy so the driver can't allocate it.

Is /sbin/modprobe a current version (for 2.5.50++ and recent)?

~Randy

It's compiled into the kernel. I'm not sure why I would be getting modprobe errors, everything is compiled in. I have module-init-tools 0.9.11a, which is the right modprobe for 2.5.46 and up, right?

Udo

#6 lore raw

On Wed, 16 Apr 2003 02:00:57 -0400 Udo Hoerhold <[email protected]> wrote:

| On Wednesday 16 April 2003 12:58 am, Randy.Dunlap wrote:

| > >
| > > I have the exact configuration you have above.  The soundcard is
| > > detected, but I do get one error:
| > >
| > > Apr 15 22:17:45 hobbiton kernel: Advanced Linux Sound Architecture Driver
| > > Version 0.9.2 (Thu Mar 20$
| > > Apr 15 22:17:45 hobbiton kernel: request_module: failed /sbin/modprobe --
| > > snd-card-0. error = -16
| > > Apr 15 22:17:45 hobbiton kernel: PCI: Found IRQ 10 for device 02:0b.0 Apr
| > > 15 22:17:45 hobbiton kernel: PCI: Sharing IRQ 10 with 00:1f.2
| > > Apr 15 22:17:45 hobbiton kernel: ALSA device list:
| > > Apr 15 22:17:45 hobbiton kernel:   #0: Sound Blaster Live! (rev.7) at
| > > 0xdf80, irq 10
| > >
| > > I've been ignoring modprobe errors because I know there are some issues
| > > with 2.5 kernel and modules, and I'm compiling everything into the
| > > kernel.  Could this be causing a problem, though?
| >
| > I don't think you need to be ignoring module problems now.
| >
| > Do you have emu10k1 built as loadable module or in-kernel?
| >
| > -16 error is saying that the IO region or the IRQ is busy so the
| > driver can't allocate it.
| >
| > Is /sbin/modprobe a current version (for 2.5.50++ and recent)?
| >
| > ~Randy
| 
| It's compiled into the kernel.  I'm not sure why I would be getting modprobe 
| errors, everything is compiled in.  I have module-init-tools 0.9.11a, which 
| is the right modprobe for 2.5.46 and up, right?

That sounds right for tools.
But if emu10k1 is built into the kernel, you don't need to modprobe it at all. Why is that happening? Do you actually have emu10k1 module also? It should have errors when loading if the device is already claimed.

--
~Randy