Re: bluetoothd not starting at boot with udev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Bastien:

Bastien Nocera wrote:
> On Sat, 2009-07-11 at 18:26 -0500, Mario_Limonciello@xxxxxxxx wrote:
>   
>
> Your udev scripts are missing a call to "udevadm trigger --retry-failed"
>
> Cheers
>   
Currently in the Ubuntu udev init script there is a call to 'udevadm
trigger' (without any arguments).  Without any arguments it appears the
default is "--type=devices".  When I add --type=failed (--retry-failed
is deprecated), the system fails to boot up to X.  If I return it back
to it's old state and add a second call right afterward of
"--type=failed", there is no difference in behavior.  bluetoothd still
fails to spawn by the udev rule.
-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@xxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux