*** This bug is a duplicate of bug 315780 ***
https://bugs.launchpad.net/bugs/315780
udev (137-1) jaunty; urgency=low
* New upstream release:
- udevadm test no longer has force option.
- udevd has --resolve-names=early|late|never option.
- Group of IDE CD-ROM drives fixed. LP:
I think I am getting this bug as well, after installing Jaunty 64bit
Alpha 3. It displays what I believe is this error before usplash for me,
beeps about 10-15 times, and then goes I think to a black screen. I
tried then installing i386 instead and got a similar looking error,
although it only
I can second that - for me, with 2.6.28 the system is not even booting
up at all, as I'm using LUKS for file system encryption and the failing
udev prevents this from working. I have to go back to 2.6.24 to have the
system running at all.
--
udevd[926] unable to open /etc/udev/rules.d: no such
I am running a custom 2.6.29-rc2 on a crypted-root machine, and as kenzo
pointed out, it doesn't boot at all.
The machine was upgraded to jaunty from intrepid without any warnings or errors.
update-initramfs on a (old) working kernel/initrd causes this bug to
appear, too.
Afer some time, the
It appears on my ubuntu jaunty 64bit in early boot. Something different
in initrd creation not reflecting udev changes? It came up together with
Bug #318338 which is due to missing link /etc/udev/rules.d -
/lib/udev/rules.d in initrd. Is something missing for udev management in
Error: unable to open /etc/udev/rules.d: no such file or directory
I can confirm that this error occur in early boot of amd64 arch. system is not
able to load nvidia driver, i guess its related to udev error.
--
udevd[926] unable to open /etc/udev/rules.d: no such file or directory.
I am having this issue as well on an updated Jaunty 64 bit, updated from
Intrepid 64 (update-manager -d).
--
udevd[926] unable to open /etc/udev/rules.d: no such file or directory.
https://bugs.launchpad.net/bugs/318338
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu
Status: Incomplete = Confirmed
--
udevd[926] unable to open /etc/udev/rules.d: no such file or directory.
https://bugs.launchpad.net/bugs/318338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Actually, the nvidia thing is a different issue, assuming the driver is
installed, you need to add the -ignoreABI option to /etc/X11/xorg.conf. When
I did that, nvidia works fine.
2009/1/20 k1dugar k1du...@gmail.com
Error: unable to open /etc/udev/rules.d: no such file or directory
I can
Seems something in mkinitd ... on root filesystem, /etc/udev/rules.d is
hardlinked to /lib/udev/rules.d, while on initrd image this is not the case.
Again, this may be related to Bug #315979, which for me appeared on same update.
Maybe it is needed to check the initrd creation procedure, to
jaunty's udev now uses /lib/udev/rules.d, not /etc/udev/rules.d
** Changed in: ubuntu
Status: New = Incomplete
--
udevd[926] unable to open /etc/udev/rules.d: no such file or directory.
https://bugs.launchpad.net/bugs/318338
You received this bug notification because you are a member of
OK, well I have many more files in /lib/udev/rules.d
Still doesn't explain why the error occurs.
2009/1/18 Daniel T Chen crimsu...@yahoo.com
jaunty's udev now uses /lib/udev/rules.d, not /etc/udev/rules.d
** Changed in: ubuntu
Status: New = Incomplete
--
udevd[926] unable to open
12 matches
Mail list logo
