/dev/modem bug
Posts: 724
I have seen a few posts on this forum concerning problems with modems not being set properly, ie not at /dev/modem or when the symlink is created it not "sticking" after a reboot. After discussing this issue with Warren it seems that there is a problem with autodetection and /dev/modem.
In order to create a symlink from /dev/modem to the actual serial device, /dev/ttySx you can do the following to make it "stick".
Open a terminal and su to root. Open your favorite text editor and open the following file:
/etc/modutils/modem
Next add the following lines to /etc/modutils/modem:
pre-install serial rm /dev/modem
post-install serial ln -s /dev/ttySx /dev/modem
Where x is the comm port that your modem uses, ie ttyS0 is comm 1, ttyS1 is comm 2 and so on. Save the file and exit your editor. Next, still as root, run the following:
update-modutils
Exit out of the terminal and reboot.
Now you should have a symlink from /dev/modem to the comm port that your modem uses.
Again thanks to Warren for the solution.
HTH,
MYoung
I checked back over the post on MEPISdev...
Posts: 724
to make sure but according to Warren you just run update-modules as root. Now I see that mistyped the command, thanks for pointing that out.
After you make the change to /etc/modutils/modem run update-modules. Of course as I said, all must be run as root.
Later,
MYoung
_____________________________________________________________
I don't work here. I'm a consult.
HCFPCI Modem
Posts: 1
I have this described problem and tried the given solution.
It does not work for me, but this could be because I don't know what COM port or TtyX my modem is at. Is there a way to find out what is at the different TtyX ports, or another way to set the modem.
Frits de Koning
alternative solution to /dev/modem problem
Posts: 7
Hi,
I had the exact same problem of the /dev/modem symlink being changed every time I rebooted. My modem is at /dev/ttySHSF0. For some reason the method posted above didn't work for me, so I had to figure out a way to run the commands
rm /dev/modem
ln -s /dev/ttySHSF0 /dev/modem
every time the system boots. In the end I settled on adding them to the end of a shell script in the /etc/rcS.d directory. The scripts in there are run every boot. I chose the bootmisc.sh file which on my system is S55bootmisc.sh. This worked fine and seems like a quicker and more direct solution than the one mentioned. Any comments?
-Basil.
It Worked !
Posts: 229
Thanks ever so much Basil, your alternative method worked, and I am an amature.
Carl
modem install
Posts: 38
i've been following this forum as a newbie trying to get his trendware external modem running. In the bootup I see a message about a modprobe with an exclamation mark and my sense is that the modem isn't getting seen at all. querying the modem at any com port only yields an uncapable connection message. I tried the /etc/modutils/modem command in root but I get a permission denied answer. I'm wondering if the promepis cd'sthat I burned from a download and then installed on my hard drive missed something in the install. well, any help would be considerably appreciated.
thanks
mike

Bloody TTYS0
Posts: 88
Tried em all, with no success, is there a problem because I installed the system on my daughters machine using my ADSL connection?
Dunno!
Anyway, I am unable to get KPP to probe "/dev/modem" or "/dev/TTYSx" ie. any serial device using any of the above?
On boot the system just gives an error message that it is unable to locate any TTY.
Elp needed in Oz,
jim
I shot an arrow into the air. It stuck! Anon

Bloody ttyS0
Posts: 88
Further to the above, I've now noticed that on the install CD, tty ports are recognised, booting the 2.4 kernel, they are recognised, so it seems that the problem is in the 2.6 kernel where something is not a little confused about the serial ports?!
Any further thortz?
I shot an arrow into the air. It stuck! Anon
Thank you so much for posting
Posts: 83
Thank you so much for posting this!! I think you meant
/sbin/update-modules.modutils instead up update-modutils?