[lug] Newbie tries to make laptop modem work

[D. Stimits]

Disclaimer: I know nothing about this modem or laptops in general.

Glenn Murray wrote:
> 
> With predictable results.
> 
> I have a Fujitsu LifeBook 985Tx laptop with what Win98 says is a
> Fujitsu LifeBook K56 Flex DVSD LTModem. (The laptop is running Debian
> with a 2.2.19 kernel image.)  Research indicates this is a winmodem
> made by Lucent.  Note also:
> 
> /$ cat /proc/pci
> PCI devices found:
> ...
>   Bus  0, device  16, function  0:
>     Communication controller: Lucent (ex-AT&T) Microelectronics L56xMF (rev 0).
>       Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.  Latency=64.  Min Gnt=252.Max Lat=14.
>       Non-prefetchable 32 bit memory at 0xfedffc00 [0xfedffc00].
>       I/O at 0xf4c8 [0xf4c9].
>       I/O at 0xf800 [0xf801].
> ...
> 
> Apparently this modem is supported as a linmodem
> (http://www.heby.de/ltmodem) whence I downloaded and installed the
> following (after installing kernel-image-2.2.19 for compatibility).
> 
> glenn at puck:glenn/$ sudo dpkg -i ltmodem-2.2.19_6.00b6_i386.deb
> Selecting previously deselected package ltmodem-2.2.19.
> (Reading database ... 50515 files and directories currently installed.)
> Unpacking ltmodem-2.2.19 (from ltmodem-2.2.19_6.00b6_i386.deb) ...
> Setting up ltmodem-2.2.19 (6.00b6) ...
>    Made device file    /dev/ttyLT0
>      group ownership set to dialout
>    Made symbolic link    /dev/modem --> /dev/ttyLT0
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/lt_serial.o

This would tend to indicate that your module was compiled and linked
against a kernel source tree that was either configured differently from
your running kernel, or even a different source version. I assume your
kernel is 2.2.19? And that the kernel source is not only installed, but
configured exactly as the running kernel is configured? If this was a
binary module, it means you must use the exact binary kernel that it was
compiled against (unless you are quite lucky).

D. Stimits, stimits at idcomm.com

> 
> I then tried to run wvdialconf:
> 
> glenn at puck:glenn/$ sudo wvdialconf /etc/wvdial.conf
> Scanning your serial ports for a modem.
> ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
> Port Scan<*1>: S1   S2
> Sorry, no modem was detected!  Is it in use by another program?
> Did you configure it properly with setserial?
> Please read the FAQ at http://www.worldvisions.ca/wvdial/
> If you still have problems, send mail to wvdial-list at worldvisions.ca.
> 
> I also tried kppp which presented a dialog that said "Looking for
> modem..." and then "Modem not found".  This is a PCI modem, so why is
> wvdial checking serial ports?
> 
> Any help much appreciated,
> Glenn Murray
> www.mines.edu/~gmurray/public_html/Welcome.html
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug