Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I currently use SME Server 5.5, with an Actiontec 56k Internal Hardware modem. I used Actiontec's guide to use setserial to setup my modem with little trouble and has been working fine for a long time.
Now I am looking to upgrade to 5.6 or even the beta 6, but there seems to be a problem with newer distros and the setserial command. For some reason I cannot use setserial on any of the ttyS* ports without getting a "port/device currently in use" or some similar error. From memory I had the same issue with MDK9 or Slack9, I cant remember which, but the exact same thing happened.
The modem is automatically detected at /dev/ttyS4. The SME setup only allows selection up to /dev/ttyS3, and changing the link to /dev/modem doesnt help. I can give it manual commands on ttyS4, and it dials, but the SME dialing software wont use it, so it must use the ttyS* port directly instead of /dev/modem.
Now there is no /etc/serial.conf file to edit, so I was wondering if anyone knows of a way to free the serial ports so I can edit them using setserial?
Is there a kernal option now that freezes serial data to Autodetect only? or are there new lockfiles or something?
I know using an external modem will solve all my problems, but I dont currently own one, and wont be able to get one for some time.
The only thing I didnt try now I think of it is using ttyS3 as a link to ttyS4, but I am not sure if that would work.
Thanks for the reply, but I have already fixed it.
Funny how I get a reply from Computing.Net within hours, when they are only a generic help forum, but I cant get the slightest reply for over a month from a dedicated Linux help site. Irony at its best I guess.