Alsa 1.0.6

mel82 · 09-14-2004, 03:56 PM

I've downloaded and compiled kernel 2.6.7.

I've made my personal and simple configuration, leaving out the audio support (just including modular support for it, I've tested it will not work correctly if included).
All (but the audio, of course) works fine.

I've downloaded the alsa-lib and alsa-driver (1.0.6).
Some ./configures, makes, alsaconfs after, the audio seems to work correct, and even eSound (but not Arts - why?) works correctly.

I turned off the pc, and at the next reboot (now) the audio is missing!
??What the FAQ?? :? :?

Quote:

sh-2.05b$ alsamixer
No mixer elems found

Quote:

bash-2.05b# alsaconf
[some configuration choices, where I choose my card, as it is correctly detected]
===============================================================================

Now ALSA is ready to use.
For adjustment of volumes, use your favorite mixer.

Have a lot of fun!

bash-2.05b# alsamixer
No mixer elems found

??What the FAQ?? :? :?

Well.. I don't know what to do..
the first time a new "make install" of the alsa-libs have solved the situation, but this time nothing seems to wake my speakers..

bonecrusher · 09-28-2004, 01:58 PM

Quote:

Originally posted by mel82
I've downloaded and compiled kernel 2.6.7.

I've made my personal and simple configuration, leaving out the audio support (just including modular support for it, I've tested it will not work correctly if included).
All (but the audio, of course) works fine.

I've downloaded the alsa-lib and alsa-driver (1.0.6).
Some ./configures, makes, alsaconfs after, the audio seems to work correct, and even eSound (but not Arts - why?) works correctly.

I turned off the pc, and at the next reboot (now) the audio is missing!
??What the FAQ?? :? :?

??What the FAQ?? :? :?

Well.. I don't know what to do..
the first time a new "make install" of the alsa-libs have solved the situation, but this time nothing seems to wake my speakers..

you compiled yourself?
Compiling alsa is a bitch.

Why not just install them as packages?

bc

mel82 · 09-29-2004, 01:51 AM

Theorically it won't make any difference.

I have also tried to retrieve the package with swaret, but it does not work.

Now, after a compilation with the right parameters, it works, but I haven't found yet how to get the sound working at boot.

I need every time to do
"alsaconf" -- chose my card and double [enter]
and "alsactl restore" to restore the mixer settings.

Ho to avoid that?

bonecrusher · 09-29-2004, 11:34 AM

Quote:

Originally posted by mel82
Theorically it won't make any difference.

I have also tried to retrieve the package with swaret, but it does not work.

Now, after a compilation with the right parameters, it works, but I haven't found yet how to get the sound working at boot.

I need every time to do
"alsaconf" -- chose my card and double [enter]
and "alsactl restore" to restore the mixer settings.

Ho to avoid that?

Again- As complicated as ALSA is I can't recommend enough getting the packages and using swaret. If that doesn't work then use plain old pkgtool...if that doesn't work then you have worse problems then just ALSA not working.

Just remove all the old alsa crap first .. then when you have no compiled form of alsa and no old packages (ALSA) laying around, use pkgtools to install the new versions..

I could try and figure out went wrong.. sounds like a boot problem.. but it would be a whole lot cleaner just to use the pkgtool. If you insist on doing it the hard way let me know and I will try and help you with your boot-up (alsa) problem...

let me know.

bc

ps:
I am sure you did this, but are you sure your running modules for ALSA (I personally turn off old OSS drivers completely and just use ALSA as modules).
and r u running hotplug? (Just curious)

mel82 · 09-29-2004, 12:19 PM

I'm running hotplug, but I have not understood how it works..

can you post your rc.alsa pls?

bonecrusher · 09-29-2004, 04:19 PM

Quote:

Originally posted by mel82
I'm running hotplug, but I have not understood how it works..

can you post your rc.alsa pls?

My rc.alsa isn't going to help you. I simply think your rc.alsa isn't getting loaded....

do this:

Code:

# cd /etc/rc.d
# grep alsa *

If it doesnt list any files besides rc.alsa (namely rc.M) then you have a problem. Under Slackware this usually defaults to rc.M
(Mine got removed when I did an upgrade to Slack v10 so maybe that's what happened to you?)

Code:

if [ -x /etc/rc.d/rc.acpid ]; then
  /bin/emit -p acpid

  if [ $? -eq 0 ]; then
    SETLEVEL_ERR_TXT
    . /etc/rc.d/rc.acpid start
    SETLEVEL_IGNORE_TXT
    LINE_OVFLO=1
  fi
fi

if [ -x /etc/rc.d/rc.alsa ]; then
  /bin/emit -p alsa-

  if [ $? -eq 0 ]; then
  SETLEVEL_INFO_TXT
  . /etc/rc.d/rc.alsa
  SETLEVEL_IGNORE_TXT
  fi
fi

# Start crond (Dillon's crond):
#
# If you want cron to actually log activity to /var/log/cron,
# then change -l10 to -l8 to increase the logging level.
#
/bin/emit -p crond -l10   

if [ $? -eq 0 ]; then
  SETLEVEL_ERR_TXT
  /usr/sbin/crond -l10 >> /var/log/cron 2>&1
  SETLEVEL_IGNORE_TXT
fi
echo    # ^ BMS additions 7/5/2004

Just ignore that 'SETLEVEL' crap.. that is just some stuff I added to my boot that makes it look nice and 'knoppix' like or something-when Slackware loads up..(SETLEVEL just adds color.. other stuff gives you option of overiding any daemon you like...)

Anyway add that alsa entry above without the SETLEVEL stuff to your "rc.M" ....
eg:

Code:

if [ -x /etc/rc.d/rc.alsa ]; then 
. /etc/rc.d/rc.alsa
fi

Then rc.alsa should load as long as it resides in /etc/rc.d and rc.alsa is executable (-x) as in:

chmod 755 rc.alsa

(That reminds me that the possibility also exists that your rc.alsa might not be executable.. if that is the case then it will fail to load also..rc files are designed to be loaded/no loaded or 'turned off' by simply chmod'ing them to read/write/noexec so if the exec bit is off then no load...so make sure of this....!)

bc

bonecrusher · 09-29-2004, 04:38 PM

I meant to mention also, that under KDE/Xwindows my sound worked fine without rc.alsa even being executed. So I dunno where your problem is, but hopefully we can fix it by the above. If not, then I would still suggest cleaning out your system of alsa and installing by using 'swaret' or 'installpkg' (pkgtools)....

bc