Re: Modem not connected after hardware change
Max Mothwurf <[email protected]> Fri, 02 Dec 2016 16:52:46 +0100
| Newsgroups | gmane.comp.telephony.fax.hylafax.user |
|---|---|
| Message-ID | <2551227.D44xfsBdfh@southpole> |
Am Donnerstag, 10. November 2016, 13:07:47 CET schrieb Lee Howard: > On 11/10/2016 04:13 AM, Max Mothwurf wrote: > > Am Donnerstag, 3. November 2016, 10:11:21 CET schrieb Lee Howard: > >> On 11/02/2016 07:49 AM, Max Mothwurf wrote: > >>> Hi, > >>> > >>> my old motherboard got defective, and I had to change it to something > >>> new, > >>> an MSI H110M PRO-D, which still has a com-port: > >>> > >>> southpole:/home # dmesg | grep tty > >>> [ 0.000000] console [tty0] enabled > >>> [ 1.301116] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) > >>> is > >>> a > >>> 16550A > >>> [ 1.321787] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = > >>> 115200) is a 16550A > >>> [ 1.332473] tty ttyS15: hash matches > >>> [ 4.396806] dw-apb-uart.2: ttyS4 at MMIO 0xdff2b000 (irq = 20, > >>> base_baud = 115200) is a 16550A > >>> > >>> IMHO that looks like ttyS0 is working properly. Permissions on > >>> /dev/ttyS0 > >>> are OK as well, but during probe hylafax cant access the port: > >>> southpole:/home # faxaddmodem ttyS0 > >>> Sorry, the device is currently in use by another program. > >>> - no idea which one that could be > >>> Hylafax version is hylafax+ 5.5.6 > >> > >> That "sorry..." message is because there is a lock file found for that > >> modem. Look in /var/lock or /var/lock/uucp for a lock file and remove > >> it. > > > > I did a new installation of the whole system, but still can access. Speed > > probe says that it cant deduce the speed. > > southpole: # dmesg | grep tty > > [ 0.000000] console [tty0] enabled > > [ 1.053210] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is > > a > > 16550A > > [ 1.073867] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = > > 115200) is a 16550A > > [ 3.656479] dw-apb-uart.2: ttyS4 at MMIO 0xdf12b000 (irq = 20, > > base_baud = 115200) is a 16550A > > > > If course I tried ttyS1 as well.... > > Have you tried accessing the modem with minicom or cu? Problem is solved...hardware problem. The shop installed the wrong connector cable - obviously there are two different kinds Thanks for supporting anyway! MAx ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null *To learn about commercial HylaFAX(tm) support, mail [email protected].*