LinuxQuestions.org - [SOLVED] Zoom Modem Install in Slackware 14.1 32-bit

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Zoom Modem Install in Slackware 14.1 32-bit (https://www.linuxquestions.org/questions/slackware-14/zoom-modem-install-in-slackware-14-1-32-bit-4175503833/)

Zoom Modem Install in Slackware 14.1 32-bit

My friend has a Zoom dial up modem. I've done a clean install of Slackware 32-bit 14.1 (and all the patches) and can't get the drivers for it built with dgcmodem-1.13 (which worked with 14.0 and there is no update for it). Doing the installation

Code:

make install

make[1]: Entering directory `/usr/local/packages/src/zoom/dgcmodem-1.13/scripts'

install -m 700 dgcconfig dgcstop dgcmodconflicts dgcdcpd /usr/sbin

install -m 700 rcdgc /usr/lib/dgcmodem

make[1]: Leaving directory `/usr/local/packages/src/zoom/dgcmodem-1.13/scripts'

make[1]: Entering directory `/usr/local/packages/src/zoom/dgcmodem-1.13/modules'

rm -rf "/usr/lib/dgcmodem/config.mak" "/usr/lib/dgcmodem/modules/imported" "/usr/lib/dgcmodem/modules"

mkdir -m 755 -p /usr/lib/dgcmodem/modules

(cd .. && find config.mak modules/imported -depth -print | cpio -pdmu /usr/lib/dgcmodem)

13 blocks

find . \( -name COPYING -o -name '*.sh' -o -name '*.[ch]' -o -name '*.mak' -o -name '[Mm]akefile' \) -print | cpio -pdmu /usr/lib/dgcmodem/modules

197 blocks

find binaries -depth -print | cpio -pdmu /usr/lib/dgcmodem/modules

0 blocks

make[1]: Leaving directory `/usr/local/packages/src/zoom/dgcmodem-1.13/modules'

install -m 444 LICENSE /usr/lib/dgcmodem



To complete the installation and configuration of your modem,

please run "dgcconfig" (or "/usr/sbin/dgcconfig")



dgcconfig

Conexant DGC USB modem driver, version 1.13



If you need assistance or more information, please go to:

        http://www.linuxant.com/



When reporting a problem for the first time, please send

us the file generated by "dgcconfig --dumpdiag".



No pre-built modules for: Slackware-Slackware linux-3.10.17-smp i686



Trying to automatically build the driver modules...

(this requires a C compiler and proper kernel sources to be installed)



Where is the linux source build directory that matches your running kernel?

[/lib/modules/3.10.17-smp/build] 



WARNING: missing file /lib/modules/3.10.17-smp/build/include/linux/version.h

The cause of this is usually a missing or unconfigured

kernel source tree (and sometimes an incorrect directory or symbolic link).



First, ensure that the proper kernel source and compiler packages

from your distribution vendor and/or the community are installed.



The Linux kernel can then be reconfigured by running "make menuconfig"

under the kernel source directory (usually /usr/src/linux).



Verify that the proper options for your system are selected.



Then compile and install your new kernel (for more information about

this procedure, see the README file under the kernel source directory),

reboot the system using the new kernel, and re-run "dgcconfig".

As far as I know the kernel source is installed and the thing should have worked without recompiling the kernel (which takes about six hours on this box) and I don't want to do that unless absolutely necessary.

Has anybody gotten one of these things to work on 14.1?

Is there an alternative (other than, you know, having her get wireless)?

Anything?

Thanks.

I used to have one of those until I was finally able to get away from dial-up a year and a half +/- ago. Sorry I can't help with it this time and 14.1. It was actually a darn good modem when I was on dial-up.

Did she check /var/log/packages to see if the kernel source is for sure installed?

Yeah, first thing:

Code:

/var/log/packages/kernel-source-3.10.17_smp-noarch-3

Good thinking, though, thanks.

What kind of Zoom modem? ISA or PCi card? USB? Serial port conection?
Did you check if there exists a kernel module for this device?
Is the kernel module loaded/loading?
Did you check the kernel configuration to see if any module is selected?

You can recompile the kernel modules without recompiling the entire kernel. See the Slackware kernel source tree slackbuilds.

Is there a reason other than 14.1 is the latest and greatest that you can't stick with 14.0, since it works, until she can go the wireless route? 14.0 is still supported via security updates.

The Zoom modem is a USB device (and it does require additional software to work).

The box has a Conexant HSF 56K Data/Fax Modem in it and there two packages available, hcfpsimodem and hsfmodem, that may -- may -- work (haven't tried 'em yet, still trying to wade though the documentation produced by the scanModem utility provided by Linuxant (lots and lots of information).

I can't find any module that provides support for either the external Zoom USB device or the intern Data/Fax device.

@bassplayer69: on this peculiar box, a Dell Dimension E510, 14.0 worked but not too well (here a glitch, there a glitch, everywhere a glitch-glitch; nothing major, but annoyances). One problem has always been (since Slackware 10.x) the graphics card (a Radeon X300 SE ). 14.1 has better support for that card that 14.0 did plus additional faster, better, gooder all around -- this is the first time this dinosaur has come up running without having to screw around with a lot of things to get it to go.

She has two options: wireless (from Verizon and only Verizon in this area) or, maybe, DSL on the land line. Neither of those is real attractive from a cost point of view, but may wind up being the only option if I can't get this damned modem thing going (and, frankly, I've forgotten everything I never knew about dial up, it's kind of a struggle).

It's kind of a PITA. First time the thing has decent video (that doesn't go "negative" every now and again), it's at my house (with satellite) getting it set up, patched, yadda, yadda and it works without yammering at me about this, that and the other thing.

lswh reports

Code:

          *-communication UNCLAIMED

                description: Communication controller

                product: HSF 56k Data/Fax Modem

                vendor: Conexant Systems, Inc.

                physical id: 3

                bus info: pci@0000:03:03.0

                version: 00

                width: 32 bits

                clock: 33MHz

                capabilities: pm bus_master cap_list

                configuration: latency=64

                resources: memory:efbf0000-efbfffff ioport:ccb8(size=8)

That's what I have work with if I can't find something that will work with the Zoom.

Onward and upward!

Well, I finally noticed that I'm being stupid, really, really stupid.

Linuxant provides driver software for kernels 2.4 and 2.6, not for 3.10.

Duh.

So, no, there's no sense in recompiling anything having to do with the kernel, modules or otherwise and the search is on for something, somewhere that'll get this thing communicating.

Sigh.

Thanks to all for contributing.

It tuns out that I've been on a fool's errand. The kernel has drivers, the modem gets assigned to /dev/ttyACM0. Who knew.

I've had problems getting it to connect with KPPP, a little fiddling, a little twiddling and the problem appears to be kinda-sorta solved (at least as root).

Ran netconfig and set it for loopback (seem to remember a modem needs that), rebooted.

Logged in as root, set up KPPP. It connects and stays connected (most of the time anyway); this is being typed via the modem.

I'm wondering if I've missed something, like a group or something because there's no symbolic link to /dev/modem (which may or may not matter). I have it connected to /dev/ttyACM0.

Anybody remember any tricks or techniques for getting KPPP to be solid and dependable?

Unfortunately A year and a half and I've forgotten pretty much everything I used to know to use/get connected with dial-up and my exact same Zoom usb modem.

I gave it to someone who used to be a friend. The reason I won't go look at his system (which I set up for him to use linux and Slackware in particular and my old Zoom modem) is too long to detail, but let's just say he and I are nothing at all even closely resembling 'friends' anymore. I'd as much shoot him in the face as ask for the time of day from him.

I don't remember having to ever do anything with kppp as root though. And the ttyACM0 (or try usb/ttyACMO) looks right. I always manually configured the modem. Make sure you have the right phone number to dial out/up, also make sure the connection speed drop-down menu is at 115200...sometimes putting it higher will mess things up somehow and not connect well IIRR.

Can't remember much else at the moment, sorry.

Yeah, things started coming back (the main thing was I was beating a dead horse with the Linuxant driver software -- they're all 2.4 and 2.6 kernel -- uh, duh, this is a 3.10 kernel, stupid. Live and learn.

I set the thing up manually; PAP/CHAT, right phone number, /dev/ttyACM0, shut off call interrupt, log in and password. 'Round here we have kind of crappy phone lines (out in the country and all) so it might take two or three tries to get a good connection. I do set the speed to 57400(?) rather than the default because I remember having problems with the thing when it set to the default 115200 or so. Good connection, it works and it keeps working and I tied both the user accounts my friends use and all is well that ends.

Thanks for the thoughts.

Realize the thread is old, but if you have the details/notes of what you did, I'd appreciate it if you could spell it out.

I've gotten one of these things, mostly so I can receive or send the occasional fax when I have to, and I see that it is recognized by the kernel and that I have /dev/ttyACM0.

Quote:

Originally Posted by mostlyharmless (Post 5255641)

Actually, there isn't much to it -- you plug it in, it gets recognized and you set it up with KPPP.

You start KPPP and you're presented with a box that lets you connect to a telephone connection you've already set up with the Configure box -- generally, you'll just select the Modems tab in Configure, where you click New and add your modem (which should be at /dev/tty/ACM0) then back up through the menus to set an account (with the phone number). Not too difficult to figure out. If you happen to have call waiting on your phone line, you'll want to check in your directory for how to disable call waiting (and how to turn it back on when you're done with faxing). Use the accounts part for the different fax machines you'll be calling (or, heaven help you, dial-up IPs you may call, eh?).

Hope this helps some.

Thanks, got it working with efax built from SlackBuilds, just the fax...
No dialup for me.

There used to be another dialer in GNU/Linux, wvdial I think, that worked with just about any USB, PCI, AMR, or Serial modem as well. I'm not sure if Slackware still provides that package however.

wvdial and the required wvstreams are available at SlackBuilds.org if you're interested (I'm not familiar with it, though, so can't offer any opinion).

Hope this helps some.