this might help those stuck with a sm56 softmodem -sdg- PS: If this does not work, send me a mail, and i have a more "violent" way that might work
-----Forwarded Message----- > From: Jacques Goldberg <[EMAIL PROTECTED]> > To: Adam <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Help on SM5k motrolla > Date: 26 May 2002 09:04:24 +0300 > > On Sat, 25 May 2002, Adam wrote: > > > ive switched on linux recently . my sm56k modem 0f motrolla was perfectly > > worked on windows but on linux it was not detecting it. I downloaded the > > http://e-www.motorola.com/collateral/SM56_5.1_I386.rpm and install itbut > > it was not the updateddriver. as it initialized modem but did'nt connect to > > the isp while from windows it is connected. > > Type uname -r , it will tell you which kernel you are using, for > example something like 2.4.2 > Then open Web page http://linmodems.technion.ac.il/resources.html , > look for Motorola, and read there if you are using a kernel for which the > file which you installed has a chance to succeed. Read from there the page > http://e-www.motorola.com/collateral/SM56_DRIVERS.html#linux and the page > http://linmodems.technion.ac.il/Motorola.html (both are links available > in the Motorola section of http://linmodems.technion.ac.il/resources.html) > > If your kernel is one which can use that driver, then go to page: > http://linmodems.technion.ac.il/post-install.html and first try to use > program minicom then wvdial as indicated there. > You have to go through four steps. If you try to jump straight to the > end and give us no details, we of course cannot help you: > 1-install the software making sure there are no error messages. Remember > that with any computer you can always write a program and load it in > memory, but this does not imply that it will do what you wanted! > 2-use minicom to see if you can communicate with the modem software > using any AT command other than ATDT, for example ATI0 to ATI10. Remember > that a program made to talk to the user and successfully loaded in memory > will talk to the user even if it also contains a second part made to talk > to some modem hardware which is not necessarily there. > 3-Use ATDTxxxx where xxxxxx stands for your ISP's number, see on the > screen if the computer reached message CONNECT or gives an error before > that. If it works, hang the modem. If it fails, send us all the details. > 4-If 3 was successfull try to connect to the ISP with wvdial. > > For further help on this list, let us know which Linux distribution you > use, which kernel, which driver file you installed (the one I stored on > http://linmodems.technion.ac.il/resources.html, referred above seems, from > its name, more recent than yours if you correctly copied the name of the > file which you downloaded), and send the log seen on console when starting > wvdial until the failure, and the few lines which you will find close to > the end of file /var/log/messages which are related to the attempt to use > the modem. > > Your claim that you need an updated driver because you connect to your > ISP with the other system but not with Linux needs solid confirmation. For > example, you could see in /var/log/messages the logging of LCP requests > which are not satisfied. In that case, make sure you have Stupid Mode = > yes in the wvdial configuration file. Your ISP may assume that all their > customers use the other system, thus by default expect the other's system > manufacturer's copyrighted password procedure (MCHAP). > You may have the wrong driver, or you may have the right one. If you > have the right one, your failure is due to some wrong setting, not to the > driver. > > Jacques > -- To unsubscribe, send mail to [EMAIL PROTECTED] with the body "unsubscribe ilug-cal" and an empty subject line. FAQ: http://www.ilug-cal.org/help/faq_list.html
