Re: David Ellis, USA, Kernel 2.6.27-7 Generic

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

 



Hi Marvin,

After a reboot here is the result from agrsm-test.  No modem found.

*********************************************************************
Loading drivers:

Drivers loaded:
agrserial              19808  0 
agrmodem             1259268  1 
snd                    63268  16 agrmodem,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device

and symbolic link created:
lrwxrwxrwx 1 root root 12 2009-03-21 09:53 /dev/ttySAGR -> /dev/ttyAGS3

Checking for utility wvdialconf
Found /usr/bin/wvdialconf, preparing to run:
	wvdialconf /etc/wvdial.conf

Modem Port Scan<*1>: S0   S1   S2   S3   
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.

A reboot may be necessary before modem detection through:
	sudo modprobe agrserial
Which will load agrmodem, agrserial and create the symbolic link needed for:
	sudo wvdialconf


The installation record has been written to ./agrsm-test.txt
*********************************************************************

Thanks for the help.

David



--- On Sat, 3/21/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:

> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
> Subject: Re: David Ellis, USA, Kernel 2.6.27-7 Generic
> To: davesjunk@xxxxxxxxxx
> Cc: discuss@xxxxxxxxxxxxx
> Date: Saturday, March 21, 2009, 7:14 PM
> David
> 
> When you reboot, again run
> $ sudo agrsm-test
> Report back.
> 
> MarvS
> 
> On Fri, Mar 20, 2009 at 9:51 PM, David Ticer
> <davesjunk@xxxxxxxxxx> wrote:
> >
> > Thanks Marvin,
> >
> > I ran agrsm-test and no modem was detected.
> >
> > Here's the text file output agrsm-test.txt
> >
> >
> **********************************************************
> > Loading drivers:
> >
> > Drivers loaded:
> > agrserial              19808  0
> > agrmodem             1259268  1
> > snd                    63268  16
> agrmodem,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
> >
> > and symbolic link created:
> > lrwxrwxrwx 1 root root 12 2009-03-20 14:24
> /dev/ttySAGR -> /dev/ttyAGS3
> >
> > Checking for utility wvdialconf
> > Found /usr/bin/wvdialconf, preparing to run:
> >        wvdialconf /etc/wvdial.conf
> >
> > Modem Port Scan<*1>: S0   S1   S2   S3
> > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400
> baud, next try: 9600 baud
> > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600
> baud, next try: 115200 baud
> > ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at
> 115200, giving up.
> >
> > A reboot may be necessary before modem detection
> through:
> >        sudo modprobe agrserial
> > Which will load agrmodem, agrserial and create the
> symbolic link needed for:
> >        sudo wvdialconf
> >
> ************************************************************************
> >
> > What's next?
> >
> > Best Regards,
> >
> > Dave
> >
> >
> > --- On Fri, 3/20/09, Marvin Stodolsky
> <marvin.stodolsky@xxxxxxxxx> wrote:
> >
> >> From: Marvin Stodolsky
> <marvin.stodolsky@xxxxxxxxx>
> >> Subject: Re: David Ellis, USA, Kernel 2.6.27-7
> Generic
> >> To: davesjunk@xxxxxxxxxx
> >> Cc: discuss@xxxxxxxxxxxxx
> >> Date: Friday, March 20, 2009, 7:21 PM
> >> David,
> >>
> >> Don't try to manage modems through the Network
> menu.
> >> It you have installed the agrsm-tools package,
> just run:
> >> $ sudo agrsm-test
> >> For a first testing of the drivers, followed by a
> modem
> >> test through
> >> the included:
> >>   wvdialconf
> >> which it successful will create /etc/wvdial.conf
> >>
> >> DO an edit with:
> >> $ sudo gedit /etc/wvdial.conf
> >> putting in your personal infor and  deleting the
> symbols ;
> >> < >
> >>
> >> Before trying to dialout, check COMM channels
> with:
> >> $ ifconfig
> >> close any except loopback "lo"  with
> commands
> >> like:
> >> $ sudo ifconfig eth0 down
> >> Such COMM channels are automatically setup if a
> System has
> >> cogent hardware,
> >> but they will interfere with DNS services of the
> dialout
> >> ppp0 COMM channel.
> >>
> >> Lastly, try your dialout with:
> >> $ sudo wvdial
> >>
> >> MarvS
> >>
> >>
> >>
> >> On Fri, Mar 20, 2009 at 1:43 PM, David Ticer
> >> <davesjunk@xxxxxxxxxx> wrote:
> >> >
> >> > Thanks Antonio,
> >> >
> >> > This is my first encounter with Linux, so
> please
> >> forgive me for being clueless.  I downloaded the
> agrsm
> >> package and installed it by double clicking it
> using the
> >> file browser.  I then rebooted but I'm not
> sure where
> >> to go from here.  I searched help and found a
> page that
> >> said to open SYSTEM > ADMINISTRATION >
> NETWORK, but I
> >> couldn't find the NETWORK menu item.
> >> >
> >> > I read YourSystem.txt, looked and found a VPN
> WIRED
> >> item - Auto eth0, I deleted it but it keeps
> reappearing when
> >> I reboot.
> >> >
> >> > How can I tell if the drivers are loading?
>  Where do
> >> I go from here?
> >> >
> >> > Thanks for the help.
> >> >
> >> > Regards,
> >> > Dave
> >> >
> >> >
> >> > --- On Thu, 3/19/09, Antonio Olivares
> >> <olivares14031@xxxxxxxxx> wrote:
> >> >
> >> >> From: Antonio Olivares
> >> <olivares14031@xxxxxxxxx>
> >> >> Subject: Re: David Ellis, USA, Kernel
> 2.6.27-7
> >> Generic
> >> >> To: discuss@xxxxxxxxxxxxx,
> davesjunk@xxxxxxxxxx
> >> >> Date: Thursday, March 19, 2009, 8:58 PM
> >> >> David,
> >> >>
> >> >> Your modem appears to be supported by
> agrsm
> >> package:
> >> >>
> >> >>
> >>
> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/agrsm-2.6.27-7-generic_2.6.27-7.14_i386.deb
> >> >>
> >> >> Read YourSystem.txt carefully and follow
> the
> >> instructions
> >> >> therein.  Report back if you have
> trouble.
> >> >>
> >> >> If the modem is non responsive after you
> have
> >> installed the
> >> >> driver.  Follow the directions that
> scanModem
> >> provided:
> >> >>
> >> >> >  03:0a.0    11c1:0620      
> 11c1:0620
> >>       Communication controller:
> >> >> > Agere Systems Device 0620
> >> >> >
> >> >> >  Modem interrupt assignment and
> sharing:
> >> >> >  --- Bootup diagnostics for card in
> PCI slot
> >> 03:0a.0
> >> >> ----
> >> >> > [    0.492408] PCI: 0000:03:0a.0
> reg 10 io
> >> port:
> >> >> [de00,
> >> >> > deff]
> >> >> > [    0.492445] pci 0000:03:0a.0:
> PME#
> >> supported from
> >> >> D3hot
> >> >> > D3cold
> >> >> > [    0.492450] pci 0000:03:0a.0:
> PME#
> >> disabled
> >> >> >
> >> >> >  The PCI slot 03:0a.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.
> >> >>
> >> >> Regards,
> >> >>
> >> >> Antonio
> >> >>
> >> >>
> >> >> --- On Thu, 3/19/09, David Ticer
> >> >> <davesjunk@xxxxxxxxxx> wrote:
> >> >>
> >> >> > From: David Ticer
> >> <davesjunk@xxxxxxxxxx>
> >> >> > Subject: David Ellis, USA, Kernel
> 2.6.27-7
> >> Generic
> >> >> > To: discuss@xxxxxxxxxxxxx
> >> >> > Date: Thursday, March 19, 2009,
> 12:37 PM
> >> >> > Thanks for the help, best regards.
> >> >> >
> >> >> >
> >> >> >
> >> >> > 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.27-7-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.27-7-generic
> >> (buildd@rothera) (gcc
> >> >> > version 4.3.2 (Ubuntu
> 4.3.2-1ubuntu10) ) #1
> >> SMP Fri
> >> >> Oct 24
> >> >> > 06:42:44 UTC 2008
> >> >> >  scanModem update of:  2009_03_01
> >> >> >
> >> >> >  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 0718:0086 Imation Corp.
> >> >> > If a cellphone is not detected, see
> >> >> >
> >> >>
> >>
> http://ubuntuforums.org/archive/index.php/t-878554.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 03:0a.0,
> firmware
> >> >> information
> >> >> > and bootup diagnostics are:
> >> >> >  PCI slot   PCI ID
> >>  SubsystemID     Name
> >> >> >  ---------- ---------      
> ---------
> >>     --------------
> >> >> >  03:0a.0    11c1:0620      
> 11c1:0620
> >>       Communication controller:
> >> >> > Agere Systems Device 0620
> >> >> >
> >> >> >  Modem interrupt assignment and
> sharing:
> >> >> >  --- Bootup diagnostics for card in
> PCI slot
> >> 03:0a.0
> >> >> ----
> >> >> > [    0.492408] PCI: 0000:03:0a.0
> reg 10 io
> >> port:
> >> >> [de00,
> >> >> > deff]
> >> >> > [    0.492445] pci 0000:03:0a.0:
> PME#
> >> supported from
> >> >> D3hot
> >> >> > D3cold
> >> >> > [    0.492450] pci 0000:03:0a.0:
> PME#
> >> disabled
> >> >> >
> >> >> >  The PCI slot 03:0a.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.
> >> >> >
> >> >> >
> >> >> > For candidate card in slot 00:10.1,
> firmware
> >> >> information
> >> >> > and bootup diagnostics are:
> >> >> >  PCI slot   PCI ID
> >>  SubsystemID     Name
> >> >> >  ---------- ---------      
> ---------
> >>     --------------
> >> >> >  00:10.1    10de:026c      
> 103c:2a3e
> >>       Audio device: nVidia
> >> >> > Corporation MCP51 High Definition
> Audio
> >> >> >
> >> >> >  Modem interrupt assignment and
> sharing:
> >> >> >  22:       1964  
> IO-APIC-fasteoi
> >> ohci_hcd:usb2, HDA
> >> >> > Intel
> >> >> >  --- Bootup diagnostics for card in
> PCI slot
> >> 00:10.1
> >> >> ----
> >> >> > [    0.492097] PCI: 0000:00:10.1
> reg 10
> >> 32bit mmio:
> >> >> > [fe024000, fe027fff]
> >> >> > [    0.492129] pci 0000:00:10.1:
> PME#
> >> supported from
> >> >> D3hot
> >> >> > D3cold
> >> >> > [    0.492133] pci 0000:00:10.1:
> PME#
> >> disabled
> >> >> > [    1.512083] pci 0000:00:10.1:
> Enabling
> >> HT MSI
> >> >> Mapping
> >> >> > [   16.490500] HDA Intel
> 0000:00:10.1: PCI
> >> INT B ->
> >> >> > Link[AAZA] -> GSI 22 (level, low)
> ->
> >> IRQ 22
> >> >> > [   16.490520] HDA Intel
> 0000:00:10.1:
> >> setting latency
> >> >> > timer to 64
> >> >> >
> >> >> >  The PCI slot 00:10.1 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.17
> >> >> > The modem cards detected by
> "aplay
> >> -l"  are:
> >> >> None
> >> >> >
> >> >> >
> >> >> > The /proc/asound/pcm file reports:
> >> >> > -----------------------
> >> >> > 00-02: ALC883 Analog : ALC883 Analog
> :
> >> capture 1
> >> >> > 00-01: ALC883 Digital : ALC883
> Digital :
> >> playback 1
> >> >> > 00-00: ALC883 Analog : ALC883 Analog
> :
> >> playback 1 :
> >> >> capture
> >> >> > 1
> >> >> >
> >> >> > about /proc/asound/cards:
> >> >> > ------------------------
> >> >> >  0 [NVidia         ]: HDA-Intel
> - HDA
> >> NVidia
> >> >> >                       HDA
> NVidia
> >> at 0xfe024000 irq 22
> >> >> >
> >> >> >  PCI slot 00:10.1 has a High
> Definition
> >> Audio Card
> >> >> >  The drivers are in the kernel
> modules tree
> >> at:
> >> >> >
> >> >> >
> >> >>
> >>
> /lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko
> >> >> > UNEXPECTED HDA diagnostic outcome.
> >> >> > === Finished firmware and bootup
> diagnostics,
> >> next
> >> >> deducing
> >> >> > cogent software. ===
> >> >> >
> >> >> > Predictive  diagnostics for card in
> bus
> >> 03:0a.0:
> >> >> >     Modem chipset  detected on
> >> >> > NAME="Communication controller:
> Agere
> >> Systems
> >> >> Device
> >> >> > 0620"
> >> >> > CLASS=0780
> >> >> > PCIDEV=11c1:0620
> >> >> > SUBSYS=11c1:0620
> >> >> > IRQ=10
> >> >> > IDENT=agrsm
> >> >> >
> >> >> >  For candidate modem in:  03:0a.0
> >> >> >    0780 Communication controller:
> Agere
> >> Systems Device
> >> >> 0620
> >> >> >       Primary device ID:
>  11c1:0620
> >> >> >  Support type needed or chipset:  
>  agrsm
> >> >> >
> >> >> >
> >> >> > ----------------end Softmodem
> section
> >> --------------
> >> >> >
> >> >> >
> >> >> > Predictive  diagnostics for card in
> bus
> >> 00:10.1:
> >> >> >     Modem chipset not detected on
> >> >> > NAME="Audio device: nVidia
> Corporation
> >> MCP51 High
> >> >> > Definition Audio "
> >> >> > CLASS=0403
> >> >> > PCIDEV=10de:026c
> >> >> > SUBSYS=103c:2a3e
> >> >> > IRQ=22
> >> >> > HDA=10de:026c
> >> >> > SOFT=10de:026c.HDA
> >> >> >
> >> >> >
> >> >> >  High Definition Audio (HDA) cards
> MAY host
> >> a modem
> >> >> chip in
> >> >> > their Subsystem,
> >> >> >  and many are supported by the ALSA
> >> audio+modem driver
> >> >> > snd-hda-intel
> >> >> >  A modem was not detected on HDA
> card
> >> 10de:026c.
> >> >> >  If another modem card is present,
> then most
> >> likely
> >> >> > 10de:026c does not host a modem.
> >> >> >  If another modem card has not been
> >> detected, then
> >> >> > possibilities are:
> >> >> >     1) A Conexant modem chip is
> present on
> >> 10de:026c, as
> >> >> > Conexant chips
> >> >> >  are frequently not detectable by
> ALSA
> >> diagnostics
> >> >> >     gedit Modem/ModemData.txt
> >> >> > 2) The modem may be of the older
> non-PCI
> >> Controller
> >> >> Chipset
> >> >> > (hardware) type.
> >> >> > Try detection with Root permission:
> >> >> >     sudo wvdialconf
>  /etc/wvdial.conf
> >> >> >
> >> >> >  For candidate modem in:  00:10.1
> >> >> >    0403 Audio device: nVidia
> Corporation
> >> MCP51 High
> >> >> > Definition Audio
> >> >> >       Primary device ID:
>  10de:026c
> >> >> >     Subsystem PCI_id  103c:2a3e
> >> >> >     Softmodem codec or chipset
> from
> >> diagnostics:
> >> >> >
> >>  from    Archives:
> >> >> >
> >> >> >
> >> >> >
> >> >> > Support type needed or chipset:
> >> >> >
> >> >> > Support can likely be achieved
> through two
> >> mutually
> >> >> > exclusive alternatives:
> >> >> > 1) The hsfmodem software for
> Conexant chipset
> >> modems:
> >> >> Read
> >> >> > DOCs/Conexant.txt
> >> >> > The following ALSA alternative
> CANNOT work
> >> with
> >> >> Conexant
> >> >> > modems.
> >> >> >
> >> >> > 2) An ALSA modem driver plus
> slmodemd.  Read
> >> >> > DOCs/Smartlink.txt for details, and
> >> >> > to test get the package
> >> SLMODEMD.gcc4.3.tar.gz from:
> >> >> >
> >>
> http://linmodems.technion.ac.il/packages/smartlink/
> >> >> >
> >> >> > ----------------end Softmodem
> section
> >> --------------
> >> >> > 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.2
> >> >> >              and the compiler
> used in
> >> kernel assembly:
> >> >> > 4.3.2
> >> >> >
> >> >> >  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.27-7-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 273064
> 2008-10-15
> >> 20:51
> >> >> > /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
> >> >> > 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:
> >> >> > slmodemd created symbolic link
> /dev/ttySL0:
> >> >> >      Within /etc/udev/ files:
> >> >> >
> >> >> >      Within /etc/modprobe.conf
> files:
> >> >> > /etc/modprobe.d/alsa-base:options
> >> snd-atiixp-modem
> >> >> index=-2
> >> >> > /etc/modprobe.d/alsa-base:options
> >> snd-via82xx-modem
> >> >> > index=-2
> >> >> > /etc/modprobe.d/blacklist-modem:#
> Uncomment
> >> these
> >> >> entries
> >> >> > in order to blacklist unwanted modem
> drivers
> >> >> > /etc/modprobe.d/blacklist-modem:#
> blacklist
> >> >> > snd-atiixp-modem
> >> >> > /etc/modprobe.d/blacklist-modem:#
> blacklist
> >> >> > snd-via82xx-modem
> >> >> >      Within any ancient
> /etc/devfs files:
> >> >> >
> >> >> >      Within ancient kernel 2.4.n
> >> /etc/module.conf
> >> >> files:
> >> >> >
> >> >> > --------- end modem support lines
> --------
> >> >
> >


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

  Powered by Linux