Tying to install a PCI Modem

New to Debian (Or Linux in general)? Ask your questions here!

Tying to install a PCI Modem

Postby a11an » 2021-01-02 20:56

I'm very new to Linux and this might be a very silly question. I hope someone can help as I have been looking at this all day and i'm getting nowhere!

I am migrating a pc that I use to control my home automation tasks from Windows XP running Housebot to the latest version of Debian and openHab. It's mostly working except the modem that I use for caller Id.

The modem is a PCI Zoom 3025C that I believe its known as a winmodem the PCI ID is 10B4 which is listed on the page http://www.linuxant.com/drivers/hcf/ but the installs are for very old 32bit builds.

Would you know if there is any chance I can get this working? The downloads page (http://www.linuxant.com/drivers/hcf/full/downloads.php) mentions the tar package with source can be used to rebuild the kernal, but I'm not sure how to do this, or if it's even possible.

I hope someone can offer some advice. Thanks.
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby arzgi » 2021-01-03 15:21

Welcome!

http://www.zoomtel.com/techsupport/dial_up/3025c.shtml
Really seems a winmodem. I years ago used linxuant driver for a different modem. Even linuxant has ceased support
https://www.linuxant.com/drivers/

You might get that working, but maybe try a different method for communication, or if you could find a real modem (vs. winmodem), i suppose it would not cost much.
arzgi
 
Posts: 701
Joined: 2008-02-21 17:03
Location: Finland

Re: Tying to install a PCI Modem

Postby arochester » 2021-01-03 17:23

if you could find a real modem


All external modems will work.
arochester
 
Posts: 1826
Joined: 2010-12-07 19:55

Re: Tying to install a PCI Modem

Postby p.H » 2021-01-03 20:32

Even all USB modems ?
p.H
 
Posts: 1620
Joined: 2017-09-17 07:12

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-03 21:25

Thanks for the replies, I guess this is a bit of a lost cause. I really wanted to get this to work as it supports caller id, a lot of them don't.
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby CwF » 2021-01-03 22:47

I have a few crates of modems maybe, some serial zoom speakerphone 56k...not sure.

What kind do you need?
CwF
 
Posts: 881
Joined: 2018-06-20 15:16

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-04 14:38

CwF wrote:...What kind do you need?


Thanks for this, but I picked up a couple of Smart Link modems on eBay last night. Hopefully, they will do the job, as there is a page on debian wiki here https://wiki.debian.org/slmodem
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby p.H » 2021-01-07 18:47

Does this work with a 64-bit kernel ? The sl-modem-dkms package contains a 32-bit binary object file. Is it possible to include a 32-bit object file in a 64-bit module ?
p.H
 
Posts: 1620
Joined: 2017-09-17 07:12

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-09 19:09

p.H wrote:Does this work with a 64-bit kernel ?


I thought I'd be ok, as the page mentions "...available for the x86 and x86-64 architectures (Debian i386 and AMD64 ports respectively)"

The card arrived, but, I'm having problems, I really don't know what I'm doing. Would anyone have any advice?

Plugged the card in and run lspci -vv I get this

Code: Select all
04:01.0 Modem: Philips Semiconductors SmartPCI56(UCB1500) 56K Modem (rev 01) (prog-if 00 [Generic])
        Subsystem: CIS Technology Inc SmartPCI56(UCB1500) 56K Modem
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort <MAbort- >SERR- <PERR- INTx-
        Latency: 64
        Interrupt: pin A routed to IRQ 16
        Region 0: I/O ports at ec00 [size=16]
        Capabilities: [80] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: serial


Running dmesg | grep tty retuns no extra com ports so I guess I need to install something. Followed the instructions on https://wiki.debian.org/slmodem.

First I added the following line to the sources.list (changed the version from Wheezy to Buster)
Code: Select all
deb http://httpredir.debian.org/debian/ buster main contrib non-free


Once this was done I ran aptitude update && aptitude install sl-modem-daemon but this did not work as aptitude did not existing so I installed that with apt-get and now when I run it I get the following error.

Code: Select all
[16:52:00] root@house:~# aptitude update && aptitude install sl-modem-daemon
Hit http://httpredir.debian.org/debian buster InRelease
Hit http://deb.debian.org/debian buster InRelease
Hit http://deb.debian.org/debian buster-updates InRelease
Hit http://security.debian.org/debian-security buster/updates InRelease
Ign http://repos.azulsystems.com/debian stable InRelease
Hit http://repos.azulsystems.com/debian stable Release
Hit https://deb.nodesource.com/node_12.x buster InRelease
Ign https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Get: 1 https://dl.bintray.com/openhab/apt-repo2 stable Release [6,051 B]
Hit https://repos.azul.com/zulu/deb stable InRelease
Fetched 6,051 B in 4s (1,633 B/s)
Couldn't find any package matching "sl-modem-daemon", but there are 1 packages which contain "sl-modem-daemon" in their description:  sl-modem-dkms
Unable to apply some actions, aborting


Now i'm stuck, any ideas on what to do next? or is it time to give up and try and get a pci hardware modem, although I believe they are hard to find, maybe I should just get a USB one, I was just hoping to not having another device hanging out the back of the computer.

Hope someone has some advice. Thanks.
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby p.H » 2021-01-09 21:10

a11an wrote:Kernel driver in use: serial

Interesting. What does the following command show ?
Code: Select all
dmesg | grep -i serial -C2


a11an wrote: aptitude did not existing so I installed that with apt-get

You could use apt-get or apt instead of aptitude.

a11an wrote:Couldn't find any package matching "sl-modem-daemon", but there are 1 packages which contain "sl-modem-daemon" in their description: sl-modem-dkms

As explained in the wiki, this package exists only in the i386 architecture. If the system architecture is amd64, did you add the i386 architecture with
Code: Select all
dpkg --add-architecture i386

before updating the package list ?
p.H
 
Posts: 1620
Joined: 2017-09-17 07:12

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-10 14:58

Thanks for the reply.

p.H wrote:Interesting. What does the following command show ?
CODE: SELECT ALL
dmesg | grep -i serial -C2


This returns the following

?[ 3.328542] serial 0000:04:01.0: Couldn't register serial port ec00, irq 16, type 0, error -28
Code: Select all
[15:27:41] root@house:~# dmesg | grep -i serial -C2
[    3.244004] intel_idle: v0.4.1 model 0x1C
[    3.244371] intel_idle: lapic_timer_reliable_states 0x2
[    3.245165] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    3.265710] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    3.286455] 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[    3.307103] 00:05: ttyS2 at I/O 0x4e0 (irq = 4, base_baud = 115200) is a 16550A
[    3.327730] 00:06: ttyS3 at I/O 0x4e8 (irq = 3, base_baud = 115200) is a 16550A
[    3.328542] serial 0000:04:01.0: Couldn't register serial port ec00, irq 16, type 0, error -28
[    3.329006] Linux agpgart interface v0.103
[    3.329313] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
--
[    4.218875] ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[    4.219162] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    4.219169] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.219174] usb usb1: Product: EHCI Host Controller
[    4.219179] usb usb1: Manufacturer: Linux 4.19.0-13-amd64 ehci_hcd
[    4.219184] usb usb1: SerialNumber: 0000:00:1a.7
[    4.220001] hub 1-0:1.0: USB hub found
[    4.220046] hub 1-0:1.0: 4 ports detected
--
[    4.221751] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000c880
[    4.222075] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    4.222082] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.222087] usb usb2: Product: UHCI Host Controller
[    4.222092] usb usb2: Manufacturer: Linux 4.19.0-13-amd64 uhci_hcd
[    4.222097] usb usb2: SerialNumber: 0000:00:1a.0
[    4.222689] hub 2-0:1.0: USB hub found
[    4.222749] hub 2-0:1.0: 2 ports detected
--
[    4.239904] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[    4.240229] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    4.240238] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.240244] usb usb3: Product: EHCI Host Controller
[    4.240250] usb usb3: Manufacturer: Linux 4.19.0-13-amd64 ehci_hcd
[    4.240255] usb usb3: SerialNumber: 0000:00:1d.7
[    4.240845] hub 3-0:1.0: USB hub found
[    4.240891] hub 3-0:1.0: 6 ports detected
--
[    4.241970] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000c800
[    4.242321] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    4.242329] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.242334] usb usb4: Product: UHCI Host Controller
[    4.242340] usb usb4: Manufacturer: Linux 4.19.0-13-amd64 uhci_hcd
[    4.242344] usb usb4: SerialNumber: 0000:00:1a.1
[    4.242962] hub 4-0:1.0: USB hub found
[    4.243009] hub 4-0:1.0: 2 ports detected
--
[    4.244407] scsi host1: ata_piix
[    4.244411] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    4.244418] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.244424] usb usb5: Product: UHCI Host Controller
[    4.244430] usb usb5: Manufacturer: Linux 4.19.0-13-amd64 uhci_hcd
[    4.244436] r8169 0000:02:00.0 enp2s0: renamed from eth0
[    4.244440] usb usb5: SerialNumber: 0000:00:1d.0
[    4.244687] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[    4.244694] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
--
[    4.246129] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c400
[    4.246359] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    4.246366] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.246371] usb usb6: Product: UHCI Host Controller
[    4.246376] usb usb6: Manufacturer: Linux 4.19.0-13-amd64 uhci_hcd
[    4.246380] usb usb6: SerialNumber: 0000:00:1d.1
[    4.247022] hub 6-0:1.0: USB hub found
[    4.247062] hub 6-0:1.0: 2 ports detected
--
[    4.248136] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c080
[    4.248405] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[    4.248413] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.248418] usb usb7: Product: UHCI Host Controller
[    4.248424] usb usb7: Manufacturer: Linux 4.19.0-13-amd64 uhci_hcd
[    4.248429] usb usb7: SerialNumber: 0000:00:1d.2
[    4.249045] hub 7-0:1.0: USB hub found
[    4.249088] hub 7-0:1.0: 2 ports detected
--
[    4.759860] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[    4.918190] usb 5-2: New USB device found, idVendor=413c, idProduct=2005, bcdDevice= 1.05
[    4.918196] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.918200] usb 5-2: Product: DELL USB Keyboard
[    4.918204] usb 5-2: Manufacturer: DELL
--
[    5.032300] hid-generic 0003:413C:2005.0001: input,hidraw0: USB HID v1.10 Keyboard [DELL DELL USB Keyboard] on usb-0000:00:1d.0-2/input0
[    5.149903] usb 2-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
[    5.149910] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.149914] usb 2-1: Product: USB-Serial Controller
[    5.149917] usb 2-1: Manufacturer: Prolific Technology Inc.
[    5.191917] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
--
[    5.591856] usb 4-2: new low-speed USB device number 2 using uhci_hcd
[    5.757893] usb 6-1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[    5.757899] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.757902] usb 6-1: Product: RFXtrx433
[    5.757906] usb 6-1: Manufacturer: RFXCOM
[    5.757909] usb 6-1: SerialNumber: AEVD63JI
[    5.759893] ata4.01: failed to resume link (SControl 0)
[    5.770608] ata4.00: SATA link down (SStatus 0 SControl 310)
--
[    5.788309] sd 2:0:0:0: [sda] Attached SCSI disk
[    5.795929] usb 4-2: New USB device found, idVendor=0403, idProduct=c630, bcdDevice= 1.01
[    5.795935] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.795939] usb 4-2: Product: LCD2USB
[    5.795943] usb 4-2: Manufacturer: Lcdmod Kit
--
[    8.083544] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x0860)
[    8.084061] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    8.085208] usbcore: registered new interface driver usbserial_generic
[    8.085261] usbserial: USB Serial support registered for generic
[    8.141732] usbcore: registered new interface driver pl2303
[    8.141792] usbserial: USB Serial support registered for pl2303
[    8.141868] pl2303 2-1:1.0: pl2303 converter detected
[    8.154282] usb 2-1: pl2303 converter now attached to ttyUSB0
[    8.173914] usbcore: registered new interface driver ftdi_sio
[    8.173979] usbserial: USB Serial support registered for FTDI USB Serial Device
[    8.174290] ftdi_sio 6-1:1.0: FTDI USB Serial Device converter detected
[    8.174435] usb 6-1: Detected FT232RL
[    8.175188] input: PC Speaker as /devices/platform/pcspkr/input/input6
[    8.178652] usb 6-1: FTDI USB Serial Device converter now attached to ttyUSB1
[    8.201446] sd 2:0:0:0: Attached scsi generic sg0 type 0
[    8.210524] intel_powerclamp: No package C-state available



Thanks for the tip about using apt-get instead of aptitude. It's all very new to me.

a11an wrote:As explained in the wiki, this package exists only in the i386 architecture. If the system architecture is amd64, did you add the i386 architecture with
CODE: SELECT ALL
dpkg --add-architecture i386

before updating the package list ?


I have now entered the following commands, but I don't get a ttySL0 port and get the following error when restarting the sl-modem-deamon

dpkg --add-architecture i386 && aptitude update
aptitude install sl-modem-daemon:i386
aptitude install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,') sl-modem-dkms
service sl-modem-daemon restart

Code: Select all
Job for sl-modem-daemon.service failed because the control process exited with error code.
See "systemctl status sl-modem-daemon.service" and "journalctl -xe" for details.


systemctl status sl-modem-daemon.service

Code: Select all
● sl-modem-daemon.service - LSB: Setup the SmartLink modem daemon
   Loaded: loaded (/etc/init.d/sl-modem-daemon; generated)
   Active: failed (Result: exit-code) since Sun 2021-01-10 15:36:47 GMT; 2min 15s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5526 ExecStart=/etc/init.d/sl-modem-daemon start (code=exited, status=1/FAILURE)

Jan 10 15:36:36 house systemd[1]: Starting LSB: Setup the SmartLink modem daemon...
Jan 10 15:36:47 house sl-modem-daemon[5526]: Only access through ALSA is available on amd64 but slamr driver was chosen!
Jan 10 15:36:47 house sl-modem-daemon[5526]: Make sure that an ALSA driver for your chipset is available and is loaded
Jan 10 15:36:47 house sl-modem-daemon[5526]: and that access to SmartLink modem components is supported by it.
Jan 10 15:36:47 house systemd[1]: sl-modem-daemon.service: Control process exited, code=exited, status=1/FAILURE
Jan 10 15:36:47 house systemd[1]: sl-modem-daemon.service: Failed with result 'exit-code'.
Jan 10 15:36:47 house systemd[1]: Failed to start LSB: Setup the SmartLink modem daemon.


Thanks again for the help, do you think it's time to give up on a internal pci modem and get something like this? I only need it for caller id. https://www.ebay.co.uk/itm/USB-56K-Exte ... 0005.m1851
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby p.H » 2021-01-10 15:20

Was the slamr module properly built, installed and loaded ?
Code: Select all
modinfo slamr
modprobe -v slamr
lsmod | grep slamr
dmesg | egrep "slamr|0000:04:01"
p.H
 
Posts: 1620
Joined: 2017-09-17 07:12

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-10 21:51

a11an wrote:Was the slamr module properly built, installed and loaded ?


Don't look like it, typing modinfo slamr returns
Code: Select all
modinfo: ERROR: Module slamr not found.


modprobe -v slamr returns
Code: Select all
install /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='slamr'
modprobe: ERROR: could not insert 'slamr': Unknown symbol in module, or unknown parameter (see dmesg)


lsmod | grep slamr returns nothing

and dmesg | egrep "slamr|0000:04:01" returns
Code: Select all
[    0.752352] pci 0000:04:01.0: [1131:3400] type 00 class 0x070300
[    0.752374] pci 0000:04:01.0: reg 0x10: [io  0xec00-0xec0f]
[    0.752463] pci 0000:04:01.0: PME# supported from D0 D3hot D3cold
[    3.328542] serial 0000:04:01.0: Couldn't register serial port ec00, irq 16, type 0, error -28


