Ian, On Sun, Aug 28, 2011 at 12:11 PM, Ian Smith <ismith@xxxxxxxxxxxxxx> wrote: > Marvin, > > Many thanks for your help. > > I followed your instructions and got:- > > [: 10: -ne: unexpected operator > These script shuts down support for Ethernet and Pcmcia and unloads > Non-essential modules. > This is a pre-cautionary step when resource conflicts are suspected. > The script is obvious and can be easily modified should you choose to > do so. > > Should you wish to avoid shutdown actions, > Abort now with: Ctrl-C > or to continue: Enterread: 23: arg count > ============================================== > > There is an eth0, shutting it down > Ignoring unknown interface eth0=eth0. > ifdown: interface down not configured > > With retention of power sensor and mouse drivers, > Initiating removals of unused modules with: > modprobe -r ModuleName > > -- Action summary from file Unload.txt --- > MODULES_INITIAL=agrserial agrmodem binfmt_misc vboxnetadp vboxnetflt > vboxdrv parport_pc ppdev vesafb snd_hda_codec_hdmi nvidia > snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep joydev > snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer > snd_seq_device snd psmouse soundcore sis_agp snd_page_alloc lp serio_raw > uvcvideo videodev parport mos7840 usbserial video ahci sis190 libahci > > modprobe -r on: agrserial binfmt_misc vboxnetadp vboxnetflt > parport_pc ppdev vesafb snd_hda_codec_hdmi nvidia snd_hda_codec_realtek > snd_hda_intel snd_hda_codec snd_hwdep joydev snd_pcm snd_seq_midi > snd_timer snd soundcore sis_agp snd_page_alloc lp serio_raw uvcvideo > mos7840 video ahci sis190 libahci > Need agrmodem too here. Only agrserial is here. > > MODULES_FINAL=binfmt_misc vesafb snd_hda_codec_hdmi nvidia > snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm > snd_timer snd psmouse soundcore snd_page_alloc ahci libahci > Then both agrserial, agrmodem are not present, thus the command ian@ian-laptop:~/Downloads/Unloading$ sudo wvdialconf wvtest.conf fails :( If it were to survive, this is when the computer freezes right? (without running sudo ./unloading). Regards, Antonio > Bye > > ian@ian-laptop:~/Downloads/Unloading$ sudo wvdialconf wvtest.conf > Editing `wvtest.conf'. > > Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 S1 S2 S3 S4 S5 S6 S7 > Modem Port Scan<*1>: S8 S9 S10 S11 S12 S13 S14 S15 > Modem Port Scan<*1>: S16 S17 S18 S19 S20 S21 S22 S23 > Modem Port Scan<*1>: S24 S25 S26 S27 S28 S29 S30 S31 > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://alumnit.ca/wiki/?WvDial > > > ============================== > > Does this mean the modem isn't set up? > > Kind Regards, > > > Ian > > > On 28/08/11 17:22, Marvin Stodolsky wrote: >> Ian, >> >> Per earlier, please run >> $ sudo /unloading >> before running >> $ sudo wvdialconf wvtest >> >> Since this combination worked for you before, likely it will again. >> Once basic responsiveness of the modem is thus confirmed, >> you can proceed with FAX specific tests. >> >> On http://linmodems.technion.ac.il/packages/ there is a faxing.tar.gz >> with guidance for setting up fax. This was worked up for modems using >> the /dev/ttySL0 port >> Thus in your trials, substitute ttySAGR for ttySL0 >> >> MarvS >> >> On Sun, Aug 28, 2011 at 11:27 AM, Ian Smith <ismith@xxxxxxxxxxxxxx> wrote: >>> Jacques, >>> >>> My apologies - I will try to give as much information as possible. I am >>> most grateful for all your help, but I didn't appreciate that my >>> situation hadn't been observed before. >>> >>> On completion of the sudo modprobe command, I don't get any message - >>> only a fresh command line. >>> >>> On the wvdialconf command. I get (from memory) a listing containing S1 >>> S2 .... I can try to run the command again, but I may not be able to >>> capture the output - unless a photo would suffice. >>> >>> After the output, the command line prompt was appended to the current >>> line, not on a new line - at that point, the mouse cursor still worked. >>> When I hit Enter, then the laptop froze. >>> >>> When I said the laptop "froze", the mouse cursor had disappeared, and no >>> keyboard inputs generated any response. >>> >>> My only way to restart the laptop was to depress the "On" button for >>> several seconds. >>> >>> I have looked for wvtest.conf but cannot seem to locate it, and the >>> searches throughout my laptop are taking a long time without any >>> results. Where should I find it? >>> >>> Kind Regards, >>> >>> >>> Ian >>> >>> >>> On 28/08/11 15:21, Jacques Goldberg wrote: >>>> Ian >>>> >>>> I always select not to "compete" with Marv becaise it distubs more >>>> than it helps. >>>> I answer to save your time waiting and his time answering >>>> We do not see your screen. We have no other source than you. So we >>>> must ask you NOT to be terse in your answer. Please give us all details. >>>> You gave the sudo modprobe command: what did it output to the screen? >>>> Then you gave the sudo wvdialconf command as shown by Marv sudo >>>> wvdialconf wvtest.conf with a carriage return like when you give any >>>> console command, right? >>>> But what happened next? >>>> Did wvdialconf write anything to the screen? If yes, what? What does >>>> mean "after the wvdialconf the laptop froze"? did wvdialconf complete >>>> with a prompt at the end of the output text, which suggests that >>>> wvdialconf did print something? >>>> If indeed you got a prompt after running wvdialconf, what did you try >>>> to do ? Did you try several things, in several windows, none of which >>>> gave any sign of life, to conclude that the laptop froze? >>>> How did you restart the laptop? >>>> Most important, have you checked if a file named wvtest.conf has been >>>> created in your computer? We badly need its contents, if it exists! >>>> >>>> >>>> Jacques >>>> >>>> On 08/28/2011 04:53 PM, Ian Smith wrote: >>>>> Marvin, >>>>> >>>>> Many thanks - I tried the modprobe -which worked, but after the >>>>> wvdialconf - my laptop froze - but only (it seems) once I add a >>>>> carriage return as the prompt is on the end of the output text. >>>>> >>>>> Kind Regards, >>>>> >>>>> >>>>> Ian >>>>> >>>>> On 28/08/11 13:11, Marvin Stodolsky wrote: >>>>>> Ian, >>>>>> >>>>>> A first simple response test is: >>>>>> $ sudo modprobe agrserial >>>>>> $ sudo wvdialconf wvtest.txt >>>>>> >>>>>> MarvS >>>>>> >>>>>> On Sun, Aug 28, 2011 at 6:56 AM, Ian Smith <ismith@xxxxxxxxxxxxxx >>>>>> <mailto:ismith@xxxxxxxxxxxxxx>> wrote: >>>>>> >>>>>> Marvin, >>>>>> >>>>>> Many thanks - I did as you instructed, and there was no crash, >>>>>> but how can I tell if the modem is working - I can't seem to see >>>>>> any new device - or anything that seems to be a modem? >>>>>> >>>>>> Sorry for being so daft. >>>>>> >>>>>> Kind Regards, >>>>>> >>>>>> >>>>>> Ian >>>>>> >>>>>> On 28/08/11 11:40, Marvin Stodolsky wrote: >>>>>>> Ian, >>>>>>> >>>>>>> Try installing the attached with: >>>>>>> >>>>>>> $ sudo dpkg -i agrsm-tools*.deb >>>>>>> >>>>>>> It is OK on my System >>>>>>> If the install is OK, it will later suffice to activate the >>>>>>> modem with: >>>>>>> $ sudo modprobe agrserial >>>>>>> >>>>>>> MarvS >>>>>>> >>>>>>> >>>>>>> On Sun, Aug 28, 2011 at 5:43 AM, Ian Smith , Aug 28, 2011 at >>>>>>> 5:43 AM, Ian Smith <ismith@xxxxxxxxxxxxxx >>>>>>> <mailto:ismith@xxxxxxxxxxxxxx>> wrote: >>>>>>> >>>>>>> Marvin, >>>>>>> My apologies for the delay in getting back to you. >>>>>>> >>>>>>> When I tried to install the package, Ubuntu Software Centre >>>>>>> complains, saying "wrong-file-owner-uid-or-gid" for maybe >>>>>>> all of the files. How should I proceed? >>>>>>> >>>>>>> Kind Regards, >>>>>>> >>>>>>> >>>>>>> Ian >>>>>>> >>>>>>> On 13/08/11 00:55, Marvin Stodolsky wrote: >>>>>>>> Updates of the two packages to 2.6.38 level, >>>>>>>> including the new Debian/Ubuntu packaging requirements >>>>>>>> >>>>>>>> Ian, >>>>>>>> Nothing is required on your part. You can use your >>>>>>>> already installed code. >>>>>>>> Only the packaging is different >>>>>>>> >>>>>>>> MarvS >>>>>>>> >>>>>>>> On Thu, Aug 11, 2011 at 8:59 PM, Marvin Stodolsky >>>>>>>> <marvin.stodolsky@xxxxxxxxx >>>>>>>> <mailto:marvin.stodolsky@xxxxxxxxx>> wrote: >>>>>>>> >>>>>>>> Just a minor change in the packaging procedure, >>>>>>>> because the older package will not install on current >>>>>>>> Debian/Ubuntu systems. >>>>>>>> Discard the old package. >>>>>>>> >>>>>>>> MarvS >>>>>>>> >>>>>>>> >> >
