t to the headphone output on the LiveDrive. If anyone
> could help out, it would be appreciated.
Run alsamixer and change the volume of the item "Headphone 1".
Both items "Headphone LFE 1" and "Headphone Center 1" must be _muted_.
My soundcard:
-8.1mdk _doesn't_compile_. It
complains about the absence of an intem in a struct. How funny. The
compilation doesn't last 15 seconds.
I'm building vanilla 2.4.19 right now, and things seem running the way
them should be. No preemp, no low-latency, but at least a workin
solved
symbol register_sound_special_R69a88294
/lib/modules/2.4.18-8.1mdk/kernel/sound/acore/snd.o: unresolved symbol
unregister_sound_special_R99c95fa5
modprobe: insmod /lib/modules/2.4.18-8.1mdk/kernel/sound/acore/snd.o failed
modprobe: insmod snd failed
[root@localhost taupter]# cd /lib/modu
Alan Miles wrote:
> All,
>
> I am new to alsa, so please be patient with me - I had to use alsa to get
> here xawtv using an ATI radeon video card.
>
> I have successfully implemented the following on my Slackware 8.1 Linux
> machine, running the 2.4.19 kernel, using the following:
>
> alsa-dri
m not sure at all. This line should be
responsible for loading a SoundFont to my card, but it never worked
(maybe because sfxload is an OSS program and I should run it _after_
loading the OSS compatibility modules) and I'm not exactly sure why.
Taupter
e 2.4.19? And preempt? And about both? Dunno... But what is AlsaBuild?
Plese explain a bit more... ?!
Taupter
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_
Taupter wrote:
> Mark Constable wrote:
>
>> One thing that can happen is that when you compile the modules you
>> may have a completely different set of include files onboard that
>> do not reflect your current kernel. I have no idea how Mandrake does
>> things but
able to load
> them.
Uh... Well, making some symlink magic here... Compiling... Thanks for
remembering me this detail... If I don't complain anymore assume I got
it right. Thanks alot...
Taupter
---
This sf.net email is sponso
/snd.o failed
modprobe: insmod snd failed
Any help will be appreciated.
Thanks in advance
Taupter
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Takashi Iwai wrote:
> ok, that shows the bug.
> please apply the following patch on alsa-driver directory.
> and run "aclocal" then "autoconf" to regenerate configure script.
> this should fix this problem.
Mr. Takashi,
It worked like a breeze!!!
Everything is fine now.
This patch is very usef
Takashi Iwai wrote:
> anyway, please check config.log file on alsa-driver directory.
> you can find there why CONFIG_PCI was not detected.
> (look for a string something like 'checking for PCI devices' and see
> the messages below it)
The erro was (line 41)
configure:1502: checking for PCI supp
Takashi Iwai wrote:
> ok. do you have then /usr/src/linux/include/linux/autoconf.h?
Yes, I do have. 3149 lines long
> and CONFIG_PCI and CONFIG_ISA are defined in the file?
#define CONFIG_PCI 1
#undef CONFIG_PCI_GOBIOS
#undef CONFIG_PCI_GODIRECT
#define CONFIG_PCI_GOANY 1
#define CONFIG_PCI_
Takashi Iwai wrote:
> CONFIG_SND_PCI is obsolete. it is now renamed to CONFIG_PCI as well
Nice. So I should simply alter the Makefile.conf to CONFIG_PCI=y ?
>>What should I create, alter, or such to have a working alsa-driver0.9.0rc2?
> i guess that your kernel tree is not located at /usr/src/
Taupter wrote:
> It sems CONFIG_SND_PCI doesn't exists al all in Makefile.conf. The one
> that resembles it more is CONFIG_PCI (that is set to 'n' the same way
> CONFIG_ISA is, but the ISA modules are compiled anyway).
As a complementary information I send th
Johan Gill wrote:
> The problem is that CONFIG_SND_PCI is not set to y in Makefile.conf. I
> should have reported this bug somewhere else than on this list when I
> encountered it in rc1 it seems.
It sems CONFIG_SND_PCI doesn't exists al all in Makefile.conf. The one
that resembles it more is
Hello
I was trying to compile alsa-driver0.9.0rc2, and it didn't compile or
install PCI modules.
Machine configuration:
PentiumII 350MHz /384MB RAM
Sound Blaster Live! Platinum 5.1 (emu10k1)
Mandrake linux 8.2 with kernel 2.4.18-6mdk with devfs support
already working alsa-driver 0.9.0rc1 (th
Takashi Iwai wrote:
> Taupter wrote:
>>Excuse me for ranting, and many thanks to Takashi Iwai and the ALSA
>>developers for their hard work...
> Sorry for the very late reply.
> I put a workaround code into cvs to avoid triggering the note-on/off
> at the same time.
0 XT-PIC cascade
4:2500241 XT-PIC serial
5: 57461 XT-PIC em8300
8:1068675 XT-PIC rtc
10: 62 XT-PIC aic7xxx
11: 186813 XT-PIC EMU10K1
12: 675472 XT-PIC PS/2 Mouse
14: 3723301
Paul Davis wrote:
>>What I found quite astounding is how brave pmidi keeps its timing: It
>>uses no extra threads, no RTC, no suid-root privileges (and my kernel
>>doesn't have LL or PE patches built in right now), but still plays back
>>a 10-track MIDI file very time-stable even if I do somethin
Jeremiah Benham wrote:
> You definately need alsa. Alsa is much lower latency. Alsa works fine for
> my Sblive!
>>>http://www.zip.com.au/~akpm/linux/schedlat.html#downloads installed and
>>>enabled, and I have yet to see an ALSA MIDI player that doesn't eat notes
>>>when playing using EMU10K s
Frank Neumann wrote:
> Honestly, I believe I never tried building MusE without ALSA, and I
> believe by now it's impossible to build OSS-only versions of MusE. ALSA
> is the way to go anyway :-}.
If that ALSA thing only worked... I have a SBLive! Platinum 5.1, using
ALSA 0.9.10a drivers, the l
Juan Linietsky wrote:
> Hello, I have a sblive value and I've been trying to use the sequencer. I've tried
>the latest relases and in all of them i've found the following problems:
>
> -Noise in the synth: With many soundfont patches, using the synth, the card starts
>doing an horrible crackin
Patrice Garbe wrote:
> Hello,
>
> I installed the ALSA drivers correctly and I have sound. However I have KDE
> 2.2.1 and ALSA does not appear in the Sound Server selection list
> ("Autodetect" is currently selected). Why does KDE not detect It ? I swear
> that I ran the script "snddevices".
Takashi Iwai wrote:
> At Fri, 19 Oct 2001 05:03:10 -0200,
> Taupter wrote:
>
>>Hello
>>
>>
>>I have properly configured ALSA-0.9.0beta8a drivers for SBLive Platinum
>>5.1 (Emu10K1) on my system, and I can load sound fonts and play MIDI
>>files, bu
Hello
I have properly configured ALSA-0.9.0beta8a drivers for SBLive Platinum
5.1 (Emu10K1) on my system, and I can load sound fonts and play MIDI
files, but it seems some voices are missing.
When I play a MIDI file (using pmidi 1.5.4), some voices simply don't
play, cutting at a time some
Frank Barknecht wrote:
> Taupter hat gesagt: // Taupter wrote:
>>I'm trying to play MIDI files with the internal synth of my soundcard
>>using alsa 0.9.0b7, but I simply can't. I can't even use sfxload
> You forgot to include the emu-synth stuff in you modu
Oscar Ya#ez Suarez wrote:
> Hi everyone,
>
> In trying to setup the internal MIDI synth of my SBLive! I
> realized from the list postings that I needed to load a
> soundfont. Many mails refer to the file "8mbgmsfx.sf2" as the
> one to download with sfxload. Where do I find this file? Is it
> pub
> Do you usually try MIDI as soon as you use sfxload? If you wait awhile the
> soundfont will unload, unless you add sfxload to modules.conf. BTW, also are
> you using the 8mb Creative sf2 file (the one that comes with the Live! card),
> or an older AWE-series font? Those older fonts do not w
Hello
I'm trying to play MIDI files with the internal synth of my soundcard
using alsa 0.9.0b7, but I simply can't. I can't even use sfxload to set
sounf fonts. Everything else works nicely. I'm looking for your help to
set up this thing.
This is my ALSA-related modules.conf (made with the
29 matches
Mail list logo
