Mitt27 Posted May 27, 2013 #1 Posted May 27, 2013 Hi, I have been running with the 3202 build for a few weeks now but I am still receiving issues due to the following mentioned in the messages file. console: TCGETS: Input/output error^M console: TCGETS: Input/output error^M Does anybody else have these issues or know how to resolve them? Thanks
Schnapps Posted May 27, 2013 #2 Posted May 27, 2013 This is what i see in the logfiles May 27 20:54:38 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:38 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:38 scemd: write to uart2 error, error=(5)Input/output error May 27 20:54:39 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:39 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:40 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:40 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:41 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:41 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:41 scemd: write to uart2 error, error=(5)Input/output error May 27 20:54:42 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:42 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:43 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:43 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:44 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:44 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:44 scemd: write to uart2 error, error=(5)Input/output error May 27 20:54:45 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:45 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:46 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:46 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:47 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:47 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed May 27 20:54:48 scemd: write to uart2 error, error=(5)Input/output error May 27 20:54:48 usbipd: syno_usbipd_func.c:2796(No child processes) invalid parameter May 27 20:54:48 usbipd: stub_server.c:1057(No child processes) add listen socket to select failed
pLANner Posted May 28, 2013 #4 Posted May 28, 2013 Hi, I have been running with the 3202 build for a few weeks now but I am still receiving issues due to the following mentioned in the messages file. console: TCGETS: Input/output error^M console: TCGETS: Input/output error^M Does anybody else have these issues or know how to resolve them? Thanks Yes. Try to enable the COM-port in the motherboard BIOS. It's solved my problem.
Mitt27 Posted May 28, 2013 Author #5 Posted May 28, 2013 Hi, I have been running with the 3202 build for a few weeks now but I am still receiving issues due to the following mentioned in the messages file. console: TCGETS: Input/output error^M console: TCGETS: Input/output error^M Does anybody else have these issues or know how to resolve them? Thanks Yes. Try to enable the COM-port in the motherboard BIOS. It's solved my problem. Thanks for that, unfortunate my motherboard doesn't have a COM port, I have the biostar A68i-350
jokies Posted August 11, 2013 #6 Posted August 11, 2013 Hi, I have been running with the 3202 build for a few weeks now but I am still receiving issues due to the following mentioned in the messages file. console: TCGETS: Input/output error^M console: TCGETS: Input/output error^M Does anybody else have these issues or know how to resolve them? Thanks Yes. Try to enable the COM-port in the motherboard BIOS. It's solved my problem. I don't have one, either.
Recommended Posts