Installed a USR5610B that is supposed to linux complient. According tothe documentation any kernel from 2.2x and up should recoginze the modem. However when I install the moden (even when reinstalling Suse) Yast does not recognize the modem I have also downloaded the linux drivers. and installed then as an rpm under Yaste

I am new to Linux so any help would be appreciated.

Thanks

Dani AI

Generated

This looks like a classic resource conflict rather than a missing protocol stack. ’s logs show the card enumerated as a serial device but pppd never gets AT responses. The PCI slot being given the same IRQ as the USB host controller explains that: the modem hardware appears to the kernel but never receives interrupts, so it will not answer commands. ’s BIOS advice (disable Plug‑and‑Play OS) is the right direction.

Three practical approaches, ordered from least to most intrusive:

  • Let the BIOS assign different resources (set “Plug‑and‑Play OS” to No or equivalent) or update the BIOS; this often fixes IRQ collisions.
  • Move the modem to another PCI slot (different slot -> different IRQ routing on many motherboards).
  • As a short test, free IRQ 5 by unloading USB host drivers (will disconnect USB devices). Example (use only if a PS/2 keyboard is available or remote access is possible):
    sudo modprobe -r usbserial
    sudo modprobe -r uhci_hcd ehci_hcd

    If the modem then responds, the IRQ conflict is confirmed; make the BIOS/slot change permanent rather than relying on module removal.

Verify device binding and test AT-level communication before retesting PPP:

  • Confirm the /dev/modem link actually points to the same tty the PCI device created (use a readlink-style check).
  • Use setserial to view tty properties and IRQ assignment.
  • Use a terminal program to send plain AT commands and watch for a response (minicom, screen, cu). Example checks:
    readlink -f /dev/modem
    setserial -g /dev/ttyS*
    minicom -D /dev/ttyS14 -b 115200

If freeing the IRQ and confirming the correct tty does not produce AT replies, the card may be a software (Win)modem requiring vendor firmware/drivers. At that point the PCI vendor/device ID (lspci -nn) should be checked against Linux driver support and the USR driver RPM revalidated for kernel compatibility. If no Linux driver exists, consider a different modem (one known to expose a true serial interface) or an external USB/serial modem.

Recommended Answers

All 4 Replies

The problem could be due to a number of things, including a resource (IRQ or I/O address conflict) or a driver issue.

1. If your BIOS allows, turn off the "Plug-N-Play OS" (or similar) option; this is known to cause problems with PCI hardware under non-Microsoft operating systems.

2. Open a terminal window, type the following commands, and post the results of each (remember that commands in Linux are case sensitive!):

- lspci

- less /proc/interrupts

- less /proc/ioports

- lsmod

- ls -l /dev/modem

(all of the " l " characters in the above commands are lowercase "L"s; some fonts make that hard to determine)

