Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: lrwxrwxrwx 1 root root 13 2005-10-12 16:43 080.rules - ../udev.rules lrwxrwxrwx 1 root root 15 2005-10-12 16:30 100compat.rules - ../compat.rules Same thing. You cannot use both of these files. -- ciao, Marco signature.asc Description: Digital signature
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Tuesday 20 December 2005 09:18, Marco d'Itri wrote: On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: lrwxrwxrwx 1 root root 13 2005-10-12 16:43 080.rules - ../udev.rules lrwxrwxrwx 1 root root 15 2005-10-12 16:30 100compat.rules - ../compat.rules Same thing. You cannot use both of these files. So they're not distinct subsets? The ALSA devices are only in 080.rules, and the dsp device for OSS emulation only in 100compat.rules ... I remember having had problems with some devices - so I tried to use that, too. I've now removed the symlink 100compat.rules, but the problem remains - I get only a /dev/dsp - dsp. Thank you for your help! Regards, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: So they're not distinct subsets? The ALSA devices are only in 080.rules, and This is explained in README.Debian. I've now removed the symlink 100compat.rules, but the problem remains - I get only a /dev/dsp - dsp. Hard to believe, unless I missed some other file. Did you reboot? You should also check with udevinfo/udevtest. -- ciao, Marco signature.asc Description: Digital signature
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Tuesday 20 December 2005 09:34, Marco d'Itri wrote: On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: So they're not distinct subsets? The ALSA devices are only in 080.rules, and This is explained in README.Debian. Oops, sorry. Should read documentation first, no? I've now removed the symlink 100compat.rules, but the problem remains - I get only a /dev/dsp - dsp. Hard to believe, unless I missed some other file. I just rmmod snd_pcm_oss rm /dev/dsp modprobe snd_pcm_oss and /dev/dsp - dsp reappears. Did you reboot? That is a machine where I do software suspend - so it basically gets no reboots unless absolutely necessary. Do you think that may help? You should also check with udevinfo/udevtest. $ udevinfo -q all -n dsp P: /class/sound/dsp N: dsp S: dsp $ udevtest /class/sound/dsp sound main: looking at device '/class/sound/dsp' from subsystem 'sound' main: opened class_dev-name='dsp' udev_rules_get_name: no node name set, will use kernel name 'dsp' create_node: creating device node '/dev/dsp', major = '14', minor = '3', mode = '0660', uid = '0', gid = '29' Is that what you need to know? On a modprobe snd_pcm_oss my pid's jump from 2969 to 2988 - so there are some processes started. How do I find them? Regards, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: On Tuesday 20 December 2005 09:34, Marco d'Itri wrote: Did you reboot? That is a machine where I do software suspend - so it basically gets no reboots unless absolutely necessary. Do you think that may help? Maybe. It's worth trying. You should also check with udevinfo/udevtest. $ udevinfo -q all -n dsp P: /class/sound/dsp N: dsp S: dsp So you still have NAME and SYMLINK set to dsp. On a modprobe snd_pcm_oss my pid's jump from 2969 to 2988 - so there are some processes started. How do I find them? Look at /etc/modprobe.d/. -- ciao, Marco signature.asc Description: Digital signature
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Tuesday 20 December 2005 12:51, Marco d'Itri wrote: You should also check with udevinfo/udevtest. $ udevinfo -q all -n dsp P: /class/sound/dsp N: dsp S: dsp So you still have NAME and SYMLINK set to dsp. One suspend later I'm getting $ udevinfo -q all -n dsp no record for 'dsp' in database. Re-doing rmmod, modprobe I get the values from above. Where does this information come from? $ grep -ri dsp /etc/udev/ compat-full.rules:KERNEL==dsp* SYMLINK+=%k compat.rules:KERNEL==dsp* SYMLINK+=%k devfs.rules:KERNEL==dsp*, NAME=sound/%k devfs.rules:KERNEL==adsp*, NAME=sound/%k Looking at these lines I see that most lines have KERNEL==..., SYMLINK+=%k but that audio*, dsp* and mixer* are there with KERNEL==... SYMLINK+=%k (notice the missing ,). I entered the colons, and did my rmmod/modprobe routing, but I still get my dsp - dsp ;-( On a modprobe snd_pcm_oss my pid's jump from 2969 to 2988 - so there are some processes started. How do I find them? Look at /etc/modprobe.d/. $ grep -ri dsp /etc/modprobe.d/ $ Thank you for your help! Regards, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: One suspend later I'm getting I asked you to reboot. $ grep -ri dsp /etc/udev/ Not relevant, only files in /etc/udev/rules.d/ are considered. (notice the missing ,). Not relevant either. -- ciao, Marco signature.asc Description: Digital signature
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Tuesday 20 December 2005 13:27, Marco d'Itri wrote: On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: One suspend later I'm getting I asked you to reboot. I don't really know why that should be necessary, but it's in progress now. $ grep -ri dsp /etc/udev/ Not relevant, only files in /etc/udev/rules.d/ are considered. The -r says to grep the whole directory structure, so no dsp in /etc/udev/rules.d/ either. (notice the missing ,). Not relevant either. Ok. I just thought that strange. later On reboot it works. Where is the data caches? I thought that every hotplug event causes udev to be run which reads its configuration files afresh. udevinfo says no record ... ... Hey, on nearer examining of ps -efax I see an udevd ... That may be the cause. (You could have told me to restart that instead of the whole machine :-) Hmm... Maybe udevd should re-parse its configuration upon change, like cron does. Thank you *very much* for your patience and your help. Regards, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: Hmm... Maybe udevd should re-parse its configuration upon change, like cron It does (unless you are running a kernel without inotify support). -- ciao, Marco signature.asc Description: Digital signature
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
On Tuesday 20 December 2005 13:52, Marco d'Itri wrote: On Dec 20, Ph. Marek [EMAIL PROTECTED] wrote: Hmm... Maybe udevd should re-parse its configuration upon change, like cron It does (unless you are running a kernel without inotify support). Well, that's it, then. # CONFIG_INOTIFY is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y Thank you very much! Regards, Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344120: udev: snd_pcm_oss makes symlink /dev/dsp - dsp
X-Reportbug-Version: 3.18 X-Debbugs-Cc: [EMAIL PROTECTED] Package: udev Version: 0.076-6 Severity: normal On a Acer Travelmate 529TXV I include snd_pcm_oss. I get a /dev/dsp, but that is a symlink to dsp: $ ls -la /dev/dsp lrwxrwxrwx 1 root root 3 2005-12-20 09:40 /dev/dsp - dsp udevmonitor: udevmonitor prints the received event from the kernel [UEVENT] and the event which udev sends out after rule processing [UDEV] UEVENT[1135068286.920648] add@/module/snd_pcm_oss UEVENT[1135068286.920795] add@/class/sound/dsp UEVENT[1135068286.920811] add@/class/sound/audio UEVENT[1135068286.920826] add@/class/sound/adsp UDEV [1135068286.928839] add@/module/snd_pcm_oss UDEV [1135068286.940921] add@/class/sound/dsp UDEV [1135068286.961477] add@/class/sound/audio UDEV [1135068286.980755] add@/class/sound/adsp $ cat /sys/class/sound/dsp/dev 14:3 If I mknod the /dev/dsp with appropriate rights it works. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: insgesamt 4 lrwxrwxrwx 1 root root 19 2005-10-12 08:05 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 16 2005-12-19 08:15 025_libsane.rules - ../libsane.rules lrwxrwxrwx 1 root root 22 2005-12-06 08:12 025_logitechmouse.rules - ../logitechmouse.rules -rw-r--r-- 1 root root 302 2005-06-21 08:12 0mine.rules lrwxrwxrwx 1 root root 20 2005-05-10 08:06 20_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 13 2005-01-10 10:20 50_udev.rules - ../udev.rules lrwxrwxrwx 1 root root 14 2005-01-10 10:20 60_devfs.rules - ../devfs.rules lrwxrwxrwx 1 root root 19 2005-01-10 10:20 cd-aliases.rules - ../cd-aliases.rules lrwxrwxrwx 1 root root 19 2005-08-16 07:55 z20_persistent.rules - ../persistent.rules lrwxrwxrwx 1 root root 12 2005-07-11 07:28 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2005-10-10 08:25 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 15 2005-09-20 07:27 z60_hdparm.rules - ../hdparm.rules lrwxrwxrwx 1 root root 17 2005-07-11 07:28 z70_hotplugd.rules - ../hotplugd.rules -- /sys/: /sys/block/fd0/dev /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hdc/dev /sys/block/ram0/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram1/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/class/drm/card0/dev /sys/class/input/event0/dev /sys/class/input/event1/dev /sys/class/input/event2/dev /sys/class/input/event3/dev /sys/class/input/mice/dev /sys/class/input/mouse0/dev /sys/class/input/mouse1/dev /sys/class/misc/agpgart/dev /sys/class/misc/device-mapper/dev /sys/class/misc/hpet/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/tun/dev /sys/class/printer/lp0/dev /sys/class/sound/controlC1/dev /sys/class/sound/dmmidi1/dev /sys/class/sound/dsp/dev /sys/class/sound/midi1/dev /sys/class/sound/midiC1D0/dev /sys/class/sound/mixer/dev /sys/class/sound/timer/dev /sys/class/usb_device/usbdev1.1/dev /sys/class/usb_device/usbdev1.2/dev /sys/class/usb_device/usbdev2.1/dev /sys/class/usb_device/usbdev2.2/dev /sys/class/usb/lp0/dev -- Kernel configuration: -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-1) (ignored: LC_ALL set to de_AT) Versions of packages udev depends on: ii initscripts 2.86.ds1-6 Standard scripts needed for bootin ii libc6 2.3.5-9GNU C Library: Shared libraries an ii libselinux1 1.26-1 SELinux shared libraries ii lsb-base 3.0-12 Linux Standard Base 3.0 init scrip ii makedev 3.3.8.2-0 Creates device files in /dev ii sed 4.1.4-5The GNU sed stream editor udev recommends no packages. -- debconf information: udev/devfs-warning: * udev/reboot-warning: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
