On Saturday 10 July 2004 08:54 am, Christoph Sticksel wrote:
> | open("/dev/snd/controlC0", O_RDONLY)= -1 ENODEV (No such device)
> | open("/dev/aloadC0", O_RDONLY) = -1 ENODEV (No such device)
> | open("/dev/snd/controlC0", O_RDWR) = -1 ENODEV (No such device)
> | open("/dev/snd
Silvan wrote:
> On Tuesday 06 July 2004 11:00 am, Christoph Sticksel wrote:
>> What is the preferred way to load modules? modconf or
>> /etc/also/modultils/0.5? Does is matter that /etc/alsa/0.9 is empty?
>
> I don't know what the "preferred" way is, I don't suppose. I always use
> modconf, but th
On Tuesday 06 July 2004 11:00 am, Christoph Sticksel wrote:
> That's what I thought. This is what lsmod tells me about loaded modules
> | snd_ac97_codec 70020 1 snd_ymfpci
[etc...]
That looks fine off-hand, though I don't know exactly what I should see there
for your hardware. I don't
Silvan wrote:
> On Sunday 04 July 2004 01:14 pm, Christoph Sticksel wrote:
>
>> Everything sound-related is loaded and lsmod shows a whole bunch of snd_*
>> modules, snd, soundcore, opl3sa2 and ad1848 are there as well.
>
>> If I do a "modprobe -r opl3sa2" and reload it with "modprobe opl3sa2" I
On Sunday 04 July 2004 01:14 pm, Christoph Sticksel wrote:
> Everything sound-related is loaded and lsmod shows a whole bunch of snd_*
> modules, snd, soundcore, opl3sa2 and ad1848 are there as well.
> If I do a "modprobe -r opl3sa2" and reload it with "modprobe opl3sa2" I see
I'm not familiar w
5 matches
Mail list logo