Annotated edit history of
ENODEV version 4, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
PerryLorier |
1 |
!!!No such device |
| |
|
2 |
|
| |
|
3 |
The device you are trying to access doesn't exist, or the drivers for this device aren't loaded. This can occur if you refer to a file in /dev that has no driver loaded for it, or when loading a driver if no hardware exists. |
| 4 |
JohnMcPherson |
4 |
|
| |
|
5 |
Note the following quote from open(2) in the Errors section: |
| |
|
6 |
;ENODEV: pathname refers to a device special file and no corresponding device exists. (This is a Linux kernel bug - in this situation [ENXIO] must be returned.) |
| 2 |
JohnMcPherson |
7 |
|
| |
|
8 |
It is also quite common to see this under linux if you try to load a device driver and the driver can't find the corresponding hardware (for example, you've given the driver the wrong options). |
| 3 |
JohnMcPherson |
9 |
|
| |
|
10 |
This message can also be given when a process has a file handle open for a removable device (such as a [USB] or [SCSI]) which is then removed... further use of the file handle should result in this error message. |
| 1 |
PerryLorier |
11 |
|
| |
|
12 |
Compare [ENOMEDIUM] |
