Roger, the command suggested below should be: $ sudo /etc/init.d/pulseaudio off not $ sudo /etc/init.d/pulse-audio off Just trying it on my system there is a response: "The script you are attempting to invoke has been converted to an Upstart job, but off is not supported for Upstart jobs." So I presume you will be blocked also. I was also blocked on trying to unload snd related modules: $ sudo modprobe -r snd_hda_codec_hdmi FATAL: Module snd_hda_codec_hdmi is in use. Short of removing your audio card from the PC, there is not a simple solution under Ubuntu, with its high media usage preferences. You might try other Linux distros, where under this problem might not be present. Condolences MarvS On Mon, Apr 1, 2013 at 9:22 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > Roger, > > I have reviewed all your communications. > My best guess on the problem is that the IRQ 17 has been assigned to both > the ATI audio card and the modem card. > > Under Ubuntu the Audio function will have precedence over the modem. > The only way to use the modem would be to completely shut down audio > function. The details depend on one's particular system. > But you can try: > $ sudo /etc/init.d/pulse-audio off > If this is successful, again > $ sudo wvdialconf > to assess if the modem is found. > > Another approach is to list the Audio related drivers with: > $ lsmod | grep snd > Starting from the top of the list thus obtained do: > $ sudo modprobe -r DriverName > checking occassionally for success with again > $ lsmod | grep snd > If you can remove all these drivers, try the > $ sudo wvdialconf > > Report back presently: > > MarvS > > > On Sat, Mar 30, 2013 at 1:09 AM, Roger Davis <rogerdavis@xxxxxxxxxxx> > wrote: >> >> If all it does is the same as setserial, I have worked all around that a >> couple of times. >> >> However, if it actually sets the modem on ttyS3 instead of ttyS4, there >> may be something there. I presume I can't do that in SetSerial? >> >> >> >> The reasonable man adapts himself to the world. >> The unreasonable man persists in trying to adapt the world to himself. >> Therefore, all progress depends on the unreasonable man. >> ,-._,-. >> \/)"(\/ >> (:o:) >> (!) >> >> On 03/14/13, Marvin Stodolsky<marvin.stodolsky@xxxxxxxxx> wrote: >> >> Roger >> >> I just realized that 3Comdm was compiled 32 bit. >> Thus likely that it will fail on your x86_64 system. >> However all it does is set setserial parameters, which can be done >> manually. >> >> Unfortunately I cannot advise you on how best to optimise with it. >> Read for guidance: >> $ man setserial >> >> MarvS >> >> On Thu, Mar 14, 2013 at 9:18 AM, Marvin Stodolsky >> <marvin.stodolsky@xxxxxxxxx> wrote: >> > Package attached >> > >> > MarvS >> > >> > On Thu, Mar 14, 2013 at 9:16 AM, Marvin Stodolsky >> > <marvin.stodolsky@xxxxxxxxx> wrote: >> >> Roger, >> >> >> >> I have unpacked and looked at the 3COM rpm support package. >> >> It is compirised of a script "serial" which sets up (if necessary) a >> >> /dev/ttyS3 port and then calls a binary/compiled >> >> /bin/3ComMdm >> >> which aspires to optimize setserial action. >> >> >> >> Whether these will serve you well, I cannot assess. >> >> However I will send serial & 3ComMdm to you. >> >> To use first: >> >> $ sudo cp 3ComMdm /bin/ >> >> $ sudo chmod +x /bin/3ComMdm >> >> >> >> With serial in your home folder just once: >> >> $ sudo chmod +x serial >> >> There after you can just >> >> $ sudo ./serial >> >> to run a test. This will call the 3ComMdm action. >> >> >> >> Next again try >> >> $ sudo wvdialconf >> >> >> >> Report back to the List. >> >> >> >> MarvS >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Mar 13, 2013 at 9:20 PM, Antonio Olivares >> >> <olivares14031@xxxxxxxxx> wrote: >> >>> Attention List: >> >>> >> >>> Anyone having a modem similar to Roger's? >> >>> If you do please advise Roger. >> >>> >> >>> Thanks, >> >>> >> >>> >> >>> Antonio >> >>> >> >>> >> >>> ---------- Forwarded message ---------- >> >>> From: Roger Davis <rogerdavis@xxxxxxxxxxx> >> >>> Date: Tue, Mar 12, 2013 at 12:30 AM >> >>> Subject: USR 5610c >> >>> To: olivares14031@xxxxxxxxx >> >>> >> >>> >> >>> I have been having BIG problems with my modem. It worked when I first >> >>> install 12.04 on this 64 bit machine, but after a few kernel updates >> >>> it quit. I've tried 10.04 on CD, early 12.04 on CD, and nothing will >> >>> wake it up again. I need it for fax in / fax out. >> >>> >> >>> This is all covered in a bug report, >> >>> (https://bugs.launchpad.net/bugs/1087519) , and recognized as >> >>> confirmed. BUT it is unassigned for a fix. >> >>> >> >>> Anyway, I saw your comment on a different USR modem >> >>> ">> scanModem reports that your modem would be supported but >> >>>>> under 32 bit >> >>>>> linux. You are using 64 bit linux which does not >> >>>>> support your modem." >> >>> I wonder if I have the same problem. >> >>> >> >>> This modem is said to be a full hardware modem ( >> >>> http://www.usr.com/products/modem/modem-product.asp?sku=USR5610c ), >> >>> but others argue that is not. >> >>> >> >>> This modem has a driver package from USR, but it's an RPM package, >> >>> and >> >>> I don't know if it works on a 64bit machine, or if I can even load >> >>> it. >> >>> >> >>> Thanks! >> >>> >> >>> >> >>> The reasonable man adapts himself to the world. >> >>> The unreasonable man persists in trying to adapt the world to >> >>> himself. >> >>> Therefore, all progress depends on the unreasonable man. >> >>> ,-._,-. >> >>> \/)"(\/ >> >>> (:o:) >> >>> (!) > >
