How do I load sound module so it starts at boot?

Booting, installing, newbie
Post Reply
Message
Author
plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

How do I load sound module so it starts at boot?

#1 Post by plockery »

I have a creative vibra 16x isa pnp sound card.
The card is detected during boot and the driver given is sb.
But it does not appear to be loaded at boot.
So I have no sound.
lsmod does not return any sound modules as far as I can see.

How can I load say "modprobe sb" so that it always starts at boot?

User avatar
Ian
Official Dog Handler
Posts: 1234
Joined: Wed 04 May 2005, 12:00
Location: Queensland

#2 Post by Ian »

Does the sound card work when you load a module by hand.

plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

#3 Post by plockery »

Yes it works manually.

When I do a modprobe sb I get the following message:

/etc/modules.conf is more recent than /lib/modules/2.4.27/modules.dep.

Not sure what that means.

But when I open gxine and play /usr/share/audio/ivy.mp3 it plays.

When I reboot without manually loading the sb module, it doesn't.

So I presume I need to somehow have module sb load at boot.

How is this done? And what does thqt message I get above mean?

Guest

#4 Post by Guest »

You could try adding the line ' modprobe sb' in the /etc/rc.d/rc.local file.
Use Rox filer to find rc.local and right click on it, Open as Text, add the line and click save.

What version of Puppy are you using.

plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

#5 Post by plockery »

Thanks guest!

That works! I can play the ivy.wav after boot-up with gxine.

But I do not get any sound at boot-up itself.

Is that because fvmw95 has executed before it loads the sound module?

Should I try putting modprobe sb in .xinitrc before exec fvmw95?

User avatar
Ian
Official Dog Handler
Posts: 1234
Joined: Wed 04 May 2005, 12:00
Location: Queensland

#6 Post by Ian »

Actually the Guest was me, I was in a hurry and didn't log on.
The sound you are talking about, is that the dog barking a bootup, if so have a look in /etc/profiles and see if the entry on line 69 'play.tcl.......' is commented out, if it is remove the # and it should work.

plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

#7 Post by plockery »

Thanks Ian.

It does work but I get two dog barks - one just before the grey screen with an X in the middle comes up and one after fvwm95 loads. Id that normal.

Also I forgot to ask.
This is the output in dmesg for sound:

sb: Creative ViBRA16X PnP detected
sb: ISAPnP reports 'Creative ViBRA16X PnP' at i/o 0x220, irq 10, dma 1, 3
SB 4.16 detected OK (220)
SB16: Bad or missing 16 bit DMA channel
sb: 1 Soundblaster PnP card(s) found.

Do you know what the error about the missing dma channel means?

Peter

User avatar
Ian
Official Dog Handler
Posts: 1234
Joined: Wed 04 May 2005, 12:00
Location: Queensland

#8 Post by Ian »

I found this bit of info on the web in regard to SbB cards.

The SB16 needs two DMA channels. A 8 bit one (1 or 3) is required for 8 bit operation and a 16 bit one (5, 6 or 7) for the 16 bit mode. In theory it's possible to use just one (8 bit) DMA channel by answering the 8 bit one when the configuration program asks for the 16 bit one. This may work in some systems but is likely to cause terrible noise on some other system.

The 'grey screen', usually reffered to as the mesh, is the start of X loading the window manager and as far as I know the only sound enabled at startup is the two barks that are in profile.
You could try changing the sound file by editing the profile file line that you enabled /usr/share/audio/2barks.au & and using bark.au instead which gives only one bark.

plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

#9 Post by plockery »

Thanks Ian for the info.
It looks like the sb module simply cant use the DMA 5, 6 or 7 for some reason.
Sound still seems to work ok, but it is probably just 8 bit.
Can you set dma channels manually for modules to use?

Another problem with sound has arisen - different pc.
I now have puppy loaded on another pc dual booting with win95.
It is a sound blaster compatible PCI card.
The sound is definitely working but it is so faint I can hardly hear it.
(By the way the 2barks occur together at the mesh screen like you say on this pc)
I have the sound coming through my LCD monitor and volume is at 100%.
When I boot in win95 startup sound is loud and clear.
But not when I boot up into puppy. Really faint.
Do you have any clues on this one?
Is there a basic volume control that might need to be adjusted?

The sound information in dmesg is as follows:

es1371: version v0.32 time 16:59:39 Dec 21 2004
PCI: Found IRQ 10 for device 00:0b.0
PCI: Sharing IRQ 10 with 00:07.2
es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x08
es1371: found es1371 rev 8 at io 0xe800 irq 10
es1371: features: joystick 0x0
ac97_codec: AC97 Audio codec, id: CRY19 (Cirrus Logic CS4297A rev A)
PCI: Found IRQ 5 for device 00:09.0

And lsmod returns:

parport_pc 14756 0
parport 24128 0 [parport_pc]
sr_mod 14648 0 (unused)
ide-cd 29504 0
cdrom 28096 0 [sr_mod ide-cd]
sd_mod 11372 0 (unused)
usb-uhci 21964 0 (autoclean) (unused)
usbcore 58976 1 (autoclean) [usb-uhci]
3c59x 26384 1 (autoclean)
es1371 25768 0 (autoclean)
ac97_codec 12040 0 (autoclean) [es1371]
soundcore 3524 4 (autoclean) [es1371]
gameport 1628 0 (autoclean) [es1371]
scsi_mod 96952 2 [sr_mod sd_mod]

So the right modules seem to be loaded.
Any clues?

Peter

plockery
Posts: 26
Joined: Mon 13 Jun 2005, 09:28

#10 Post by plockery »

Solved the faint sound problem.
Found xtmix and after adjusting volume levels I can now here the sound fine.

Peter

Post Reply