I upgraded to Suse 9.1. (Treated it as a new install.


When the systemboots I see ttyS14 with the correct IRQ (5) and settings (d000) and the 6550a uart chip.

After the system came up I enter the ln /dev/ttyS14 /dev/modem. However I cannot get the moden to work.


When I enter the command cat /dev/pic I get no output.

Any Suggestions.

Thanks

2. Open a terminal window, type the following commands, and post the results of each

I asked for the information returned by the commands I posted because that info would at least tell us whether or not you had any low-level conflicts. Although the modem shows an IRQ and I/O address at boot-up, that doesn't necessarilly mean that there isn't a conflict with another device.

Modems can sometimes be difficult to get running under Linux, here are some links which (hopefully) contain some useful suggestions and info:

http://www.justlinux.com/forum/search.php?action=showresults&searchid=1027483&sortby=lastpost&sortorder=descending

http://www.linuxquestions.org/questions/search.php?s=&action=showresults&searchid=2897985&sortby=lastpost&sortorder=descending

Both www.justlinux.com and www.linuxnewbie.org are excellent Linux-only tech support sites; I'm sure you'll get some help from the members of those sites if you register and post your question there.

I asked for the information returned by the commands I posted because that info would at least tell us whether or not you had any low-level conflicts. Although the modem shows an IRQ and I/O address at boot-up, that doesn't necessarilly mean that there isn't a conflict with another device.

Modems can sometimes be difficult to get running under Linux, here are some links which (hopefully) contain some useful suggestions and info:

http://www.justlinux.com/forum/search.php?action=showresults&searchid=1027483&sortby=lastpost&sortorder=descending

http://www.linuxquestions.org/questions/search.php?s=&action=showresults&searchid=2897985&sortby=lastpost&sortorder=descending

Both www.justlinux.com and www.linuxnewbie.org are excellent Linux-only tech support sites; I'm sure you'll get some help from the members of those sites if you register and post your question there.

SuSE 9.1 Pro & USR5610B Modem ( post #1)

I am new to Linux and hve loaded. SUSE 9.1 Pro. I have a USR5610B. I have read the HOW-TO-MODEM and searched the thread for answers about getting SUSE to recognized my modem.

Iam running a dual boot system withh Windows XP. The modem is recognized under XP.

When the system boots under SUSE, it recognizes the modem and displays the following info
ttyS0 3f8 4
ttyS1 2f8 3
ttyS14 0xd000 5 uart 6550

I enter the command ln - s /dev/ttyS14 /dev/modem, b ut it still does not work and configured the dialup connection but get no response from the modem


I have extracted the following information from various commands


Any help would be greatly appreciated.

Thanks in advanced

Dickbeamish

I have extracted the following information from various commands

Kinternet log

SuSE Meta pppd (smpppd-ifcfg), Version 1.16 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin loaded.
pppd[0]: --> WvDial: Internet dialer version 1.54.0
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: --> Sending: ATQ0
pppd[0]: --> Re-Sending: ATZ
pppd[0]: --> Modem not responding.
pppd[0]: Connect script failed


lspci -vv
0000:00:0a.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610 (rev 0
1) (prog-if 02 [16550])
Subsystem: 5610 56K FaxModem: Unknown device 00d3
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at d000
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot
+,D3cold+)


lspci -v

0000:00:0a.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610 (rev 01) (prog-if 02 [1655
0])
Subsystem: 5610 56K FaxModem: Unknown device 00d3
Flags: medium devsel, IRQ 5
I/O ports at d000
Capabilities: [dc] Power Management version inux:/ # cd /proc

linux:/proc # cat ioports
0000-001f : dma1
0020-0021 : pic1
0040-005f : timer
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
02f8-02ff : serial
0376-0376 : ide1
0378-037a : parport0
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : seria0cf8-0cff : PCI conf1
c000-cfff : PCI Bus #01
c000-c0ff : 0000:01:00.0
d000-d007 : 0000:00:0a.0
d000-d007 : serial
d400-d4ff : 0000:00:0d.0
d800-d81f : 0000:00:10.0
d800-d81f : uhci_hcd
dc00-dc1f : 0000:00:10.1
dc00-dc1f : uhci_hcd
e000-e01f : 0000:00:10.2
e000-e01f : uhci_hcd
e400-e40f : 0000:00:11.1
e400-e407 : ide0
e408-e40f : ide1
e800-e8ff : 0000:00:11.5
e800-e8ff : VIA8233
ec00-ecff : 0000:00:12.0
ec00-ecff : via-rhincat interrupts

linux:/proc # cat interrupts
CPU0
0: 812464 XT-PIC timer
1: 721 XT-PIC i8042
2: 0 XT-PIC cascade
5: 100000 XT-PIC uhci_hcd
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi
10: 0 XT-PIC uhci_hcd, VIA8233
11: 20 XT-PIC aic7xxx, uhci_hcd, ehci_hcd, eth0
12: 51044 XT-PIC i8042
14: 13437 XT-PIC ide0
15: 12215 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0

MIS: linux:/proc # cd /dev
linux:/dev # ls -l modem
lrwxrwxrwx 1 root root 11 2004-11-14 05:57 modem -> /dev/ttyS1inux:/dev # cd /

linux:/ # lsmod
Module Size Used by
nls_iso8859_1 4224 0
nls_cp437 5888 0
vfat 14080 0
fat 43328 1 vfat
ppp_generic 28692 0
slhc 7424 1 ppp_generic
usbserial 28912 0
parport_pc 35264 1
lp 10916 0
parport 37704 2 parport_pc,lp
edd 9240 0
joydev 10176 0
st 38940 0
sr_mod 15652 0
ide_cd 36484 0
cdrom 36508 2 sr_mod,ide_cd
nvram 8328 0
snd_seq_oss 30976 0
snd_seq_midi_event 7680 1 snd_seq_oss
snd_seq 54672 5 snd_seq_oss,snd_seq_midi_event
ipv6 244100 13
snd_pcm_oss 56868 0
speedstep_lib 3712 0
snd_mixer_oss 18688 1 snd_pcm_oss
freq_table 4612 0
thermal 12424 0
processor 16040 1 thermal
fan 3972 0
button 6032 0
battery 8580 0
ac 4868 0
snd_via82xx 24224 6
snd_pcm 96776 4 snd_pcm_oss,snd_via82xx
snd_timer 25476 2 snd_seq,snd_pcm
snd_ac97_codec 60676 1 snd_via82xsnd_page_alloc 11012 2 snd_via82xx,snd_pcm
gameport 4736 1 snd_via82xx
snd_mpu401_uart 7808 1 snd_via82xx
snd_rawmidi 24992 1 snd_mpu401_uart
snd_seq_device 8328 3 snd_seq_oss,snd_seq,snd_rawmidi
snd 59524 23 snd_seq_oss,snd_seq_midi_event,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_pcm,snd_timer,snd_a
c97_codec,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 8800 1 snd
via_rhine 19720 0
mii 5248 1 via_rhine
ehci_hcd 27140 0
via_ircc 20240 0
irda 120124 1 via_ircc
uhci_hcd 29584 0
usbcore 96988 5 usbserial,ehci_hcd,uhci_hcd
via_agp 7424 1
agpgart 28712 1 via_agp
evdev 9600 0
subfs 7296 3
nls_utf8 2176 1
ntfs 86092 1
dm_mod 50044 0
reiserfs 233808 1
aic7xxx 177716 0
sd_mod 19840 0
scsi_mod 107980 4 st,sr_mod,aic7xxx,sd_mod
linux:/ #

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.