Debian: Problem installing 'Source RPM package' driver for winmodem
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Debian: Problem installing 'Source RPM package' driver for winmodem
Anyone who can advise please on getting a Debian (derived from the Knoppix 3.3 live CD) setup to build & install this RPM source for a winmodem driver:
I've been using Linux for about 1 week so far, so I dont really know what i'm doing *yet* -
I got from the WWW (the page has since been removed from Agere's site), the driver for the laptop's pseudo-modem. The documentation suggest this driver should work with the modem I have (according to the response I got from 'scanmodem').
The problem I have is using this Redhat/Suse source RPM with Debian:
Agere's instructions were:
> Source RPM Generic x86: "AgereSoftModemBeta-2.1.0-2.src.rpm"
> To install driver from the Source RPM package (*.src.rpm), you need to
> first make the Binary RPM package using the following command.
> RedHat # rpmbuild --rebuild AgereSoftModemxx.src.rpm
> SuSE # rpm --rebuild AgereSoftModemxx.src.rpm
> Install the binary package from the appropriate
> RPMS/(architecture) directory with the command
> # rpm -i AgereSoftModemBetaxx.i386.rpm
So I have the file "AgereSoftModemBeta-2.1.0-2.src.rpm", and I issue comand
"rpmbuild --rebuild AgereSoftModemBeta-2.1.0-2.src.rpm" at the root console.
Some things happen, files are copied, then I get a message:
"Error: ./agrinst : Line 86: /agr_softmodem : No such file or directory.
So I go and dig in "agr_inst", which I find in
along with some .c .h & .o files, and "Makefile".
Inside "agrinst" is the following: (line numbers added by me here)
62 chmod +x agr_softmodem
63 if [ -e /etc/rc.d/halt ]; then \
64 RC_DIR=`echo /etc/rc.d`; \
66 if [ -e /etc/rc.d/init.d/halt ]; then \
67 RC_DIR=`echo /etc/rc.d/init.d`; \
71 if [ -e $RC_DIR/halt ]; then \
72 cp -f ./agr_softmodem $RC_DIR/agr_softmodem; \
73 if [ -d /etc/rc.d/rc3.d ]; then \
74 ln -s $RC_DIR/agr_softmodem /etc/rc.d/rc3.d/S99agr_softmodem; \
76 if [ -d /etc/rc.d/rc5.d ]; then \
77 ln -s $RC_DIR/agr_softmodem /etc/rc.d/rc5.d/S99agr_softmodem; \
81 mknod $device c 62 78
82 ln -s $device /dev/modem
83 chgrp $group $device
84 chmod $mode $device
86 $RC_DIR/agr_softmodem start
88 echo some files needed for installation are missing; \
There in Line 86 the label $RC_DIR is missing, 'cos in lines 63,66,73,76 the conditions are never satisfied.
My DEBIAN installation has no "/etc/rc.d" and obviously no subdirs like "/rc3.d"
What I do have is
all with various links/files in them, but nothing like "halt" or "init.d".
IS there any easy change to this script that will make it work?
Is there any point to doing that (getting the rc run-level links correct, since when I issue the command "agr_softmodem start" directly, I get a response that the modem driver is installed, but I still get no useful response from the modem, only that it is 'BUSY", (which is better than modem-not-found I guess).
Oh I did change device="/dev/ttyS14" (in Line 14 of agrinst) to ttyS3, since my comms software doesn't show any ports beyond S3. Are the first 4 reserved? Have I unmapped something importand by 'taking' ttyS3 like that?
At some stuge I expected to find a file:
since the instuctions say I have to "rpm -i" it, but it hasn't appeared yet.
I DO have files like:
/usr/src/rpm/BUILD/AgereSoftModemBeta-2.1.0/[several .o .c .h files]
(Yes, I know I need to use 'Alien' to proces an RPM to a DEB pakage)
then compile it yourself. There should be a readme in the package but the basics for the Debian way to create a Debian package would be to untar the file into /usr/local/src and then from the command line cd to /usr/local/src . Unpack the file by doing as root tar -xvf name_of_fiile.tar.gz . Have a look at the readme but you should be able to build a debian package. First do apt-get install fakeroot then do fakeroot debian/rules binary and when the package has been created do fakeroot debian/rules clean. Check that the package is there and then do dpkg -i name_of_package.deb.
The normal way would be ./configure then do make then do make install.
Thanks for that info,
That .tar.gz driver file you mentioned, I have it, and when I examine its contents it holds exactly the same files that my "rpmbuild" command created, including that pesky "agrinst" file with all the troublesome labels concerning "/etc/rc.d" directories.
I haven't followed you instructions any further yet - but will report back when i get a chance to try it all out.
Thanks again for that info - that was what I was anticipating would fix things;
However, the driver seems to install Ok now, with no errors. and I can turn it "on" and "off" with command line switches, & it responds that it is loaded & unloaded Ok, etc. (and warns me iabout tainted kernel modules), but even so, I can get no response from the modem or dev/ttyS14.
Should I conclude this is not the right driver after all ?
These drivers are very if'y and quite honestly for the amount of time and energy spent trying to get them to work you might as well go out and buy an external serial modem that just work. They are very cheap now and many about the same price as internal modems. If you want to pursue this you may need to do quite a bit of research through Google. The warning about "tainted kernel module" is normal since you have added a non-standard module.
If at any stage you want/need to get rid of this stuff in rc.d etc then do update-rc.d -f <script_name> remove.