| Autor |
Nachricht |
|
|
Titel: Saving Sound Config for the next restarts of the PC
 Verfasst am: 28.08.2006, 08:52 Uhr
|
|
Anmeldung: 28. Aug 2006
Beiträge: 5
|
|
Hi all!
This is my first message to this forum. I a newb to Linux and to Kanotix.
Recently I have chosen Kanotix between some distros to be installed on my old AMD Duron 750 MHz + 192 MB RAM. I chose Kanotix 2005-04 Release with Kernel 2.6.14 because it detected automatically most of my hardware, except for my Conexant winmodem and my old Soundblaster 16 Card.
Let's now forget about the winmodem, which seems for me a bit troubling (I have read info in www.linuxant.com and I think all I will be able to do is to setup the modem to 11,4 kbps unless I pay for the full version).
Now I want to setup, once and for all, my SB16, but my computer has a strange behaviour.I have been searching in the forum about this issue and I have found nothing, so I decided to open this thread.
The most curious thing is that I setup the sound correctly in my system with the alsa program. I run alsaconf in a shell as root, and the SB is detected and the sound works properly ... until I restart the system.
Every new restart the sound configuration is deleted and I have to run again the alsaconf.
I found in the KDE documentation that I had also to run "alsactl store" to save the configuration. So I did, but the next start the sound does not work.
In the log of the start I read in the screen the following:
......
Setting up ALSA ... done (none loaded)
This message gave the clue to think the sound configuration was not being stored in the system, so I decided to investigate i little bit more about how to load the drivers in the boot.I found /etc/init.d/alsa, which seemed to be the initscript of the alsa, but editing the file I read the following:
***********Extract of /etc/init.d/alsa *********
### END INIT INFO
#
# At one time this script loaded and unloaded ALSA driver modules on
# bootup and shutdown. This feature has since been removed. To load
# modules on bootup use the hotplug or the discover package or add
# the names of the modules that should be loaded to /etc/modules.
#
# At one time this script restored and stored mixer levels on
# bootup and shutdown. This feature has since been moved to the
# alsa-utils initscript.
#
# There is no longer any need to run this script on bootup or shutdown.
# It must remain in /etc/init.d/ for now, though, because certain
# other scripts expect to find it there.
***************************************************
I have been looking for information about how to use the hotplug or the discover package to save my sound config for the next restarts, but the info I found in debian is a little bit cryptic for my level of linux knowledge.At a last try,I found in the KDE menu the KDE SysV-init Editor, which seemed to be what I was looking for. I added "alsa" in the runlevel 6 of the start, and now I get the following message error the next time I logon again on the system:
*****************************************************
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such device)
The sound server will continue, using the null output device.
*************************************************************
So, i have to run again the alsaconf script in a shell every new restart of my PC in order to let the sound work.
Is there a way to save my SoundBlaster 16 Card Configuration for the next start of the system?Do I have to deal with the above mentioned "hotplug" and "discover" packages?.Perhaps I am missing a silly concept.Perhaps it´s a matter of incompatibilty, but I doubt it, because the alsaconf works ok everytime I run it.
Any clue please?
Thanks to everyone! |
|
|
| |
|
|
|
 |
|
|
|
Titel:
Verfasst am: 28.08.2006, 17:47 Uhr
|
|
Team Member
Anmeldung: 04. Apr 2006
Beiträge: 153
Wohnort: Melbourne, Australia
|
|
| try turning off aRTS in Control Centre,, better still uncheck "enable system sounds" |
_________________
Kanotix Easter RC4 on a dual boot P4 and a production box Desktop KDE::
Kanotix 2006 Easter RC4 on a P2 and Production Box , Desktop KDE::
Kanotix EasterRC4 on a MMX 199Mhz lappy
and a Production Box, Desktop ICEWM::
|
| |
|
|
|
|
|
|
|
Titel: Re: Saving Sound Config for the next restarts of the PC
Verfasst am: 28.08.2006, 18:54 Uhr
|
|
Anmeldung: 31. Jul 2004
Beiträge: 249
|
|
|
StrangETimeS hat folgendes geschrieben::
I found in the KDE documentation that I had also to run "alsactl store" to save the configuration. So I did, but the next start the sound does not work.
Did you do it as root? |
_________________
http://kanotix.wordpress.com/ inoffizielles Kanotix-Blog
|
| |
|
|
|
|
|
|
|
Titel: Re: Saving Sound Config for the next restarts of the PC
Verfasst am: 28.08.2006, 19:26 Uhr
|
|
Anmeldung: 28. Aug 2006
Beiträge: 5
|
|
|
zulu9 hat folgendes geschrieben::
StrangETimeS hat folgendes geschrieben::
I found in the KDE documentation that I had also to run "alsactl store" to save the configuration. So I did, but the next start the sound does not work.
Did you do it as root?
Yes, I do a "su" in the shell and then I execute:
"alsactl store"
The alsactl returns no log, so I don´t know wether it has done something or not.
I will try what bluewater says, and I will tell you.
Thanx again |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: Saving Sound Config for the next restarts of the PC
Verfasst am: 28.08.2006, 19:36 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
Try this
Go to K-Menu > Multimedia > and click on Kmix , it will shoot to the lower right corner on the kicker, right click on it, click on show mixer window > settings > configure kmix > just hit apply > reboot. |
_________________
h2's d-u script
h2's rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: Saving Sound Config for the next restarts of the PC
Verfasst am: 28.08.2006, 21:02 Uhr
|
|
Anmeldung: 31. Jul 2004
Beiträge: 249
|
|
|
|
|
|
|
|
|
Titel:
Verfasst am: 29.08.2006, 09:48 Uhr
|
|
Anmeldung: 28. Aug 2006
Beiträge: 5
|
|
Thanks piper and zulu9!
I will try both solutions asap.
Regarding the solution of the German forum...
I have been reading the solution Kano gave in the german forum and I understand that all I have to do (I assume as root) in a shell is execute 2 commands:
1) echo $(</proc/asound/modules )|awk '{print $2}' >> /etc/modules
2) update-rc.d -f alsa-utils defaults
Do I have to execute 1) as is withaout changing any path or do I have to bear in mind that these paths could be other ones in my PC?
Regards
StrangETimeS |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 29.08.2006, 15:04 Uhr
|
|
Team Member
Anmeldung: 03. Mai 2005
Beiträge: 1544
Wohnort: out there somewhere
|
|
Hi StrangETimeS
As root in konsole
echo $(</proc/asound/modules )|awk '{print $2}' >> /etc/modules (hit enter)
update-rc.d -f alsa-utils defaults (hit enter) |
_________________
h2's d-u script
h2's rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 29.08.2006, 20:17 Uhr
|
|
Anmeldung: 28. Aug 2006
Beiträge: 5
|
|
|
piper hat folgendes geschrieben::
Hi StrangETimeS
As root in konsole
echo $(</proc/asound/modules )|awk '{print $2}' >> /etc/modules (hit enter)
update-rc.d -f alsa-utils defaults (hit enter)
Hi!
It worked!
Thanx piper, zulu9... and Kano,of course! |
|
|
| |
|
|
|
|
|
|
