Yes yes yes, that's what I'm thinking about Mr. Jacques ! Thank you very much for your patient, that was exactly what I want to learn! Ok, this is what I done : 1. Commenting out the three lines at etc/rc.local 2. Reboot my computer 3. lsmod | grep snd-via82xx-modem --> noresults 4. modprobe snd-via82xx-modem --> done with no error 5. lsmod | grep snd-via82xx-modem --> still no results Why ?? Trying with underscore : lsmod | grep snd_via82xx_modem It gives result : snd_via82xx_modem 12644 0 snd_ac97_codec 84860 2 snd_via82xx_modem,snd_via82xx snd_pcm 79784 4 snd_via82xx_modem,snd_pcm_oss,snd_via82xx,snd_ac97_codec snd_page_alloc 8392 3 snd_via82xx_modem,snd_via82xx,snd_pcm snd 47492 15 snd_via82xx_modem,snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_os s,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,s nd_seq_device 6. Rebooting my computer 7. lsmod | grep snd_via82xx_modem Yes, it still there : snd_via82xx_modem 12644 0 snd_ac97_codec 84860 2 snd_via82xx_modem,snd_via82xx snd_pcm 79784 4 snd_via82xx_modem,snd_pcm_oss,snd_via82xx,snd_ac97_codec snd_page_alloc 8392 3 snd_via82xx_modem,snd_via82xx,snd_pcm snd 47492 15 snd_via82xx_modem,snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_os s,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,s nd_seq_device Now what I have to do ? Apparently there is no module snd-via82xx-modem ??? only snd with underscore snd_via82xx_modem. Now I'm more confusing than before. :-) Of course in this state the slmodemd gives an error attach hw:1 error : nosuch file or directory. Cheers, Jusuf -----Original Message----- From: Jacques Goldberg [mailto:Jacques.Goldberg@xxxxxxx] Sent: Thursday, January 11, 2007 3:48 PM To: Jusuf Cc: discuss@xxxxxxxxxxxxx Subject: Re: jfdesign, Indonesia Mandriva 2006.0 kernel 2.6.12-12mdk Jusuf, Could you please do ONLY the following. Disable the lines which you have placed in /etc/rc.local I suggest to just add # at the beginning of the lines, which will make them ineffective but not erase them. Verify that snd-via82xx-modem is present in memory with lsmod , and modprobe it if it is not present. Reboot the computer. Wait until reboot has finished and login. Check with lsmod if snd-via82xx-modem is in memory. Tell us the result. EXPLANATION: If snd-via82xx-modem is found after reboot, doing what I told you, then snd-via82xx-modem is loaded in the natural, recommended, way. And then the best way to automatically start slmodemd is by a script in /etc/init.d BUT A SCRIPT IN /etc/init.d IS NOT ENOUGH, you must also have something to start it at the run level at which you want to work. So you have to open your Control Center, find Task Management, and activate slmodemd . Of course, you have to do that only one time. If you prefer to do this by hand, just open /etc/rc5.d/ and add ln -s /etc/init.d/slmodemd S80slmodemd and slmodemd will start when you reach run level five (5) which is normal X11 operation. Am I right to guess that you did correctly install the slmodemd script but did not make it active? This is MUCH better than the rc.local technique which you have reached because if there is a bug anywhere and you play with rc.local, you may easily reach a situation where you cannot boot anymore. Indeed at the instant you boot you can request the option single to select which boot level you want to reach (and also, modify rc.local if necessary), so that you can prevent the boot to reach the place where the system hangs. This is why it is RECOMMENDED to use the rc.d chain to set up your system. Finally, if you want us to help you, when something did not work, report what you have done step by step and where it went wrong, rather than writing: "rather than editing the /etc/sysconfig/slmodemd or /etc/init.d/slmodemd because it didn't work." By the way, I have never seen anything like /etc/sysconfig/slmodemd. I believe it is an exotic way that SuSE has invented in order to make things differently from "standard". Jacques Jacques Jusuf wrote: > Hi Mr. Jacques Goldberg, > > No, Mr. Jacques, here is the story : > After succeeding turning on the modem with : slmodemd -c INDONESIA --alsa > modem:1 and tested perfectly with kppp, then I have to arrange so the > slmodem loaded each time after reboot, right ? > Then I choose to add this line at my /etc/rc.local file : > slmodemd -c INDONESIA --alsa modem:1 & > rather than editing the /etc/sysconfig/slmodemd or /etc/init.d/slmodemd > because it didn't work. > After adding that line, reboot my system, and try the modem with kppp it > brings an error cause kppp cannot find ttySL0. > I have to do this steps : > Modprobe -r snd-via82xx-modem > Modprobe snd-via82xx-modem > Then trying with kppp again, now it succeeded. > So I have to add this three lines of command to my etc/rc.local : > Modprobe -r snd-via82xx-modem > Modprobe snd-via82xx-modem > slmodemd -c INDONESIA --alsa modem:1 & > Now It works ! > > I know that is not usual, then I ask Mr. MarvS. :-) > > So, answering your question is a little bit confusing to me, before or after > resetting modprobing the snd-via82xx-modem module ? > If after resetting , yes the module was there, and the slmodem also work, > until restarting occur. > If before resetting, yes the module was there, but the slmodem won't work. > The point is the snd-via82xx-modem needs to be resetting after restart to > make slmodem to work. Is that usual ? > > Please advise Mr. Jacques .... > I'm really be thankful for your help. > > Cheers, > > Jusuf > > -----Original Message----- > From: Jacques Goldberg [mailto:Jacques.Goldberg@xxxxxxx] > Sent: Thursday, January 11, 2007 2:40 PM > To: Jusuf > Cc: DISCUSS@xxxxxxxxxxxxx > Subject: Re: jfdesign, Indonesia Mandriva 2006.0 kernel 2.6.12-12mdk > > Jusuf, > I do not understand. > Please do the following and tell me exactly where the problem is: > > 1-Type /sbin/lsmod . This shows the modules present in memory. Do > you see snd-via82xx-modem in the output? > You can save the long list by just typing /sbin/lsmod | grep modem > > 2-If it is not there, modprobe snd-via82xx-modem > > 3-Try to connect: start slmodemd as usual wvdial (kppp if you use kppp). > Success? > > 4-Reboot > > 5-Repeat #1 above . /sbin/lsmod | grep modem . Is the driver there? > > 6-Repeat #3. Success? Then I do not understand why you write: > "But why I have to : > > Modprobe -r snd-via82xx-modem > > Modprobe snd-via82xx-modem > > Each time after reboot, if doesn't the slmodemd cannot find the > device ???" > since obviously slmodemd DOES find the modem (module snd-via82xx-modem). > > Or are you asking why do you need to start slmodemd after each reboot > although snd-via82xx-modem is already in memory? > > It is trivial to start slmodemd automatically at boot if you do not care > for the resources (memory, cpu) which it takes when not in use. > > The file from which you started, SLMODEMD... , contains instructions and > example on how to do that (paragraph number 4 in file README). > > You can also start the modem connection automatically, by the same > method, if you do not care paying for the communication while you do not > use it. > > Jacques > > Jusuf wrote: >> Thank you Mr. MarvS. >> Now my second laptop's modem works too. :-) >> Using 2.6.12-12mdk good, upgrade to 2.6.17-5mdv also works perfectly. >> This is the aplay -l results : >> **** List of PLAYBACK Hardware Devices **** >> card 0: V8235 [VIA 8235], device 0: VIA 8235 [VIA 8235] >> Subdevices: 4/4 >> Subdevice #0: subdevice #0 >> Subdevice #1: subdevice #1 >> Subdevice #2: subdevice #2 >> Subdevice #3: subdevice #3 >> card 0: V8235 [VIA 8235], device 1: VIA 8235 [VIA 8235] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> card 1: modem [VIA 82XX modem], device 0: VIA 82XX modem [VIA 82XX modem] >> Subdevices: 0/1 >> Subdevice #0: subdevice #0 >> And the slmodemd command from SLMODEM.GCC4.tar.gz : >> Slmodemd -c INDONESIA --alsa modem:1 >> Will turned on the modem. >> >> But why I have to : >> Modprobe -r snd-via82xx-modem >> Modprobe snd-via82xx-modem >> Each time after reboot, if doesn't the slmodemd cannot find the device ??? >> >> But, thank you anyway Mr. MarvS. >> >> Cheers, >> >> >> jfdesign >> >> -----Original Message----- >> From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] >> Sent: Wednesday, January 10, 2007 8:43 PM >> To: Jusuf >> Cc: DISCUSS@xxxxxxxxxxxxx >> Subject: Re: jfdesign, Indonesia Mandriva 2006.0 kernel 2.6.12-12mdk >> >> Jusuf >> >> Class 0780: 1106:3068 Communication controller: VIA Technologies, >> Inc. AC'97 Modem Controller >> Primary PCI_id 1106:3068 >> Subsystem PCI_id 1558:5402 >> Softmodem codec or Vendor from diagnostics: MOT66, an AgereSystems > type. >> is NOT a Conexant chipset modem. Remove the hsfmodem software. >> Use: >> Download from http://linmodems.technion.ac.il/packages/smartlink/ >> the package SLMODEMD.gcc4.tar.gz having a compiled slmodemd. Unpack >> under Linux with: >> $ tar zxf SLMODEMD.gcc4.tar.gz >> and read instructions therein. But briefly, the modem is setup with >> command: >> slmodemd -c INDONESIA --alsa modem:1 >> reporting dynamic creation of ports: >> /dev/ttySL0 --> /dev/pts/N , with N some number >> Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance. >> >> MarvS >> >> On 1/10/07, Jusuf <jusuf@xxxxxxxxxxxx> wrote: >>> Mr. MarvS, >>> >>> Regardless to your pointer, I remove the slmodem driver including the >> dkms, >>> then d/l-ing hsfmodem from linuxant. >>> Installing the dkms-hsfmodem, run scanModem again, now my modem at >>> modemdata.txt change to MOT-66 ???? >>> Please advise ??? >>> >>> Thank you in advance Mr. MarvS. >>> >>> Cheers, >>> >>> >>> jfdesign >>> >>> ________________________________________ >>> From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] >>> Sent: Wednesday, January 10, 2007 10:55 AM >>> To: Jusuf >>> Cc: DISCUSS@xxxxxxxxxxxxx >>> Subject: Re: jfdesign, Indonesia Mandriva 2006.0 kernel 2.6.12-12mdk >>> >>> Jusuf >>> >>> The failure of the scanModem diagnostic: >>> For candidate modem in PCI bus: 00:11.6 >>> Class 0780: 1106:3068 Communication controller: VIA Technologies, Inc. >>> AC'97 Modem Controller >>> Primary PCI_id 1106:3068 >>> >>> Subsystem PCI_id 1558:5402 >>> Softmodem codec or Vendor from diagnostics: >>> ------------------ >>> is most likely the signature of a Conexant subsystem. Try an hsfmodem >>> package at >>> www.linuxant.com >>> for your >>> Mandriva Linux release 2006.0 (Official) for i586 >>> Kernel 2.6.12-12mdk on an i686 >>> >>> MarvS >>> >>> On 1/9/07, Jusuf <jusuf@xxxxxxxxxxxx> wrote: >>> Here is my other notebook modem. >>> >>> Thank you in advance, Mr. MarvS. >>> >>> Cheers, >>> >>> >>> jfdesign >>> >>> >>> >>> >>> >
