LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   Sound Blaster Live! Audio Problem in Mandrake 10CE (https://www.linuxquestions.org/questions/mandriva-30/sound-blaster-live-audio-problem-in-mandrake-10ce-187182/)

DaveThePuzzled 05-29-2004 12:26 AM

Sound Blaster Live! Audio Problem in Mandrake 10CE
 
Hello All,

I am having a problem with my sound card. I have made sure the master and PCM is unmuted, I have checked my driver usage to make sure it is using the right driver, which is "emu10k1". Is there anything else to do for this problem??

Thanks in advance,
DaveThePuzzled
:newbie:

bibilit 05-29-2004 01:35 AM

What is the output of : dmesg ?

adz 05-29-2004 02:35 AM

You said you're having problems but neglected to specify them. Are you saying that sounds looks like it's playing but no actual sound comes out? If so, try to go through and umute ALL channels and set them to about 70-80%.

DaveThePuzzled 05-29-2004 03:03 AM

I hope you are ready for this. There was a lot of output for this....

Linux version 2.6.3-4mdk (nplanel@n3.mandrakesoft.com) (gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)) #1 Tue Mar 2 07:26:13 CET 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000040fd800 (usable)
BIOS-e820: 00000000040fd800 - 00000000040ff800 (ACPI data)
BIOS-e820: 00000000040ff800 - 00000000040ffc00 (ACPI NVS)
BIOS-e820: 00000000040ffc00 - 000000000c000000 (usable)
BIOS-e820: 00000000fffe7000 - 0000000100000000 (reserved)
192MB LOWMEM available.
On node 0 totalpages: 49152
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 45056 pages, LIFO batch:11
HighMem zone: 0 pages, LIFO batch:1
DMI 2.1 present.
ACPI disabled because your bios is from 1999 and too old
You can enable it with acpi=force
Built 1 zonelists
Kernel command line: root=/dev/hdb1 devfs=mount acpi=ht resume=/dev/hdb5 splash=silent vga=788
bootsplash: silent mode.
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 547.320 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Memory: 190564k/196608k available (1815k kernel code, 5360k reserved, 846k data, 272k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1081.34 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 131k freed
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Katmai) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 547.0086 MHz.
..... host bus clock speed is 99.0469 MHz.
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfd983, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040211
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX/ICH [8086/7110] at 0000:00:07.0
vesafb: framebuffer at 0xf0000000, mapped to 0xcc800000, size 16384k
vesafb: mode is 800x600x16, linelength=1600, pages=67
vesafb: protected mode interface info at c000:569b
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Initializing Cryptographic API
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
bootsplash 3.1.3-2003/11/14: looking for picture.... silentjpeg size 14856 bytes, found (800x600, 14808 bytes, v3).
Console: switching to colour frame buffer device 92x32
pty: 1024 Unix98 ptys configured
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1000-0x1007, BIOS settings: hda:pio, hdb:DMA
ide1: BM-DMA at 0x1008-0x100f, BIOS settings: hdc:pio, hdd:DMA
hda: WDC WD400BB-00DEA0, ATA DISK drive
hdb: WDC WD205BA, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: DVDROM 10X, ATAPI CD/DVD-ROM drive
hdd: SONY CD-RW CRX140E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(33)
/dev/ide/host0/bus0/target0/lun0: p1
hdb: max request size: 128KiB
hdb: 40088160 sectors (20525 MB) w/2048KiB Cache, CHS=39770/16/63, UDMA(33)
/dev/ide/host0/bus0/target1/lun0: p1 p2 < p5 p6 >
Console: switching to colour frame buffer device 92x32
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
EISA: Probing bus 0 at eisa0
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET: Registered protocol family 1
BIOS EDD facility v0.12 2004-Jan-26, 2 devices found
Please report your BIOS at http://linux.dell.com/edd/results.html
Resume Machine: resuming from /dev/hdb5
Resuming from device hdb5
Resume Machine: This is normal swap space
PM: Reading pmdisk image.
PM: Resume from disk failed.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Mounted devfs on /dev
Freeing unused kernel memory: 272k freed
Real Time Clock Driver v1.12
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
PCI: Found IRQ 9 for device 0000:00:07.2
PCI: Sharing IRQ 9 with 0000:00:10.0
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: irq 9, io base 00001020
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usb 1-2: new full speed USB device using address 2
Linux video capture interface: v1.00
drivers/usb/media/ibmcam.c: Veo Stingray [800C] USB camera found (model 2, rev. 0x030a)
videodev: "ibmcam USB Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
drivers/usb/media/usbvideo.c: ibmcam on /dev/video0: canvas=352x240 videosize=352x240
drivers/usb/core/usb.c: registered new driver ibmcam
EXT3 FS on hdb1, internal journal
Adding 4089416k swap on /dev/hdb5. Priority:-1 extents:1
SCSI subsystem initialized
imm: Version 2.05 (for Linux 2.4.0)
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
ppa: Version 2.07 (for Linux 2.4.x)
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 440BX Chipset.
agpgart: Maximum main memory to use for agp memory: 150M
agpgart: AGP aperture is 64M @ 0xec000000
Supermount version 2.0.4 for kernel 2.6
NTFS driver 2.1.6 [Flags: R/O MODULE].
NTFS volume version 3.1.
sundance.c:v1.01+LK1.09a 10-Jul-2003 Written by Donald Becker
http://www.scyld.com/network/sundance.html
PCI: Enabling device 0000:00:0e.0 (0114 -> 0117)
PCI: Found IRQ 11 for device 0000:00:0e.0
PCI: Sharing IRQ 11 with 0000:01:00.0
eth0: D-Link DFE-530TXS FAST Ethernet Adapter at 0x1080, 00:05:5d:fe:f3:da, IRQ 11.
eth0: MII PHY found at address 1, status 0x782d advertising 01e1.
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (1536 buckets, 12288 max) - 300 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (1536 buckets, 12288 max) - 300 bytes per conntrack
inserting floppy driver for 2.6.3-4mdk
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
hdc: ATAPI DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
NET: Registered protocol family 17
eth0: Link changed: 100Mbps, full duplex
PCI: Enabling device 0000:00:0f.0 (0104 -> 0105)
PCI: Found IRQ 10 for device 0000:00:0f.0
NET: Registered protocol family 10
Disabled Privacy Extensions on device c035fa20(lo)
IPv6 over IPv4 tunneling driver
mtrr: 0xf0000000,0x4000000 overlaps existing 0xf0000000,0x1000000
[drm] Initialized radeon 1.10.0 20020828 on minor 0: ATI Radeon RV280 9200 SE
mtrr: 0xf0000000,0x4000000 overlaps existing 0xf0000000,0x1000000
agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
drivers/usb/media/usbvideo.c: Packet Statistics: Total=64. Empty=31. Usage=51%
drivers/usb/media/usbvideo.c: Transfer Statistics: Transferred=2 B Usage=0%
[drm] Loading R200 Microcode
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 0 changed to on
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 1 changed to on
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 2 changed to on
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 3 changed to on
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 4 changed to on
bootsplash 3.1.3-2003/11/14: looking for picture.... found (800x600, 11943 bytes, v3).
bootsplash: status on console 5 changed to on
eth0: no IPv6 routers present
mtrr: 0xf0000000,0x4000000 overlaps existing 0xf0000000,0x1000000
mtrr: 0xf0000000,0x4000000 overlaps existing 0xf0000000,0x1000000
agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
drivers/usb/media/usbvideo.c: Packet Statistics: Total=64. Empty=31. Usage=51%
drivers/usb/media/usbvideo.c: Transfer Statistics: Transferred=2 B Usage=0%
[drm] Loading R200 Microcode
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.

