Dzwiek SBAudigy

Gdy jakieś urządzenie nie chce w Slackware działać...

Moderatorzy: Moderatorzy, Administratorzy

Rafals
Użytkownik
Posty: 5
Rejestracja: 2006-10-12, 08:55

Dzwiek SBAudigy

Post autor: Rafals » 2006-10-12, 10:40

Witam na forum.

Mam problem z odtwarzaniem muzyki.

Zainstalowalem sobie slakware 10.0.
Sprzet:
Plyta glowna: ASRock K7VT4A Pro (5 PCI, 1 AGP, 2 DDR DIMM, Audio, LAN)
Mikroukład płyty głównej: VIA VT8377A Apollo KT400A
Karta dźwiękowa: Creative SB0090 Audigy Player Sound Card
Skompilowalem i zainstalowalem jadro 2.6.18. System sie uruchamia.
Opcje kompilacji jadra:
<*> Sound Card Support
Advanced Linux Sound Architecture --->
<*> Advanced Linux Sound Architecture
<*> Sequencer support
< > Sequencer dummy client
<*> OSS Mixer API
<*> OSS PCM (digital audio) API
[ ] OSS PCM (digital audio) API - Include plugin system
[*] OSS Sequencer API
<*> RTC Timer support
[ ] Use RTC as default sequencer timer
[ ] Dynamic device file minor numbers
[ ] Support old ALSA API
[ ] Verbose procfs contents
[ ] Verbose printk
[ ] Debug
Generic devices --->
PCI devices --->
<*> Emu10k1 (SB Live!, Audigy, E-mu APS)
X-y: KDE 3.2.3

Sprzet jest poprawnie wykrywany:
root@rafal:/home/rafal# lspci -v > pci.txt
00:0a.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Subsystem: Creative Labs SB0090 Audigy Player/OEM
Flags: bus master, medium devsel, latency 32, IRQ 3
I/O ports at d000
Capabilities: [dc] Power Management version 2

00:0a.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 03)
Subsystem: Creative Labs SB Audigy MIDI/Game Port
Flags: bus master, medium devsel, latency 32
I/O ports at ec00
Capabilities: [dc] Power Management version 2

00:0a.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at dfffb800 (32-bit, non-prefetchable)
Memory at dfff4000 (32-bit, non-prefetchable)
Capabilities: [44] Power Management version 2


ustawienia w KDE :

Dzwiek i Multimedia->System Dzwiekowy->sprzet
*wybor i konfiguracja karty dzwiekowej jest
Rozpoznaj Automatycznie lub
Advanced Linux Sound Architecture
*Wybierz urzadzenie Midi - AUDIGY1[SB0090]


Gdy uruchamiam alsaconf (wersja 1.0.5)
pojawia sie komunikat:

No supported PnP or PCI card found.


Gdy uruchamiam alsamixer 1.0.5 to pojawiaja mi sie sporo tych suwakow,ale moge je co najwyzej dostroic tak aby bardzo slaby dzwiek byl slyszany w wielkim szumie.Do testowania dzwiekow uzywalem XMMS,Juk i Testuj dzwiek z centrum sterowania.

Doczytalem sie na forum,ze problem moze byc z wersja sterownikow ALSA.Na stronie Alsa jest opis instalacji sterownikow,ale ja mam je przeciez wkompilowne w jadro.Chcialbym sie dowiedziec jakie mam
mozliwosci czy moge w jakis sposob wkompilowac te sterowniki w jadro,zeby to dzialalo,czy musze po prostu odznaczyc te wszystkie opcje dotyczace kompilacji dzwieku w jadrze i zainstalowac te sterowniki recznie?Wolalbym je miec wkompilowane w jadro.

Zgory dzieki za odpowiedz.

RafalS

Awatar użytkownika
darvark
Użytkownik
Posty: 164
Rejestracja: 2005-12-17, 11:45
Lokalizacja: Kielce
Kontakt:

Re: Dzwiek SBAudigy

Post autor: darvark » 2006-10-12, 10:58

probuj przesiasc sie na sterowniki z projektu alsy, wyrzucajac z jajka cala alse i oss. moze pomoze, przynajmnije u mnie pomoglo na SB audigy SE

Awatar użytkownika
kazalot
Użytkownik
Posty: 1259
Rejestracja: 2006-04-05, 10:48

Re: Dzwiek SBAudigy

Post autor: kazalot » 2006-10-12, 11:09

