Dear Marvin This is how it went :- ____________________________________________ ankur@ankur:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:1b:38:a1:94:62 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:19 eth1 Link encap:Ethernet HWaddr 00:21:00:27:6c:dc inet6 addr: fe80::221:ff:fe27:6cdc/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:66 errors:0 dropped:0 overruns:0 frame:0 TX packets:66 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5910 (5.9 KB) TX bytes:5910 (5.9 KB) ankur@ankur:~$ sudo ifconfig eth0 down [sudo] password for ankur: ankur@ankur:~$ sudo ifconfig eth1 down ankur@ankur:~$ ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:74 errors:0 dropped:0 overruns:0 frame:0 TX packets:74 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6518 (6.5 KB) TX bytes:6518 (6.5 KB) ankur@ankur:~$ sudo wvdialconf wvtest Editing `wvtest'. Scanning your serial ports for a modem. Modem Port Scan<*1>: S0 S1 S2 S3 WvModem<*1>: Cannot get information for serial port. ttySL0<*1>: ATQ0 V1 E1 -- OK ttySL0<*1>: ATQ0 V1 E1 Z -- OK ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem ttySL0<*1>: Speed 4800: AT -- OK ttySL0<*1>: Speed 9600: AT -- OK ttySL0<*1>: Speed 19200: AT -- OK ttySL0<*1>: Speed 38400: AT -- OK ttySL0<*1>: Speed 57600: AT -- OK ttySL0<*1>: Speed 115200: AT -- OK ttySL0<*1>: Speed 230400: AT -- OK ttySL0<*1>: Speed 460800: AT -- OK ttySL0<*1>: Max speed is 460800; that should be safe. ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK Found a modem on /dev/ttySL0. Modem configuration written to wvtest. ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" ankur@ankur:~$ sudo slmodemd -c INDIA--alsa hw:0,6 error: mdm setup: cannot stat `hw:0,6': No such file or directory error: cannot setup device `hw:0,6' ankur@ankur:~$ sudo wvdialconf wvtestsudo slmodemd -c INDIA--alsa hw:0,6 wvdialconf: invalid option -- c Try `wvdialconf --help' or `wvdialconf --usage' for more information. ____________________________________________________________ sudo slmodemd -c INDIA--alsa hw:0,6 is still now working for me ... & the step you expected to fail ' sudo wvdialconf wvtest' , went on with all outputs as OK !!!! More suggestions / options plz ... Regards, Ankur Joshi On Sun, Sep 13, 2009 at 10:25 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > Ankur, > > Apologies, > > I forgot the --alas for > $ sudo slmodemd -c INDIA hw:0,6 > so it should be: > $ sudo slmodemd -c INDIA--alsa hw:0,6 > > Don't bother rurring the setup again. It will add nothing. Your > sequence should be: > $ sudo ifconfig eth0 down > $ sudo ifconfig eth1 down > > This is expected to fail, but it tests whether the modem has been > somehow setup on boot up: > $ sudo wvdialconf wvtest > > Assuming a failure of this wvdialconf > $ sudo slmodemd -c INDIA--alsa hw:0,6 > should now report port creartion: /dev/ttySL0 --> /dev/pts/N > > Assuming this success, the modem has been activated. If should now be found by: > $ sudo wvdialconf wvtest > > Assuming success, now try a dialout: > $ sudo wvdial > > MarvS > > > > On Sun, Sep 13, 2009 at 12:20 PM, Ankur Joshi <pharmankur@xxxxxxxxx> wrote: > > Marvin, > > > > I have tried everything still no success ... > > Now when i typed $ sudo slmodemd -c INDIA hw:0,6 > > once again it said > > 'error: mdm setup: cannot stat `hw:0,6': No such file or directory > > > > error: cannot setup device `hw:0,6' > > > > So I tried to install it again .. still nothing is working for me ... > > this is my complete output starting from ifconfig :- > > > > > > ankur@ankur:~$ ifconfig > > > > eth0 Link encap:Ethernet HWaddr 00:1b:38:a1:94:62 > > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > Interrupt:19 > > > > > > > > eth1 Link encap:Ethernet HWaddr 00:21:00:27:6c:dc > > > > inet6 addr: fe80::221:ff:fe27:6cdc/64 Scope:Link > > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > Interrupt:17 > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > inet6 addr: ::1/128 Scope:Host > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:76 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:0 > > > > RX bytes:6622 (6.6 KB) TX bytes:6622 (6.6 KB) > > > > > > > > ankur@ankur:~$ sudo ifconfig eth0 down > > > > [sudo] password for ankur: > > > > ankur@ankur:~$ sudo ifconfig eth1 down > > > > ankur@ankur:~$ ifconfig > > > > eth1 Link encap:Ethernet HWaddr 00:21:00:27:6c:dc > > > > inet6 addr: fe80::221:ff:fe27:6cdc/64 Scope:Link > > > > UP BROADCAST MULTICAST MTU:1500 Metric:1 > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > Interrupt:17 > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > inet6 addr: ::1/128 Scope:Host > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:84 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:0 > > > > RX bytes:7230 (7.2 KB) TX bytes:7230 (7.2 KB) > > > > > > > > ankur@ankur:~$ sudo ifconfig eth1 down > > > > ankur@ankur:~$ ifconfig > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > inet6 addr: ::1/128 Scope:Host > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:84 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:0 > > > > RX bytes:7230 (7.2 KB) TX bytes:7230 (7.2 KB) > > > > > > > > ankur@ankur:~$ sudo slmodemd -c INDIA hw:0,6 > > > > error: mdm setup: cannot stat `hw:0,6': No such file or directory > > > > error: cannot setup device `hw:0,6' > > > > ankur@ankur:~$ cd /Desktop/SLMODEMD.gcc4.3 > > > > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo ./setup > > > > > > > > There is already installed a slmodemd of version: 2.9.11 > > > > There is a file /usr/sbin/slmodemd > > > > Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11 > > > > Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and > > checking for version 2.9.11 > > > > SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > > > > Version verified: 2.9.11 > > > > > > > > With root permission, the typical activation command is: > > > > for modems hosted on High Definition Audio cards > > > > slmodemd -c USA --alsa hw:0,6 > > > > for modems of the AC'97 family > > > > slmodemd -c USA --alsa modem:1 > > > > for modems on ALI5451 sound cards > > > > slmodemd -c USA --alsa hw:0,1 > > > > for Smartlink chipset PCI card modems: > > > > slmodemd -c USA /dev/slamr0 > > > > for Smartlink chipset USB modems > > > > slmodemd -c USA /dev/slusb0 > > > > > > > > If not in the USA, replace USA with a country from the output of: > > > > slmodemd --countrylist > > > > For other slmodemd parameters, query with: > > > > slmodemd --help > > > > > > > > Report any problems to discuss@xxxxxxxxxxxxx > > > > > > > > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo slmodemd -c INDIA hw:0,6 > > > > error: mdm setup: cannot stat `hw:0,6': No such file or directory > > > > error: cannot setup device `hw:0,6' > > > > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ > > > > > > > > > > SO IS THIS THE END TO MY HOPES FOR INTERNET CONNECTION ??? > > > > Regards, > > Ankur Joshi > > > > > > > > On 9/12/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > >> Ankur, > >> > >> Typically there are but two steps for general modem use after bootup. > >> 1) activating the modem. For your System, this is the > >> $ sudo slmodemd -c INDIA hw:0,6 > >> > >> 2)With slmodemd left running, start a dialout with from another > >> console or 2nd window on the same console with: > >> $ sudo wvdial > >> > >> Your wvdial.conf file is now appropriate so that does not have do be > >> written again. > >> Best make a safety copy of this file with: > >> $ sudo cp /etc/wvdial.conf /etc/wvdial.conf.1 > >> > >> Whether the modem has been activated can be tested without overwriting > >> wvdialconf with: > >> $ sudo wvdialconf wvtest > >> which will write to wvtest rather than overwrite /etc/wvdial.conf. > >> On at least one boot up, there was an apparent slmodemd activation > >> automatically, > >> which we do not yet understand, and may be part of your problems. > >> > >> When you bootup again, please test slmodemd status by: > >> $ sudo wvdialconf wvtest > >> This will fail (as expected), if slmodemd is not yet active, but > >> should succeed after the step 1), > >> > >> Marvin > >> > >> > >> On Sat, Sep 12, 2009 at 2:18 AM, Ankur Joshi <pharmankur@xxxxxxxxx> wrote: > >>> Marvin, > >>> > >>> I was not knowing that it is necessary to do it every time. > >>> That's why i asked u about what is the procedure for connecting to the > >>> internet. > >>> I am totally new to linux world & even i do not understand the meaning > >>> of the commands u tell to me. > >>> > >>> So please explain to me the procedure considering i am a total dumbo!!! > >>> > >>> Anyway today I will try the thing u have suggested. 1st I will do, > >>> > >>> sudo ifconfig > >>> > >>> then will shutdown everything except lo > >>> > >>> then will do, > >>> > >>>> $ sudo slmodemd -c INDIA hw:0,6 > >>> > >>>> $ sudo wvdial > >>> > >>> & will hope that firefox will open Google page !!! > >>> > >>> Regards, > >>> Ankur Joshi > >>> > >>> > >>> > >>> On Sat, Sep 12, 2009 at 3:53 AM, Marvin Stodolsky > >>> <marvin.stodolsky@xxxxxxxxx> wrote: > >>>> Ankur, > >>>> > >>>> Before > >>>> $ sudo wvdial > >>>> > >>>> Did you: > >>>> $ sudo slmodemd -c INDIA hw:0,6 > >>>> > >>>> On Fri, Sep 11, 2009 at 4:43 AM, Ankur Joshi <pharmankur@xxxxxxxxx> > >>>> wrote: > >>>>> Dear Marvin / Antonio, > >>>>> > >>>>> Now my wvdial.conf looks like --> > >>>>> > >>>>> [Dialer Defaults] > >>>>> Init1 = ATZ > >>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS90 > >>>>> Modem Type = Analog Modem > >>>>> Baud = 460800 > >>>>> New PPPD = yes > >>>>> Modem = /dev/ttySL0 > >>>>> ISDN = 0 > >>>>> Phone = ******** > >>>>> Carrier Check = no > >>>>> Password = ************* > >>>>> Username = *********** > >>>>> > >>>>> __________________________________________________ > >>>>> > >>>>> THEN I DID IFCONFIG & GOT FOLLOWING ... > >>>>> > >>>>> etho & eth1 running with lo > >>>>> ________________________________________________________________________ > >>>>> > >>>>> > >>>>> I SHUT DOWN eth0 & eth1 by following --> > >>>>> > >>>>> $ sudo ifconfig eth0 down > >>>>> $ sudo ifconfig eth1 down > >>>>> > >>>>> _________________________________________________________________________ > >>>>> > >>>>> THEN AGAIN I DID > >>>>> > >>>>> $ sudo ifconfig > >>>>> lo Link encap:Local Loopback > >>>>> inet addr:127.0.0.1 Mask:255.0.0.0 > >>>>> inet6 addr: ::1/128 Scope:Host > >>>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 > >>>>> RX packets:77 errors:0 dropped:0 overruns:0 frame:0 > >>>>> TX packets:77 errors:0 dropped:0 overruns:0 carrier:0 > >>>>> collisions:0 txqueuelen:0 > >>>>> RX bytes:8072 (8.0 KB) TX bytes:8072 (8.0 KB) > >>>>> > >>>>> > >>>>> & ensured eth0 & eth1 are shut. > >>>>> > >>>>> ___________________________________________________________________________ > >>>>> > >>>>> After this i did sudo wvdial > >>>>> > >>>>> But it gave ERROR > >>>>> > >>>>> ALSO i tried with my Gnome PPP it showed Cannot open modem ... SO > >>>>> finally today i faced failure one again :) > >>>>> > >>>>> > >>>>> How exactly i am supposed to 'Connect' to the internet .... as in > >>>>> windows i go to internet connection dialer where my phone no, login, > >>>>> password is entered... then i just click 'connect' ... & it gets > >>>>> connected .... > >>>>> So what is the procedure to connect in UBUNTU ? ... I tried with Gnome > >>>>> PPP which looks much like windows dialer but has never worked for me > >>>>> till date ... > >>>>> > >>>>> > >>>>> Regards, > >>>>> Ankur Joshi > >>>>> > >>>>> > >>>>> On Thu, Sep 10, 2009 at 4:58 AM, Marvin Stodolsky > >>>>> <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> > >>>>>> Ankur, > >>>>>> > >>>>>> Before trying to dialout > >>>>>> $ ifconfig > >>>>>> any COMM channels except "lo" must be shut with commands like: > >>>>>> $ sudo ifconfig eth0 down > >>>>>> $ sudo ifconfig wlan0 down > >>>>>> before starting a dialout or DNS services for PPPD will fail > >>>>>> > >>>>>> MarvS > >>>>>> > >>>>>> On Wed, Sep 9, 2009 at 3:25 PM, Antonio > >>>>>> Olivares<olivares14031@xxxxxxxxx> wrote: > >>>>>> > Ankur, > >>>>>> > > >>>>>> > Remove the ";", and you might need to modify > >>>>>> > > >>>>>> > Init1 = ATZ > >>>>>> > Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS90 > >>>>>> > > >>>>>> > Try that and report back. > >>>>>> > > >>>>>> > Regards, > >>>>>> > > >>>>>> > Antonio > >>>>>> > > >>>>>> > On Wed, Sep 9, 2009 at 7:19 AM, Ankur Joshi <pharmankur@xxxxxxxxx> > >>>>>> > wrote: > >>>>>> >> Dear Marvin, > >>>>>> >> > >>>>>> >> This might be because I did that on my LAPTOP from my office where > >>>>>> >> my > >>>>>> >> broadband connection with my UBUNTU works fine. I never thought abt > >>>>>> >> any modem in office (I just plug in the LAN datacable & i get > >>>>>> >> connected) > >>>>>> >> > >>>>>> >> Problem is when i am at home i have only dialup access that i am > >>>>>> >> not > >>>>>> >> able to configure. > >>>>>> >> > >>>>>> >> So whatever you say to do, i do it in office ... then go home with > >>>>>> >> my > >>>>>> >> LAPTOP to see whether it worked ... & give u the feedback next day > >>>>>> >> from office. > >>>>>> >> > >>>>>> >> So in nutshell I have done following in my wvdial.conf --> > >>>>>> >> > >>>>>> >> Dialer Defaults] > >>>>>> >> Init1 = ATZ > >>>>>> >> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>>>>> >> Modem Type = Analog Modem > >>>>>> >> Baud = 460800 > >>>>>> >> New PPPD = yes > >>>>>> >> Modem = /dev/ttySL0 > >>>>>> >> ISDN = 0 > >>>>>> >> ; Phone = ********** > >>>>>> >> Carrier Check = no > >>>>>> >> ; Password = ********** > >>>>>> >> ; Username = ********* > >>>>>> >> > >>>>>> >> Note :- ***** represent the real data of my phone no. / pass / > >>>>>> >> username etc. AND i have removed < > from each entry. > >>>>>> >> > >>>>>> >> & in second tab now its showing --> > >>>>>> >> > >>>>>> >> ankur@ankur:~$ sudo wvdial > >>>>>> >> --> WvDial: Internet dialer version 1.60 > >>>>>> >> --> Cannot get information for serial port. > >>>>>> >> --> Initializing modem. > >>>>>> >> --> Sending: ATZ > >>>>>> >> ATZ > >>>>>> >> OK > >>>>>> >> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>>>>> >> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>>>>> >> OK > >>>>>> >> --> Modem initialized. > >>>>>> >> --> Configuration does not specify a valid phone number. > >>>>>> >> --> Configuration does not specify a valid login name. > >>>>>> >> --> Configuration does not specify a valid password. > >>>>>> >> > >>>>>> >> > >>>>>> >> Now is this thing will work when I am at home? > >>>>>> >> > >>>>>> >> At home now i will do sudo wvdial & i want the net to get > >>>>>> >> connected. > >>>>>> >> > >>>>>> >> If not happens will tell you ... plz don't mind !!! > >>>>>> >> > >>>>>> >> Regards, > >>>>>> >> Ankur Joshi > >>>>>> >> > >>>>>> >> > >>>>>> >> On Wed, Sep 9, 2009 at 3:36 AM, Marvin Stodolsky > >>>>>> >> <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> >>> > >>>>>> >>> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > >>>>>> >>> RE: Is this ok??? > >>>>>> >>> --------- > >>>>>> >>> Yes, though I don't under stand what has activated your modem > >>>>>> >>> during bootup. > >>>>>> >>> > >>>>>> >>> Please use wvdial, rather than gnome-ppp, which is just a front end > >>>>>> >>> to wvdial. > >>>>>> >>> You must edit with > >>>>>> >>> $ sudo gedit /etc/wvdia.conf > >>>>>> >>> adding a line: > >>>>>> >>> Carrier Check = no > >>>>>> >>> while removing the symbols ; < > > >>>>>> >>> > >>>>>> >>> Then with the modem still activated > >>>>>> >>> $ sudo wvdial > >>>>>> >>> > >>>>>> >>> Note that the configuation file for gnome-ppp is a hidder file in > >>>>>> >>> your > >>>>>> >>> Home folder, > >>>>>> >>> .wvdial.conf , and not the /etc/wvdial.conf used by wvdial. > >>>>>> >>> > >>>>>> >>> MarvS > >>>>>> >>> > >>>>>> >>> On Tue, Sep 8, 2009 at 8:20 AM, Ankur Joshi<pharmankur@xxxxxxxxx> > >>>>>> >>> wrote: > >>>>>> >>> > Dear MarvS, > >>>>>> >>> > > >>>>>> >>> > Done that !!! > >>>>>> >>> > See my outputs ... > >>>>>> >>> > ankur@ankur:~$ sudo slmodemd -c INDIA hw:0,6 > >>>>>> >>> > [sudo] password for ankur: > >>>>>> >>> > error: mdm setup: cannot stat `hw:0,6': No such file or > >>>>>> >>> > directory > >>>>>> >>> > error: cannot setup device `hw:0,6' > >>>>>> >>> > ankur@ankur:~$ > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > and in other tab --> > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > ankur@ankur:~$ sudo wvdialconf > >>>>>> >>> > [sudo] password for ankur: > >>>>>> >>> > Editing `/etc/wvdial.conf'. > >>>>>> >>> > > >>>>>> >>> > Scanning your serial ports for a modem. > >>>>>> >>> > > >>>>>> >>> > Modem Port Scan<*1>: S0 S1 S2 S3 > >>>>>> >>> > WvModem<*1>: Cannot get information for serial port. > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 -- OK > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 Z -- OK > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > >>>>>> >>> > ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem > >>>>>> >>> > ttySL0<*1>: Speed 4800: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 9600: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 19200: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 38400: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 57600: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 115200: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 230400: AT -- OK > >>>>>> >>> > ttySL0<*1>: Speed 460800: AT -- OK > >>>>>> >>> > ttySL0<*1>: Max speed is 460800; that should be safe. > >>>>>> >>> > ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK > >>>>>> >>> > > >>>>>> >>> > Found a modem on /dev/ttySL0. > >>>>>> >>> > Modem configuration written to /etc/wvdial.conf. > >>>>>> >>> > ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 > >>>>>> >>> > +FCLASS=0" > >>>>>> >>> > ankur@ankur:~$ > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > Is this ok??? > >>>>>> >>> > > >>>>>> >>> > But still when i open GNOME PPP & put my userneme & password & > >>>>>> >>> > dial up > >>>>>> >>> > phone no. AND click connect..... it says "Cannot open Modem" > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > Regards, > >>>>>> >>> > Ankur Joshi > >>>>>> >>> > > >>>>>> >>> > > >>>>>> >>> > On Tue, Sep 8, 2009 at 6:53 AM, Marvin Stodolsky > >>>>>> >>> > <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> >>> >> > >>>>>> >>> >> Ankur, > >>>>>> >>> >> > >>>>>> >>> >> Just try again. > >>>>>> >>> >> slmodemd was already activated by the setup I think > >>>>>> >>> >> > >>>>>> >>> >> After bootup, start with > >>>>>> >>> >> $ sudo slmodemd -c INDIA hw:0,6 > >>>>>> >>> >> leave it running > >>>>>> >>> >> > >>>>>> >>> >> Then open a 2nd console/TAB for the: > >>>>>> >>> >> $ sudo wvdialconf > >>>>>> >>> >> > >>>>>> >>> >> MarvS > >>>>>> >>> >> > >>>>>> >>> >> On Mon, Sep 7, 2009 at 9:57 AM, Ankur > >>>>>> >>> >> Joshi<pharmankur@xxxxxxxxx> wrote: > >>>>>> >>> >> > Marvin, > >>>>>> >>> >> > Its not happening dear ... following is my complete output. > >>>>>> >>> >> > Just check whether I am making any mistake, or there is some > >>>>>> >>> >> > error in > >>>>>> >>> >> > anything else --> > >>>>>> >>> >> > > >>>>>> >>> >> > > >>>>>> >>> >> > ankur@ankur:~$ sudo apt-get remove sl-modem-daemon > >>>>>> >>> >> > Reading package lists... Done > >>>>>> >>> >> > Building dependency tree > >>>>>> >>> >> > Reading state information... Done > >>>>>> >>> >> > Package sl-modem-daemon is not installed, so not removed > >>>>>> >>> >> > The following packages were automatically installed and are no > >>>>>> >>> >> > longer required: > >>>>>> >>> >> > libarts1c2a libartsc0 linux-headers-2.6.27-7 libmagick++10 > >>>>>> >>> >> > linux-headers-2.6.28-11 ttf-kannada-fonts > >>>>>> >>> >> > linux-headers-2.6.27-7-generic > >>>>>> >>> >> > kdebase-workspace-libs4+5 libaccess-bridge-java librasqal0 > >>>>>> >>> >> > python-serial > >>>>>> >>> >> > libx264-59 linux-headers-2.6.28-11-generic python-qt4-dbus > >>>>>> >>> >> > ttf-telugu-fonts > >>>>>> >>> >> > libpigment0.3-5 libtunepimp5 libpackagekit8 libdvdread3 > >>>>>> >>> >> > libffcall1 > >>>>>> >>> >> > thunderbird-locale-ja ttf-oriya-fonts gnustep-back-common > >>>>>> >>> >> > ttf-bengali-fonts > >>>>>> >>> >> > Use 'apt-get autoremove' to remove them. > >>>>>> >>> >> > 0 upgraded, 0 newly installed, 0 to remove and 0 not > >>>>>> >>> >> > upgraded. > >>>>>> >>> >> > ankur@ankur:~$ find /usr -name slmodemd > >>>>>> >>> >> > /usr/sbin/slmodemd > >>>>>> >>> >> > ankur@ankur:~$ cd Desktop/SLMODEMD.gcc4.3 > >>>>>> >>> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo ./setup > >>>>>> >>> >> > > >>>>>> >>> >> > There is already installed a slmodemd of version: > >>>>>> >>> >> > 2.9.11 > >>>>>> >>> >> > There is a file /usr/sbin/slmodemd > >>>>>> >>> >> > Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11 > >>>>>> >>> >> > Copying slmodemd to /usr/sbin/slmodemd, making exectuable, > >>>>>> >>> >> > and > >>>>>> >>> >> > checking for version 2.9.11 > >>>>>> >>> >> > SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > >>>>>> >>> >> > Version verified: 2.9.11 > >>>>>> >>> >> > > >>>>>> >>> >> > With root permission, the typical activation command is: > >>>>>> >>> >> > for modems hosted on High Definition Audio cards > >>>>>> >>> >> > slmodemd -c USA --alsa hw:0,6 > >>>>>> >>> >> > for modems of the AC'97 family > >>>>>> >>> >> > slmodemd -c USA --alsa modem:1 > >>>>>> >>> >> > for modems on ALI5451 sound cards > >>>>>> >>> >> > slmodemd -c USA --alsa hw:0,1 > >>>>>> >>> >> > for Smartlink chipset PCI card modems: > >>>>>> >>> >> > slmodemd -c USA /dev/slamr0 > >>>>>> >>> >> > for Smartlink chipset USB modems > >>>>>> >>> >> > slmodemd -c USA /dev/slusb0 > >>>>>> >>> >> > > >>>>>> >>> >> > If not in the USA, replace USA with a country from the output > >>>>>> >>> >> > of: > >>>>>> >>> >> > slmodemd --countrylist > >>>>>> >>> >> > For other slmodemd parameters, query with: > >>>>>> >>> >> > slmodemd --help > >>>>>> >>> >> > > >>>>>> >>> >> > Report any problems to discuss@xxxxxxxxxxxxx > >>>>>> >>> >> > > >>>>>> >>> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ slmodemd --version > >>>>>> >>> >> > SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > >>>>>> >>> >> > > >>>>>> >>> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo slmodemd -c INDIA > >>>>>> >>> >> > --alsa hw:0,6 > >>>>>> >>> >> > error: alsa setup: cannot open playback device 'hw:0,6': > >>>>>> >>> >> > Device or resource busy > >>>>>> >>> >> > error: cannot setup device `hw:0,6' > >>>>>> >>> >> > > >>>>>> >>> >> > ---- see still its giving error ... i dunno .. > >>>>>> >>> >> > > >>>>>> >>> >> > Regards, > >>>>>> >>> >> > Ankur Joshi > >>>>>> >>> >> > > >>>>>> >>> >> > > >>>>>> >>> >> > On Sat, Sep 5, 2009 at 9:03 PM, Marvin Stodolsky > >>>>>> >>> >> > <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> >>> >> >> > >>>>>> >>> >> >> Ankur, > >>>>>> >>> >> >> > >>>>>> >>> >> >> $ sudo slmodemd -c INDIA --alsa hw:0,6 > >>>>>> >>> >> >> Can now be done within your home folder > >>>>>> >>> >> >> After the successful > >>>>>> >>> >> >> > modem `hw:0,6' created. TTY is `/dev/pts/1' > >>>>>> >>> >> >> > >>>>>> >>> >> >> Run in a 2nd console without closing slmodemd > >>>>>> >>> >> >> $ sudo wvdialconf > >>>>>> >>> >> >> the modem should be found. This step does not have to be > >>>>>> >>> >> >> repeated upon reboot > >>>>>> >>> >> >> > >>>>>> >>> >> >> Now do the edit > >>>>>> >>> >> >> $ sudo gedit /etc/wvdial.conf > >>>>>> >>> >> >> This step does not have to be repeated. See the sample > >>>>>> >>> >> >> information in > >>>>>> >>> >> >> the wvdial.txt > >>>>>> >>> >> >> > >>>>>> >>> >> >> $ sudo wvdial > >>>>>> >>> >> >> should now find the modem at /dev/ttySL0 and start a > >>>>>> >>> >> >> dialout > >>>>>> >>> >> >> > >>>>>> >>> >> >> If in doubt, send us your wvdial.conf > >>>>>> >>> >> >> first replacing your PASSWORD with XXXX > >>>>>> >>> >> >> > >>>>>> >>> >> >> MarvS > >>>>>> >>> >> >> > >>>>>> >>> >> >> On Sat, Sep 5, 2009 at 12:04 AM, Ankur > >>>>>> >>> >> >> Joshi<pharmankur@xxxxxxxxx> wrote: > >>>>>> >>> >> >> > Marvin > >>>>>> >>> >> >> > Sorry I forgot to add following output in my earlier mail > >>>>>> >>> >> >> > ... > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo slmodemd -c > >>>>>> >>> >> >> > INDIA --alsa hw:0,6 > >>>>>> >>> >> >> > SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > >>>>>> >>> >> >> c > >>>>>> >>> >> >> > modem `hw:0,6' created. TTY is `/dev/pts/1' > >>>>>> >>> >> >> > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > >>>>>> >>> >> >> > ^Cankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo gedit > >>>>>> >>> >> >> > /etc/wvdial.conf > >>>>>> >>> >> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo wvdial > >>>>>> >>> >> >> > --> WvDial: Internet dialer version 1.60 > >>>>>> >>> >> >> > --> Cannot open /dev/modem: No such file or directory > >>>>>> >>> >> >> > --> Cannot open /dev/modem: No such file or directory > >>>>>> >>> >> >> > --> Cannot open /dev/modem: No such file or directory > >>>>>> >>> >> >> > ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > & I ensured to add the extra line in /etc/wvdial.conf > >>>>>> >>> >> >> > Carrier Check = no > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > Still i am not figuring out how exactly to connect to my > >>>>>> >>> >> >> > internet. > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > Regards, > >>>>>> >>> >> >> > Ankur Joshi > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > > >>>>>> >>> >> >> > On Sat, Sep 5, 2009 at 12:12 PM, Ankur > >>>>>> >>> >> >> > Joshi<pharmankur@xxxxxxxxx> wrote: > >>>>>> >>> >> >> >> Marvin, > >>>>>> >>> >> >> >> As you have suggested I did the thing & got following > >>>>>> >>> >> >> >> output :- > >>>>>> >>> >> >> >> ---------------------------------------------------------------------------------------------------------------------------------- > >>>>>> >>> >> >> >> ankur@ankur:~$ find /usr -name slmodemd > >>>>>> >>> >> >> >> ankur@ankur:~$ slmodemd --version > >>>>>> >>> >> >> >> The program 'slmodemd' is currently not installed. You > >>>>>> >>> >> >> >> can install it > >>>>>> >>> >> >> >> by typing: > >>>>>> >>> >> >> >> sudo apt-get install sl-modem-daemon > >>>>>> >>> >> >> >> bash: slmodemd: command not found > >>>>>> >>> >> >> >> ankur@ankur:~$ cd /home/ankur/Desktop/SLMODEMD.gcc4.3 > >>>>>> >>> >> >> >> ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ sudo ./setup > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> ./setup: 4: slmodemd: not found > >>>>>> >>> >> >> >> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, > >>>>>> >>> >> >> >> and > >>>>>> >>> >> >> >> checking for version 2.9.11 > >>>>>> >>> >> >> >> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > >>>>>> >>> >> >> >> Version verified: 2.9.11 > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> With root permission, the typical activation command is: > >>>>>> >>> >> >> >> for modems hosted on High Definition Audio cards > >>>>>> >>> >> >> >> slmodemd -c USA --alsa hw:0,6 > >>>>>> >>> >> >> >> for modems of the AC'97 family > >>>>>> >>> >> >> >> slmodemd -c USA --alsa modem:1 > >>>>>> >>> >> >> >> for modems on ALI5451 sound cards > >>>>>> >>> >> >> >> slmodemd -c USA --alsa hw:0,1 > >>>>>> >>> >> >> >> for Smartlink chipset PCI card modems: > >>>>>> >>> >> >> >> slmodemd -c USA /dev/slamr0 > >>>>>> >>> >> >> >> for Smartlink chipset USB modems > >>>>>> >>> >> >> >> slmodemd -c USA /dev/slusb0 > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> If not in the USA, replace USA with a country from the > >>>>>> >>> >> >> >> output of: > >>>>>> >>> >> >> >> slmodemd --countrylist > >>>>>> >>> >> >> >> For other slmodemd parameters, query with: > >>>>>> >>> >> >> >> slmodemd --help > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> Report any problems to discuss@xxxxxxxxxxxxx > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ slmodemd --version > >>>>>> >>> >> >> >> SmartLink Soft Modem: version 2.9.11 Aug 3 2008 22:31:06 > >>>>>> >>> >> >> >> ankur@ankur:~/Desktop/SLMODEMD.gcc4.3$ > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> -------------------------------------------------------------------------------------------------------------- > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> Now whats next step ??? > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> Regards, > >>>>>> >>> >> >> >> Ankur Joshi > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> >> On Fri, Sep 4, 2009 at 8:55 PM, Marvin Stodolsky > >>>>>> >>> >> >> >> <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> Ankur, > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> If you have installed the sl-modem-daemon package, > >>>>>> >>> >> >> >>> uninstall it because it is useless for the snd-hda-intel > >>>>>> >>> >> >> >>> case and may > >>>>>> >>> >> >> >>> interfere. Uninstall with: > >>>>>> >>> >> >> >>> $ sudo apt-get remove sl-modem-daemon > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> Then run > >>>>>> >>> >> >> >>> $ find /usr -name slmodemd > >>>>>> >>> >> >> >>> which will locate the slmodemd . This is usually at > >>>>>> >>> >> >> >>> /usr/sbin/slmodemd > >>>>>> >>> >> >> >>> If > >>>>>> >>> >> >> >>> $ slmodemd --version > >>>>>> >>> >> >> >>> reports version 2.9.11, all is OK. if not rerun the > >>>>>> >>> >> >> >>> slmodemd install > >>>>>> >>> >> >> >>> from the SLMODEMD.gcc4.3.tar.gz > >>>>>> >>> >> >> >>> Afterwards again check > >>>>>> >>> >> >> >>> $ slmodemd --version > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> MarvS > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> > >>>>>> >>> >> >> >>> On Thu, Sep 3, 2009 at 10:31 PM, Ankur > >>>>>> >>> >> >> >>> Joshi<pharmankur@xxxxxxxxx> wrote: > >>>>>> >>> >> >> >>> > Thanks for yor replies. > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > but when i try your steps following thing occurs:- > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > ankur@ankur:~/Desktop$ tar zxf SLMODEMD.gcc4.3.tar.gz > >>>>>> >>> >> >> >>> > ankur@ankur:~/Desktop$ sudo slmodemd -c INDIA --alsa > >>>>>> >>> >> >> >>> > hw:0,6 > >>>>>> >>> >> >> >>> > [sudo] password for ankur: > >>>>>> >>> >> >> >>> > error: alsa setup: cannot open playback device > >>>>>> >>> >> >> >>> > 'hw:0,6': Device or resource > >>>>>> >>> >> >> >>> > busy > >>>>>> >>> >> >> >>> > error: cannot setup device `hw:0,6' > >>>>>> >>> >> >> >>> > ankur@ankur:~/Desktop$ > >>>>>> >>> >> >> >>> > ankur@ankur:~/Desktop$ > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > Note :- I have tried a no. of times for installing the > >>>>>> >>> >> >> >>> > modem ... is it > >>>>>> >>> >> >> >>> > because of such attempts create some 'Debris' & give me > >>>>>> >>> >> >> >>> > the error ..? if so > >>>>>> >>> >> >> >>> > plz tell me how to clear the Debris of my previous > >>>>>> >>> >> >> >>> > failed attempts... > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > and oh yes ... thanks again for your help. > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > Regards, > >>>>>> >>> >> >> >>> > Ankur Joshi > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > On Fri, Sep 4, 2009 at 12:51 AM, Marvin Stodolsky > >>>>>> >>> >> >> >>> > <marvin.stodolsky@xxxxxxxxx> wrote: > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Pablo, > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Try to get the tarball made of the functioning > >>>>>> >>> >> >> >>> >> kernel+plus modules, so > >>>>>> >>> >> >> >>> >> I can package it for others > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> List, > >>>>>> >>> >> >> >>> >> Does anyone have a modem success using the > >>>>>> >>> >> >> >>> >> snd-hda-intel driver > >>>>>> >>> >> >> >>> >> under ANY 2.6.28 kernel?? If so, what Distro and > >>>>>> >>> >> >> >>> >> kernel? > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Ankur, > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> RE responses. > >>>>>> >>> >> >> >>> >> Please be carefull to send in plain text or your > >>>>>> >>> >> >> >>> >> emails are rejected > >>>>>> >>> >> >> >>> >> by the List server. > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Re modem failures. Use for activation: > >>>>>> >>> >> >> >>> >> $ sudo slmodemd -c INDIA --alsa hw:0,6 > >>>>>> >>> >> >> >>> >> and then > >>>>>> >>> >> >> >>> >> $ sudo wvdial > >>>>>> >>> >> >> >>> >> should in principle result in a dialout, provided > >>>>>> >>> >> >> >>> >> that > >>>>>> >>> >> >> >>> >> /etc/wvdial.conf has been properly written It should > >>>>>> >>> >> >> >>> >> contain an added > >>>>>> >>> >> >> >>> >> line: > >>>>>> >>> >> >> >>> >> Carrier Check = no > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> However all that being well, there is evidence that > >>>>>> >>> >> >> >>> >> there is a problem > >>>>>> >>> >> >> >>> >> with snd-hda-intel modem support under 2.6.28 kernels, > >>>>>> >>> >> >> >>> >> seee below, and > >>>>>> >>> >> >> >>> >> we are trying to figure this situation out. > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> If failures continue under your 2.6.28 kernel, it > >>>>>> >>> >> >> >>> >> might be simplest to > >>>>>> >>> >> >> >>> >> install a 2.6.27 kernel of the Intepid series. > >>>>>> >>> >> >> >>> >> Instructions are in: > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg01316.html > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> MarvS > >>>>>> >>> >> >> >>> >> ------------------------ > >>>>>> >>> >> >> >>> >> from Pablo Marcondes <pablo.mmarcondes@xxxxxxxxx> > >>>>>> >>> >> >> >>> >> to Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> > >>>>>> >>> >> >> >>> >> cc David Monniaux <David.Monniaux@xxxxxxx>, > >>>>>> >>> >> >> >>> >> discuss@xxxxxxxxxxxxx > >>>>>> >>> >> >> >>> >> date Tue, Aug 18, 2009 at 5:30 PM > >>>>>> >>> >> >> >>> >> subject Re: problems with HP Pavilion tx1219us > >>>>>> >>> >> >> >>> >> (Si3054) > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> None, I think theres something with the kernel > >>>>>> >>> >> >> >>> >> itself. > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Ive tested with a self compiled kernel 2.6.28-10-686 > >>>>>> >>> >> >> >>> >> and it works, but > >>>>>> >>> >> >> >>> >> not with 2.6.28-11-generic from jaunty. > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> And Im in need of this modem working with jaunty too, > >>>>>> >>> >> >> >>> >> If I got any > >>>>>> >>> >> >> >>> >> success I will let you know. > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> Thanks, > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> > >>>>>> >>> >> >> >>> >> On Thu, Sep 3, 2009 at 8:00 AM, Antonio > >>>>>> >>> >> >> >>> >> Olivares<olivares14031@xxxxxxxxx> > >>>>>> >>> >> >> >>> >> wrote: > >>>>>> >>> >> >> >>> >> > Ankur, > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > scanModem reports that your modem is supported by > >>>>>> >>> >> >> >>> >> > SLMODEMD.gcc4.3.tar.gz: > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > For candidate modem in: 00:1b.0 > >>>>>> >>> >> >> >>> >> > 0403 Audio device: Intel Corporation 82801H > >>>>>> >>> >> >> >>> >> > Primary device ID: 8086:284b > >>>>>> >>> >> >> >>> >> > Subsystem PCI_id 17aa:384e > >>>>>> >>> >> >> >>> >> > Softmodem codec or chipset from diagnostics: > >>>>>> >>> >> >> >>> >> > 0x10573055 > >>>>>> >>> >> >> >>> >> > from Archives: > >>>>>> >>> >> >> >>> >> > The HDA card softmodem chip > >>>>>> >>> >> >> >>> >> > is 0x10573055 > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Support type needed or chipset: slmodemd > >>>>>> >>> >> >> >>> >> > supporting the > >>>>>> >>> >> >> >>> >> > snd-hda-intel audio+modem driver > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > An ALSA (Advanced Linux Sound Architecture) modem > >>>>>> >>> >> >> >>> >> > driver: > >>>>>> >>> >> >> >>> >> > snd-hda-intel > >>>>>> >>> >> >> >>> >> > provides Low Level support enabling contact with > >>>>>> >>> >> >> >>> >> > the modem hardware. > >>>>>> >>> >> >> >>> >> > For all BUT Conexant chip soft modems (using > >>>>>> >>> >> >> >>> >> > hsfmodem software) > >>>>>> >>> >> >> >>> >> > complementary High Level support is through a > >>>>>> >>> >> >> >>> >> > Smartlink utility: > >>>>>> >>> >> >> >>> >> > slmodemd > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Download from > >>>>>> >>> >> >> >>> >> > http://linmodems.technion.ac.il/packages/smartlink/ > >>>>>> >>> >> >> >>> >> > the package SLMODEMD.gcc4.3.tar.gz having a > >>>>>> >>> >> >> >>> >> > compiled slmodemd. Unpack > >>>>>> >>> >> >> >>> >> > under Linux with: > >>>>>> >>> >> >> >>> >> > $ tar zxf SLMODEMD.gcc4.3.tar.gz > >>>>>> >>> >> >> >>> >> > and read instructions therein. But briefly, the > >>>>>> >>> >> >> >>> >> > modem is setup with > >>>>>> >>> >> >> >>> >> > command: > >>>>>> >>> >> >> >>> >> > $ sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6 > >>>>>> >>> >> >> >>> >> > reporting dynamic creation of ports: > >>>>>> >>> >> >> >>> >> > /dev/ttySL0 --> /dev/pts/N , with N some > >>>>>> >>> >> >> >>> >> > number > >>>>>> >>> >> >> >>> >> > Read DOCs/Smartlink.txt and > >>>>>> >>> >> >> >>> >> > Modem/DOCs/YourSystem.txt for follow > >>>>>> >>> >> >> >>> >> > through guidance. > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Have you tried the SLMODEMD.gcc4.3.tar.gz and the > >>>>>> >>> >> >> >>> >> > slmodemd contained > >>>>>> >>> >> >> >>> >> > in it? If you have, have you addressed the IRQ > >>>>>> >>> >> >> >>> >> > issue:? > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > For candidate card in slot 00:1b.0, firmware > >>>>>> >>> >> >> >>> >> > information and bootup > >>>>>> >>> >> >> >>> >> > diagnostics are: > >>>>>> >>> >> >> >>> >> > PCI slot PCI ID SubsystemID Name > >>>>>> >>> >> >> >>> >> > ---------- --------- --------- > >>>>>> >>> >> >> >>> >> > -------------- > >>>>>> >>> >> >> >>> >> > 00:1b.0 8086:284b 17aa:384e Audio device: > >>>>>> >>> >> >> >>> >> > Intel Corporation > >>>>>> >>> >> >> >>> >> > 82801H > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Modem interrupt assignment and sharing: > >>>>>> >>> >> >> >>> >> > 22: 756 750 IO-APIC-fasteoi HDA > >>>>>> >>> >> >> >>> >> > Intel > >>>>>> >>> >> >> >>> >> > --- Bootup diagnostics for card in PCI slot 00:1b.0 > >>>>>> >>> >> >> >>> >> > ---- > >>>>>> >>> >> >> >>> >> > [ 0.533455] pci 0000:00:1b.0: reg 10 64bit mmio: > >>>>>> >>> >> >> >>> >> > [0xf8200000-0xf8203fff] > >>>>>> >>> >> >> >>> >> > [ 0.533503] pci 0000:00:1b.0: PME# supported from > >>>>>> >>> >> >> >>> >> > D0 D3hot D3cold > >>>>>> >>> >> >> >>> >> > [ 0.533509] pci 0000:00:1b.0: PME# disabled > >>>>>> >>> >> >> >>> >> > [ 13.316811] HDA Intel 0000:00:1b.0: PCI INT A -> > >>>>>> >>> >> >> >>> >> > GSI 22 (level, > >>>>>> >>> >> >> >>> >> > low) -> IRQ 22 > >>>>>> >>> >> >> >>> >> > [ 13.316973] HDA Intel 0000:00:1b.0: setting > >>>>>> >>> >> >> >>> >> > latency timer to 64 > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > The PCI slot 00:1b.0 of the modem card may be > >>>>>> >>> >> >> >>> >> > disabled early in > >>>>>> >>> >> >> >>> >> > a bootup process, but then enabled later. If modem > >>>>>> >>> >> >> >>> >> > drivers load > >>>>>> >>> >> >> >>> >> > but the modem is not responsive, read > >>>>>> >>> >> >> >>> >> > DOCs/Bootup.txt about possible > >>>>>> >>> >> >> >>> >> > fixes. > >>>>>> >>> >> >> >>> >> > Send dmesg.txt along with ModemData.txt to > >>>>>> >>> >> >> >>> >> > discuss@xxxxxxxxxxxxx > >>>>>> >>> >> >> >>> >> > if help is needed. > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Other than above advice, we need more information in > >>>>>> >>> >> >> >>> >> > order to try to > >>>>>> >>> >> >> >>> >> > help you. > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Regards, > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > Antonio > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> >> > On Thu, Sep 3, 2009 at 2:08 AM, Ankur > >>>>>> >>> >> >> >>> >> > Joshi<pharmankur@xxxxxxxxx> wrote: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Hi, > >>>>>> >>> >> >> >>> >> >> Following is my modemdata.txt file output. Pls help > >>>>>> >>> >> >> >>> >> >> me in insatlling > >>>>>> >>> >> >> >>> >> >> modem > >>>>>> >>> >> >> >>> >> >> drivers & setup dialup internet connection. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> NOTE :- this is my 5th mail to you & till date > >>>>>> >>> >> >> >>> >> >> whatever you have > >>>>>> >>> >> >> >>> >> >> suggested > >>>>>> >>> >> >> >>> >> >> have never worked. AND more bad is I did not > >>>>>> >>> >> >> >>> >> >> received prompt replies > >>>>>> >>> >> >> >>> >> >> from u. > >>>>>> >>> >> >> >>> >> >> PLZ help me this time at least ... > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Only plain text email is forwarded by the > >>>>>> >>> >> >> >>> >> >> Discuss@xxxxxxxxxxxxx List > >>>>>> >>> >> >> >>> >> >> Server, > >>>>>> >>> >> >> >>> >> >> as HTML can contain viruses. Use as the email > >>>>>> >>> >> >> >>> >> >> Subject Line: > >>>>>> >>> >> >> >>> >> >> YourName, YourCountry kernel > >>>>>> >>> >> >> >>> >> >> 2.6.28-15-generic > >>>>>> >>> >> >> >>> >> >> With this Subject Line cogent experts will be > >>>>>> >>> >> >> >>> >> >> alerted, and useful case > >>>>>> >>> >> >> >>> >> >> names left in the Archive. > >>>>>> >>> >> >> >>> >> >> YourCountry will enable Country specific guidance. > >>>>>> >>> >> >> >>> >> >> Linux experts in > >>>>>> >>> >> >> >>> >> >> YourCountry > >>>>>> >>> >> >> >>> >> >> can be found through: > >>>>>> >>> >> >> >>> >> >> http://www.linux.org/groups/index.html. > >>>>>> >>> >> >> >>> >> >> They will know your Country's modem code, which may > >>>>>> >>> >> >> >>> >> >> be essential for > >>>>>> >>> >> >> >>> >> >> dialup > >>>>>> >>> >> >> >>> >> >> service. > >>>>>> >>> >> >> >>> >> >> Responses from Discuss@xxxxxxxxxxxxx are sometimes > >>>>>> >>> >> >> >>> >> >> blocked by an > >>>>>> >>> >> >> >>> >> >> Internet > >>>>>> >>> >> >> >>> >> >> Provider mail filters. > >>>>>> >>> >> >> >>> >> >> So in a day, also check the Archived responses at > >>>>>> >>> >> >> >>> >> >> http://www.linmodems.org > >>>>>> >>> >> >> >>> >> >> -------------------------- System information > >>>>>> >>> >> >> >>> >> >> ---------------------------- > >>>>>> >>> >> >> >>> >> >> CPU=i686, > >>>>>> >>> >> >> >>> >> >> Linux version 2.6.28-15-generic (buildd@palmer) > >>>>>> >>> >> >> >>> >> >> (gcc version 4.3.3 > >>>>>> >>> >> >> >>> >> >> (Ubuntu > >>>>>> >>> >> >> >>> >> >> 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 > >>>>>> >>> >> >> >>> >> >> 18:40:08 UTC 2009 > >>>>>> >>> >> >> >>> >> >> scanModem update of: 2009_08_15 > >>>>>> >>> >> >> >>> >> >> The modem symbolic link is /dev/modem -> ttySL0 > >>>>>> >>> >> >> >>> >> >> The slmodemd set symbolic link is /dev/ttySL0 -> > >>>>>> >>> >> >> >>> >> >> /dev/pts/0 > >>>>>> >>> >> >> >>> >> >> There are no blacklisted modem drivers in > >>>>>> >>> >> >> >>> >> >> /etc/modprobe* files > >>>>>> >>> >> >> >>> >> >> Potentially useful modem drivers now loaded are: > >>>>>> >>> >> >> >>> >> >> snd_hda_intel > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Attached USB devices are: > >>>>>> >>> >> >> >>> >> >> ID 04f3:0217 Elan Microelectronics Corp. > >>>>>> >>> >> >> >>> >> >> ID 0bda:0158 Realtek Semiconductor Corp. Mass > >>>>>> >>> >> >> >>> >> >> Stroage Device > >>>>>> >>> >> >> >>> >> >> ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 > >>>>>> >>> >> >> >>> >> >> Bluetooth > >>>>>> >>> >> >> >>> >> >> If a cellphone is not detected, see > >>>>>> >>> >> >> >>> >> >> http://ubuntuforums.org/archive/index.php/t-878554.html > >>>>>> >>> >> >> >>> >> >> A sample report is: > >>>>>> >>> >> >> >>> >> >> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> If a USB modem or cellphone is attached and was not > >>>>>> >>> >> >> >>> >> >> detected, please > >>>>>> >>> >> >> >>> >> >> provide available information in your request to > >>>>>> >>> >> >> >>> >> >> discuss@xxxxxxxxxxxxx > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> For candidate card in slot 00:1b.0, firmware > >>>>>> >>> >> >> >>> >> >> information and bootup > >>>>>> >>> >> >> >>> >> >> diagnostics are: > >>>>>> >>> >> >> >>> >> >> PCI slot PCI ID SubsystemID Name > >>>>>> >>> >> >> >>> >> >> ---------- --------- --------- > >>>>>> >>> >> >> >>> >> >> -------------- > >>>>>> >>> >> >> >>> >> >> 00:1b.0 8086:284b 17aa:384e Audio device: > >>>>>> >>> >> >> >>> >> >> Intel Corporation > >>>>>> >>> >> >> >>> >> >> 82801H > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Modem interrupt assignment and sharing: > >>>>>> >>> >> >> >>> >> >> 22: 756 750 IO-APIC-fasteoi HDA > >>>>>> >>> >> >> >>> >> >> Intel > >>>>>> >>> >> >> >>> >> >> --- Bootup diagnostics for card in PCI slot > >>>>>> >>> >> >> >>> >> >> 00:1b.0 ---- > >>>>>> >>> >> >> >>> >> >> [ 0.533455] pci 0000:00:1b.0: reg 10 64bit > >>>>>> >>> >> >> >>> >> >> mmio: > >>>>>> >>> >> >> >>> >> >> [0xf8200000-0xf8203fff] > >>>>>> >>> >> >> >>> >> >> [ 0.533503] pci 0000:00:1b.0: PME# supported > >>>>>> >>> >> >> >>> >> >> from D0 D3hot D3cold > >>>>>> >>> >> >> >>> >> >> [ 0.533509] pci 0000:00:1b.0: PME# disabled > >>>>>> >>> >> >> >>> >> >> [ 13.316811] HDA Intel 0000:00:1b.0: PCI INT A -> > >>>>>> >>> >> >> >>> >> >> GSI 22 (level, low) > >>>>>> >>> >> >> >>> >> >> -> > >>>>>> >>> >> >> >>> >> >> IRQ 22 > >>>>>> >>> >> >> >>> >> >> [ 13.316973] HDA Intel 0000:00:1b.0: setting > >>>>>> >>> >> >> >>> >> >> latency timer to 64 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The PCI slot 00:1b.0 of the modem card may be > >>>>>> >>> >> >> >>> >> >> disabled early in > >>>>>> >>> >> >> >>> >> >> a bootup process, but then enabled later. If > >>>>>> >>> >> >> >>> >> >> modem drivers load > >>>>>> >>> >> >> >>> >> >> but the modem is not responsive, read > >>>>>> >>> >> >> >>> >> >> DOCs/Bootup.txt about possible > >>>>>> >>> >> >> >>> >> >> fixes. > >>>>>> >>> >> >> >>> >> >> Send dmesg.txt along with ModemData.txt to > >>>>>> >>> >> >> >>> >> >> discuss@xxxxxxxxxxxxx > >>>>>> >>> >> >> >>> >> >> if help is needed. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> ===== Advanced Linux Sound Architecture (ALSA) > >>>>>> >>> >> >> >>> >> >> diagnostics ===== > >>>>>> >>> >> >> >>> >> >> The ALSA packages provide audio support and also > >>>>>> >>> >> >> >>> >> >> drivers for some > >>>>>> >>> >> >> >>> >> >> modems. > >>>>>> >>> >> >> >>> >> >> ALSA diagnostics are written during bootup to > >>>>>> >>> >> >> >>> >> >> /proc/asound/ folders. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The ALSA verion is 1.0.18 > >>>>>> >>> >> >> >>> >> >> The modem cards detected by "aplay -l" are: > >>>>>> >>> >> >> >>> >> >> card 0: Intel [HDA Intel], device 6: Si3054 Modem > >>>>>> >>> >> >> >>> >> >> [Si3054 Modem] > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The /proc/asound/pcm file reports: > >>>>>> >>> >> >> >>> >> >> ----------------------- > >>>>>> >>> >> >> >>> >> >> 00-00: ALC861VD Analog : ALC861VD Analog : playback > >>>>>> >>> >> >> >>> >> >> 1 : capture 1 > >>>>>> >>> >> >> >>> >> >> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : > >>>>>> >>> >> >> >>> >> >> capture 1 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> about /proc/asound/cards: > >>>>>> >>> >> >> >>> >> >> ------------------------ > >>>>>> >>> >> >> >>> >> >> 0 [Intel ]: HDA-Intel - HDA Intel > >>>>>> >>> >> >> >>> >> >> HDA Intel at 0xf8200000 irq > >>>>>> >>> >> >> >>> >> >> 22 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> PCI slot 00:1b.0 has a High Definition Audio Card > >>>>>> >>> >> >> >>> >> >> The drivers are in the kernel modules tree at: > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.28-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.28-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.27-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.28-13-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko > >>>>>> >>> >> >> >>> >> >> The modem codec file for the HDA card is: > >>>>>> >>> >> >> >>> >> >> /proc/asound/card0/codec#1 > >>>>>> >>> >> >> >>> >> >> -------------------------------------------------------- > >>>>>> >>> >> >> >>> >> >> Codec: Motorola Si3054 > >>>>>> >>> >> >> >>> >> >> Address: 1 > >>>>>> >>> >> >> >>> >> >> Vendor Id: 0x10573055 > >>>>>> >>> >> >> >>> >> >> Subsystem Id: 0x10573055 > >>>>>> >>> >> >> >>> >> >> Revision Id: 0x100700 > >>>>>> >>> >> >> >>> >> >> Modem Function Group: 0x1 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The audio card hosts a softmodem chip: > >>>>>> >>> >> >> >>> >> >> 0x10573055 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The softmodem chip 0x10573055 is in principle > >>>>>> >>> >> >> >>> >> >> supported by the COMM > >>>>>> >>> >> >> >>> >> >> support > >>>>>> >>> >> >> >>> >> >> of slmodemd > >>>>>> >>> >> >> >>> >> >> and the joint snd-hda-intel audio+modem driver, > >>>>>> >>> >> >> >>> >> >> begun with ALSA version > >>>>>> >>> >> >> >>> >> >> 1.0.13. > >>>>>> >>> >> >> >>> >> >> For HDA cards with ALC883 chips, an upgrade to ALSA > >>>>>> >>> >> >> >>> >> >> verions 1.0.15 way > >>>>>> >>> >> >> >>> >> >> be > >>>>>> >>> >> >> >>> >> >> necessary. Instructions for Upgrading snd-hda-intel > >>>>>> >>> >> >> >>> >> >> and its dependent > >>>>>> >>> >> >> >>> >> >> driver > >>>>>> >>> >> >> >>> >> >> set are at: > >>>>>> >>> >> >> >>> >> >> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> If not a Conexant modem, the driver snd-hda-intel > >>>>>> >>> >> >> >>> >> >> with its dependent > >>>>>> >>> >> >> >>> >> >> drivers: > >>>>>> >>> >> >> >>> >> >> snd_hda_intel 434100 6 > >>>>>> >>> >> >> >>> >> >> snd_pcm 83076 4 > >>>>>> >>> >> >> >>> >> >> snd_hda_intel,snd_pcm_oss > >>>>>> >>> >> >> >>> >> >> snd 62756 20 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device > >>>>>> >>> >> >> >>> >> >> snd_page_alloc 16904 2 > >>>>>> >>> >> >> >>> >> >> snd_hda_intel,snd_pcm > >>>>>> >>> >> >> >>> >> >> ---------- > >>>>>> >>> >> >> >>> >> >> provide audio + modem support with the modem chip > >>>>>> >>> >> >> >>> >> >> residing on the > >>>>>> >>> >> >> >>> >> >> subsystem. > >>>>>> >>> >> >> >>> >> >> Any particular card can host any one of several > >>>>>> >>> >> >> >>> >> >> soft modem chips. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> === Finished firmware and bootup diagnostics, next > >>>>>> >>> >> >> >>> >> >> deducing cogent > >>>>>> >>> >> >> >>> >> >> software. > >>>>>> >>> >> >> >>> >> >> === > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Predictive diagnostics for card in bus 00:1b.0: > >>>>>> >>> >> >> >>> >> >> Modem chipset detected on > >>>>>> >>> >> >> >>> >> >> NAME="Audio device: Intel Corporation 82801H " > >>>>>> >>> >> >> >>> >> >> CLASS=0403 > >>>>>> >>> >> >> >>> >> >> PCIDEV=8086:284b > >>>>>> >>> >> >> >>> >> >> SUBSYS=17aa:384e > >>>>>> >>> >> >> >>> >> >> IRQ=22 > >>>>>> >>> >> >> >>> >> >> HDA=8086:284b > >>>>>> >>> >> >> >>> >> >> SOFT=8086:284b.HDA > >>>>>> >>> >> >> >>> >> >> HDAchipVendorID=1057 > >>>>>> >>> >> >> >>> >> >> CHIP=0x10573055 > >>>>>> >>> >> >> >>> >> >> IDENT=slmodemd > >>>>>> >>> >> >> >>> >> >> SLMODEMD_DEVICE=hw:0,6 > >>>>>> >>> >> >> >>> >> >> Driver=snd-hda-intel > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> For candidate modem in: 00:1b.0 > >>>>>> >>> >> >> >>> >> >> 0403 Audio device: Intel Corporation 82801H > >>>>>> >>> >> >> >>> >> >> Primary device ID: 8086:284b > >>>>>> >>> >> >> >>> >> >> Subsystem PCI_id 17aa:384e > >>>>>> >>> >> >> >>> >> >> Softmodem codec or chipset from diagnostics: > >>>>>> >>> >> >> >>> >> >> 0x10573055 > >>>>>> >>> >> >> >>> >> >> from Archives: > >>>>>> >>> >> >> >>> >> >> The HDA card softmodem chip > >>>>>> >>> >> >> >>> >> >> is 0x10573055 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Support type needed or chipset: slmodemd > >>>>>> >>> >> >> >>> >> >> supporting the > >>>>>> >>> >> >> >>> >> >> snd-hda-intel > >>>>>> >>> >> >> >>> >> >> audio+modem driver > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> An ALSA (Advanced Linux Sound Architecture) modem > >>>>>> >>> >> >> >>> >> >> driver: > >>>>>> >>> >> >> >>> >> >> snd-hda-intel > >>>>>> >>> >> >> >>> >> >> provides Low Level support enabling contact with > >>>>>> >>> >> >> >>> >> >> the modem hardware. > >>>>>> >>> >> >> >>> >> >> For all BUT Conexant chip soft modems (using > >>>>>> >>> >> >> >>> >> >> hsfmodem software) > >>>>>> >>> >> >> >>> >> >> complementary High Level support is through a > >>>>>> >>> >> >> >>> >> >> Smartlink utility: > >>>>>> >>> >> >> >>> >> >> slmodemd > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Download from > >>>>>> >>> >> >> >>> >> >> http://linmodems.technion.ac.il/packages/smartlink/ > >>>>>> >>> >> >> >>> >> >> the package SLMODEMD.gcc4.3.tar.gz having a > >>>>>> >>> >> >> >>> >> >> compiled slmodemd. Unpack > >>>>>> >>> >> >> >>> >> >> under > >>>>>> >>> >> >> >>> >> >> Linux with: > >>>>>> >>> >> >> >>> >> >> $ tar zxf SLMODEMD.gcc4.3.tar.gz > >>>>>> >>> >> >> >>> >> >> and read instructions therein. But briefly, the > >>>>>> >>> >> >> >>> >> >> modem is setup with > >>>>>> >>> >> >> >>> >> >> command: > >>>>>> >>> >> >> >>> >> >> sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6 > >>>>>> >>> >> >> >>> >> >> reporting dynamic creation of ports: > >>>>>> >>> >> >> >>> >> >> /dev/ttySL0 --> /dev/pts/N , with N some > >>>>>> >>> >> >> >>> >> >> number > >>>>>> >>> >> >> >>> >> >> Read DOCs/Smartlink.txt and > >>>>>> >>> >> >> >>> >> >> Modem/DOCs/YourSystem.txt for follow > >>>>>> >>> >> >> >>> >> >> through > >>>>>> >>> >> >> >>> >> >> guidance. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Writing DOCs/Intel.txt > >>>>>> >>> >> >> >>> >> >> Writing DOCs/Smartlink.txt > >>>>>> >>> >> >> >>> >> >> ============ end Smartlink section > >>>>>> >>> >> >> >>> >> >> ===================== > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Completed candidate modem analyses. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The base of the UDEV device file system is: > >>>>>> >>> >> >> >>> >> >> /dev/.udev > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Versions adequately match for the compiler > >>>>>> >>> >> >> >>> >> >> installed: 4.3.3 > >>>>>> >>> >> >> >>> >> >> and the compiler used in kernel > >>>>>> >>> >> >> >>> >> >> assembly: 4.3.3 > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> The patch utility is needed and is needed for > >>>>>> >>> >> >> >>> >> >> compiling ALSA drivers, > >>>>>> >>> >> >> >>> >> >> and > >>>>>> >>> >> >> >>> >> >> possibly others. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Minimal compiling resources appear complete: > >>>>>> >>> >> >> >>> >> >> make utility - /usr/bin/make > >>>>>> >>> >> >> >>> >> >> Compiler version 4.3 > >>>>>> >>> >> >> >>> >> >> linuc_headers base folder > >>>>>> >>> >> >> >>> >> >> /lib/modules/2.6.28-15-generic/build > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> However some compilations and executable functions > >>>>>> >>> >> >> >>> >> >> may need additional > >>>>>> >>> >> >> >>> >> >> files, > >>>>>> >>> >> >> >>> >> >> in the FileNames.h (so called kernel "h"eaders) > >>>>>> >>> >> >> >>> >> >> collection installed > >>>>>> >>> >> >> >>> >> >> in > >>>>>> >>> >> >> >>> >> >> /usr/include/ . > >>>>>> >>> >> >> >>> >> >> For martian_modem, additional required packages > >>>>>> >>> >> >> >>> >> >> are needed. The also > >>>>>> >>> >> >> >>> >> >> required headers of package libc6 are commonly > >>>>>> >>> >> >> >>> >> >> installed by default. > >>>>>> >>> >> >> >>> >> >> Compiling hsfmodem drivers does require > >>>>>> >>> >> >> >>> >> >> linux-libc-dev and libc6-dev > >>>>>> >>> >> >> >>> >> >> packages, for kernels 2.6.24 and later versions. > >>>>>> >>> >> >> >>> >> >> In not included on your install CD, search for > >>>>>> >>> >> >> >>> >> >> them at > >>>>>> >>> >> >> >>> >> >> http://packages.ubuntu.com > >>>>>> >>> >> >> >>> >> >> or comparable Repository for other Linux distros. > >>>>>> >>> >> >> >>> >> >> When compiling ALSA drivers, the utility "patch" > >>>>>> >>> >> >> >>> >> >> will also be needed. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> If a driver compilation fails, with message > >>>>>> >>> >> >> >>> >> >> including some lack of some > >>>>>> >>> >> >> >>> >> >> FileName.h (stdio.h for example), then > >>>>>> >>> >> >> >>> >> >> Some additional kernel-header files need > >>>>>> >>> >> >> >>> >> >> installation to /usr/include. > >>>>>> >>> >> >> >>> >> >> The > >>>>>> >>> >> >> >>> >> >> minimal additional packages are libc6-dev > >>>>>> >>> >> >> >>> >> >> and any of its dependents, under Ubuntu > >>>>>> >>> >> >> >>> >> >> linux-libc-dev > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> If an alternate ethernet connection is available, > >>>>>> >>> >> >> >>> >> >> $ apt-get update > >>>>>> >>> >> >> >>> >> >> $ apt-get -s install linux-kernel-devel > >>>>>> >>> >> >> >>> >> >> will install needed packages. > >>>>>> >>> >> >> >>> >> >> For Debian/Ubuntu related distributions, run the > >>>>>> >>> >> >> >>> >> >> following command to > >>>>>> >>> >> >> >>> >> >> display the needed package list: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Otherwise packages have to be found through > >>>>>> >>> >> >> >>> >> >> http://packages.ubuntu.com > >>>>>> >>> >> >> >>> >> >> Once downloaded and transferred into a Linux > >>>>>> >>> >> >> >>> >> >> partition, > >>>>>> >>> >> >> >>> >> >> they can be installed alltogether with: > >>>>>> >>> >> >> >>> >> >> $ sudo dpkg -i *.deb > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Checking pppd properties: > >>>>>> >>> >> >> >>> >> >> -rwsr-xr-- 1 root dip 277352 2009-02-20 22:55 > >>>>>> >>> >> >> >>> >> >> /usr/sbin/pppd > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> In case of an "error 17" "serial loopback" problem, > >>>>>> >>> >> >> >>> >> >> see: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> To enable dialout without Root permission do: > >>>>>> >>> >> >> >>> >> >> $ su - root (not for Ubuntu) > >>>>>> >>> >> >> >>> >> >> sudo chmod a+x /usr/sbin/pppd > >>>>>> >>> >> >> >>> >> >> or under Ubuntu related Linuxes > >>>>>> >>> >> >> >>> >> >> sudo chmod a+x /usr/sbin/pppd > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Checking settings of: /etc/ppp/options > >>>>>> >>> >> >> >>> >> >> asyncmap 0 > >>>>>> >>> >> >> >>> >> >> noauth > >>>>>> >>> >> >> >>> >> >> crtscts > >>>>>> >>> >> >> >>> >> >> lock > >>>>>> >>> >> >> >>> >> >> hide-password > >>>>>> >>> >> >> >>> >> >> modem > >>>>>> >>> >> >> >>> >> >> proxyarp > >>>>>> >>> >> >> >>> >> >> lcp-echo-interval 30 > >>>>>> >>> >> >> >>> >> >> lcp-echo-failure 4 > >>>>>> >>> >> >> >>> >> >> noipx > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> In case of a message like: > >>>>>> >>> >> >> >>> >> >> Warning: Could not modify /etc/ppp/pap-secrets: > >>>>>> >>> >> >> >>> >> >> Permission denied > >>>>>> >>> >> >> >>> >> >> see > >>>>>> >>> >> >> >>> >> >> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Read Modem/DOCs/YourSystem.txt concerning other > >>>>>> >>> >> >> >>> >> >> COMM channels: eth0 > >>>>>> >>> >> >> >>> >> >> eth1 > >>>>>> >>> >> >> >>> >> >> Which can interfere with Browser naviagation. > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Don't worry about the following, it is for experts > >>>>>> >>> >> >> >>> >> >> should trouble > >>>>>> >>> >> >> >>> >> >> shooting > >>>>>> >>> >> >> >>> >> >> be necessary. > >>>>>> >>> >> >> >>> >> >> ========================================================== > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Checking for modem support lines: > >>>>>> >>> >> >> >>> >> >> -------------------------------------- > >>>>>> >>> >> >> >>> >> >> /device/modem symbolic link: lrwxrwxrwx 1 > >>>>>> >>> >> >> >>> >> >> root root 6 2009-08-31 > >>>>>> >>> >> >> >>> >> >> 17:27 /dev/modem -> ttySL0 > >>>>>> >>> >> >> >>> >> >> slmodemd created symbolic link /dev/ttySL0: > >>>>>> >>> >> >> >>> >> >> lrwxrwxrwx 1 root root 10 > >>>>>> >>> >> >> >>> >> >> 2009-08-31 17:27 /dev/ttySL0 -> /dev/pts/0 > >>>>>> >>> >> >> >>> >> >> Within /etc/udev/ files: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Within /etc/modprobe.conf files: > >>>>>> >>> >> >> >>> >> >> /etc/modprobe.d/blacklist-modem.conf:# Uncomment > >>>>>> >>> >> >> >>> >> >> these entries in order > >>>>>> >>> >> >> >>> >> >> to > >>>>>> >>> >> >> >>> >> >> blacklist unwanted modem drivers > >>>>>> >>> >> >> >>> >> >> /etc/modprobe.d/blacklist-modem.conf:# blacklist > >>>>>> >>> >> >> >>> >> >> snd-atiixp-modem > >>>>>> >>> >> >> >>> >> >> /etc/modprobe.d/blacklist-modem.conf:# blacklist > >>>>>> >>> >> >> >>> >> >> snd-via82xx-modem > >>>>>> >>> >> >> >>> >> >> /etc/modprobe.d/alsa-base.conf:options > >>>>>> >>> >> >> >>> >> >> snd-atiixp-modem index=-2 > >>>>>> >>> >> >> >>> >> >> /etc/modprobe.d/alsa-base.conf:options > >>>>>> >>> >> >> >>> >> >> snd-via82xx-modem index=-2 > >>>>>> >>> >> >> >>> >> >> Within any ancient /etc/devfs files: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> Within ancient kernel 2.4.n /etc/module.conf > >>>>>> >>> >> >> >>> >> >> files: > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> --------- end modem support lines -------- > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> >> > >>>>>> >>> >> >> >>> >> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >>> > > >>>>>> >>> >> >> >> > >>>>>> >>> >> >> > > >>>>>> >>> >> > > >>>>>> >>> > > >>>>>> >> > >>>>>> > > >>>>> > >>>> > >>> > >> > >
