Fri, 12 Aug 2005 14:02:24 -0400 Moby First: # su - root # modprobe snd-intel8x0m Then # slmodemd --alsa -c GREECE hw:1 Should report port creation. If successful leave it running. Open a 2nd console # su - root # wvdialconf /etc/wvdial.conf and so forth as described in Testing.txt when you edit your personal info into /etc/wvdial.conf be sure to add the slmodemd neccessary support line: Carrier Check = no If your installation doesn't have wvdial try using KPPP, specifying /dev/ttySLO as the port during the kppp setup. Report back presently MarvS Original Message: ----------------- From: Moby Dick fishbone20002001@yahoo.com Date: Fri, 12 Aug 2005 06:38:34 -0700 (PDT) To: discuss@linmodems.org Subject: Re: Fwd: Re : scanModem, Mandrake Linux release 10.0 (Official) for i586/ Kernel 2.6.3-7mdk on an i686 / kernel 2.6.3-7mdk Dear Mr Stodolsky: I proceeded as you suggested, and got this far: I downloaded the slmodemd driver that you recommended and unzipped it, moving slmodemd to //bin. I then proceeded to execute the commands that are found in the text that accompanies the modem driver, but here I found a problem. Below is output from the linux bash console: [root@localhost bin]# slmodemd --alsa -c GREECE hw:1 & [1] 3143 [root@localhost bin]# error: mixer setup: attach hw:1 error: No such file or directory error: alsa setup: cannot open playback device 'hw:1': No such file or directory error: cannot setup device `hw:1' [1]+ Exit 255 slmodemd --alsa -c GREECE hw:1 [root@localhost bin]# slmodemd --alsa -c GREECE hw:1 error: mixer setup: attach hw:1 error: No such file or directory error: alsa setup: cannot open playback device 'hw:1': No such file or directory error: cannot setup device `hw:1' [root@localhost bin]# root@localhost bin]# ls arch* ex@ mail* sleep* awk@ false* mkdir* slmodemd* basename* fbmngplay.static* mknod* sort* ... env* ls* sh@ [root@localhost bin]# chmod +x slmodemd [root@localhost bin]# abcduser@localhost abcduser]$ cd //bin ... slmodemd --alsa GREECE dev/modem & Usage: slmodemd [option...] <device> Where 'device' is name of modem device (default `/dev/slamr0') and 'option' may be: -h, --help this usage -u, --usage this usage ... -d, --debug=VAL debug level (default `0') -l, --log=VAL logging mode (default `5') [3] 3639 [2] Exit 255 slmodemd --alsa dev/modem [3] Exit 1 slmodemd --alsa GREECE dev/modem [abcduser@localhost bin]$ Could you please advise me how to proceed? Thank you very much. Moby Dick --- "marvstod@comcast.net" <marvstod@comcast.net> wrote: > Moby, > > I'm the author of the Texts output by > scanModem,which have partially > contributed to your partially contributed to your > problems. Unfortunately, > they are rapidly outdated by dynamic Linux > developments, and I am only > prompted to improve them, when problems are caused, > as in your case. > > Here are briefest instructions to get you online. > 1) From > http://linmodems.technion.ac.il/packages/smartlink/ > download the package with an already compiled > slmodemd, the > slmodemd-2.9.9-pre1-alsa.tar.gz .Do Not confuse it > with > slmodem-2.9.9-pre1-alsa.tar.gz > Unpack with > # tar zxvf slmodemd-2.9.9-pre1-alsa.tar.gz > Read the enclosed directions. > These with the Testing.txt output by scanModem > should get you online for > under your > > Class 0703: 8086:2486 Modem: Intel Corp. > 82801CA/CAM AC'97 Modem > Controller (rev 02) (prog-if 00 [Generic]) > > SubSystem 134d:4c21 PCTel Inc Dell Inspiron > and 2.6.n kernel > > Should you want to do compiling, the 2.6.n > Mandiva/Mandrake kernel-source > packages are properly configured as installed. If > was the earlier 2.4.n > kernel-source packages which required the > configuration steps. > > MarvS > scanModem maintainer > > > > > > > Original Message: > ----------------- > From: Moby Dick fishbone20002001@yahoo.com > Date: Thu, 11 Aug 2005 23:10:46 -0700 (PDT) > To: discuss@linmodems.org > Subject: Re: Fwd: Re : scanModem, Mandrake Linux > release 10.0 (Official) > for i586/ Kernel 2.6.3-7mdk on an i686 / kernel > 2.6.3-7mdk > > > Dear Mr Goldberg (Jacques): > > I am very sorry for the inconvenience I have caused > you and the waste of your time. > > In what follows I reply directly to some of the > points > in your email, without however quoting the relevant > passages, so as not to tire you. > > I forwarded my original email (a standard reply > automatically addressed to you@cern) to you@technion > and that is what caused the mail to arrive as an > attachment. The reason I did the forward is that > the > Postmaster at Cern returned my reply to you as being > unable to resolve the domain. However the return > message gave me your forwarding address @technion, > which I used. Sorry. > > I am not stupid, I have some experience, but I am > completely confused by the various scanModem text > files instructing me what to do, and by the > websites, > for the simple reason that I lack experience with > Linux. I can at this point only follow simple > instructions what to type into the console. > > I am a poor author living in a remote part of > Greece. > My telephone number is +30 (23770) 23859. If you > wish > to phone please do. With daylight saving time, I am > GMT+3. > > Now to the substance. > > The 'other fellow responding to my scanModem send' > was > none other than Robert Thornburrow himself. Here is > the text of his message: > > Dear Mr Dick, > > ScanModem indicates you have an Intel AC'97 based > modem and that it > uses a PCTel Codec: > > > Class 0703: 8086:2486 Modem: Intel Corp. > 82801CA/CAM AC'97 Modem > Controller (rev 02) (prog-if 00 [Generic]) > > SubSystem 134d:4c21 PCTel Inc Dell Inspiron > 2100 internal modem > > The current PCTel driver for Linux does not support > kernel 2.6, however > the SmartLink driver (slamr / slmodem) should work > fine with this > modem. > > Best regards, > > Robert > > As you can see, Mr. Thornburrow didn't tell me to > use > the PCTEL modem. What happened was that I went to > the > scanModem output called DriverCompiling.txt and read > it, just as you yourself told me to. Here is the > passage that frightened me: > > HIGHLY IMPORTANT: the kernel-source as installed in > generally does NOT > represent your current kernel version, EVEN if the > kernel-version is the same. > Only one of several possible kernels was installed > on > your System, > and the unpacked kernel-source need NOT represent it > exactly!!! > For example, in the RedHat Distro there is a set of > kernel-configuration files within > /usr/src/linux/configs/ > Each is specialized for a different CPU (i586, i686, > K6, etc), > Yet each will be represented by the VERY SAME > version > name: "uname -r" . > !!!! Thus a PROPER CONFIGURATION MUST BE DONE by > You, > before compiling drivers !!!! > > This is where I got stuck and went to Mandriva for > assistance, since I was using their product. I > wanted > to find out how they viewed the problem of matching > the kernel source to the kernel. Given the > opportunity however, since they distribute the > version > of Linux I am using, I posed the question of the > modem > generally. The person I dealt with at Mandriva was > a > M. Christophe Potigny. He seems to say, if I > understand him correctly (you can see that I don't > understand much) that I don't have to do anything. > What also happened was that M. Potigny asked me why > I > didn't use the 2.4 kernel. Now I made the inference > that that was to be able to use the PCTEL modem, but > it seems that the slmodem works better with the 2.4 > kernel according to how M. Potigny and perhaps also > his colleagues read a website. > > Now, if in fact I should stay with the 2.6.7 kernel > and with the slmodem, that's fine with me. I just > don't have the technical experience with Linux to > make > a judgement by myself. > > However, the problem remains with the kernel-source > and the kernel. I did load all the tools, all the > extra modules listed, I did load the kernel source > from the Mandriva CD. However, the warning given > above has made me seek your advice what to do. > Should > I just go ahead and execute the various console > instructions that are given? Do I have to do > anything > to tailor the kernel-source to the kernel? What? > > Whom do I trust? Well, I am trying to communicate > with you and I hope you have the patience to give me > a > clear easy to follow procedure for installing the > Modem. As for compiling, I understand that I have > to > execute instructions that compile the Modem. But > before that, the kernel-source has to be matched to > the kernel. > > My referring to the Technion as saying something was > simply my literary style because I was too lazy to > dig > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ .