Re: safetycopy, USA, kernel 2.6.24-16-generic

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

 



I didn't explicitly install any of the dependencies as I was under the impression that the installation of penggy would complain if I was missing something necessary. I did download all the dependencies just in case, so I do have them.

Also, I made a mistake with something. In the penggy configuration file, there is an option to set a protocol to use. It defaults to p3, but I was getting an error message with that so I changed it to FLAP. The 'Segmentation fault' occurred with FLAP set as the protocol. This morning I've been playing around with things and noticed that there was a comment saying that FLAP support wasn't yet implemented with penggy, so I changed it back to p3 and am now getting the original error message:

Unable to register P3 protocol functions, access is not connected

Here's the full output from penggy on the command line:

safetycopy@safetycopy:~$ sudo penggy
Using /dev/ttySM0 device...
Dialing provider...
Dialing **********
Connection at 16800b/s done.
Executing chat script (/usr/share/penggy/chat/aolnet.scm)...
Script: String 'UQKT2' matched
Script: String 'Username' matched
Script: Send 'aol '
Script: String 'Password' matched
Script: Send 'aol '
Script: String 'Connected' matched
Script: Chat success
Chat success, connected...
Unable to register P3 protocol functions, access is not connected
engine - No data to wait
Server drop the connection.

Marvin Stodolsky wrote:
Are all the package peggy dependent on installed:
#

debconf (>= 0.5)
    Debian configuration management system
or debconf-2.0
    virtual package provided by cdebconf, cdebconf-udeb, debconf

#

dep: guile-1.6-libs
    Main Guile libraries

#

dep: libc6 (>= 2.5-0ubuntu1)
    GNU C Library: Shared libraries
    also a virtual package provided by libc6-udeb

#

dep: libguile-ltdl-1
    Guile's patched version of libtool's libltdl

#

dep: libqthreads-12 [i386]
    QuickThreads library for Guile



On Fri, Jul 11, 2008 at 7:12 AM, safetycopy <safetycopy@xxxxxxxxx> wrote:
I downloaded penggy from http://packages.ubuntu.com/

Marvin Stodolsky wrote:
RE: I tried using penggy from the packages
which packages?

On Thu, Jul 10, 2008 at 2:55 PM, safetycopy <safetycopy@xxxxxxxxx> wrote:

OK... I'm so close I can taste it! :-)

I tried using penggy from the packages and it seems I'm now being
authenticated properly, but I'm getting a 'segmentation fault'. Output
from
running penggy from command line is:

Dialing provider...
Dialing ***********
Connection at 19200b/s done.
Executing chat script (/usr/share/penggy/chat/aolnet.scm)...
Script: String 'UQKT2' matched
Script: String 'Username' matched
Script: Send 'aol '
Script: String 'Password' matched
Script: Send 'aol '
Script: String 'Connected' matched
Script: Chat success
Chat success, connected...
Segmentation fault

Marvin Stodolsky wrote:

RE:  Default Gateway:   172.165.144.109
belongs to America On Line,  So your domain name is likely aol.net,
maybe aol.com

See http://www.yolinux.com/TUTORIALS/LinuxTutorialAOL.html
about additional software needed to CONNECT.

MarvS


On Thu, Jul 10, 2008 at 4:14 AM, safetycopy <safetycopy@xxxxxxxxx>
wrote:


*C:\Documents and Settings\gothy>route PRINT *


===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 03 8a 00 00 11 ...... WAN Network Driver - Packet Scheduler
Miniport
0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface


===========================================================================


===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface
 Metric
      0.0.0.0          0.0.0.0  172.165.144.109  172.165.144.109      1
    127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
  169.254.0.0      255.255.0.0  169.254.101.152  169.254.101.152
 30
 169.254.101.152  255.255.255.255        127.0.0.1       127.0.0.1
30
 169.254.255.255  255.255.255.255  169.254.101.152  169.254.101.152
 30
 172.165.144.109  255.255.255.255        127.0.0.1       127.0.0.1
50
 172.165.255.255  255.255.255.255  172.165.144.109  172.165.144.109
 50
 209.247.22.65  255.255.255.255  172.165.144.109  172.165.144.109
 1
    224.0.0.0        240.0.0.0  169.254.101.152  169.254.101.152
 30
    224.0.0.0        240.0.0.0  172.165.144.109  172.165.144.109      1
 255.255.255.255  255.255.255.255  169.254.101.152  169.254.101.152
 1
 255.255.255.255  255.255.255.255  172.165.144.109  172.165.144.109
 1
Default Gateway:   172.165.144.109


===========================================================================
Persistent Routes:
 None
*

Marvin Stodolsky wrote:


Try

route PRINT *

On Wed, Jul 9, 2008 at 3:57 AM, safetycopy <safetycopy@xxxxxxxxx>
wrote:



Hey Marvin,

Thanks again for the reply... I've tried contacting my ISP, but
they're
beyond unhelpful - I get the impression they only want me to use
their
proprietary software :(

Here's the output from ROUTE:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\gothy>route

Manipulates network routing tables.

ROUTE [-f] [-p] [command [destination]
             [MASK netmask]  [gateway] [METRIC metric]  [IF
interface]

 -f           Clears the routing tables of all gateway entries.  If
this
is
          used in conjunction with one of the commands, the tables
are
          cleared prior to running the command.
 -p           When used with the ADD command, makes a route
persistent
across
          boots of the system. By default, routes are not preserved
          when the system is restarted. Ignored for all other
commands,
          which always affect the appropriate persistent routes. This
          option is not supported in Windows 95.
 command      One of these:
            PRINT     Prints  a route
            ADD       Adds    a route
            DELETE    Deletes a route
            CHANGE    Modifies an existing route
 destination  Specifies the host.
 MASK         Specifies that the next parameter is the 'netmask'
value.
 netmask      Specifies a subnet mask value for this route entry.
          If not specified, it defaults to 255.255.255.255.
 gateway      Specifies gateway.
 interface    the interface number for the specified route.
 METRIC       specifies the metric, ie. cost for the destination.

All symbolic names used for destination are looked up in the network
database
file NETWORKS. The symbolic names for gateway are looked up in the
host
name
database file HOSTS.

If the command is PRINT or DELETE. Destination or gateway can be a
wildcard,
(wildcard is specified as a star '*'), or the gateway argument may be
omitted.

If Dest contains a * or ?, it is treated as a shell pattern, and only
matching destination routes are printed. The '*' matches any string,
and '?' matches any one char. Examples: 157.*.1, 157.*, 127.*, *224*.
Diagnostic Notes:
 Invalid MASK generates an error, that is when (DEST & MASK) != DEST.
 Example> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1 IF 1
        The route addition failed: The specified mask parameter is
invalid.
(Destination & Mask) != Destination.

Examples:

 > route PRINT
 > route ADD 157.0.0.0 MASK 255.0.0.0  157.55.80.1 METRIC 3 IF 2
        destination^      ^mask      ^gateway     metric^    ^
                                                    Interface^
 If IF is not given, it tries to find the best interface for a given
 gateway.
 > route PRINT
 > route PRINT 157*          .... Only prints those matching 157*
 > route CHANGE 157.0.0.0 MASK 255.0.0.0 157.55.80.5 METRIC 2 IF 2

 CHANGE is used to modify gateway and/or metric only.
 > route PRINT
 > route DELETE 157.0.0.0
 > route PRINT

C:\Documents and Settings\gothy>

Marvin Stodolsky wrote:



Under a Microsoft boot, dialup
open the command (DOS) console. Enter
ROUTE

Send me the response.

Or just call up your IP and ask him.

MarvS



On Tue, Jul 8, 2008 at 10:16 AM, safetycopy <safetycopy@xxxxxxxxx>
wrote:




Thanks Marvin, got that going!!!

Unfortunately, now I'm having a problem that I think is ISP
related...
Can't
seem to get my username/password authenticated as I don't know the
domain...
I'm using Netscape Connect which is complete crap, but I don't have
any
choice... I came across this old software called Penggy but that
seems
to
be
defunct now... Any ideas, or am I going beyond the scope of this
list
(ideologically, not technically, speaking!) :-)

Marvin Stodolsky wrote:




Safety,

For 11c1:044e   Communication controller: Agere Systems  LT
WinModem
martian-full-20080625.tar.gz from

http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
is the modem code package you will need.
Also get the MarsTest.txt, though it needs and update in some
details.

But before using it,  the Ubuntu  linux-libc-dev  libc6-dev
packages
must  be installed,
for additional compiling support.
Put the Ubuntu Hardy  install CD in place and:
$ sudo apt-get install linux-libc-dev  libc6-dev

If the packages are not on the install CD,
Start at http://packages.ubuntu.com/
Search for libc6-dev  in the Hardy release
You need to download the packages for  linux-libc-dev and
libc6-dev
Both can be co-installed with
$ sudo dpkg -i li*.deb

Now you can start working with the martian package.  Unpack it
with:
$ tar zxf martian*.tar.gz
Move into the new folder:
$ cd martian-full-20080625
Look around
$ ls

$ make
if successful will will assembly a driver martian_dev.ko and
martian_modem, a smart manager.  Install them with:
$ sudo make install.

At this stage, you can
$ martian_modem --help

Reboot and rerun
$ ./scanModem
There is an outstanding problem that





The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not
functional!!
The CPU cannot control the modem until this situation is
corrected!!





But possible installation of the software may cure it.
If not, we will provide additional guidance then.

This stuff is only arcane the 1st time through.
Keep the faith!

MarvS
scanModem maintainer

On Tue, Jul 8, 2008 at 3:10 AM, safetycopy <safetycopy@xxxxxxxxx>
wrote:





Hi, I'm completely new to Linux (I'm using Hardy 8.04) and am
trying
to
get
my modem working. I used scanModem and the output is included
below.
Please
make any instructions 'for dummies' as I'm a total beginner!
-------------------------
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.24-16-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.24-16-generic (buildd@palmer) (gcc
version
4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008
scanModem update of:  2008_06_28

There are no blacklisted modem drivers in /etc/modprobe*  files
Attached USB devices are:
ID 03f0:1016 Hewlett-Packard Jornada 548 / iPAQ HW6515 Pocket PC
ID 045e:0039 Microsoft Corp. IntelliMouse Optical
ID 109f:7148 eSOL Co., Ltd

USB modems not recognized

For candidate card in slot 01:0b.0, firmware information and
bootup
diagnostics are:
PCI slot    PCI ID        SubsystemID    Name
----------    ---------    ---------    --------------
01:0b.0    11c1:044e    1235:044e    Communication controller:
Agere
Systems
LT WinModem

Modem interrupt assignment and sharing:
===================================
The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not
functional!!
The CPU cannot control the modem until this situation is
corrected!!
Possible corrections are:
 1) Within the boot up BIOS, change from a Windows to a
non-PNP/Other
Operating System type.
 Instructions for accessing BIOS are at:
 http://linmodems.technion.ac.il/resources.html within:
 Additional
Resourcces.
 2a) Add an option "pci=routeirq" to the kernel boot up line.
 Here is an example paragraph from  /boot/grub/menu.lst :
 title           Ubuntu, kernel 2.6.15-26-686
 root            (hd0,6)
 kernel          /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro
pci=routeirq
 initrd          /boot/initrd.img-2.6.15-26-686
 savedefault
 2b) Same as above, but use "pollirq" instead of "pci=routeirq".
 3) Within some BIOS setups, IRQ assignments can be changed.
 4) On non-laptop systems, moving the modem card to another slot
has
helped.
 5) Sometimes upgrading the kernel changes IRQ assignment.
=====================================

--- Bootup diagnostics for card in PCI slot 01:0b.0 ----

=== Finished firmware and bootup diagnostics, next deducing
cogent
software.
===

Predictive diagnostics for card in bus 01:0b.0:
 Modem chipset  detected on
NAME="Communication controller: Agere Systems LT WinModem "
CLASS=0780
PCIDEV=11c1:044e
SUBSYS=1235:044e
IRQ=255
IDENT=Agere.DSP

For candidate modem in:  01:0b.0
 0780 Communication controller: Agere Systems LT WinModem
 Primary device ID:  11c1:044e
Support type needed or chipset:    Agere.DSP


----------------end Softmodem section --------------

The modem has a Lucent/Agere/LSI Mars or Apollo DSP (digital
signal
processing) chipset.
Support packages for 2.6.n kernels are at:


http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
,
with
current update martian-full-20071011.tar.gz

See DOCs/AgereDSP.txt for Details.


Vendor 11c1 is Lucent Technologies with modem technology now
under
LSI
Inc.
Their Linux  code developer/maintainer is Soumyendu Sarkar.
Support
for
a
chipset and its
continued maintenance is only initiated at the request of a major
chipset
buyer,
or comparable sponsor. Several different  modem chipset types
 are
produced:
with varying support under Linux.
Device ID  Support        Name           Comment
---------  -------------  -----------
 -----------------------------
0480       serial drivers Venus           controller chipset
1673JV7
0440-045d  martian        Mars/Apollo     DSP (digital signal
processing)
chipsets
0462       none           56K.V90/ADSL Wildwire
048d none                  SV2P            soft modem
048(c or f) AGRSM         SV2P            soft modem
0600       none           soft modem, very few in the field.
0620       AGRSM          Pinball  soft modem, in some HP desktop
PCs
011c11040  AGRSM_RedFlag  Softmodem on some High Definition Audio
cards,
support only for Red Flag kernel 2.6.21-20
062(1-3)   none           SV92PP,Pinball  soft modem, in some HP
desktop
PCs

martian - At


http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
AGRSM - At http://linmodems.technion.ac.il/packages/ltmodem/sv92/
,
the
agrsm-20080203.tar.gz
AGRSM_RedFlag at  At
http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
The  suse-10-2a.tar.gz has newer Agere/LSI code, but there are
compiling
problems with newer kernels/

0x044e -- Mars 3 Mercury data fax only
-------------- end Agere Systems section -------------------

Completed candidate modem analyses.

The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.2.3
      and the compiler used in kernel assembly: 4.2.3



Minimal compiling resources appear complete:
 make utility - /usr/bin/make
 Compiler version 4.2
 linuc_headers base folder /lib/modules/2.6.24-16-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 libc6-dev
(and
for
Debian/Ubuntu,
linux-libc-dev). 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 269256 2007-10-04 15:57 /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/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
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base: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 --------








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

  Powered by Linux