Timeline for Kernel recognizes USB device but then I can't find it in /sys or /dev
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 1, 2014 at 0:39 | history | edited | slm♦ | CC BY-SA 3.0 | added 3313 characters in body |
| Dec 31, 2013 at 23:53 | vote | accept | Stabledog | ||
| Dec 31, 2013 at 23:52 | comment | added | Stabledog | Ok, that helped me get oriented. I've found a device under /sys/bus/usb/devices/2-1.2 which corresponds to my phone, and 'udevadm info -a -p ...' applied to that path does dump out a bunch of udev-property style info. So now I hope to be able to follow the standard guides! :) Thanks. | |
| Dec 31, 2013 at 21:41 | comment | added | slm♦ | @Stabledog - Yes to a point. I would expect that if the kernel has successfully detected /dev/sdb1 then you'd have corresponding entries under /sys. I would investigate the /sys more thoroughly, there is likely a device handle hiding in there that corresponds to /dev/sdb1. You can walk around the tree using this command: udevadm info -a -p /sys/class/...` you'll need to add on the appropriate device in place of the dots (...). | |
| Dec 31, 2013 at 20:12 | comment | added | Stabledog | The distribution is Ubuntu 13.04 (as stated in the question). I have considered that I need to write a udev rule, but how can I do that if I can't find the device in /sys? That's really the question... I'm aware that there are plenty of resources and guidance for udev rules, but don't they all depend on being able to first find the darn thing in the kernel tree? | |
| Dec 31, 2013 at 16:49 | history | answered | slm♦ | CC BY-SA 3.0 |