View previous topic :: View next topic |
Author |
Message |
panzerdampf n00b
Joined: 03 May 2003 Posts: 25 Location: Germany / Dresden
|
Posted: Wed Jul 13, 2005 9:09 am Post subject: udev, loop and no devices [solved] |
|
|
Hy
Udev doesn't create the /dev/loop* devices for me.
- vanilla kernel (2.6.12.2)
- udev is installed (058)
- the modul `loop` is build and loaded, the kernel message "loop: loaded (max 8 devices)" appears
- udev is mounted, "udev on /dev type tmpfs (rw,nosuid)"
- I don't use device-tarballs : RC_DEVICE_TARBALL="no"
- RC_DEVICES is set to "udev".
If I try to loop-mount an image I get the message 'mount: could not find any device /dev/loop'.
That's right cause udev didn't created them. But why?
Things that irritate me :
- no running udev process : `ps ax | grep udev`
- why does RC_DEVICES exists in '/etc/conf.d/rc'? No one needs it : `grep -r RC_DEVICES /etc/*`
Any ideas?
Last edited by panzerdampf on Thu Jul 14, 2005 7:18 am; edited 1 time in total |
|
Back to top |
|
|
Darknight Guru
Joined: 26 Jan 2004 Posts: 483 Location: Italy
|
Posted: Wed Jul 13, 2005 10:44 am Post subject: |
|
|
Have you tried compiling the module into the kernel?
Are you using the latest version of udev?
Maybe run etc-update to be sure you have updated etc files? |
|
Back to top |
|
|
garlicbread Apprentice
Joined: 06 Mar 2004 Posts: 182
|
Posted: Wed Jul 13, 2005 3:26 pm Post subject: |
|
|
I've also been having trouble using 058 with device-mapper in a similar way
056 was fine as I used to use a rule that would look up the kernel device "dm-[0-9]*"
but for some reason 058 is not picking up on this
I've tried this both with 2.6.11 and 2.6.12 (as I thought 2.6.12 may have put some changes in place that may have affected this)
typically I'd use a custom rule of
KERNEL="dm-[0-9]*", PROGRAM="/etc/udev/scripts/dmmapper.sh %M %m evms/", NAME="mapper/%c{1}" SYMLINK="%c{2}"
I've rulled out the possibility of my script being at fault by fiddling around with the rule
from what I can determine "dm-[0-9]*" isn't being recognised
perhaps loop devices are being affected in the same way?
I'll try and test this when I get back tonight
EDIT
sorry nope Loop is working fine for me
for my other problem this seems to be because the rules in 50-udev.rules is overiding one in 10-local.rules
but this isn't right perhaps this is a bug? |
|
Back to top |
|
|
panzerdampf n00b
Joined: 03 May 2003 Posts: 25 Location: Germany / Dresden
|
Posted: Thu Jul 14, 2005 7:17 am Post subject: |
|
|
solved ... CONFIG_HOTPLUG was not build in
I think the name and description (the helptext) for this option should be changed.
Because, the current one is a bit confusing and does not tell about the whole truth.
Quote: | Support for hot-pluggable devices
CONFIG_HOTPLUG:
This option is provided for the case where no in-kernel-tree
modules require HOTPLUG functionality, but a module built
outside the kernel tree does. Such modules require Y here.
|
Thanks for your answers. |
|
Back to top |
|
|
Mr Faber n00b
Joined: 14 Mar 2005 Posts: 47
|
Posted: Thu Jul 14, 2005 9:30 pm Post subject: |
|
|
I have a similar problem but HOTPLUG is build in my kernel. I have some loop devices which get mounted on boot (e.g. encrypted tmp directory with loop-aes). It works for a long time but suddenly stops. I think it has something to do with the baselayout update or udev. I have an amd64 system. The funny thing is that it works on my x86 like before without problems.
The automount of loop-devices failes on boot with this error
Quote: | Mounting local filesystems ...
/dev/loop2: No such file or directory
* Some local filesystem failed to mount
|
After login I can mount loop devices like always. The tmp directory too.
Does anyone know a solution?
cu
Mr Faber |
|
Back to top |
|
|
Mr Faber n00b
Joined: 14 Mar 2005 Posts: 47
|
|
Back to top |
|
|
|