Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Tested just now - didn't appear to make a difference. I am so stumped on this problem. Commented May 26, 2015 at 19:46
  • @dtmland , Could I ask what hardware setup you are using? Could you post output of udevadm info --name=/block/mmcblk1 --attribute-walk? Commented May 26, 2015 at 19:53
  • @dtmland, you run it with --attribute-walk I don't see any parent device. What's this hardware/embedded system ? Commented May 26, 2015 at 20:11
  • 1
    Yes, I ran it with the walk attribute. I believe the mmcblk1 is the parent device? It's on unreleased SAMA5D3 based hardware. Commented May 26, 2015 at 20:43
  • 2
    @dtmland , I think that block device is added too early before udevd can catch it. Commented May 26, 2015 at 21:21