From: Harald Dunkel <harri@synopsys.COM>
To: linux-kernel@vger.kernel.org
Subject: Alsa 0.9beta8a with 2.4.{12,13} ?
Date: Wed, 24 Oct 2001 23:15:59 +0200 [thread overview]
Message-ID: <3BD72F8F.43E21E66@Synopsys.COM> (raw)
Hi folks,
Up to kernel version 2.4.12 the Alsa 0.9beta8a version was working
for my needs. Sometimes the startup script claimed that there is
no soundcard (via686a), but after one or two restarts of this
script the onboard chip was detected.
With 2.4.13 I had no such luck:
{root@bilbo:harri 937} /etc/init.d/alsasound restart
Shutting down sound driver: done
Starting sound driver: snd-card-via686a Warning: loading /lib/modules/2.4.13/misc/snd.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-seq-device.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-rawmidi.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-mpu401-uart.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-timer.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-pcm.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-ac97-codec.o will taint the kernel: no license
Warning: loading /lib/modules/2.4.13/misc/snd-card-via686a.o will taint the kernel: no license
done
/usr/sbin/alsactl: load_state:1026: No soundcards found...
I get this _every_ time with 2.4.13 .
Of course I know that this is not the Alsa EMail list. But
maybe you have some ideas which change has broken Alsa
completely and give the Alsa folks a hint.
Many thanx
Harri
next reply other threads:[~2001-10-24 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 21:15 Harald Dunkel [this message]
2001-10-24 21:26 ` Alsa 0.9beta8a with 2.4.{12,13} ? Robert Love
2001-10-25 0:28 ` Daniel T. Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BD72F8F.43E21E66@Synopsys.COM \
--to=harri@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox