This continues the thread "What is the device name for an internal 56K fax modem?". However the topic is now about using PuppyLinux to test for a modem inm the laptop.
Background
I have a Dell D630C laptop - s 64-bit machine running Linux Mint 18.1 with Cinnamon(sp?). It supposedly has a 56K modem ; there is a jack for it at the rear of the laptop. I can't get the modem to work.

So far, we're pretty sure that modem is by Conexant (Formerly Rockwell). The problem is that a proper driver for it may not be available for the current current kernel in Mint.

People seem keen to try PuppyLinux on the hardware because it seems to have a working modem driver, and that may give a hint as to what driver is needed for the Mint OS.

So my first question is this: Assuming we boot the PuppyLinux ISO from a Flash drive or CD, then what? How do we test for the modem existence and connection?

From Jefro in thread entitled "What is the device name for an internal 56K fax modem?"
Does this imply that I ought to be trying to install "slmodemd"?

From the last thread:
This modem test seems to need an add-on to wo0rk. How will that Add-on be brought into the Live CD OS to do the test?

I think we need to determine the chipset first maybe.
Since a lot of that old winmodem/linmodem stuff hasn't been used for a while many of us that did use it way way back when will have to scratch our heads trying to recall what we did.
I'd assume that if puppy did natively support it you could try AT command to it.

off topic
Due to the way LQ works, if you start a thread you should to edit the first post so that it make it look like you need help as in zero reply list.

LOL. Ok, tell me how to issue the AT commands...
And suggest the words I need to put into the first post. Even better, you can start a new thread and I'll participate. I'm not eager to lead when I'm clueless.

Hi, Lou.

There's one Puppy I would recommend you try for this little exercise. It's called Precise 571 Retro.....and has built-in support for a huge number of modems and fax devices.

You can find it here, at Ibiblio:-

http://distro.ibiblio.org/quirky/precise-5.7.1/

You can tell it must have quite a bit of extra stuff by the fact that the ISO file is over 40 MB larger than the standard 571.

Once you find out if your modem is recognised, you can do an

...in the terminal to discover what the device's hardware ID code is. Then you can find out what drivers are required for it.

Hope that helps.


Mike.

I agree that you should try running the scanmodem tool to identify the chipset. I think your still going to have to compile the drivers for Puppy.

I might of lead you astray. I was trying to relocate the source of what kernel version worked and found that someone got them to compile for a Pi which is ARM based using a 4 kernel. So it should be doable for Mint...

The driver creates a /dev/ttyshsf0 device (I believe). You can use minicom to connect to the device and send AT commands.

Yabut. How do I find out if the modem is recognized?

It will be listed in the lspci terminal readout. If it isn't, then it won't be. At least, that's how it works in Puppy.

Hardware id codes are generally listed as six pairs of two digits, each separated by a colon, thus:-

aa:bb:cc:dd:ee:ff

...and are unique to every piece of hardware that's ever been released; usually based on the specific chipsets, I believe. This will normally identify the chipset's manufacturer. I know the Linux kernel supports hundreds of thousands of device drivers OOTB, but newer versions have dropped support for stuff back beyond a certain cut-off point. That's why an older kernel is more likely to support modems than a newer one.

Once identified, you would need to find the driver source code, and compile the relevant kernel module (.ko) to work with Mint's kernel. Others will be better able to help with that particular task; compiling has never been my strong suit..!


Mike.

I knew it could be done for Mint. I just didn'twant to do it. Compiling is not useful. Either I get locked out of updates or have to recompile as updates take place.

I gave the lspci output in the first thread. Check it because I don't know what to look for. That unknown output from weeks ago. That's likely the scan modem output for Mint.

I'm frustrated that we have so much output and yet can't seem to conclude if we do or don't reconize the hardware. There is always some aspect of an audio device in the mix, did you notice? This is very disconcerting.

I don't like your chances here. Reading post #5 of your original thread, the relevant output confirms a Conexant device (with 14f1:2c06 chiset), hosted via the parent HDA Audio device. (It won't be reported by lspsci directly AFAIU.)

Referring to this Ubuntu Conexant Modem How To guide, I note that the 'hfsmodem' driver requires an appropriate 'alsa-driver-linuxant' package to be installed, and that is where you're likely to run into troubles. Your distro will be using a much later ALSA version, and I doubt that it will be possible to compile the necessary.

In short, if you must use a dialup modem/service, do yourself a favour and find a proper hardware modem. For example...
https://www.thinkpenguin.com/gnu-lin...usb-dial-modem

Ya, the audio device is a problem mentioned in many articles about these modems.
Your statement about the ALSA version is quite correct. I had already tried to install that package without success.
Thanks for the link to a hardware modem. Faxes are still used extensively here to confidential information and so hardware modem will be necessary.

About the ALSA kernel limits: My kernel is now 4.4.0.5-generic (or close), and yet the ALSA kernels are versions 2.4 and 2.6. Do these values make sense? Are we really that far along in kernel versions?

Did we prove what chip you have?

info

http://www.tldp.org/HOWTO/html_singl...m-HOWTO/#ss2.6