Skip to contentSkip to conversation

Modem Inaccessible

DISCUSSION Peter 3 participants 6 messages Jul 17, 2006 – Jul 19, 2006

lore
Share & tools
lore

Peter

author
#0 lore raw

Slackware 10.2, kernel 2.6.16

Suddenly I cannot access my modem.

Minicom will just stay offline.

efax version 0.9
minicom version 2.1

Giving command: fax receive
I get:

efax: 12:25 opened /dev/modem
efax: 12:25 Error: tcgetattr on fd=3 failed: Input/output error
efax: 12:25 Error: fax device write: Input/output error
efax: 12:29 Error: fax device write: Input/output error
efax: 12:31 sync: dropping DTR
efax: 12:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 12:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 37:31 Error: sync: modem not responding
efax: 37:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 37:31 done, returning 2 (unrecoverable error) There were errors (see 0717143714.log).

I tried it with kernel 2.4.31, it will not work either.

I moved over to Fedora4, same machine, same HD. Minicom is on-line and dials and pppd dialing is working as well, meaning there is nothing wrong with the hardware.

Here is the output of lsmod in Fed4 w/o the snd_ bits:

Module                  Size  Used by
md5                     4033  1 
ipv6                  268097  8 
parport_pc             28933  1 
lp                     13001  0 
parport                40585  2 parport_pc,lp
autofs4                29253  2 
it87                   23521  0 
eeprom                  7377  0 
i2c_sensor              3521  2 it87,eeprom
i2c_isa                 2241  0 
rfcomm                 42333  0 
l2cap                  30661  5 rfcomm
bluetooth              56133  4 rfcomm,l2cap
sunrpc                167813  1 
ipt_REJECT              5569  1 
ipt_state               1857  4 
ip_conntrack           41497  1 ipt_state
iptable_filter          2881  1 
ip_tables              19521  3 ipt_REJECT,ipt_state,iptable_filter
ide_scsi               18761  0 
scsi_mod              148105  1 ide_scsi
dm_mod                 58101  0 
video                  15941  0 
button                  6609  0 
ac                      4805  0 
uhci_hcd               35152  0 
ehci_hcd               41037  0 
shpchp                 94405  0 
i2c_viapro              8017  0 
i2c_core               21569  5 it87,eeprom,i2c_sensor,i2c_isa,i2c_viapro
snd_via82xx            30081  1 
gameport               18633  1 snd_via82xx
soundcore              10913  2 snd
via_rhine              28361  0 
mii                     5441  1 via_rhine
dmfe                   23525  0 
floppy                 65269  0 
ext3                  132553  3 
jbd                    86233  1 ext3

And here lsmod of Slack:
Module Size Used by Not tainted

i2c-dev                 3620   0 (unused)
i2c-core               12676   0 [i2c-dev]
snd-pcm-oss            36736   0
snd-mixer-oss          12376   2 [snd-pcm-oss]
pci_hotplug            15236   0
uhci                   24284   0 (unused)
ehci-hcd               17516   0 (unused)
usbcore                59148   1 [uhci ehci-hcd]
snd-via82xx            13376   2
gameport                1420   0 [snd-via82xx]
Module                  Size  Used by    Not tainted
i2c-dev                 3620   0 (unused)
i2c-core               12676   0 [i2c-dev]
snd-pcm-oss            36736   0
snd-mixer-oss          12376   2 [snd-pcm-oss]
pci_hotplug            15236   0
uhci                   24284   0 (unused)
ehci-hcd               17516   0 (unused)
usbcore                59148   1 [uhci ehci-hcd]
snd-via82xx            13376   2
gameport                1420   0 [snd-via82xx]
soundcore               3396   4 [snd]
via-rhine              12336   0 (unused)
mii                     2272   0 [via-rhine]
pcmcia_core            39172   0
ide-scsi                9392   0
dmfe                   12577   1
crc32                   2880   0 [via-rhine dmfe]
agpgart                45508   0 (unused)
lp                      6404   0
parport_pc             15044   1
parport                22824   1 [lp parport_pc]

