Re: Creative Labs SB Audigy LS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK, are you trying to run it using oss or alsa (ie what programs are you
running to try out the sound card?) Try for example to do 
aplay /usr/share/sounds/KDE_Beep_Ahem.wav
(or any other .wav file on your system). 
Open alsamixer and push up all of the sliders to max and make sure that
everything is not muted. Exactly what slider corresponds to what feature of
the sound card is a total mess-- it depends on what the sound card
manufacturer calls the feature, and there is no agreement on that. 
So try everything. You can then try turning down stuff to see exactly what is
relevant and what not.


On Thu, 9 Jul 2009, Roland Schmid wrote:

> I turned the soundcard on running alsamixer
> Tried to see what hwinfo --sound says
>
> 11: PCI 504.0: 0401 Multimedia audio controller
>  [Created at pci.310]
>  UDI: /org/freedesktop/Hal/devices/pci_1102_7
>  Unique ID: X3uT.OGyOFMz8HAD
>  Parent ID: 6NW+.k8q0T1+16w3
>  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:05:04.0
>  SysFS BusID: 0000:05:04.0
>  Hardware Class: sound
>  Model: "Creative SB0312 Audigy LS"
>  Vendor: pci 0x1102 "Creative Labs"
>  Device: pci 0x0007 "SB Audigy LS"
>  SubVendor: pci 0x1102 "Creative Labs"
>  SubDevice: pci 0x1002 "SB0312 Audigy LS"
>  Driver: "CA0106"
>  Driver Modules: "snd_ca0106"
>  I/O Ports: 0xe800-0xe81f (rw)
>  IRQ: 21 (22708 events)
>  Module Alias: "pci:v00001102d00000007sv00001102sd00001002bc04sc01i00"
>  Driver Info #0:
>    Driver Status: snd_ca0106 is active
>    Driver Activation Cmd: "modprobe snd_ca0106"
>  Config Status: cfg=new, avail=yes, need=no, active=unknown
>  Attached to: #19 (PCI bridge)
>
> looking for cat /proc/asound/cards
> 0 [CA0106         ]: CA0106 - CA0106
>                      AudigyLS [SB0310] at 0xe800 irq 21
>
> kernel module snd_ca0106 is loaded and active
> Is it possible there are any conflicts relating to the loaded oss
> modules? My user is part of the group audio

What oss modules? There are oss modules which are part of alsa ( snd-*oss*)
and there are oss modules which are native oss which could conflict with alsa
( they do not have snd_ as part of their name)

>
> I was running alsaconf, all finished fine, but no sound
>
> Roland
>
>
>
>
> Am Mittwoch, den 08.07.2009, 14:10 -0700 schrieb Bill Unruh:
>> Turn on the sound card? Ie run say alsamixer and turn up the sound on the PCM
>> slider?
>> Since you tell us nothing whatsoever about what you have done, we can
>> only assume you have tried nothing yet.
>>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user

[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux