Antonio,
Thus spake Antonio Olivares (olivares14031@xxxxxxxxx):
[skip]
> root@slax:~# ln -s /dev/ttyAGS3 /dev/ttySAG
The name of the device shall be /dev/ttySAGR
To better diagnose the problem, I would suggest building
the driver "7mdv" manually from source,
install it with 'make modules_install' and see if
wvdialconf can recognize it:
# kill all the funny Agr...Daemons, etc first, next:
$ sudo modprobe -r agrserial
$ sudo modprobe -r agrmodem
$ sudo find /lib/modules -name "agr*" -type f -exec rm -f {} \;
$ make
$ sudo make modules_install
$ sudo modprobe agrmodem
$ sudo modprobe agrserial
$ sudo ln -s /dev/ttyAGS3 /dev/ttySAGR
$ sudo wvdialconf /dev/wvdial.conf
[skip]
> I also see some differences between the packages, namely the
> agrms-2.1.80-7mdv2009.0 and the agrsm-20090502 packages.
They are for the different hardware, I think. The "7mdv" shall work for the
11c11140 chipset that sits on the HDA audio. I am not sure what other chipset
it supports and how well. The agrsm-20090502 does not have the HDA layer
support, hence it doesn't support 11c11140 on HDA, and its codebase is/was
different from the "mdv" sources.
> 5) I am more confused now than what I was before, the
> agrsm-2.1.80mdv2009.0 package should be more appropriate for the
> 11c11040 chipset than the others:
>
> 11c1:0630, 11c1:0620, 11c1:0630 and 11c1:048c(or f)
>
> This is how I interpret the results.
Were the chipsets that you mention (11c1:0630, 11c1:0620,
11c1:0630 and 11c1:048) supported by earlier release
of the "mdv" sources, like the "4mdv" sources available
at the Zsolt site, for example? What did you use before?
--
WBR, Nikolay Zhuravlev
