I hace an IBM 600 TP that has an ACP (Winmodem). I downloaded a driver for
it and my instructions were as follows:
./configure
make all
make install
insmod mwavedd (this loads mwavem.o)
setserial /dev/ttyS1 autoconfig
./mwavem
You might want to try the setserial command and see if the helps?
Mine works great and I did a small script to load it at start-up.
Good luck!
Michael
On Fri, 15 Jun 2001, you wrote:
> > I've downloaded what seems to be drivers for my Winmodem, kernel version
> 2.2.x and newer. I have 2.4 kernel. I executed the command listed in
> readme: unpacked it, created links to /dev/ttyS15 and /dev/modem . BTW,
> it's fun to do command without even understanding why and how they work.
> Well, that's for future. And, the last command I had to make was insmod
> pctel.o to activate the modem. As I had a more recent Kernel version, I
> used insmod -f pctel.o , to make Linux overlook the kernel differences.
> However, it filled screen with messages about unsolved symbol: pctel.o:
> unresolved symbol SOMETHING_HERE , and so some dozen lines. Why is this
> happening? Now I'm just one command away (hopefully) from activating my
> modem. Honestly, probably the best solution is to give this modem to a two
> year old, and buy a new one :D. Solver
----------------------------------------
Content-Type: text/html; name="Attachment: 1"
Content-Transfer-Encoding: quoted-printable
Content-Description:
----------------------------------------
