src]# ln -sf linux-2.4.21-0.13mdk /ltmodem-8.26a/source
src]# cd /ltmodem-8.26a/source
source]# make
echo Using KCFLAGS for gcc version 3.x
Using KCFLAGS for gcc version 3.x
gcc -D__KERNEL__ -I/lib/modules/2.4.21-0.13mdk/build/include -Wall -Wstrict-prototypes -O3 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -DMODULE -DLT_VERSION=8.26a9 -DLINUX -DNO_EEPROM -DLT_SERIAL_MODULE=lt_serial -c -o ltmodem.a ltmodem.c
ld -r -o lt_modem.o ltmodem.a ltmdmobj.o".gcc3"
echo Using KCFLAGS for gcc version 3.x
Using KCFLAGS for gcc version 3.x
gcc -D__KERNEL__ -I/lib/modules/2.4.21-0.13mdk/build/include -Wall -Wstrict-prototypes -O3 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -DMODULE -DLT_VERSION=8.26a9 -DLINUX -DNO_EEPROM -DLT_SERIAL_MODULE=lt_serial -c -o serial-lt-2.4.a serial-lt-2.4.c
ld -r -o lt_serial.o serial-lt-2.4.a
source]# make install
/usr/bin/install -c -m644 --owner=0 --group=0 -b -D lt_modem.o /lib/modules/2.4.21-0.13mdk/ltmodem/lt_modem.o
/usr/bin/install -c -m644 --owner=0 --group=0 -b -D lt_serial.o /lib/modules/2.4.21-0.13mdk/ltmodem/lt_serial.o
echo "The drivers are now installed - now run ./autoload if you want to enable automatic loading of the module"
The drivers are now installed - now run ./autoload if you want to enable automatic loading of the module
source]# ./autoload
Diagnostic information and Guidance is being written to BLDrecord.txt
There is a file /etc/devfs/conf.d/modem.conf which manages a symbolic link:
/dev/modem --> /dev/tts/N
for service of controller chip modems. Its presence however will fault
device file system daemon management of the symbolic link:
/dev/modem --> /dev/tts/LT0
desried for ltmodem support. For safe storage, please
mv /etc/devfs/conf.d/modem.conf /root/
and then inform the System with:
killall -HUP devfsd
/etc/modules.conf contains lines for autoloading the ltmodem driver.
the symbolic link to /dev/tts/LT0
Browse /ltmodem-8.26a/source for guidance and tools.
If not familar with the ltmodem drivers, run the interactive CHECKOUT utility by executing:
./checkout
Otherwise, get Online and Enjoy
Relate problems to
[email protected]
Gratitude too, to
[email protected]
source]# cd ..
ltmodem-8.26a]# cd utils
./checkout
which: no wvdialconf in (/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin)
A direct test of your modem is included in this checkout script.
While several other checkout tests will still be done,
please install the package WVDIAL provided by your Linux distro.
Then rerun checkout.
This checkout utility currently
checks for expected components of a Lucent DSP winmodem installation
provides a minor tutorial
if modem driver insertion is successfull
runs a wvdialconf test
unloads excess drivers if module loading fails
Does not as yet have signficant problem solving action
except for referrals to Documentation.
Can readily be adapted to work with other winmodem installations.
The current Working folder is: /ltmodem-8.26a/utils.
To continue: Enter
================================================== ==================
Now acquiring distribution data:
The Linux distribution is: mandrake
End of distribution check.
Diagnostic information is progressively being written to /ltmodem-8.26a/utils/checkout.txt .
Often, contents of this record can aid in solving problems.
ls: ../ltmodem*: No such file or directory
To continue: Enter
================================================== ==================
You will be requested to participate by prompts to Enter a pre-written command such as:
ls NoFile
with the resulting output appearing between the dotted lines.
--------------------
ls: NoFile: No such file or directory
--------------------
And with
--------------------
--------------------
meaning no output was generated.
================================================== ===============
Proceeding to access PCI modem hardware information
Enter
Found /usr/share/doc/ltmodem-kv_2.4.21_0.13mdk-8.30a3/utils/scanPCI
... using /usr/bin/lspci
By the Class 07nn: criteria, detected system PCI modem devices are:
device Class VendorID:DeviceID == ModemID
----------------------------------------------------------------
01:08.0 Class 0780: 11c1:044e
01:08.0 Communication controller: Lucent Microelectronics LT WinModem
VENDOR 0x11c1 DEVICE 0x044e
ID are within the serviced ranges:
To continue: Enter
A supported DSP Modem verified:
MODEM_ID=11c1:044e
IDs of supported Lucent DSP PCI modems have ranges:
Vendor vendor_id device_id range
-----------------------------------------------
LUCENT 0x11c1 0x0440-0x045c
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
To see detailed information on 11c1:044e
Enter
Copying this detailed information to ModemData.txt
----------------------------------------------
01:08.0 Communication controller: Lucent Microelectronics LT WinModem
01:08.0 Class 0780: 11c1:044e
Subsystem: 1235:044e
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 9
Region 0: Memory at f4100000 (32-bit, non-prefetchable) [disabled] [size=256]
Region 1: I/O ports at 2400 [size=8]
Region 2: I/O ports at 2000 [size=256]
Capabilities: [f8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
----------------------------------------------
Proceeding to verify the presence of the modem drivers, please
Enter
The active System kernel is 2.4.21-0.13mdk
For kernels 4.nn the modem drivers should have been installed within:
/lib/modules/2.4.21-0.13mdk/ltmodem
Changing directory:
cd /lib/modules/2.4.21-0.13mdk/ltmodem
The output to the next output should at least include:
-------------------
-rw-r--r-- 1 root root SIZE DATE_install lt_modem.o
-rw-r--r-- 1 root root SIZE DATE_install lt_serial.o
-------------------
wherein the driver with proprietary DSP=Digital Signal Processor code is:
lt_modem.o
and the driver with Open Source code is:
lt_serial.o
To display the resident drivers:
Enter
-------------------
-rw-r--r-- 1 root root 543712 may 30 12:41 lt_modem.o
-rw-r--r-- 1 root root 543712 may 28 22:12 lt_modem.o~
-rw-r--r-- 1 root root 28109 may 30 12:41 lt_serial.o
-rw-r--r-- 1 root root 28109 may 28 22:12 lt_serial.o~
-------------------
Found driver: lt_modem.o
Found driver: lt_serial.o
./checkout: line 309: tmp/tmpfile.drivers: No such file or directory
Modem drivers check completed.
Changing back to the original Working folder:
cd /ltmodem-8.26a/utils
================================================== =======
There is a functional dependence between many kernel modules.
During boot up and module installations, these dependencies are written during a:
depmod -a
to FileNames: /lib/modules/2.4.21-0.13mdk/modules.*
Enter
---------------------
/lib/modules/2.4.21-0.13mdk/modules.dep
/lib/modules/2.4.21-0.13mdk/modules.description
/lib/modules/2.4.21-0.13mdk/modules.generic_string
/lib/modules/2.4.21-0.13mdk/modules.ieee1394map
/lib/modules/2.4.21-0.13mdk/modules.isapnpmap
/lib/modules/2.4.21-0.13mdk/modules.parportmap
/lib/modules/2.4.21-0.13mdk/modules.pcimap
/lib/modules/2.4.21-0.13mdk/modules.pnpbiosmap
/lib/modules/2.4.21-0.13mdk/modules.usbmap
----------------------
The lt_ modules lines within then can be selectively displayed with:
grep lt_ /lib/modules/2.4.21-0.13mdk/modules.*
Enter
----------------------
/lib/modules/2.4.21-0.13mdk/modules.dep:/lib/modules/2.4.21-0.13mdk/ltmodem/lt_modem.o:
/lib/modules/2.4.21-0.13mdk/modules.dep:/lib/modules/2.4.21-0.13mdk/ltmodem/lt_serial.o: /lib/modules/2.4.21-0.13mdk/ltmodem/lt_modem.o
----------------------
For simplicity, some trimming of the PATHs can be done:
----------------------
lt_modem.o:
lt_serial.o: /lib/modules/2.4.21-0.13mdk/ltmodem/lt_modem.o
----------------------
The first line including only lt_modem.o shows that its loading
has no prior dependencies.
The line with lt_serial.o followed by lt_modem.o
means lt_serial.o loading requires prior loading of lt_modem.o
Proceed to the driver loading test.
First check which drivers are loaded already with:
lsmod
Enter
Si hay inters y deseos de aprender!!!! 
cada dia mas y mas, sobre todo lo de aprender a configurar e instalarlo, para poderlo usar como debe ser, la idea es dejar de usar sistemas como los de mocosof que solo dan dolores de cabeza y errores--
bien lo que dice el readme, entre sus instrucciones de instalacion, he seguido los pasos de instalacion, pero no se que significan los errores que me arroja y aveces cuando no los bota, no entiendo si estoy por buen camino o no,, a eso me refiero.
CONTINUA la instalcion de modem 
ahora no me deja iniciar por que me arroja un ERROR. 
mdk 10.1 ¿Cual modem? 
Te cuento que no sirvio lo del arreglo del linux, me salian preguntas a las que respondia que si (Y) pero alfinal seguia igual.
Este tema le ha gustado a 2 personas (incluyéndote)