ModemBlaster V.92 PCI to Linmodem?

It would seem at this point I'm nearly up a s**t creek without a paddle....

I have a Creative Labs Modemblaster V.92 internal PCI modem installed at /dev/ttys3 and linked to /dev/modem.

Attempts to query it apparently fall on deaf ears as all I get is "Modem is busy". The modem, however, works fine off COM4 in Windoze as would be expected.

Alas, the manual for the modem is AWOL from the box (missing at purchase... "tech support" has been worthless on this next point), so I do not know how to jumper it so that PnP is disabled. At that, isapnp is useless in my endeavor, and because I don't have the docs, I cannot seem to get the chipset information. I have found a modem listing on the linmodem knowledge database whose description matches closely to the modem I'm having trouble with, but without some way of getting the chipset information, I have no way of knowing if it really is a match to my modem. Oh, and "cat /proc/pci" wasn't real helpful either...

Anyone who can point me in a new / alternate direction to getting this stupid modem's information, or getting it working, will have my undying gratitude! I'd really like to free myself from Windoze for good and getting dial-up to work from Linux would be the last step (I'd really like this second hard drive free for something useful....)

SON OF A !!!!!!!!

Never mind..... I just now found the dire news... the stupid modem has no support yet under Linux what so ever (or, didn't 2 months ago)...

Still.. I'm going to try and drag some info from /proc/pci about the resources this modem is on. Anyone who has anymore info on this, please let me know... I don't really want to go get my old Lucent winmodem out of my other comp

[Edit]
No... ANOTHER update! I found the chipset info and matched it on the winmodems are not modems page... it just got added to the linmodem page as a (sort of) supported modem! Will keep looking...
[/edit]

All right, I think I finally figured it all out... anyone with a Creative Labs Modem Blaster v.92 PCI DI5633 chipset modem listen up:

1. Get the 2.4 kernel if you haven't already.
2. Gather your version number / architecture
3. Go here and get the appropriate driver off the HCF (controllerless) section.
4. Check the installation page for install information, I recommend the rpm method.

These instructions SHOULD, in theory, work for RH 7.x, SuSE 7.2, 7.3, 8.0, and Mandrake 8.x. I haven't been able to test to see if it works out for me personally yet... but it's 3:30 and I'm going to bed... so blah... if nothing else, it's a start!

Woohoo! I had to recompile a new kernel (had to go to 2.4.x anyway from 2.2.x, so not a big deal), hunt down generic drivers, fix the resolv.conf file, and update pppd... but I'm talkin' to you from Linux! Sheesh... I coulda saved myself 24 hours if I'd just been a little more careful about picking my modem....

Problem though: I can't connect via kppp because the stupid thing can't talk to my modem (common problem with this modem/driver setup). rp3 was working OK until I got pppd to work. Now it bombs out with gtk errors when I try to start a session (sorry, I don't have them immediately available). The only way I can GUI connect is if I run the rp3 "debug" session and leave it open or run shell scripts. What do you think, fight with rp3, or just go shell?