Jacques, I definitely have patients today, it's a lazy day around my homestead. The ol' lady is just sitting around waiting for her football game to start and I'm waiting for the game snacks. Her mother in Illinois had a place called Portillos from Naperville send us some very tasty hot dogs. Hope you're having a good one too. Thanks for all the help. RJ --- Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > > Rob, > > You have two choices: > 1-wait until Marv boards off his flight and can > logon. > 2-try my educated guess. > To me it is clear that the setup script is incorrect > because from your > log the dkpg -i *.deb clearly needs to find in > place some *.ko files > which the startup script want to copy to that place > after running dkpg! > Indeed that stage of copying the module is not > reached at all in your log. > > So, my harmless suggestion, if you are impatient, is > to REMOVE > the directory slamr-2.6.17-10-generic because if you > just untar the > tar.gz file you ADD/REPLACE the contents of that > file in the folder, > thus keeping things which may be well be wrong. > The command, to be given while being in folder > misc , is > rm -r slamr-2.6.17-10-generic > Next restart from there with tar zxf > slamr-2.6.17-10-generic.tar.gz > cd slamr-2.6.17-10-generic.tar > Save in that folder the modified version of setup > which I named jgsetup, > attached to this mail. > Apply Marv's instructions except that you type > jgsetup where he wrote > setup . > > CAVEAT: I am a COMPLETE ignorant in matters of > Debian/Ubuntu/KUbuntu > which I have never used (installed KUbuntu to see, > in view of success > among users, found nothing better that what I use, > dropped it away as I > do not need two ways to do the same thing). > > Jacques > > r jefferey wrote: > > Jacques, > > > > Looks like problems... > > > > 04Feb2007 > > > > I went to: > > > http://linmodems.technion.ac.il/packages/smartlink/Ubuntu > > and downloaded: > > slamr-2.6.17-10-generic.tar.gz > > > > Then I did this: > > > > rob@rob-desktop:~$ cd misc > > rob@rob-desktop:~/misc$ ls > > Modem NDS~ scanModem > slamr-2.6.17-10-generic.tar.gz > > rob@rob-desktop:~/misc$ tar slamr*.tar.gz > > tar: Old option `g' requires an argument. > > Try `tar --help' or `tar --usage' for more > > information. > > rob@rob-desktop:~/misc$ tar zxf slamr*.tar.gz > > rob@rob-desktop:~/misc$ ls > > Modem NDS~ scanModem slamr-2.6.17-10-generic > > slamr-2.6.17-10-generic.tar.gz > > rob@rob-desktop:~/misc$ cd slamr-2.6.27-10-generic > > bash: cd: slamr-2.6.27-10-generic: No such file or > > directory > > rob@rob-desktop:~/misc$ cd slamr-2.6.17-10-generic > > rob@rob-desktop:~/misc/slamr-2.6.17-10-generic$ ls > > 1st_Read.txt > > > sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5build1_i386.deb > > CountryList.txt slusb.ko > > setup ungrab-winmodem.ko > > slamr.ko unloading > > slmodemd wvdial.txt > > rob@rob-desktop:~/misc/slamr-2.6.17-10-generic$ > sudo > > ./setup > > Password: > > When asked about your country, Enter: > > USA > > > > Installing the Debian packages supporting > autoloading > > Selecting previously deselected package > > sl-modem-daemon. > > (Reading database ... 88231 files and directories > > currently installed.) > > Unpacking sl-modem-daemon (from > > > sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5build1_i386.deb) > > ... > > Setting up sl-modem-daemon > > (2.9.10+2.9.9d+e-pre2-5build1) ... > > FATAL: Module ungrab_winmodem not found. > > FATAL: Module slamr not found. > > Starting SmartLink Modem driver for: auto. > > Creating /dev/modem symlink, pointing to: > /dev/ttySL0. > > > > > > Copying over newer files > > cp: cannot stat `sl-modem-daemon.modutils': No > such > > file or directory > > Making folder /lib/modules/2.6.17-10-generic/extra > > Copying drivers to > > /lib/modules/2.6.17-10-generic/extra > > Checking driver install > > slamr.ko slusb.ko ungrab-winmodem.ko > > Finished installs. > > Informing the System > > > > Starting function tests, loading drivers: > > FATAL: Error inserting ungrab_winmodem > > > (/lib/modules/2.6.17-10-generic/extra/ungrab-winmodem.ko): > > Invalid module format > > FATAL: Error inserting ungrab_winmodem > > > (/lib/modules/2.6.17-10-generic/extra/ungrab-winmodem.ko): > > Invalid module format > > FATAL: Error inserting slamr > > (/lib/modules/2.6.17-10-generic/extra/slamr.ko): > > Invalid module format > > Running diagnostic: > > > > [17434203.740000] slamr: version magic > > '2.6.17-10-generic SMP mod_unload 586 REGPARM > gcc-4.0' > > should be '2.6.17-10-generic SMP mod_unload 586 > > REGPARM gcc-4.1' > > > > ports should be created by: > > slmodemd -c USA /dev/slamr0 > > error: mdm setup: cannot open dev `/dev/slamr0': > No > > such device or address > > error: cannot setup device `/dev/slamr0' > > Checking for success > > Port creation with slmodemd failed. > > Read the Slamr.txt record, other 1st_Read.txt > > CountryList.txt wvdial.txt files and the sample > > wvdial.conf. > > > > rob@rob-desktop:~/misc/slamr-2.6.17-10-generic$ > > > > > > --- Jacques Goldberg <Jacques.Goldberg@xxxxxxx> > wrote: > > > >> Ok RJ, no problem. > >> Just, please try to keep the thread in > >> discuss@xxxxxxxxxxxxx because > >> this is where it is archived - unless one of the > >> persons on the thread > >> ask you to go off line. Otherwise it is > exceedingly > >> difficult to follow. > >> I remembered very well your initial call for help > >> with the Debian kernel > >> 2.4.27. > >> Then there was this message from Marv possibly > >> charging the most recent > >> slmodem driver not to work with 2.4.27, and then > the > >> thread had changed > >> to 2.6.17. > >> With an average flux of 20-25 messages daily, > this > >> was too much for my > >> failing memory. > >> > >> Now to the point. > >> Yes just follow what Marv writes, of course. > >> He has asent you a version of the driver > specially > >> compiled for your new > >> 2.6.17-10 installation. > >> He has also sent it to me, and I immediately > stored > >> it at the usual > >> place > >> > > > http://linmodems.technion.ac.il/packages/smartlink/Ubuntu > >> Copied again from Marv's mail: > >> " Under Linux, unpack with > >> > $ tar zxf slamr*.tar.gz > >> > Move in new folder made by tar with > >> > $ cd slamr-2.6.17-10-generic > >> > Look around > >> > $ ls > >> > Do the > >> > $ sudo ./setup > >> > and follow the output instructions. > >> > > >> > When rebooting, modem setup should be > automatic, > >> You > >> > should be able > >> > to dialout with > >> > $ sudo wvdial > >> " > >> and of course return to us, please to > >> discuss@xxxxxxxxxxxxx, if you have > >> any further problem. > >> In such a mail, please remind to the readers > which > >> steps you have taken > >> from the beginning, and what went wrong (all > details > >> please). We cannot > >> remember, nor help without details! > >> > >> Keep up - Jacques > >> > > > > > > > > > > > ____________________________________________________________________________________ > > Never miss an email again! > > Yahoo! Toolbar alerts you the instant new Mail > arrives. > > > http://tools.search.yahoo.com/toolbar/features/mail/ > > #!/bin/sh > # Lines beginning with # are comments > # This is an executable file. Without the leading # > , execute it with: > # sudo ./setup &> Slamr.txt > # it will run the following commands: > COUNTRY=USA > echo "When asked about your country, Enter:" > echo " $COUNTRY" > # echo "without a space." > sleep 3 > echo Jacques inserted HERE the installation of the > echo drivers, needed by the Debian installer. > echo 4 Feb 07 > SITE=/lib/modules/`uname -r`/extra > echo Making folder $SITE > mkdir -p $SITE > echo Copying drivers to $SITE > cp *.ko $SITE/ > echo Checking driver install > ls $SITE > echo End of this modification > echo Some lines commented out at original place, see > there. > echo > echo Installing the Debian packages supporting > autoloading > dpkg -i *.deb > echo > echo Copying over newer files > cp sl-modem-daemon.modutils /etc/modprobe.d/ > # SITE=/lib/modules/`uname -r`/extra > # echo Making folder $SITE > # mkdir -p $SITE > echo Possibly copying more drivers to $SITE > cp *.ko $SITE/ > echo Preceeding command will overwrite some if not > all, so what? > echo Checking driver install > ls $SITE > echo Finished installs. > echo Informing the System > depmod -a > echo > echo Starting function tests, loading drivers: > modprobe ungrab-winmodem > modprobe slamr > # pause for a second > sleep 1 > echo Running diagnostic: > echo > dmesg | grep slamr > echo > echo ports should be created by: > echo "slmodemd -c $COUNTRY /dev/slamr0" > /usr/sbin/slmodemd -c $COUNTRY /dev/slamr0 > > echo "Checking for success" > if test -L /dev/ttySL0 ; then > echo Running wvdialconf > wvdialconf /etc/wvdial.conf > if [ -f /etc/wvdial.conf ] ; then > echo Modem detection successful > sleep 2 > echo "Carrier check = no" >> /etc/wvdial.conf > echo "edit /etc/wvdial.conf with:" > echo "sudo gedit /etc/wvdial.conf" > echo "at the lines beginning with ; and deleting > the ;" > echo "Then dialout with:" > echo " sudo wvdial" > echo "Running setup again is NOT necessary. Only > for dialout the:" > echo " sudo wvdial" > else > echo "wvdialconf failed" > fi > else > echo "Port creation with slmodemd failed." > fi > echo Read the Slamr.txt record, other *.txt files > and the sample wvdial.conf. > echo > # END > ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/
