Bug 130503 - udev - no /dev/dsp
Summary: udev - no /dev/dsp
Keywords:
Status: CLOSED DUPLICATE of bug 130746
Alias: None
Product: Fedora
Classification: Fedora
Component: udev
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-20 20:25 UTC by Sammy
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sammy 2004-08-20 20:25:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux; X11; en_US, en_US.UTF-8, en) (KHTML, like Gecko)

Description of problem:
After fixing the initscripts to start udev, making a new initrd image, etc.
I was able to reboot and everything worked except sound.

When I logged into kde interface, either as root or user I got a
message stating that /dev/dsp was not there.

I noticed that the sound modules, which are all in modprobe.conf, were
not loaded e.g. snd-pcm-oss (using artsd and alsa). When I modprobed
I could get  /dev/dsp created and sound worked. But after rebooting
the same problem. Non udev using kernel works fine. If this is a mkinitrd
problem please reassign.

PS: also microcode_ctl is failing at boot saying it could not find a certain device.

Version-Release number of selected component (if applicable):
udev-030-3

How reproducible:
Always

Steps to Reproduce:
1.install kernel using udev
2.login to kde
3.
    

Additional info:

Comment 1 Ralf Ertzinger 2004-08-22 17:27:53 UTC
Also missing are device nodes for SCSI-CD-ROM drives (/dev/scd* or
/dev/sr*), /dev/cdrom* symlinks, /dev/cdwriter* symlinks and /dev/sg*
device nodes.

Comment 2 Harald Hoyer 2004-08-24 09:04:03 UTC

*** This bug has been marked as a duplicate of 130746 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:05:12 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.