Where could be the hitch that the modem is not responding in slackware?

Thanks for any help!

Signature · 7 lines
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#1 lore raw

I can't be sure, Peter, but my hunch is that you are looking in the wrong place. I'm assuming the modem is attached to a serial port and is not one of those pseudo-modems that requires a special module (If I'm wrong, then you really left out important info) in what follows.

Serial port support is all but always compiled into kernels, not added as modules. (And I don't see anything that looks like a serial-port module in either of the lists you sent us, in any case.) But setting up serial ports so they actually work requires running "setserial" with appropriate values.

I'd suggest you approach this by:

(a) Finding out what /dev/modem is a symlink to
(b) Running setserial on that device (e.g., "setserial /dev/ttyS0") to see what settings are present.

If they are different between Slackware and Fedora, that points to your problem. If you can't spot it yourself, post here the COMPLETE results of this testing and probably someone can help you spot it.

You might also check the init-script sructures of the two distros to see where and how (and even if) both run setserial.

Quoted 79 lines · Peter

Slackware 10.2, kernel 2.6.16

Suddenly I cannot access my modem.

Minicom will just stay offline.

efax version 0.9
minicom version 2.1

Giving command: fax receive
I get:

efax: 12:25 opened /dev/modem
efax: 12:25 Error: tcgetattr on fd=3 failed: Input/output error
efax: 12:25 Error: fax device write: Input/output error
efax: 12:29 Error: fax device write: Input/output error
efax: 12:31 sync: dropping DTR
efax: 12:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 12:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 37:31 Error: sync: modem not responding
efax: 37:31 Error: tcgetattr on fd=3 failed: Input/output error
efax: 37:31 done, returning 2 (unrecoverable error) There were errors (see 0717143714.log).

I tried it with kernel 2.4.31, it will not work either.

I moved over to Fedora4, same machine, same HD. Minicom is on-line and dials and pppd dialing is working as well, meaning there is nothing wrong with the hardware.

Here is the output of lsmod in Fed4 w/o the snd_ bits:

Module                  Size  Used by
md5                     4033  1 ipv6                  268097  8 parport_pc             28933  1 lp                     13001  0 parport                40585  2 parport_pc,lp
autofs4                29253  2 it87                   23521  0 eeprom                  7377  0 i2c_sensor              3521  2 it87,eeprom
i2c_isa                 2241  0 rfcomm                 42333  0 l2cap                  30661  5 rfcomm
bluetooth              56133  4 rfcomm,l2cap
sunrpc                167813  1 ipt_REJECT              5569  1 ipt_state               1857  4 ip_conntrack           41497  1 ipt_state
iptable_filter          2881  1 ip_tables              19521  3 ipt_REJECT,ipt_state,iptable_filter
ide_scsi               18761  0 scsi_mod              148105  1 ide_scsi
dm_mod                 58101  0 video                  15941  0 button                  6609  0 ac                      4805  0 uhci_hcd               35152  0 ehci_hcd               41037  0 shpchp                 94405  0 i2c_viapro              8017  0 i2c_core               21569  5 it87,eeprom,i2c_sensor,i2c_isa,i2c_viapro
snd_via82xx            30081  1 gameport               18633  1 snd_via82xx
soundcore              10913  2 snd
via_rhine              28361  0 mii                     5441  1 via_rhine
dmfe                   23525  0 floppy                 65269  0 ext3                  132553  3 jbd                    86233  1 ext3

And here lsmod of Slack:
Module Size Used by Not tainted

i2c-dev                 3620   0 (unused)
i2c-core               12676   0 [i2c-dev]
snd-pcm-oss            36736   0
snd-mixer-oss          12376   2 [snd-pcm-oss]
pci_hotplug            15236   0
uhci                   24284   0 (unused)
ehci-hcd               17516   0 (unused)
usbcore                59148   1 [uhci ehci-hcd]
snd-via82xx            13376   2
gameport                1420   0 [snd-via82xx]
Module                  Size  Used by    Not tainted
i2c-dev                 3620   0 (unused)
i2c-core               12676   0 [i2c-dev]
snd-pcm-oss            36736   0
snd-mixer-oss          12376   2 [snd-pcm-oss]
pci_hotplug            15236   0
uhci                   24284   0 (unused)
ehci-hcd               17516   0 (unused)
usbcore                59148   1 [uhci ehci-hcd]
snd-via82xx            13376   2
gameport                1420   0 [snd-via82xx]
soundcore               3396   4 [snd]
via-rhine              12336   0 (unused)
mii                     2272   0 [via-rhine]
pcmcia_core            39172   0
ide-scsi                9392   0
dmfe                   12577   1
crc32                   2880   0 [via-rhine dmfe]
agpgart                45508   0 (unused)
lp                      6404   0
parport_pc             15044   1
parport                22824   1 [lp parport_pc]
Quoted 3 lines

Where could be the hitch that the modem is not responding in slackware?

Thanks for any help!

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

author
#2 lore raw

Thanks Ray!

Quoted 1 line · [email protected] said:

I'm assuming the modem is attached to a serial port

Yes, has been for years.

ls -l /dev/modem
lrwxrwxrwx 1 root root 10 2006-07-18 20:29 /dev/modem -> /dev/tts/1

sudo /sbin/setserial /dev/ttyS1 -a

/dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

ttyS1 used to be the place from which to run the modem I know for sure when I had kppp installed.

sudo /sbin/setserial /dev/ttyS2 -a

/dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

Now this is the output in Fed4 at ttyS0:

/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test

To which modem etc. connects properly.

Doing
sudo /sbin/setserial /dev/ttyS1 uart 16550A
I get

heisspf@~:$ sudo /sbin/setserial /dev/ttyS1 -a         
/dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

With microcom which I snatched from my DSL box where again the modem is working properly:
sudo /usr/local/Microcom/microcom
Try /dev/ttyS0
/dev/ttyS0 not found
Try /dev/ttyS1
/dev/ttyS1 not responding (after I set the uart 16550A)

Try /dev/ttyS2
/dev/ttyS2 not responding

Try /dev/ttyS3
/dev/ttyS3 not responding

In this kernel 2.6.16 there is no more ttyS0 instead /dev/tts/1 to 3. I know it was working with kernel 2.6.14 but now it does not even work with 2.4.31.

Something broke somewhere.

Fedora4 does not run setserial neither does DSL.

Regards

Signature · 7 lines
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#3 lore raw

See comments below.

Quoted 9 lines · Peter

Thanks Ray!

Quoted 1 line · [email protected] said:

I'm assuming the modem is attached to a serial port

Yes, has been for years.

It would help, Peter, if you were more thorough about indicating which configuration each report is from, I'm assuming the next few entries are from the Slackware version that does NOT work.

Quoted 10 lines

ls -l /dev/modem
lrwxrwxrwx 1 root root 10 2006-07-18 20:29 /dev/modem -> /dev/tts/1

sudo /sbin/setserial /dev/ttyS1 -a

/dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq
Quoted 8 lines

ttyS1 used to be the place from which to run the modem I know for sure when I had kppp installed.

sudo /sbin/setserial /dev/ttyS2 -a

/dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

If the above is Slackware, then ...

1. What does "sudo /sbin/setserial /dev/ttyS0 -a" report for it?

2. What does "sudo /sbin/setserial /dev/tts/1 -a" report for it?

3. What does "sudo /sbin/setserial /dev/tts/0 -a" (assuming there is a 0 there) report for it?

4. During init, does anything about serial ports appear in dmesg output? If so, quote it in your reply.

As a general matter, the "UART: unknown" is usually (in my actual experience, always) an indicator that the device entry is not pointing to an actual serial port.

Quoted 8 lines

Now this is the output in Fed4 at ttyS0:

/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test

To which modem etc. connects properly.

I don't know what "modem etc." means. Do you mean that in Fedora, /dev/modem is a symlink to this device?

Quoted 7 lines

Doing
sudo /sbin/setserial /dev/ttyS1 uart 16550A
I get

heisspf@~:$ sudo /sbin/setserial /dev/ttyS1 -a         /dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

Are you back to talking about the Slackware setup again? If so, setting the UART by hand doesn't help if the device is not actually pointing to physical hardware.

Quoted 1 line

With microcom which I snatched from my DSL box where again the modem is working properly:

Is the "DSL box" a physically different computer, or the same one booted differently? And are we once again back to Slackware again?

Quoted 3 lines

sudo /usr/local/Microcom/microcom
Try /dev/ttyS0
/dev/ttyS0 not found

This is odd. What does "ls -l /dev/ttyS*" report?

Quoted 10 lines

Try /dev/ttyS1
/dev/ttyS1 not responding (after I set the uart 16550A)

Try /dev/ttyS2
/dev/ttyS2 not responding

Try /dev/ttyS3
/dev/ttyS3 not responding

In this kernel 2.6.16 there is no more ttyS0 instead /dev/tts/1 to 3. I know it was working with kernel 2.6.14 but now it does not even work with 2.4.31.

Did it used to work with 2.4.31? Or is what you are describing in fact te result of kernel updates? If you go back to a Slackware kernel that the modem presiously worked with, does it once again work?

Peter, there is a real and important difference between these two descriptions:

"The modem suddenly stopped working"
"I changed to a new kernel and the modem doesn't work"

Which of them is the correct summary of your Slackware observations?

Quoted 3 lines

Something broke somewhere.

Fedora4 does not run setserial neither does DSL.

How do you know? Did you grep for "setserial" in the appropriate directory (probably /etc/init.d)? If not, how did you check this?

Quoted 1 line

Regards

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#4 lore raw
Quoted 11 lines · Ray Olszewski

See comments below.

Quoted 8 lines · Peter

Thanks Ray!

Quoted 1 line · [email protected] said:

I'm assuming the modem is attached to a serial port

Yes, has been for years.

Been watching the thread and wonder if the following will
help since I am running Slack10.2, 2.6.13 on one machine:

BIOS boot reports standard Com1 Com2 parameters.. Default..

Linux 2.6.13 boot; setserial /dev/ttyS0 and /dev/ttyS1 reports exact same parameters; normal.. Both UART 16550A.. The on board LSI chip seemingly AOK..

I see no mention of /dev/tts anywhere on my machine..

dmesg reports standard ttyS0 and ttyS1, normal.. This is the bundled kernel that Slackware calls test26.

If I hang an external modem on either port; normal..

Probably no help, just a thought..

Signature · 7 lines
    Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1   (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
author
#5 lore raw
In reply to Ray Olszewski

OK, I do not have anymore a /dev/ttyS0. Why, I have no idea. And that seems to be the reason that the modem does not respond.

Now I created the device node with mknod /dev/ttyS0 c 4 64, with permissions set to root:tty.

Then I get
setserial /dev/ttyS0 -a
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4

        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal skip_test auto_irq

and the modem responds to minicom, microcom and fax receive/send.

Quoted 3 lines · [email protected] said:
Quoted 1 line

Fedora4 does not run setserial neither does DSL.

How do you know? Did you grep for "setserial" in the appropriate directory (probably /etc/init.d)? If not, how did you check this?

That is exactly what I did, grep for setserial in the appropriate directories.

Yes with kernels 2.4.31, 2.6.14 I had a /dev/ttys0, however, not anymore with kernel 2.6.20. With kernel 2.17 modem responded to a setting of a symlink to /dev/tts/1.

This symlink I kept with kernel 2.6.20 and the trouble started.

Just now I resolved the issue. In /etc/udev/rules.d/modem.rules I changed the setting from NAME="/dev/tts/1" to NAME="ttyS0". Then running rc.udev and I have my
/dev/ttyS0 back.

ls -l /dev/modem
lrwxrwxrwx 1 root root 5 2006-07-19 14:26 /dev/modem -> ttyS0

Much appreciated your help.

Regards

Signature · 7 lines
Peter

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs