Re: Re: Installing modem.
This is a report on experience in getting my 3com 5610 modem working... includes details of *relevant* output from all the configuration utilities I could find, and a *working* solution. (there seem to be a significant number of people in an identical situation) Hi all, After reading all about how the 3com 5610 (or USR 5610, as 3com seems to refer to it) modem worked well in linux, I went off and bought one via paypal. Woohoo! or so I thought. Turns out it was a little more trouble to configure than expected. I'm running debian 3.0r2 on the i386 platform. I tried everything in the modem and serial howto's, to no avail. Having read through some nifty posts online, I found the suggestion to MAKEDEV -v ttyS4. That solved my problem. It seems I'm not the only person to have been stumped by this, so here is how I got mine working (and how I found the information about the modem. Just a note: before I managed to get mine working, setserial would always respond with strange messages like: # setserial /dev/ttys4 port 0xe400 irq 9 uart 16550A /dev/ttys4: Input/output error (note: I had used small s in ttys4, because the 'ls ttys*' returned what looked like a valid ttys4 port) # setserial /dev/ttyS4 port 0xe400 irq 9 uart 16550A /dev/ttyS4: No such file or directory (note: because I hadn't MAKEDEV'd the device yet) # setserial /dev/ttyS04 port 0xe400 irq 9 uart 16550A /dev/ttyS04: No such file or directory (even though dmesg made me think that it was set up as ttyS04, which made no sense) Here are the important portions of various ways of finding out about the device itself: # cat /proc/pci Bus 0, device 10, function 0: Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 1). IRQ 9. I/O at 0xe400 [0xe407]. # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 -- serial port 1 /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3 -- serial port 2 /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4 /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3 # lspci -vv 00:0a.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com USR 56k Internal FAX Modem (Model 5610) Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 9 Region 0: I/O ports at e400 [size=8] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- # dmesg Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A PCI: Found IRQ 9 for device 00:0a.0 Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00ad) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xe400 (irq = 9) is a 16550A Finally, to get the modem to work I used the following 4 commands: # MAKEDEV -v /dev/ttyS4 # setserial /dev/ttyS4 port 0xe400 irq 9 uart 16550A # setserial -g ttyS4 ttyS4, UART: 16550A, Port: 0xe400, IRQ: 2 (I also added a line to /etc/wvdial.conf, after [Dialer Defaults] I inserted the line 'Modem = /dev/ttyS4') To get wvdial working, I then used: --- # wvdialconf wvdial.conf Scanning your serial ports for a modem. ttyS0*1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud ttyS0*1: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud ttyS0*1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud ttyS0*1: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud ttyS0*1: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS1*1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud ttyS1*1: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud ttyS1*1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud ttyS1*1: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud ttyS1*1: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan*1: S2 S3 ttyS4*1: ATQ0 V1 E1 -- OK ttyS4*1: ATQ0 V1 E1 Z -- OK ttyS4*1: ATQ0 V1 E1 S0=0 -- OK ttyS4*1: ATQ0 V1 E1 S0=0 C1 -- OK ttyS4*1: ATQ0 V1 E1 S0=0 C1 D2 -- OK ttyS4*1: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- OK ttyS4*1: Modem Identifier: ATI -- 5601 ttyS4*1: Speed 4800: AT -- OK ttyS4*1: Speed 9600: AT -- OK ttyS4*1: Speed 19200: AT -- OK ttyS4*1: Speed 38400: AT -- OK ttyS4*1: Speed 57600: AT -- OK ttyS4*1: Speed 115200: AT -- OK ttyS4*1: Max speed is 115200; that should be safe. ttyS4*1: ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- OK Found a modem on /dev/ttyS4. Modem configuration written to wvdial.conf. ttyS4Info: Speed 115200; init ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 -- Now my modem appears to be quite happy, although I have yet to bring it online (I'm writing this from a second
Re: Installing modem
Success the breakthrough command was wvdialconf which located and configured the modem. The modem was located on ttyS4 and dialing the ISP succeded. Thanks to all. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Alright, it doesn't look like we are getting very far, so I am going to throw in the way I would diagnose this issue. *sigh* pppd, this is about the best way I can think of to get things done. It's a little harsh, but nothing a good man page can't handle. I am including exerts from the pppd man page I am reading. Hopefully it will provide some insights on how to appropriately diagnose this issue. It is obvious that the problem with the modem is occuring on the software level, at least so far, as I assume you have installed it already and it has worked in other OSes. So we need to get the software messages coming from the dialers. Hopefully this will help. [Exert 1] EXAMPLES The following examples assume that the /etc/ppp/options file contains the auth option (as in the default /etc/ppp/options file in the ppp distribution). Probably the most common use of pppd is to dial out to an ISP. This can be done with a command such as pppd call isp where the /etc/ppp/peers/isp file is set up by the system administrator to contain something like this: ttyS0 19200 crtscts connect '/usr/sbin/chat -v -f /etc/ppp/chat-isp' noauth In this example, we are using chat to dial the ISP's modem and go through any logon sequence required. The /etc/ppp/chat-isp file contains the script used by chat; it could for example contain something like this: ABORT NO CARRIER ABORT NO DIALTONE ABORT ERROR ABORT NO ANSWER ABORT BUSY ABORT Username/Password Incorrect at OK atd0c1 OK atdt2468135 name: ^Umyuserid word: \qmypassword ispts \q^Uppp ~-^Uppp-~ [End Exert 1] [Exert 2] DIAGNOSTICS Messages are sent to the syslog daemon using facility LOG_DAEMON. (This can be overriden by recompiling pppd with the macro LOG_PPP defined as the desired facility.) In order to see the error and debug messages, you will need to edit your /etc/syslog.conf file to direct the mes- sages to the desired output device or file. The debug option causes the contents of all control pack- ets sent or received to be logged, that is, all LCP, PAP, CHAP or IPCP packets. This can be useful if the PPP nego- tiation does not succeed or if authentication fails. If debugging is enabled at compile time, the debug option also causes other debugging messages to be logged. Debugging can also be enabled or disabled by sending a SIGUSR1 signal to the pppd process. This signal acts as a toggle. [End Exert 2] Nice Debian has provided sample scripts and such. pppconfig will also set up those scripts for you. What you need to do is to investigate those scripts, see what they are doing, then, once you know that, run pppd with pon or whatever you need to do, log it, and read the logs; in fact, send the logs to this list. Hopefully that will give us a much better idea of what is going on. Again, I also suggest that you try this on ttyS3 and ttyS4, as I think that ttyS4 is the modem, but I want to compare it to something else. pppconfig and pppd are the most reliable ways to work with your modem, and they will hopefully give us the most information, assuming they are configured right. That's where the man pages come in. Now, if I was in your situation, after I had those error logs, and knew exactly what was happening, I would take on the rest of things; but it's important to see exactly what's happening on the modem, not just if any sound comes out of it. If anyone has a better idea, let me know, because I would love to have an easier way of doing things next time around. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Aaron Hsu [EMAIL PROTECTED] To: Hoyt Bailey [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, November 15, 2003 01:42 Subject: Re: Installing modem. Alright, it doesn't look like we are getting very far, so I am going to throw in the way I would diagnose this issue. *sigh* pppd, this is about the best way I can think of to get things done. It's a little harsh, but nothing a good man page can't handle. I am including exerts from the pppd man page I am reading. Hopefully it will provide some insights on how to appropriately diagnose this issue. It is obvious that the problem with the modem is occuring on the software level, at least so far, as I assume you have installed it already and it has worked in other OSes. So we need to get the software messages coming from the dialers. Hopefully this will help. [Exert 1] EXAMPLES The following examples assume that the /etc/ppp/options file contains the auth option (as in the default /etc/ppp/options file in the ppp distribution). Probably the most common use of pppd is to dial out to an ISP. This can be done with a command such as pppd call isp where the /etc/ppp/peers/isp file is set up by the system administrator to contain something like this: ttyS0 19200 crtscts connect '/usr/sbin/chat -v -f /etc/ppp/chat-isp' noauth In this example, we are using chat to dial the ISP's modem and go through any logon sequence required. The /etc/ppp/chat-isp file contains the script used by chat; it could for example contain something like this: ABORT NO CARRIER ABORT NO DIALTONE ABORT ERROR ABORT NO ANSWER ABORT BUSY ABORT Username/Password Incorrect at OK atd0c1 OK atdt2468135 name: ^Umyuserid word: \qmypassword ispts \q^Uppp ~-^Uppp-~ [End Exert 1] [Exert 2] DIAGNOSTICS Messages are sent to the syslog daemon using facility LOG_DAEMON. (This can be overriden by recompiling pppd with the macro LOG_PPP defined as the desired facility.) In order to see the error and debug messages, you will need to edit your /etc/syslog.conf file to direct the mes- sages to the desired output device or file. The debug option causes the contents of all control pack- ets sent or received to be logged, that is, all LCP, PAP, CHAP or IPCP packets. This can be useful if the PPP nego- tiation does not succeed or if authentication fails. If debugging is enabled at compile time, the debug option also causes other debugging messages to be logged. Debugging can also be enabled or disabled by sending a SIGUSR1 signal to the pppd process. This signal acts as a toggle. [End Exert 2] Nice Debian has provided sample scripts and such. pppconfig will also set up those scripts for you. What you need to do is to investigate those scripts, see what they are doing, then, once you know that, run pppd with pon or whatever you need to do, log it, and read the logs; in fact, send the logs to this list. Hopefully that will give us a much better idea of what is going on. Again, I also suggest that you try this on ttyS3 and ttyS4, as I think that ttyS4 is the modem, but I want to compare it to something else. pppconfig and pppd are the most reliable ways to work with your modem, and they will hopefully give us the most information, assuming they are configured right. That's where the man pages come in. Now, if I was in your situation, after I had those error logs, and knew exactly what was happening, I would take on the rest of things; but it's important to see exactly what's happening on the modem, not just if any sound comes out of it. If anyone has a better idea, let me know, because I would love to have an easier way of doing things next time around. :-) It is pretty clear to me that the problem is that there is no connection between the modem and ttyS3 or 4 or most likely there are two connections being attempted (at least the logs seem to suggest). Setserial seems to work but dosent clear the problem even after deleting /dev/ttyS3 and /dev/ttyS4 the same message appears in the log (Redundant entry in serial pci-table[ends with ttyS4 at port 0x7fe0 (irq = 10) is a 16550A. I did try wvdial and wvdial.conf but just reread post and will try wvdial.conf.test tomorrow or monday. wvdial appears to be configured ok , will recheck. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Thursday, November 13, 2003 21:16 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] I tried minicom as I remember I reported the results the first time they were the same this time. I started KDE and selected the terminal read the man page for minicom not much help there. issued su and input the password. input minicom -c, got 1/2 screen (top to bottom full 1/2 wide)with a colored panel at the bottom. The only thing that worked was right clicking on the items at the bottom (they showed menus that wouldnt do anything). Finally reset and tryed again this time minicom -s and got the same 1/2 screen B/W with options A thru F. Typing a thru f resulted in going to that option on screen. Changing the option had no effect. There was also a box below that I couldnt get into that had some options including Exit. Could not do anything except reset. That doesn't sound like the minicom I just looked at, but then I'm running unstable. fancypiper: Make sure that plug-n-pray is disabled in your bios as it can screw up your settings. Couldnt find an entry in BIOS for plug-n-pray or for plug-n-play either. Isnt that a Windows function? No; well, yes. Sort of. Not really. No. Definitely no. It's a name popularized by Microsoft (perhaps invented by MS) that simply refers to the ability of the operating system (Windows in the case of MS) to set the hardware resources, such as COM ports and IRQ settings, etc, automagically for your various hardware. It was a much bigger deal in the days before PCI devices became popular. Nowadays the PCI subsystem takes care of PnP, for the most part. Still, many BIOSes have the option to turn the feature on or off. If the BIOS is told that there is a PnP OS, then the BIOS does just the minimal setup necessary and lets the OS do the rest. IF the BIOS is told that there is not a PnP OS, then the BIOS does all the hardware setup. It has been my experience that it's best to let the BIOS handle things, even if you have a Plug-n-Play-capable OS. # cat /proc/pci My system returned the following: Bus 0, device 11, Function 0 Serial Controller: US Robotics/3Com 56K FaxModom Model 5610 (rev 1) IRQ 19 Master capabile, latency=32 I/O at 0xd000 [0xd007] With this info, I use the setserial command: # setserial /dev/ttyS0 irq 5 port 0xc400 uart 16550a # setserial /dev/ttyS3 irq 19 port 0xd000 uart 16550a bash: setserial command not found. It would appear that there is a package I dont have installed. Does anyone know what the package would be? Would that package also contain minicom? setserial They are separate packages. See apt-cache show setserial and apt-cache show minicom. I though setserial is part of the base OS and is installed automatically. I guess not. Then I test the modem with the internet connection wizard and it works. ?What is the internet connection wizard? It's some utility in whatever distro he was using. For you, you'd use KPPP or pppconfig, etc. -- Kent I did some more research this morning and the above isnt accurate. While it is what I experienced in KDE login as me and su to root. I ran minicom -s on the command line, as root, after reading the rather extensive manual (much more than one page). I was able to setup the modem dont know if it is right though. After exiting the setup I was in a screen that said, as the last line, cntl A-Z for help. No matter what I did it was not possible to even move the cursor. Cntl C or D also didnt do anything. Finally reset the system to get out. I did reissue the setserial command as listed and it appeared to work. That probable means that KDE is bad. Could this be happening because most of these programs were installed before the nvidia driver was installed? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Friday, November 14, 2003 08:45 Subject: Re: Installing modem. Hoyt Bailey wrote: I did some more research this morning and the above isnt accurate. While it is what I experienced in KDE login as me and su to root. I ran minicom -s on the command line, as root, after reading the rather extensive manual (much more than one page). I was able to setup the modem dont know if it is right though. After exiting the setup I was in a screen that said, as the last line, cntl A-Z for help. No matter what I did it was not possible to even move the cursor. Cntl C or D also didnt do anything. Finally reset the system to get out. I did reissue the setserial command as listed and it appeared to work. That probable means that KDE is bad. Could this be happening because most of these programs were installed before the nvidia driver was installed? Regards; Hoyt The modem is totally unrelated to the video driver. KPPP may not be working, but that's a very small part of KDE, so it would be inaccurate to say that KDE is bad. When in minicom, if it's talking properly to the modem, you should be able to enter a command like: ATZ and your modem will respond with something like OK or READY If you don't get such a response, something is still wrong with your modem/configuration. I wish I could give you more information, but I'm not that familiar with modems. I don't like dealing with modems, especially ones that aren't external on COM1 or COM2, and so avoid them whenever I can. All I can suggest is keep trying. -- Kent -- Kent West ([EMAIL PROTECTED]) Ok thanks for trying. I'm not convinced that the hang up of minicom is unrelated yet. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
On Thu, Nov 13, 2003 at 05:41:52PM -0600, Hoyt Bailey wrote: On Thursday, November 13, 2003 10:01, Kent West wrote: I thought that echoing a command to the device file was a good test, but someone else in this thread with the same modem as you says this test does not work. So ignore this test and its results. Instead, try minicom. I tried minicom as I remember I reported the results the first time they were the same this time. I started KDE and selected the terminal read the man page for minicom not much help there. issued su and input the password. input minicom -c, got 1/2 screen (top to bottom full 1/2 wide)with a colored panel at the bottom. The only thing that worked was right clicking on the items at the bottom (they showed menus that wouldnt do anything). Finally reset and tryed again this time minicom -s and got the same 1/2 screen B/W with options A thru F. Typing a thru f resulted in going to that option on screen. Changing the option had no effect. There was also a box below that I couldnt get into that had some options including Exit. Could not do anything except reset. Try switching to a text console and running minicom from there. With this info, I use the setserial command: # setserial /dev/ttyS0 irq 5 port 0xc400 uart 16550a # setserial /dev/ttyS3 irq 19 port 0xd000 uart 16550a bash: setserial command not found. It would appear that there is a package I dont have installed. Does anyone know what the package would be? It's called... tadaa... setserial apt-get install setserial Would that package also contain minicom? No, minicom's a separate package which you appear to have installed already. Then I test the modem with the internet connection wizard and it works. ?What is the internet connection wizard? He's a little bloke with a pointy hat and a staff who does things like flipping bits in your telco's computer so as to enable ADSL on your phone line without the billing department knowing about it. I'd rather like to meet him. -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F pgp0.pgp Description: PGP signature
Re: Installing modem.
- Original Message - From: Pigeon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 14, 2003 07:52 Subject: Re: Installing modem. From my last post you can see that I finally went to command line and while that solved a lot of problems it didnt allow *me* to send a command to the modem I'll search for more info on minicom. By the way I would like to meet that turkey is he the same one that shows up in KDE? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 21:30 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: oskar nl [EMAIL PROTECTED] Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. From U.S. Robotic Installation guide pag 4: Linux 2.3 and Higher Users NOTE: All 2.3 and higher Linux kernels contain the U.S. Robotics Linux modem drivers. Installation of the modem under this kernel is fully automatic provided your kernel has the Plug and Play module enabled (default). BTW wich kernel you use?: The kernel is 2.4.18bf2.4. and I have to accept the fact that the modem is probably installed, but twice it seems. I don't understand what you mean by this. It doesn't make sense. The modem, a physical device that is singular in nature, can only be installed once, on a single physical PCI slot. Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A I dont know how else to explain the Redundant entry in serial pci_table. Does anyone know where that is or how to remove it? I do know that I removed the only entry of ttsS4 that I know about. I just rm /dev/ttyS3 ttyS4. Then I confirmed that they both gone. Then form the /dev directory I ran MAKEDEV -v update, this restored /dev/ttyS3. No harm done here; a good effort at troubleshooting. OK ttyS3 is where the modem should be. I had hope went and checked dmesg and there was ttyS0, ttyS1, ttyS2 and ttyS4. I believe I understand that you're saying that dmesg reports the existence of devices on /dev/ttyS0, /dev/ttyS1, and /dev/ttyS4. (In an earlier message I apparently mistyped that your modem is on /dev/ttyS3 -- but if I understand what you're saying above, it's on /dev/ttyS4 - probably - it's hard to say without the relevant portions of dmesg's output.) Confirmed that /dev/ttyS4 does not exist. ?How do you delete something that dosent exist? Why do you want to delete /dev/ttyS4? Perhaps to start over, like you did above with the other four standard ports? If it's not there, don't worry about deleting it. Perhaps what you need to worry about is creating it. Try ls -l /dev/ttyS*; you should get something like this: crw-rw1 root dialout4, 64 May 12 2001 /dev/ttyS0 crw-rw1 root dialout4, 65 May 12 2001 /dev/ttyS1 crw-rw1 root dialout4, 66 May 12 2001 /dev/ttyS2 crw-rw1 root dialout4, 67 May 12 2001 /dev/ttyS3 crw-rw1 root dialout4, 64 Oct 16 09:25 /dev/ttyS0 crw-rw1 root dialout4, 65 Oct 16 09:28 /dev/ttyS1 crw-rw1 root dialout4, 66 Mar 14 2002 /dev/ttyS2 crw-rw1 root dialout4, 67 Mar 14 2002 /dev/ttyS3 -Currently.- If not, you might want to do: MAKEDEV -v generic to create generic devices, including the four serial ports. So all you need to do is create a similar file for ttyS4. This command should do it: MAKEDEV -v ttyS4 Already tryed that it created /dev/ttyS4 but dosent change the message (dmesg) in any way I noticed. Also will not respond to echo ATDTphone # /dev/ttyS4 which it should. more specifically the screen does this: Blackgold: / # echo ATDT3633070 /dev/ttyS4 Blackgold: / # Also there is no sound from the modem and there always is when it dials this number untill connection is confirmed. I blame this action on Redundant entry (etc.). I suspect the pci-table is in the kernel but have no confidence that reinstalling everything would alter the results. There is likely something I am doeing wrong or incorrectly at least but I dont have a clue. Now see if your modem works. I am attaching dmesg in case anyone can figure out how to fix this. Unless I'm missing something, dmesg was not attached. It was attached on my copy of the email but it was the wrong one. The copy that was attached was the one where I had disabled ttyS0 1. I am reattaching the correct current copy. Regards; Hoyt dmesg-A Description: Binary data
Re: Installing modem
I begin to wonder if the pci-tables might be listed in /proc didnt find that but the following was interesting:/proc/interrupts CPU0 0: 50953IO-APIC-edge timer 1:140IO-APIC-edge keyboard 2: 0 XT-PIC cascade 6: 32IO-APIC-edge floppy 8: 3IO-APIC-edge rtc 12: 19237IO-APIC-edge PS/2 Mouse 14: 205935IO-APIC-edge ide0 15: 4IO-APIC-edge ide1 16: 36548 IO-APIC-level nvidia 18: 43 IO-APIC-level eth0 21: 0 IO-APIC-level usb-uhci, usb-uhci, usb-uhci NMI: 0 LOC: 50902 ERR: 0 MIS: 0 It seems a little strange that IRQ19 is missing. Does that have meaning? Also:/proc/ioports -001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02f8-02ff : serial(set) 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(set) 0cf8-0cff : PCI conf1 d000-d007 : US Robotics/3Com 56K FaxModem Model 5610 d000-d007 : serial(auto) d400-d41f : VIA Technologies, Inc. UHCI USB d400-d41f : usb-uhci d800-d81f : VIA Technologies, Inc. UHCI USB (#2) d800-d81f : usb-uhci dc00-dc1f : VIA Technologies, Inc. UHCI USB (#3) dc00-dc1f : usb-uhci e000-e00f : VIA Technologies, Inc. Bus Master IDE e400-e4ff : VIA Technologies, Inc. AC97 Audio Controller e800-e8ff : Realtek Semiconductor Co., Ltd. RTL-8139 e800-e8ff : 8139too d000-d007 is defined as serial(auto) and is tied to the modem (Model 5610). Seems right. Couldnt find anything else that appeared relative. Does any of this help? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: From: Kent West [EMAIL PROTECTED] So all you need to do is create a similar file for ttyS4. This command should do it: MAKEDEV -v ttyS4 Already tryed that it created /dev/ttyS4 but dosent change the message (dmesg) in any way I noticed. Also will not respond to echo ATDTphone # /dev/ttyS4 which it should. more specifically the screen does this: Blackgold: / # echo ATDT3633070 /dev/ttyS4 Blackgold: / # Also there is no sound from the modem and there always is when it dials this number untill connection is confirmed. I blame this action on Redundant entry (etc.). I suspect the pci-table is in the kernel but have no confidence that reinstalling everything would alter the results. There is likely something I am doeing wrong or incorrectly at least but I dont have a clue. I thought that echoing a command to the device file was a good test, but someone else in this thread with the same modem as you says this test does not work. So ignore this test and its results. Instead, try minicom. Also, I found this information at: http://www.linuxquestions.org/questions/archive/18/2003/08/4/86297 nonrusteScenario: I purchased a US Robotics 56K* V.92 Performance Pro Modem because they advertised support for Linux: usr.com/products/home/home-product.asp?sku=USR5610B I followed the advice of the author of the following page when my modem was not detected with Yast2: webpronews.com/wpn-22-20030623SettingUpaLinuxModem.html The command 'cat /proc/pci' listed my modem with hardware address IRQ number. When I tried the setserial command I got an error of 'Address in use'. Though I could not get a peep out of my modem with 'echo atdt555 /dev/ttySX' (I've tried many ttySX including 'ttyS04' which is echoed across my monitor upon bootup with the hardware address of the modem. I tried installing the RPM (usr.com/support/product-template.asp?prod=5610b) from US Robotics. That gave me a funky error. I didn't write it down, though tried to re-install the RPM to recreate error, but got an error stating that the RPM was already installed and I'm yet too ignorant to know how to resolve that. fancypiper: Make sure that plug-n-pray is disabled in your bios as it can screw up your settings. Here is how I configured my modem (below modem links) # Configuring a real hardware pci modem To configure a pci modem, open an x terminal and su - to the root $ su - Password: # cat /proc/pci Look for your modem in the returned list. Look for something similar to mine: Bus 2, device 2, function 0: Communication controller: PCI device 151f: (TOPIC SEMICONDUCTOR Corp) (rev 0). IRQ 5. I/O at 0xc400 [0xc407]. With this info, I use the setserial command: # setserial /dev/ttyS0 irq 5 port 0xc400 uart 16550a Then I test the modem with the internet connection wizard and it works. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
Hoyt Bailey wrote: I begin to wonder if the pci-tables might be listed in /proc didnt find that but the following was interesting:/proc/interrupts CPU0 0: 50953IO-APIC-edge timer 1:140IO-APIC-edge keyboard 2: 0 XT-PIC cascade 6: 32IO-APIC-edge floppy 8: 3IO-APIC-edge rtc 12: 19237IO-APIC-edge PS/2 Mouse 14: 205935IO-APIC-edge ide0 15: 4IO-APIC-edge ide1 16: 36548 IO-APIC-level nvidia 18: 43 IO-APIC-level eth0 21: 0 IO-APIC-level usb-uhci, usb-uhci, usb-uhci NMI: 0 LOC: 50902 ERR: 0 MIS: 0 It seems a little strange that IRQ19 is missing. Does that have meaning? I'd say no. [EMAIL PROTECTED]:/home/westk: cat /proc/interrupts CPU0 0: 59068572 XT-PIC timer 1: 65703 XT-PIC keyboard 2: 0 XT-PIC cascade 8: 4 XT-PIC rtc 9:9821656 XT-PIC eth0 10: 21152 XT-PIC Intel 82801BA-ICH2 11: 0 XT-PIC usb-uhci 12:1857264 XT-PIC PS/2 Mouse 14: 503689 XT-PIC ide0 15: 52 XT-PIC ide1 NMI: 0 LOC: 59069577 ERR: 0 MIS: 0 -- Kent West ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Thursday, November 13, 2003 10:01 Subject: Re: Installing modem. Hoyt Bailey wrote: From: Kent West [EMAIL PROTECTED] So all you need to do is create a similar file for ttyS4. This command should do it: MAKEDEV -v ttyS4 Already tryed that it created /dev/ttyS4 but dosent change the message (dmesg) in any way I noticed. Also will not respond to echo ATDTphone # /dev/ttyS4 which it should. more specifically the screen does this: Blackgold: / # echo ATDT3633070 /dev/ttyS4 Blackgold: / # Also there is no sound from the modem and there always is when it dials this number untill connection is confirmed. I blame this action on Redundant entry (etc.). I suspect the pci-table is in the kernel but have no confidence that reinstalling everything would alter the results. There is likely something I am doeing wrong or incorrectly at least but I dont have a clue. I thought that echoing a command to the device file was a good test, but someone else in this thread with the same modem as you says this test does not work. So ignore this test and its results. Instead, try minicom. I tried minicom as I remember I reported the results the first time they were the same this time. I started KDE and selected the terminal read the man page for minicom not much help there. issued su and input the password. input minicom -c, got 1/2 screen (top to bottom full 1/2 wide)with a colored panel at the bottom. The only thing that worked was right clicking on the items at the bottom (they showed menus that wouldnt do anything). Finally reset and tryed again this time minicom -s and got the same 1/2 screen B/W with options A thru F. Typing a thru f resulted in going to that option on screen. Changing the option had no effect. There was also a box below that I couldnt get into that had some options including Exit. Could not do anything except reset. Also, I found this information at: http://www.linuxquestions.org/questions/archive/18/2003/08/4/86297 nonrusteScenario: I purchased a US Robotics 56K* V.92 Performance Pro Modem because they advertised support for Linux: Exactly my reason. usr.com/products/home/home-product.asp?sku=USR5610B I followed the advice of the author of the following page when my modem was not detected with Yast2: Is Yast2 the program that detects hardware? webpronews.com/wpn-22-20030623SettingUpaLinuxModem.html The command 'cat /proc/pci' listed my modem with hardware address IRQ number. When I tried the setserial command I got an error of 'Address in use'. Though I could not get a peep out of my modem with 'echo atdt555 /dev/ttySX' (I've tried many ttySX including 'ttyS04' which is echoed across my monitor upon bootup with the hardware address of the modem. I tried installing the RPM (usr.com/support/product-template.asp?prod=5610b) from US Robotics. That gave me a funky error. I didn't write it down, though tried to re-install the RPM to recreate error, but got an error stating that the RPM was already installed and I'm yet too ignorant to know how to resolve that. fancypiper: Make sure that plug-n-pray is disabled in your bios as it can screw up your settings. Couldnt find an entry in BIOS for plug-n-pray or for plug-n-play either. Isnt that a Windows function? Here is how I configured my modem (below modem links) # Configuring a real hardware pci modem To configure a pci modem, open an x terminal and su - to the root $ su - Password: # cat /proc/pci Look for your modem in the returned list. Look for something similar to mine: Bus 2, device 2, function 0: Communication controller: PCI device 151f: (TOPIC SEMICONDUCTOR Corp) (rev 0). IRQ 5. I/O at 0xc400 [0xc407]. My system returned the following: Bus 0, device 11, Function 0 Serial Controller: US Robotics/3Com 56K FaxModom Model 5610 (rev 1) IRQ 19 Master capabile, latency=32 I/O at 0xd000 [0xd007] With this info, I use the setserial command: # setserial /dev/ttyS0 irq 5 port 0xc400 uart 16550a # setserial /dev/ttyS3 irq 19 port 0xd000 uart 16550a bash: setserial command not found. It would appear that there is a package I dont have installed. Does anyone know what the package would be? Would that package also contain minicom? Then I test the modem with the internet connection wizard and it works. ?What is the internet connection wizard? -- Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] I tried minicom as I remember I reported the results the first time they were the same this time. I started KDE and selected the terminal read the man page for minicom not much help there. issued su and input the password. input minicom -c, got 1/2 screen (top to bottom full 1/2 wide)with a colored panel at the bottom. The only thing that worked was right clicking on the items at the bottom (they showed menus that wouldnt do anything). Finally reset and tryed again this time minicom -s and got the same 1/2 screen B/W with options A thru F. Typing a thru f resulted in going to that option on screen. Changing the option had no effect. There was also a box below that I couldnt get into that had some options including Exit. Could not do anything except reset. That doesn't sound like the minicom I just looked at, but then I'm running unstable. fancypiper: Make sure that plug-n-pray is disabled in your bios as it can screw up your settings. Couldnt find an entry in BIOS for plug-n-pray or for plug-n-play either. Isnt that a Windows function? No; well, yes. Sort of. Not really. No. Definitely no. It's a name popularized by Microsoft (perhaps invented by MS) that simply refers to the ability of the operating system (Windows in the case of MS) to set the hardware resources, such as COM ports and IRQ settings, etc, automagically for your various hardware. It was a much bigger deal in the days before PCI devices became popular. Nowadays the PCI subsystem takes care of PnP, for the most part. Still, many BIOSes have the option to turn the feature on or off. If the BIOS is told that there is a PnP OS, then the BIOS does just the minimal setup necessary and lets the OS do the rest. IF the BIOS is told that there is not a PnP OS, then the BIOS does all the hardware setup. It has been my experience that it's best to let the BIOS handle things, even if you have a Plug-n-Play-capable OS. # cat /proc/pci My system returned the following: Bus 0, device 11, Function 0 Serial Controller: US Robotics/3Com 56K FaxModom Model 5610 (rev 1) IRQ 19 Master capabile, latency=32 I/O at 0xd000 [0xd007] With this info, I use the setserial command: # setserial /dev/ttyS0 irq 5 port 0xc400 uart 16550a # setserial /dev/ttyS3 irq 19 port 0xd000 uart 16550a bash: setserial command not found. It would appear that there is a package I dont have installed. Does anyone know what the package would be? Would that package also contain minicom? setserial They are separate packages. See apt-cache show setserial and apt-cache show minicom. I though setserial is part of the base OS and is installed automatically. I guess not. Then I test the modem with the internet connection wizard and it works. ?What is the internet connection wizard? It's some utility in whatever distro he was using. For you, you'd use KPPP or pppconfig, etc. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 19:07 Subject: Re: Installing modem. Hoyt Bailey wrote: You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A It looks like you have two serial ports on your motherboard (00 01), in addition to your modem on 04. Apparently the PCI bus is getting confused somehow. You might want to go into the BIOS and temporarily disable the built-in serial ports, and see what that does for you. I have sent the requested message to the sourceforge.net. with a cc to this list. Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. Because somewhere in the diddleing I came across dmesg as the log file which I didnt know and thought it might have something that would help. But I'm unsure why you'd want to copy it to floppy. If you need it in a file form, you can: dmesg dmesg.txt and then copy dmesg.txt to wherever you want it, including floppy. If you just want to see the dmesg messages, you can: dmesg | more I need to transport stuff to windows to make a hard copy /or to include in an emale. Floppy is the only way I have to do that. What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This I don't understand; you say it's doing nothing absolutely nothing and then immediately say you hear the modem sending, which means it's doing something. Either it's doing nothing or it's doing something. Which is it? How about: When and if the modem dials my ISP I can hear The modem output untill a connection is made. I can assure you the modem is doing nothing on either ttys3 or ttys4. I also assume you didn't really use the bogus number 555-1234? You want to use a real number, say to your cell phone, or a second line, or to the local time temperature (I didn't say that - no one can prove I did) and listen to the modem speaker for the time/temp announcement. If this works, that means the computer is seeing your modem, your modem is seeing the phone line, and the modem can dial out. I used both the bogus number and my ISP's number nothing happened. I dont think the modem is smart enough to know wheather the number is valid or not and a busy signal or error message from SBC is good enough. By the way the town is too small for time temp and cell phone service stops at my frount door. Outside it works inside forget it. -- Kent What program generated the connection between the modem's 8 I/O lines d000-d007 and /dev/ttyS3 and what would happen if I rm /dev/ttyS4 and maybe /dev/ttyS3 as well and remade, with MAKEDEV, ttyS3 and then run the program that makes the original connection. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 19:30 Subject: Re: Installing modem Hoyt Bailey wrote: I installed minicom from KDE package manager. It is very easy. Issued 'minicom -s' and was able to move around and inserted a telephone number in the calling option but couldnt make anything happen. Red the man page as well. Got into initalization modem and couldnt get out without closeing window. What am I doing wrong? Regards; Hoyt You're having tremendous difficulties getting a modem working. Could I suggest that you beg/borrow an external serial modem (not USB, not internal) from a friend, even if it's a lowly 1200baud modem? Get that working; then when you're satisfied that you're making progress, then start struggling again with your internal PCI modem (which I despise, because they're always trouble in my experience). -- Kent Good Idea but the only person I know with a computer likely has a winmodem and I already have 2 of those and I think the problem is deeper than the modem. Of course I cant prove it but there is somthing not right and I cant put my finger on the difficulty too many things just happen and logic just dosent permit that. There is a cockroach in this system and I had hoped to find it by fixing the basic problems first. Dont forget when I installed this modem and put the case back together. Turned on power windows booted and dialed my ISP. No install no hassel of any kind, the modem cant be totally at falt. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 19:07 Subject: Re: Installing modem. Hoyt Bailey wrote: You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A It looks like you have two serial ports on your motherboard (00 01), in addition to your modem on 04. Apparently the PCI bus is getting confused somehow. You might want to go into the BIOS and temporarily disable the built-in serial ports, and see what that does for you. I have sent the requested message to the sourceforge.net. with a cc to this list. Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. Because somewhere in the diddleing I came across dmesg as the log file which I didnt know and thought it might have something that would help. But I'm unsure why you'd want to copy it to floppy. If you need it in a file form, you can: dmesg dmesg.txt and then copy dmesg.txt to wherever you want it, including floppy. If you just want to see the dmesg messages, you can: dmesg | more I need to transport stuff to windows to make a hard copy /or to include in an emale. Floppy is the only way I have to do that. What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This I don't understand; you say it's doing nothing absolutely nothing and then immediately say you hear the modem sending, which means it's doing something. Either it's doing nothing or it's doing something. Which is it? How about: When and if the modem dials my ISP I can hear The modem output untill a connection is made. I can assure you the modem is doing nothing on either ttys3 or ttys4. I also assume you didn't really use the bogus number 555-1234? You want to use a real number, say to your cell phone, or a second line, or to the local time temperature (I didn't say that - no one can prove I did) and listen to the modem speaker for the time/temp announcement. If this works, that means the computer is seeing your modem, your modem is seeing the phone line, and the modem can dial out. I used both the bogus number and my ISP's number nothing happened. I dont think the modem is smart enough to know wheather the number is valid or not and a busy signal or error message from SBC is good enough. By the way the town is too small for time temp and cell phone service stops at my frount door. Outside it works inside forget it. -- Kent What program generated the connection between the modem's 8 I/O lines d000-d007 and /dev/ttyS3 and what would happen if I rm /dev/ttyS4 and maybe /dev/ttyS3 as well and remade, with MAKEDEV, ttyS3 and then run the program that makes the original connection. Regards; Hoyt I think it would be a good idea if you would try a diferent aproach. Since you have some problems configuring it by hand, I suggest using kppp wich is a very nice and userfriendly interface for configuring modems and serial line connections. In the times I used the phone line I used it and it would work on first time ever ! Try it - apt-get install kppp ( I hope you have KDE, I don't kow if it will run as a standallone...) John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: John Peter [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 05:36 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 19:07 Subject: Re: Installing modem. Hoyt Bailey wrote: You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A It looks like you have two serial ports on your motherboard (00 01), in addition to your modem on 04. Apparently the PCI bus is getting confused somehow. You might want to go into the BIOS and temporarily disable the built-in serial ports, and see what that does for you. I have sent the requested message to the sourceforge.net. with a cc to this list. Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. Because somewhere in the diddleing I came across dmesg as the log file which I didnt know and thought it might have something that would help. But I'm unsure why you'd want to copy it to floppy. If you need it in a file form, you can: dmesg dmesg.txt and then copy dmesg.txt to wherever you want it, including floppy. If you just want to see the dmesg messages, you can: dmesg | more I need to transport stuff to windows to make a hard copy /or to include in an emale. Floppy is the only way I have to do that. What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This I don't understand; you say it's doing nothing absolutely nothing and then immediately say you hear the modem sending, which means it's doing something. Either it's doing nothing or it's doing something. Which is it? How about: When and if the modem dials my ISP I can hear The modem output untill a connection is made. I can assure you the modem is doing nothing on either ttys3 or ttys4. I also assume you didn't really use the bogus number 555-1234? You want to use a real number, say to your cell phone, or a second line, or to the local time temperature (I didn't say that - no one can prove I did) and listen to the modem speaker for the time/temp announcement. If this works, that means the computer is seeing your modem, your modem is seeing the phone line, and the modem can dial out. I used both the bogus number and my ISP's number nothing happened. I dont think the modem is smart enough to know wheather the number is valid or not and a busy signal or error message from SBC is good enough. By the way the town is too small for time temp and cell phone service stops at my frount door. Outside it works inside forget it. -- Kent What program generated the connection between the modem's 8 I/O lines d000-d007 and /dev/ttyS3 and what would happen if I rm /dev/ttyS4 and maybe /dev/ttyS3 as well and remade, with MAKEDEV, ttyS3 and then run the program that makes the original connection. Regards; Hoyt I think it would be a good idea if you would try a diferent aproach. Since you have some problems configuring it by hand, I suggest using kppp wich is a very nice and userfriendly interface for configuring modems and serial line connections. In the times I used the phone line I used it and it would work on first time ever ! Try it - apt-get install kppp ( I hope you have KDE, I don't kow if it will run as a standallone...) John Have KDE kppp not installed. Installed with KDE Package Manager. Ran it and configured the modem. Pressed the connect button, wouldnt you know, the modem was busy. That was a good idea how about another. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
What program generated the connection between the modem's 8 I/O lines d000-d007 and /dev/ttyS3 and what would happen if I rm /dev/ttyS4 and maybe /dev/ttyS3 as well and remade, with MAKEDEV, ttyS3 and then run the program that makes the original connection. Regards; Hoyt Alright, I am wondering, did you diff the dmesg before you put your modem in with the one after? That might help in figuring out some things. I think you can go ahead and remake the ttyS3 and 4 devices, and try again. I am also a little confused, when you dial out, do you hear the dial tone and the phone number being dialed, then it cuts out; or do you just get a modem not responding error? What I am asking is, exactly where does the initialization and dialing begin to fail? Instead of using ATDT###- you might want to look at some of the scripts and try running some of the modem scripts, assuming your modem is that far along, and see what happens. It would be really nice to see the exact errors that are happening, i.e.-the output from the modem commands. There is a program that allows you to manually enter a shell like interface and run modem commands, you should be able to see the output. I only used this on OpenBSD a while ago though, so I don't know what the program is. You can also try WVDial, which is essentially like kppp and some of the others, in that it auto-detects and is pretty smart about getting things right; I found that it is a nice program for debugging and general use, it's also console based. ;-) Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
I disabled com1 com2 hardware ports in the BIOS and booted into Linux the dmesg log concerning the serial ports is as follows: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A I noticed while in BIOS the only IRQ1 thru 14 are listed. Does this matter? After extracting dmesg, I returned to command line and issued the following: echo ADTD3633070 /dev/ttyS3 echo ADTD3633070 /dev/ttyS4 Niether command resulted in any sound from the modem and no errors were reported. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
I disabled com1 com2 hardware ports in the BIOS and booted into Linux the dmesg log concerning the serial ports is as follows: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A I noticed while in BIOS the only IRQ1 thru 14 are listed. Does this matter? After extracting dmesg, I returned to command line and issued the following: echo ADTD3633070 /dev/ttyS3 echo ADTD3633070 /dev/ttyS4 Niether command resulted in any sound from the modem and no errors were reported. Regards; Hoyt Have you tried resetting your BIOS? Have you tried using another kernel as well? Try also running the ppp scripts where you will see output, I don't think echoing into the devices will out put anything unless you are watching the ttyS's. You might have to be dumping the ttyS* output using cat or something similiar in order to see any errors. Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
On Tue, 11 Nov 2003, Kent West wrote: Hoyt Bailey wrote: Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A It looks like you have two serial ports on your motherboard (00 01), in addition to your modem on 04. Apparently the PCI bus is getting confused somehow. You might want to go into the BIOS and temporarily disable the built-in serial ports, and see what that does for you. Same thing happens with my system: # Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ # SERIAL_PCI ISAPNP enabled # ttyS00 at 0x03f8 (irq = 4) is a 16550A # ttyS01 at 0x02f8 (irq = 3) is a 16550A # Redundant entry in serial pci_table. Please send the output of # lspci -vv, this message (12b9,1008,12b9,00aa) # and the manufacturer and name of serial board or modem board # to [EMAIL PROTECTED] # ttyS04 at port 0x7fe0 (irq = 10) is a 16550A Modem still works fine. What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This I don't understand; you say it's doing nothing absolutely nothing and then immediately say you hear the modem sending, which means it's doing something. Either it's doing nothing or it's doing something. Which is it? Since the grandparent poster has the same modem as mine, and my modem does not want to dial out by echoing that command to ttyS4, I would assume that it's the wrong way to debug the modem. Btw, if his dmesg log is correct, its ttyS4 he should be checking, not ttyS3, unless I am misunderstanding something. To debug, I would try these steps: 1) `wvdialconf /etc/wvdial.conf.test` 2) Assuming you get the line Found a modem on /dev/ttyS4 then continue, else post another message to debian user. 3) edit /etc/wvdial.conf.test and add in a null phone number (5551234) and uncomment the phone number, username, and password lines. 4) `wvdial --config /etc/wvdial.conf.test` 5) If you hear it dial, congrats, your modem is working. Try putting in your real phone number, username, and password. Then redo step #4. -- icq:34583382 | Nethack 3.4.2 is out! http://www.nethack.org jabber: [EMAIL PROTECTED] | And how can man die better / Than facing msn:[EMAIL PROTECTED] | fearful odds / For the ashes of his fathers / yim:tsunad | and the temples of his gods? ~ Babington pgp0.pgp Description: PGP signature
Re: Installing modem.
Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD and booted debian. Did ^alt F1 read man rpm man alien. No problem mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked for files 3commdn and found the following: /usr/share/doc/3commdn /usr/share/doc/3commdn/changelog.Debian.gz /usr/share/doc/3commdn/copyright /usr/doc/3commdn /usr/dpkg/info/3commdn/.postinst /usr/dpkg/info/3commdn/.list /usr/dpkg/info/3commdn/.prerm /usr/dpkg/info/3commdn/.conffiles /usr/dpkg/info/3commdn/.md5sums Read the copyright file and there is a statement (Not Installed). Went back to X read the log XFree86 no indication of modem. Tryed to start connection -No-. Any Suggestions? Regards; Hoyt From U.S. Robotic Installation guide pag 4: Linux 2.3 and Higher Users NOTE: All 2.3 and higher Linux kernels contain the U.S. Robotics Linux modem drivers. Installation of the modem under this kernel is fully automatic provided your kernel has the Plug and Play module enabled (default). page 6 If you have Linux Reboot the PC and note that another serial port is listed along with the device name (/dev/ttyX), indicating the modem is present. Log in to the system. Check that the modem is communicating properly. If working in a shell environment, start a Minicom terminal session from the terminal prompt. If using X Windows, use Minicom through a shell window or use the dial-up program (Kppp or equivalent). Make sure that your internal modem is physically installed correctly in your computer. With power off, press the modem in firmly so that it is seated properly in its slot. When the modem is installed correctly, you will no longer see any part of the gold edge. If your modem still does not work, you may need to remove it and reinstall it in another available PCI slot. Shut down and restart your PC. Downloaded from: http://www.usr.com/support/product-template.asp?prod=5610b Take a breath a read carefully and go slow you are maybe repeating same mistake again and again. But if you still having problems and you want to try this rpm, looks like alien can't make a good debianizing, you can try installing rpm package, but the same package say: Description: Red Hat Package Manager If you want to install Red Hat Packages then please use the alien package. Using RPM directly will bypass the Debian packaging system! Well i hope you can make it without this last, but just another idea to make your modem get ready!!. BTW wich kernel you use?: uname -a will tell you. I hope this help you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: oskar nl [EMAIL PROTECTED] Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. From U.S. Robotic Installation guide pag 4: Linux 2.3 and Higher Users NOTE: All 2.3 and higher Linux kernels contain the U.S. Robotics Linux modem drivers. Installation of the modem under this kernel is fully automatic provided your kernel has the Plug and Play module enabled (default). BTW wich kernel you use?: The kernel is 2.4.18bf2.4. and I have to accept the fact that the modem is probably installed, but twice it seems. I don't understand what you mean by this. It doesn't make sense. The modem, a physical device that is singular in nature, can only be installed once, on a single physical PCI slot. I just rm /dev/ttyS3 ttyS4. Then I confirmed that they both gone. Then form the /dev directory I ran MAKEDEV -v update, this restored /dev/ttyS3. No harm done here; a good effort at troubleshooting. OK ttyS3 is where the modem should be. I had hope went and checked dmesg and there was ttyS0, ttyS1, ttyS2 and ttyS4. I believe I understand that you're saying that dmesg reports the existence of devices on /dev/ttyS0, /dev/ttyS1, and /dev/ttyS4. (In an earlier message I apparently mistyped that your modem is on /dev/ttyS3 -- but if I understand what you're saying above, it's on /dev/ttyS4 - probably - it's hard to say without the relevant portions of dmesg's output.) Confirmed that /dev/ttyS4 does not exist. ?How do you delete something that dosent exist? Why do you want to delete /dev/ttyS4? Perhaps to start over, like you did above with the other four standard ports? If it's not there, don't worry about deleting it. Perhaps what you need to worry about is creating it. Try ls -l /dev/ttyS*; you should get something like this: crw-rw1 root dialout4, 64 May 12 2001 /dev/ttyS0 crw-rw1 root dialout4, 65 May 12 2001 /dev/ttyS1 crw-rw1 root dialout4, 66 May 12 2001 /dev/ttyS2 crw-rw1 root dialout4, 67 May 12 2001 /dev/ttyS3 If not, you might want to do: MAKEDEV -v generic to create generic devices, including the four serial ports. So all you need to do is create a similar file for ttyS4. This command should do it: MAKEDEV -v ttyS4 Now see if your modem works. I am attaching dmesg in case anyone can figure out how to fix this. Unless I'm missing something, dmesg was not attached. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
On Sun, 09 Nov 2003, Hoyt Bailey wrote: wvdialconf would not run unless I did the following: wvdialconf /etc/wvdial.conf (or something like that) When it did run it only checked ttyS0 and ttyS1 plus some ports and didnt find the modem. However the modem shows up in KDE Control Center. Since I have the same modem, lets try this: - /etc/wvdial.conf - [Dialer Defaults] Phone = 5551234 Username = xxx Password = xxx New PPPD = yes Modem = /dev/ttyS4 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 C1 D2 +FCLASS=0 ISDN = 0 Modem Type = Analog Modem - (If you want to try this, may I suggest backing up the original /etc/wvdial.conf file first?) Hope that helps. I don't use KDE (this being a headless box) but rather pon/poff for my isp connection. -- icq:34583382 | Nethack 3.4.2 is out! http://www.nethack.org jabber: [EMAIL PROTECTED] | And how can man die better / Than facing msn:[EMAIL PROTECTED] | fearful odds / For the ashes of his fathers / yim:tsunad | and the temples of his gods? ~ Babington pgp0.pgp Description: PGP signature
Re: Installing modem.
- Original Message - From: Jesse Meyer [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 04:27 Subject: Re: Installing modem. I tryed echo ATDT555-1234 /dev/ttyS3 that should have done the same thing and nothing happened.See my previous post for more. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Monday, November 10, 2003 21:55 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] finished I attempted to transfer /var/log/demsg to floppy and received the file does not exit message. Knowing it had to be there I issued 'startx' and received the X is running message. So I did a 'killx' and another 'startx' which booted directly into KDE bypassing GUI login Then I went to console and reissued the command to transfer /var/log/demsg to floppy and file not found message appeared. Called Konk(sp) and moved to /var/log and demsg was present ckicked on same and transfered it to floppy. That is the long way around. When I clicked on the logout symbol I returned to command line. Regards; Hoyt crw-rw1 root dialout4, 64 Oct 16 09:25 /dev/ttyS0 crw-rw1 root dialout4, 65 Oct 16 09:28 /dev/ttyS1 crw-rw1 root dialout4, 66 Mar 14 2002 /dev/ttyS2 crw-rw1 root dialout4, 67 Mar 14 2002 /dev/ttyS3 Oo-kay-y, but how does this info about dmesg existing in X but not in console and copying said file to floppy relate to your modem issues? I dont know, but I thought it strange that KDE knows about the modem and apparantly other things dont. Not finding any info on minicom just means that it's not installed. In that case, I'd probably just work with pppconfig until I got frustrated enough to bother with getting minicom installed for an additional testing tool. I'll do that but it will likely bring up a score of other problems. You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A I have sent the requested message to the sourceforge.net. with a cc to this list. Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. Because somewhere in the diddleing I came across dmesg as the log file which I didnt know and thought it might have something that would help. What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This should cause the modem (assuming it's on COM4 in Windows-speak) to dial the phone number 555-1234). -- Kent Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
I installed minicom from KDE package manager. It is very easy. Issued 'minicom -s' and was able to move around and inserted a telephone number in the calling option but couldnt make anything happen. Red the man page as well. Got into initalization modem and couldnt get out without closeing window. What am I doing wrong? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Yes, from dmesg: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Redundant entry in serial pci_table. Please send the output of lspci -vv, this message (12b9,1008,12b9,00d3) and the manufacturer and name of serial board or modem board to [EMAIL PROTECTED] ttyS04 at port 0xd000 (irq = 19) is a 16550A It looks like you have two serial ports on your motherboard (00 01), in addition to your modem on 04. Apparently the PCI bus is getting confused somehow. You might want to go into the BIOS and temporarily disable the built-in serial ports, and see what that does for you. I have sent the requested message to the sourceforge.net. with a cc to this list. Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. Because somewhere in the diddleing I came across dmesg as the log file which I didnt know and thought it might have something that would help. But I'm unsure why you'd want to copy it to floppy. If you need it in a file form, you can: dmesg dmesg.txt and then copy dmesg.txt to wherever you want it, including floppy. If you just want to see the dmesg messages, you can: dmesg | more What happens with the command: echo ATDT555-1234 /dev/ttyS3 Nothing absolutely nothing and I can hear my modem sending. Dont have another number I can call. This I don't understand; you say it's doing nothing absolutely nothing and then immediately say you hear the modem sending, which means it's doing something. Either it's doing nothing or it's doing something. Which is it? I also assume you didn't really use the bogus number 555-1234? You want to use a real number, say to your cell phone, or a second line, or to the local time temperature (I didn't say that - no one can prove I did) and listen to the modem speaker for the time/temp announcement. If this works, that means the computer is seeing your modem, your modem is seeing the phone line, and the modem can dial out. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem
Hoyt Bailey wrote: I installed minicom from KDE package manager. It is very easy. Issued 'minicom -s' and was able to move around and inserted a telephone number in the calling option but couldnt make anything happen. Red the man page as well. Got into initalization modem and couldnt get out without closeing window. What am I doing wrong? Regards; Hoyt You're having tremendous difficulties getting a modem working. Could I suggest that you beg/borrow an external serial modem (not USB, not internal) from a friend, even if it's a lowly 1200baud modem? Get that working; then when you're satisfied that you're making progress, then start struggling again with your internal PCI modem (which I despise, because they're always trouble in my experience). -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 22:37 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Jesse Meyer [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 11:52 Subject: Re: Installing modem. Your output and mine agree except as follows: Yours:ttyS04 at port 0x7feo (IRQ = 10) is a 16550A Mine: ttyS04 at port 0xd000 (IRQ = 19) is a 16550A Which means you're modem is on Com5, IRQ 10. You should be able to set this in /etc/wvdial.conf, or if you run pon/poff, pppconfig should give you an option to type in /dev/ttyS04. -- Kent The problem is the(Mine) not the (Your). The (Your) works. How do you translate 0x7fe0 to Com5? A doc ref would help. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] Your output and mine agree except as follows: Yours:ttyS04 at port 0x7feo (IRQ = 10) is a 16550A Mine: ttyS04 at port 0xd000 (IRQ = 19) is a 16550A Which means you're modem is on Com5, IRQ 10. You should be able to set this in /etc/wvdial.conf, or if you run pon/poff, pppconfig should give you an option to type in /dev/ttyS04. The problem is the(Mine) not the (Your). The (Your) works. How do you translate 0x7fe0 to Com5? A doc ref would help. I don't; I translate the ttyS4 as COM5. I thought I had written this before, but perhaps it was in another thread, or it didn't make it through; you subtract one from whatever value Windows labels the COM port. If Windows calls it COM1, then in Linux it'd be 0, or more accurately, /dev/ttyS0; COM4 in Windows would be /dev/ttyS3 in Linux. (I believe I (and someone else) miswrote above, by adding a zero in the name; it should be /dev/ttyS4, not /dev/ttyS04, but not having used a serial port in ages, I'm not for certain.) -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
I have come into this thread pretty late, but from what I understand, you are trying to get a modem to work. It's a PCI modem, and you can see it mentioned in the kernel as ttyS04. The problem, as I see it, is that you can't get the modem to respond to any calls from any programs? If I understand this all correctly, I had a horrible time with this a while back with another computer, where I could get the PCI modem automatically recognized and used in RedHat, but in Debian I could get nothing out of it. Some wise user showed me how to fix this: 1. Use /dev/MAKEDEV to make the ttyS4 device in /dev, as your kernel will normally not make it for you. 2. The device should now be available under that name, and you should be able to use it freely in any system, you should probably also symlink it to /dev/modem so that some dialer programs will work properly. I hope this helps, tell me if I misunderstand what you are trying to do, and sorry if this was OT. Aaron Hsu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Monday, November 10, 2003 10:22 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] Your output and mine agree except as follows: Yours:ttyS04 at port 0x7feo (IRQ = 10) is a 16550A Mine: ttyS04 at port 0xd000 (IRQ = 19) is a 16550A Which means you're modem is on Com5, IRQ 10. You should be able to set this in /etc/wvdial.conf, or if you run pon/poff, pppconfig should give you an option to type in /dev/ttyS04. The problem is the(Mine) not the (Your). The (Your) works. How do you translate 0x7fe0 to Com5? A doc ref would help. I don't; I translate the ttyS4 as COM5. I thought I had written this before, but perhaps it was in another thread, or it didn't make it through; you subtract one from whatever value Windows labels the COM port. If Windows calls it COM1, then in Linux it'd be 0, or more accurately, /dev/ttyS0; COM4 in Windows would be /dev/ttyS3 in Linux. (I believe I (and someone else) miswrote above, by adding a zero in the name; it should be /dev/ttyS4, not /dev/ttyS04, but not having used a serial port in ages, I'm not for certain.) -- Kent Thanks for the info: Since my windows lists the modom on com4 then it should be mounted on ttyS03 or TTYS03 as listed on my system. Part of the system recognize the modem (KDE) but it shows it mounted: I/O Ports: d000-d007 US Robitics//3Com 56K fakmodem 5610 d000-d007 serial (auto) I am confused; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Aaron W. Hsu [EMAIL PROTECTED] To: Kent West [EMAIL PROTECTED] Cc: debian-user [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, November 10, 2003 10:52 Subject: Re: Installing modem. I have come into this thread pretty late, but from what I understand, you are trying to get a modem to work. It's a PCI modem, and you can see it mentioned in the kernel as ttyS04. The problem, as I see it, is that you can't get the modem to respond to any calls from any programs? If I understand this all correctly, I had a horrible time with this a while back with another computer, where I could get the PCI modem automatically recognized and used in RedHat, but in Debian I could get nothing out of it. Some wise user showed me how to fix this: 1. Use /dev/MAKEDEV to make the ttyS4 device in /dev, as your kernel will normally not make it for you. 2. The device should now be available under that name, and you should be able to use it freely in any system, you should probably also symlink it to /dev/modem so that some dialer programs will work properly. I hope this helps, tell me if I misunderstand what you are trying to do, and sorry if this was OT. Aaron Hsu You are on target however there is some question, in my mind at least, where the modem is installed in linux. KDE says it is d000-d007 others say it should be ttyS04 and ttyS4 my system seems to list ttyS? as TTYS??. Windows XP installed it on com4, which impilys that it should be probably on TTYS03. Perhaps I'm just confused because I dont know enough. Thanks for your input I'll keep it in mind. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: You are on target however there is some question, in my mind at least, where the modem is installed in linux. KDE says it is d000-d007 others say it should be ttyS04 and ttyS4 my system seems to list ttyS? as TTYS??. Windows XP installed it on com4, which impilys that it should be probably on TTYS03. Perhaps I'm just confused because I dont know enough. Thanks for your input I'll keep it in mind. Regards; Hoyt I have no uppercase TTYs in my /dev directory. Have never heard of such? Perhaps earlier in your attempts to get the modem working you manually created these device files? This command, executed as root from within the /dev directory, should create the standard tty device files: ./MAKEDEV std Then I'd try minicom and play with the COM port settings; after each change, try dialing your cell phone with something like ATDT555-555-1234 When you hear the modem dial out and/or your cell phone ring, you know you're on the right COM port. (You can hang up the modem with ATZ.) -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Kent West [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Monday, November 10, 2003 16:21 Subject: Re: Installing modem. Hoyt Bailey wrote: You are on target however there is some question, in my mind at least, where the modem is installed in linux. KDE says it is d000-d007 others say it should be ttyS04 and ttyS4 my system seems to list ttyS? as TTYS??. Windows XP installed it on com4, which impilys that it should be probably on TTYS03. Perhaps I'm just confused because I dont know enough. Thanks for your input I'll keep it in mind. Regards; Hoyt I have no uppercase TTYs in my /dev directory. Have never heard of such? I made a mistake I would have sworn that the devices listed by lspci were TTYS?: Here is ttyS? list from lspci: Attached: Perhaps earlier in your attempts to get the modem working you manually created these device files? This command, executed as root from within the /dev directory, should create the standard tty device files: ./MAKEDEV std /dev/ttyS? files agree with ls-1.txt Then I'd try minicom and play with the COM port settings; after each change, try dialing your cell phone with something like ATDT555-555-1234 When you hear the modem dial out and/or your cell phone ring, you know you're on the right COM port. (You can hang up the modem with ATZ.) -- Kent minicom dosent exist on my system. 'minicom' command results in file not found message and man minicom results are simular. Also there is no entry in info for minicom. The entry in dmesg for ttyS3 is different from ttyS0 ttyS1 it may be helpful. There was somthing strange happened. I booted normally and at the GUI login cntl-alt-F1 to get back to command line. When finished I attempted to transfer /var/log/demsg to floppy and received the file does not exit message. Knowing it had to be there I issued 'startx' and received the X is running message. So I did a 'killx' and another 'startx' which booted directly into KDE bypassing GUI login Then I went to console and reissued the command to transfer /var/log/demsg to floppy and file not found message appeared. Called Konk(sp) and moved to /var/log and demsg was present ckicked on same and transfered it to floppy. That is the long way around. When I clicked on the logout symbol I returned to command line. Regards; Hoyt crw-rw1 root dialout4, 64 Oct 16 09:25 /dev/ttyS0 crw-rw1 root dialout4, 65 Oct 16 09:28 /dev/ttyS1 crw-rw1 root dialout4, 66 Mar 14 2002 /dev/ttyS2 crw-rw1 root dialout4, 67 Mar 14 2002 /dev/ttyS3 dmesg Description: Binary data
Installing modem
I am not a subscriber to [EMAIL PROTECTED] . Therefore I would apperciate a Cc. dmesg requested that I send the following information to this address. Manufacturer: U.S. Robitics/3Com 56K Fax Modem. Card: Model 5610B (Rev 01) (Prog-if 02[16550A]) Any help would be appericated. Regards; Hoyt dmesg Description: Binary data 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3189 Subsystem: Giga-byte Technology: Unknown device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 8 Region 0: Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [a0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2 Command: RQ=31 SBA- AGP+ 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b168 (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e800-e9ff Prefetchable memory behind bridge: d800-e7ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) Subsystem: US Robotics/3Com: Unknown device 00d3 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 19 Region 0: I/O ports at d000 [size=8] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=2 PME- 00:10.0 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology: Unknown device 5004 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin A routed to IRQ 21 Region 4: I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:10.1 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology: Unknown device 5004 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin B routed to IRQ 21 Region 4: I/O ports at d800 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:10.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 80) (prog-if 00 [UHCI]) Subsystem: Giga-byte Technology: Unknown device 5004 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin C routed to IRQ 21 Region 4: I/O ports at dc00 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:10.3 USB Controller: VIA Technologies, Inc.: Unknown device 3104 (rev 82) (prog-if 20) Subsystem: Giga-byte Technology: Unknown device 5004 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: Kent West [EMAIL PROTECTED] Then I'd try minicom and play with the COM port settings; after each minicom dosent exist on my system. 'minicom' command results in file not found message and man minicom results are simular. Also there is no entry in info for minicom. The entry in dmesg for ttyS3 is different from ttyS0 ttyS1 it may be helpful. There was somthing strange happened. I booted normally and at the GUI login cntl-alt-F1 to get back to command line. When finished I attempted to transfer /var/log/demsg to floppy and received the file does not exit message. Knowing it had to be there I issued 'startx' and received the X is running message. So I did a 'killx' and another 'startx' which booted directly into KDE bypassing GUI login Then I went to console and reissued the command to transfer /var/log/demsg to floppy and file not found message appeared. Called Konk(sp) and moved to /var/log and demsg was present ckicked on same and transfered it to floppy. That is the long way around. When I clicked on the logout symbol I returned to command line. Regards; Hoyt crw-rw1 root dialout4, 64 Oct 16 09:25 /dev/ttyS0 crw-rw1 root dialout4, 65 Oct 16 09:28 /dev/ttyS1 crw-rw1 root dialout4, 66 Mar 14 2002 /dev/ttyS2 crw-rw1 root dialout4, 67 Mar 14 2002 /dev/ttyS3 Oo-kay-y, but how does this info about dmesg existing in X but not in console and copying said file to floppy relate to your modem issues? Not finding any info on minicom just means that it's not installed. In that case, I'd probably just work with pppconfig until I got frustrated enough to bother with getting minicom installed for an additional testing tool. You say ttyS3 is different from ttyS0 ttyS1; um, yes. They're different files. Maybe you mean something else when you say they're different? Why are you trying to transfer dmesg to floppy? Without knowing the exact command you used, as whom, in what directory, it's hard to say what might have gone wrong with your copy attempt. What happens with the command: echo ATDT555-1234 /dev/ttyS3 This should cause the modem (assuming it's on COM4 in Windows-speak) to dial the phone number 555-1234). -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
1. Use /dev/MAKEDEV to make the ttyS4 device in /dev, as your kernel will normally not make it for you. 2. The device should now be available under that name, and you should be able to use it freely in any system, you should probably also symlink it to /dev/modem so that some dialer programs will work properly. . . . You are on target however there is some question, in my mind at least, where the modem is installed in linux. KDE says it is d000-d007 others say it should be ttyS04 and ttyS4 my system seems to list ttyS? as TTYS??. Windows XP installed it on com4, which impilys that it should be probably on TTYS03. Perhaps I'm just confused because I dont know enough. Thanks for your input I'll keep it in mind. Regards; Hoyt To find out what device you should be using, I recomend this method, which worked for me. If you are using a PCI modem, then it is almost guaranteed that your device will be something like ttyS4. To find out what you should use in /dev/MAKEDEV, just dmesg | grep tty or whatever happens to bring up the relevant lines about your modem. Should it say something like ttyS05, then you should MAKEDEV ttyS5. In my case, I saw ttyS04, so I think [it has been a while] I ran /dev/MAKEDEV /dev/ttyS4 and it created the device properly and the modem responded. The thing that confused me back then was that I thought the modem device was already created, since I already had ttyS0-3, but I didn't realize that I had to make another device for ttyS04 that the dmesg reported. I hope this helps. Aaron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Installing modem.
I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD and booted debian. Did ^alt F1 read man rpm man alien. No problem mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked for files 3commdn and found the following: /usr/share/doc/3commdn /usr/share/doc/3commdn/changelog.Debian.gz /usr/share/doc/3commdn/copyright /usr/doc/3commdn /usr/dpkg/info/3commdn/.postinst /usr/dpkg/info/3commdn/.list /usr/dpkg/info/3commdn/.prerm /usr/dpkg/info/3commdn/.conffiles /usr/dpkg/info/3commdn/.md5sums Read the copyright file and there is a statement (Not Installed). Went back to X read the log XFree86 no indication of modem. Tryed to start connection -No-. Any Suggestions? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote:
I recieved my USR5610B and replaced the Intel winmodem. Turned on the
computer and it dialed the ISP in Windows. So I said hey this is going to
be easy. Went to U.S. Robitics website and no debian driver only RH,
Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD
and booted debian. Did ^alt F1 read man rpm man alien. No problem
mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked
for files 3commdn and found the following:
/usr/share/doc/3commdn
/usr/share/doc/3commdn/changelog.Debian.gz
/usr/share/doc/3commdn/copyright
/usr/doc/3commdn
/usr/dpkg/info/3commdn/.postinst
/usr/dpkg/info/3commdn/.list
/usr/dpkg/info/3commdn/.prerm
/usr/dpkg/info/3commdn/.conffiles
/usr/dpkg/info/3commdn/.md5sums
Read the copyright file and there is a statement (Not Installed). Went back
to X read the log XFree86 no indication of modem. Tryed to start
connection -No-. Any Suggestions?
Regards;
Hoyt
I assume this is a _real_ modem? If so, it should be assigned to a COM
port {1-4]. What COM port is it assigned to in Windows? Subtract one
from that number, and that's the port in Linux. For example, if it's
COM2 in Windows, it'll be /dev/ttyS1 in Linux. If it's COM3 in Windows,
it'll be /dev/ttyS2 in Linux.
If it's a real modem, don't worry about drivers; it'll just work.
Run pppconfig; let it autodetect the modem, or mnaually specify the
COM port if necessary. Once that's done, you can use pon to start your
ppp connection, or poff to turn ppp off. Or you can use any of the
GUI-style connection tools, like KISP or KPPP (I think those are real
names; I never use them).
You can also use minicom to do some basic modem activity; it's a
terminal program.
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
On 9 Nov 2003 at 7:24, Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD and booted debian. Did ^alt F1 read man rpm man alien. No problem mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked for files 3commdn and found the following: /usr/share/doc/3commdn /usr/share/doc/3commdn/changelog.Debian.gz /usr/share/doc/3commdn/copyright /usr/doc/3commdn /usr/dpkg/info/3commdn/.postinst /usr/dpkg/info/3commdn/.list /usr/dpkg/info/3commdn/.prerm /usr/dpkg/info/3commdn/.conffiles /usr/dpkg/info/3commdn/.md5sums Read the copyright file and there is a statement (Not Installed). Went back to X read the log XFree86 no indication of modem. Tryed to start connection -No-. Any Suggestions? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I have the same exact modem and it should *NOT* need a driver. It is controller based, and it should work like an external modem, even thought it is PCI. I had mine working under Suse 8.1 and Red Hat 7.0, but have not figured out how to get it working under debian woody. I just tried those other distro before I was enlightened. I will be interested to follow this thread also. I but the modem in a windows box and got the port value, but every serial port I try I get modem is busy. I can see the modem under KDE - control center - information - PCI. It's at IRQ3 and I/O port b800. Salutations, Marlin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
On Sun, 09 Nov 2003, Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. [ ... snip discussion of trying to adapt rpm drivers ... ] I believe that's a controller based modem. An lspci (as root) should return something like this: [ ... other devices ... ] 00:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) If you see it, try a 'grep ttyS /var/log/dmesg'. You should get something like this: ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A ttyS04 at port 0x7fe0 (irq = 10) is a 16550A If you have three choices (like my system does) and ttyS00 and ttyS01 exists, those are probably the motherboard's serial ports. The odd man out is ttyS04 (which, oddly enough, is how my USR5610 set itself up as - com5 in dosland). Fire up wvdialconf, and see if it works. Report back if it doesn't. Remember, if you can hear it dial out, then the driver is probably working and you have the right serial port, if you can't connect, there is probably something wrong with your ppp configuration. Feel free to ask as many questions as you want, I seem to own the exact same model. Its a good modem, and stays connected for days when I want it to. :) ~ Jesse Meyer -- icq:34583382 | Nethack 3.4.2 is out! http://www.nethack.org jabber: [EMAIL PROTECTED] | And how can man die better / Than facing msn:[EMAIL PROTECTED] | fearful odds / For the ashes of his fathers / yim:tsunad | and the temples of his gods? ~ Babington pgp0.pgp Description: PGP signature
Re: Installing modem.
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 09:31 Subject: Re: Installing modem. On 9 Nov 2003 at 7:24, Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD and booted debian. Did ^alt F1 read man rpm man alien. No problem mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked for files 3commdn and found the following: /usr/share/doc/3commdn /usr/share/doc/3commdn/changelog.Debian.gz /usr/share/doc/3commdn/copyright /usr/doc/3commdn /usr/dpkg/info/3commdn/.postinst /usr/dpkg/info/3commdn/.list /usr/dpkg/info/3commdn/.prerm /usr/dpkg/info/3commdn/.conffiles /usr/dpkg/info/3commdn/.md5sums Read the copyright file and there is a statement (Not Installed). Went back to X read the log XFree86 no indication of modem. Tryed to start connection -No-. Any Suggestions? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I have the same exact modem and it should *NOT* need a driver. It is controller based, and it should work like an external modem, even thought it is PCI. I had mine working under Suse 8.1 and Red Hat 7.0, but have not figured out how to get it working under debian woody. I just tried those other distro before I was enlightened. I will be interested to follow this thread also. I but the modem in a windows box and got the port value, but every serial port I try I get modem is busy. I can see the modem under KDE - control center - information - PCI. It's at IRQ3 and I/O port b800. Salutations, Marlin Marlin, I seem to have some differences maybe some one can tell us how to get them working: KDE Information: PCI 00:0b Serial Controller: US Robotics/3com 56K Fax Modem Model 5610 (Rev 01)(Prog-if 02[16550]) Subsystem: US Robitics/3com unknown device 00d3 Flags: medium devsel, IR019 I/O Ports at d000 size 8 Capabilities: dc power management version 2. under I/O Ports: d000-d007 US Robotics/3 com 56k Faxmodem 5610 d000-d007 serian (auto) I dont know what it all means but I didnt see a com port unless d000 is one. At least the system knows its there. What do I do now? Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Charles-Roberts To: Hoyt Bailey [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 13:16 Subject: Re: Installing modem. Hoyt Bailey wrote: - Original Message - From: Charles-Roberts To: Hoyt Bailey [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 09:50 Subject: Re: Installing modem. Hoyt Bailey wrote: I recieved my USR5610B and replaced the Intel winmodem. Turned on the computer and it dialed the ISP in Windows. So I said hey this is going to be easy. Went to U.S. Robitics website and no debian driver only RH, Mandrake, SUSE. Ok I can do rpm. downloaded rpm driver put it on a CD and booted debian. Did ^alt F1 read man rpm man alien. No problem mounted CD issued alien -i /cdrom/pkgname ran ok w/no errors. Checked for files 3commdn and found the following: /usr/share/doc/3commdn /usr/share/doc/3commdn/changelog.Debian.gz /usr/share/doc/3commdn/copyright /usr/doc/3commdn /usr/dpkg/info/3commdn/.postinst /usr/dpkg/info/3commdn/.list /usr/dpkg/info/3commdn/.prerm /usr/dpkg/info/3commdn/.conffiles /usr/dpkg/info/3commdn/.md5sums Read the copyright file and there is a statement (Not Installed). Went back to X read the log XFree86 no indication of modem. Tryed to start connection -No-. Any Suggestions? Regards; Hoyt Hoyt; PS my earlier reply. There may not be a /dev/ttyS4 defined. If not, do this command: ls -al /dev/ttyS* note the minor/major numbers from ttyS0 to ttyS3 do command 'mknod See 'man mknod' HTH Charles I have a problem with mkno its written in debian(not clear). I issued the following commands mknod -m TTYS4 c 4 68 (invalid mode) mknod -m MODE TTYS4 c 4 68 (invalid mode) mknod -m=MODE TTYS4 c 4 68 (invalid mode) That was all the options mentioned. Could you provide the correct command. Why the hell are you using CAPITAL letters? DID you read 'man setserial' 'man mknod'? the command is: mknod /dev/ttyS4 c 4 68 You may have to chmod to correct user. Usually the 'Group' user is dialout. Add what ever user will be using this device to /etc/group 'dialout'. On your first post the command: setserial -G /dev/ttyS4 NOTE the capital 'S' should ^ be an 'S'? or were you refering to ttyS4? As usuall confused; What do you think? Read 'man setserial'. It is the 'S' in /dev/ttyS4. If you had issued the command 'ls -al /dev/ttyS*' you would have seen for yourself th capital 'S'. I did and copyed the previous 3 exactly except for the 68. Hoyt Maybe I am a little harsh!!! Maybe English is not your mother language! It is but man pages are written in linux (var debian) not english. Maybe you have no experience with linux!! True, the man pages are not easy to read. Very little. But, the man pages get easer with practice READING them. You must try. You must think. You must try to help yourself. It is not good for someone to hold you hand. You will never learn anything that way. If you are going to use Debian you had best learn to READ READ READ READ READ. And to THINK THINK THINK THINK. You MUST learn a lot about the 'cli'. Anyway, I use this very same moden with Debian I will help you get it working. It works very good for me. HTH Charles PS. Is the debian-user mailing list still messed up where if one post to the list one gets a lot of virus for microsoft? Thanks for the info the man setserial I didnt read. I havent gotten any viruses or spam either. Apparantly many do but Norton Spam Defender are protecting me pretty well. Regards; Hoyt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
- Original Message - From: Jesse Meyer [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 11:52 Subject: Re: Installing modem. Your output and mine agree except as follows: Yours:ttyS04 at port 0x7feo (IRQ = 10) is a 16550A Mine: ttyS04 at port 0xd000 (IRQ = 19) is a 16550A wvdialconf would not run unless I did the following: wvdialconf /etc/wvdial.conf (or something like that) When it did run it only checked ttyS0 and ttyS1 plus some ports and didnt find the modem. However the modem shows up in KDE Control Center. I couldnt get anything out of setserial -a or -G while it run the output appeared larger than than the screen and wouldnt record on floppy or be controled by less. I also ran wvdial but didnt hear anything. You are right about it being a good modem on one trial it appeared to double my download rate up to 11kbs from windows. Regards; Hoyt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing modem.
Hoyt Bailey wrote: - Original Message - From: Jesse Meyer [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED] Sent: Sunday, November 09, 2003 11:52 Subject: Re: Installing modem. Your output and mine agree except as follows: Yours:ttyS04 at port 0x7feo (IRQ = 10) is a 16550A Mine: ttyS04 at port 0xd000 (IRQ = 19) is a 16550A Which means you're modem is on Com5, IRQ 10. You should be able to set this in /etc/wvdial.conf, or if you run pon/poff, pppconfig should give you an option to type in /dev/ttyS04. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
installing modem
Whats the process to install a modem for a tcp/ip ppp conection to use the internet? _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installing modem
Install the package pppconfig or dunc. They both create a connection by asking simple questions. pppconfig is my preference for a quick and easy setup. hope this helps, troy Endless Loop -- See Loop, Endless mailto:[EMAIL PROTECTED] http://www.dakota.net/~troy On Thu, 18 Jun 1998, Micha Feigin wrote: Whats the process to install a modem for a tcp/ip ppp conection to use the internet? _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