DaveThePuzzled 05-29-2004 03:06 AM

Quote:

Originally posted by adz
You said you're having problems but neglected to specify them. Are you saying that sounds looks like it's playing but no actual sound comes out? If so, try to go through and umute ALL channels and set them to about 70-80%.
That is correct. It looks like sound comes out but no sound is heard. Everything is already unmuted and turned all the way up. I have been spending this whole day working on correcting my sound card issue. I am using Mandy 10 CE, using a Sound Blaster Live! card I got with my Gateway computer in 2000. My speakers are turned on. I have gone through even trying to recompile my alsa drivers to no avail. I am also reading that this is a common problem for some people. I have even thought about getting a brand new Sound Blaster Live! card just to make sure, unlike the Dell computers, that this card is, in fact, a true Sound Blaster card.:mad:

bibilit 05-29-2004 04:20 AM

Ok, did not know it was a DELL, some troubles with dell products ... problably won't work with Linux !!

Your sound card not detected anyway.

Is MDK control center detecting anything related with your sound card ?

motub 05-29-2004 07:22 AM

I wouldn't be so sure about the sound card not being detected, for the following reasons:

1) The 2.6 series kernels have ALSA integrated by default, but this seems to confuse the hardware detection in some way; I've had 4 2.6-series kernels under 3 different distros, and the boot messages always say "no soundcard detected" until the ALSA init script actually initializes the card;

