Yesterday I tryed to connect as "root" (I logged in as root and tryed to call my dial-up ISP using Kppp) but the following message appeared: --Connecting to: BOL-- "Looking for modem... Sorry, can't open modem" After this I tryed again logging in as user "adagilson" and this appeared: --Connecting to: BOL-- "Modem ready Sorry, the modem doesn't respond." Connection on Windows is fine! I need help. a. -- Adagilson Batista Bispo da Silva Bibliotecário FIOCRUZ-Centro de Pesquisa Aggeu Magalhães Fone 81 3302-6524
Is it possible that you have a Win-modem installed? If that's so, then it won't work under linux. Win-modems don't have their interface in firmware. You have to be running the interface on the CPU with Windows. Win-modems will have a cable attached to it which connects to the motherboard. Run the hardware profiles under YAST2 and see if the hardware detection sees it. If it does, then you have to configure it with YAST2. The config. tool should assign a port to your modem (like ttys4, for example, which corresponds to the PCI bus slot its in). If hardware detection doesn't see it, then open your computer to see if there's a Win-modem there. You'll have to replace it if there is, but when you install the new modem insert it into a different PCI slot. I had a problem where the new modem still wasn't recognized when I inserted it into the old Win-modem slot. The fact that the modem couldn't be found under root sounds like the hardware detection doesn't see it or it isn't configured. Address the issues mentioned and let me know what you see. Bill Porada On Friday 29 November 2002 03:07, Adagilson B B da Silva wrote:
Yesterday I tryed to connect as "root" (I logged in as root and tryed to call my dial-up ISP using Kppp) but the following message appeared: --Connecting to: BOL-- "Looking for modem... Sorry, can't open modem"
After this I tryed again logging in as user "adagilson" and this appeared: --Connecting to: BOL-- "Modem ready Sorry, the modem doesn't respond."
Connection on Windows is fine! I need help. a.
On Fri, 29 Nov 2002, Bill wrote:
Is it possible that you have a Win-modem installed? If that's so, then it won't work under linux. Win-modems don't have their interface in firmware. You have to be running the interface on the CPU with Windows.
This is old and outdated info you are giving. Some Win-modems can be made to work with Linux. See http://linmodems.org/ for details. Regards Ole
It may be old and outdated, but I am new to linux. I'm just relaying the experiences I've had. Yes, I understand that some Win-modems can be made to work with linux but not all. However, my approach to the whole Win-whatever thing is to totally divorce myself from Windows in whatever shape or form. Thanks for your input. Bill On Friday 29 November 2002 15:54, Ole Kofoed Hansen wrote:
On Fri, 29 Nov 2002, Bill wrote:
Is it possible that you have a Win-modem installed? If that's so, then it won't work under linux. Win-modems don't have their interface in firmware. You have to be running the interface on the CPU with Windows.
This is old and outdated info you are giving. Some Win-modems can be made to work with Linux.
See http://linmodems.org/ for details.
Regards
Ole
On Fri, 29 Nov 2002, Bill wrote:
It may be old and outdated, but I am new to linux. I'm just relaying the experiences I've had. Yes, I understand that some Win-modems can be made to work with linux but not all.
True.
However, my approach to the whole Win-whatever thing is to totally divorce myself from Windows in whatever shape or form.
OK, then let's call those socalled win-modems what they really are: software-controlled telephone line interfaces. This also makes it a lot easier to see some of the interesting stuff they could be used for. If you just need a plain old modem, get a hardware modem. On that we agree. If, however, you find the thought of a computerized, completely programmable telephone interesting, a soft-modem is for you. How about a phone that: - pages you about important email? - give unwanted callers an automatic response while letting friends through? - interfaces with your address-book application? - has voice dialing? - tells you the name of the caller? - will use Voice-over-IP if available? - can be a switchboard? (That also knows who is still at work - and not in a meeting.) - has a touch-tone gateway? (Press 1 if you want to ...) Most of these things are not possible with a traditional modem, but since a winmodem has its functionality primarily in software, it is only a matter of actually writing the software for it. Just some food for thought. Just because some people call it Win-something, it doesn't have to be totally bad. Regards Ole
Yes, it is a winmodem, but now with a pctel driver it could be made a linmodem. I made a install some week ago and it was connecting as "root". I've got to download Ximian Desktop and it was installed it. But, I never got myself connecting as user "adagilson". So I tried to make some alterations and now it's not connecting even as user "root". I just want to put my modem to connect again. a. Bill escreveu:
Is it possible that you have a Win-modem installed? If that's so, then it won't work under linux. Win-modems don't have their interface in firmware. You have to be running the interface on the CPU with Windows. Win-modems will have a cable attached to it which connects to the motherboard. Run the hardware profiles under YAST2 and see if the hardware detection sees it. If it does, then you have to configure it with YAST2. The config. tool should assign a port to your modem (like ttys4, for example, which corresponds to the PCI bus slot its in). If hardware detection doesn't see it, then open your computer to see if there's a Win-modem there. You'll have to replace it if there is, but when you install the new modem insert it into a different PCI slot. I had a problem where the new modem still wasn't recognized when I inserted it into the old Win-modem slot.
The fact that the modem couldn't be found under root sounds like the hardware detection doesn't see it or it isn't configured. Address the issues mentioned and let me know what you see.
Bill Porada
-- Adagilson Batista Bispo da Silva Bibliotecário FIOCRUZ-Centro de Pesquisa Aggeu Magalhães Fone 81 3302-6524
On Wednesday 04 December 2002 1:26 pm, Adagilson B B da Silva wrote:
Yes, it is a winmodem, but now with a pctel driver it could be made a linmodem. I made a install some week ago and it was connecting as "root". I've got to download Ximian Desktop and it was installed it. But, I never got myself connecting as user "adagilson". So I tried to make some alterations and now it's not connecting even as user "root". I just want to put my modem to connect again. a.
what alterations did you make? and to what? what dialer (kppp,kinternet,wvdial) are you using? and have you tried the others? What do the logs say? kinternet has a log if you right click the plug icon, and click view logs. To see Kppp's log there's a checkbox on the window. i think wvdial gives the info in the terminal window it opens. What happens if you hit query modem in the kppp setup window.Setup>Modem>query Modem. Does it return info about the modem? -- Franklin Maurer <nebbish@sprynet.com>
I tried Kppp (it worked some days ago). I used a shell command line to get the output messages from the system: ------------------------------------------ "linux: # kppp DCOPServer up and running. Opener: received SetSecret Opener: received SetSecret Opener: received OpenLock Opener: received OpendDevice error opening modem device ! Opener: received RemoveLock" After this wvdial was in test, but this error occured: --------------------------------------------- "linux:/ # wvdial --> WvDial: Internet dialer version 1.42 --> Initializing modem. --> Sending: ATZ --> Sending: ATQ0 --> Re-Sending: ATZ --> Modem not responding. linux:/ # -------------------------------------- Kppp setup was invoked trying to correct a pretended wrong location of my modem. So I tested it as /dev/ttys0: "Modem ready. Sorry, the modem doesn't respond." ...as ttys1, ttys2, ttyXX...: "The modem is busy" Permissions to /etc/resolv.conf was modified to allow others user than "root" to write to this file. "plugin passwordfd.so" was checked in /etc/ppp/peers/kppp. /etc/permissions.local was edited. And after this I tryed to reinstall the pctel-0.9.6 driver. I don't whether I should uninstall first the current driver or make a install over the current one, but it was done. Franklin Maurer escreveu:
what alterations did you make? and to what?
what dialer (kppp,kinternet,wvdial) are you using? and have you tried the others?
What do the logs say? kinternet has a log if you right click the plug icon, and click view logs. To see Kppp's log there's a checkbox on the window. i think wvdial gives the info in the terminal window it opens.
What happens if you hit query modem in the kppp setup window.Setup>Modem>query Modem. Does it return info about the modem?
Tonight, I'll try this last advise. Thanks for helping. a. -- Adagilson Batista Bispo da Silva Bibliotecário FIOCRUZ-Centro de Pesquisa Aggeu Magalhães Fone 81 3302-6524
participants (4)
-
Adagilson B B da Silva -
Bill -
Franklin Maurer -
Ole Kofoed Hansen