Tempest Posted November 3, 2015 Share Posted November 3, 2015 I've recently reinstalled Ubuntu on my computer and I'm having trouble getting AspeQT working again. Whenever I start it up and switch it to ttyS4 (my serial port) it gives me a "Cannot set serial port speed to 19200: Input/output error" message. Any idea what could cause this? It's not a permissions error or anything like that as far as I can tell. It worked before (last week as a matter of fact) so it's not the hardware. Quote Link to comment Share on other sites More sharing options...
Tempest Posted November 3, 2015 Author Share Posted November 3, 2015 And just like that it's working again. Weird. Quote Link to comment Share on other sites More sharing options...
Joey Z Posted November 3, 2015 Share Posted November 3, 2015 You may want to look into switching to RespeQt, as free AspeQt is no longer maintained. 2 Quote Link to comment Share on other sites More sharing options...
Tempest Posted November 3, 2015 Author Share Posted November 3, 2015 I didn't realize an alternative existed. I'll look into that. Quote Link to comment Share on other sites More sharing options...
Tempest Posted November 25, 2015 Author Share Posted November 25, 2015 I tried RespeQT and got the same error. Any idea why this is happening? Quote Link to comment Share on other sites More sharing options...
Tempest Posted November 25, 2015 Author Share Posted November 25, 2015 Now it's saying Cannot Clear DTR and RTS lines Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 13, 2015 Author Share Posted December 13, 2015 I'm still getting this error. Any help? Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted December 13, 2015 Share Posted December 13, 2015 Maybe try the RespeQt sub-forum? http://atariage.com/forums/topic/242422-respeqt-general-discussion/ Quote Link to comment Share on other sites More sharing options...
GoodByteXL Posted December 13, 2015 Share Posted December 13, 2015 I'm still getting this error. Any help? Sounds like contact problems? What's your interface? Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 14, 2015 Author Share Posted December 14, 2015 Sounds like contact problems? What's your interface? It's a SIO2PC style interface (can't remember who made it for me). But it works with windows so it can't be anything physical. Maybe try the RespeQt sub-forum? http://atariage.com/forums/topic/242422-respeqt-general-discussion/ I never knew we had one. I'll move this thread there. 1 Quote Link to comment Share on other sites More sharing options...
sloopy Posted December 14, 2015 Share Posted December 14, 2015 Sounds like you dont have permissions set correctly. Check to see if your user is added to the 'dialout' or 'modem' group... This would certainly cause this type of issue, alternatively check the permissions on the /dev/ttyS4 device. sloopy. Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 14, 2015 Author Share Posted December 14, 2015 I thought I had set those, but I can check again. Do you happen to have the commands handy? If not I can look it up later. Quote Link to comment Share on other sites More sharing options...
Joey Z Posted December 14, 2015 Share Posted December 14, 2015 (edited) I thought I had set those, but I can check again. Do you happen to have the commands handy? If not I can look it up later. start by doing 'ls -l' on /dev. it'll likely reveal that /dev/ttyS4 is set to root and dialout group access only. You can change the permissions, but they'll only last until a reboot, so the real fix is to add your user to the dialout group. the command is 'usermod -a -G dialout username_here' I think you'll have to log out, then back in for the group change to take effect. Edited December 14, 2015 by Joey Z Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 14, 2015 Author Share Posted December 14, 2015 Thanks, I'll try that when I get home. Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 15, 2015 Author Share Posted December 15, 2015 Tried that, no dice. BTW ls -l shows crw--w---- 1 root tty 4, 4 Dec 14 20:28 tty4 Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 15, 2015 Author Share Posted December 15, 2015 Ok it looks like something is physically wrong with one of my serial ports. I tried the other and it works fine. Quote Link to comment Share on other sites More sharing options...
charliecron Posted December 15, 2015 Share Posted December 15, 2015 (edited) Eh, I give up! Edited December 15, 2015 by charliecron Quote Link to comment Share on other sites More sharing options...
charliecron Posted December 15, 2015 Share Posted December 15, 2015 Tried that, no dice. BTW ls -l shows crw--w---- 1 root tty 4, 4 Dec 14 20:28 tty4 Thats tty4, you were looking for ttyS4. Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 15, 2015 Author Share Posted December 15, 2015 Thats tty4, you were looking for ttyS4. Yeah I realized that after I posted. As I stated above, it seems to be working with my other serial port so I'll just use that. I still don't know what the issue is though since if it was a bad port it wouldn't work with software in Windows. There's just something about that port that Ubuntu doesn't like. Thankfully I have two. Quote Link to comment Share on other sites More sharing options...
HiassofT Posted December 17, 2015 Share Posted December 17, 2015 As I stated above, it seems to be working with my other serial port so I'll just use that. I still don't know what the issue is though since if it was a bad port it wouldn't work with software in Windows. There's just something about that port that Ubuntu doesn't like. Thankfully I have two.It could be that some other (background-)process is accessing /dev/ttyS4 and thus disabling access for aspeqt/respeqt. You can check for that with one of the following 2 commands (run as user root or use sudo before the commands): lsof /dev/ttyS4or fuser -v /dev/ttyS4 I've had a lot of "fun" with the modemmanager daemon which is installed by default on most desktop linux distributions. Sometimes it would hook a serial port forever (maybe got stuck during modem detection or something like that). I'm sure there's some way to configure the ports modemmanager should use but since I have no use for modemmanager I usually just do an "apt-get --purge remove modemmanager" and everything's fine so long, Hias Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 17, 2015 Author Share Posted December 17, 2015 Interesting. I'll give that a try tonight. Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 18, 2015 Author Share Posted December 18, 2015 The first command produced this output: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. The second command did nothing Quote Link to comment Share on other sites More sharing options...
HiassofT Posted December 18, 2015 Share Posted December 18, 2015 The first command produced this output: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. The second command did nothing OK, that indicates noone else is using the port. Hmmm... Just to be sure: did you run these commands when AspeQT reported errors with /dev/ttyS4? If yes then the issues are caused by something else (no idea what, though). Your descriptions read like the AspeQT issues are somewhat intermittent, so it's important to know you didn't test in one of the "working fine" moments. so long, Hias Quote Link to comment Share on other sites More sharing options...
Tempest Posted December 18, 2015 Author Share Posted December 18, 2015 Lately the error has been consistent though. I'll play around with it a bit more tonight and see. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.