I had wondered if entering buster instead of wheezy in the /etc/apt/sources.list might be an issue as that is different from the instructions, so I changed it to wheezy and ran the commands again, but still nothing :(
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Re: Tying to install a PCI Modem

Postby p.H » 2021-01-11 08:39

a11an wrote:modprobe -v slamr returns

Looks like there is an "install" directive for slamr in some /{etc,lib}/modprobe.d/* file.
IIUC, sl-modem-dkms should build slamr and slusb modules. Is any of them present ?
Code: Select all
modinfo slamr
modinfo slusb


a11an wrote:I changed it to wheezy

Wheezy is severely obsolete. Did you try on a 32-bit install ?
p.H
 
Posts: 1620
Joined: 2017-09-17 07:12

Re: Tying to install a PCI Modem

Postby a11an » 2021-01-11 16:09

Thanks for persevering with me :?

p.H wrote:...build slamr and slusb modules. Is any of them present ?

Yes, it looks like slamr is missing, and I think this is the one I need, as my modem is listed on the slamr part of the website. Running modinfo slamr returns
Code: Select all
modinfo: ERROR: Module slamr not found.


modinfo slusb returns
Code: Select all
filename:       /lib/modules/4.19.0-13-amd64/updates/dkms/slusb.ko
alias:          char-major-243-*
license:        Dual BSD/GPL
description:    ST7554 USB Smart Link Soft Modem driver.
author:         Smart Link Ltd.
alias:          usb:v0483p7554d*dc*dsc*dp*ic*isc*ip*in*
depends:        usbcore
retpoline:      Y
name:           slusb
vermagic:       4.19.0-13-amd64 SMP mod_unload modversions
parm:           debug:Debug level: 0-3 (default=0) (int)


a11an wrote:Wheezy is severely obsolete. Did you try on a 32-bit install ?

Not sure what I'm doing, but am on latest 64bit version on Debian, which I understand is buster. I just thought that wheezy might be required in the sources.list as that is what is on the slmodem website. I have updated it back to buster and rerun all the install commands but no change.
a11an
 
Posts: 8
Joined: 2021-01-02 20:43

Next

Return to Beginners Questions

Who is online

Users browsing this forum: sgage and 12 guests

fashionable