[ltp] Modem on A22p with RH 8.0

[Ted Johansson]

James Mckenzie wrote:
> *** List MOVED use linux-thinkpad@linux-thinkpad.org for future postings ***
> Ted:
> 
> Did your error message look like the following:
> Next checking utilty versions,
>            Version_min
>  Utility    or range for kernels
>    name     2.2.16       2.4.18          Actual_version
> -------------------------------------------------------------------
> Gnu C      2.7.2.3      2.95.3-2.9.99   3.2
> Gnu make   3.79.1       3.77            3.79.1
> binutils   2.8.1.0.23   2.9.1.0.25      2.13.90.0.2
> 
> -------------------------------------------------------------------
> Sorry, versions of 3 and greater are not yet compatible with the source
> code.
> While the compilation may will succeed, the drives most likely will not
> be functional.
> Aborting with Ctrl-C is RECOMMENDED. But to continue:
> 
> I could not get the drivers to compile and work.  Although the two
> follow-up installation programs stated they successfully completed:
> ./instup2
> ./autoload.
> 
> James Mckenzie

I am not very experienced with building drivers and RPMs. First I did 
part of the build as a user, this was the first RPM on www.heby.de until 
about a week ago, but two users reported that it required a certain user 
or a group. I then rebuild everything from the clean tgz as root, and 
the two users has confirmed it did install/work OK now, and the RPM at 
www.heby.de has now been replaced with the new one.

Doing this again today, following the instructions in 1ST-RAED, and 
doing ./build_module, I do get the  warning messages as listed above, 
but I continued, and finally the script said everything was OK. I submit 
the last ~10 lines from the log BLDrecord.txt* which is the log of the 
build:
++++++++++++++++++
Next checking utilty versions, with ranges
            Version_min
  Utility    or range for kernels
    name     2.2.16       2.4.18          Actual_version
Gnu C      2.7.2.3      2.95.3-2.9.99   3.2
Gnu make   3.79.1       3.77            3.79.1
binutils   2.8.1.0.23   2.9.1.0.25      2.12.90.0.15

         gcc versions less than 3 are recommended

-rw-r--r--    1 root     root       559373 okt 13 19:24 lt_modem.o
-rw-r--r--    1 root     root        26841 okt 13 19:24 lt_serial.o
DEPMOD=/sbin/depmod
EXTRAMOD=
succeeded:  /sbin/depmod -e lt_modem.o
succeeded:  /sbin/depmod -e lt_modem.o  lt_serial.o
++++++++++++++++++
Then ./ltinst2 (You did differently, "./instup2") returns no error 
messages, and same with ./autoload.

My modules.conf now contains at the end:
++++++++++++++++++
# lt_drivers: autoloading and insertion parameter u
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 Rare 
         ter usage during lt_drivers insertion. See document
# options lt_modem vendor_id=0x115d device_id=0x042
# options lt_modem Forced=3,0x130,0x2f8,0
# section for lt_drivers ends
++++++++++++++++++
at the end, a result of the ./autoload command I think.

/dev/modem goes to tts/LT0.

Testing this with kppp, the ATI-commands give reasonable answers back.

Dialing and connection to the ISP also works as expected.


However, I see now that when I run ./build_rpm, it end with an error 
message "rpm build failed", but the RPM has been built and is working 
OK. Maybe it is the gcc2/3-thing that trickers the error message?


Regards,   Ted