2) My experience with Mandrake suggests that they almost certainly would have set the ALSA init script to start at rnlevel 5 automatically;

3) If no sound card was detected at all, you would get errors in audio apps-- they wouldn't play on, mutely.

Of course, the easiest way to be certain is to go to the Mandrake Control Center=>HardDrake and confirm that the card is listed there.

I think the card is there and working properly, but you have something muted that is preventing the sound from being heard.

For instance, if the program in question is XMMS, that app has its own volume control. Have you raised that above 0%?

Stupid question for today, but... are the speakers plugged into the correct socket and is their volume raised above 0?

If trying to play an audio CD, is there an audio cable connecting the CD-ROM drive to the sound card?

Have you unmuted the volume in your Desktop Environment's volume control applet only (KMix, or the GNOME Volume Control), alsamixer only, or both (you have to adjust the volume in both areas)?

Have you started the sound server in your Desktop Environment (aRTs if KDE, esd if GNOME, both in the Sound Control Panel of the DE's Control Center), and tested if you can hear system sounds?

Have you tried to play Frozen Bubble (installed by default, as Mandrake supported the development of this great little game)? Can you hear the music on the startup screen (which is unrelated to the systems used for playing music via XMMS or the audio component of a video)?

Getting sound working is usually more of a PITA than it seems like it ought to be, but it's also usually less of a PITA than it seems like it's going to be when you find that you can't hear anything :) .

Hope this helps narrow down the problem.

adz 05-29-2004 07:28 AM

Could you show me the output of lspci, lsmod and the contents of /etc/modprobe.conf? I assume Mandy 10 uses the 2.6 kernel series.

DaveThePuzzled 05-29-2004 02:59 PM

Everything is turned up as much as it can be in alsamixer and Kmix and unmuted.

Here is the output from lspci for the soundcard:
00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)

Here is the output of lsmod for the soundcard:
snd-seq-midi 8160 0
snd-emu10k1-synth 6816 0
snd-emux-synth 36320 1 snd-emu10k1-synth
snd-seq-virmidi 6912 1 snd-emux-synth
snd-seq-midi-emul 7776 1 snd-emux-synth
snd-seq-oss 31232 0
snd-seq-midi-event 7552 3 snd-seq-midi,snd-seq-virmidi,snd-seq-oss
snd-seq 51024 8 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-midi-emul,snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 51812 0
snd-mixer-oss 17952 1 snd-pcm-oss
snd-emu10k1 85508 2 snd-emu10k1-synth
snd-rawmidi 23616 3 snd-seq-midi,snd-seq-virmidi,snd-emu10k1
snd-pcm 93156 2 snd-pcm-oss,snd-emu10k1
snd-timer 24484 2 snd-seq,snd-pcm
snd-seq-device 8008 7 snd-seq-midi,snd-emu10k1-synth,snd-emux-synth,snd-seq-oss,snd-seq,snd-emu10k1,snd-rawmidi
snd-ac97-codec 58148 1 snd-emu10k1
snd-page-alloc 11972 2 snd-emu10k1,snd-pcm
snd-util-mem 4448 2 snd-emux-synth,snd-emu10k1
snd-hwdep 8928 2 snd-emux-synth,snd-emu10k1
snd 52484 18 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-emu10k1,snd-rawmidi,snd-pcm,snd-timer,snd-seq-device,snd-ac97-codec,snd-util-mem,snd-hwdep
soundcore 9248 1 snd

