I am hunting for a driver for my Agere PCI modem, and the site I keep coming up with tells me that SuSE included drivers on the CD. I have hunted on the CD and not found any. Does anyone know where you can find Agere drivers for SuSE 10?

What site do you keep coming up with?
Have you tried Linmodems.org, winmodems.org, or linuxant.com?

That's a Lucent chipset I believe in that; is it a HSF or HCF modem? If you get nowhere, please post the output of 'lspci' if it shows anything for the modem, and also the exact make & model number(s) of the device.

The only driver on the Suse cd is smart link I think and maybe another. I depends on the chipset of the Agere modem if you can get it to work. I have never found a driver to work for the ones I have tried (free). I have had luck with smart link modems if you want to run an internal inexpensive one. I understand that linmodems will sell you a driver for the Agere modem for about 20.00. That might be the route to go if you don't want to replace your modem

I kept coming up with http://www.physcip.uni-stuttgart.de/heby/ltmodem/, though after a few more tries after posting this, I may be starting to get somewhere. I was finally able to chase Linmodems.org down, and have since learned I have an SV2PP chipset. The Scantool tells me this is not supported (though it's an old version, updating...). Groups like Driverguide, who I use mostly, has only Windows drivers. XCF and XSF are Conexant chipsets (which have proven super agravating for me, and unreliable), and Agere is from Lucent. I got this Agere modem just for my Linux box too!

Also, what I keep getting is that the SV22PP chipsets have no prospects of being supported for Linux. :sad: Someone has to have written drivers for this thing!

Mod: After updating my Scantool, it led me to a drivers on linmodems which is currently in alpha. I'll try it (if SuSE can unzip a BZ-2), and see what happens. It's times like these when I thank God for scripts.

I've installed the drivers with no obvious errors, but I still cannot tell whether it worked or not. I had to go "make module" then "make install" to do the full installation (after installing my kernel headers). It tells that I should use /dev/modem to access the modem, but that link does not exist. Usually, I've seen it as a simlink to another device. What do these modems often appear as in the /dev listing once the drivers are installed? The only thing I've found in dmesg is something about /dev/ttyS0, but I think that may be my existing COM port. How would I open a serial terminal to query it with AT commands? Also, how would I query it via the /dev entry?

Here's my output:

Have you yet created the /dev/modem symlink? If not, here's how:

move into the /dev directory. I'm not sure what your device node is called, but for example, if it is /dev/ttys0, then to make the /dev/modem/ symlink, do the following (in a root terminal):
And presto, there it is. (It *may* not stay over reboot, but it should. If not, let us know. Easy to fix.

If you have KPPP or GnomePPP or something like that (any ppp GUI) they will generally have a little built-in terminal you can use, provided you have correctly installed the driver, linked the device node, and identified which device it is (ttys0, tty???, etc..)

How's it going so far anyways? Any luck? I am going to very soon be installing Linux on a laptop which has one of these miserable modems in it, so I am curious how it works for you, PLUS I found some links to more drivers today for the Lucent/Agere modems for 2.4 and 2.4 kernels, so If your current efforts are not working, mmaybe there's something I found that will help.

Now, to query the thing, the easiest way is using a front-end to wvdial, like gnomeppp or something like that. I use KDE, so I typically use KPPP.
To do a very basic query, like to see if the modem is alive, in a root terminal, try:
and see if you get a reply.

I had exactly the same problem! After many hours, visiting all the web sites like LinModem and a couple of reinstalls without getting anywhere I finally found the solution.

I bought an external modem off ebay for less than the cost of posting it and was up and running in the time it took to configure it in YAST.

I should have heeded the advise of a very wise man who told me: If at first you don't succeed, give up!

Thanks. That "echo" command is actually what I'm needing--a way to query a /dev entry and ask "what are you?". I'll bet that if it responds to something like "+++ATI7" or whatever, I can bet that it's a modem.

So far, it isn't any of my seven ttyS ports. What else can an internal winmodem typically be? I think if I can find it, we may be in business.

Hard to say. It can be any variety of strange /dev/???? devices. Is that a plugin modem or an onboard one? It might be a ttyM-something. Hafta experiment

I'm willing to learn something new but I've only seen pci internal Agere modems

Internal, yes, but I wonder if it was an onboard, like I have in a laptop here, or a PCI-slot-card design, incase it may have any bearing on how it is identified. Our laptop's onboard one comes up as ttyACM0 or some such thing with the driver I plan to use. I wouldn't have guessed that it would have been in 'that' particular group of /dev devices, but rather something more 'normal' like ttys#.

PCI slot is the only ones I have come across, if you can find an easy way to make them work please let everyone know. I've put 4 of them in the throw away bin.

Agreed, they're a pain in the a$$, as with most PCI modems of either type. Many *can* be got to work though, but it sure takes patience and persistence. Soon I will be (er.. hope to be.) getting the laptop one working, that's the onboard one. If it does work, I'll tell what was involved for sure.
I have 3 or 4 PCI plug-in modems here, and have only gotten one of them to work, but: my main connection is by LAN, and if I decide I want to switch to the modem (which works just fine) I have to jump through hoops to get the computer to recognize that it should now be using ppp instead of eth0. I still haven't figured an easy way about that. But the modem itself works great; it's an Intel 536ep 56k PCI-card.

This is your average, everyday PCI modem that goes in the poker-card slots in your computer. I think I have a driver, but I'm not a Linux expert and need to know what I can poke to get this thing to say "Hey! Quit it!". I think once I can just query the silicon, I can then get this box on the 'net. It may just be in issue of hide and seek right now.