View previous topic :: View next topic |
Author |
Message |
odin_ago n00b
Joined: 07 Mar 2011 Posts: 47
|
Posted: Wed Dec 12, 2012 9:49 pm Post subject: [solved] Error msgs during boot caused by VirtualBox&ude |
|
|
Hello.
I have recently upgraded the whole system using emerge -auvND world, and after that I get the following errors during startup:
Code: | udevd[1229]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh'
'%UDEV
DIR%/VBoxCreateUSBNode.sh 189 0 09': No such file or directory
udevd[1230]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh'
'%UDEV
DIR%/VBoxCreateUSBNode.sh 189 128 09': No such file or directory
udevd[1300]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh'
'%UDEV
DIR%/VBoxCreateUSBNode.sh 189 129 09': No such file or directory
udevd[1301]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh'
'%UDEV
DIR%/VBoxCreateUSBNode.sh 189 1 09': No such file or directory
udevd[1303]: failed to execute '/lib/udev/%UDEVDIR%/VBoxCreateUSBNode.sh'
'%UDEV
DIR%/VBoxCreateUSBNode.sh 189 2 ff': No such file or directory
|
It seems to me that these errors are connected with VirtualBox and udev. The versions of these packages are now 4.1.22:0 and 171-r9:0, respectively.
Last edited by odin_ago on Sat Dec 15, 2012 2:29 pm; edited 1 time in total |
|
Back to top |
|
|
BT Guru
Joined: 13 Jun 2004 Posts: 318
|
Posted: Thu Dec 13, 2012 10:29 am Post subject: |
|
|
I believe this issue is caused by the commit for bug 442742. The commit correctly fixes the bug for >=virtualbox-4.2.2-r1 but causes a regression with virtualbox-4.1.22. |
|
Back to top |
|
|
odin_ago n00b
Joined: 07 Mar 2011 Posts: 47
|
Posted: Thu Dec 13, 2012 8:05 pm Post subject: |
|
|
So, is it OK to replace %UDEVDIR% with /lib/udev in the file 10-virtualbox.rules (by the way, I don't understand from the above links where this file should be located, but I hope
Code: | # find / -name 10-virtualbox.rules -print |
will suggest exactly one location. |
|
Back to top |
|
|
BT Guru
Joined: 13 Jun 2004 Posts: 318
|
Posted: Thu Dec 13, 2012 8:48 pm Post subject: |
|
|
This issue has now been fixed in virtualbox-4.1.22-r1. You just need to sync portage and update your system. |
|
Back to top |
|
|
odin_ago n00b
Joined: 07 Mar 2011 Posts: 47
|
Posted: Fri Dec 14, 2012 11:54 am Post subject: |
|
|
Didn't notice the update from yesterday. Thanks. |
|
Back to top |
|
|
ferreirafm Guru
Joined: 28 Jul 2005 Posts: 487 Location: Sao Paulo, Brazil
|
Posted: Tue Jan 08, 2013 11:18 am Post subject: |
|
|
The same problem remains for the binary version virtualbox-bin-4.1.22 |
|
Back to top |
|
|
Polynomial-C Retired Dev
Joined: 01 Jun 2003 Posts: 1432 Location: Germany
|
Posted: Thu Jan 10, 2013 2:00 pm Post subject: |
|
|
This is bug 451018 which was already fixed. _________________ The manual said "Requires Windows10 or better" so I installed GNU/Linux...
my portage overlay
Need a stage1 tarball? (Unofficial builds) |
|
Back to top |
|
|
|