I'm trying to get a modem working on my 600e running debian testing. I
have 3 options, in descending order of preference (although at this
stage I'd be very happy to get any one of them going): mwave, external
serial, US robotics xj4336 pcmcia.
Here's what I've done so far with the mwave. I got mwavem-1.0.4.tar.gz
from http://oss.software.ibm.com/acpmodem/ and did configure, make, make
install without reading any docs. I only include this in case it could
bugger up my subsequent, informed efforts. I ran pppconfig and told it
to use /dev/modems/mwave. pon did nothing and plog gave this:
Jul 15 09:29:27 hallypolis pppd[4172]: pppd 2.4.1 started by matt,
uid 1000
Jul 15 09:29:27 hallypolis pppd[4172]: Failed to open
/dev/thinkpad/thinkpad: No such device
Jul 15 09:29:27 hallypolis pppd[4172]: Exit.
Interestingly that(failed to....such device)'s also what tpctl says when
I try to enable the serial port.
So read the mini-howto (http://oss.software.ibm.com/acpmodem/mwave.html)
and added --enable-mwavedd to configure. Output:
configure: error: *** You must specify the correct path to your linux
kernel source tree in order to build the driver module. If you do
not wish to build the driver module from this distribution, you must
specify --disable-mwavedd when you
run ./configure.
Back to the howto and realised I didn't have the kernel src so got it
with apt-get install kernel-source-2.4.18 Unpacked it and tryed again
with identical result. Next did configure
--with-linuxsrcdir=/usr/src/kernel-source-2.4.18/ this worked but I
don't know if it built the driver as well as the mwavem app. I also
tried using both the --enable and --with args (both ways) but got the
same src path error(above).
Assuming it worked I went insmod mwave mwave_3780i_irq=10
mwave_3780i_io=0x0130 mwave_uart_irq=3 mwave_uart_io=0x2f8 which is the
example in the howto for ttyS1. Output:
Using /lib/modules/2.4.18-bf2.4/kernel/drivers/char/mwave/mwave.o
/lib/modules/2.4.18-bf2.4/kernel/drivers/char/mwave/mwave.o:
init_module: Input/output error
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
I tried variations of insmod and modprobe with and without various args
but it all gave the same output(above). Reading Thomas Hoods page now it
seems I should have started by recompiling my kernel. I will give this a go.
Briefly the other options.
Serial: tpctl I mentioned already. I've also mucked with dosemu to use
ps2.exe but so far I've only got ps2 in the form of this thing which
puts itself on a floppy and haven't got dosemu to recognise /dev/fd0
pcmcia: the card locks my system solid at a certain point during boot or
whenever I stick it in later.
Any help would really be appreciated.
Thanks,
Matt.