> Save and exit from the editor. [root@localhost guest]# cat /etc/wvdial.conf [Dialer Defaults] Modem = /dev/ttySL0 Baud = 460800 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ISDN = 0 Modem Type = Analog Modem Phone = 048350760 ; Phone = <Target Phone Number> ; Username = <Your Login Name> ; Password = <Your Password> > Now type wvdial > You should see a number of messages including CONNECTED. > This is enough to know that the modem works. No, it never said CONNECTED, it looks like it didn't even try: [root@localhost guest]# wvdial --> WvDial: Internet dialer version 1.54.0 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Modem initialized. --> Configuration does not specify a valid login name. --> Configuration does not specify a valid password. [root@localhost guest]# Is it possible for ME to type AT commands to the modem, as I might do using Windows Hyperterminal app? > KDEFAX. > > This application too must be run as root unless you are willing to take the risk > of being hacked. This is because a hacker can visit your machine if the pseudo-file > /dev/ttySL0 is open to any user. Do you mean a "local" user (with access to my keyboard) or a remote Internet user? My Internet is via ethernet/ADSL, not the modem (which is attached to my home phone line). And local "users" are just my family, not hackers, so I am not sure I understand what danger there could be. I haven't phoned because I don't want to trouble you, I usually work on this stuff late at night. Thank you VERY much, Shimon On Tue, Dec 2, 2008 at 12:03 PM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Shimon, > You write: >> At this point the terminal stopped, I did not get a new >> ready-message/prompt. > This is perfectly normal and expected. > YOU MUST NOT DO ANYTHING IN THIS TERMINAL, UNTIL YOU WANT TO STOP THE MODEM > DRIVER. AT THAT TIME AND NOT BEFORE, USE CTRL-C TO STOP THE DRIVER. > > At this time, before trying to FAX, you must check that your modem works. > Please, while slmodemd is running in its terminal: > Open a new terminal > As root (you can use su to become root, no need to logout), do > wvdialconf /etc/wvdial.conf > This will find that your modem is /dev/ttySL0 > After wvdialconf stops, edit the file /etc/wvdial.conf > You will see a line with Phone > > It starts with ; which means it is disabled. > At the same place, add the line > Phone = 048350760 > > This is a modem at the Technion. Just to check that the modem works. > I am not allowed to supply the username and the password, of course. > Save and exit from the editor. > > Now type wvdial > You should see a number of messages including CONNECTED. > This is enough to know that the modem works. > You now can stop wvdial if it did not stop alone, again with CTRL-C, but do > not stop slmodemd > Now you can try faxing making sure that your FAX software is defined for > modem /dev/ttySL0 > Or if you do not know how to set the modem for that, you can type > ln -sf /dev/ttySL0 /dev/modem > > Your FAX software certainly knows how to use /dev/modem > > Jacques > > > > > > > Shimon Lebowitz wrote: >>> >>> Try that and report back. >> >> I downloaded the two packages you mentioned: >> ungrab-winmodem-20080126.tar.gz and slmodem-2.9.11-20080126 >> >> I followed the instructions you supplied (thank you, they were very >> clear!), >> and got these responses: >> ============================================ >> [root@localhost guest]# modprobe ungrab-winmodem >> [root@localhost guest]# modprobe slamr >> [root@localhost guest]# slmodemd -c USA /dev/slamr0 >> SmartLink Soft Modem: version 2.9.11 Dec 2 2008 09:37:17 >> symbolic link `/dev/ttySL0' -> `/dev/pts/5' created. >> modem `slamr0' created. TTY is `/dev/pts/5' >> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >> ================================================= >> >> At this point the terminal stopped, I did not get a new >> ready-message/prompt. >> >>> Then also look at the fax documentation which is provided in newer >>> slmodem-2.9.11.X.tar.gz packages. >> >> I also looked at the fax folder in slmodem-2.9.11-20080817.tar.gz >> but I did not see anything that helped me. >> >> I tried to send a fax using kdeprintfax (and the efax engine), and got >> this error: >> ==================================== >> Sending to fax using: /usr/bin/fax NAME="'guest'" DEV='ttySL0' >> PAGE='letter' send '0543212296' >> '/tmp/kde-guest/kdeprintfax_XJ8OO5oC' >> fax: version 0.9001114a7 (30 Jan 2002) >> fax: version 0.9001114a7 (30 Jan 2002) >> /tmp/kde-guest/kdeprintfax_XJ8OO5oC is postscript... >> Now sending fax to T0543212296 >> /usr/bin/efax: Tue Dec 2 11:13:44 2008 efax v 0.9a-001114 Copyright >> 1999 Ed Casas >> efax: 13:44 Error: can't open serial port /dev/ttySL0: Permission denied >> efax: 13:44 failed -> /tmp/kde-guest/kdeprintfax_XJ8OO5oC.001 >> efax: 13:44 done, returning 2 (unrecoverable error) >> There were errors (see T0543212296.log). >> ==================================== >> >> Are there more steps I missed? >> >> Thank you for your help! >> Shimon >> >> On Tue, Dec 2, 2008 at 2:50 AM, Antonio Olivares >> <olivares14031@xxxxxxxxx> wrote: >>> >>> Shimon, >>> >>> You have done the following right? >>> >>> The modem is supported by the Smartlink >>> plus the slmodemd helper utility. Read the >>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >>> guidance. >>> >>> >>> For 2.6.18.8.tex5 compiling drivers is necessary. As of October 2007 >>> the current packages at >>> http://linmodems.technion.ac.il/packages/smartlink/ are the >>> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz >>> >>> If you have not download ungrab-winmodem-20080126.tar.gz and >>> slmodem-2.9.11-20080126 since your kernel is < 2.6.25 or so. >>> >>> extract them with >>> $ tar -zxvf slmodem-2.9.11-20080126.tar.gz >>> $ cd slmodem-2.9.11-20080126 >>> $ make KERNEL_DIR=/lib/modules/2.6.18.8.tex5/build >>> $ make >>> $ su >>> passwd: >>> # make install >>> # tar -zxvf ungrab-winmodem-20080126.tar.gz >>> # cd ungrab-winmodem-20080126 >>> # make >>> # make install >>> # exit >>> $ su - >>> passwd: >>> # modprobe ungrab-winmodem >>> # modprobe slamr >>> # slmodemd -c USA /dev/slamr0 >>> >>> Try that and report back. >>> >>> Then also look at the fax documentation which is provided in newer >>> slmodem-2.9.11.X.tar.gz packages. >>> >>> Regards, >>> >>> Antonio >>> >>> >>> >>> --- On Mon, 12/1/08, Shimon Lebowitz <shimonleb@xxxxxxxxx> wrote: >>> >>>> From: Shimon Lebowitz <shimonleb@xxxxxxxxx> >>>> Subject: Shimon, Israel kernel 2.6.18.8.tex5 >>>> To: "discuss" <discuss@xxxxxxxxxxxxx> >>>> Date: Monday, December 1, 2008, 4:07 PM >>>> I have spent ages on the web site trying to figure out by >>>> myself what >>>> to do next, but nothing works. >>>> >>>> Please help me get my modem to work, I need to send a fax >>>> (NOT to connect to Internet, I do that via ethernet). >>>> >>>> I am using PCLinuxOS2007 and my modem is >>>> SmartLink SmartPCI562 56K Modem >>>> >>>> Thank you very much! >>>> Shimon >>>> ============================================================ >>>> >>>> Only plain text email is forwarded by the >>>> Discuss@xxxxxxxxxxxxx List Server, >>>> as HTML can contain viruses. Use as the email Subject >>>> Line: >>>> YourName, YourCountry kernel 2.6.18.8.tex5 >>>> With this Subject Line cogent experts will be alerted, and >>>> useful >>>> case names left in the Archive. >>>> YourCountry will enable Country specific guidance. Linux >>>> experts in YourCountry >>>> can be found through: >>>> http://www.linux.org/groups/index.html. >>>> They will know your Country's modem code, which may be >>>> essential for >>>> dialup service. >>>> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked >>>> by an >>>> Internet Provider mail filters. >>>> So in a day, also check the Archived responses at >>>> http://www.linmodems.org >>>> -------------------------- System information >>>> ---------------------------- >>>> CPU=i686, >>>> Linux version 2.6.18.8.tex5 (vaughan@localhost) (gcc >>>> version 4.1.1 >>>> 20060724 (prerelease) (4.1.1-4pclos2007)) #1 SMP Thu May 10 >>>> 11:36:58 >>>> WST 2007 >>>> scanModem update of: 2008_11_06 >>>> >>>> There are no blacklisted modem drivers in /etc/modprobe* >>>> files >>>> Attached USB devices are: >>>> ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W >>>> 3300U/4300U >>>> ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub >>>> ID 045e:0040 Microsoft Corp. Wheel Mouse Optical >>>> >>>> USB modems not recognized >>>> >>>> For candidate card in slot 02:0d.0, firmware information >>>> and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 02:0d.0 163c:3052 163c:3052 Modem: Smart Link >>>> Ltd. SmartLink >>>> SmartPCI562 56K Modem >>>> >>>> Modem interrupt assignment and sharing: >>>> --- Bootup diagnostics for card in PCI slot 02:0d.0 ---- >>>> ACPI: PCI Interrupt 0000:02:0d.0[A] -> GSI 21 (level, >>>> low) -> IRQ 20 >>>> 0000:02:0d.0: ttyS2 at I/O 0xd408 (irq = 20) is a 16450 >>>> 0000:02:0d.0: ttyS3 at I/O 0xd410 (irq = 20) is a 8250 >>>> Couldn't register serial port 0000:02:0d.0: -28 >>>> >>>> === Finished firmware and bootup diagnostics, next deducing >>>> cogent software. === >>>> >>>> Predictive diagnostics for card in bus 02:0d.0: >>>> Modem chipset detected on >>>> NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K >>>> Modem " >>>> CLASS=0703 >>>> PCIDEV=163c:3052 >>>> SUBSYS=163c:3052 >>>> IRQ=20 >>>> IDENT=slamr >>>> >>>> For candidate modem in: 02:0d.0 >>>> 0703 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K >>>> Modem >>>> Primary device ID: 163c:3052 >>>> Support type needed or chipset: slamr >>>> >>>> >>>> ----------------end Softmodem section -------------- >>>> The modem is supported by the Smartlink >>>> plus the slmodemd helper utility. Read the >>>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow >>>> through guidance. >>>> >>>> >>>> For 2.6.18.8.tex5 compiling drivers is necessary. As of >>>> October 2007 >>>> the current packages at >>>> http://linmodems.technion.ac.il/packages/smartlink/ are >>>> the >>>> ungrab-winmodem-20070505.tar.gz and >>>> slmodem-2.9.11-20080126.tar.gz >>>> >>>> Writing DOCs/Smartlink.txt >>>> ============ end Smartlink section ===================== >>>> >>>> Completed candidate modem analyses. >>>> >>>> The base of the UDEV device file system is: /dev/.udev >>>> >>>> Versions adequately match for the compiler installed: >>>> 4.1.1 >>>> and the compiler used in kernel assembly: 4.1.1 >>>> >>>> >>>> >>>> Minimal compiling resources appear complete: >>>> make utility - /usr/bin/make >>>> Compiler version 4.1 >>>> linuc_headers base folder >>>> /lib/modules/2.6.18.8.tex5/build >>>> >>>> However some compilations and executable functions may >>>> need additional files, >>>> in the FileNames.h (so called kernel "h"eaders) >>>> collection installed >>>> in /usr/include/ . >>>> For martian_modem, additional required packages are >>>> needed. The also >>>> required headers of package libc6 are commonly installed by >>>> default. >>>> Compiling hsfmodem drivers does require linux-libc-dev and >>>> libc6-dev >>>> packages, for kernels 2.6.24 and later versions. >>>> In not included on your install CD, search for them at >>>> http://packages.ubuntu.com >>>> or comparable Repository for other Linux distros. >>>> When compiling ALSA drivers, the utility "patch" >>>> will also be needed. >>>> >>>> >>>> >>>> >>>> If a driver compilation fails, with message including some >>>> lack of >>>> some FileName.h (stdio.h for example), then >>>> Some additional kernel-header files need installation to >>>> /usr/include. >>>> The minimal additional packages are libc6-dev >>>> and any of its dependents, under Ubuntu linux-libc-dev >>>> >>>> If an alternate ethernet connection is available, >>>> $ apt-get update >>>> $ apt-get -s install linux-kernel-devel >>>> will install needed packages. >>>> For Debian/Ubuntu related distributions, run the following >>>> command to >>>> display the needed package list: >>>> >>>> Otherwise packages have to be found through >>>> http://packages.ubuntu.com >>>> Once downloaded and transferred into a Linux partition, >>>> they can be installed alltogether with: >>>> $ sudo dpkg -i *.deb >>>> >>>> >>>> Checking pppd properties: >>>> -rwsr-xr-t 1 root root 304536 Nov 7 2006 >>>> /usr/sbin/pppd >>>> >>>> In case of an "error 17" "serial >>>> loopback" problem, see: >>>> >>>> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html >>>> >>>> To enable dialout without Root permission do: >>>> $ su - root (not for Ubuntu) >>>> chmod a+x /usr/sbin/pppd >>>> or under Ubuntu related Linuxes >>>> chmod a+x /usr/sbin/pppd >>>> >>>> Checking settings of: /etc/ppp/options >>>> lock >>>> noauth >>>> noipdefault >>>> usepeerdns >>>> >>>> In case of a message like: >>>> Warning: Could not modify /etc/ppp/pap-secrets: >>>> Permission denied >>>> see >>>> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html >>>> >>>> Read Modem/DOCs/YourSystem.txt concerning other COMM >>>> channels: eth0 >>>> Which can interfere with Browser naviagation. >>>> >>>> Don't worry about the following, it is for experts >>>> should trouble >>>> shooting be necessary. >>>> ========================================================== >>>> >>>> Checking for modem support lines: >>>> -------------------------------------- >>>> /device/modem symbolic link: >>>> slmodemd created symbolic link /dev/ttySL0: >>>> Within /etc/udev/ files: >>>> >>>> Within /etc/modprobe.conf files: >>>> >>>> Within any ancient /etc/devfs files: >>>> >>>> Within ancient kernel 2.4.n /etc/module.conf files: >>>> >>>> --------- end modem support lines -------- >>> >>> >
