Re: Manuel, Spain Ubuntu 8.10 kernel 2.6.27-9-generic,11c11040 success

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

 



Manuel

The modem is only sharing IRQ with:
 Modem interrupt assignment and sharing:
 22:     398465     393690   IO-APIC-fasteoi   HDA Intel

Try shutting down all ongoing audio function  before starting a modem
session with:
$ sudo /etc/init.d/pulseaudio stop
Afterward it  can restarted with:
$ sudo /etc/init.d/pulseaudio start

MarvS

On Sat, Dec 27, 2008 at 3:18 PM, Manuel Matias
<manuel.a.matias@xxxxxxxxx> wrote:
> Dear Marvin,
>
> Thank you for your patience again!
>
> On 12/27/08, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>> Manuel,
>>
>> Re:
>>> Kill Request for PID, Faking
>>> In the case of kppp it exits with "Exit status 16".
>> -------
>> This indicates it is not primarily a driver problem.
>> Rather there is some other Process competing for resources which is
>> killing the connection.
>>
>> Looking at your original ModemData.txt
>> -------------------------
>> /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
>> /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
>> /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe
>> --ignore-install ungrab-winmodem ;  modprobe --ignore-install slamr;
>> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
>> 2>/dev/null && chgrp dialout /dev/slamr0)
>> -----------------------
>> for unnecessary processes suggests the following.
>>
>> Uninstall the sl-modem-daemon package, as it is useless for your modem:
>> $ sudo apt-get --purge remove  sl-modem-daemon
>
> Done.
>
>>
>> Blacklist modem drivers not needed with:
>> $ sudo gedit /etc/modprobe.d/blacklist-modem
>> so final lines are:
>> blacklist snd-atiixp-modem
>> blacklist snd-via82xx-modem
>> blacklist snd-intel8x0m
>
> Done.
>
>>
>> Please download and used the newest scanModem and send the List the
>> ModemData.txt
>
> Please, find it enclosed:
>
>  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-9-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-9-generic (buildd@rothera) (gcc version 4.3.2
> (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
>  scanModem update of:  2008_12_25
> The modem symbolic link is /dev/modem -> /dev/ttyAGS3
> Modem drivers blocked from loading during bootup are listed in
> /etc/modprobe* file lines:
> /etc/modprobe.d/blacklist-modem:blacklist snd-atiixp-modem
> /etc/modprobe.d/blacklist-modem:blacklist snd-via82xx-modem
> /etc/modprobe.d/blacklist-modem:blacklist snd-intel8x0m
>
> Attached USB devices are:
>  ID 1d6b:0002 Linux Foundation 2.0 root hub
>  ID 174f:5932 Syntek
>  ID 1d6b:0002 Linux Foundation 2.0 root hub
>  ID 04d9:1133 Holtek Semiconductor, Inc.
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>  ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>  ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> USB modems not recognized
>
> For candidate card in slot 00:1b.0, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:1b.0        8086:293e       144d:c048       Audio device: Intel Corporation 82801I
>
>  Modem interrupt assignment and sharing:
>  22:     398465     393690   IO-APIC-fasteoi   HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [    0.524561] PCI: 0000:00:1b.0 reg 10 64bit mmio: [fc200000, fc203fff]
> [    0.524614] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [    0.524619] pci 0000:00:1b.0: PME# disabled
> [   13.320556] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
> low) -> IRQ 22
> [   13.320581] HDA Intel 0000:00:1b.0: setting latency timer to 64
>
>  The PCI slot 00:1b.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.
>
>
>
> ===== 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-00: ALC262 Analog : ALC262 Analog : playback 1 : capture 1
>
> about /proc/asound/cards:
> ------------------------
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                      HDA Intel at 0xfc200000 irq 22
>
>  PCI slot 00:1b.0 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
> /lib/modules/2.6.27-9-generic/kernel/sound/pci/hda/snd-hda-intel.ko
>  The modem codec file for the HDA card is: /proc/asound/card0/codec#1
> --------------------------------------------------------
> Codec: LSI ID 1040
> Address: 1
> Vendor Id: 0x11c11040
> Subsystem Id: 0x2118144d
> Revision Id: 0x100200
> Modem Function Group: 0x1
>
>  The audio card hosts a softmodem chip:  0x11c11040
> If not a Conexant modem, the driver
> agrmodem+agrserial+patched_snd-hda-intel with its dependent drivers:
>
> ----------
> provide audio + modem support with the modem chip residing on the subsystem.
> Any particular card can host any one of several soft modem chips.
>
> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>
> Predictive  diagnostics for card in bus 00:1b.0:
>        Modem chipset  detected on
> NAME="Audio device: Intel Corporation 82801I "
> CLASS=0403
> PCIDEV=8086:293e
> SUBSYS=144d:c048
> IRQ=22
> HDA=8086:293e
> SOFT=8086:293e.HDA
> CHIP=0x11c11040
> IDENT=11c11040
> Driver=agrmodem+agrserial+patched_snd-hda-intel
>
>  For candidate modem in:  00:1b.0
>   0403 Audio device: Intel Corporation 82801I
>      Primary device ID:  8086:293e
>    Subsystem PCI_id  144d:c048
>    Softmodem codec or chipset from diagnostics: 0x11c11040
>                               from    Archives:
>                        The HDA card softmodem chip is 0x11c11040
>
>
> Support type needed or chipset: 11c11040
>
> ----------------end Softmodem section --------------
>
> Writing DOCs/Intel.txt
>
> The LSI/Agere 11c11040 modem chip resides on the Subsystem of some
> High Definition Audio
> cards. At http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
> there may be
> a package with precompiled drivers with your Kernel-version in its
> name.  If drivers
> must be compiled, read
> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03863.html
>
> As of Jan 2009 the most current code is at http://linux.zsolttech.com/linmodem/
> Read the Modem/DOCs/Agrsm.txt
>
> -------------- 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.3.2
>             and the compiler used in kernel assembly: 4.3.2
>
>
>
>  Minimal compiling resources appear complete:
>   make utility - /usr/bin/make
>   Compiler version 4.3
>   linuc_headers base folder /lib/modules/2.6.27-9-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.
>
>
> Compressed files at: /usr/src/linux-source-2.6.27.tar.bz2
> /usr/src/sl-modem.tar.bz2
>
>
> 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-sr-x 1 root dip 277160 Nov 20 21:58 /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
> debug
> proxyarp
> lcp-echo-interval 30
> lcp-echo-failure 4
> noipx
> defaultroute
>
> 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
> wlan0 wmaster0
> 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:   lrwxrwxrwx 1 root root 12 Dec 27
> 20:21 /dev/modem -> /dev/ttyAGS3
> slmodemd created symbolic link /dev/ttySL0:
>     Within /etc/udev/ files:
>
>     Within /etc/modprobe.conf files:
> /etc/modprobe.d/agrsm:# setup agrsm modem with only: "sudo modprobe agrmodem"
> /etc/modprobe.d/agrsm:install agrmodem /sbin/modprobe --ignore-install
> agrmodem && /sbin/modprobe --ignore-install agrserial && test -e
> /dev/ttySAGR || ln -s /dev/ttyAGS3 /dev/ttySAGR
> /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
> /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 --------
>
>
>> We want to assess what processes are sharing the modems IRQ/interrupt
>>
>> After a dialout failure, do copy out the terminal section of dmesg
>
> Please, find it enclosed:
>
> Dec 27 20:57:27 manuel02 kernel: [ 2285.605477] * Hello Agere Driver **
> Dec 27 20:57:30 manuel02 kernel: [ 2287.841362] ttyAGS3 at I/O 0x4
> (irq = 22) is a AgereModem
> Dec 27 20:57:30 manuel02 kernel: [ 2287.841511] Loading module Agere
> Modem Interface driver version 2.1.80.0 (2008-10-31)
> Dec 27 20:58:12 manuel02 kernel: [ 2330.322081] ==> codecType = 0x32
> Dec 27 20:58:12 manuel02 kernel: [ 2330.362783] Kill Request for PID, FAKING!
> Dec 27 20:58:14 manuel02 kernel: [ 2332.811971] Kill Request for PID, FAKING!
> Dec 27 20:58:15 manuel02 kernel: [ 2333.347868] Kill Request for PID, FAKING!
> Dec 27 20:58:16 manuel02 kernel: [ 2333.879898] Kill Request for PID, FAKING!
> Dec 27 20:58:49 manuel02 kernel: [ 2367.656127] Kill Request for PID, FAKING!
> Dec 27 20:58:49 manuel02 pppd[9107]: pppd 2.4.4 started by manuel, uid 676
> Dec 27 20:58:50 manuel02 pppd[9107]: Using interface ppp0
> Dec 27 20:58:50 manuel02 pppd[9107]: Connect: ppp0 <--> /dev/ttyAGS3
> Dec 27 20:58:55 manuel02 pppd[9107]: PAP authentication succeeded
> Dec 27 20:58:55 manuel02 pppd[9107]: local  IP address 212.59.203.83
> Dec 27 20:58:55 manuel02 pppd[9107]: remote IP address 10.68.6.45
> Dec 27 20:58:55 manuel02 pppd[9107]: primary   DNS address 212.59.199.2
> Dec 27 20:58:55 manuel02 pppd[9107]: secondary DNS address 212.59.199.6
> Dec 27 20:59:38 manuel02 kernel: [ 2416.471952] Kill Request for PID, FAKING!
> Dec 27 20:59:38 manuel02 pppd[9107]: Hangup (SIGHUP)
> Dec 27 20:59:38 manuel02 pppd[9107]: Modem hangup
> Dec 27 20:59:38 manuel02 pppd[9107]: Connect time 0.8 minutes.
> Dec 27 20:59:38 manuel02 pppd[9107]: Sent 124 bytes, received 0 bytes.
> Dec 27 20:59:38 manuel02 pppd[9107]: Connection terminated.
> Dec 27 20:59:38 manuel02 pppd[9107]: Exit.
>
> And, just in case, this is the output after running scanModem:
>
>> sudo ./scanModem
> UPDATE=2008_12_25
>  Continuing as this update is only 0 weeks old,
>  but the current Update is always at: http://linmodems.technion.ac.il
>
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try `grep --help' for more information.
>
> Identifying PCI bus slots with candidate modems.
> Running PCIbus cases
> Analysing card in PCI bus 00:1b.0, writing to scanout.00:1b.0
> Using scanout.00:1b.0 data, and writing guidance to ModemData.txt
> Writing DOCs/Intel.txt
> ./scanModem: line 4056: i686: command not found
>
>  Writing residual guidance customized to your System.
>   A subfolder Modem/  has been written,  containing these files with
> more detailed Information:
>  ------------------------------------------------------------------------------------------
>  1stRead.txt  Bootup.txt  DOCs  ModemData.txt  dmesg.txt  scanout.00:1b.0  tmp
>    and in the DOCs subfolder:
>  Agrsm.txt       DriverCompiling.txt  InfoGeneral.txt  Intel.txt
> LSI_Agere.txt    Rational.txt         SoftModem.txt    Testing.txt
> UNSUBSCRIBE.txt  YourSystem.txt       wvdial.txt
> -------------------------------------------------------------------------------------------
>       Please read 1stRead.txt first for Guidance.
>
>
>>
>> MarvS
>>
>
> Best regards,
>
> Manuel
>
>
>>
>>
>> read the PostInstall Howto at http://linmodems.technion.ac.il
>> mostly about tuning parameters in /etc/ppp/option
>>
>> On Sat, Dec 27, 2008 at 5:34 AM, Manuel Matias
>> <manuel.a.matias@xxxxxxxxx> wrote:
>>> Hi Marvin,
>>>
>>> I'm having problems with the connection to Internet, both with wvdial and
>>> kppp:
>>> the connection starts, everything is allright, but invariably after
>>> some time (between 1, 5
>>> or even 10 minutes) the connection is broken.
>>> In the /var/log/messages (using both wvdial and kppp) the following
>>> line appears (typically
>>> twice):
>>> Kill Request for PID, Faking
>>> In the case of kppp it exits with "Exit status 16".
>>>
>>> As the connection is so unstable, it is not good to work with it (I'm
>>> writing this
>>> message connecting with Windows to the same ISP).
>>> Any clue?
>>>
>>> Regards,
>>>
>>> Manuel
>>>
>>> On 12/26/08, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>>>> Manuel
>>>>
>>>> It is good news that under Ubuntu 8.10  kernel 2.6.27-9-generic your
>>>> 11c11040 chip modem is functional.
>>>>
>>>> Do read the PostInstall Howto at http://linmodems.technion.ac.il
>>>> mostly about tuning parameters in /etc/ppp/option
>>>>
>>>> To automate , use
>>>> $ sudo gedit /etc/modprobe.d/agrsm
>>>> to create a file with two lines. The 2nd is folded in this email)
>>>> # setup agrsm modem with only: "sudo modprobe agrmodem"
>>>> install agrmodem /sbin/modprobe --ignore-install agrmodem &&
>>>> /sbin/modprobe --ignore-install agrserial && test -e /dev/ttySAGR ||
>>>> ln -s /dev/ttyAGS3 /dev/ttySAGR
>>>>
>>>> Then per record below, both drivers are loaded and the /dev/ttySAGR
>>>> symbolic link are created by single command:
>>>> $ sudo modprobe agrmodem
>>>>
>>>> MarvS
>>>>
>>>> $ sudo modprobe agrmodem
>>>>  agrmodem: module license 'Proprietary' taints kernel.
>>>> * Hello Agere Driver **
>>>>  ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
>>>>  Loading module Agere Modem Interface driver version 2.1.80.0
>>>> (2008-10-31)
>>>>
>>>> $ ls -l /dev/ttyAGS3 /dev/ttySAGR
>>>> crw-rw---- 1 root dialout 62, 67 2008-12-26 08:38 /dev/ttyAGS3
>>>> lrwxrwxrwx 1 root root          12 2008-12-26 08:38
>>>>        /dev/ttySAGR -> /dev/ttyAGS3
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Dec 26, 2008 at 5:09 AM, Manuel Matias
>>>> <manuel.a.matias@xxxxxxxxx> wrote:
>>>>> Dear Marvin,
>>>>>
>>>>> You were right: wvdial was not properly configured.
>>>>>
>>>>> Now I'm able to connect, but the connection (both with wvdial and with
>>>>> kppp) is
>>>>> somehow unstable, and lasts a maximum of 10-15 minutes; also the speed
>>>>> is a bit low.
>>>>> By comparison, with Windows I can be connected 1 hour or more, and the
>>>>> speed is good.
>>>>>
>>>>> Any suggestion?
>>>>>
>>>>> Regards and thanks for all your help and support,
>>>>>
>>>>> Manuel
>>>>>
>>>>> On Wed, Dec 24, 2008 at 2:29 PM, Marvin Stodolsky
>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>>>>> Manuel
>>>>>>
>>>>>> from "man pppd"
>>>>>>  error 0 -   Pppd  has detached, or otherwise the connection was
>>>>>> successfully
>>>>>>              established and terminated at the peer's request.
>>>>>> -----------
>>>>>> Are you sure your dialout information is correct, Send us a copy of
>>>>>> your wvdial.conf if using wvdial.
>>>>>> There would be no harm in using kppp, but be sure to go through the
>>>>>> configuration for your IP.
>>>>>>
>>>>>> Do read the PostInstall Howto at http://linmodems.technion.ac.il
>>>>>>
>>>>>> MarvS
>>>>>>
>>>>>> On Wed, Dec 24, 2008 at 5:24 AM, Manuel Matias
>>>>>> <manuel.a.matias@xxxxxxxxx> wrote:
>>>>>>> Dear Marvin,
>>>>>>>
>>>>>>> The installation works in principle (the drivers are loaded, etc,) but
>>>>>>> now I have problems to
>>>>>>> connect. Before (with a slamr supported Winmodem) I have always used
>>>>>>> 'kppp' without
>>>>>>> problems. Now, instead, I get all kind of problems (the connection
>>>>>>> disconnects in second 1
>>>>>>> with pppd error '0', or then hangs, or... although once I was able to
>>>>>>> connect briefly for a couple
>>>>>>> of minutes: the connection really worked, but afterwards no success).
>>>>>>> Could this be solved with the patching you mentioned?
>>>>>>> Or could it be a different problem? E.g. with kppp?
>>>>>>>
>>>>>>> Thanks for all your help!
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Manuel
>>>>>>>
>>>>>>> On Mon, Dec 22, 2008 at 3:00 PM, Marvin Stodolsky
>>>>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>>>>>>> Manuel,
>>>>>>>>
>>>>>>>> VEN_11C1&DEV_1040 corresponds under Linux to the 11c11040 Agere modem
>>>>>>>> chipset which is hosted on the SUbsystem of HIgh Definition Audio
>>>>>>>> cards. in your case
>>>>>>>>  PCI slot      PCI ID   SubsystemID  Name
>>>>>>>>  ----------   ---------  ---------   --------------
>>>>>>>> 00:1b.0  8086:293e  144d:c048  Audio device: Intel Corporation 82801I
>>>>>>>>
>>>>>>>> under Ubuntu kernel 2.6.27-9-generic
>>>>>>>>
>>>>>>>>  I'll separately forward my post of two days ago cogent to this
>>>>>>>> modem.
>>>>>>>> General info on this modem is at
>>>>>>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
>>>>>>>> though some updating is necessary.
>>>>>>>>
>>>>>>>> Always write back to the List, not directly to me. Others are more
>>>>>>>> expert on this chipset
>>>>>>>>
>>>>>>>> MarvS
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Dec 22, 2008 at 6:46 AM, Manuel Matias
>>>>>>>> <manuel.a.matias@xxxxxxxxx> wrote:
>>>>>>>>> Dear Antonio,
>>>>>>>>>
>>>>>>>>> Thank you very much for your mail!
>>>>>>>>>
>>>>>>>>> I downloaded scanModem.gz from:
>>>>>>>>> http://132.68.73.235/linmodems/packages/scanModem.gz
>>>>>>>>> I have just downloaded it again and the file has not changed. If you
>>>>>>>>> can tell me
>>>>>>>>> the link to the newest version, I'll run it, of course.
>>>>>>>>>
>>>>>>>>> For the moment I have had a look at Windows, as you point out, and
>>>>>>>>> the
>>>>>>>>> info I get is as follows:
>>>>>>>>>
>>>>>>>>> ATI3   Agere SoftModem Version 2.1.88
>>>>>>>>> ATI5   2.1.88, HDA MB , HDA, A35 S-Rev:1 L-Rev:3, 12
>>>>>>>>>
>>>>>>>>> I have not found any file called ('MODEM.INF' or 'MODEM.*') (the
>>>>>>>>> O.S.
>>>>>>>>> is Vista, not XP) but
>>>>>>>>> the following Modem Information can be useful:
>>>>>>>>> HDAUDIO\FUNC_02&VEN_11C1&DEV_1040&SUBSYS_2118144D&REV_1002
>>>>>>>>>
>>>>>>>>> and somewhere else "Driver files" I find the following:
>>>>>>>>> C:\\Windows\agrmsdel.exe
>>>>>>>>> C:\\Windows\system32\agrscoin.dll
>>>>>>>>> C:\\Windows\system32\agrsmsvc,exe
>>>>>>>>> C:\\Windows\system32\DRIVERS\AGRSM.sys
>>>>>>>>> C:\\Windows\system32\drivers\modem.sys
>>>>>>>>>
>>>>>>>>> although the files cannot be edited.
>>>>>>>>>
>>>>>>>>> Unfortunately, I have not been able to obtain the info:
>>>>>>>>>
>>>>>>>>> Start > Settings > Control Panel > Classical View (for Window XP) >
>>>>>>>>> System
>>>>>>>>> Hardware > Device Manager > Modems > Click on the + > Modem. Double
>>>>>>>>> click to
>>>>>>>>> expand the graphic. Manufacturer information may be displayed. For
>>>>>>>>> example, CXT
>>>>>>>>> stands for Conexant.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I hope that the info I have collected is useful.
>>>>>>>>>
>>>>>>>>> And thanks a lot!
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>>
>>>>>>>>> Manuel
>>>>>>>>>
>>>>>>>>> On Sun, Dec 21, 2008 at 5:21 PM, Antonio Olivares
>>>>>>>>> <olivares14031@xxxxxxxxx> wrote:
>>>>>>>>>> Manuel,
>>>>>>>>>>
>>>>>>>>>> If you can get the newest scanModem, it would make a big
>>>>>>>>>> difference.
>>>>>>>>>> IF you can't then please follow the suggestion by scanModem
>>>>>>>>>>
>>>>>>>>>>       If an alternative boot into Microsoft windows can be done, do
>>>>>>>>>> mouse
>>>>>>>>>>  clicks on:
>>>>>>>>>>   Start > Settings > Control Panel > Classical View (for Window XP)
>>>>>>>>>> >
>>>>>>>>>> System
>>>>>>>>>>  > Hardware > Device Manager > Modems > Click on the + > Modem.
>>>>>>>>>> Double click to
>>>>>>>>>>  expand the graphic. Manufacturer information may be displayed. For
>>>>>>>>>> example, CXT
>>>>>>>>>>  stands for Conexant. Click the Diagnostics Tab. Record any
>>>>>>>>>> hardware
>>>>>>>>>> ID or vendor
>>>>>>>>>>  and device information.
>>>>>>>>>>  Next do the Query Modem and record the ATI specifications
>>>>>>>>>> displayed
>>>>>>>>>> such as:
>>>>>>>>>>    ATI3 - Agere SoftModem Version 2.1.22
>>>>>>>>>>    ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
>>>>>>>>>>  Try to identify the modem setup file, with name perhaps MODEM.INF.
>>>>>>>>>>  If may contain chipset Vendor informaton.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Antonio
>>>>>>>>>>
>>>>>>>>>> On 12/21/08, Manuel Matias <manuel.a.matias@xxxxxxxxx> wrote:
>>>>>>>>>>> Good afternoon!
>>>>>>>>>>>
>>>>>>>>>>> I am trying to install Linux support for a recently purchased
>>>>>>>>>>> Samsung
>>>>>>>>>>> X460 laptop, and have had no success in having the Winmodem
>>>>>>>>>>> working.
>>>>>>>>>>>
>>>>>>>>>>> Vista reports the modem as:
>>>>>>>>>>> "Agere Systems HDA Modem"
>>>>>>>>>>> and I also enclose the ModemData.txt file generated by the
>>>>>>>>>>> scanModem
>>>>>>>>>>> utility
>>>>>>>>>>> (sorry for having forgotten to do so in my previous
>>>>>>>>>>> communication).
>>>>>>>>>>>
>>>>>>>>>>> Yours sincerely,
>>>>>>>>>>>
>>>>>>>>>>> Manuel
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>  Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx
>>>>>>>>>>> List
>>>>>>>>>>> Server.
>>>>>>>>>>>  Do use the following as the email Subject Line:
>>>>>>>>>>>            SomeName, YourCountry Ubuntu 8.10  kernel
>>>>>>>>>>> 2.6.27-9-generic
>>>>>>>>>>>  This will alert cogent experts, and  distinguish cases in the
>>>>>>>>>>> Archives.
>>>>>>>>>>>  YourCountry will enable Country Code guidance.
>>>>>>>>>>>  Occassionally responses are blocked by an Internet Provider mail
>>>>>>>>>>> filters.
>>>>>>>>>>>  So in a day, also check the Archived responses at
>>>>>>>>>>> http://www.linmodems.org
>>>>>>>>>>> .
>>>>>>>>>>>  Local Linux experts can be found through:
>>>>>>>>>>> http://www.linux.org/groups/index.htm
>>>>>>>>>>> l
>>>>>>>>>>> --------------------------  System information
>>>>>>>>>>> ----------------------------
>>>>>>>>>>>  Ubuntu 8.10
>>>>>>>>>>> Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2
>>>>>>>>>>> (Ubuntu
>>>>>>>>>>> 4.3.2
>>>>>>>>>>> -1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
>>>>>>>>>>>  scanModem update of:  2006_October_3
>>>>>>>>>>> The modem symbolic link is /dev/modem -> ttySL0
>>>>>>>>>>>
>>>>>>>>>>> USB modem not detected by lsusb
>>>>>>>>>>>
>>>>>>>>>>> Modem or host audio card candidates have firmware information:
>>>>>>>>>>>  PCI slot      PCI ID   SubsystemID  Name
>>>>>>>>>>>  ----------   ---------  ---------   --------------
>>>>>>>>>>> 00:1b.0  8086:293e  144d:c048  Audio device: Intel Corporation
>>>>>>>>>>> 82801I
>>>>>>>>>>>
>>>>>>>>>>>  Modem interrupt assignment and sharing:
>>>>>>>>>>>  22:      26660      26615   IO-APIC-fasteoi   HDA Intel
>>>>>>>>>>>
>>>>>>>>>>>  --- Bootup diagnositcs for 00:1b.0 ----
>>>>>>>>>>> [    0.524293] pci 0000:00:1a.7: PME# disabled
>>>>>>>>>>> [    0.524339] PCI: 0000:00:1b.0 reg 10 64bit mmio: [fc200000,
>>>>>>>>>>> fc203fff]
>>>>>>>>>>> [    0.524392] pci 0000:00:1b.0: PME# supported from D0 D3hot
>>>>>>>>>>> D3cold
>>>>>>>>>>> [    0.524397] pci 0000:00:1b.0: PME# disabled
>>>>>>>>>>> [    0.524466] pci 0000:00:1c.0: PME# supported from D0 D3hot
>>>>>>>>>>> D3cold
>>>>>>>>>>> [    0.524472] pci 0000:00:1c.0: PME# disabled
>>>>>>>>>>> --
>>>>>>>>>>> (manuel02)/home/manuel/tcs/images/Modem$> cat ModemData.txt
>>>>>>>>>>>  Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx
>>>>>>>>>>> List
>>>>>>>>>>> Server.
>>>>>>>>>>>  Do use the following as the email Subject Line:
>>>>>>>>>>>            SomeName, YourCountry Ubuntu 8.10  kernel
>>>>>>>>>>> 2.6.27-9-generic
>>>>>>>>>>>  This will alert cogent experts, and  distinguish cases in the
>>>>>>>>>>> Archives.
>>>>>>>>>>>  YourCountry will enable Country Code guidance.
>>>>>>>>>>>  Occassionally responses are blocked by an Internet Provider mail
>>>>>>>>>>> filters.
>>>>>>>>>>>  So in a day, also check the Archived responses at
>>>>>>>>>>> http://www.linmodems.org
>>>>>>>>>>> .
>>>>>>>>>>>  Local Linux experts can be found through:
>>>>>>>>>>> http://www.linux.org/groups/index.html
>>>>>>>>>>> --------------------------  System information
>>>>>>>>>>> ----------------------------
>>>>>>>>>>>  Ubuntu 8.10
>>>>>>>>>>> Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2
>>>>>>>>>>> (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
>>>>>>>>>>>  scanModem update of:  2006_October_3
>>>>>>>>>>> The modem symbolic link is /dev/modem -> ttySL0
>>>>>>>>>>>
>>>>>>>>>>> USB modem not detected by lsusb
>>>>>>>>>>>
>>>>>>>>>>> Modem or host audio card candidates have firmware information:
>>>>>>>>>>>  PCI slot      PCI ID   SubsystemID  Name
>>>>>>>>>>>  ----------   ---------  ---------   --------------
>>>>>>>>>>> 00:1b.0  8086:293e  144d:c048  Audio device: Intel Corporation
>>>>>>>>>>> 82801I
>>>>>>>>>>>
>>>>>>>>>>>  Modem interrupt assignment and sharing:
>>>>>>>>>>>  22:      26660      26615   IO-APIC-fasteoi   HDA Intel
>>>>>>>>>>>
>>>>>>>>>>>  --- Bootup diagnositcs for 00:1b.0 ----
>>>>>>>>>>> [    0.524293] pci 0000:00:1a.7: PME# disabled
>>>>>>>>>>> [    0.524339] PCI: 0000:00:1b.0 reg 10 64bit mmio: [fc200000,
>>>>>>>>>>> fc203fff]
>>>>>>>>>>> [    0.524392] pci 0000:00:1b.0: PME# supported from D0 D3hot
>>>>>>>>>>> D3cold
>>>>>>>>>>> [    0.524397] pci 0000:00:1b.0: PME# disabled
>>>>>>>>>>> [    0.524466] pci 0000:00:1c.0: PME# supported from D0 D3hot
>>>>>>>>>>> D3cold
>>>>>>>>>>> [    0.524472] pci 0000:00:1c.0: PME# disabled
>>>>>>>>>>> --
>>>>>>>>>>> [   14.203195] Linux video capture interface: v2.00
>>>>>>>>>>> [   14.213846] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>>>>>>>>>>> low) -> IRQ 22
>>>>>>>>>>> [   14.213872] HDA Intel 0000:00:1b.0: setting latency timer to 64
>>>>>>>>>>> [   14.231668] Bluetooth: Generic Bluetooth USB driver ver 0.3
>>>>>>>>>>> [   14.233276] usbcore: registered new interface driver btusb
>>>>>>>>>>> --
>>>>>>>>>>> [ 6321.596193] uhci_hcd 0000:00:1d.0: PCI INT A disabled
>>>>>>>>>>> [ 6321.644052] HDA Intel 0000:00:1b.0: PCI INT A disabled
>>>>>>>>>>> [ 6321.660099] ehci_hcd 0000:00:1a.7: PCI INT C disabled
>>>>>>>>>>> [ 6321.676083] uhci_hcd 0000:00:1a.2: PCI INT C disabled
>>>>>>>>>>> --
>>>>>>>>>>> [ 6322.456043] ehci_hcd 0000:00:1a.7: setting latency timer to 64
>>>>>>>>>>> [ 6322.472052] HDA Intel 0000:00:1b.0: restoring config space at
>>>>>>>>>>> offset 0xf (was 0x100, writing 0x105)
>>>>>>>>>>> [ 6322.472075] HDA Intel 0000:00:1b.0: restoring config space at
>>>>>>>>>>> offset 0x3 (was 0x0, writing 0x10)
>>>>>>>>>>> [ 6322.472083] HDA Intel 0000:00:1b.0: restoring config space at
>>>>>>>>>>> offset 0x1 (was 0x100000, writing 0x100002)
>>>>>>>>>>> [ 6322.472104] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>>>>>>>>>>> low) -> IRQ 22
>>>>>>>>>>> [ 6322.472111] HDA Intel 0000:00:1b.0: setting latency timer to 64
>>>>>>>>>>> [ 6322.472149] pcieport-driver 0000:00:1c.0: restoring config
>>>>>>>>>>> space
>>>>>>>>>>> at
>>>>>>>>>>> offset 0xf (was 0x40100, writing 0x4010a)
>>>>>>>>>>> [ 6322.472161] pcieport-driver 0000:00:1c.0: restoring config
>>>>>>>>>>> space
>>>>>>>>>>> at
>>>>>>>>>>> offset 0x9 (was 0x10001, writing 0xf1f1f001)
>>>>>>>>>>>
>>>>>>>>>>>  The PCI slot 00:1b.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 Bootup.txt about possible
>>>>>>>>>>> fixes.
>>>>>>>>>>>  Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>>>>>>>>>>>  if help is needed.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>  and a NEW HDA softmodem controller.
>>>>>>>>>>>
>>>>>>>>>>>  For candidate modem in PCI bus:  00:1b.0
>>>>>>>>>>>    Class 0403: 8086:293e Audio device: Intel Corporation 82801I
>>>>>>>>>>>       Primary PCI_id  NEW_softmodem_8086:293e
>>>>>>>>>>>  Support type needed or chipset:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> scanModem could not identify the Support Type needed from
>>>>>>>>>>> diagnosics
>>>>>>>>>>> or archives.
>>>>>>>>>>>         If an alternative boot into Microsoft windows can be done,
>>>>>>>>>>> do mouse
>>>>>>>>>>> clicks on:
>>>>>>>>>>>    Start > Settings > Control Panel > Classical View (for Window
>>>>>>>>>>> XP)
>>>>>>>>>>> >
>>>>>>>>>>> System
>>>>>>>>>>>> Hardware > Device Manager > Modems > Click on the + > Modem.
>>>>>>>>>>>> Double
>>>>>>>>>>>> click
>>>>>>>>>>>> to
>>>>>>>>>>> expand the graphic. Manufacturer information may be displayed. For
>>>>>>>>>>> example,
>>>>>>>>>>> CXT
>>>>>>>>>>> stands for Conexant. Click the Diagnostics Tab. Record any
>>>>>>>>>>> hardware
>>>>>>>>>>> ID or
>>>>>>>>>>> vendor
>>>>>>>>>>> and device information.
>>>>>>>>>>> Next do the Query Modem and record the ATI specifications
>>>>>>>>>>> displayed
>>>>>>>>>>> such as:
>>>>>>>>>>>     ATI3 - Agere SoftModem Version 2.1.22
>>>>>>>>>>>     ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
>>>>>>>>>>> Try to identify the modem setup file, with name perhaps MODEM.INF.
>>>>>>>>>>> If may contain chipset Vendor informaton.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Writing Intel.txt
>>>>>>>>>>>
>>>>>>>>>>>  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
>>>>>>>>>>>
>>>>>>>>>>>  Kernel-header resources needed for compiling are not manifestly
>>>>>>>>>>> ready!
>>>>>>>>>>>
>>>>>>>>>>>  If compiling is necessary packages must be installed, providing:
>>>>>>>>>>>          linux-headers-2.6.27-9-generic
>>>>>>>>>>> Compressed files at: /usr/src/sl-modem.tar.bz2
>>>>>>>>>>>
>>>>>>>>>>> Checking settings of:   /etc/ppp/options
>>>>>>>>>>> asyncmap 0
>>>>>>>>>>> noauth
>>>>>>>>>>> crtscts
>>>>>>>>>>> lock
>>>>>>>>>>> hide-password
>>>>>>>>>>> modem
>>>>>>>>>>> proxyarp
>>>>>>>>>>> lcp-echo-interval 30
>>>>>>>>>>> lcp-echo-failure 4
>>>>>>>>>>> noipx
>>>>>>>>>>>
>>>>>>>>>>> Read Modem/YourSystem.txt concerning other COMM channels: eth0
>>>>>>>>>>> wlan0
>>>>>>>>>>> wmaster0
>>>>>>>>>>> Which can interfere with Browser naviagation.
>>>>>>>>>>>
>>>>>>>>>>>  Don't worry about the following, it is for the experts
>>>>>>>>>>>  should trouble shooting be necessary.
>>>>>>>>>>> ==========================================================
>>>>>>>>>>>
>>>>>>>>>>> # start/stop the daemon when the USB modem is connected
>>>>>>>>>>> KERNEL=="slusb[0-9]*", GROUP="dialout",
>>>>>>>>>>> RUN+="/etc/init.d/sl-modem-daemon"
>>>>>>>>>>>  Checking for modem support lines:
>>>>>>>>>>>  --------------------------------------
>>>>>>>>>>>      /device/modem symbolic link:   lrwxrwxrwx 1 root root 6 Dec
>>>>>>>>>>> 20
>>>>>>>>>>> 08:53 /dev/modem -> ttySL0
>>>>>>>>>>> slmodemd created symbolic link /dev/ttySL0:
>>>>>>>>>>>      Within /etc/udev/ files:
>>>>>>>>>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the
>>>>>>>>>>> daemon
>>>>>>>>>>> when the USB modem is connected
>>>>>>>>>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>>>>>>>>>>> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
>>>>>>>>>>> /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the
>>>>>>>>>>> USB
>>>>>>>>>>> modem is connected
>>>>>>>>>>> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>>>>>>>>>>> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
>>>>>>>>>>>      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
>>>>>>>>>>> blacklistunwanted modem drivers
>>>>>>>>>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
>>>>>>>>>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
>>>>>>>>>>> /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe
>>>>>>>>>>> --ignore-install ungrab-winmodem ;  modprobe --ignore-install
>>>>>>>>>>> slamr;
>>>>>>>>>>> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
>>>>>>>>>>> 2>/dev/null && chgrp dialout /dev/slamr0)
>>>>>>>>>>>      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