Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
01-04-2005, 11:21 AM
|
#1
|
Member
Registered: Sep 2002
Location: Atlanta, GA
Distribution: Linux Mint Gloria, Slackware 12.2
Posts: 165
Rep:
|
problems with udev - 2.6.10 kernel
I can't seem to get udev to start properly. I have a rc.udev script, butwhen it runs the first time, no nodes get created for the soud devices (/dev/dsp, etc) that ALSA needs to emulate OSS. I end up having to re-initialize udev in my local script. And when I do that, somehow /dev/pts gets uncreated and I have to re-mount it, again from my local script. (Without /dev/pts, I can't access the command-line from X  !)
My basic question is what am I not doing right with udev? Why should I have to turn it on twice? I'm thinking that something stops it before it gets fully initialized, but dmesg and syslog don't show anything. Hmm, maybe I didn't scrutinize syslog as closely as I need to, now that I think about it.
In any case, suggestions would be appreciated. Thanks in advance!
--Akshun J
|
|
|
01-04-2005, 12:50 PM
|
#2
|
Senior Member
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721
Rep:
|
well...i don't know any other solution as the one you posted.
( might have to do with the Slack-startup script or udev itself....... )
egag
|
|
|
01-04-2005, 01:03 PM
|
#3
|
Senior Member
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140
|
I had the same issue (I use snd_intel8x0 driver), I ended with compile all sound features as built-in
Now udev creates the /dev/dsp etc... the same way as before
|
|
|
01-04-2005, 01:54 PM
|
#4
|
Member
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761
Rep:
|
The solution I came across and use is simply to reload the OSS emulation modules.
To do that, the following is in my /etc/rc.d/rc.local
Code:
# /dev/dsp Also loads snd_mixer_oss for /dev/mixer
modprobe snd_pcm_oss
# /dev/midi
modprobe snd_seq_oss
|
|
|
01-04-2005, 01:55 PM
|
#5
|
Senior Member
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140
|
Good point  , you did not put them in /etc/hotplug/blacklist ?
|
|
|
01-04-2005, 02:41 PM
|
#6
|
Member
Registered: Sep 2002
Location: Atlanta, GA
Distribution: Linux Mint Gloria, Slackware 12.2
Posts: 165
Original Poster
Rep:
|
No, they are not blacklisted. They autoload from /etc/modprobe.conf. Which I thought was the desired behavior. So I should load them from rc.local and blacklist them on hotplug? Hmm, I will give it a try.
Is it just an issue of timing? If Alsa loads the OSS module before udev initializes, does that create the issue? It would make sense. I'll just kill rc.alsa all together and reload volume and OSS from local. I'll post if that works when I get home. Thanks for the help, dude. I really appreciate i!
--Akshun J
|
|
|
01-05-2005, 03:41 PM
|
#7
|
Member
Registered: Sep 2002
Location: Atlanta, GA
Distribution: Linux Mint Gloria, Slackware 12.2
Posts: 165
Original Poster
Rep:
|
Well, I have determined that this issue is a conflict between ALSA and udev. I think the bug is with udev. However, it appears on the ALSA bug-tracking. I compiled soundcore as a module. When soundcore loads, udev creates a node at /dev/sound. Then, when the oss modules are loaded, udev tries to put them in a /dev/sound directory, but the existence of /dev/sound node intereferes with this. There is no where for them to go. I think I can blacklist soundcore and load it after udev is grooving, but I think it's got to load BEFORE the oss modules, which leaves me with the problem again. The only solution I have that works is to restart udev and remount /dev/pts. I can live with it, but it seems like a dirty hack. And, of course, I can compile soundcore into the kernel. That works for my laptop (same version of udev and ALSA.) I think udev still needs some work.
--Akshun J
|
|
|
01-21-2005, 11:32 AM
|
#8
|
LQ Newbie
Registered: Dec 2003
Distribution: Slackware
Posts: 4
Rep:
|
How exactly do you generate a /dev/dsp. Mine went away between 2.6.8.1 and 2.6.10. I am using the snd-cmipci sound module.
tcorner@emerson:~$ ls /sys/class/sound
adsp/ controlC0/ dsp1/ pcmC0D0c/ pcmC0D2c/ timer/
audio/ controlC1/ mixer/ pcmC0D0p/ pcmC0D2p/
audio1/ dsp/ mixer1/ pcmC0D1p/ pcmC1D0c/
Now how do I link the devices described in /sys/class/sound to a /dev/dsp etc. ?
Thanks,
Tom
|
|
|
01-21-2005, 11:45 AM
|
#9
|
LQ Newbie
Registered: Dec 2003
Distribution: Slackware
Posts: 4
Rep:
|
I hate to reply to myself, but I got it. There is already an /etc/rc.d/rc.udev script. It just needs to be rerun in r/etc/rc.d/rc.local.
Thanks,
Tom
|
|
|
All times are GMT -5. The time now is 05:29 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|