Re: Ivan, Serbia kernel 2.6.15-23-386

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



@Jacques, I did everything U told me to (no modem was detected):
-----------------------------------------------------------------------------------------------------------------------
brzi@brzi-linux:~$ sudo lsmod | grep agr
brzi@brzi-linux:~$ sudo modprobe agrmodem
brzi@brzi-linux:~$ sudo modprobe agrserial
brzi@brzi-linux:~$ sudo lsmod | grep agr
agrserial              16688  0
agrmodem             1180932  2
brzi@brzi-linux:~$ sudo wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1   S2   S3   S4   S5   S6   S7   S8
Modem Port Scan<*1>: S9   S10  S11  S12  S13  S14  S15  S16
Modem Port Scan<*1>: S17  S18  S19  S20  S21  S22  S23  S24
Modem Port Scan<*1>: S25  S26  S27  S28  S29  S30  S31  S32
Modem Port Scan<*1>: S33  S34  S35  S36  S37  S38  S39  S40
Modem Port Scan<*1>: S41  S42  S43  S44  S45  S46  S47


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://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
-----------------------------------------------------------------------------------------------------------------------
brzi@brzi-linux:~$ ls -l /dev/ttyAG*
crw-rw---- 1 root dialout 62, 67 2008-01-17 20:26 /dev/ttyAGS3
brzi@brzi-linux:~$ ls -l /dev/ttySAG*
ls: /dev/ttySAG*: No such file or directory
brzi@brzi-linux:~$ ls -l /dev/modem
ls: /dev/modem: No such file or directory
brzi@brzi-linux:~$
----------------------------------------------------------------------------------------------------------------------
Regards,
Ivan

