mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
gferg
parent
725a4e7eae
commit
2004f03492
|
|
@ -38,7 +38,7 @@ section can be combined for all of them, methinks.
|
|||
|
||||
<title>Linmodem-HOWTO <!-- insert your title here -->
|
||||
<author>Sean Walbran <tt/sean(at)walbran.org/ and Marvin Stodolsky <tt/stodolsk(at)erols.com/
|
||||
<date>v0.40, 13 December 2000 <!-- always have a version number
|
||||
<date>v0.41, 13 December 2000 <!-- always have a version number
|
||||
and a date -->
|
||||
<abstract> <!-- the abstract: a short and precise description -->
|
||||
<nidx>template</nidx> <!-- add indexing keywords as you go along -->
|
||||
|
|
@ -747,13 +747,13 @@ With the modules in hand, proceed to install as follows:
|
|||
<p>
|
||||
<enum>
|
||||
<item> Change to the root user: <tt>su</tt> (enter root password when prompted)
|
||||
<item> Create the device file: <tt>mknod /dev/pctel c 62 79 </tt><p>
|
||||
<item> Create the device file: <tt>mknod /dev/pctel c 62 79 </tt>
|
||||
<item> Make convenience device: <tt>ln -s /dev/pctel /dev/modem</tt>
|
||||
<item> Make convenience device: <tt>ln -s /dev/pctel /dev/ttyS15</tt>
|
||||
<item> Set device ownership: <tt>chgrp uucp /dev/pctel </tt>
|
||||
<item> Set device permissions: <tt>chmod 666 /dev/pctel </tt>
|
||||
<item> Install module file (only for package type 2, above): <tt>cp pctel.o /lib/modules/`uname -r`/misc/</tt>
|
||||
<item> Insert module(s) in kernel with <tt>insmod -f</tt><em>modulename</em>
|
||||
<item> Insert module(s) in kernel with <tt>insmod -f ham</tt>
|
||||
</enum>
|
||||
<p>
|
||||
|
||||
|
|
@ -813,8 +813,20 @@ you can get this version at Rob Clark's site
|
|||
A binary-only, beta driver for the Intel Creatix V.90 HaM
|
||||
compiled under kernel 2.2.16 was released to the Linmodems.org
|
||||
mailing list in late November, 2000, and is mirrored at
|
||||
<url url="http://walbran.org/sean/linux/stodolsk/Ham.zip">. Contact Dorian
|
||||
Araneda (dorian.araneda@intel.com) for details.
|
||||
<url url="http://walbran.org/sean/linux/stodolsk/Ham.zip">.
|
||||
To install:
|
||||
<p>
|
||||
<enum>
|
||||
<item> Change to the root user: <tt>su</tt> (enter root password when prompted)
|
||||
<item> Create the device file: <tt>mknod /dev/ham c 240 1 </tt>
|
||||
<item> Make convenience device: <tt>ln -s /dev/ham /dev/modem</tt>
|
||||
<item> Make convenience device: <tt>ln -s /dev/ham /dev/ttyS15</tt>
|
||||
<item> Set device ownership: <tt>chgrp uucp /dev/ham </tt>
|
||||
<item> Set device permissions: <tt>chmod 666 /dev/ham </tt>
|
||||
<item> Install module file: <tt>cp ham.o /lib/modules/`uname -r`/misc/</tt>
|
||||
<item> Insert module in kernel with <tt>insmod -f</tt><em>ham</em>
|
||||
</enum>
|
||||
|
||||
<p>
|
||||
|
||||
<sect1>3Com Mini-PCI
|
||||
|
|
@ -829,6 +841,103 @@ given, linmodem@new-n-used.com, and not to the mailing list.
|
|||
and links.
|
||||
<p>
|
||||
|
||||
<!--
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
-->
|
||||
<sect>Troubleshooting
|
||||
<p>
|
||||
So you've read through this document, the
|
||||
<url url="http://www.linuxdoc.org/HOWTO/Modem-HOWTO.html" name="Modem-HOWTO">,
|
||||
and the
|
||||
<url url="http://www.linuxdoc.org/HOWTO/PPP-HOWTO/index.html" name="PPP Howto">,
|
||||
are pretty sure that your modem matches one of the drivers available,
|
||||
but it still doesn't work? There are a number of points in
|
||||
the process at which something could break down.
|
||||
<p>
|
||||
Linux generally maintains records of networking connections which are
|
||||
very useful in troubleshooting problems. Their particular filenames
|
||||
vary with both the Linux distribution and Dial-in software,
|
||||
but
|
||||
the system log files <tt>/var/log/messages</tt>, <tt>/var/log/syslog</tt>,
|
||||
etcetera, should provide at least some information.
|
||||
<p>
|
||||
For both
|
||||
your own trouble shooting and queries for help to a list, it will be
|
||||
useful if you accumulate the information requested below. As root,
|
||||
change to the directory in which the modem
|
||||
install scripts are located, and
|
||||
start a
|
||||
script record as shown below. After this script is terminated
|
||||
with "exit," copy it out of your Linux partition for transmission to the
|
||||
list which may aid you.
|
||||
<p>
|
||||
(Below, # are explanatory comments.)
|
||||
<verb>
|
||||
# start the recording,
|
||||
script ModemTest.txt
|
||||
# type in as much info on your Modem card as you have
|
||||
echo winmodem name, manufacturer, designation, and chip if possible
|
||||
# this gives your current kernel version
|
||||
uname -r
|
||||
# this gives information on your serial ports
|
||||
setserial -agv /dev/ttyS*
|
||||
# this information on your interrupts (irq)
|
||||
cat /proc/interrupts
|
||||
# show the contents of your module installation script (insert script name):
|
||||
cat ScriptName
|
||||
# Check if your script is executable:
|
||||
ls -l ScriptName
|
||||
# a response is OK if it has "x" such as below:
|
||||
# -rwxrw-rw- 1 root root 654 Jan 6 2000 ltinst
|
||||
# otherwise make it executable with:
|
||||
chmod o+x ScriptName
|
||||
# verify with
|
||||
ls -l ScriptName
|
||||
# if ScriptName has not been successfully run before under this kernel
|
||||
# run it with:
|
||||
./ScriptName
|
||||
# what is the symbolic link /dev/modem set to:
|
||||
ls -l /dev/modem
|
||||
# What is the DeviceName specified in the ScriptName (/dev/ttyS14 or ...?)
|
||||
echo DeviceName
|
||||
# what is your modem driver name? Something like DriverName.o
|
||||
# with the ".o" indicating it is a compiled binary
|
||||
echo This is my DriverName.o
|
||||
# if should have been inserted in the Modules Path
|
||||
# Try to display it there with:
|
||||
find /lib/modules | grep DriverName
|
||||
# Is DriverName among the modules installed in the running kernel?
|
||||
lsmod
|
||||
# if not try a simple insertion:
|
||||
insmod ./DriverName.o
|
||||
# or if it was in the Modules Path, the following will suffice:
|
||||
insmod DriverName
|
||||
# check for insertion:
|
||||
lsmod
|
||||
# if not inserted, try forcing:
|
||||
insmod -f ./DriverName
|
||||
# list your inserted modules again.
|
||||
lsmod
|
||||
# If DriverName is NOT listed,
|
||||
# their is an incompatibility between modem hardware, driver and kernel.
|
||||
# Further effort will be of No use.
|
||||
# If DriverName is listed, let's do a bit more information.
|
||||
# You may first wish to rerun the configuration utility
|
||||
# used to setup dial-in connections for your Linux installation.
|
||||
# Remember to edit your PassWord from this record later.
|
||||
# You will probably be queried for the following information
|
||||
# which you should have ready:
|
||||
#Port to be used (/dev/modem or /dev/ttySn),Dial-inNumber, UserName, PassWord.
|
||||
# Run your configuration utility.
|
||||
YourSetUpConf
|
||||
# To stop recording
|
||||
exit
|
||||
</verb>
|
||||
<p>
|
||||
If dialin was not successfull, append to this a record from your log file.
|
||||
As an example, a section of a /var/log/syslog from a Debian
|
||||
Linux system is below.
|
||||
|
||||
<!--
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
-->
|
||||
|
|
@ -976,7 +1085,7 @@ mailing list at <url url="http://linmodems.org" name="Linmodems.org">.
|
|||
<p>
|
||||
<sect1> Who wrote the driver for my winmodem, and how do I contact him/her?
|
||||
<p>
|
||||
If a contact address is not given above, you can in genera assume
|
||||
If a contact address is not given above, you can in general assume
|
||||
that it was probably somebody on contract to the manufacturer, who probably
|
||||
does not have the
|
||||
authority the update/release/change the source code, and who probably doesn't
|
||||
|
|
|
|||
Loading…
Reference in New Issue