alsaconf wyszukuje ci moduly do karty ktora masz jezeli wkompilowales ja w kernel to niby co mialby ci alsaconf znalezc? ;) jezeli masz bardzo cicho to pewnie masz jakies external amplifier albo cos takiego zaznaczone.
do testowania dzwieku pod alsa zawsze uzywaj narzedzia alsy (aplay) bo tylko wtedy dowiesz sie jaki moze byc ew blad, xmms czy inny program jedyne co ci powie to ze "masz zle skonfigurowana karte".

Awatar użytkownika
Corvin
Administrator
Posty: 1143
Rejestracja: 2004-05-21, 15:04
Lokalizacja: Gdańsk

Re: Dzwiek SBAudigy

Post autor: Corvin » 2006-10-12, 12:43

w tak starej lsie moze jeszcze nie być obsługiwana ... Zainstaluj 11
"Spróbuj zapalić maleńką świeczkę zamiast przeklinać ciemność."
Konfucjusz

tomekk
Użytkownik
Posty: 308
Rejestracja: 2004-11-14, 18:21
Lokalizacja: Oświęcim
Kontakt:

Re: Dzwiek SBAudigy

Post autor: tomekk » 2006-10-12, 12:50

Kod: Zaznacz cały

01:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
Audigy 1 [SB0090]
tez mam cos takiego, nigdy nie mialem problemow, skompiluj sterownik EMU10k* w jajku jako modulek, wywal domyslne alsa-utils,lib,oss, nastepnie zaciagnij sobie ze stronki alsa-project.org alsa-utils,lib,oss, kompilacje zacznij od lib, potem oss utils, przy takiej konfiguracji musi isc od strzala, sadze ze cos zle w jadrze zaznaczyles ;-)

Rafals
Użytkownik
Posty: 5
Rejestracja: 2006-10-12, 08:55

Re: Dzwiek SBAudigy

Post autor: Rafals » 2006-10-12, 20:22

Dzieki wielkie wszystkim za pomoc i zainteresowanie.

Wywalilem sterowniki z jadra i zainstalowalem paczki,o ktorych mowil tomekk ze zrodel(w wersji 1.0.11 ).I po uruchomieniu alsaconf wykrylo ladnie karte i dzwiek mometalnie stal sie czysciutki. prawie nic nie musialem ustawiac w alsamixer.

Obecna konfiguracja jadra;
<*> Sound card support
Advanced Linux Sound Architecture --->
<M> Advanced Linux Sound Architecture
PCI devices --->
<M> Emu10k1 (SB Live!, Audigy, E-mu APS)
Z tym,ze po kazdym uruchomieniu kompa musze uruchamiac alsaconf,aby dwiek dzialal prawidlowo.
alsactl store
nie pomaga.Pewnie trzeba cos gdzies wpisac w jakims pliku konfiguracyjnym.Ale na razie nie wiem gdzie.Szukam w googlu.Gdyby ktos wiedzial,to z gory dzieki.

RafalS

tomekk
Użytkownik
Posty: 308
Rejestracja: 2004-11-14, 18:21
Lokalizacja: Oświęcim
Kontakt:

Re: Dzwiek SBAudigy

Post autor: tomekk » 2006-10-12, 22:53

ja mam banalny skrypt 'rc.alsa' w katalogu 'etc/rc.d/', jesli masz to sobie wyedytuj, jak nie to zrob nowy i wstaw cos takiego:

Kod: Zaznacz cały

#!/bin/sh
echo "ALSA restore mixer settings..."
/usr/sbin/alsactl restore
potem 'chmod +x rc.alsa' i to tyle, przy kazdym starcie beda sie ustawienia przywracac....

a, jeszcze jedno, przed wykonaniem tych czynnosci odpal sobie 'alsamixer', ustaw suwaki jak chcesz i wpisz 'alsactl store', chodzi o zapamietanie domyslnych ustawien, to musi zadzialac ;)

sprawdz czy tez jakies mixery z nakladek nie laduja same swoich ustawien ;)

pozdrawiam
Ostatnio zmieniony 2006-10-12, 22:54 przez tomekk, łącznie zmieniany 1 raz.

Rafals
Użytkownik
Posty: 5
Rejestracja: 2006-10-12, 08:55

Re: Dzwiek SBAudigy

Post autor: Rafals » 2006-10-13, 10:34

Niestety nie pomoglododanie tych dwoch linijek do rc.alsa.Moj plik rc.alsa:
#!/bin/sh
# Load the mixer settings and OSS compatibility for ALSA.
# (the Advanced Linux Sound Architecture)

# A function to load the ALSA mixer settings:
load_alsa_mixer() {
if [ -r /etc/asound.state ]; then
echo "Loading ALSA mixer settings: /usr/sbin/alsactl restore"
/usr/sbin/alsactl restore
else
echo "ALSA warning: No mixer settings found in /etc/asound.state."
echo " Sound may be muted. Use 'alsamixer' to unmute your sound card,"
echo " and then 'alsactl store' to save the default ALSA mixer settings"
echo " to be loaded at boot."
fi
}

# A function to load the ALSA OSS compat modules:
load_alsa_oss_modules() {
if ! cat /proc/modules | grep -w snd-pcm-oss 1> /dev/null 2> /dev/null ; then
echo "Loading OSS compatibility modules for ALSA."
modprobe snd-pcm-oss
modprobe snd-mixer-oss
fi
}

# If hotplug or something else has loaded the ALSA modules, then
# simply load the mixer settings and make sure the OSS compat
# modules are loaded:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
else
# If there are ALSA modules defined in /etc/modules.conf, but
# ALSA is not yet loaded, then load the modules now:
DRIVERS=`modprobe -c | grep -E "^[[:space:]]*alias[[:space:]]+snd-card-[[:digit:]]" | awk '{ print $3 }'`
if [ ! "$DRIVERS" = "" ]; then
echo "Loading ALSA kernel modules."
for module in $DRIVERS; do
modprobe $module
done
fi
# If ALSA is now up, then load the mixer settings and OSS modules:
if [ -d /proc/asound ]; then
load_alsa_mixer
load_alsa_oss_modules
fi
fi

echo "ALSA restore mixer settings..."
/usr/sbin/alsactl restore
Dodanie tych dwoch lini na koncu nie pomoglo.Ale cos innego mi sie rzucilo w oczy.
Podczas startu systemu mam:
Loading ALSA mixer settings ; /usr/sbin/alsactl restore
Loading OSS compatibility module for ALSA
FATAL: Module snd_pcm_oss not found
FATAL: Module snd_mixer_oss not found
ALSA restore mixer settings #ta linia pojawia sie wtedy gdy dodam te dwie linijki rzecz jasna
lsmod to potwierdza.
root@rafal:/home/rafal# lsmod
Module Size Used by
snd_emu10k1 120704 3
snd_rawmidi 17664 1 snd_emu10k1
snd_ac97_codec 93088 1 snd_emu10k1
snd_ac97_bus 1984 1 snd_ac97_codec
snd_pcm 63752 3 snd_emu10k1,snd_ac97_codec
snd_timer 19908 2 snd_emu10k1,snd_pcm
snd_page_alloc 8200 2 snd_emu10k1,snd_pcm
snd_util_mem 3584 1 snd_emu10k1
snd_hwdep 6788 1 snd_emu10k1
snd 39672 11 snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
A jak uruchomie alsaconf i wybiore swoja karte to slysze wypasiony dzwiek.Lista modulow jest identyczna przed skonfigurowanie alsaconf i po.Czy ktos wie co on robi?I jak to zrobic aby sam sie konfigurowal przy starcie?
Spojrzalem do katalogu /sys/modules i tam faktycznie tych modulow nie ma.Ladowanie modulow
tez nic nie daje,bo ich nie znajduje.
root@rafal:/home/rafal# modprobe snd_pcm_oss
FATAL: Module snd_pcm_oss not found.
Wiec do czego sa te moduly?Dlaczego mimo wszystko bez nich dzwiek dziala?

