At 21 Mar 2003 05:50:47 -0800, Mark Knecht wrote: > > Hi, > The --help option says that I can get a log file from alsaconf using > the -L option. If I look in /tmp while alsaconf is running, I see some > files, but when alsaconf has finished, the files are gone...
yep, they are temporary working directories. > > [EMAIL PROTECTED] mark]$ ls /tmp > alsaconf.3nMgvm alsaconf.txNTFm ksocket-mark orbit-mark > ssh-XX7Jn9me > alsaconf.Ef6KCm kde-mark mcop-mark ssh-XX1CS1IB > ssh-XXIbrHpS > [EMAIL PROTECTED] mark]$ ls /tmp > kde-mark ksocket-mark mcop-mark orbit-mark ssh-XX1CS1IB > ssh-XX7Jn9me ssh-XXIbrHpS > [EMAIL PROTECTED] mark]$ > > Is this file possibly put somewhere else? I'm trying to figure out why > alsaconf is complaining about this card. /tmp/alsaconf.log is created only when the legacy cards are probed. it's for a deubgging purpose only... > Loading driver.. > Starting sound driver snd-hdsp > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: Hint: > insmod errors can be caused by incorrect module parameters, including invalid IO or > IRQ parameters. > You may find more information in syslog or the output from dmesg > init_module: No such device > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o failed > /lib/modules/2.4.20-1.12.ll.acpi/kernel/drivers/sound/pci/rme9652/snd-hdsp.o: insmod > snd-hdsp failed do you already have another sound module? alsaconf can configure only the first device (i.e. index=0). configuring more than one card is not supported yet. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
