Linmodems Mailing list Archives

Google
 
Web archives.linmodems.org

Return-Path: <stodolsk@rcn.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 29791 invoked from network); 8 Mar 2001 13:01:28 -0000
Received: from smtp02.mrf.mail.rcn.net (207.172.4.61)
  by www.linmodems.org with SMTP; 8 Mar 2001 13:01:28 -0000
Received: from 66-44-6-165.s1689.apx1.lnh.md.dialup.rcn.com ([66.44.6.165] helo=rcn.com)
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.16 #5)
	id 14b02I-0006G9-00 ; Thu, 08 Mar 2001 08:00:55 -0500
Sender: marv
Message-ID: <3AA78280.CCDAE7C2@rcn.com>
Date: Thu, 08 Mar 2001 08:00:48 -0500
From: Marvin Stodolsky <stodolsk@rcn.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.4.2 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Sebastian.Zerbe@rz.uni-duesseldorf.de
CC: discuss@linmodems.org
Subject: Re: Typhoon Modem Quick Com 56 PCI works - I now can use my WinModem,the 
 Typhoon Modem Quick Com 56 PCI. It is a Lucent one (part of lspci's 
 outputfollws): --- 00:0a.0 Communication controller: Lucent 
 Microelectronics 56kWinModem (rev 01) --- Thanks to XX for giving the 
 clue.  I had problems to setup a connection with pppconfig and pon,but 
 with the great wvdial everything works fine.  But one little 
 problemremains: I used the precompiled tgz for the 2.2.17 Kernel,and the 
 ltinst script coming with it looks like that: --- # /*name and 
 versionnumber:@(#)ltinst 1.3*/ # /*date of get:     05/10/00 11:23:50*/ 
 # /*date ofdelta:   12/28/99 
 12:10:46*/#=========================================================================== 
 #File Name :     
 ltinst#===========================================================================#!/bin/sh  
 group="uucp" mode="666"   device="/dev/ttyS14"  ./ltuninst >/dev/null 
 2>/dev/null  /sbin/insmod -f ltmodem  rm -f $device  mknod $device c62 
 78  rm -f /dev/mod
References: <01030811124300.00839@pc765>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sebastian

>I'm using a Debian system (2.2)). So far so good,
> but it occasionally (not only at reboots!) happens that the mode of /dev/ttyS14
> is changed to crw-r----- without me doing anything. Has anybody a clue >what might be the reason for that?

A few items.
1) The old kernel-2.2.17 which I put together, is now not necessary and
might not? be beneficial.  It includes the old tty.h patch, which was
only necessary in the Dark Age of version mis-matched ltmodem.o and
drivers.  My system is Debian too, and using version matched ltmodem.o
into kernels 2.4.2

2) The are many subtle benefits to using the current driver kit.
Download
ltmodem-5.78e.tar.gz from: http://walbran.org/sean/linux/stodolsk/.

3) Use its ltinst, underwhich /dev/ttyS14 still serves wvdial as Only a
symbolic link to the real character device /dev/ttyLT0

4) The change in permissions you mention, on my system: 
$ ls -l /dev/ttyLT0
crw-r--r--    1 root     uucp      62,  64 Mar  8 07:35 /dev/ttyLT0

is harmless and presumable done as part of a Debian security sweep,
though I haven't tried to track it in detail.

MarvS   




> Zerbe wrote:
> 
> I now can use my WinModem, the Typhoon Modem Quick Com 56 PCI.
> It is a Lucent one (part of lspci's output follws):
> ---
> 00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
> ---
> Thanks to Jaques Goldberg for giving the clue.
> 
> I had problems to set up a connection with pppconfig and pon, but with the
> great wvdial everything works fine.
> 
> But one little problem remains:
> I used the precompiled tgz for the 2.2.17 Kernel, and the ltinst script coming
> with it looks like that:
> ---
> #       /*name and version number:@(#)ltinst    1.3*/
> #       /*date of get:            05/10/00 11:23:50*/
> #       /*date of delta:          12/28/99 12:10:46*/
> #===========================================================================
> #       File Name :     ltinst
> #===========================================================================
> #!/bin/sh
> 
> group="uucp"
> mode="666"
> 
> device="/dev/ttyS14"
> 
> ./ltuninst > /dev/null 2>/dev/null
> 
> /sbin/insmod -f ltmodem
> 
> rm -f $device
> 
> mknod $device c 62 78
> 
> rm -f /dev/modem
> 
> ln -s $device /dev/modem
> 
> chgrp $group $device
> chmod $mode $device
> 
> cp ltmodem.o /lib/modules/`uname -r`/misc/
> 
> echo "/sbin/insmod -f ltmodem" >> /etc/rc.d/rc.local
> ---
> I ran it once and then changed the group of /dev/ttyS14 to modem and the mode
> to crw-rw---- . Then I used modconf to make the ltmodem.o reloaded every time
> I'm booting (as you can guess I'm using a Debian system (2.2)). So far so good,
> but it occasionally (not only at reboots!) happens that the mode of /dev/ttyS14
> is changed to crw-r----- without me doing anything. Has anybody a clue what
> might be the reason for that?
> 
> Sebastian Zerbe

Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003