RE: FW: Brian, CANADA, kernel 2.6.35-22-generic

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


Gentlemen,

Well I've tried all of your suggestions. I keep getting the same message.
Command not found. So either I'm missing something fundamental in your
instructions, or the martian modem development simply will not work on my
system. Unfortunately, I'm left with little alternative but to give learning
Linux a miss and revert to a Windows-based system. I'd rather not, but what
else can I do? I must have Internet, and dial-up is all that's available
here.

Thank-you all for your help!

Brian

-----Original Message-----
From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] 
Sent: May 14, 2011 1:26 PM
To: Antonio Olivares
Cc: brackishfish@xxxxxxxxx
Subject: Re: FW: Brian, CANADA, kernel 2.6.35-22-generic

Brıan

Compile the martıan_dev on your 64 bıt system.
Your should be able to use avaılable pre-compıled (32 bıt)
martıan_modem wıth ıt, as ıt ıs a utılıty and not a drıver whıch must
be kernel and gcc compıler matched.  If not already ınstalled,
ınstallatıon of the 32 bıt lıbc6-dev package wıll be necessary to
support martıan_modem.

MarvS

On Thu, May 12, 2011 at 7:39 PM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
> Brian,
>
> I forwarded a message CC'd to Marv maintainer of scanModem.  He can
> best advice you, although he might be very busy these days.  I don't
> know if any users out there have a working martian_dev in 64 bits.
>
> I apologize for not being able to help you as I don't have an ubuntu
> system to compile a martian_dev.ko with 32 bit martian_modem so you
> could have a working connection.
>
> Regards,
>
> Antonio
>
> On Thu, May 12, 2011 at 9:17 AM, Brian <brackishfish@xxxxxxxxx> wrote:
>> Hello,
>>
>> Can anyone help me? I am a new Linux user in a location with only dial-up
>> Internet available. I need to get this modem working on my new system and
am
>> having trouble. Please see below for a sequence of detailed information.
>>
>> Thank-you!
>>
>> Brian
>>
>>
>>
>> -----Original Message-----
>> From: Brian [mailto:brackishfish@xxxxxxxxx]
>> Sent: May 11, 2011 12:54 PM
>> To: 'Antonio Olivares'
>> Subject: RE: Brian, CANADA, kernel 2.6.35-22-generic
>>
>> Hello,
>>
>> I tried your suggestion. I downloaded the file
>> martian-modem-source_20080625-1_i386.deb which I found at the link
>> indicated. Copied it to the directory /usr/sbin, then issued the command
>> sudo -depmod -a, as instructed. This produced errors, so I tried sudo
depmod
>> -a. This produced no response. I then issued the command sudo
martian_modem.
>> This produced command not found.
>>
>> Suggestions?
>>
>>
>> -----Original Message-----
>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>> Sent: May 9, 2011 9:40 PM
>> To: brackishfish@xxxxxxxxx
>> Cc: Linmodems; Marvin Stodolsky
>> Subject: Re: Brian, CANADA, kernel 2.6.35-22-generic
>>
>> Brian,
>>
>> You are indeed correct.  Something like this happened to me a while
>> ago and Marv was very kind to provide a precompiled martian_modem that
>> was copied over to /usr/sbin/ , ran depmod -a in your case it would be
>> sudo -depmod -a and then martian modem would work.  I don't have
>> experience with a new package that exists for Ubuntu/Debian distros
>> called maritan-modem-src
>>
>> http://packages.ubuntu.com/da/lucid/martian-modem-source
>>
>> don't know for sure if the have a working martian_dev.ko
>>
>> Marv,
>> are there any success stories with this new package, and if so does it
>> make a good working driver for 64 bit Ubuntu
>>
>>
>> Regards,
>>
>> Antonio
>> On Mon, May 9, 2011 at 8:12 PM, Brian <brackishfish@xxxxxxxxx> wrote:
>>> Well I tried it all again. I'm getting the same result. This is a
summary
>> of
>>> the commands I entered in the terminal session:
>>>
>>> bri@NORMAN:~/Desktop$ tar -zxvf martian-full-20100123.tar.gz
>>> martian-full-20100123/
>>> martian-full-20100123/sample.txt
>>> martian-full-20100123/Cleaning.txt
>>> martian-full-20100123/Concept
>>> martian-full-20100123/kmodule/
>>> martian-full-20100123/kmodule/Files.txt
>>> martian-full-20100123/kmodule/mixspinlock.h
>>> martian-full-20100123/kmodule/marsio.h
>>> martian-full-20100123/kmodule/marsio.c
>>> martian-full-20100123/kmodule/martian.c
>>> martian-full-20100123/kmodule/mfifo.h
>>> martian-full-20100123/kmodule/fifo.h
>>> martian-full-20100123/kmodule/kmodulefiles.txt
>>> martian-full-20100123/kmodule/kmartian.h
>>> martian-full-20100123/kmodule/martian_ids.c
>>> martian-full-20100123/kmodule/Makefile
>>> martian-full-20100123/kmodule/mfifo.c
>>> martian-full-20100123/scripts/
>>> martian-full-20100123/scripts/martian
>>> martian-full-20100123/scripts/automate.sh
>>> martian-full-20100123/scripts/wv.conf
>>> martian-full-20100123/scripts/remove_outdated.sh
>>> martian-full-20100123/scripts/martian.in
>>> martian-full-20100123/ChangeLog
>>> martian-full-20100123/INSTALL
>>> martian-full-20100123/martian.h
>>> martian-full-20100123/modem/
>>> martian-full-20100123/modem/watch3.gdb
>>> martian-full-20100123/modem/pty.c
>>> martian-full-20100123/modem/watch.gdb
>>> martian-full-20100123/modem/main.c
>>> martian-full-20100123/modem/sysdep.c
>>> martian-full-20100123/modem/log.h
>>> martian-full-20100123/modem/tweakrelocsdynamic.c
>>> martian-full-20100123/modem/elf386tweakrelocs.c
>>> martian-full-20100123/modem/link.c
>>> martian-full-20100123/modem/coresubst.c
>>> martian-full-20100123/modem/tweakcore.sh
>>> martian-full-20100123/modem/debug_script.in
>>> martian-full-20100123/modem/watch2.gdb
>>> martian-full-20100123/modem/session.c
>>> martian-full-20100123/modem/isr.c
>>> martian-full-20100123/modem/coreadd.c
>>> martian-full-20100123/modem/dumpers.c
>>> martian-full-20100123/modem/mixspinlock.h
>>> martian-full-20100123/modem/mport.h
>>> martian-full-20100123/modem/watch4.gdb
>>> martian-full-20100123/modem/log.c
>>> martian-full-20100123/modem/core.h
>>> martian-full-20100123/modem/profile.c
>>> martian-full-20100123/modem/mport.c
>>> martian-full-20100123/modem/modemfiles.txt
>>> martian-full-20100123/modem/watch.h
>>> martian-full-20100123/modem/README
>>> martian-full-20100123/modem/Makefile
>>> martian-full-20100123/modem/ltmdmobj.o
>>> martian-full-20100123/modem/smp.c
>>> martian-full-20100123/modem/ASWMLICENSE
>>> martian-full-20100123/modem/overriden_core_functions
>>> martian-full-20100123/modem/common.h
>>> martian-full-20100123/modem/core_if.c
>>> martian-full-20100123/modem/main.h
>>> martian-full-20100123/modem/sysdep.h
>>> martian-full-20100123/README
>>> martian-full-20100123/Makefile
>>> bri@NORMAN:~/Desktop$ cd kmodule
>>> bash: cd: kmodule: No such file or directory
>>> bri@NORMAN:~/Desktop$ dir
>>> martian-full-20100123  martian-full-20100123.tar.gz
>>> bri@NORMAN:~/Desktop$ cd martian-full-20100123
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ dir
>>> ChangeLog     Concept  kmodule   martian.h  README      scripts
>>> Cleaning.txt  INSTALL  Makefile  modem      sample.txt
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ cd kmodule
>>> bri@NORMAN:~/Desktop/martian-full-20100123/kmodule$ make -C kmodule/
>> modules
>>> make: *** kmodule/: No such file or directory.  Stop.
>>> bri@NORMAN:~/Desktop/martian-full-20100123/kmodule$ cd
>>> bri@NORMAN:~$ cd Desktop
>>> bri@NORMAN:~/Desktop$ cd martian-full-20100123
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ dir
>>> ChangeLog     Concept  kmodule   martian.h  README      scripts
>>> Cleaning.txt  INSTALL  Makefile  modem      sample.txt
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ make -C kmodule/ modules
>>> make: Entering directory
`/home/bri/Desktop/martian-full-20100123/kmodule'
>>> make -C /lib/modules/2.6.35-22-generic/build
>>> M="/home/bri/Desktop/martian-full-20100123/kmodule"  modules
>>> make[1]: Entering directory `/usr/src/linux-headers-2.6.35-22-generic'
>>>  CC [M]  /home/bri/Desktop/martian-full-20100123/kmodule/martian.o
>>> /home/bri/Desktop/martian-full-20100123/kmodule/martian.c: In function
>>> 'martian_isr':
>>> /home/bri/Desktop/martian-full-20100123/kmodule/martian.c:135: warning:
>>> value computed is not used
>>>  CC [M]  /home/bri/Desktop/martian-full-20100123/kmodule/marsio.o
>>> /home/bri/Desktop/martian-full-20100123/kmodule/marsio.c:358: warning:
>>> 'mars_read_register_rem' defined but not used
>>> /home/bri/Desktop/martian-full-20100123/kmodule/marsio.c:371: warning:
>>> 'mars_write_register_rem' defined but not used
>>>  CC [M]  /home/bri/Desktop/martian-full-20100123/kmodule/mfifo.o
>>>  LD [M]  /home/bri/Desktop/martian-full-20100123/kmodule/martian_dev.o
>>>  Building modules, stage 2.
>>>  MODPOST 1 modules
>>>  CC    
 /home/bri/Desktop/martian-full-20100123/kmodule/martian_dev.mod.o
>>>  LD [M]  /home/bri/Desktop/martian-full-20100123/kmodule/martian_dev.ko
>>> make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-22-generic'
>>> make: Leaving directory
`/home/bri/Desktop/martian-full-20100123/kmodule'
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ sudo make -C kmodule/
install
>>> [sudo] password for bri:
>>> make: Entering directory
`/home/bri/Desktop/martian-full-20100123/kmodule'
>>> make -C /lib/modules/2.6.35-22-generic/build
>>> M="/home/bri/Desktop/martian-full-20100123/kmodule" modules_install
>>> make[1]: Entering directory `/usr/src/linux-headers-2.6.35-22-generic'
>>>  INSTALL /home/bri/Desktop/martian-full-20100123/kmodule/martian_dev.ko
>>>  DEPMOD  2.6.35-22-generic
>>> make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-22-generic'
>>> if ! /sbin/modprobe -nq martian_dev ; then /sbin/depmod -a; fi
>>> make: Leaving directory
`/home/bri/Desktop/martian-full-20100123/kmodule'
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ sudo modprobe martian_dev
>>> bri@NORMAN:~/Desktop/martian-full-20100123$ sudo martian_modem
>>> sudo: martian_modem: command not found
>>> bri@NORMAN:~/Desktop/martian-full-20100123$
>>>
>>> Thank you.
>>>
>>> -----Original Message-----
>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>>> Sent: May 9, 2011 6:38 PM
>>> To: brackishfish@xxxxxxxxx
>>> Cc: Linmodems
>>> Subject: Re: Brian, CANADA, kernel 2.6.35-22-generic
>>>
>>> Brian,
>>>
>>> $ make
>>> $ sudo make install
>>> might have worked, but instructions specifically say to run the
>>> commands I referenced, see below for a successfull compilation
>>>
>>> bash-4.1$ cd martian-full-20100123
>>> bash-4.1$ uname -r
>>> 2.6.37.6
>>> bash-4.1$ uname -a
>>> Linux GHS-E213-2 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64
>>> AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux
>>>
>>> README file:
>>>
>>> x86_64 platform.
>>> ----------------
>>>
>>> martian_modem is a 32-bit application. It can be built on x86_64 the
>>> way prescribed, but you need 32-bit development environment for that.
>>> Second option is to use binary built on i386.
>>>
>>> To compile and install module only do
>>> $ make -C kmodule/ modules
>>> $ su
>>> # make -C kmodule/ install
>>>
>>>
>>> bash-4.1$ make -C kmodule/ modules
>>> make: Entering directory
>>> `/home/olivares/Downloads/martian-full-20100123/kmodule'
>>> make -C /lib/modules/2.6.37.6/build
>>> M="/home/olivares/Downloads/martian-full-20100123/kmodule"  modules
>>> make[1]: Entering directory `/usr/src/linux-2.6.37.6'
>>>  CC [M]
 /home/olivares/Downloads/martian-full-20100123/kmodule/martian.o
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/martian.c: In
>>> function 'martian_isr':
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/martian.c:135:27:
>>> warning: value computed is not used
>>>  CC [M]  /home/olivares/Downloads/martian-full-20100123/kmodule/marsio.o
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/marsio.c:358:11:
>>> warning: 'mars_read_register_rem' defined but not used
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/marsio.c:371:13:
>>> warning: 'mars_write_register_rem' defined but not used
>>>  CC [M]  /home/olivares/Downloads/martian-full-20100123/kmodule/mfifo.o
>>>  LD [M]
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/martian_dev.o
>>>  Building modules, stage 2.
>>>  MODPOST 1 modules
>>>  CC
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/martian_dev.mod.o
>>>  LD [M]
>>> /home/olivares/Downloads/martian-full-20100123/kmodule/martian_dev.ko
>>> make[1]: Leaving directory `/usr/src/linux-2.6.37.6'
>>> make: Leaving directory
>>> `/home/olivares/Downloads/martian-full-20100123/kmodule'
>>> bash-4.1$
>>>
>>> Then running install would install the martian driver successfully and
>>> $ sudo modprobe martian_dev for Debian/Ubuntu distros
>>> # sudo modprobe martian_dev in non Debian/Ubuntu distros
>>> $ sudo martian_modem or
>>> # martian_modem
>>>
>>> Try to do it but with :
>>>
>>> $ make clean
>>> $ make -C kmodule/ modules
>>> $ sudo make -C kmodule/ install
>>>
>>> then
>>> $ sudo modprobe martian_dev
>>> $ sudo martian_modem
>>>
>>> leave it running then run
>>> $ sudo wvdialconf /etc/wvdial.conf
>>> to see if it finds /dev/ttySM0 as the modem port.
>>>
>>> Regards,
>>>
>>> Antonio
>>>
>>>
>>>
>>>
>>> On Mon, May 9, 2011 at 4:26 PM, Brian <brackishfish@xxxxxxxxx> wrote:
>>>> Yes I did, but with some caveats. The command "$ make -C kmodule
>> /modules"
>>>> yielded errors. I looked at the README file, as you suggested, and it
>>>> directed me to the developer's page
>> (http://martian.barrelsoutofbond.org),
>>>> where I found revisions to the commands. I used the commands "$ make
>> all",
>>>> and "# make install". So I may have made an error.
>>>>
>>>> I have since run "$ which martian_modem", and it has returned no output
>>>> whatsoever.
>>>>
>>>> -----Original Message-----
>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>>>> Sent: May 9, 2011 3:41 PM
>>>> To: brackishfish@xxxxxxxxx
>>>> Cc: Linmodems
>>>> Subject: Re: Brian, CANADA, kernel 2.6.35-22-generic
>>>>
>>>> Brian,
>>>>
>>>> You did run all the commands without problems:
>>>>
>>>> $ tar -zxvf martian-full-20100123.tar.gz
>>>> $ cd martian-full-20101023
>>>>
>>>> Since your machine is 64 bit, you will need different comands than 32
>> bit:
>>>> $ cd kmodule
>>>> $ make -C kmodule/ modules
>>>> $ su
>>>> # make -C kmodule/ install
>>>>
>>>> or similar command.  Check README for instructions in case I made a
>>>> mistake/typo.
>>>>
>>>> then after successfull install run
>>>> $ sudo modprobe martian_dev
>>>>
>>>> Before you did
>>>> $ sudo martian_modem
>>>>
>>>> You did get to do:
>>>> ``$ sudo modprobe martian_dev``
>>>> right?
>>>>
>>>> If you did, then would you post output of
>>>> $ which martian_modem
>>>> and send to list(discuss@xxxxxxxxxxxxx)
>>>>
>>>> Regards,
>>>>
>>>> Antonio
>>>>
>>>> On Mon, May 9, 2011 at 2:23 PM, Brian <brackishfish@xxxxxxxxx> wrote:
>>>>> OK. I've followed your instructions, and have made it as far as the
>>>> command
>>>>> $ sudo martian_modem. At this point the machine returns "command not
>>>> found".
>>>>> Suggestions?
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>>>>> Sent: May 9, 2011 1:22 PM
>>>>> To: brackishfish@xxxxxxxxx
>>>>> Subject: Re: Brian, CANADA, kernel 2.6.35-22-generic
>>>>>
>>>>> Brian,
>>>>>
>>>>> It is a development package that was recommended when installing the
>>>>> martian modem drivers.  It might be present already on new systems?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Antonio
>>>>>
>>>>> On Mon, May 9, 2011 at 10:14 AM, Brian <brackishfish@xxxxxxxxx> wrote:
>>>>>> Thank-you Sir. I'm just collecting the required files now. What is
>>>>>> libc6-devel and what do I do with it?
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>>>>>> Sent: May 6, 2011 2:42 PM
>>>>>> To: brackishfish@xxxxxxxxx
>>>>>> Cc: discuss@xxxxxxxxxxxxx
>>>>>> Subject: Re: Brian, CANADA, kernel 2.6.35-22-generic
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> scanModem reports that your modem is an Agere DSP modem that is
>>>>>> supported through martian-full-20100123.tar.gz drivers from linmodems
>>>>>> page:
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/martian-
>>>>>> full-20100123.tar.gz
>>>>>>
>>>>>> Download it and also download: libc6-devel if not installed*
>>>>>>
>>>>>> Copy them to your linux partition and run
>>>>>> $ tar -zxvf martian-full-20100123.tar.gz
>>>>>> $ cd martian-full-20101023
>>>>>>
>>>>>> Since your machine is 64 bit, you will need different comands than 32
>>>> bit:
>>>>>> $ cd kmodule
>>>>>> $ make -C kmodule/ modules
>>>>>> $ su
>>>>>> # make -C kmodule/ install
>>>>>>
>>>>>> or similar command.  Check README for instructions in case I made a
>>>>>> mistake/typo.
>>>>>>
>>>>>> then after successfull install run
>>>>>> $ sudo modprobe martian_dev
>>>>>> $ sudo martian_modem
>>>>>>
>>>>>> leave it running and openup another terminal/tab and run without
>> quotes.
>>>>>> $ sudo wvdialconf /etc/wvdial.conf
>>>>>>
>>>>>> and add edit it with sudo priviledges
>>>>>> $ sudo gedit /etc/wvdial.conf
>>>>>>
>>>>>> and add username, password, ISP phone number and a line "Carrier
Check
>>>>>> = no" without "'s
>>>>>>
>>>>>> then try a connection.
>>>>>>
>>>>>> $ sudo wvdial
>>>>>>
>>>>>> Report back if you have questions.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Antonio
>>>>>>
>>>>>>
>>>>>> For candidate card in slot 03:05.0, firmware information and bootup
>>>>>> diagnostics are:
>>>>>>  PCI slot       PCI ID          SubsystemID     Name
>>>>>>  ----------     ---------       ---------       --------------
>>>>>>  03:05.0        11c1:0440       11c1:0440       Communication
>>> controller:
>>>>>> Agere Systems 56k WinModem
>>>>>>
>>>>>>  Modem interrupt assignment and sharing:
>>>>>>  --- Bootup diagnostics for card in PCI slot 03:05.0 ----
>>>>>> [    0.850090] pci 0000:03:05.0: reg 10: [mem 0xfebffc00-0xfebffcff]
>>>>>> [    0.850097] pci 0000:03:05.0: reg 14: [io  0xec00-0xec07]
>>>>>> [    0.850105] pci 0000:03:05.0: reg 18: [io  0xe800-0xe8ff]
>>>>>> [    0.850153] pci 0000:03:05.0: supports D2
>>>>>> [    0.850155] pci 0000:03:05.0: PME# supported from D2 D3hot D3cold
>>>>>> [    0.850159] pci 0000:03:05.0: PME# disabled
>>>>>>
>>>>>>  The PCI slot 03:05.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.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 6, 2011 at 1:05 PM, Brian <brackishfish@xxxxxxxxx> wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I am a very new Linux user, and have just installed Ubuntu 10.10 on
a
>>>> new
>>>>>>> AMD machine. I do have some very limited experience with Solaris,
and
>>>>>>> running some Unix commands. I am unfortunately in an area that only
>> has
>>>>>>> dial-up Internet service available. I need to get a modem working
and
>>>>> wish
>>>>>>> to try the Winmodem I have installed. I have installed and
>> successfully
>>>>>> run
>>>>>>> the scanmodem tool which has yielded the following output. I am
>>>> uncertain
>>>>>>> what to do next. Any assistance would be greatly appreciated.
>>>>>>>
>>>>>>> Thank-you very much for your time and attention!
>>>>>>>
>>>>>>> The following is the text of the Modemdata.txt file generated by
>>>>> scanmodem
>>>>>>> on my system:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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.35-22-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=x86_64,  Ubuntu ,  ALSA_version=1.0.23
>>>>>>> Linux version 2.6.35-22-generic (buildd@allspice) (gcc version 4.4.5
>>>>>>> (Ubuntu/Linaro 4.4.4-14ubuntu4) ) #33-Ubuntu SMP Sun Sep 19 20:32:27
>>> UTC
>>>>>>> 2010
>>>>>>>  scanModem update of:  2011_02_04
>>>>>>>
>>>>>>> Distrib_ID=Ubuntu
>>>>>>> DistribCodeName=maverick
>>>>>>> AptRepositoryStem=http://ca.archive.ubuntu.com/ubuntu/
>>>>>>>
>>>>>>>
>>>>>>> Presently install your Linux Distributions dkms package. It provides
>>> for
>>>>>>> automated driver updates,
>>>>>>> following upgrade of your kernel.  For details see
>>>>>>> http://linux.dell.com/projects.shtml#dkms
>>>>>>>
>>>>>>>
>>>>>>> Some modem drivers can only be used in 32 bit modem on x86_64
systems,
>>>>>>> while some others are competent on x86_64 Systems.  Cases are:
>>>>>>> 1)
>>> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
>>>>>>> for the snd-hda-intel audio+modem driver. Also applicable to AC97
>> modem
>>>>>>> controllers.
>>>>>>> In both cases, 32 bit libraries must be installed to support the
>>>> slmodemd
>>>>>>> helper having a precompiled 32 bit component.
>>>>>>> 2) For USB modems using the slusb.ko driver. 32 bit libraries must
be
>>>>>>> installed to support the slmodemd helper having a precompiled 32 bit
>>>>>>> component
>>>>>>> 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes
>> are
>>>>>>> x86_64 competent.
>>>>>>> 4) agrsm packages for LSI/AgereSystems softmodems are not competent
on
>>>>>>> x86_64 systems.
>>>>>>>
>>>>>>>  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 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
>>>>>>>  ID 051d:0002 American Power Conversion Uninterruptible Power Supply
>>>>>>> If a cellphone is not detected, see
>>>>>>> http://ubuntuforums.org/archive/index.php/t-878554.html
>>>>>>> A sample report is:
>>>>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
>>>>>>>
>>>>>>> If a USB modem or cellphone is attached and was not detected, please
>>>>>>> provide available information in your request to
discuss@xxxxxxxxxxxxx
>>>>>>>
>>>>>>> Candidate PCI devices with modem chips are:
>>>>>>> 03:05.0 Communication controller: Agere Systems 56k WinModem (rev
01)
>>>>>>> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
>>>>>>> 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device
[Radeon
>>> HD
>>>>>>> 4200]
>>>>>>> High Definition Audio cards can host modem chips.
>>>>>>>
>>>>>>> For candidate card in slot 03:05.0, firmware information and bootup
>>>>>>> diagnostics are:
>>>>>>>  PCI slot       PCI ID          SubsystemID     Name
>>>>>>>  ----------     ---------       ---------       --------------
>>>>>>>  03:05.0        11c1:0440       11c1:0440       Communication
>>>> controller:
>>>>>>> Agere Systems 56k WinModem
>>>>>>>
>>>>>>>  Modem interrupt assignment and sharing:
>>>>>>>  --- Bootup diagnostics for card in PCI slot 03:05.0 ----
>>>>>>> [    0.850090] pci 0000:03:05.0: reg 10: [mem 0xfebffc00-0xfebffcff]
>>>>>>> [    0.850097] pci 0000:03:05.0: reg 14: [io  0xec00-0xec07]
>>>>>>> [    0.850105] pci 0000:03:05.0: reg 18: [io  0xe800-0xe8ff]
>>>>>>> [    0.850153] pci 0000:03:05.0: supports D2
>>>>>>> [    0.850155] pci 0000:03:05.0: PME# supported from D2 D3hot D3cold
>>>>>>> [    0.850159] pci 0000:03:05.0: PME# disabled
>>>>>>>
>>>>>>>  The PCI slot 03:05.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:14.2, firmware information and bootup
>>>>>>> diagnostics are:
>>>>>>>  PCI slot       PCI ID          SubsystemID     Name
>>>>>>>  ----------     ---------       ---------       --------------
>>>>>>>  00:14.2        1002:4383       1043:836c       Audio device: ATI
>>>>>>> Technologies Inc SBx00 Azalia
>>>>>>>
>>>>>>>  Modem interrupt assignment and sharing:
>>>>>>>  16:      10435          0          5       2416   IO-APIC-fasteoi
>>>>>>> ohci_hcd:usb3, ohci_hcd:usb4, hda_intel
>>>>>>>  --- Bootup diagnostics for card in PCI slot 00:14.2 ----
>>>>>>> [    0.834264] pci 0000:00:14.2: reg 10: [mem 0xfe8f4000-0xfe8f7fff
>>>>> 64bit]
>>>>>>> [    0.834303] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
>>>>>>> [    0.834306] pci 0000:00:14.2: PME# disabled
>>>>>>> [    8.077752] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level,
>> low)
>>>>> ->
>>>>>>> IRQ 16
>>>>>>>
>>>>>>>  The PCI slot 00:14.2 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 01:05.1, firmware information and bootup
>>>>>>> diagnostics are:
>>>>>>>  PCI slot       PCI ID          SubsystemID     Name
>>>>>>>  ----------     ---------       ---------       --------------
>>>>>>>  01:05.1        1002:970f       1043:843e       Audio device: ATI
>>>>>>> Technologies Inc RS880 Audio Device [Radeon HD 4200]
>>>>>>>
>>>>>>>  Modem interrupt assignment and sharing:
>>>>>>>  19:          0         73          0      34595   IO-APIC-fasteoi
>>>>>>> ehci_hcd:usb2, hda_intel
>>>>>>>  --- Bootup diagnostics for card in PCI slot 01:05.1 ----
>>>>>>> [    0.834555] pci 0000:01:05.1: reg 10: [mem 0xfeaf4000-0xfeaf7fff]
>>>>>>> [    0.834571] pci 0000:01:05.1: supports D1 D2
>>>>>>> [    8.253772] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level,
>> low)
>>>>> ->
>>>>>>> IRQ 19
>>>>>>> [    8.253801] HDA Intel 0000:01:05.1: setting latency timer to 64
>>>>>>>
>>>>>>> === Finished firmware and bootup diagnostics, next deducing cogent
>>>>>> software.
>>>>>>> ===
>>>>>>>
>>>>>>> Predictive  diagnostics for card in bus 03:05.0:
>>>>>>>        Modem chipset  detected on
>>>>>>> NAME="Communication controller: Agere Systems 56k WinModem "
>>>>>>> CLASS=0780
>>>>>>> PCIDEV=11c1:0440
>>>>>>> SUBSYS=11c1:0440
>>>>>>> IRQ=11
>>>>>>> HDA2=00:14.2
>>>>>>> HDA2=01:05.1
>>>>>>> IDENT=Agere.DSP
>>>>>>>
>>>>>>>  For candidate modem in:  03:05.0
>>>>>>>   0780 Communication controller: Agere Systems 56k WinModem
>>>>>>>      Primary device ID:  11c1:0440
>>>>>>>  Support type needed or chipset:        Agere.DSP
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Predictive  diagnostics for card in bus 00:14.2:
>>>>>>>        Modem chipset not detected on
>>>>>>> NAME="Audio device: ATI Technologies Inc SBx00 Azalia "
>>>>>>> CLASS=0403
>>>>>>> PCIDEV=1002:4383
>>>>>>> SUBSYS=1043:836c
>>>>>>> IRQ=16
>>>>>>>
>>>>>>>  For candidate modem in:  00:14.2
>>>>>>>   0403 Audio device: ATI Technologies Inc SBx00 Azalia
>>>>>>>      Primary device ID:  1002:4383
>>>>>>>  Support type needed or chipset:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Predictive  diagnostics for card in bus 01:05.1:
>>>>>>>        Modem chipset not detected on
>>>>>>> NAME="Audio device: ATI Technologies Inc RS880 Audio Device [Radeon
HD
>>>>>>> 4200]"
>>>>>>> CLASS=0403
>>>>>>> PCIDEV=1002:970f
>>>>>>> SUBSYS=1043:843e
>>>>>>> IRQ=19
>>>>>>>
>>>>>>>  For candidate modem in:  01:05.1
>>>>>>>   0403 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon
>> HD
>>>>>>> 4200]
>>>>>>>      Primary device ID:  1002:970f
>>>>>>>  Support type needed or chipset:
>>>>>>>
>>>>>>>
>>>>>>>  Completed candidate modem analyses.
>>>>>>>
>>>>>>>  The base of the UDEV device file system is: /dev/.udev
>>>>>>>
>>>>>>>  Versions adequately match for the compiler installed: 4.4.5
>>>>>>>             and the compiler used in kernel assembly: 4.4.5
>>>>>>>
>>>>>>>  linux-headers-2.6.35-22-generic resources needed for compiling are
>> not
>>>>>>> manifestly ready!
>>>>>>>  The patch utility is needed for compiling ALSA drivers, and
possibly
>>>>>>> others.
>>>>>>>
>>>>>>>  If compiling is necessary packages must be installed, providing:
>>>>>>>         linux-headers-2.6.35-22-generic
>>>>>>>
>>>>>>>
>>>>>>> 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 321592 2010-07-09 16:10 /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
>>>>>>>
>>>>>>> For guidance on FAX usage, get from
>>>>>>> http://linmodems.technion.ac.il/packages/  get faxing.tar.gz
>>>>>>> It has samples for a modem using port /dev/ttySL0, which must be
>>> changed
>>>>>> to
>>>>>>> match your modem's port.
>>>>>>>
>>>>>>> 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.conf:# Uncomment these entries in
>> order
>>>>> to
>>>>>>> blacklist unwanted modem drivers
>>>>>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
>>>>>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
>>>>>>> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
>>>>>>> /etc/modprobe.d/alsa-base.conf: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 --------
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>




[Linux DVB]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Xfree86]     [Fedora Women]     [Linux USB]

Powered by Linux