Re: Ivan, Serbia kernel 2.6.15-23-386

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

 



Drafter in Serbia

$ sudo modprobe agrmodem
must preceed
$ sudo modprobe agrserial

Record the outputs of
$ dmesg | grep agr
$  dmesg | grep 02:0a.0
$ sudo tail -f /var/log/messages
and send them to us.  They relate kernel actions in response to driver loading.

Redo
$ sudo ln -s /dev/ttyAGS3 /dev/ttySAGR
before running the

$ sudo wvdialconf  /etc/wvdial.conf

This is one of our more troublesome modems under Linux
Success seems dependent on the detailed hardware environment.

MarvS


On Jan 20, 2008 5:10 PM, - Drafter - <it.drafter@xxxxxxxxx> wrote:
> @Jacques
> I had not installed an other driver before the agrsm. I came to you
> for help with freshly installed Ubuntu, so that couldn't be the
> problem.
>
> @Hugo
> I typed "acpi=off" to the end of the document "/boot/grub/menu.lst
> ", restarted the system and then:
> -----------------------------------------------------------------------
> brzi@brzi-linux:~$ sudo modprobe agrserial
> Password:
> FATAL: Error inserting agrserial
> (/lib/modules/2.6.15-23-386/extra/agrserial.ko): No such device
> brzi@brzi-linux:~$ sudo ln -s /dev/ttyAGS3 /dev/ttySAGR
> brzi@brzi-linux:~$ sudo ln -s /dev/ttyAGS3 /dev/modem
> 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  SAGR
>
>
> 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>.
> -----------------------------------------------------------------------
>
> I got the same result when I typed "pci=noacpi" instead of "acpi=off".
>
> Ivan Tancik
>

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

  Powered by Linux