| View previous topic :: View next topic |
| Author |
Message |
»Q«
Guest
|
 Posted: Wed Nov 19, 2008 3:48 am Post subject: no sound with runlevel 4 |
 |
|
Slack 12.1, using KDE whenever I use X.
I've been booting to runlevel 3 and typing startx when I wanted KDE,
but I decided to start booting to runlevel 4. The only changes I made
were to change the 3 to a 4 and to add runlevel 4 to the
first 5 agetty respawning rules inittab. Other than that, I've never
made any changes to Slack's init system.
When I boot to runlevel 3, my sound drivers are loaded, and all is well.
But when I boot to runlevel 4 (or switch to runlevel 4), the sound
drivers are not loaded.
I guess I could solve this problem by just compiling the sound stuff
into the kernel, but I'd rather understand why it's not loaded
automagically as it is with runlevel 3.
In case it matters, I have Intel HD sound, using the snd_hda_intel
driver. |
|
| |
|
 Back to top |
Thomas Overgaard
Guest
|
| Posted: Wed Nov 19, 2008 4:10 am Post subject: Re: no sound with runlevel 4 |
|
|
Q. boxcars wrote :
| Quote: | The only changes I made were to change the 3 to a 4
|
This ought to be enough.
| Quote: | and to add runlevel 4 to the first 5 agetty respawning rules inittab.
|
That shouldn't be necessary. What happen if you undo this?
--
Thomas O.
This area is designed to become quite warm during normal operation. |
|
| |
|
| Back to top |
Lubiraz Alerano
Guest
|
| Posted: Wed Nov 19, 2008 5:18 am Post subject: Re: no sound with runlevel 4 |
|
|
On Nov 19, 8:48 am, »Q« <boxc...@gmx.net> wrote:
| Quote: | When I boot to runlevel 3, my sound drivers are loaded, and all is well.
But when I boot to runlevel 4 (or switch to runlevel 4), the sound
drivers are not loaded.
|
Did something similar few days ago and the system (Slack 12.1)
continued singing in both instances.
It may relate to old habit, which means that on initial install one of
last things done IS call alsamixer and configure the relevant audio
responses presented and 'tell' it 'alsactl store'. So after this when
booting the computer writes to screen a long story with alsa mentioned
in last few lines, before the logon call.
Then I changed in inittab file the default run level from 3 to 4,
saved the file and rebooted to singing AND dancing KDE.
HTH |
|
| |
|
| Back to top |
»Q«
Guest
|
| Posted: Wed Nov 19, 2008 8:42 am Post subject: Re: no sound with runlevel 4 |
|
|
In <mid:63rbv5-6t6.ln1@news.inet.tele.dk>,
Thomas Overgaard <thover@post2.tele.dk> wrote:
| Quote: | Q. boxcars wrote :
The only changes I made were to change the 3 to a 4
This ought to be enough.
and to add runlevel 4 to the first 5 agetty respawning rules
inittab.
That shouldn't be necessary.
|
Eventually, I do want the VCs, but I can wait for that until after
solving the sound problem.
| Quote: | What happen if you undo this?
|
I reverted all changes, then just changed the runlevel. To be sure,
here's the diff with the Slack-supplied inittab.
# diff /etc/inittab.orig /etc/inittab
24c24
< id:3:initdefault:
---
Alas, the sound modules are still not loading with runlevel 4.
--
»Q«
Kleeneness is next to Gödelness. |
|
| |
|
| Back to top |
»Q«
Guest
|
| Posted: Wed Nov 19, 2008 8:42 am Post subject: Re: no sound with runlevel 4 |
|
|
In <news:20081118224351.3d6e04e4@prezmyra.remarqs.net>,
»Q« <boxcars@gmx.net> wrote:
| Quote: | Alas, the sound modules are still not loading with runlevel 4.
|
Ugh, that's just wrong. I don't know how I was misreading the lsmod
output, but somehow I was. Sorry for the red herring.
The modules *are* loading, but for some reason KDE does not recognize
the sound device. I don't have a clue why that is; if I get any clue,
I'll post back.
--
»Q«
Kleeneness is next to Gödelness. |
|
| |
|
| Back to top |
»Q«
Guest
|
| Posted: Wed Nov 19, 2008 8:42 am Post subject: Re: no sound with runlevel 4 |
|
|
In
<news:ce75f10d-b0b0-458f-9e01-cb079a521a6e@w39g2000prb.googlegroups.com>,
Lubiraz Alerano <compaid@aussiebroadband.com.au> wrote:
| Quote: | On Nov 19, 8:48 am, »Q« <boxc...@gmx.net> wrote:
When I boot to runlevel 3, my sound drivers are loaded, and all is
well. But when I boot to runlevel 4 (or switch to runlevel 4), the
sound drivers are not loaded.
Did something similar few days ago and the system (Slack 12.1)
continued singing in both instances.
It may relate to old habit, which means that on initial install one of
last things done IS call alsamixer and configure the relevant audio
responses presented and 'tell' it 'alsactl store'. So after this when
booting the computer writes to screen a long story with alsa mentioned
in last few lines, before the logon call.
Then I changed in inittab file the default run level from 3 to 4,
saved the file and rebooted to singing AND dancing KDE.
HTH
|
I did use alsamixer and alsactrl store back when I installed.
As I posted a little earlier, I was simply wrong about the modules not
being loaded. They are loaded, just KDE cannot see the device. More
than that, it seems that within a KDE session, nothing can see the
device.
Everything below is after booting to runlevel 4.
If I use ctrl+alt+f6 to get to a VC, I can play audio from the command
line just fine. 'play example.mp3' works ok, and I can run alsamixer.
Within KDE, I can't do any of that. Whether I try it in Konsole or
xterm or the xfce terminal, the results are the same.
$ play example.mp3
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3510:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such device ALSA lib
confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib
conf.c:3510:(_snd_config_evaluate) function snd_func_concat returned
error: No such device ALSA lib confmisc.c:1251:(snd_func_refer) error
evaluating name ALSA lib conf.c:3510:(_snd_config_evaluate) function
snd_func_refer returned error: No such device ALSA lib
conf.c:3982:(snd_config_expand) Evaluate error: No such device ALSA lib
pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default sox: Failed
writing default: cannot open audio device
$ alsamixer
alsamixer: function snd_ctl_open failed for default: No such device
--
»Q«
Kleeneness is next to Gödelness. |
|
| |
|
| Back to top |
Sylvain Robitaille
Guest
|
| Posted: Wed Nov 19, 2008 5:19 pm Post subject: Re: no sound with runlevel 4 |
|
|
»Q« wrote:
| Quote: | When I boot to runlevel 3, my sound drivers are loaded, and all is
well.
But when I boot to runlevel 4 (or switch to runlevel 4), the sound
drivers are not loaded.
...
(later corrected: sound drivers load, but still no sound in run-level 4) |
See the AOLS FAQ at http://www.therockgarden.ca/aolsfaq.txt (an HTML
version is also pointed to in a periodic posting to this newsgroup,
entitled "Alt.OS.Linux.Slackware FAQ pointer").
Look specifically for the following:
Why am I unable to get sound after setting up a graphical login program?
I hope this helps ...
--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
---------------------------------------------------------------------- |
|
| |
|
| Back to top |
Clemens Ladisch
Guest
|
| Posted: Wed Nov 19, 2008 6:43 pm Post subject: Re: no sound with runlevel 4 |
|
|
»Q« wrote:
| Quote: | As I posted a little earlier, I was simply wrong about the modules not
being loaded. They are loaded, just KDE cannot see the device. More
than that, it seems that within a KDE session, nothing can see the
device.
If I use ctrl+alt+f6 to get to a VC, I can play audio from the command
line just fine.
|
This sounds like a permissions problem. Do the owner/access bits of the
files in /dev/snd/ change when you are in KDE?
Best regards,
Clemens |
|
| |
|
| Back to top |
Lubiraz Alerano
Guest
|
| Posted: Wed Nov 19, 2008 11:12 pm Post subject: Re: no sound with runlevel 4 |
|
|
On Nov 19, 5:28 pm, »Q« <boxc...@gmx.net> wrote:
| Quote: | In
news:ce75f10d-b0b0-458f-9e01-cb079a521a6e@w39g2000prb.googlegroups.com>,
Lubiraz Alerano <comp...@aussiebroadband.com.au> wrote:
On Nov 19, 8:48 am, »Q« <boxc...@gmx.net> wrote:
When I boot to runlevel 3, my sound drivers are loaded, and all is
well. But when I boot to runlevel 4 (or switch to runlevel 4), the
sound drivers are not loaded.
|
Are you in this instance 'root' or just lowly user?
Try both and if,repeat if, it makes any difference look in your
'groups' file and enroll this user in proper group(s).
Just don't make him too powerful or one keystroke can give you
something else to worry about;^).
Have fun |
|
| |
|
| Back to top |
Eric Hameleers
Guest
|
| Posted: Thu Nov 20, 2008 5:07 am Post subject: Re: no sound with runlevel 4 |
|
|
»Q« schreef:
| Quote: | Slack 12.1, using KDE whenever I use X.
I've been booting to runlevel 3 and typing startx when I wanted KDE,
but I decided to start booting to runlevel 4. The only changes I made
were to change the 3 to a 4 and to add runlevel 4 to the
first 5 agetty respawning rules inittab. Other than that, I've never
made any changes to Slack's init system.
When I boot to runlevel 3, my sound drivers are loaded, and all is well.
But when I boot to runlevel 4 (or switch to runlevel 4), the sound
drivers are not loaded.
I guess I could solve this problem by just compiling the sound stuff
into the kernel, but I'd rather understand why it's not loaded
automagically as it is with runlevel 3.
In case it matters, I have Intel HD sound, using the snd_hda_intel
driver.
|
This is a very very old FAQ and a quick google would have revealed the
solution.
When you boot in runlevel 4 "graphical login", you need to add your
user account at least to the following groups:
- audio (so that you have sound),
- plugdev (so that auto-mounting a CD or USB stick works),
- power (so that you are allowed to power down your box),
- floppy (if you have a floppy drive and want to use it),
- cdrom (if you want to be able to access the DVD you just inserted)
This is the difference with runlevel 3 "console login": in runlevel 3
you are implicitly added to all these groups when you login. In
runlevel 4, you must be explicitly a member of these groups or else
you will not have access to your computer peripherals.
As root, run:
# gpasswd -a audio <youraccount>
# gpasswd -a plugdev <youraccount>
# gpasswd -a power <youraccount>
# gpasswd -a floppy <youraccount>
# gpasswd -a cdrom <youraccount>
to add your account. Logout and login again, and it should all work as
expected.
Eric |
|
| |
|
| Back to top |
»Q«
Guest
|
| Posted: Thu Nov 20, 2008 8:43 pm Post subject: Re: no sound with runlevel 4 |
|
|
In <news:slrngi8ilm.n3n.syl@charlotte.concordia.ca>,
Sylvain Robitaille <syl@alcor.concordia.ca> wrote:
| Quote: | »Q« wrote:
When I boot to runlevel 3, my sound drivers are loaded, and all is
well.
But when I boot to runlevel 4 (or switch to runlevel 4), the sound
drivers are not loaded.
...
(later corrected: sound drivers load, but still no sound in run-level
4)
See the AOLS FAQ at http://www.therockgarden.ca/aolsfaq.txt (an HTML
version is also pointed to in a periodic posting to this newsgroup,
entitled "Alt.OS.Linux.Slackware FAQ pointer").
Look specifically for the following:
Why am I unable to get sound after setting up a graphical login
program?
I hope this helps ...
|
It did, thanks. I had googled without turning up anything, but I
hadn't looked at that faq. I will from now on.
I had added myself to most groups needed (cdrom, plugdev, wheel) when
I created the account, but I'd left out audio.
--
»Q«
Kleeneness is next to Gödelness. |
|
| |
|
| Back to top |
Loki Harfagr
Guest
|
| Posted: Thu Nov 20, 2008 11:28 pm Post subject: Re: no sound with runlevel 4 |
|
|
Thu, 20 Nov 2008 00:07:32 +0100, Eric Hameleers did cat :
| Quote: | As root, run:
# gpasswd -a audio <youraccount
|
just a small detail, that should read:
# gpasswd -a <youraccount> audio |
|
| |
|
| Back to top |
otzy_007
Guest
|
| Posted: Sat Nov 22, 2008 8:06 pm Post subject: Re: no sound with runlevel 4 |
|
|
i had the same problem like you. in runlevel 3 i had sound and in
runlevel 4 none. I've just added the user to the audio group and now I
have sound |
|
| |
|
| Back to top |
|