Last, here is the output of modprobe.conf:
alias eth0 sundance
alias sound-slot-0 snd-emu10k1
install scsi_hostadapter /sbin/modprobe imm; /sbin/modprobe ppa; /bin/true
install snd-emu10k1 /sbin/modprobe --first-time --ignore-install snd-emu10k1 && { /sbin/modprobe snd-pcm-oss; /bin/true; }
install usb-interface /sbin/modprobe usb-uhci; /bin/true
remove snd-emu10k1 { /sbin/modprobe -r snd-pcm-oss; } ; /sbin/modprobe -r --first-time --ignore-remove snd-emu10k1

This last one on the last line says remove snd-emu10k1. What is that??

DaveThePuzzled 05-29-2004 03:00 PM

Oh, and here is the kernel version I am using
2.6.3-4mdk

bibilit 05-29-2004 04:01 PM

snd-emu10k1 is module ( driver ) for your sound card ( sound blaster live )

and probably trying OSS for sound.

modules should like this :

#ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1

or

#OSS/free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-emu10k1

seek here for your module,as i am not pretty sure of what will work for you.

What MDK control center says about your sound card and the module used ( you probably find OSS or ALSA listed, but have read somewhere MDK and new kernel was using ALSA by default )

bibilit 05-29-2004 04:12 PM

Hi, here is the information i get from the ALSA site :

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

Hope will help, try to copy and paste the above ( as ROOT ) instead of the only line you have in modules.conf.

Save the information > log out,log in > and see if any change appears.

For more information, go to the alsa site and seek for emu-10k1.

DaveThePuzzled 05-30-2004 03:24 AM

Log in as root
 
How do I log in as root?? I know I can go in console and do su and become root there but how would I edit from there and just log in as root??

bibilit 05-30-2004 06:20 AM

well the easiest way, is to log as root at start up, instead of your usual loggin, select root and use root password.

Mandrake sometimes hide the root user by default, so go to kde control center and unhide it !!

Then seek for modules.conf in konqueror and make changes.

