| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 40533 | 2003-12-10 12:03:00 | Linux and ttys0 | mikebartnz (21) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 199202 | 2003-12-10 12:03:00 | Hi there all. Have just installed Fedora and having a little trouble getting my external modem working. It is on Com1 or ttys0. I have tried setserial /dev/ttys0 and just get an I/O error. When querying the modem from kppp the tr led lights up then it says modem not responding. Any help would be much appreciated. |
mikebartnz (21) | ||
| 199203 | 2003-12-10 12:41:00 | Try using ttyS0. Everything in linux is CaSe sensitive :) | b1naryb0y (3) | ||
| 199204 | 2003-12-11 07:24:00 | Yes that was a bit slack of me for not noticing that it was a capital S. Had a play around with setserial but still can't get my modem to work | mikebartnz (21) | ||
| 199205 | 2003-12-11 08:17:00 | By "play around" do you mean that you also tried configuring using 1-3 as well as 0? I have noticed that some distros seem to pop the modem on unusual locations :) |
Gorela (901) | ||
| 199206 | 2003-12-11 11:12:00 | Yes I did try others but the one it was originaly on and is back on is what is set in the bios. As stated above in kppp when querying the modem the tr led goes on then it says modem not responding. In previous versions I had mapped it to /dev/modem but they say that is old hat :D now. | mikebartnz (21) | ||
| 199207 | 2003-12-11 22:48:00 | Something seems a bot odd here - external serial port modems normally "just go". Does Fedora still call the GUI network configuration tool "redhat-config-network"? If so, I suggest you start it (or the equivalent tool) and check the devices tab for the modem. If the modem is there, remove it, add it again, then reactivate. Normally this would get the modem going. JohnD |
JohnD (509) | ||
| 199208 | 2003-12-11 22:50:00 | P.S. You should check the hardware tab first. |
JohnD (509) | ||
| 199209 | 2003-12-11 22:59:00 | Maybe setserial has stuffed the port settings up. Generally for standard Com ports, ie. Com1-4 setserial is not required. Setserial should only really be used if you want to add more Com ports from Com5 onwards or to change the standard Com port settings. |
b1naryb0y (3) | ||
| 199210 | 2003-12-12 03:30:00 | Have a look with dmesg and see what serial ports the Linux knows about. If it says it has found ttyS0 and ttyS1, that's what it knows about. I haven't had to do this for a long time, but I seem to remember having a command which just looked for modems and set /dev/modem appropriately. O: That might be the problem. Just about all the modem using software knows that there will be a logical link "/dev/modem" which it can talk to. |
Graham L (2) | ||
| 199211 | 2003-12-12 09:04:00 | dmesg certainly gives a bit of info. It found ttyS0. As I stated setting the /dev/modem is old hat :D now although I don't know about pci modems. In kppp you can point to /dev/ttyS0 as your modem. I did try it with the same results of the tr led on the modem lighting up and then "modem not responding". This is bugging me as I had no problems in RH9. Not related but I get two errors on close down 1) mouse services not closing down. 2) It has four goes at unmounting /usr saying it is busy on the first three. This doesn't seem right. Thanks for your time |
mikebartnz (21) | ||
| 1 2 | |||||