[ltp] thinkpad t20 modem

Sun, 25 May 2003 18:59:53 -0700

Sorry If I was confusing.  The modem works fine on my T20.

I was wondering why the message I quoted had to use the -f option to insmod.  It should not be needed unless your system has some strange behavior.

michael 
On Sun, 25 May 2003 18:51:14 -0700
James Mckenzie <jjmckenzie51@earthlink.net> wrote:

> Micheal:
> 
> Look at the output from dmesg for the lines associated with the lt_modem 
> driver.  They should look like the following:
> 
> Loading Lucent Modem Controller driver version 8.26
> Detected Parameters Irq=11 BaseAddress=0x1800 ComAddress=0x1c00
> Lucent Modem Interface driver version 8.26 (2002-11-04) with SHARE_IRQ 
> enabled
> ttyLT00 at 0x1800 (irq = 11) is a Lucent Modem
> 
> You should be able to 'cat' /dev/ttyLT0.  
> 
> Also did you check for the link between /dev/modem and /dev/ttyLT0?
> 
> If it exists you should be able to start up kppp and run the terminal 
> program and check the output of the atz and ati series of commands.
> 
> James McKenzie
> 
> Michael Reilly wrote:
> 
> >I installed the latest lt drivers built from source code on my T20 running slackware 9.0 (2.4.20 kernel).  The  build went fine and the kernel modules load file without the -f - just the usual "tainted" modules message.
> >
> >Do the module utilities on RH not allow loading of "tainted" modules?  If so I'd recommend that you build and use the standard module utilities which do not have this problem.
> >
> >There was no problem on slackware 8.1 (2.4.18 kernel) either.
> >
> >BTW - I did not have to use any extra parameters in my modules.conf file.
> >Mine looks like your file except for the devfs line which I commented out since I do not use devfs.
> >
> >michael
> >
> >On Sun, 25 May 2003 15:59:00 -0700
> >James Mckenzie <jjmckenzie51@earthlink.net> wrote:
> >
> >  
> >
> >>Matt:
> >>
> >>First, my apologies, I have two machines I run Linux on, an A22p and a 
> >>600E.  The 600E uses the mwave modem driver and requires settings in 
> >>order to operate properly.  However, I built my own lt_modem drivers 
> >>because I am not running a standard linux install and have upgraded the 
> >>kernel several times.  
> >>
> >>Let me look at the dmesg from where the lt_modem.o driver file loads. 
> >> Did you get a rpm file or did you download and then build the drivers? 
> >> If you built the drivers, make sure that they are in the 
> >>/lib/modules/<kernel #>/ltmodem/ directory.  For example if your kernel 
> >>is 2.4.18-24.8.0 this would appear as 
> >>/lib/modules/2.4.18-14.8.0/ltmodem.  If you upgrade your kernel, you 
> >>will have to either download a new .rpm file or build new drivers.  A 
> >> .rpm file should load the driver files into the correct directory.
> >>
> >>I meant to say that I had to force the load of the lt_modem.o driver 
> >>with the following line:
> >>
> >>insmod -f lt_modem.o
> >>
> >>This module is not GPL, and would not load under RH 7.x and RH 8.0 
> >>without the -f (force) option.  On some systems, you might have to 
> >>specify where the modem is located, by specifying its location.  See the 
> >>modules.conf 'chunk' below on the format for this information.
> >>
> >>James Mckenzie
> >>
> >>The following is from my modules.conf:
> >>
> >># lt_drivers: autoloading and insertion parameter usage
> >>alias char-major-62 lt_serial
> >>alias /dev/tts/LT0 lt_serial
> >>alias /dev/modem lt_serial
> >># The next two lines are syntax examples, only Rarely Needed, to 
> >>automate parameter usage during lt_drivers insertion. See documentation 
> >>for details.
> >># options lt_modem vendor_id=0x115d device_id=0x0420
> >># options lt_modem Forced=3,0x130,0x2f8,0
> >># section for lt_drivers ends
> >>
> >>Also, if /dev/modem exists before you install the lt_modem drivers, you 
> >>WILL have to delete it.  Also, if you insert and remove a PC Card modem, 
> >>you will lose the link to the lt_modem driver and have to reestablish it.
> >>
> >>matt zagrabelny wrote:
> >>
> >>    
> >>
> >>>On Sat, 2003-05-24 at 11:04, James Mckenzie wrote:
> >>> 
> >>>
> >>>      
> >>>
> >>>>Matt:
> >>>>
> >>>>These are all PCI devices and can share an IRQ.  This is not usually the 
> >>>>problem with the LT modem device.  Usually the problem is either 
> >>>>incorrect memory location for the device or the wrong port selection.  I 
> >>>>think I had to specify the correct port for the modem on my A22p system.
> >>>>
> >>>>James McKenzie
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>james,
> >>>
> >>>thanks for the info. 
> >>>
> >>>what do you mean when you say, "specify the correct port"? and how did
> >>>you do it?
> >>>
> >>>also, did you have to use the dos utility PS.EXE to get it working?
> >>>
> >>>-matt
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>-- 
> >>The linux-thinkpad mailing list home page is at:
> >>http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> >>    
> >>
> >
> >
> >  
> >
> 
> 
> -- 
> The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad

-- 
---- ---- ----
Michael Reilly    michaelr@cisco.com
    Cisco Systems, Santa Cruz, CA