[ltp] 600e modem

[Thomas Hood]

On Tue, 2003-07-15 at 00:34, Matt Smith wrote:
> I ran pppconfig and told it 
> to use /dev/modems/mwave.

Make sure that this device node exists and that mwavem is set up
to use this device node.

> 	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

Strange.  Why are the pppd scripts calling tpctl?  

Anyway, you should either make sure that tpctl is properly installed
or else find the line where tpctl is called and disable it.

> 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).

You need to build a new kernel using make-kpkg in the kernel-package
package.  Before building, make sure that you have opted to build
the mwave device driver in the kernel configuration.

> 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.

Yes.

> Briefly the other options.
> 
> Serial: tpctl I mentioned already. I've also mucked with dosemu to use 
> ps2.exe

That won't work.  PS2.EXE needs to run on the real machine, not in an
emulator.

-- 
Thomas Hood <jdthood2@yahoo.co.uk>