zamieszcze logi z kompilacji alsa-oss:
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11# ./configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether ln -s works... yes
checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld...
yes
checking for /usr/i486-slackware-linux/bin/ld option to reload object f
iles... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supp
orts shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld...
yes
checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supp
orts shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supp orts shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
appending configuration tag "F77" to libtool
checking for aoss... yes
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread
checking for libasound headers version >= 0.9.0... found.
checking for snd_ctl_open in -lasound... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating alsa/Makefile
config.status: creating alsa/aoss
config.status: creating alsa/aoss.old
config.status: creating oss-redir/Makefile
config.status: creating test/Makefile
config.status: creating alsa/testaoss
config.status: creating test/testaoss
config.status: executing depfiles commands
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11#
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11# make
Making all in alsa
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-pcm.lo -MD -MP -MF ".deps/libalsatoss_la-pcm.Tpo" -c -o libalsatoss_la-pcm.lo `test -f 'pcm.c' || echo './'`pcm.c; \
then mv -f ".deps/libalsatoss_la-pcm.Tpo" ".deps/libalsatoss_la-pcm.Plo"; else rm -f ".deps/libalsatoss_la-pcm.Tpo"; exit 1; fi
mkdir .libs
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-pcm.lo -MD -MP -MF .deps/libalsatoss_la-pcm.Tpo -c pcm.c -fPIC -DPIC -o .libs/libalsatoss_la-pcm.o
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-pcm.lo -MD -MP -MF .deps/libalsatoss_la-pcm.Tpo -c pcm.c -o libalsatoss_la-pcm.o >/dev/null 2>&1
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-mixer.lo -MD -MP -MF ".deps/libalsatoss_la-mixer.Tpo" -c -o libalsatoss_la-mixer.lo `test -f 'mixer.c' || echo './'`mixer.c; \
then mv -f ".deps/libalsatoss_la-mixer.Tpo" ".deps/libalsatoss_la-mixer.Plo"; else rm -f ".deps/libalsatoss_la-mixer.Tpo"; exit 1; fi
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-mixer.lo -MD -MP -MF .deps/libalsatoss_la-mixer.Tpo -c mixer.c -fPIC -DPIC -o .libs/libalsatoss_la-mixer.o
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT libalsatoss_la-mixer.lo -MD -MP -MF .deps/libalsatoss_la-mixer.Tpo -c mixer.c -o libalsatoss_la-mixer.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o libalsatoss.la -rpath /usr/lib -version-info 0:0:0 libalsatoss_la-pcm.lo libalsatoss_la-mixer.lo -lasound -lm -ldl -lpthread
gcc -shared .libs/libalsatoss_la-pcm.o .libs/libalsatoss_la-mixer.o /usr/lib/libasound.so -lm -ldl -lpthread -Wl,-soname -Wl,libalsatoss.so.0 -o .libs/libalsatoss.so.0.0.0
(cd .libs && rm -f libalsatoss.so.0 && ln -s libalsatoss.so.0.0.0 libalsatoss.so.0)
(cd .libs && rm -f libalsatoss.so && ln -s libalsatoss.so.0.0.0 libalsatoss.so)
ar cru .libs/libalsatoss.a libalsatoss_la-pcm.o libalsatoss_la-mixer.o
ranlib .libs/libalsatoss.a
creating libalsatoss.la
(cd .libs && rm -f libalsatoss.la && ln -s ../libalsatoss.la libalsatoss.la)
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT alsa-oss.lo -MD -MP -MF ".deps/alsa-oss.Tpo" -c -o alsa-oss.lo alsa-oss.c; \
then mv -f ".deps/alsa-oss.Tpo" ".deps/alsa-oss.Plo"; else rm -f ".deps/alsa-oss.Tpo"; exit 1; fi
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT alsa-oss.lo -MD -MP -MF .deps/alsa-oss.Tpo -c alsa-oss.c -fPIC -DPIC -o .libs/alsa-oss.o
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT alsa-oss.lo -MD -MP -MF .deps/alsa-oss.Tpo -c alsa-oss.c -o alsa-oss.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o libaoss.la -rpath /usr/lib -version-info 0:0:0 alsa-oss.lo libalsatoss.la
libtool: link: warning: `/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libasound.la' seems to be moved
gcc -shared .libs/alsa-oss.o -Wl,--rpath -Wl,/usr/src/ALSA/alsa-oss-1.0.11/alsa/.libs -L/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../ ./.libs/libalsatoss.so -Wl,-soname -Wl,libaoss.so.0 -o .libs/libaoss.so.0.0.0
(cd .libs && rm -f libaoss.so.0 && ln -s libaoss.so.0.0.0 libaoss.so.0)
(cd .libs && rm -f libaoss.so && ln -s libaoss.so.0.0.0 libaoss.so)
ar cru .libs/libaoss.a alsa-oss.o
ranlib .libs/libaoss.a
creating libaoss.la
(cd .libs && rm -f libaoss.la && ln -s ../libaoss.la libaoss.la)
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
Making all in oss-redir
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT oss-redir.lo -MD -MP -MF ".deps/oss-redir.Tpo" -c -o oss-redir.lo oss-redir.c; \
then mv -f ".deps/oss-redir.Tpo" ".deps/oss-redir.Plo"; else rm -f ".deps/oss-redir.Tpo"; exit 1; fi
mkdir .libs
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT oss-redir.lo -MD -MP -MF .deps/oss-redir.Tpo -c oss-redir.c -fPIC -DPIC -o .libs/oss-redir.o
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"alsa-oss\" -DVERSION=\"1.0.11\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBASOUND=1 -I. -I. -g -O2 -MT oss-redir.lo -MD -MP -MF .deps/oss-redir.Tpo -c oss-redir.c -o oss-redir.o >/dev/null 2>&1
/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -o libossredir.la -rpath /usr/lib -static oss-redir.lo -ldl
ar cru .libs/libossredir.a oss-redir.o
ranlib .libs/libossredir.a
creating libossredir.la
(cd .libs && rm -f libossredir.la && ln -s ../libossredir.la libossredir.la)
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
Making all in test
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[1]: Nie nic do roboty w `all'.
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11'
make[1]: Nie nic do roboty w `all-am'.
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11'
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11#
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11# make install
Making install in alsa
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
make[2]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
test -z "/usr/bin" || mkdir -p -- "/usr/bin"
/usr/bin/ginstall -c 'aoss' '/usr/bin/aoss'
test -z "/usr/lib" || mkdir -p -- "/usr/lib"
/bin/sh ../libtool --mode=install /usr/bin/ginstall -c 'libalsatoss.la' '/usr/lib/libalsatoss.la'
/usr/bin/ginstall -c .libs/libalsatoss.so.0.0.0 /usr/lib/libalsatoss.so.0.0.0
(cd /usr/lib && rm -f libalsatoss.so.0 && ln -s libalsatoss.so.0.0.0 libalsatoss.so.0)
(cd /usr/lib && rm -f libalsatoss.so && ln -s libalsatoss.so.0.0.0 libalsatoss.so)
/usr/bin/ginstall -c .libs/libalsatoss.lai /usr/lib/libalsatoss.la
/usr/bin/ginstall -c .libs/libalsatoss.a /usr/lib/libalsatoss.a
ranlib /usr/lib/libalsatoss.a
chmod 644 /usr/lib/libalsatoss.a
PATH="$PATH:/sbin" ldconfig -n /usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/bin/sh ../libtool --mode=install /usr/bin/ginstall -c 'libaoss.la' '/usr/lib/libaoss.la'
libtool: install: warning: relinking `libaoss.la'
(cd /usr/src/ALSA/alsa-oss-1.0.11/alsa; /bin/sh ../libtool --mode=relink gcc -g -O2 -o libaoss.la -rpath /usr/lib -version-info 0:0:0 alsa-oss.lo libalsatoss.la )
libtool: link: warning: `/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libasound.la' seems to be moved
gcc -shared .libs/alsa-oss.o -L/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../../ -L/usr/lib -lalsatoss -Wl,-soname -Wl,libaoss.so.0 -o .libs/libaoss.so.0.0.0
/usr/bin/ginstall -c .libs/libaoss.so.0.0.0T /usr/lib/libaoss.so.0.0.0
(cd /usr/lib && rm -f libaoss.so.0 && ln -s libaoss.so.0.0.0 libaoss.so.0)
(cd /usr/lib && rm -f libaoss.so && ln -s libaoss.so.0.0.0 libaoss.so)
/usr/bin/ginstall -c .libs/libaoss.lai /usr/lib/libaoss.la
/usr/bin/ginstall -c .libs/libaoss.a /usr/lib/libaoss.a
ranlib /usr/lib/libaoss.a
chmod 644 /usr/lib/libaoss.a
PATH="$PATH:/sbin" ldconfig -n /usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
test -z "/usr/man/man1" || mkdir -p -- "/usr/man/man1"
/usr/bin/ginstall -c -m 644 './aoss.1' '/usr/man/man1/aoss.1'
make[2]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/alsa'
Making install in oss-redir
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
make[2]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
test -z "/usr/lib" || mkdir -p -- "/usr/lib"
/bin/sh ../libtool --mode=install /usr/bin/ginstall -c 'libossredir.la' '/usr/lib/libossredir.la'
/usr/bin/ginstall -c .libs/libossredir.lai /usr/lib/libossredir.la
/usr/bin/ginstall -c .libs/libossredir.a /usr/lib/libossredir.a
ranlib /usr/lib/libossredir.a
chmod 644 /usr/lib/libossredir.a
PATH="$PATH:/sbin" ldconfig -n /usr/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
test -z "/usr/include" || mkdir -p -- "/usr/include"
/usr/bin/ginstall -c -m 644 'oss-redir.h' '/usr/include/oss-redir.h'
make[2]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/oss-redir'
Making install in test
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[2]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[2]: Nie nic do roboty w `install-exec-am'.
make[2]: Nie nic do roboty w `install-data-am'.
make[2]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11/test'
make[1]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11'
make[2]: Entering directory `/usr/src/ALSA/alsa-oss-1.0.11'
make[2]: Nie nic do roboty w `install-exec-am'.
make[2]: Nie nic do roboty w `install-data-am'.
make[2]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11'
make[1]: Leaving directory `/usr/src/ALSA/alsa-oss-1.0.11'
root@rafal:/usr/src/ALSA/alsa-oss-1.0.11#
Bledow nie ma,a modolow jak nie bylo tak nie ma.:(
Sorry,ze jestem meczliwy,ale dopiero od kilku dni mam slacka.

Pozdrawiam.

tomekk
Użytkownik
Posty: 308
Rejestracja: 2004-11-14, 18:21
Lokalizacja: Oświęcim
Kontakt:

Re: Dzwiek SBAudigy

Post autor: tomekk » 2006-10-13, 12:01

wywal caly rc.alsa, zrob nowy, dodaj do niego tylko to co ja Ci podalem, zrob chmod +x rc.alsa i test ;] btw oss, to jest juz troche stary system, polecam w jajku odznaczyc opcje 'Open Sound System ---> < > Open Sound System (DEPRECATED)', a nastepnie w ' Advanced Linux Sound Architecture --->' zaznaczyc:

Kod: Zaznacz cały

 <*>   OSS Mixer API
 <*>   OSS PCM (digital audio) API
  [*]     OSS PCM (digital audio) API - Include plugin system
po takim zabiegu powinno byc OK, pamietaj skompiluj to w jadrze, popraw ten rc.alsa, tak jak pisalem wywal caly plik i stworz nowy, nie dodawaj nieczego do niego..a, jeszcze sprawdz czy napewno masz 'alsactl' w '/usr/sbin', (komenda which alsactl), czasem jakby bylo gdzies indziej to sobie tylko popraw wpis ;)

Rafals
Użytkownik
Posty: 5
Rejestracja: 2006-10-12, 08:55

Re: Dzwiek SBAudigy

Post autor: Rafals » 2006-10-17, 10:31

Zrobilem tak jak pisales,ale nie w tym jest problem.Dodalem linie :
alsactl restore
do pliku rc.M i po restarcie gdy jestem w konsoli,konfiguracja jest zachowana.Slysze pekny dzwiek.Ale gdy uruchamiam x-y (startx) Gdy kade pokazuje wykrywanie urzadzen peryferyjnych to slysze male pykniecie i konfiguracja idzie w diably.Krotko mowiac potrzebuje albo nazwe pliku,ktory uruchamia sie przy starcie po inicjalizacji urzadzen peryferyjnych,przez kde,wtedy tam dodam tez ten wpis,albo zrobic tak co by kde nie zmienialo tej konfiguracji.

tomekk
Użytkownik
Posty: 308
Rejestracja: 2004-11-14, 18:21
Lokalizacja: Oświęcim
Kontakt:

Re: Dzwiek SBAudigy

Post autor: tomekk » 2006-10-17, 13:54

moze to byc przez server arts, wylacz go najlpiej, przy tej karcie jest zbedny, dwa .. sprawdz czy 'kmix' nie laduje swoich ustawien, najlepiej tez go wywal z autostartu

Rafals
Użytkownik
Posty: 5
Rejestracja: 2006-10-12, 08:55

Re: Dzwiek SBAudigy

Post autor: Rafals » 2006-10-17, 15:01

Wielkie dzieki tomekk,wreszcie dziala tak jak powinno.

Wystarczylo w CentrumSterowania->Dzwiek i Multimedia->Mikser.Odznaczyc opcje uruchom przy logowaniu.Twoj post mnie naprowadzil.

Pozdrawiam.

ODPOWIEDZ