Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35955 - Cannot create devices in /dev with udev now
Summary: Cannot create devices in /dev with udev now
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-16 09:59 UTC by Decibels
Modified: 2003-12-16 16:28 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Decibels 2003-12-16 09:59:48 UTC
I know udev is under developement, but thought should bring up this issue, especially in regards to alsa.

After emerge udev-007,....and setting up everything to work (this is where it gets a little fuzzy, ie. not sure if remerged nvidia-kernel before or after emerging the new baselayout-1.8.6.12-r2 to get the init scripts inplace to work with udev and sysfs).  But, had to remerge the nvidia-kernel to get the devices in place in /dev like nvidiactl. Started X and came up, nvidia /dev files continued to be there after the next reboot,.... 

Now am certain that have the new baselayout in place, and just tried this: Cannot run alsamixer or amixer again. Why? Because the devices are not in /dev/snd, the snd folder disappeared. Ran alsaconf (which used to create the devices the first time. It will not create them now. Can mkdir /dev/snd, can make a character device in there with mknod. Looks like the only way to get them there now is to manually create them or copy them into the tarball in /lib/udev-state (which haven't tried yet). 

Reproducible: Always
Steps to Reproduce:
1. Setup system for udev.
2. Reboot so /sys is mounted and /dev mounted in ramfs
3. Have to reinstall nvidia-kernel and alsa devices because are not in the tarball in /lib/udev-state.
4. Alsaconf will not create the devices in /dev now. Not sure about nvidia-kernel cause don't want to mess with it and screw up X.

Actual Results:  
/dev/snd folder is not created or the devices that should be there. Previously
ran alsaconf and correctly installed the folder and devices. 

Expected Results:  
First to not have to reinstall nvidia-kernel or alsa for just a /dev change.
Second to be able to create the devices.


Udev is working fine otherwise. Not sure if this is caused by the new
baselayout, udev or combo of both. Had udev-007, first tried this with udev-008,
but downgraded to 007, to see if it would work and nogo.
Also tried creating the /dev/snd folder and rerunning alsaconf, but still nogo.
Comment 1 Decibels 2003-12-16 10:01:14 UTC
Sorry about the long lines. Thought it would take care of it like the forums. But I can't edit it. If someone wants to fix it that can feel free. 
Comment 2 Decibels 2003-12-16 10:43:49 UTC
Manually created /dev/snd, then 
mknod /dev/snd/controlC0  c 116 0
mknod /dev/snd/controlC1  c 116 0
mknod /dev/snd/controlC2  c 116 0

Hope I got the minor node correct on the last two, don't know if should be a 1 and 2 or 0 is fine. Is there a command to show the major and minor nodes of devices while in /dev?

Anyways, rebooted and still there. So scripts are doing their job on that part of saving and restoring from /lib/udev-state/devices.tar.bz2

Was able to get into alsamixer and reset my asound.state.
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2003-12-16 15:19:44 UTC
Alsa is not sysfs-ified yet, so it will not work (same as nvidia driver).
You will have to wait for sysfs support in alsa I am afraid.
Comment 4 Decibels 2003-12-16 16:28:17 UTC
"sysfs-ified"  lol.  Okay, will manually create till then. Silly me, major and minor node are listed with 'ls -l'

Someone else mention same problem with /dev/mapper/control for lvm2 if you making a list. 

Cheers.