On 1/17/08, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:
> Ivan,
>
> Can you please do
> sudo lsmod | grep agr
> which should show  agrmodem.ko and agrserial.ko ?
> In case it does not, can you please
> sudo modprobe agrmodem
> sudo modprobe agrserial
> and again sudo lsmod | grep agr in order to verify that the modules
> which you compiled are loaded in memory.
> At that time
> sudo wvdialconf /etc/wvdial.conf
> should detect the modem.
> From what you reported (see below) you just typed wvdialconf,
> not sudo wvdialconf
>
> Furthermore,
> What do you see when typing
> ls -l /dev/ttyAG*
> ls -l /dev/ttySAG*
> ls -l /dev/modem
>  A simple link command may be missing.
>
> Jacques
>
> - Drafter - wrote:
> > OK, I think I'm getting somewhere now! But, still don't know how to
> > connect to the Internet.
> > After installing (as advised by Antonio) "build-essential" and
> > "setserial" from the ubuntu cd, and downloading
> > "linux-headers-2.6.15-23-386_2.6.15-23.39_i386.deb" and all the
> > depends files (command "sudo dpkg -i *.deb"), I was able to execute
> > "sudo meke module" and "sudo make install", as you can see:
> >
> > ------------------------------------------------------------------------------------------------------------------------
> > ------------------------------------------------------------------------------------------------------------------------
> > brzi@brzi-linux:~$ cd agrsm
> >
> > brzi@brzi-linux:~/agrsm$ sudo make module
> > make -C /lib/modules/`uname -r`/build SUBDIRS=/home/brzi/agrsm modules
> > make[1]: Entering directory `/usr/src/linux-headers-2.6.15-23-386'
> >   CC [M]  /home/brzi/agrsm/agrsoftmodem.o
> > /home/brzi/agrsm/agrsoftmodem.c: In function 'SetAgrModemInterface':
> > /home/brzi/agrsm/agrsoftmodem.c:106: warning: 'inter_module_put' is
> > deprecated (declared at include/linux/module.h:575)
> > /home/brzi/agrsm/agrsoftmodem.c: In function 'modem_init_module':
> > /home/brzi/agrsm/agrsoftmodem.c:136: warning: 'inter_module_register'
> > is deprecated (declared at include/linux/module.h:571)
> > /home/brzi/agrsm/agrsoftmodem.c:137: warning: 'inter_module_register'
> > is deprecated (declared at include/linux/module.h:571)
> > /home/brzi/agrsm/agrsoftmodem.c: In function 'modem_cleanup_module':
> > /home/brzi/agrsm/agrsoftmodem.c:148: warning:
> > 'inter_module_unregister' is deprecated (declared at
> > include/linux/module.h:572)
> > /home/brzi/agrsm/agrsoftmodem.c:149: warning:
> > 'inter_module_unregister' is deprecated (declared at
> > include/linux/module.h:572)
> >   CC [M]  /home/brzi/agrsm/serial26.o
> > /home/brzi/agrsm/serial26.c: In function 'serial8250_config_port':
> > /home/brzi/agrsm/serial26.c:1998: warning: unused variable 'ret'
> > /home/brzi/agrsm/serial26.c: At top level:
> > /home/brzi/agrsm/serial26.c:2090: warning: initialization from
> > incompatible pointer type
> > /home/brzi/agrsm/serial26.c:2091: warning: initialization from
> > incompatible pointer type
> > /home/brzi/agrsm/serial26.c: In function 'serial8250_exit':
> > /home/brzi/agrsm/serial26.c:2523: warning: 'inter_module_unregister'
> > is deprecated (declared at include/linux/module.h:572)
> > /home/brzi/agrsm/serial26.c:2524: warning: 'inter_module_put' is
> > deprecated (declared at include/linux/module.h:575)
> > /home/brzi/agrsm/serial26.c:2525: warning: 'inter_module_put' is
> > deprecated (declared at include/linux/module.h:575)
> > /home/brzi/agrsm/serial26.c: In function 'agr_init_module':
> > /home/brzi/agrsm/serial26.c:2555: warning: 'inter_module_put' is
> > deprecated (declared at include/linux/module.h:575)
> > /home/brzi/agrsm/serial26.c:2561: warning: 'inter_module_register' is
> > deprecated (declared at include/linux/module.h:571)
> > /home/brzi/agrsm/serial26.c: At top level:
> > /home/brzi/agrsm/serial26.c:1881: warning:
> > 'serial8250_request_rsa_resource' defined but not used
> >   LD [M]  /home/brzi/agrsm/agrmodem.o
> >   LD [M]  /home/brzi/agrsm/agrserial.o
> >   Building modules, stage 2.
> >   MODPOST
> > Warning: could not find /home/brzi/agrsm/.agrmodemlib.o.cmd for
> > /home/brzi/agrsm/agrmodemlib.o CC      /home/brzi/agrsm/agrmodem.mod.o
> >   LD [M]  /home/brzi/agrsm/agrmodem.ko
> >   CC      /home/brzi/agrsm/agrserial.mod.o
> >   LD [M]  /home/brzi/agrsm/agrserial.ko
> > make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
> >
> > brzi@brzi-linux:~/agrsm$ sudo make install
> > make -C /lib/modules/`uname -r`/build M="/home/brzi/agrsm" modules_install
> > make[1]: Entering directory `/usr/src/linux-headers-2.6.15-23-386'
> >   INSTALL /home/brzi/agrsm/agrmodem.ko
> >   INSTALL /home/brzi/agrsm/agrserial.ko
> > make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-23-386'
> > if ! /sbin/modprobe -nq agrmodem.ko ; then /sbin/depmod -a; fi
> > brzi@brzi-linux:~/agrsm$
> > ------------------------------------------------------------------------------------------------------------------------
> > ------------------------------------------------------------------------------------------------------------------------
> >
> >
> >
> > I don't know what to do next, anyway I tried to follow Jacques's
> > advice to use WvDial, but the next lines show up:
> >
> > brzi@brzi-linux:~$ wvdialconf
> > Editing `/etc/wvdial.conf'.
> >
> > Scanning your serial ports for a modem.
> >
> > WvModem<*1>: Cannot set information for serial port.
> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> > Modem Port Scan<*1>: S1   S2   S3   S4   S5   S6   S7   S8
> > Modem Port Scan<*1>: S9   S10  S11  S12  S13  S14  S15  S16
> > Modem Port Scan<*1>: S17  S18  S19  S20  S21  S22  S23  S24
> > Modem Port Scan<*1>: S25  S26  S27  S28  S29  S30  S31  S32
> > Modem Port Scan<*1>: S33  S34  S35  S36  S37  S38  S39  S40
> > Modem Port Scan<*1>: S41  S42  S43  S44  S45  S46  S47
> >
> >
> > 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://open.nit.ca/wiki/?WvDial
> >
> > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
> >
> >
> > brzi@brzi-linux:~$ wvdial
> > --> WvDial: Internet dialer version 1.55
> > --> 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
> >
> > On 1/17/08, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
> >> Drafter,
> >>
> >> Compiling fails because you do not have gcc installed:
> >> This is directly from ScanModem output that you have sent.  You need
> >> to do this so that your modem drivers can compile
> >>
> >> $ sudo apt-get install  gcc-4.0  make
> >> Additionally the package linux-headers-2.6.15-23-386 must be downloaded.
> >> Go to http://packages.ubuntu.com/  and search for linux-headers-2.6.15-23-386
> >> After downloading, it can be installed with:
> >> $ sudo dpkg -i linux-header*.deb
> >>
> >> If that is unsuccessful, do try the alternate methods provided below.
> >>
> >> \begin{QUOTE}
> >> If compiling a modem driver proves to be necessary, one of the two
> >> procedures must be followed.
> >> If not yet on the Internet, put the Dapper install CD in the drive
> >> Open a terminal and therein:
> >> $ sudo apt-get install  gcc-4.0  make
> >> Additionally the package linux-headers-2.6.15-23-386 must be downloaded.
> >> Go to http://packages.ubuntu.com/  and search for linux-headers-2.6.15-23-386
> >> After downloading, it can be installed with:
> >> $ sudo dpkg -i linux-header*.deb
> >>
> >> Or alternatively if online through Ethernet do:
> >> $ sudo apt-get update
> >> $ sudo apt-get install build-essential
> >> will do all the necessary installations mentioned above.
> >>
> >> In either installation case, set a symbolic link which will be expected later:
> >> $ sudo ln -s /usr/bin/gcc-4.0  /usr/bin/gcc
> >> After check with:
> >> $ ls -l /usr/bin/gcc*
> >> which should display:
> >> lrwxrwxrwx 1 root root    16 2006-07-09 21:53 /usr/bin/gcc -> /usr/bin/gcc-4.0
> >> -rwxr-xr-x 1 root root 93584 2006-04-20 18:22 /usr/bin/gcc-4.0
> >> -rwxr-xr-x 1 root root 16245 2006-04-20 18:13 /usr/bin/gccbug-4.0
> >>
> >> linux-headers-2.6.15-23-386 resources needed for compiling are not
> >> manifestly ready!
> >>
> >> If compiling is necessary packages must be installed, providing:
> >>        gcc-4.0 make linux-headers-2.6.15-23-386
> >>
> >>
> >> 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 package
> >> 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
> >> \end{QUOTE}
> >>
> >> Hope this helps,
> >>
> >> Antonio
> >>
> >>
> >> On 1/16/08, - Drafter - <it.drafter@xxxxxxxxx> wrote:
> >>> I'm having some hard time installing the driver... It's probably
> >>> stupid, but I'm an absolute beginner, so please don't laugh :-)
> >>> Here's what I did - step by step:
> >>> 1) downloaded the file "agrsm-alpha.tar.bz2"
> >>> 2) copied it to "Home folder"
> >>> 3) started the terminal
> >>> 4) gave the command "tar jxf agrsm-alpha.tar.bz2"
> >>> 5) "cd agrsm" and then "ls", all the files are there!
> >>> 6) "sudo make module", and it's asking me for the password, which I
> >>> successfully entered
> >>> 7) HERE'S THE PROBLEM: the following line showed up: "sudo: make:
> >>> command not found". I also tried "sudo make install", and got the same
> >>> message.
> >>>
> >>> P.S.
> >>> I also tried to enter the command "sudo make module | tee mywork.txt"
> >>> as you advised, but I got the following message:
> >>> "sudo: make: command not found
> >>> tee: mywork.txt: Permission denied"
> >>>
> >>> The same message shows up for "sudo make install | tee -a mywork.txt".
> >>>
> >>> I know I'm doing something wrong, just don't know what...
> >>>
> >>>
> >>> On 1/16/08, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:
> >>>>
> >>>> - Drafter - wrote:
> >>>>> Absolutelu new in Linux, please help! tnx
> >>>> ModemData has identified your modem as a Lucent (Agere) 048C supported
> >>>> by driver AGRSM.
> >>>>
> >>>> ModemData wrote:
> >>>> "
> >>>> AGRSM - At http://phep2.technion.ac.il/linmodems/packages/ltmodem/sv92/
> >>>> Read Agrsm.txt
> >>>> "
> >>>> The first line means: this is the place on the Web where you will find
> >>>> the driver.
> >>>> The second line means: when you used scanModem to obtain ModemData.txt,
> >>>> you found ModemData.txt in a directory named Modem.
> >>>> This directory contains a file named Agrsm.txt. ModemData.txt asks you
> >>>> to read it.
> >>>> If a beginner you are likely find hard to read it ans ask yourself why
> >>>> should you read it.
> >>>>
> >>>> So, what you can do at the very beginner level is to download from the
> >>>> address above the file agrsm-alpha.tar.bz2  into your logon directory
> >>>> Then give the command
> >>>> tar jxf agrsm-alpha.tar.bz2
> >>>> This will create a new subdirectory named agrsm . Enter it with command
> >>>> cd agrsm
> >>>> Give the command
> >>>> ls
> >>>> to see which files are present in this directory agrsm
> >>>> One is named README
> >>>> Read it using the command
> >>>> less README
> >>>> With this command named less you can read and read back, go to the
> >>>> beginning with < and to the end with > , you can use the keyboard
> >>>> arrows, page up, page down, and you use the space bar to get to the next
> >>>> page.
> >>>> Now you are ready to build the driver except that with Ubuntu you must
> >>>> type the commands as follows:
> >>>> sudo make module
> >>>> sudo make install
> >>>> (the command sudo is not quoted in file README, specific to Debian and
> >>>> Ubuntu systems).
> >>>>
> >>>> There are several ways to continue.
> >>>> kppp suggested in README is reasonable.
> >>>> I personally prefer using wvdial because it gives many messages and
> >>>> makes life possible when kppp fails.
> >>>> Details at: http://linmodems.technion.ac.il/wvdial.html
> >>>>
> >>>> PLEASE TELL US THE RESULT, SUCCESS OR FAILURE.
> >>>> If FAILURE, do not write "there is an error" as this gives us no
> >>>> information. Please write everything you did and all the error messages.
> >>>> A good way to do it is to give the commands as follows:
> >>>> sudo make module | tee mywork.txt
> >>>> sudo make install | tee -a mywork.txt
> >>>>
> >>>> The | sign is usually above \ on most keyboards (| visible as if cut in
> >>>> middle)
> >>>> The tee command will make a copy of the outputs of make module and make
> >>>> install into the file so that you just need to send us the file.
> >>>> If you follow my advice to use wvdial (one step, wvdialconf, then wvdial
> >>>> every time you want to connect) you can again use the tee command to
> >>>> record the outputs of wvdialconf and wvdial to help us help you.
> >>>>
> >>>> Jacques
> >>>>
>


-- 
U can visit my web site @:
www.drafter.co.nr

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux