Timeline for udev not running rule at boot?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2015 at 21:21 | comment | added | user.dz |
@dtmland , I think that block device is added too early before udevd can catch it.
|
|
| May 26, 2015 at 20:43 | comment | added | dtmland | Yes, I ran it with the walk attribute. I believe the mmcblk1 is the parent device? It's on unreleased SAMA5D3 based hardware. | |
| May 26, 2015 at 20:11 | comment | added | user.dz |
@dtmland, you run it with --attribute-walk I don't see any parent device. What's this hardware/embedded system ?
|
|
| May 26, 2015 at 19:53 | comment | added | user.dz |
@dtmland , Could I ask what hardware setup you are using? Could you post output of udevadm info --name=/block/mmcblk1 --attribute-walk?
|
|
| May 26, 2015 at 19:46 | comment | added | dtmland | Tested just now - didn't appear to make a difference. I am so stumped on this problem. | |
| May 26, 2015 at 18:41 | history | answered | user.dz | CC BY-SA 3.0 |