uinput on headless system ...
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Any thoughts on this? or can you redirect me to an ongoing mailing list about the kernel input system
Thanks in advance ...
Hi Roberto,
Quoted 6 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
Thanks.
Signature · 1 line
Dmitry
Hi Roberto,
Quoted 10 lines · Dmitry Torokhov
Hi Roberto,
Quoted 6 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Quoted 4 lines
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
As Dmitry said, uinput is independent of any attached hardware. You might want to see how we managed to create new devices through uinput by looking at libevdev[1] (see libevdev/libevdev-uinput.c).
You might actually also want to use libevdev instead of manually doing the ioctls and processing of all the small things :)
Cheers,
Benjamin
Yes the uinput driver is compiled as a module and loaded before running the test app that I have (double checked with modprobe and lsmod). The same code has been compiled for my laptop and everything loads and works fine when sending events to the input subsystem. I mentioned the physical keyboard issue because that's what made it work: SCENARIO1 the headless motherboard starts without a keyboard and both the module and the app loads but no events get injected and the problem occurs when writing to the /dev/uinput device, SCENARIO2 I connect a physical keyboard and all goes well. I looked at the libevdev before and sinced my code ended up working on my laptop I discarded the library. I saw the libevdev-uinput.c you recommended, I think I'm following the same rationale.
Thanks for the replies ...
This is the code I'm using that fails at the end when writing to the /dev/uinput device:
int uinputDev;
struct uinput_user_dev device;
memset(&device, 0, sizeof device);
uinputDev = open("/dev/uinput",O_WRONLY | O_NONBLOCK);
strcpy(device.name,"test remote");
device.id.bustype=BUS_USB;
device.id.vendor=1;
device.id.product=1;
device.id.version=1;
if (write(uinputDev,&device,sizeof(device)) != sizeof(device))
{
fprintf(stderr, "error setup\n");
}
if (ioctl(uinputDev,UI_SET_EVBIT,EV_KEY) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_LEFT) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_UP) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_DOWN) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_RIGHT) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_ENTER) < 0)
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_DEV_CREATE) < 0)
{
fprintf(stderr, "error create\n");
}
struct input_event event;
memset(&event, 0, sizeof(event));
event.type = EV_KEY;
event.code = KEY_UP;
event.value = 1;
gettimeofday(&event.time,NULL);
if (write( uinputDev, &event, sizeof(struct input_event)) !=
sizeof( struct input_event) ) {
fprintf(stderr, "Error on send_event");
return -1;
}
memset(&event, 0, sizeof(event));
event.type = EV_KEY;
event.code = KEY_UP;
event.value = 0;
gettimeofday(&event.time,NULL);
if (write( uinputDev, &event, sizeof(struct input_event)) !=
sizeof( struct input_event) ) {
fprintf(stderr, "Error on send_event");
return -1;
}Quoted 32 lines · Benjamin Tissoires
Hi Roberto,
Quoted 9 lines · Dmitry Torokhov
Hi Roberto,
Quoted 6 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Quoted 4 lines
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
As Dmitry said, uinput is independent of any attached hardware. You might want to see how we managed to create new devices through uinput by looking at libevdev[1] (see
libevdev/libevdev-uinput.c).You might actually also want to use libevdev instead of manually doing the ioctls and processing of all the small things :)
Cheers,
Benjamin[1] http://www.freedesktop.org/wiki/Software/libevdev/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 50 lines · Roberto Alejandro Espi Munoz
Yes the uinput driver is compiled as a module and loaded before running the test app that I have (double checked with modprobe and lsmod). The same code has been compiled for my laptop and everything loads and works fine
when sending events to the input subsystem. I mentioned the physical
keyboard issue because that's what made it work: SCENARIO1 the headless motherboard starts without a keyboard and both the module and the app loads but no events get injected and the problem occurs when writing to the/dev/uinputdevice, SCENARIO2 I connect a physical keyboard and all goes well. I looked at the libevdev before and sinced my code ended up working on my laptop I discarded the library. I saw thelibevdev-uinput.cyou recommended, I think I'm following the same rationale.Thanks for the replies ...
This is the code I'm using that fails at the end when writing to the
/dev/uinputdevice:int uinputDev; struct uinput_user_dev device; memset(&device, 0, sizeof device); uinputDev = open("/dev/uinput",O_WRONLY | O_NONBLOCK); strcpy(device.name,"test remote"); device.id.bustype=BUS_USB; device.id.vendor=1; device.id.product=1; device.id.version=1; if (write(uinputDev,&device,sizeof(device)) != sizeof(device)) { fprintf(stderr, "error setup\n"); } if (ioctl(uinputDev,UI_SET_EVBIT,EV_KEY) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_LEFT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_UP) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_DOWN) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_RIGHT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_ENTER) < 0)
Quoted 9 lines
fprintf(stderr, "error evbit key\n");
if (ioctl(uinputDev,UI_DEV_CREATE) < 0)
{
fprintf(stderr, "error create\n");
}
struct input_event event;Just to be sure, is there any sleep here or way to ensure your motherboard actually opened the device here?
If not, you might simply send the events too early, when nobody reads them, and thus you think you did not receive them.
Cheers,
Benjamin
Quoted 65 lines
memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 1; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; } memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 0; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; }Quoted 37 lines · Benjamin Tissoires
Hi Roberto,
Quoted 13 lines · Dmitry Torokhov
Hi Roberto,
Quoted 7 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Quoted 4 lines
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
As Dmitry said, uinput is independent of any attached hardware. You might want to see how we managed to create new devices through uinput by looking at libevdev[1] (see
libevdev/libevdev-uinput.c).You might actually also want to use libevdev instead of manually doing the ioctls and processing of all the small things :)
Cheers,
Benjamin[1] http://www.freedesktop.org/wiki/Software/libevdev/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Well yes ... the code I posted is actually part of a TCP server client connection. One part of the code gets executed up to the point you mentioned. The part where the keys get sent only executes when receiving the network command, so yes, there is a time lapse between one part and the other.
Quoted 133 lines · Benjamin Tissoires
Quoted 50 lines · Roberto Alejandro Espi Munoz
Yes the uinput driver is compiled as a module and loaded before running the test app that I have (double checked with modprobe and lsmod). The same code has been compiled for my laptop and everything loads and works fine
when sending events to the input subsystem. I mentioned the physical
keyboard issue because that's what made it work: SCENARIO1 the headless motherboard starts without a keyboard and both the module and the app loads but no events get injected and the problem occurs when writing to the/dev/uinputdevice, SCENARIO2 I connect a physical keyboard and all goes well. I looked at the libevdev before and sinced my code ended up working on my laptop I discarded the library. I saw thelibevdev-uinput.cyou recommended, I think I'm following the same rationale.Thanks for the replies ...
This is the code I'm using that fails at the end when writing to the
/dev/uinputdevice:int uinputDev; struct uinput_user_dev device; memset(&device, 0, sizeof device); uinputDev = open("/dev/uinput",O_WRONLY | O_NONBLOCK); strcpy(device.name,"test remote"); device.id.bustype=BUS_USB; device.id.vendor=1; device.id.product=1; device.id.version=1; if (write(uinputDev,&device,sizeof(device)) != sizeof(device)) { fprintf(stderr, "error setup\n"); } if (ioctl(uinputDev,UI_SET_EVBIT,EV_KEY) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_LEFT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_UP) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_DOWN) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_RIGHT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_ENTER) < 0)Quoted 9 lines
fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_DEV_CREATE) < 0) { fprintf(stderr, "error create\n"); } struct input_event event;Just to be sure, is there any sleep here or way to ensure your motherboard actually opened the device here?
If not, you might simply send the events too early, when nobody reads them, and thus you think you did not receive them.Cheers,
BenjaminQuoted 24 lines
memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 1; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; } memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 0; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; }Quoted 36 lines
Quoted 33 lines · Benjamin Tissoires
Hi Roberto,
Quoted 10 lines · Dmitry Torokhov
Hi Roberto,
Quoted 6 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Quoted 4 lines
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
As Dmitry said, uinput is independent of any attached hardware. You might want to see how we managed to create new devices through uinput by looking at libevdev[1] (see
libevdev/libevdev-uinput.c).You might actually also want to use libevdev instead of manually doing the ioctls and processing of all the small things :)
Cheers,
Benjamin[1] http://www.freedesktop.org/wiki/Software/libevdev/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html--
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Bump ... any other insights or suggestions I could try?
Quoted 144 lines · Roberto Alejandro Espi Munoz
Well yes ... the code I posted is actually part of a TCP server client connection. One part of the code gets executed up to the point you mentioned. The part where the keys get sent only executes when receiving the network command, so yes, there is a time lapse between one part and the other.
Quoted 135 lines · Benjamin Tissoires
Quoted 50 lines · Roberto Alejandro Espi Munoz
Yes the uinput driver is compiled as a module and loaded before running the test app that I have (double checked with modprobe and lsmod). The same code has been compiled for my laptop and everything loads and works fine
when sending events to the input subsystem. I mentioned the physical
keyboard issue because that's what made it work: SCENARIO1 the headless motherboard starts without a keyboard and both the module and the app loads but no events get injected and the problem occurs when writing to the/dev/uinputdevice, SCENARIO2 I connect a physical keyboard and all goes well. I looked at the libevdev before and sinced my code ended up working on my laptop I discarded the library. I saw thelibevdev-uinput.cyou recommended, I think I'm following the same rationale.Thanks for the replies ...
This is the code I'm using that fails at the end when writing to the
/dev/uinputdevice:int uinputDev; struct uinput_user_dev device; memset(&device, 0, sizeof device); uinputDev = open("/dev/uinput",O_WRONLY | O_NONBLOCK); strcpy(device.name,"test remote"); device.id.bustype=BUS_USB; device.id.vendor=1; device.id.product=1; device.id.version=1; if (write(uinputDev,&device,sizeof(device)) != sizeof(device)) { fprintf(stderr, "error setup\n"); } if (ioctl(uinputDev,UI_SET_EVBIT,EV_KEY) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_LEFT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_UP) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_DOWN) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_RIGHT) < 0) fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_SET_KEYBIT, KEY_ENTER) < 0)Quoted 9 lines
fprintf(stderr, "error evbit key\n"); if (ioctl(uinputDev,UI_DEV_CREATE) < 0) { fprintf(stderr, "error create\n"); } struct input_event event;Just to be sure, is there any sleep here or way to ensure your motherboard actually opened the device here?
If not, you might simply send the events too early, when nobody reads them, and thus you think you did not receive them.Cheers,
BenjaminQuoted 62 lines
memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 1; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; } memset(&event, 0, sizeof(event)); event.type = EV_KEY; event.code = KEY_UP; event.value = 0; gettimeofday(&event.time,NULL); if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) ) { fprintf(stderr, "Error on send_event"); return -1; }Quoted 33 lines · Benjamin Tissoires
Hi Roberto,
Quoted 10 lines · Dmitry Torokhov
Hi Roberto,
Quoted 6 lines · Roberto Alejandro Espi Munoz
Hello ... I've been searching around the web for a specific mailing list for the uinput driver but couldn't find any. I managed to create an example app that injects keyboard events to the running linux kernel succesfully when I have a keyboard attached to the computer. However if I run it on a keyboardless machine, like a standalone motherboard, the uinput device fails to open.
Quoted 4 lines
uinput driver does not depend on presence of a physical keyboard. I'd start looking whether uinput module is enabled on your headless box and if it is a module verify that it is loaded.
As Dmitry said, uinput is independent of any attached hardware. You might want to see how we managed to create new devices through uinput by looking at libevdev[1] (see
libevdev/libevdev-uinput.c).You might actually also want to use libevdev instead of manually doing the ioctls and processing of all the small things :)
Cheers,
Benjamin[1] http://www.freedesktop.org/wiki/Software/libevdev/
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.htmlSignature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 2 lines · Roberto Alejandro Espi Munoz
Bump ... any other insights or suggestions I could try?
You can check what error you are getting when trying to open the device and that might give you idea.
Thanks.
Signature · 1 line
Dmitry
The error is produced when the write operation doesn't return the same number of bytes as the one requested to write. Is there any other way of checking a specific error message on files associated with devices?
if (write( uinputDev, &event, sizeof(struct input_event)) != sizeof( struct input_event) )
{
fprintf(stderr, "Error on send_event");
return -1;}
Quoted 8 lines · Dmitry Torokhov
Quoted 2 lines · Roberto Alejandro Espi Munoz
Bump ... any other insights or suggestions I could try?
You can check what error you are getting when trying to open the device and that might give you idea.
Thanks.
Quoted 10 lines · Roberto Alejandro Espi Munoz
The error is produced when the write operation doesn't return the same number of bytes as the one requested to write. Is there any other way of checking a specific error message on files associated with devices?
if (
write( uinputDev, &event, sizeof(struct input_event))!=sizeof( struct input_event)){ fprintf(stderr, "Error on send_event"); return -1;}
1. Could you please stop top-posting
2. man errno; man strerror
3. I wonder what was the return value from write() and what is sizeof(struct inptu_event) on your system.
4. Please do take care when describing your problem. In your original email you said that "... the uinput device fails to open".
5. Is it system with 64 bit kernel and 32 bit userspace by any chance?
Thanks.
Quoted 15 lines · Dmitry Torokhov
Quoted 11 lines
Quoted 3 lines · Roberto Alejandro Espi Munoz
Bump ... any other insights or suggestions I could try?
You can check what error you are getting when trying to open the device and that might give you idea.
Thanks.
Signature · 1 line
Dmitry