Root has all rights, so be careful, i made a lot of changes in modules before getting sound, so think is harmless... and so i read in some books (
" Running Linux " is the one you should get - O'REILLY books - )

Don't forget to save changes, but first go to Alsa site for more information, once again i'm not using the same sound card as you do !!

motub 05-30-2004 06:38 AM

You don't have to log in as root; su to root, then in the root terminal type:
name_of_text_editor /etc/modules.conf &.

The whole purpose of the root terminal created by su is that you can type any command and it will be considered to be coming from root. So you can open programs as root as well, especially text files only editable by root, without logging out and logging back in.

DaveThePuzzled 05-30-2004 01:58 PM

Thank you guys. I will try that and let you know how it goes. I have a friend that has a spare sound card lying around that he will give to me so I can get this working. It is maybe alittle older than the card I have, 'bout couple mos.

DaveThePuzzled 06-01-2004 02:48 AM

I did paste the above ALSA lines in modules.conf but still no sound.

Let me ask you, if I were to upgrade to the official version, could be sound card work better there?? I am asking before I upgrade so I don't have any problems there.

adz 06-01-2004 05:17 AM

I looked around and it seems that Dell soundblasters use a different chipset and are therefore not supported by the emu10k1 driver. Therefore upgrading to the official version would probably do nothing.

motub 06-01-2004 05:28 AM

No, it's really not necessary to upgrade your whole distro just for the sound card, although the Official apparently does fix a lot of bugs in CE, so you might want to upgrade for that reason.

You pasted the lines in modules.conf, but did you then reboot? Or insert the module using modprobe snd_emuk101? You really shouldn't have to do this, as your lsmod shows that the module is loaded and running (as does the fact that the sound apps do play, rather than returning errors).

/etc/modules.conf is only read at boot, so nothing would have changed simply by adding the lines to the file.

Really, really stupid question, but are your speakers plugged into the proper connector, plugged in (if necessary) and turned on?

Second, less stupid, question-- you say that you unmuted alsamixer, but have you rebooted since you did so? In order for alsamixer to retain settings, there is a script/daemon which must run at boot (alsactl). The alsactl store command stores the settings at logoff (or you can do this manually), and the alsactl restore command restores the saved settings on boot (or, again, you can do this manually). Otherwise alsamixer will revert to the only settings it knows, which atm are ... muted.

Mandrake has, in the past, been good about adding the script that runs alsactl during the boot sequence to the default runlevel, but this may be one of the little bugs that got by.

I'm not using MDK atm, so offhand I can't tell you where it lives, but I'd try running alsactl manually (store after changing alsamixer settings, then restore after a reboot) to see if that's even the issue before trying to figure out how to add the script to the boot sequence.

motub 06-01-2004 05:46 AM

Quote:

Originally posted by adz
I looked around and it seems that Dell soundblasters use a different chipset and are therefore not supported by the emu10k1 driver. Therefore upgrading to the official version would probably do nothing.
Yipes, that sucks. Is it possible that another driver supports the Dell chipset? If not (or if it's not worth looking), I guess that original idea of buying an SBLive! wasn't too far off the mark at all.

DaveThePuzzled 06-02-2004 01:48 AM

Well....I know it is a problem with Dell but my computer is a Gateway bought in 2000 and Windows recognizes it as SBLive, not Sound Blaster Live! so I am thinking it might be along the same lines of Dell, as that is why I brought that up, but I am looking to just buy a Sound Blaster Live! RETAIL box to make sure it is the REAL thing. I hate these manufacturers sometimes.

motub 06-02-2004 04:06 AM

Gateway, iirc, uses a similar technique of "re-branding" or "tweaking" hardware so that you can't use standard parts in a Gateway either-- you have to buy upgrades from them for the parts to work. For all we know, the Gateway part might have been bought from Dell and had a new label slapped on it; Dell buys a lot of parts and gets them very cheap for that reason, and what would they do with any extras but sell them to like-minded companies?

I think the easiest and most sensible all around solution is to get a real SB Live (the 5.1s and the Players are still around and quite cheap since they're getting a bit long in the tooth in terms of release cycle. But if you don't need an Audigy, I don't see why they wouldn't be just fine.

DaveThePuzzled 06-02-2004 04:28 AM

Well, as a request from a guru in this forum, I opened the case and pulled the card to look at the biggest chip on the sound card to see if it was a card like Dell uses and Creative made the card, says Creative on it and even has the driver name of EMU10K1 on it, so I think it is authentic, no some forgery that Dell/Gate use...

adz 06-02-2004 07:50 AM

Well some people have reported that messing with the 3D slider and the external amp settings did something for their sb live.

ryan00davis 06-02-2004 11:23 PM

i know for the dell card (which i have) you can get it to work by using the driver from opensound.com. the only downside is that it will only work for so long, because they want you to pay for it. i am also looking into buying a new card, i rather spend a little more money and then a new card then buy the driver, but it is a temporary fix for now. if anyone knows of a free driver for the dell soundblaster card, let me know.

ryan

bibilit 06-03-2004 01:36 AM

Did you try using OSS ??

I talked about ALSA because mdk is using it by default, but OSS can maybe your solution ( i'm using oss, alsa never worked for my sound card !! )

go to mdk control center>and try to change from alsa to oss>log out and in >report any change !

DaveThePuzzled 06-03-2004 03:23 AM

bibilit,

I only gives my a different driver to try. I doesn't tell me if it is OSS or what. It does tell me that snd-emu10k1 that it is using is ALSA and using it by default but it gives me an option for emu10k1 and audigy but neither says that it is OSS. But I will try those others, log out and restart and I will tell you what happens.

adz 06-03-2004 03:39 AM

Well you could do it manually. Remove all the ALSA drivers (all the ones starting with "snd") and do a modprobe emu10k1.

DaveThePuzzled 06-03-2004 04:14 AM

This is the message I get for trying to use OSS...

Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such file or directory)
The sound server will continue, using the null output device.

So I am switching it back to ALSA where I do not have any messages come up.

bibilit 06-03-2004 03:21 PM

Did you have any changes in /etc/modules.conf when switching from alsa to oss ? ( mdk do the changes for you )

I had that message many times, until modules where right, then no more ...but get sound !! ( i'm still smilling ).

Problem with sound in Linux, is that it can be long to fix...

When everything is right, dmesg should return to you that kind of message :

emu101k: card found at 0xf11xxxxx and xxx , IRQ XX

You can try several modules until the problem is solved.

Let me know the following points :

# have you sound when root ?

# can you hear music from your cd player ( with the small wire connected )

# is everything unmuted ( kmix/aumix/alsamixer and volumes 100 % )

# output of lsmod

DaveThePuzzled 06-03-2004 06:32 PM

bibilit,
I went into the console, ran xmms as ROOT and tried to play a song from XMMS and did not hear any sounds or music. I have a dual boot with WinXP and sound works perfectly from audio CD to wave music and mp3's but nothing from Mandy so it cannot be cable connections. I open my computer and have done so twice in the last week to check my card, to see who the manufacturer is, get numbers and things off of the card itself and seems to be authentic. I have even so much as disconnected and reconnected my speakers to make sure they are connected and make sure there is a truer connection. Everything is unmuted, I even made sure aumix was installed and made sure everything was unmuted and turned up to 100% there

As far as MDK doing the changes in /etc/modules.conf, I do the changes, MDK does not do any changes. I even reboot after doing the changes manually and it does nothing.

The following lines are the output of lsmod having to do with sound, that I could tell.

emu10k1 69348 1
soundcore 9248 2 emu10k1
ac97_codec 17804 1 emu10k1

This is the modified changes to /etc/modules.conf that are in effect right now.

alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

Just to make sure you know, I know A LOT about computers and I know how to edit and make changes to things. I am learning more and more about Linux and I love it other than having sooooo much trouble with my sound card that I am ready to just dump my current card and get another card.

ANY help would be greatly appreciated from ANYONE on this issue.

bibilit 06-04-2004 02:20 AM

Thanks for the reply.

I'm not a100 % sure but your modules are strange, as far as i can see the portion you gave to me is for oss, not alsa.

Moreover, if it 's for oss... a part of it is missing !!

Not so long ago i was in the same boat as you are now.

Did you see anything in dmesg telling you the sound card was detected ??

bibilit 06-04-2004 02:30 AM

Just something else, did you try to play a cd with Kscd... you always try with xmms.( try another player )

Also, is xmms set to play with alsa or oss ?? go to options in xmms and try a change.

Last thing, in kde control center you should find something like files association > sound ... is everything associated ??

DaveThePuzzled 06-04-2004 04:02 AM

bibilit,

Yes, the sound card is detected. Here is the lines saying it was detected.
-----------------------------------------------------------------------------------------------------------
Creative EMU10K1 PCI Audio Driver, version 0.20a, 07:21:39 Mar 2 2004
PCI: Found IRQ 10 for device 0000:00:0f.0
emu10k1: EMU10K1 rev 7 model 0x8031 found, IO at 0x10a0-0x10bf, IRQ 10
ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
-----------------------------------------------------------------------------------------------------------

XMMS is using OSS. I did go into KDE Control Center and it was set for ALSA but changed that to OSS and still did nothing. I checked on those associations and not all of them were associated. What does associations have to do with not getting sound??

motub 06-04-2004 04:42 AM

OK, yes, you are using the OSS driver; the OSS driver is emuk101 and the ALSA driver is snd-emuk101.

billibit is right, it certainly looks like part of your /etc/modules.conf is missing, most notably

# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
.

(This is an ALSA setup, and even were you using ALSA, you might not have all of these, as I have a different card from you, but you should have snd-mixer-oss, snd-seq-oss and snd-pcm-oss at least once)

Basically you've loaded the drivers, but no modules to access the sound card via the mixer, sequencer or volume.

Have you run sndconfig to configure the OSS driver?

The thing is, though-- you're using the 2.6 kernel, and if you're using the 2.6 kernel, you should be using ALSA and OSS emulation (OSS is deprecated and moving swiftly towards obsolete).

You should in fact not have any OSS drivers enabled (I don't even have OSS core enabled in my kernel).

Here's my modules.conf (for a VIA 8233 onboard sound chip, under Gentoo, 2.6.5 kernel):

Code:

# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore

##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
##  ALSA portion
alias snd-card-0 snd-via82xx
## alias snd-card-1 snd-ens1371
##  OSS/Free portion
alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##

# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
##  OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=1

### modules-update: end processing /etc/modules.d/alsa

bibilit posted the settings for your card, as listed on the ALSA site, previously.

I would suggest that you switch back to the ALSA driver (snd-emuk101), via either HardDrake or a kernel recompile (it can't use the OSS drivers if they aren't there, after all), run alsaconf if available (if not, install the alsa-utils package; the kernel only has the drivers, not alsa-libs or alsa-utils) and/or edit modules.conf to conform with the ALSA settings given by bibilit, and see what happens.

bibilit 06-04-2004 03:45 PM

You are very close i think.

Card is detected as that is a good point.

Concerning file association, try to associate all related files ( all sound files ) with your player ( wav,...)

You did not say if you get sound with Kscd, probably not, that was the first step for me.

Good luck.

bibilit 06-04-2004 03:56 PM

Hi,

Found that on Oss site, maybe can help :
#
This document is for the SBLive soundcards that come pre-installed
in some Dell machines. Due to differences with the standard SBLive
and Audigy soundcards, we call this the EMU10K1X device.

- The analog front and rear speaker signals will get mixed together (both
signals can be heard from both speakers).

- There is no volume control for PCM rear or PCM Center/LFE channels.

- No S/PDIF mixer support.

Channel allocation:
-------------------
/dev/dsp0 is front playback and recording.
/dev/dsp1 is rear playback.
/dev/dsp2 is center/lfe.

There is one options.cfg setting. emu10k1x_spdif_enable=0 disables S/PDIF
and enables the analog center/lfe output (digital center/LFE output will
always work). emu10k1x_spdif_enable=1 (default) enables S/PDIF and
disables analog center/LFE.
#

If somebody using same or analog device can give you some clues !!

DaveThePuzzled 06-04-2004 05:48 PM

KsCD does not give any sound either....

motub 06-04-2004 06:00 PM

Yes, but that could also be due to the lack of an audio cable (is there a thin cable plugged into your CD-ROM that connects to a pair of pins on your sound card? Such a cable is necessary to hear CD audio direct from the CD-ROM drive generally, though they are becoming obsolete, slowly).

DaveThePuzzled 06-04-2004 07:03 PM

Yes, there is a cable from both CD-ROMs to my cd connections to my sound card because I get sound from a CD-ROM in WinXP. My prob is probably going to be either a module or driver problem. Everything works as far as sound in WinXP, CD, Wave, everything but not in Linux.

DaveThePuzzled 06-04-2004 07:08 PM

I ran alsaconf and it reconfigured and filled in the /etc/modules.conf file and looks good, like...
---------------------------------------------------------------------------------------------------------------------
probeall scsi_hostadapter imm ppa
probeall usb-interface usb-uhci
alias eth0 sundance
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-emu10k1

# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
above snd-emu10k1 snd-pcm-oss
---------------------------------------------------------------------------------------------------------------------

Looks complete like biblit's post on the first page of this thread. I still do not have sound and have gone through and made sure that everything was unmuted and turned up as high as possible.

motub 06-04-2004 07:40 PM

And that your speakers are plugged into the right port, I presume ;) ?

Errors? Or just no sound? Do you have sound as root?

Basically, we're just going to go through the troubleshooting steps again, to see if we have any improvement whatsoever, so please be patient :) . Or... even more patient.

DaveThePuzzled 06-04-2004 07:53 PM

No errors...no sound...not even as root, no sound. Speakers are plugged in correctly because occasionally, I do get a like popping sound, more like a thump....I also went in a did alsactl restore and Master and PCM came up muted so I went into alsamixer, made sure they were unmuted and did alsactl store to make sure it stores that info and I am going to reboot to see if it does anything there.

DaveThePuzzled 06-04-2004 07:54 PM

Believe me, I have a lot of patience but I can tell you that it is wearing thin but I will do my best to have tons more patience

motub 06-04-2004 08:11 PM

OK, the thump thing is good. That's a channel initializing, but kind of incorrectly, so it's not passing the sound through properly, but at least it's there.

Don't worry about your patience; getting sound working under Linux is more often than not much much more trouble than any reasonable or unreasonable person should have to deal with for something so relatively stupid. We all like music, but let's face it, it's not literally essential to the operation of the system as a whole.

OK, back to the issue at hand.

Now I hate to tell you, but your reboot may have done you no good, because alsactl store is really only useful if alsactl restore is run at boot (or shortly thereafter). The loading of ALSA drivers and the restoration of the ALSA mixer levels saved at shutdown is supposed to be handled by a script, which should be somewhere in wherever Mandrake keeps its list of daemons (services, in Windows terms) that are to be run at the various stages of startup.

Off the top of my head I don't know where this is, but I'm almost positive that there is a Runlevel Editor somewhere in the Mandrake Control Center (or in Linuxconf, which is also installed by default iirc).

That's the good news. The bad news is that I don't know what Mandrake calls this script (though it obviously is going to be called something containing "alsa"). On Gentoo, it's called "alsasound". Under Mandrake it might just be called alsa. Anyway, this thing needs to run during the boot process, probably should be set to the boot runlevel or runlevels 3 through 5... it depends on how Mandrake 10 is organized-- I didn't use it long enough to take much note of the differences between 9.2 and 10 in this respect, and I didn't have sound problems, so I didn't look to see where things were stored or what they were named.

So if you don't feel like trawling around through your filetree, you can, as an alternative task (should you choose to accept it), go through the KDE Control Center=>Sound and Multimedia=>Sound I/O, the XMMS preference menu, and the Options menu of any other sound apps you might use and make sure that they are all using the ALSA plugin, or that at least aRTs is using ALSA and not Autodetect, and that the applications are then using the aRTs sound server.

In addition, you can swing by the MDK Control Center=>HardDrake and make sure that it is set to use the ALSA driver for your sound card (to prevent MDK from overwriting your manual settings).

And then do something fun having nothing to do with your PC, just for a change ;) .

DaveThePuzzled 06-04-2004 08:27 PM

I did go into Harddrake and under the config tool for sound, it does provide a few troubleshooting steps and it did mention something about the runlevels and for alsa, 3-5 are on for sound and alsa. But I will shuffle through the filesystem and see what I can find.

DaveThePuzzled 06-04-2004 08:32 PM

I did find the file, it is called alsa under /etc/rc.d/init.d and it is a bunch a C/C++ language which I have no idea how to read it to determine what to do with it.

DaveThePuzzled 06-04-2004 09:07 PM

One last thing then I am giving up for the day.......would it be easier or better to get a Sound Blaster Audigy card.....and another I have been meaning to ask about....you know how Dell was/is using untrue Sound Blaster cards...that they use a different chipset....referred to as EMU10K1X?? I go into alsamixer and it tells me the chipset says Sigmatel STAC9721/23. Does anyone know anything about that chipset...and where in the ALSA website do I find anything about the chipset that Dell uses?? I want to do some definate comparisons so I can see if my card is compatible and would work because I get no errors....it just looks like it is muted....even aRTs shows some response but still no sound. I turn down and then up the volume and I get the thump....I have even tried different jacks on the sound card but still no sound so I think I am in the right jack because of the colors matching...from the speakers to the jack itself.

Anyway...let me know

bibilit 06-05-2004 02:21 AM

Hi,

Audigy card is using the same module as the one you have, you will probably have the same trouble anyway ( except if the problem is coming from the Dell source).

One thing strange about your modules is :

alias char-major-14 soundcore
alias sound-slot-0 snd-emu10k1

should be

alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

Is all i see strange, the other thing is strange to me is that you cannot play any cd - don't need to have sound modules fixed, to have sound from your cd player ... everything was wrong for me except that, and get sound as long as the fine cable to the mother board was connected !!

DaveThePuzzled 06-05-2004 02:39 PM

And I have a cable going from the CD drive to the sound card and it is connected correctly too....so that is strange then....now bibilit, what if I were to make those changes in /etc/modules.conf, would that change anything??


All times are GMT -5. The time now is 03:47 AM.