Nabble - Linux Winmodem Support - Discussion

Server http://linmodems.technion.ac.il down

2009-12-15T07:24:22Z

Folks I am sorry.
I cannot find help to fix today, see below if interested.
I will post a note when it restarts - not before Wednesday morning.

A problem, I still do not know which one, has occurred during the weekend.

I have left my lab for 3 weeks on Tuesday 8 December. Everything was
working well on Friday.

On Saturday night I could not connect to the
computer. Early on Sunday morning I left Paris for Amsterdam, due
returning late Monday evening (yesterday), without any connectivity. But
the new fast train did not make it: it dumped us in a hotel in Brussels
around 2 AM. The continuation train today arrived late again.

Until I was back to my laptop, it was already too late to find somebody to
visit my computer.

Must wait until Wednesday morning.

I will keep you informed.

Jacques

Re: Nick, Australia kernel 2.6.31-14-generic

2009-12-15T06:14:23Z

Nick,

Marv sent another driver slamr for kernel 2.6.31 so you may try that
one instead and report back.

Regards,

Antonio

On Tue, Dec 15, 2009 at 8:16 PM, Nick <nwahl@...> wrote:

> Antonio,
>
> Marvin sent me wvdial_karmic.zip, and I installed everything,
> including Ubuntu, from scratch, but it didn't make any difference. I
> still get the following errors:
>
> Warning: no device detected by hsf driver - HDA modems may require reboot.
> Note: HDA support not compiled in the driver.
> Sorry. You can retry the autodetection at any time by running
> "wvdialconf". (Or you can create /etc/wvdial.conf yourself.)
> Sorry, no modem was detected! Is it in use by another program?
> Did you configure it properly with setserial?
> Cannot open /dev/modem: Input/output error
>
> I rebooted the computer, but I don't know how to reboot the modem or,
> as it says somewhere else, activate the modem (on its own) - if that's
> what's required.
>
> Needless to say that I look forward to some more help. - Nick
>
> Antonio Olivares wrote:
>> Nick,
>>
>> You have done everything according to instructions and your modem is
>> not functioning correctly? Did you reboot and try it again?
>>
>> The wvdial packages have been updated for newer Ubuntu release
>> wvdial_karmic.zip, but sadly the page at linmodems is currently down
>> :(
>>
>> Details of the Request:
>> URL: http://linmodems.technion.ac.il/packages/
>> Protocol: http
>> Date and Time: Sunday 13 December 2009 03:01
>> Additional Information: linmodems.technion.ac.il: Socket operation timed out
>> Description:
>> The server linmodems.technion.ac.il refused to allow this computer to
>> make a connection.
>>
>> For the other problem modem not found/responding, rebooting the
>> machine and giving it a retry does it find the modem?
>>
>> Let us know and report back.
>>
>> Regards,
>>
>> Antonio
>>
>> On 12/13/09, Nick Wahl <nwahl@...> wrote:
>>> Thank you, Antonio, for your prompt help!
>>>
>>> I believe I did everything the way you recommended. However, I could
>>> not get it to work (yet) and, even after reading up on possible causes
>>> and trying possible solutions, I cannot tell why - which, of course,
>>> tells you how much of an expert I am at this.
>>>
>>> Please have a look at what I did and my comments in ( ).
>>>
>>> Before I attempt more complicated possible solutions, I would
>>> appreciate your advice. I am, therefore, also attaching dmesg.txt in
>>> case you need it.
>>>
>>> Your help is very much appreciated. Thank you! - Nick
>>>
>>> *************************************
>>> Step 1
>>> nw@nw:~$ sudo dpkg -i hsfmodem*.deb
>>> (Reading database ... 114040 files and directories currently installed.)
>>> Unpacking hsfmodem (from
>>> hsfmodem_7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb) ...
>>> Setting up hsfmodem (7.80.02.05full-k2.6.31-14-generic-1.ubuntu) ...
>>> Conexant HSF softmodem driver, version 7.80.02.05full
>>>
>>> Pre-built driver modules that seem compatible with your system were
>>> found under
>>> /usr/lib/hsfmodem/modules/binaries/linux-2.6.31-14-generic-SMP.
>>>
>>> Warning: no device detected by hsf driver - HDA modems may require reboot
>>>
>>> (Why wouldn't it be detected if it was detected by scanModem? I
>>> couldn't find any evidence that it has been disabled. There is some
>>> Firmware missing, but I can't tell if that has anything to do with
>>> this. I would have liked to reboot the modem, but I don't know how to
>>> do that.)
>>>
>>> Note: HDA support not compiled in the driver
>>>
>>> Note: kernel module snd-via82xx-modem overridden by hsfmc97via
>>> Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis
>>> Note: kernel module snd-atiixp-modem overridden by hsfmc97ati
>>>
>>> Step 2
>>> nw@nw:~$ sudo wvdialconf /etc/wvdial.conf
>>> sudo: wvdialconf: command not found
>>> nw@nw:~$
>>>
>>> Steps 3
>>> nw@nw:/etc/wvdial$ sudo unzip wv*.zip
>>> Archive: wvdial_jaunty_i386.zip
>>> inflating: wvdial_jaunty_i386/debconf_1.5.26ubuntu3_all.deb
>>> inflating: wvdial_jaunty_i386/libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb
>>> inflating:
>>> wvdial_jaunty_i386/libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb
>>> inflating:
>>> wvdial_jaunty_i386/libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb
>>> inflating: wvdial_jaunty_i386/libxplc0.3.13_0.3.13-1build1_i386.deb
>>> inflating: wvdial_jaunty_i386/Readme.txt.txt
>>> inflating: wvdial_jaunty_i386/wvdial_1.60.1+nmu2_i386.deb
>>>
>>> (I am running Ubuntu 9.10 Karmic Koala, not Jaunty and the CPU is an
>>> i686 not an i386. I cannot tell if that would have something to do
>>> with it.)
>>>
>>> Step 4
>>> nw@nw:/etc/wvdial/wvdial_jaunty_i386$ sudo dpkg -i *.deb
>>> dpkg: warning: downgrading debconf from 1.5.27ubuntu2 to 1.5.26ubuntu3.
>>> (Reading database ... 115932 files and directories currently installed.)
>>> Preparing to replace debconf 1.5.27ubuntu2 (using
>>> debconf_1.5.26ubuntu3_all.deb) ...
>>> Unpacking replacement debconf ...
>>> Selecting previously deselected package libuniconf4.4.
>>> Unpacking libuniconf4.4 (from libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb) ...
>>> Selecting previously deselected package libwvstreams4.4-base.
>>> Unpacking libwvstreams4.4-base (from
>>> libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb) ...
>>> Selecting previously deselected package libwvstreams4.4-extras.
>>> Unpacking libwvstreams4.4-extras (from
>>> libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb) ...
>>> Selecting previously deselected package libxplc0.3.13.
>>> Unpacking libxplc0.3.13 (from libxplc0.3.13_0.3.13-1build1_i386.deb) ...
>>> Selecting previously deselected package wvdial.
>>> Unpacking wvdial (from wvdial_1.60.1+nmu2_i386.deb) ...
>>> Setting up debconf (1.5.26ubuntu3) ...
>>>
>>> Setting up libxplc0.3.13 (0.3.13-1build1) ...
>>>
>>> Setting up libwvstreams4.4-base (4.4.1-0.2ubuntu2) ...
>>>
>>> Setting up libwvstreams4.4-extras (4.4.1-0.2ubuntu2) ...
>>>
>>> Setting up libuniconf4.4 (4.4.1-0.2ubuntu2) ...
>>>
>>> Processing triggers for man-db ...
>>> Setting up wvdial (1.60.1+nmu2) ...
>>>
>>> Sorry. You can retry the autodetection at any time by running
>>> "wvdialconf".
>>> (Or you can create /etc/wvdial.conf yourself.)
>>>
>>> Processing triggers for libc-bin ...
>>> ldconfig deferred processing now taking place
>>> nw@nw:/etc/wvdial/wvdial_jaunty_i386$
>>>
>>> Step 5 (trying again:)
>>> nw@nw:~$ sudo wvdialconf /etc/wvdial.conf
>>> Editing `/etc/wvdial.conf'.
>>>
>>> Scanning your serial ports for a modem.
>>>
>>> Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to it.
>>> Modem Port Scan<*1>: SHSF0 S0 S1 S2 S3 SHSF1 SHSF2 SHSF3
>>> Modem Port Scan<*1>: SHSF4 SHSF5 SHSF6 SHSF7
>>>
>>>
>>> Sorry, no modem was detected! Is it in use by another program?
>>> Did you configure it properly with setserial?
>>>
>>> (Why wouldn't it be detected if scanModem did? It was not used by
>>> another program and the info on setserial does not seem to apply here.)
>>>
>>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>>>
>>> (There are no FAQ at the above link.)
>>>
>>> If you still have problems, send mail to <wvdial-list@...>.
>>> nw@nw:~$
>>>
>>> (I don't want to try this, unless wvdial is the problem.)
>>>
>>> Step 6
>>> nw@nw:~$ sudo gedit /etc/wvdial.conf
>>> [sudo] password for nw:
>>>
>>> (Details entered O.K.)
>>>
>>> Step 7
>>> nw@nw:~$ sudo wvdial
>>> --> WvDial: Internet dialer version 1.60
>>> --> Cannot open /dev/modem: Input/output error
>>> --> Cannot open /dev/modem: Input/output error
>>> --> Cannot open /dev/modem: Input/output error
>>> nw@nw:~$
>>> ********************************************
>>>
>>> Antonio Olivares wrote:
>>>> Nick,
>>>>
>>>> scanModem reports that you need hsfmodem drivers and that wvdial is
>>>> not installed:
>>>>
>>>> For candidate modem in: 00:1b.0
>>>> 0403 Audio device: Intel Corporation 82801H
>>>> Primary device ID: 8086:284b
>>>> Subsystem PCI_id 103c:30d9
>>>> Softmodem codec or chipset from diagnostics:
>>>> from Archives:
>>>>
>>>>
>>>>
>>>> Support type needed or chipset: hsfmodem
>>>>
>>>>
>>>> Writing DOCs/Intel.txt
>>>>
>>>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>>>> package with full speed enabled is available, but requires driver
>>>> compiling. Read DOCs/Conexant.txt
>>>>
>>>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>>>> download hsfmodem-7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb.zip
>>>> Under Linux unpack with:
>>>> $ unzip hsfmodem*.zip
>>>> Then install with:
>>>> $ sudo dpkg -i hsfmodem*.deb
>>>> Subsequently, the modem should be found with
>>>> $ sudo wvdialconf /etc/wvdial.conf
>>>> Edit in your personal information with:
>>>> $ sudo gedit /etc/wvdial.conf
>>>> and try dialing out with:
>>>> $ sudo wvdial.
>>>> See DOCs/Testing.txt for details.
>>>>
>>>> The dialer utility package WVDIAL does not appear to be installed on
>>>> your System.
>>>> For Ubuntu Jaunty users, there are at the bottom of
>>>> http://linmodems.technion.ac.il/packages/:
>>>> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
>>>> wvdial_jaunty_i386.zip for 32 bit systems.
>>>> These are about 1 MB in size. After downloaded and copied into your
>>>> Linux partition:
>>>> $ unzip wv*.zip
>>>> Within the new folder:
>>>> $ sudo dpkg -i *.deb
>>>> will complete the wvdial installation
>>>> Please read Modem/DOCs/wvdial.txt for usage information.
>>>>
>>>> Regards.
>>>>
>>>>
>>>> Antonio
>>>>
>>>> On 11/30/09, Nick <nwahl@...> wrote:
>>>>> Only plain text email is forwarded by the Discuss@... List
>>>>> Server,
>>>>> as HTML can contain viruses. Use as the email Subject Line:
>>>>> YourName, YourCountry kernel 2.6.31-14-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@... 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.31-14-generic (buildd@rothera) (gcc version 4.4.1
>>>>> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
>>>>> scanModem update of: 2009_11_26
>>>>>
>>>>> The dialer utility package WVDIAL does not appear to be installed on
>>>>> your System.
>>>>> For Ubuntu Jaunty users, there are at the bottom of
>>>>> http://linmodems.technion.ac.il/packages/:
>>>>> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
>>>>> wvdial_jaunty_i386.zip for 32 bit systems.
>>>>> These are about 1 MB in size. After downloaded and copied into your
>>>>> Linux partition:
>>>>> $ unzip wv*.zip
>>>>> Within the new folder:
>>>>> $ sudo dpkg -i *.deb
>>>>> will complete the wvdial installation
>>>>> Please read Modem/DOCs/wvdial.txt for usage information.
>>>>>
>>>>> 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
>>>>>
>>>>> 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 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
>>>>> ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
>>>>> 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@...
>>>>>
>>>>> For candidate card in slot 00:1b.0, firmware information and bootup
>>>>> diagnostics are:
>>>>> PCI slot PCI ID SubsystemID Name
>>>>> ---------- --------- --------- --------------
>>>>> 00:1b.0 8086:284b 103c:30d9 Audio device: Intel Corporation 82801H
>>>>>
>>>>> Modem interrupt assignment and sharing:
>>>>> 22: 1051 IO-APIC-fasteoi HDA Intel
>>>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>>>>> [ 0.293090] pci 0000:00:1b.0: reg 10 64bit mmio:
>>>>> [0x72400000-0x72403fff]
>>>>> [ 0.293159] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>>>>> [ 0.293164] pci 0000:00:1b.0: PME# disabled
>>>>> [ 8.913160] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>>>>> low) -> IRQ 22
>>>>> [ 8.913198] 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@...
>>>>> 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.20
>>>>> The modem cards detected by "aplay -l" are: None
>>>>>
>>>>>
>>>>> The /proc/asound/pcm file reports:
>>>>> -----------------------
>>>>> 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1
>>>>> 00-01: Conexant Digital : Conexant Digital : playback 1
>>>>>
>>>>> about /proc/asound/cards:
>>>>> ------------------------
>>>>> 0 [Intel ]: HDA-Intel - HDA Intel
>>>>> HDA Intel at 0x72400000 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.31-14-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 00:1b.0:
>>>>> Modem chipset detected on
>>>>> NAME="Audio device: Intel Corporation 82801H "
>>>>> CLASS=0403
>>>>> PCIDEV=8086:284b
>>>>> SUBSYS=103c:30d9
>>>>> IRQ=22
>>>>> HDA=8086:284b
>>>>> SOFT=8086:284b.HDA
>>>>> IDENT=hsfmodem
>>>>> Driver=hsfmodem-drivers
>>>>>
>>>>> For candidate modem in: 00:1b.0
>>>>> 0403 Audio device: Intel Corporation 82801H
>>>>> Primary device ID: 8086:284b
>>>>> Subsystem PCI_id 103c:30d9
>>>>> Softmodem codec or chipset from diagnostics:
>>>>> from Archives:
>>>>>
>>>>>
>>>>>
>>>>> Support type needed or chipset: hsfmodem
>>>>>
>>>>>
>>>>> Writing DOCs/Intel.txt
>>>>>
>>>>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>>>>> package with full speed enabled is available, but requires driver
>>>>> compiling. Read DOCs/Conexant.txt
>>>>>
>>>>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>>>>> download hsfmodem-7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb.zip
>>>>> Under Linux unpack with:
>>>>> $ unzip hsfmodem*.zip
>>>>> Then install with:
>>>>> $ sudo dpkg -i hsfmodem*.deb
>>>>> Subsequently, the modem should be found with
>>>>> $ sudo wvdialconf /etc/wvdial.conf
>>>>> Edit in your personal information with:
>>>>> $ sudo gedit /etc/wvdial.conf
>>>>> and try dialing out with:
>>>>> $ sudo wvdial.
>>>>> See DOCs/Testing.txt for details.
>>>>>
>>>>> The directions following below need only be pursued, if the above
>>>>> procedures are not adequate.
>>>>>
>>>>> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to
>>>>> find the
>>>>> hsfmodem package matching your System. For several Linux distros,
>>>>> there are
>>>>> precompiled drivers matched to specific kernels. These have within the
>>>>> FileName,
>>>>> your KernelVersion: 2.6.31_14_generic
>>>>> They can be found through
>>>>> http://www.linuxant.com/drivers/hsf/full/downloads.php
>>>>> A more precise location may be given a few paragraphs below.
>>>>> If an EXACT Match with your your KernelVersion is not found, one of the
>>>>> "Generic packages with source" near the bottom of the page must be used.
>>>>> Downloaded packages must be moved into the Linux partition (home
>>>>> folder is OK)
>>>>> and unzipped with:
>>>>> unzip hsf*.zip
>>>>> The installation command for a .deb suffic packages is, with root/adm
>>>>> permission:
>>>>> sudo dpkg -i hsf*.deb
>>>>> while for .rpm suffix it is, with:
>>>>> rpm -i hsf*.rpm
>>>>>
>>>>> Support for Conexant chips hosted on High Definition Audio cards may
>>>>> require
>>>>> installation of additional packages, one of the alsa-driver-linuxant
>>>>> packages
>>>>> on http://www.linuxant.com/alsa-driver/ At the same time download the
>>>>> alsa-driver-1.0.17-1.patch , in case it prove to be later needed.
>>>>> During the
>>>>> hsfmodem install, there will be a message if there is necessary
>>>>> installation of
>>>>> alsa-driver-linuxant
>>>>>
>>>>> The installation command for a .deb suffic packages is, with root/adm
>>>>> permission:
>>>>> sudo dpkg -i hsf*.deb
>>>>> while for .rpm suffix it is, with:
>>>>> rpm -i hsf*.rpm
>>>>>
>>>>> There may a message that "Dependencies" are not satisfied. In this
>>>>> case the Ubuntu/Debian packages to be installed are linux-libc-dev &
>>>>> libc6-dev. Package
>>>>> names may be different for other Linuxes. If not on your install CD,
>>>>> these
>>>>> packages can be searched for at http://packages.ubuntu.com. After
>>>>> download,
>>>>> they can be coinstalled with:
>>>>> sudo dpkg -i li*.deb
>>>>> Again try the alsa-driver-linuxant
>>>>>
>>>>> There may be a message that the patch must be applied. In this case
>>>>> get the
>>>>> ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
>>>>> Under Linux, this package is unpacked with:
>>>>> $ tar jxf alsa*.tar.bz2
>>>>> Next the patch is applied with:
>>>>> $ patch -p0 < alsa-driver-1.0.17-1.patch
>>>>>
>>>>> See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
>>>>> for details on compiling and installing replacement snd-hda-intel + its
>>>>> dependent drivers.
>>>>> After the installation is completed, rerun the hsfmodem installation.
>>>>> Reboot and try to detect the modem with Root permission:
>>>>> sudo wvdialconf /etc/wvdial.conf
>>>>>
>>>>> Read DOCs/Conexant.txt
>>>>>
>>>>> Writing DOCs/Conexant.txt
>>>>>
>>>>>
>>>>> Completed candidate modem analyses.
>>>>>
>>>>> The base of the UDEV device file system is: /dev/.udev
>>>>>
>>>>> Versions adequately match for the compiler installed: 4.4.1
>>>>> and the compiler used in kernel assembly: 4.4.1
>>>>>
>>>>> 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.4
>>>>> linuc_headers base folder /lib/modules/2.6.31-14-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 277352 2009-02-21 03:25 /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.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 --------
>
>
>

Re: Vikas, India kernel 2.6.31-14-generic

2009-12-14T12:56:15Z

Vikas,

Your modem is sadly unsuppported :(

Predictive diagnostics for card in bus 00:09.0:
Modem chipset detected on
NAME="Communication controller: Analog Devices SM56 PCI modem"
CLASS=0780
PCIDEV=11d4:1805
SUBSYS=11d4:1805
IRQ=12
IDENT=Motorola_not_supported

For candidate modem in: 00:09.0
0780 Communication controller: Analog Devices SM56 PCI modem
Primary device ID: 11d4:1805
Support type needed or chipset: Motorola_not_supported

Read Modem/InfoGeneral.txt for alternatives.

Regards,

Antonio

On 12/14/09, Vikas Bhasin <vikasbhasin@...> wrote:

> 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@... 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.31-14-generic (buildd@rothera) (gcc version 4.4.1
> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
> scanModem update of: 2009_12_07
>
> The dialer utility package WVDIAL does not appear to be installed on
> your System.
> For Ubuntu Jaunty users, there are at the bottom of
> http://linmodems.technion.ac.il/packages/:
> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
> wvdial_jaunty_i386.zip for 32 bit systems.
> These are about 1 MB in size. After downloaded and copied into your
> Linux partition:
> $ unzip wv*.zip
> Within the new folder:
> $ sudo dpkg -i *.deb
> will complete the wvdial installation
> Please read Modem/DOCs/wvdial.txt for usage information.
>
> 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
>
> There are no blacklisted modem drivers in /etc/modprobe* files
>
> Potentially useful modem drivers now loaded are:
>
>
> Attached USB devices are:
> ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
> 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@...
>
> For candidate card in slot 00:09.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:09.0 11d4:1805 11d4:1805 Communication controller: Analog Devices
> SM56 PCI modem
>
> Modem interrupt assignment and sharing:
> --- Bootup diagnostics for card in PCI slot 00:09.0 ----
> [ 0.079231] pci 0000:00:09.0: reg 10 32bit mmio: [0xe7000000-0xe70000ff]
> [ 0.079275] pci 0000:00:09.0: supports D2
> [ 0.079283] pci 0000:00:09.0: PME# supported from D0 D2 D3hot
> [ 0.079292] pci 0000:00:09.0: PME# disabled
>
> The PCI slot 00:09.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@...
> if help is needed.
>
>
> === Finished firmware and bootup diagnostics, next deducing cogent software.
> ===
>
> Predictive diagnostics for card in bus 00:09.0:
> Modem chipset detected on
> NAME="Communication controller: Analog Devices SM56 PCI modem"
> CLASS=0780
> PCIDEV=11d4:1805
> SUBSYS=11d4:1805
> IRQ=12
> IDENT=Motorola_not_supported
>
> For candidate modem in: 00:09.0
> 0780 Communication controller: Analog Devices SM56 PCI modem
> Primary device ID: 11d4:1805
> Support type needed or chipset: Motorola_not_supported
>
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.4.1
> and the compiler used in kernel assembly: 4.4.1
>
> 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.4
> linuc_headers base folder /lib/modules/2.6.31-14-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 277352 2009-02-20 22:55 /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
>
>
> 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 --------
>
>
>
> --
> Thanks,
> Vikas
>

Vikas, India kernel 2.6.31-14-generic

2009-12-14T06:47:33Z

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@... 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.31-14-generic (buildd@rothera) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
scanModem update of: 2009_12_07

The dialer utility package WVDIAL does not appear to be installed on
your System.
For Ubuntu Jaunty users, there are at the bottom of
http://linmodems.technion.ac.il/packages/:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your
Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

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

There are no blacklisted modem drivers in /etc/modprobe* files

Potentially useful modem drivers now loaded are:

Attached USB devices are:
ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
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@...

For candidate card in slot 00:09.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0 11d4:1805 11d4:1805 Communication controller: Analog Devices
SM56 PCI modem

Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:09.0 ----
[ 0.079231] pci 0000:00:09.0: reg 10 32bit mmio: [0xe7000000-0xe70000ff]
[ 0.079275] pci 0000:00:09.0: supports D2
[ 0.079283] pci 0000:00:09.0: PME# supported from D0 D2 D3hot
[ 0.079292] pci 0000:00:09.0: PME# disabled

The PCI slot 00:09.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@...
if help is needed.

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

Predictive diagnostics for card in bus 00:09.0:
Modem chipset detected on
NAME="Communication controller: Analog Devices SM56 PCI modem"
CLASS=0780
PCIDEV=11d4:1805
SUBSYS=11d4:1805
IRQ=12
IDENT=Motorola_not_supported

For candidate modem in: 00:09.0
0780 Communication controller: Analog Devices SM56 PCI modem
Primary device ID: 11d4:1805
Support type needed or chipset: Motorola_not_supported

Completed candidate modem analyses.

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

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

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.4
linuc_headers base folder /lib/modules/2.6.31-14-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 277352 2009-02-20 22:55 /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

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 --------

--
Thanks,
Vikas

Technions server is down

2009-12-13T08:25:39Z

Jacques,
The Technions Linmodems server http://linmodems.technion.ac.il is down.
Please report to the List when it is up again.

MarvS

On Tue, Dec 8, 2009 at 2:18 AM, Jacques Goldberg
<Jacques.Goldberg@...> wrote:

> Done.
>
>
> Please note: leaving to Paris within a few hours, followed by Geneva
> Wednesday morning, back to Paris Thursday evening.
>
> Completely off line Saturday as usual and Sunday-Monday -> Amsterdam.
>
> I then stay in Paris until Dec 29 with good connectivity.
>
>
> Best regards
>
> Jacques
>
>
> Marvin Stodolsky wrote:
>
>> Jacques,
>> Please put the agrsm-2.6.30.tar.bz2 in the ltmodem/11c11040 folder.
>>
>> MarvS
>>
>>
>> ---------- Forwarded message ----------
>> From: Bjorn Wielens <Uniacke1@...>
>> Date: Mon, Dec 7, 2009 at 1:25 PM
>> Subject: Re: Agere systems HDA modem
>> To: Marvin Stodolsky <marvin.stodolsky@...>
>> Cc: Nikolay Zhuravlev <xxor@...>, Zsolt BÉRCZES <zsolt@...>
>>
>>
>> As attached.
>> Please note- trying to load the modules on my OpenSuSE 11.2 system gives
>> an error about the module_version symbol. using modprobe --force is
>> necessary to load the drivers and does not appear to cause ill effects.
>>
>> The modules compile without ANY warnings or errors on my computer... if
>> any appear on yours, beware of using the --force option.
>>
>> Bjorn.
>>
>>
>> Marvin Stodolsky wrote:
>>
>>>
>>> Bjorn,
>>>
>>> Please resend the tarball, it wasn't attached in any of the messages I
>>> received.
>>>
>>> Marvin
>>>
>>> On Mon, Dec 7, 2009 at 6:19 AM, Bjorn Wielens <Uniacke1@...> wrote:
>>>
>>>>
>>>> You could just use the agrsm-2.6.30 I sent out yesterday to build the
>>>> dkms tarballs. It is fully patched and ready to use (the exact source I
>>>> use on my 2.6.31 system)
>>>>
>>>> The printk issue has been removed, and I've already forwarded the
>>>> tarball to Jacques.
>>>>
>>>>
>>>> Bjorn.
>>>>
>>>> Marvin Stodolsky wrote:
>>>>
>>>>>
>>>>> Nikolay,
>>>>>
>>>>> Thanks for the great rescue!!
>>>>> Would you and Bjorn please coordinate on a final recommended tarball,
>>>>> with a 11mdv designation
>>>>>
>>>>> There should be some text on the printk() issues,
>>>>> which will be obscure to most Users including me.
>>>>>
>>>>> Then send the tarball to both Jacques, Zsolt and me as
>>>>> I can do the dkms compatibility update and the Debian installer
>>>>> package.
>>>>>
>>>>> For any suspect calls, It might be worth while looking at code
>>>>> features in the agrsm06pci-2.1.80~20090825.tar.gz
>>>>> This was a code update by the LSI/Agere maintainer to 2.6.28 kernels,
>>>>> though only for none HDA dependent 11c1:0620/30 chipsets.
>>>>>
>>>>> MarvS
>>>>>
>>>>> On Sun, Dec 6, 2009 at 3:01 PM, Nikolay Zhuravlev <xxor@...> wrote:
>>>>>
>>>>>>
>>>>>> The tarball is bzip2 compressed, not gzipped.
>>>>>> Also, Makefile.mine is not needed.
>>>>>>
>>>>>> --
>>>>>> Nick Zhuravlev
>>>>>> www.auriga.com
>>>>>>
>>>>>>
>>>>>> On Sun, Dec 06, 2009 at 03:25:50PM -0400, Bjorn Wielens
>>>>>> <Uniacke1@...> wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> This is the source (NON-DKMS) for the agrsm 11c11040 (and others
>>>>>>> supported by agrsm) on 2.6.30 or above.
>>>>>>> All patches have already been applied, including Nikolays'. Also some
>>>>>>> changes to pid handling since it used functions that were deprecated.
>>>>>>>
>>>>>>> To use you must MANUALLY change the module license from proprietary.
>>>>>>>
>>>>>>> Modem dialling sounds do NOT work in this package, hence agrMdmDaemon
>>>>>>> is
>>>>>>> NOT included.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Bjorn Wielens wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> I've stripped all the unnecessary ones from my source.
>>>>>>>> I was able to dial in and maintain a PPP session on 2.6.31 (openSuSE
>>>>>>>> 11.2 stock kernel) and now I am testing to see whether the dialling
>>>>>>>> sounds can be made to work (they worked in 2.6.27 for me, not
>>>>>>>> anymore).
>>>>>>>> I will send a tarball of sources to Jacques as soon as I get a
>>>>>>>> definitive result.
>>>>>>>>
>>>>>>>> Bjorn.
>>>>>>>>
>>>>>>>> Nikolay Zhuravlev wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> All,
>>>>>>>>>
>>>>>>>>> I got the same results for the 2.6.28.10 kernel.
>>>>>>>>> (without the patches a_18_19.patch and a_19_20.patch)
>>>>>>>>>
>>>>>>>>> Also, I noticed that the driver does quite a lot of output
>>>>>>>>> to /var/log/messages, as compared to the "7mdv" tarball:
>>>>>>>>>
>>>>>>>>> $ grep printk agrsm-2.1.80-10mdv2009.0-modified/*.c | wc -l
>>>>>>>>> 82
>>>>>>>>> $ grep printk agrsm-2.1.80-7mdv2009.0/*.c | wc -l
>>>>>>>>> 46
>>>>>>>>>
>>>>>>>>> It is better to #ifdef the printk()s and use them only for
>>>>>>>>> the debugging sessions.
>>>>>>>>>
>>>>>>>>> If something goes wrong, the /var/log/messages grows to
>>>>>>>>> hundreds of megabytes within minutes.
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>
>> >
>
>

Re: Nick, Australia kernel 2.6.31-14-generic

2009-12-13T01:11:29Z

Nick,

You have done everything according to instructions and your modem is
not functioning correctly? Did you reboot and try it again?

The wvdial packages have been updated for newer Ubuntu release
wvdial_karmic.zip, but sadly the page at linmodems is currently down
:(

Details of the Request:
URL: http://linmodems.technion.ac.il/packages/
Protocol: http
Date and Time: Sunday 13 December 2009 03:01
Additional Information: linmodems.technion.ac.il: Socket operation timed out
Description:
The server linmodems.technion.ac.il refused to allow this computer to
make a connection.

For the other problem modem not found/responding, rebooting the
machine and giving it a retry does it find the modem?

Let us know and report back.

Regards,

Antonio

On 12/13/09, Nick Wahl <nwahl@...> wrote:

> Thank you, Antonio, for your prompt help!
>
> I believe I did everything the way you recommended. However, I could
> not get it to work (yet) and, even after reading up on possible causes
> and trying possible solutions, I cannot tell why - which, of course,
> tells you how much of an expert I am at this.
>
> Please have a look at what I did and my comments in ( ).
>
> Before I attempt more complicated possible solutions, I would
> appreciate your advice. I am, therefore, also attaching dmesg.txt in
> case you need it.
>
> Your help is very much appreciated. Thank you! - Nick
>
> *************************************
> Step 1
> nw@nw:~$ sudo dpkg -i hsfmodem*.deb
> (Reading database ... 114040 files and directories currently installed.)
> Unpacking hsfmodem (from
> hsfmodem_7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb) ...
> Setting up hsfmodem (7.80.02.05full-k2.6.31-14-generic-1.ubuntu) ...
> Conexant HSF softmodem driver, version 7.80.02.05full
>
> Pre-built driver modules that seem compatible with your system were
> found under
> /usr/lib/hsfmodem/modules/binaries/linux-2.6.31-14-generic-SMP.
>
> Warning: no device detected by hsf driver - HDA modems may require reboot
>
> (Why wouldn't it be detected if it was detected by scanModem? I
> couldn't find any evidence that it has been disabled. There is some
> Firmware missing, but I can't tell if that has anything to do with
> this. I would have liked to reboot the modem, but I don't know how to
> do that.)
>
> Note: HDA support not compiled in the driver
>
> Note: kernel module snd-via82xx-modem overridden by hsfmc97via
> Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis
> Note: kernel module snd-atiixp-modem overridden by hsfmc97ati
>
> Step 2
> nw@nw:~$ sudo wvdialconf /etc/wvdial.conf
> sudo: wvdialconf: command not found
> nw@nw:~$
>
> Steps 3
> nw@nw:/etc/wvdial$ sudo unzip wv*.zip
> Archive: wvdial_jaunty_i386.zip
> inflating: wvdial_jaunty_i386/debconf_1.5.26ubuntu3_all.deb
> inflating: wvdial_jaunty_i386/libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb
> inflating:
> wvdial_jaunty_i386/libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb
> inflating:
> wvdial_jaunty_i386/libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb
> inflating: wvdial_jaunty_i386/libxplc0.3.13_0.3.13-1build1_i386.deb
> inflating: wvdial_jaunty_i386/Readme.txt.txt
> inflating: wvdial_jaunty_i386/wvdial_1.60.1+nmu2_i386.deb
>
> (I am running Ubuntu 9.10 Karmic Koala, not Jaunty and the CPU is an
> i686 not an i386. I cannot tell if that would have something to do
> with it.)
>
> Step 4
> nw@nw:/etc/wvdial/wvdial_jaunty_i386$ sudo dpkg -i *.deb
> dpkg: warning: downgrading debconf from 1.5.27ubuntu2 to 1.5.26ubuntu3.
> (Reading database ... 115932 files and directories currently installed.)
> Preparing to replace debconf 1.5.27ubuntu2 (using
> debconf_1.5.26ubuntu3_all.deb) ...
> Unpacking replacement debconf ...
> Selecting previously deselected package libuniconf4.4.
> Unpacking libuniconf4.4 (from libuniconf4.4_4.4.1-0.2ubuntu2_i386.deb) ...
> Selecting previously deselected package libwvstreams4.4-base.
> Unpacking libwvstreams4.4-base (from
> libwvstreams4.4-base_4.4.1-0.2ubuntu2_i386.deb) ...
> Selecting previously deselected package libwvstreams4.4-extras.
> Unpacking libwvstreams4.4-extras (from
> libwvstreams4.4-extras_4.4.1-0.2ubuntu2_i386.deb) ...
> Selecting previously deselected package libxplc0.3.13.
> Unpacking libxplc0.3.13 (from libxplc0.3.13_0.3.13-1build1_i386.deb) ...
> Selecting previously deselected package wvdial.
> Unpacking wvdial (from wvdial_1.60.1+nmu2_i386.deb) ...
> Setting up debconf (1.5.26ubuntu3) ...
>
> Setting up libxplc0.3.13 (0.3.13-1build1) ...
>
> Setting up libwvstreams4.4-base (4.4.1-0.2ubuntu2) ...
>
> Setting up libwvstreams4.4-extras (4.4.1-0.2ubuntu2) ...
>
> Setting up libuniconf4.4 (4.4.1-0.2ubuntu2) ...
>
> Processing triggers for man-db ...
> Setting up wvdial (1.60.1+nmu2) ...
>
> Sorry. You can retry the autodetection at any time by running
> "wvdialconf".
> (Or you can create /etc/wvdial.conf yourself.)
>
> Processing triggers for libc-bin ...
> ldconfig deferred processing now taking place
> nw@nw:/etc/wvdial/wvdial_jaunty_i386$
>
> Step 5 (trying again:)
> nw@nw:~$ sudo wvdialconf /etc/wvdial.conf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to it.
> Modem Port Scan<*1>: SHSF0 S0 S1 S2 S3 SHSF1 SHSF2 SHSF3
> Modem Port Scan<*1>: SHSF4 SHSF5 SHSF6 SHSF7
>
>
> Sorry, no modem was detected! Is it in use by another program?
> Did you configure it properly with setserial?
>
> (Why wouldn't it be detected if scanModem did? It was not used by
> another program and the info on setserial does not seem to apply here.)
>
> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>
> (There are no FAQ at the above link.)
>
> If you still have problems, send mail to <wvdial-list@...>.
> nw@nw:~$
>
> (I don't want to try this, unless wvdial is the problem.)
>
> Step 6
> nw@nw:~$ sudo gedit /etc/wvdial.conf
> [sudo] password for nw:
>
> (Details entered O.K.)
>
> Step 7
> nw@nw:~$ sudo wvdial
> --> WvDial: Internet dialer version 1.60
> --> Cannot open /dev/modem: Input/output error
> --> Cannot open /dev/modem: Input/output error
> --> Cannot open /dev/modem: Input/output error
> nw@nw:~$
> ********************************************
>
> Antonio Olivares wrote:
>> Nick,
>>
>> scanModem reports that you need hsfmodem drivers and that wvdial is
>> not installed:
>>
>> For candidate modem in: 00:1b.0
>> 0403 Audio device: Intel Corporation 82801H
>> Primary device ID: 8086:284b
>> Subsystem PCI_id 103c:30d9
>> Softmodem codec or chipset from diagnostics:
>> from Archives:
>>
>>
>>
>> Support type needed or chipset: hsfmodem
>>
>>
>> Writing DOCs/Intel.txt
>>
>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>> package with full speed enabled is available, but requires driver
>> compiling. Read DOCs/Conexant.txt
>>
>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>> download hsfmodem-7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb.zip
>> Under Linux unpack with:
>> $ unzip hsfmodem*.zip
>> Then install with:
>> $ sudo dpkg -i hsfmodem*.deb
>> Subsequently, the modem should be found with
>> $ sudo wvdialconf /etc/wvdial.conf
>> Edit in your personal information with:
>> $ sudo gedit /etc/wvdial.conf
>> and try dialing out with:
>> $ sudo wvdial.
>> See DOCs/Testing.txt for details.
>>
>> The dialer utility package WVDIAL does not appear to be installed on
>> your System.
>> For Ubuntu Jaunty users, there are at the bottom of
>> http://linmodems.technion.ac.il/packages/:
>> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
>> wvdial_jaunty_i386.zip for 32 bit systems.
>> These are about 1 MB in size. After downloaded and copied into your
>> Linux partition:
>> $ unzip wv*.zip
>> Within the new folder:
>> $ sudo dpkg -i *.deb
>> will complete the wvdial installation
>> Please read Modem/DOCs/wvdial.txt for usage information.
>>
>> Regards.
>>
>>
>> Antonio
>>
>> On 11/30/09, Nick <nwahl@...> wrote:
>>> Only plain text email is forwarded by the Discuss@... List
>>> Server,
>>> as HTML can contain viruses. Use as the email Subject Line:
>>> YourName, YourCountry kernel 2.6.31-14-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@... 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.31-14-generic (buildd@rothera) (gcc version 4.4.1
>>> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
>>> scanModem update of: 2009_11_26
>>>
>>> The dialer utility package WVDIAL does not appear to be installed on
>>> your System.
>>> For Ubuntu Jaunty users, there are at the bottom of
>>> http://linmodems.technion.ac.il/packages/:
>>> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
>>> wvdial_jaunty_i386.zip for 32 bit systems.
>>> These are about 1 MB in size. After downloaded and copied into your
>>> Linux partition:
>>> $ unzip wv*.zip
>>> Within the new folder:
>>> $ sudo dpkg -i *.deb
>>> will complete the wvdial installation
>>> Please read Modem/DOCs/wvdial.txt for usage information.
>>>
>>> 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
>>>
>>> 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 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
>>> ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device
>>> 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@...
>>>
>>> For candidate card in slot 00:1b.0, firmware information and bootup
>>> diagnostics are:
>>> PCI slot PCI ID SubsystemID Name
>>> ---------- --------- --------- --------------
>>> 00:1b.0 8086:284b 103c:30d9 Audio device: Intel Corporation 82801H
>>>
>>> Modem interrupt assignment and sharing:
>>> 22: 1051 IO-APIC-fasteoi HDA Intel
>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>>> [ 0.293090] pci 0000:00:1b.0: reg 10 64bit mmio:
>>> [0x72400000-0x72403fff]
>>> [ 0.293159] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>>> [ 0.293164] pci 0000:00:1b.0: PME# disabled
>>> [ 8.913160] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>>> low) -> IRQ 22
>>> [ 8.913198] 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@...
>>> 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.20
>>> The modem cards detected by "aplay -l" are: None
>>>
>>>
>>> The /proc/asound/pcm file reports:
>>> -----------------------
>>> 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1
>>> 00-01: Conexant Digital : Conexant Digital : playback 1
>>>
>>> about /proc/asound/cards:
>>> ------------------------
>>> 0 [Intel ]: HDA-Intel - HDA Intel
>>> HDA Intel at 0x72400000 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.31-14-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 00:1b.0:
>>> Modem chipset detected on
>>> NAME="Audio device: Intel Corporation 82801H "
>>> CLASS=0403
>>> PCIDEV=8086:284b
>>> SUBSYS=103c:30d9
>>> IRQ=22
>>> HDA=8086:284b
>>> SOFT=8086:284b.HDA
>>> IDENT=hsfmodem
>>> Driver=hsfmodem-drivers
>>>
>>> For candidate modem in: 00:1b.0
>>> 0403 Audio device: Intel Corporation 82801H
>>> Primary device ID: 8086:284b
>>> Subsystem PCI_id 103c:30d9
>>> Softmodem codec or chipset from diagnostics:
>>> from Archives:
>>>
>>>
>>>
>>> Support type needed or chipset: hsfmodem
>>>
>>>
>>> Writing DOCs/Intel.txt
>>>
>>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>>> package with full speed enabled is available, but requires driver
>>> compiling. Read DOCs/Conexant.txt
>>>
>>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>>> download hsfmodem-7.80.02.05full_k2.6.31_14_generic_ubuntu_i386.deb.zip
>>> Under Linux unpack with:
>>> $ unzip hsfmodem*.zip
>>> Then install with:
>>> $ sudo dpkg -i hsfmodem*.deb
>>> Subsequently, the modem should be found with
>>> $ sudo wvdialconf /etc/wvdial.conf
>>> Edit in your personal information with:
>>> $ sudo gedit /etc/wvdial.conf
>>> and try dialing out with:
>>> $ sudo wvdial.
>>> See DOCs/Testing.txt for details.
>>>
>>> The directions following below need only be pursued, if the above
>>> procedures are not adequate.
>>>
>>> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to
>>> find the
>>> hsfmodem package matching your System. For several Linux distros,
>>> there are
>>> precompiled drivers matched to specific kernels. These have within the
>>> FileName,
>>> your KernelVersion: 2.6.31_14_generic
>>> They can be found through
>>> http://www.linuxant.com/drivers/hsf/full/downloads.php
>>> A more precise location may be given a few paragraphs below.
>>> If an EXACT Match with your your KernelVersion is not found, one of the
>>> "Generic packages with source" near the bottom of the page must be used.
>>> Downloaded packages must be moved into the Linux partition (home
>>> folder is OK)
>>> and unzipped with:
>>> unzip hsf*.zip
>>> The installation command for a .deb suffic packages is, with root/adm
>>> permission:
>>> sudo dpkg -i hsf*.deb
>>> while for .rpm suffix it is, with:
>>> rpm -i hsf*.rpm
>>>
>>> Support for Conexant chips hosted on High Definition Audio cards may
>>> require
>>> installation of additional packages, one of the alsa-driver-linuxant
>>> packages
>>> on http://www.linuxant.com/alsa-driver/ At the same time download the
>>> alsa-driver-1.0.17-1.patch , in case it prove to be later needed.
>>> During the
>>> hsfmodem install, there will be a message if there is necessary
>>> installation of
>>> alsa-driver-linuxant
>>>
>>> The installation command for a .deb suffic packages is, with root/adm
>>> permission:
>>> sudo dpkg -i hsf*.deb
>>> while for .rpm suffix it is, with:
>>> rpm -i hsf*.rpm
>>>
>>> There may a message that "Dependencies" are not satisfied. In this
>>> case the Ubuntu/Debian packages to be installed are linux-libc-dev &
>>> libc6-dev. Package
>>> names may be different for other Linuxes. If not on your install CD,
>>> these
>>> packages can be searched for at http://packages.ubuntu.com. After
>>> download,
>>> they can be coinstalled with:
>>> sudo dpkg -i li*.deb
>>> Again try the alsa-driver-linuxant
>>>
>>> There may be a message that the patch must be applied. In this case
>>> get the
>>> ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
>>> Under Linux, this package is unpacked with:
>>> $ tar jxf alsa*.tar.bz2
>>> Next the patch is applied with:
>>> $ patch -p0 < alsa-driver-1.0.17-1.patch
>>>
>>> See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
>>> for details on compiling and installing replacement snd-hda-intel + its
>>> dependent drivers.
>>> After the installation is completed, rerun the hsfmodem installation.
>>> Reboot and try to detect the modem with Root permission:
>>> sudo wvdialconf /etc/wvdial.conf
>>>
>>> Read DOCs/Conexant.txt
>>>
>>> Writing DOCs/Conexant.txt
>>>
>>>
>>> Completed candidate modem analyses.
>>>
>>> The base of the UDEV device file system is: /dev/.udev
>>>
>>> Versions adequately match for the compiler installed: 4.4.1
>>> and the compiler used in kernel assembly: 4.4.1
>>>
>>> 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.4
>>> linuc_headers base folder /lib/modules/2.6.31-14-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 277352 2009-02-21 03:25 /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.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 --------
>>>
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.339 / Virus Database: 270.14.88/2537 - Release Date: 11/30/09
>> 21:05:00
>>
>
>
>
>

Re: Ivan,Cuba kernel 2.6.31-14-generic

2009-12-12T20:13:06Z

Ivan,

for
Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr

There is a driver package which will follow this email,
slamr-2.6.31-14-generic.tar.gz
Our regular repository at the http://linmodems.technion.ac.il/ is
offine at the moment
However, we have been having problems under the 2.6.31 kernels.
But you can test and report back.

MarvS
scanModem maintainer

2009/12/12 Ivan <jgo@...>:

>
>
>
> __________ Información de ESET Smart Security, versión de la base de firmas
> de virus 4676 (20091210) __________
>
> ESET Smart Security ha comprobado este mensaje.
>
> part000.txt - esta correcto
> ModemData.txt - esta correcto
> dmesg.txt - esta correcto
>
> http://www.eset.com
>
>
> --
> Este mensaje ha sido analizado por MailScanner Nodo Finlay, Camaguey, Cuba
> en busca de virus y otros contenidos peligrosos,
> y se considera que está limpio.
>
> Visite nuestro sitio http://nodofinlay.cmw.sld.cu
>
>
>
>
> --
>
> Este mensaje le ha llegado mediante el servicio de correo electronico que
> ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema
> Nacional de Salud. La persona que envia este correo asume el compromiso de
> usar el servicio a tales fines y cumplir con las regulaciones establecidas
>
> Infomed: http://www.sld.cu/
>

Re: KERNEL 2.6.29 and Agere Systems Soft Modem (chipset 11c1:0620)

2009-12-12T14:33:04Z

Folks,

Along with the fix suggested by John below, I have
made a few other cleanup fixes, and introduced the Kbuild
file that shall simplify the module build process, same idea
I used some time ago
for the 11c11040 chip. I do not have the 0620 chip, so
please test this patch if you can. On my notebook, it builds Ok for
the vanilla
2.6.29.1 kernel, and the modules load Ok with modprobe.

The patch is attached.

Patch and then build as follows:
$ make clean
$ make
$ sudo make modules_install
$ sudo modprobe agrmodem

General comments:

I would say that modprobe not finding the modules is a sign
of some trouble. Forcing it with insmod is a mere workaround.
Thoughts?

--
Nick Zhuravlev
www.auriga.com

On Sat, Dec 12, 2009 at 12:19:01PM -0500, John McGowan <jmcgowan@...> wrote:

> KERNEL 2.6.29 and Agere Systems Soft Modem (chipset 11c1:0620)
> ==============================================================
>
> The following is using Fedora Core11.
>
> Using agrsm06pci-2.1.80~20090825.tar.gz as the source for
> the modules to work with this modem:
>
>
> Attempting to compile the modules for kernel 2.6.29 (Fedora Core 11 with its
> PAE configuration) led to
> agrsm06pci-2.1.80~20090825/agrsoftmodem.c:263: error: too few arguments to function `__request_region'
>
> Examining
> /usr/src/linux/include/linux/ioport.h
>
> I see
> #define request_region(start,n,name) __request_region(&ioport_resource, (start), (n), (name), 0)
>
> #define __request_mem_region(start,n,name, excl) __request_region(&iomem_resource, (start), (n), (name), excl)
>
> extern struct resource * __request_region(struct resource *,
> resource_size_t start,
> resource_size_t n,
> const char *name, int flags);
>
> #define request_mem_region_exclusive(start,n,name) \
> __request_region(&iomem_resource, (start), (n), (name), IORESOURCE_EXCLUSIVE)
>
>
> and it appears that __request_region has gained another argument, a flag
> which may specify exclusivity along with request_region(start,n,name)
> which uses a value of zero for that argument.
>
> I changed the code
>
> // return(request_region(start, n, name));
> return(__request_region(&ioport_resource, (start), (n), (name)));
>
> in agrsoftmodem.c to
>
> // return(request_region(start, n, name));
> // return(__request_region(&ioport_resource, (start), (n), (name)));
> return(__request_region(&ioport_resource, (start), (n), (name), 0));
>
> It seems that request_region was originally used,
> then changed to use the more kernel-specific __request_region and
> while request_region did not change, __request_region did.
>
> I am no C-programmer but I *seem* to have gotten it to work.
>
>
> MODPROBE:
> =========
> After installing I find that modprobe will not find it.
> Howver,
> insmod -f [filename]
> is used in
> /etc/init.d/agr_softmodem
>
> /sbin/insmod -f /lib/modules`uname -r`/kernel/drivers/char/agrmodem.ko; \
> /sbin/insmod -f /lib/modules/`uname -r`/kernel/drivers/char/agrserial.ko; \
> /usr/lib/AgereSoftModem/AgereMdmDaemon
>
> so one may want to edit the material on using modprobe (which cannot
> find the module while insmod can specify the module by path/filename
> and so the attempt to load the modules in agrsm-test.txt from
> agrsm-tools-0.0.1-2.noarch.rpm using modprobe fails).
>
> service agr_softmodem (start|stop)
>
> can be used to start/stop it (inserting/removing the modules and so
> creating/removing /dev/ttyAGS3) in Fedora Core11.

diff -Naur agrsm06pci-backup/agrsoftmodem.c agrsm06pci-2.1.80~20090825/agrsoftmodem.c --- agrsm06pci-backup/agrsoftmodem.c 2009-12-13 01:04:56.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/agrsoftmodem.c 2009-12-13 01:06:09.000000000 +0300 @@ -260,7 +260,11 @@ fnatr void *x_request_region(unsigned long start, unsigned long n, const char *name) { // return(request_region(start, n, name)); +#if LINUX_VERSION_CODE <= KERNEL_VERSION(2,6,28) return(__request_region(&ioport_resource, (start), (n), (name))); +#else + return(__request_region(&ioport_resource, (start), (n), (name), 0)); +#endif } #ifndef LT_KER_26 @@ -385,22 +389,23 @@ } fnatr int x_pcibios_read_config_byte (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned char *val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_byte(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_byte(dev, where, val));} fnatr int x_pcibios_read_config_word (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned short *val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_word(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_word(dev, where, val));} fnatr int x_pcibios_read_config_dword (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned int *val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_dword(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_read_config_dword(dev, where, val));} fnatr int x_pcibios_write_config_byte (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned char val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_byte(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_byte(dev, where, val));} fnatr int x_pcibios_write_config_word (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned short val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_word(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_word(dev, where, val));} fnatr int x_pcibios_write_config_dword (unsigned char bus, unsigned char dev_fn, unsigned char where, unsigned int val) -{struct pci_dev *dev = pci_find_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_dword(dev, where, val));} +{struct pci_dev *dev = pci_get_bus_and_slot(bus, dev_fn); return ((!dev)? PCIBIOS_DEVICE_NOT_FOUND : pci_write_config_dword(dev, where, val));} + #ifndef LT_KER_26 int x_pcibios_find_class (unsigned int class_code, unsigned short index, unsigned char *bus, unsigned char *dev_fn) @@ -439,7 +444,7 @@ #else struct work_struct *x_tqueue = (struct work_struct *) task_x; - INIT_WORK(x_tqueue, wrap_LXHardwareBottomHalf); + INIT_WORK(x_tqueue, (work_func_t)wrap_LXHardwareBottomHalf); #endif } @@ -451,7 +456,7 @@ #else struct work_struct *x_tqueue = (struct work_struct *) task_x; - INIT_WORK(x_tqueue, func); + INIT_WORK(x_tqueue, (work_func_t)func); #endif } diff -Naur agrsm06pci-backup/hda.c agrsm06pci-2.1.80~20090825/hda.c --- agrsm06pci-backup/hda.c 2009-12-13 01:04:56.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/hda.c 2009-12-13 01:06:09.000000000 +0300 @@ -10,7 +10,7 @@ * *****************************************************************************/ -#include <sound/driver.h> +// #include <sound/driver.h> #include <linux/init.h> #include <linux/delay.h> #include <linux/slab.h> @@ -23,8 +23,7 @@ //#include <sound/tlv.h> #include <sound/initval.h> -//#define HDA_MODEM -//#define wake_enable +// #define HDA_MODEM #define fnatr __attribute__((regparm(0))) @@ -35,47 +34,57 @@ //#define HDAdbg struct azx_dev { struct snd_dma_buffer bdl; /* BDL buffer */ - u32 *posbuf; /* position buffer pointer */ + u32 *posbuf; /* position buffer pointer */ - unsigned int bufsize; /* size of the play buffer in bytes */ - unsigned int frags; /* number for period in the play buffer */ - unsigned int fifo_size; /* FIFO size */ + unsigned int bufsize; /* size of the play buffer in bytes */ + unsigned int period_bytes; /* size of the period in bytes */ + unsigned int frags; /* number for period in the play buffer */ + unsigned int fifo_size; /* FIFO size */ + unsigned long start_jiffies; /* start + minimum jiffies */ + unsigned long min_jiffies; /* minimum jiffies before position is valid */ - void __iomem *sd_addr; /* stream descriptor pointer */ + void __iomem *sd_addr; /* stream descriptor pointer */ - u32 sd_int_sta_mask; /* stream int status mask */ + u32 sd_int_sta_mask; /* stream int status mask */ /* pcm support */ - struct snd_pcm_substream *substream; /* assigned substream, + struct snd_pcm_substream *substream; /* assigned substream, * set in PCM open */ - unsigned int format_val; /* format value to be set in the + unsigned int format_val; /* format value to be set in the * controller and the codec */ - unsigned char stream_tag; /* assigned stream */ - unsigned char index; /* stream index */ - /* for sanity check of position buffer */ - unsigned int period_intr; + unsigned char stream_tag; /* assigned stream */ + unsigned char index; /* stream index */ unsigned int opened :1; unsigned int running :1; + unsigned int irq_pending :1; + unsigned int start_flag: 1; /* stream full start flag */ + /* + * For VIA: + * A flag to ensure DMA position is 0 + * when link position is not greater than FIFO size + */ + unsigned int insufficient :1; }; /* CORB/RIRB */ struct azx_rb { - u32 *buf; /* CORB/RIRB buffer + u32 *buf; /* CORB/RIRB buffer * Each CORB entry is 4byte, RIRB is 8byte - */ - dma_addr_t addr; /* physical address of CORB/RIRB buffer */ + * */ + dma_addr_t addr; /* physical address of CORB/RIRB buffer */ /* for RIRB */ - unsigned short rp, wp; /* read/write pointers */ - int cmds; /* number of pending requests */ - u32 res; /* last read value */ + unsigned short rp, wp; /* read/write pointers */ + int cmds; /* number of pending requests */ + u32 res; /* last read value */ }; struct azx { struct snd_card *card; struct pci_dev *pci; + int dev_index; /* chip type specific */ int driver_type; @@ -102,6 +111,7 @@ /* HD codec */ unsigned short codec_mask; + int codec_probe_mask; /* copied from probe_mask option */ struct hda_bus *bus; /* CORB/RIRB */ @@ -119,10 +129,20 @@ unsigned int single_cmd :1; unsigned int polling_mode :1; unsigned int msi :1; + unsigned int irq_pending_warned :1; + unsigned int via_dmapos_patch :1; /* enable DMA-position fix for VIA */ + unsigned int probing :1; /* codec probing phase */ /* for debugging */ - unsigned int last_cmd; /* last issued command (to sync) */ + unsigned int last_cmd; /* last issued command (to sync) */ + + /* for pending irqs */ + struct work_struct irq_pending_work; + + /* reboot notifier (for mysterious hangup problem at power-down) */ + struct notifier_block reboot_notifier; }; + extern void snd_hda_get_codec_name(struct hda_codec *, char *, int); extern struct snd_card *snd_cards[SNDRV_CARDS]; extern unsigned int snd_hda_codec_read(struct hda_codec *codec, hda_nid_t nid, int direct, @@ -130,8 +150,8 @@ extern int HDA_resume(void); extern int HDA_suspend(void); -int *ResumePt; -int *SuspendPt; +int *(ResumePt); +int *(SuspendPt); struct hda_codec *AgrHDACodec; /* assign a stream for the PCM */ @@ -150,9 +170,9 @@ chip->azx_dev[dev].opened = 1; #ifdef HDAdbg if (stream == SNDRV_PCM_STREAM_PLAYBACK) - snd_printk(KERN_WARNING "AGR_azx_assign_device SNDRV_PCM_STREAM_PLAYBACK %x %x %x\n",i,dev,&chip->azx_dev[dev]); + snd_printk(KERN_WARNING "AGR_azx_assign_device SNDRV_PCM_STREAM_PLAYBACK %x %x %p\n",i,dev,&chip->azx_dev[dev]); else - snd_printk(KERN_WARNING "AGR_azx_assign_device SNDRV_PCM_STREAM_receiveBACK %x %x %x\n",i,dev,&chip->azx_dev[dev]); + snd_printk(KERN_WARNING "AGR_azx_assign_device SNDRV_PCM_STREAM_receiveBACK %x %x %p\n",i,dev,&chip->azx_dev[dev]); #endif return &chip->azx_dev[dev]; @@ -183,15 +203,13 @@ int fnatr releaseHDAStream(void **pDev) { #ifdef HDAdbg -snd_printk(KERN_WARNING"eleaseHDAStream %x\n",*pDev); +snd_printk(KERN_WARNING"releaseHDAStream %p\n",*pDev); #endif azx_release_device(*pDev); return 1; } -#ifdef HDA_MODEM - int fnatr getHDAStream( unsigned int streamType, unsigned char *StreamId, void **pRegMap, void **pDev) { struct azx_dev * azx_dev_temp; @@ -204,23 +222,22 @@ *pRegMap = (unsigned int *)azx_dev_temp->sd_addr; *StreamId = (unsigned int) azx_dev_temp->stream_tag; #ifdef HDAdbg -printk(KERN_ALERT"getHdaStream dev = %x stream id = %x\n", azx_dev_temp, *StreamId); +printk(KERN_ALERT"getHdaStream dev = %p stream id = %x\n", azx_dev_temp, *StreamId); #endif return 1; } -unsigned long * GetHDABaseAddress() +unsigned long * GetHDABaseAddress(void) { struct azx *chip_temp; struct hda_bus *bus_temp; -struct hda_codec *codec_temp; -unsigned long temp; +unsigned long *temp; chip_temp = snd_cards[0]->private_data; bus_temp = chip_temp->bus; #ifdef HDAdbg -snd_printk(KERN_ERR"HDA chip address %x \n",chip_temp->remap_addr); +snd_printk(KERN_ERR"HDA chip address %p \n",chip_temp->remap_addr); #endif temp = (unsigned long *) chip_temp->remap_addr; @@ -234,100 +251,87 @@ unsigned long *temp; struct azx *chip_temp; struct hda_bus *bus_temp; -struct hda_codec *codec_temp; chip_temp = snd_cards[0]->private_data; //probe bus_temp = chip_temp->bus; //hda register dump -snd_printk(KERN_ERR"HDA chip address %x \n",chip_temp->remap_addr); +snd_printk(KERN_ERR"HDA chip address %p \n",chip_temp->remap_addr); temp = (unsigned long *) chip_temp->remap_addr; for (i=0; i<(0x1A0/4);) { - snd_printk(KERN_ERR"HDA register %04X %08X %08X %08X %08X\n",i*4,temp[i],temp[i+1],temp[i+2],temp[i+3]); + snd_printk(KERN_ERR"HDA register %04X %08lX %08lX %08lX %08lX\n",i*4,temp[i],temp[i+1],temp[i+2],temp[i+3]); i = i+4; } } char findHDACodec(void) { -int i; -struct azx *chip_temp; -struct hda_bus *bus_temp; -struct hda_codec *codec_temp; + int i; + struct azx *chip_temp; + struct hda_bus *bus_temp; + struct hda_codec *codec_temp; -chip_temp = snd_cards[0]->private_data; //probe -bus_temp = chip_temp->bus; + chip_temp = snd_cards[0]->private_data; //probe + bus_temp = chip_temp->bus; -for (i=0; i<16; i++) -{ - codec_temp = bus_temp->caddr_tbl[i]; - if (codec_temp == 0) - return 0; - if ((codec_temp->vendor_id >> 16) == 0x11C1) + for (i=0; i<16; i++) { + codec_temp = bus_temp->caddr_tbl[i]; + if (codec_temp == 0) + return 0; + if ((codec_temp->vendor_id >> 16) == 0x11C1) + { #ifdef HDAdbg - snd_printk(KERN_ERR"found agr codec vendor id %x %x\n",codec_temp->vendor_id,codec_temp->addr & 0x0f); + snd_printk(KERN_ERR"found agr codec vendor id %x %x\n",codec_temp->vendor_id,codec_temp->addr & 0x0f); #endif - AgrHDACodec = codec_temp; - return (codec_temp->addr & 0x0F); + AgrHDACodec = codec_temp; + return (codec_temp->addr & 0x0F); + } } + return -ESRCH; } -} -#else - -int fnatr getHDAStream( unsigned int streamType, unsigned char *StreamId, void **pRegMap, void **pDev){} -unsigned long * GetHDABaseAddress() {} -void HDAdump(void) {} -char findHDACodec(void) {} -#endif - void fnatr azlGetResourceInformation(unsigned char *codecAddress, unsigned char* functionGroupStartNode) { -codecAddress[0] = findHDACodec(); +#ifdef HDAdbg + HDAdump(); +#endif + codecAddress[0] = findHDACodec(); } int fnatr setResumeCallBack(int *ResumeCallBack) { -#ifdef wake_enable -ResumePt = AgrHDACodec->patch_ops.resume; -AgrHDACodec->patch_ops.resume=ResumeCallBack; -#endif -return(1); + ResumePt = (int *)AgrHDACodec->patch_ops.resume; + AgrHDACodec->patch_ops.resume=(void *)ResumeCallBack; + return(1); } int fnatr setSuspendCallBack(int *SuspendCallBack) { -#ifdef wake_enable -SuspendPt = AgrHDACodec->patch_ops.suspend; -AgrHDACodec->patch_ops.suspend=SuspendCallBack; -#endif -return(1); + SuspendPt = (int *)AgrHDACodec->patch_ops.suspend; + AgrHDACodec->patch_ops.suspend=(void *)SuspendCallBack; + return(1); } -int fnatr resetResumeCallBack() +int fnatr resetResumeCallBack(void) { -#ifdef wake_enable -AgrHDACodec->patch_ops.resume=ResumePt; -#endif -return(1); + AgrHDACodec->patch_ops.resume=(void *)ResumePt; + return(1); } -int fnatr resetSuspendCallBack() +int fnatr resetSuspendCallBack(void) { -#ifdef wake_enable -AgrHDACodec->patch_ops.suspend=SuspendPt; -#endif -return(1); + AgrHDACodec->patch_ops.suspend=(void *)SuspendPt; + return(1); } unsigned long fnatr LnxTransferCodecVerbs(unsigned long* cmd) { -unsigned int CodecAddress, nid,direct, verb, para, rvalue; +unsigned int nid,direct, verb, para, rvalue=0; //snd_printk(KERN_ERR"azlTransferCodecVerbs %x\n", *cmd); nid = (*cmd >> 20) & 0x7F; direct = (*cmd >> 27) & 1; verb = (*cmd >> 8) & 0xFFF; para = *cmd & 0xFF; #ifdef HDAdbg -snd_printk(KERN_ERR"azlTransferCodecVerbs %x %x %x %x %x %x\n",AgrHDACodec, nid, direct, verb, para); +snd_printk(KERN_ERR"azlTransferCodecVerbs %p %x %x %x %x\n",AgrHDACodec, nid, direct, verb, para); #endif if (AgrHDACodec == 0) return 0; @@ -341,14 +345,14 @@ } unsigned long fnatr LnxTransferCodecVerbsWrite(unsigned long* cmd) { -unsigned int CodecAddress, nid,direct, verb, para, rvalue; +unsigned int nid,direct, verb, para, rvalue=0; //snd_printk(KERN_ERR"azlTransferCodecVerbsWrite %x\n", *cmd); nid = (*cmd >> 20) & 0x7F; direct = (*cmd >> 27) & 1; verb = (*cmd >> 8) & 0xFFF; para = *cmd & 0xFF; #ifdef HDAdbg -snd_printk(KERN_ERR"azlTransferCodecVerbsWrite %x %x %x %x %x %x\n",AgrHDACodec, nid, direct, verb, para); +snd_printk(KERN_ERR"azlTransferCodecVerbsWrite %p %x %x %x %x\n",AgrHDACodec, nid, direct, verb, para); #endif if (AgrHDACodec == 0) return 0; diff -Naur agrsm06pci-backup/Kbuild agrsm06pci-2.1.80~20090825/Kbuild --- agrsm06pci-backup/Kbuild 1970-01-01 03:00:00.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/Kbuild 2009-12-12 01:04:44.000000000 +0300 @@ -0,0 +1,14 @@ +obj-m += agrmodem.o agrserial.o + +# Stupid definition of LT_KER_26 +EXTRA_CFLAGS += -Wall -DLT_KER_26 +# For Debug Build use next line too +#EXTRA_CFLAGS += -DHDAdbg -DDebIn -DDebAc +EXTRA_CFLAGS += -Isound/pci/hda -Idrivers/serial +# Ubuntu/Debian Users - Fix this Path to your alsa version +#EXTRA_CFLAGS += -I/usr/src/modules/alsa/alsa-driver-VERSION/alsa-kernel/pci/hda + +EXTRA_LDFLAGS := -d +agrmodem-objs := agrsoftmodem.o agrmodemlib.o hda.o +agrserial-objs := serial26.o + diff -Naur agrsm06pci-backup/Makefile agrsm06pci-2.1.80~20090825/Makefile --- agrsm06pci-backup/Makefile 2009-12-13 01:05:49.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/Makefile 2009-12-13 01:06:00.000000000 +0300 @@ -5,91 +5,27 @@ # Description: # Makes the following modules # - Agere Soft Modem Controller driver module -# - Modem Serial Interface driver module +# - Modem Serail Interface driver module # # Usage: -# make install: to make and install the driver modules -# make uninstall: to uninstall the driver modules +# make - build the module(s) +# make modules_install - install the module(s) +# make clean - remove generated files in module directory only # # Revision History: # Name Date Change # Soumyendu Sarkar 12/03/2002 Initial # -KERNEL_DIR = /lib/modules/`uname -r`/build/ -#KERNEL_DIR = /usr/src/linux-`uname -r | sed -e 's,\-default,,'`/ -#KERNEL_DIR = /usr/src/linux-`uname -r | sed -e 's,\-.*,,'`/ -KERNEL_DIR1 = /usr/src/linux-`uname -r`/include -KERNEL_DIR2 = /usr/src/linux-`uname -r | sed -e 's,\-.*,,'`/include -KERNEL_DIR5 = /usr/src/linux-`uname -r | sed -e 's,\-.*,,'`/include/asm/mach-default -KERNEL_DIR3 = /usr/src/linux-`uname -r | sed -e 's,\..*,,'`.`uname -r | sed -e 's,[^\.]*\.,,' -e 's,\..*,,'`/include -KERNEL_DIR4 = /usr/src/linux-`uname -r | sed -e 's,\-.*,,'`.SuSE/include +PWD := $(shell pwd) +KRELEASE = $(shell uname -r) +KERNEL_DIR := /lib/modules/$(KRELEASE)/build -I_FLAGS = -I$(KERNEL_DIR1) -I$(KERNEL_DIR2) -I$(KERNEL_DIR5) -I$(KERNEL_DIR3) -I$(KERNEL_DIR4)/include +default: + $(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules -#C_FLAGS = -Wall -Wno-unused -O2 -fomit-frame-pointer -fno-strength-reduce -pipe\ -# -mcpu=i486 -falign-loops=2 -falign-jumps=2 -falign-functions=2 \ -# -DMODULE -D__KERNEL__ -DLT_KER_24 -DLT_KER_26 -DKERNEL_DIR -DNO_EEPROM - -C_FLAGS = -Wall -Wno-unused -O1 -fomit-frame-pointer -fno-strength-reduce -pipe \ - -fno-gcse-after-reload \ - -falign-loops=2 -falign-jumps=2 -falign-functions=2 \ - -DMODULE -D__KERNEL__ -DLT_KER_24 -DLT_KER_26 -DNO_EEPROM $(I_FLAGS) - -EXTRA_CFLAGS += -Wall -DLT_KER_24 -DLT_KER_26 -DNO_EEPROM - -EXTRA_LDFLAGS := -d - -help : - @echo '' - @echo 'Run "make install" to install Agere Systems Soft Modem on your system.' - @echo 'Run "make uninstall" to remove a previously installed modem.' - @echo '' - -agrmodem-objs := \ - agrsoftmodem.o agrmodemlib.o hda.o - -agrserial-objs := \ - serial26.o - -obj-m += agrmodem.o agrserial.o - -module: -# cp ../../build/Linux/dbg-agr-linux-fedora-6-0/bin/AGRSMDM_lib.o agrmodemlib.o - - make -C $(KERNEL_DIR) SUBDIRS=$(PWD) modules - -$(obj)/agrmodemlib.o: - cp $(src)/agrmodemlib.o $(obj)/agrmodemlib.o +modules_install: + $(MAKE) -C $(KERNEL_DIR) M=$(PWD) modules_install clean: - rm -f *.a - rm -f *~ - rm -f agrmodem.o - rm -f agrmodem.ko - rm -f agrmodem.mod.o - rm -f agrmodem.mod.c - rm -f agrserial.o - rm -f agrserial.ko - rm -f agrserial.mod.o - rm -f agrserial.mod.c - rm -f agrsoftmodem.o - rm -f serial26.o - rm -f HDA.o - rm -f hda.o - rm -f modules.order - rm -f Module.symvers - rm -f Module.markers - -distclean: clean - rm -f .*.cmd - rm -rf .tmp_versions - -install: - ./agrinst - -uninstall : - ./agruninst - - - + $(MAKE) -C $(KERNEL_DIR) M=$(PWD) clean diff -Naur agrsm06pci-backup/modules.order agrsm06pci-2.1.80~20090825/modules.order --- agrsm06pci-backup/modules.order 1970-01-01 03:00:00.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/modules.order 2009-12-13 01:15:01.000000000 +0300 @@ -0,0 +1,2 @@ +kernel//home/ndz/SOURCES/modem/agrsm06pci-2.1.80~20090825/agrmodem.ko +kernel//home/ndz/SOURCES/modem/agrsm06pci-2.1.80~20090825/agrserial.ko diff -Naur agrsm06pci-backup/README agrsm06pci-2.1.80~20090825/README --- agrsm06pci-backup/README 2009-12-13 01:05:49.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/README 1970-01-01 03:00:00.000000000 +0300 @@ -1,52 +0,0 @@ -Please note that this software is distributed under the Agere Systems Soft -Modem End User SOFTWARE LICENSE AGREEMENT, which can be found in the file -LICENSE, included in this package - -Please note that this version of the driver is intended to work Red Flag NE 5.0 -having Linux kernel version 2.6.21.0-22 - -################################################################# -INSTALLING THE AGERE SOFT MODEM DRIVER VERSION 2.1.80 -from the sandard driver package ( zip / tar.gz archieve) - -Step 1 -Uninstall any older version of the Agere soft modem driver by running -"make uninstall" from the directory containing the previously installed -Agere softmodem driver. - -Step 2 -To install the Agere soft modem driver in LINUX, extract the driver package -(unzip /tar -xzvf) in a directory under Linux. - -To install the modem driver you must be logged in as root. - -If your kernel version matches the one stated above, run "make install" from -the command prompt. This will install both the Agere soft modem controller -driver agrmodem.ko and the Modem serial interface driver agrserial.ko. - -If your kernel version doesn't matches the one stated above, channces are you -need to regenerate agrmodem.ko & agrserial.ko. Make sure that you have the -kernel source installed in your system and the kernel directory is linked to -/usr/src/linux. Run "make module" and then "make install" from the command prompt. - -Step 3 -To use Agere soft modem using KPPP choose "/dev/ttyAGS3" or "/dev/modem" as the modem device. - -To use the Agere soft modem, you can configure "minicom" for the modem device. -Enter "minicom -s" at the command prompt. -Choose "Serial Port Setup" -For "Serial Device" choose "/dev/ttyAGS3" or "/dev/modem" -Save settings as default (dfl) and start using the modem with minicom. - -UNINSTALLING THE MODEM DRIVER - -Following are the steps to follow to uninstall the Agere soft modem driver for -Linux. - -Step 1 -To uninstall the Agere soft modem driver in LINUX, you can run "make uninstall" -from the command prompt. To uninstall the modem driver you must be logged in as -root. - - - diff -Naur agrsm06pci-backup/serial26.c agrsm06pci-2.1.80~20090825/serial26.c --- agrsm06pci-backup/serial26.c 2009-12-13 01:04:56.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/serial26.c 2009-12-13 01:06:09.000000000 +0300 @@ -69,8 +69,7 @@ static char *serialif_revdate = "2007-10-01"; static char *serialif_name = "Agere Modem Interface driver"; #endif -//bala-dbg -//#include <linux/config.h> +#include <linux/version.h> #include <linux/module.h> #include <linux/tty.h> #include <linux/ioport.h> @@ -290,7 +289,11 @@ struct ltmodem_ops lt_modem_ops; struct ltmodem_res lt_modem_res; +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) +static void agr_rs_interrupt (unsigned long z); +#else static void agr_rs_interrupt (void); +#endif static int intf_flag = 0; static int uart_flag = 0; static int tx_empty_flag = 0; @@ -929,7 +932,11 @@ up->port.irq = (irq > 0) ? irq : 0; } +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) +static void serial8250_stop_tx(struct uart_port *port) +#else static void serial8250_stop_tx(struct uart_port *port, unsigned int tty_stop) +#endif { struct uart_8250_port *up = (struct uart_8250_port *)port; @@ -937,13 +944,21 @@ up->ier &= ~UART_IER_THRI; serial_out(up, UART_IER, up->ier); } +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) + if (up->port.type == PORT_16C950) { +#else if (up->port.type == PORT_16C950 && tty_stop) { +#endif up->acr |= UART_ACR_TXDIS; serial_icr_write(up, UART_ACR, up->acr); } } +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) +static void serial8250_start_tx(struct uart_port *port) +#else static void serial8250_start_tx(struct uart_port *port, unsigned int tty_start) +#endif { struct uart_8250_port *up = (struct uart_8250_port *)port; @@ -954,7 +969,11 @@ /* * We only do this from uart_start */ +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) + if (up->port.type == PORT_16C950) { +#else if (tty_start && up->port.type == PORT_16C950) { +#endif up->acr &= ~UART_ACR_TXDIS; serial_icr_write(up, UART_ACR, up->acr); } @@ -1064,7 +1083,11 @@ return; } if (uart_circ_empty(xmit) || uart_tx_stopped(&up->port)) { +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) + serial8250_stop_tx(&up->port); +#else serial8250_stop_tx(&up->port, 0); +#endif return; } @@ -1083,7 +1106,11 @@ DEBUG_INTR("THRE..."); if (uart_circ_empty(xmit)) +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) + serial8250_stop_tx(&up->port); +#else serial8250_stop_tx(&up->port, 0); +#endif } static _INLINE_ void check_modem_status(struct uart_8250_port *up) @@ -1196,7 +1223,11 @@ } #ifdef LUCENT_MODEM +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) +static void agr_rs_interrupt (unsigned long z) +#else static void agr_rs_interrupt (void) +#endif { serial8250_interrupt(lt_modem_res.Irq,NULL,NULL); if(start_int) @@ -1658,8 +1689,13 @@ } static void -serial8250_set_termios(struct uart_port *port, struct termios *termios, - struct termios *old) +serial8250_set_termios(struct uart_port *port, +#if LINUX_VERSION_CODE >= KERNEL_VERSION (2, 6, 22) + struct ktermios *termios, +#else + struct termios *termios, +#endif + struct ktermios *old) { struct uart_8250_port *up = (struct uart_8250_port *)port; unsigned char cval, fcr = 0; diff -Naur agrsm06pci-backup/test.sh agrsm06pci-2.1.80~20090825/test.sh --- agrsm06pci-backup/test.sh 2009-12-13 01:05:49.000000000 +0300 +++ agrsm06pci-2.1.80~20090825/test.sh 1970-01-01 03:00:00.000000000 +0300 @@ -1,10 +0,0 @@ -#!/bin/bash - -$count=1; -while [ 1 ] -do -echo "Test count:: $count" -sleep 1 -sudo make uninstall install -count=`expr $count + 1` -done

Re: KERNEL 2.6.29 and Agere Systems Soft Modem (chipset 11c1:0620)

2009-12-12T14:29:58Z

I forgot to mention that agrmodemlib.o needs to be renamed
agrmodemlib.o_shipped before the make, to mark it as a prebuilt binary
blob.
Otherwise 'make clean' will delete it.

--
Nick Zhuravlev
www.auriga.com

On Sat, Dec 12, 2009 at 12:19:01PM -0500, John McGowan <jmcgowan@...> wrote:

Ivan,Cuba kernel 2.6.31-14-generic

2009-12-12T11:38:12Z

__________ Información de ESET Smart Security, versión de la base de firmas de virus 4676 (20091210) __________

ESET Smart Security ha comprobado este mensaje.

part000.txt - esta correcto
ModemData.txt - esta correcto
dmesg.txt - esta correcto

http://www.eset.com

--
Este mensaje ha sido analizado por MailScanner Nodo Finlay, Camaguey, Cuba
en busca de virus y otros contenidos peligrosos,
y se considera que está limpio.

Visite nuestro sitio http://nodofinlay.cmw.sld.cu

--

Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas

Infomed: http://www.sld.cu/

Only plain text email is forwarded by the Discuss@... List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.31-14-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@... 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.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
scanModem update of: 2009_02_28

There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:

Attached USB devices are:
ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
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@...

For candidate card in slot 00:08.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:08.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem

Modem interrupt assignment and sharing:
19: 0 IO-APIC-fasteoi eth0
--- Bootup diagnostics for card in PCI slot 00:08.0 ----
[ 0.103798] pci 0000:00:08.0: reg 10 32bit mmio: [0xdfff3000-0xdfff3fff]
[ 0.103807] pci 0000:00:08.0: reg 14 io port: [0xe000-0xe0ff]
[ 0.103859] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 0.103865] pci 0000:00:08.0: PME# disabled
[ 0.904839] serial 0000:00:08.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 0.904983] 0000:00:08.0: ttyS2 at I/O 0xe008 (irq = 19) is a 16450
[ 0.905063] 0000:00:08.0: ttyS3 at I/O 0xe010 (irq = 19) is a 8250
[ 0.905090] Couldn't register serial port 0000:00:08.0: -28

The PCI slot 00:08.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@...
if help is needed.

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

Predictive diagnostics for card in bus 00:08.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=19
IDENT=slamr

For candidate modem in: 00:08.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr

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

1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt

The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.

For 2.6.31-14-generic compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz

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.4.1
and the compiler used in kernel assembly: 4.4.1

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.4
linuc_headers base folder /lib/modules/2.6.31-14-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 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.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

CPU0
0: 47 IO-APIC-edge timer
1: 283 IO-APIC-edge i8042
3: 14 IO-APIC-edge
4: 16 IO-APIC-edge
6: 5 IO-APIC-edge floppy
7: 0 IO-APIC-edge parport0
8: 0 IO-APIC-edge rtc0
9: 0 IO-APIC-fasteoi acpi
14: 25286 IO-APIC-edge pata_sis
15: 0 IO-APIC-edge pata_sis
17: 46314 IO-APIC-fasteoi sata_sis
18: 3773 IO-APIC-fasteoi saa7130[0], SiS SI7012
19: 0 IO-APIC-fasteoi eth0
20: 52191 IO-APIC-fasteoi ohci_hcd:usb2
21: 0 IO-APIC-fasteoi ohci_hcd:usb3
22: 0 IO-APIC-fasteoi ohci_hcd:usb4
23: 2 IO-APIC-fasteoi ehci_hcd:usb1
NMI: 0 Non-maskable interrupts
LOC: 342266 Local timer interrupts
SPU: 0 Spurious interrupts
CNT: 0 Performance counter interrupts
PND: 0 Performance pending work
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
THR: 0 Threshold APIC interrupts
MCE: 0 Machine check exceptions
MCP: 8 Machine check polls
ERR: 0
MIS: 0

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 (Ubuntu 2.6.31-14.48-generic)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000002dfb0000 (usable)
[ 0.000000] BIOS-e820: 000000002dfb0000 - 000000002dfc0000 (ACPI data)
[ 0.000000] BIOS-e820: 000000002dfc0000 - 000000002dff0000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000002dff0000 - 000000002e000000 (reserved)
[ 0.000000] BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x2dfb0 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-EFFFF uncachable
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FE0000000 write-back
[ 0.000000] 1 base 020000000 mask FF8000000 write-back
[ 0.000000] 2 base 028000000 mask FFC000000 write-back
[ 0.000000] 3 base 02C000000 mask FFE000000 write-back
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable)
[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000002dfb0000 (usable)
[ 0.000000] modified: 000000002dfb0000 - 000000002dfc0000 (ACPI data)
[ 0.000000] modified: 000000002dfc0000 - 000000002dff0000 (ACPI NVS)
[ 0.000000] modified: 000000002dff0000 - 000000002e000000 (reserved)
[ 0.000000] modified: 00000000ff780000 - 0000000100000000 (reserved)
[ 0.000000] initial memory mapped : 0 - 00c00000
[ 0.000000] init_memory_mapping: 0000000000000000-000000002dfb0000
[ 0.000000] Using x86 segment limits to approximate NX protection
[ 0.000000] 0000000000 - 0000400000 page 4k
[ 0.000000] 0000400000 - 002dc00000 page 2M
[ 0.000000] 002dc00000 - 002dfb0000 page 4k
[ 0.000000] kernel direct mapping tables up to 2dfb0000 @ 10000-15000
[ 0.000000] RAMDISK: 220b8000 - 22803ad6
[ 0.000000] ACPI: RSDP 000fad80 00014 (v00 ACPIAM)
[ 0.000000] ACPI: RSDT 2dfb0000 00030 (v01 A M I OEMRSDT 01000625 MSFT 00000097)
[ 0.000000] ACPI: FACP 2dfb0200 00081 (v02 A M I OEMFACP 01000625 MSFT 00000097)
[ 0.000000] ACPI: DSDT 2dfb03f0 03875 (v01 100XX 100XX001 00000001 INTL 02002026)
[ 0.000000] ACPI: FACS 2dfc0000 00040
[ 0.000000] ACPI: APIC 2dfb0390 0005C (v01 A M I OEMAPIC 01000625 MSFT 00000097)
[ 0.000000] ACPI: OEMB 2dfc0040 00040 (v01 A M I AMI_OEM 01000625 MSFT 00000097)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 735MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 2dfb0000
[ 0.000000] low ram: 0 - 2dfb0000
[ 0.000000] node 0 low ram: 00000000 - 2dfb0000
[ 0.000000] node 0 bootmap 00011000 - 00016bf8
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 002dfb0000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
[ 0.000000] #3 [0000100000 - 00008a80a0] TEXT DATA BSS ==> [0000100000 - 00008a80a0]
[ 0.000000] #4 [00220b8000 - 0022803ad6] RAMDISK ==> [00220b8000 - 0022803ad6]
[ 0.000000] #5 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
[ 0.000000] #6 [00008a9000 - 00008ac21c] BRK ==> [00008a9000 - 00008ac21c]
[ 0.000000] #7 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
[ 0.000000] #8 [0000011000 - 0000017000] BOOTMAP ==> [0000011000 - 0000017000]
[ 0.000000] found SMP MP-table at [c00ff780] ff780
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x0002dfb0
[ 0.000000] HighMem 0x0002dfb0 -> 0x0002dfb0
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0002dfb0
[ 0.000000] On node 0 totalpages: 188223
[ 0.000000] free_area_init_node: node 0, pgdat c0784900, node_mem_map c1000200
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3951 pages, LIFO batch:0
[ 0.000000] Normal zone: 1440 pages used for memmap
[ 0.000000] Normal zone: 182800 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled)
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] SMP: Allowing 2 CPUs, 1 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 24
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e4000
[ 0.000000] PM: Registered nosave memory: 00000000000e4000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at 2e000000 (gap: 2e000000:d1780000)
[ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages at c15c4000, static data 35612 bytes
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 186751
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=bb6691f8-a61e-4710-9cb2-f37b5134de07 ro quiet splash
[ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 3766400 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
[ 0.000000] Memory: 726768k/753344k available (4565k kernel code, 25840k reserved, 2143k data, 540k init, 0k highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfff1d000 - 0xfffff000 ( 904 kB)
[ 0.000000] pkmap : 0xff800000 - 0xffc00000 (4096 kB)
[ 0.000000] vmalloc : 0xee7b0000 - 0xff7fe000 ( 272 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xedfb0000 ( 735 MB)
[ 0.000000] .init : 0xc078e000 - 0xc0815000 ( 540 kB)
[ 0.000000] .data : 0xc0575554 - 0xc078d308 (2143 kB)
[ 0.000000] .text : 0xc0100000 - 0xc0575554 (4565 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] NR_IRQS:2304 nr_irqs:424
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2918.746 MHz processor.
[ 0.001149] Console: colour VGA+ 80x25
[ 0.001154] console [tty0] enabled
[ 0.001210] Calibrating delay loop (skipped), value calculated using timer frequency.. 5837.49 BogoMIPS (lpj=11674984)
[ 0.001242] Security Framework initialized
[ 0.001271] AppArmor: AppArmor initialized
[ 0.001281] Mount-cache hash table entries: 512
[ 0.001499] Initializing cgroup subsys ns
[ 0.001510] Initializing cgroup subsys cpuacct
[ 0.001515] Initializing cgroup subsys memory
[ 0.001525] Initializing cgroup subsys freezer
[ 0.001528] Initializing cgroup subsys net_cls
[ 0.001557] CPU: Trace cache: 12K uops, L1 D cache: 16K
[ 0.001562] CPU: L2 cache: 256K
[ 0.001565] CPU: Hyper-Threading is disabled
[ 0.001571] mce: CPU supports 4 MCE banks
[ 0.001588] CPU0: Thermal monitoring enabled (TM2)
[ 0.001595] using mwait in idle threads.
[ 0.001609] Performance Counters: no PMU driver, software counters only.
[ 0.001619] Checking 'hlt' instruction... OK.
[ 0.017196] SMP alternatives: switching to UP code
[ 0.028023] ACPI: Core revision 20090521
[ 0.038971] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.078960] CPU0: Intel(R) Celeron(R) CPU 2.93GHz stepping 09
[ 0.080001] Brought up 1 CPUs
[ 0.080001] Total of 1 processors activated (5837.49 BogoMIPS).
[ 0.080001] CPU0 attaching NULL sched-domain.
[ 0.080001] Booting paravirtualized kernel on bare hardware
[ 0.080001] regulator: core version 0.5
[ 0.080001] Time: 11:58:40 Date: 12/12/09
[ 0.080001] NET: Registered protocol family 16
[ 0.080001] EISA bus registered
[ 0.080001] ACPI: bus type pci registered
[ 0.080001] PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
[ 0.080001] PCI: Using configuration type 1 for base access
[ 0.080448] bio: create slab <bio-0> at 0
[ 0.081217] ACPI: EC: Look up EC in DSDT
[ 0.092019] ACPI: Interpreter enabled
[ 0.092033] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.092070] ACPI: Using IOAPIC for interrupt routing
[ 0.102548] ACPI Warning: Incorrect checksum in table [OEMB] - FE, should be EF 20090521 tbutils-246
[ 0.102670] ACPI: No dock devices found.
[ 0.102871] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.102951] pci 0000:00:00.0: reg 10 32bit mmio: [0xe0000000-0xe3ffffff]
[ 0.103158] pci 0000:00:02.5: reg 10 io port: [0x00-0x07]
[ 0.103166] pci 0000:00:02.5: reg 14 io port: [0x00-0x03]
[ 0.103174] pci 0000:00:02.5: reg 18 io port: [0x00-0x07]
[ 0.103182] pci 0000:00:02.5: reg 1c io port: [0x00-0x03]
[ 0.103191] pci 0000:00:02.5: reg 20 io port: [0xffa0-0xffaf]
[ 0.103226] pci 0000:00:02.5: PME# supported from D3cold
[ 0.103232] pci 0000:00:02.5: PME# disabled
[ 0.103277] pci 0000:00:02.7: reg 10 io port: [0xe800-0xe8ff]
[ 0.103286] pci 0000:00:02.7: reg 14 io port: [0xec00-0xec7f]
[ 0.103335] pci 0000:00:02.7: supports D1 D2
[ 0.103338] pci 0000:00:02.7: PME# supported from D3hot D3cold
[ 0.103343] pci 0000:00:02.7: PME# disabled
[ 0.103372] pci 0000:00:03.0: reg 10 32bit mmio: [0xdfff4000-0xdfff4fff]
[ 0.103435] pci 0000:00:03.1: reg 10 32bit mmio: [0xdfff5000-0xdfff5fff]
[ 0.103497] pci 0000:00:03.2: reg 10 32bit mmio: [0xdfff6000-0xdfff6fff]
[ 0.103571] pci 0000:00:03.3: reg 10 32bit mmio: [0xdfff7000-0xdfff7fff]
[ 0.103625] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold
[ 0.103630] pci 0000:00:03.3: PME# disabled
[ 0.103678] pci 0000:00:05.0: reg 10 io port: [0xeff0-0xeff7]
[ 0.103686] pci 0000:00:05.0: reg 14 io port: [0xefe4-0xefe7]
[ 0.103694] pci 0000:00:05.0: reg 18 io port: [0xefa8-0xefaf]
[ 0.103702] pci 0000:00:05.0: reg 1c io port: [0xefe0-0xefe3]
[ 0.103710] pci 0000:00:05.0: reg 20 io port: [0xef90-0xef9f]
[ 0.103718] pci 0000:00:05.0: reg 24 io port: [0xe480-0xe4ff]
[ 0.103747] pci 0000:00:05.0: PME# supported from D3cold
[ 0.103752] pci 0000:00:05.0: PME# disabled
[ 0.103798] pci 0000:00:08.0: reg 10 32bit mmio: [0xdfff3000-0xdfff3fff]
[ 0.103807] pci 0000:00:08.0: reg 14 io port: [0xe000-0xe0ff]
[ 0.103859] pci 0000:00:08.0: PME# supported from D0 D3hot D3cold
[ 0.103865] pci 0000:00:08.0: PME# disabled
[ 0.103908] pci 0000:00:0a.0: reg 10 32bit mmio: [0xdfff2c00-0xdfff2fff]
[ 0.103963] pci 0000:00:0a.0: supports D1 D2
[ 0.104033] pci 0000:00:0b.0: reg 10 io port: [0xee00-0xeeff]
[ 0.104042] pci 0000:00:0b.0: reg 14 32bit mmio: [0xdfff2800-0xdfff28ff]
[ 0.104093] pci 0000:00:0b.0: supports D1 D2
[ 0.104095] pci 0000:00:0b.0: PME# supported from D1 D2 D3hot D3cold
[ 0.104101] pci 0000:00:0b.0: PME# disabled
[ 0.104193] pci 0000:01:00.0: reg 10 32bit mmio: [0xd0000000-0xd7ffffff]
[ 0.104201] pci 0000:01:00.0: reg 14 32bit mmio: [0xdfee0000-0xdfefffff]
[ 0.104208] pci 0000:01:00.0: reg 18 io port: [0xdc00-0xdc7f]
[ 0.104247] pci 0000:01:00.0: supports D1 D2
[ 0.104292] pci 0000:00:01.0: bridge io port: [0xd000-0xdfff]
[ 0.104298] pci 0000:00:01.0: bridge 32bit mmio: [0xdfe00000-0xdfefffff]
[ 0.104304] pci 0000:00:01.0: bridge 32bit mmio pref: [0xcfd00000-0xdfcfffff]
[ 0.104315] pci_bus 0000:00: on NUMA node 0
[ 0.104324] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.112625] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 12 14 15)
[ 0.112795] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 7 10 11 12 14 15)
[ 0.112946] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 11 12 14 15)
[ 0.113096] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 12 14 15)
[ 0.113244] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 7 10 11 12 14 15)
[ 0.113393] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 7 10 11 12 14 15)
[ 0.113541] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 *10 11 12 14 15)
[ 0.113699] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 7 10 11 12 14 15)
[ 0.114025] SCSI subsystem initialized
[ 0.114161] libata version 3.00 loaded.
[ 0.114320] usbcore: registered new interface driver usbfs
[ 0.114350] usbcore: registered new interface driver hub
[ 0.114408] usbcore: registered new device driver usb
[ 0.114661] ACPI: WMI: Mapper loaded
[ 0.114665] PCI: Using ACPI for IRQ routing
[ 0.114895] Bluetooth: Core ver 2.15
[ 0.114995] NET: Registered protocol family 31
[ 0.114999] Bluetooth: HCI device and connection manager initialized
[ 0.115003] Bluetooth: HCI socket layer initialized
[ 0.115007] NetLabel: Initializing
[ 0.115009] NetLabel: domain hash size = 128
[ 0.115010] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.115031] NetLabel: unlabeled traffic allowed by default
[ 0.117596] pnp: PnP ACPI init
[ 0.117639] ACPI: bus type pnp registered
[ 0.123950] pnp: PnP ACPI: found 14 devices
[ 0.123956] ACPI: ACPI bus type pnp unregistered
[ 0.123963] PnPBIOS: Disabled by ACPI PNP
[ 0.124019] system 00:08: ioport range 0x290-0x297 has been reserved
[ 0.124029] system 00:09: ioport range 0x480-0x48f has been reserved
[ 0.124033] system 00:09: ioport range 0x4d0-0x4d1 has been reserved
[ 0.124036] system 00:09: ioport range 0x800-0x8df has been reserved
[ 0.124040] system 00:09: ioport range 0x8e0-0x8ff has been reserved
[ 0.124045] system 00:09: iomem range 0xffe80000-0xffefffff has been reserved
[ 0.124052] system 00:0a: ioport range 0x900-0x90f has been reserved
[ 0.124057] system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.124060] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
[ 0.124064] system 00:0a: iomem range 0xfff80000-0xffffffff has been reserved
[ 0.124073] system 00:0d: iomem range 0x0-0x9ffff could not be reserved
[ 0.124076] system 00:0d: iomem range 0xc0000-0xdffff could not be reserved
[ 0.124080] system 00:0d: iomem range 0xe0000-0xfffff could not be reserved
[ 0.124084] system 00:0d: iomem range 0x100000-0x2dfeffff could not be reserved
[ 0.158833] AppArmor: AppArmor Filesystem Enabled
[ 0.158868] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[ 0.158874] pci 0000:00:01.0: IO window: 0xd000-0xdfff
[ 0.158881] pci 0000:00:01.0: MEM window: 0xdfe00000-0xdfefffff
[ 0.158887] pci 0000:00:01.0: PREFETCH window: 0xcfd00000-0xdfcfffff
[ 0.158908] pci_bus 0000:00: resource 0 io: [0x00-0xffff]
[ 0.158912] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
[ 0.158915] pci_bus 0000:01: resource 0 io: [0xd000-0xdfff]
[ 0.158918] pci_bus 0000:01: resource 1 mem: [0xdfe00000-0xdfefffff]
[ 0.158921] pci_bus 0000:01: resource 2 pref mem [0xcfd00000-0xdfcfffff]
[ 0.158980] NET: Registered protocol family 2
[ 0.159117] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.159666] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.161114] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.161861] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.161871] TCP reno registered
[ 0.162096] NET: Registered protocol family 1
[ 0.162213] Trying to unpack rootfs image as initramfs...
[ 0.434693] Freeing initrd memory: 7470k freed
[ 0.446258] cpufreq-nforce2: No nForce2 chipset.
[ 0.446309] Scanning for low memory corruption every 60 seconds
[ 0.446475] audit: initializing netlink socket (disabled)
[ 0.446504] type=2000 audit(1260619120.444:1): initialized
[ 0.455672] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[ 0.457395] VFS: Disk quotas dquot_6.5.2
[ 0.457503] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.458328] fuse init (API version 7.12)
[ 0.458468] msgmni has been set to 1434
[ 0.458867] alg: No test for stdrng (krng)
[ 0.458897] io scheduler noop registered
[ 0.458901] io scheduler anticipatory registered
[ 0.458903] io scheduler deadline registered
[ 0.459005] io scheduler cfq registered (default)
[ 0.544051] pci 0000:01:00.0: Boot video device
[ 0.544209] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.544244] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.544427] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 0.544434] ACPI: Power Button [PWRF]
[ 0.544511] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[ 0.544515] ACPI: Power Button [PWRB]
[ 0.544756] ACPI: Invalid PBLK length [0]
[ 0.544916] processor LNXCPU:00: registered as cooling_device0
[ 0.548431] isapnp: Scanning for PnP cards...
[ 0.688045] Switched to high resolution mode on CPU 0
[ 0.902230] isapnp: No Plug & Play device found
[ 0.903785] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.903928] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.904088] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.904562] 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.904713] 00:0c: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[ 0.904823] alloc irq_desc for 19 on node -1
[ 0.904827] alloc kstat_irqs on node -1
[ 0.904839] serial 0000:00:08.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 0.904983] 0000:00:08.0: ttyS2 at I/O 0xe008 (irq = 19) is a 16450
[ 0.905063] 0000:00:08.0: ttyS3 at I/O 0xe010 (irq = 19) is a 8250
[ 0.905090] Couldn't register serial port 0000:00:08.0: -28
[ 0.906332] brd: module loaded
[ 0.906967] loop: module loaded
[ 0.907122] input: Macintosh mouse button emulation as /devices/virtual/input/input2
[ 0.907375] sata_sis 0000:00:05.0: version 1.0
[ 0.907407] alloc irq_desc for 17 on node -1
[ 0.907410] alloc kstat_irqs on node -1
[ 0.907421] sata_sis 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 0.907428] sata_sis 0000:00:05.0: Detected SiS 180/181/964 chipset in SATA mode
[ 0.907631] scsi0 : sata_sis
[ 0.907821] scsi1 : sata_sis
[ 0.908408] ata1: SATA max UDMA/133 cmd 0xeff0 ctl 0xefe4 bmdma 0xef90 irq 17
[ 0.908415] ata2: SATA max UDMA/133 cmd 0xefa8 ctl 0xefe0 bmdma 0xef98 irq 17
[ 0.908972] pata_sis 0000:00:02.5: version 0.5.2
[ 0.908997] alloc irq_desc for 16 on node -1
[ 0.909000] alloc kstat_irqs on node -1
[ 0.909011] pata_sis 0000:00:02.5: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.909309] scsi2 : pata_sis
[ 0.909458] scsi3 : pata_sis
[ 0.910402] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.910407] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.910900] Fixed MDIO Bus: probed
[ 0.910952] PPP generic driver version 2.4.2
[ 0.911140] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.911193] alloc irq_desc for 23 on node -1
[ 0.911197] alloc kstat_irqs on node -1
[ 0.911209] ehci_hcd 0000:00:03.3: PCI INT D -> GSI 23 (level, low) -> IRQ 23
[ 0.911238] ehci_hcd 0000:00:03.3: EHCI Host Controller
[ 0.911340] ehci_hcd 0000:00:03.3: new USB bus registered, assigned bus number 1
[ 0.911394] ehci_hcd 0000:00:03.3: cache line size of 128 is not supported
[ 0.911423] ehci_hcd 0000:00:03.3: irq 23, io mem 0xdfff7000
[ 0.920013] ehci_hcd 0000:00:03.3: USB 2.0 started, EHCI 1.00
[ 0.920179] usb usb1: configuration #1 chosen from 1 choice
[ 0.920232] hub 1-0:1.0: USB hub found
[ 0.920250] hub 1-0:1.0: 8 ports detected
[ 0.920361] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.920413] alloc irq_desc for 20 on node -1
[ 0.920417] alloc kstat_irqs on node -1
[ 0.920428] ohci_hcd 0000:00:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 0.920454] ohci_hcd 0000:00:03.0: OHCI Host Controller
[ 0.920546] ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2
[ 0.920588] ohci_hcd 0000:00:03.0: irq 20, io mem 0xdfff4000
[ 0.978128] usb usb2: configuration #1 chosen from 1 choice
[ 0.978184] hub 2-0:1.0: USB hub found
[ 0.978201] hub 2-0:1.0: 3 ports detected
[ 0.978292] alloc irq_desc for 21 on node -1
[ 0.978296] alloc kstat_irqs on node -1
[ 0.978305] ohci_hcd 0000:00:03.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[ 0.978328] ohci_hcd 0000:00:03.1: OHCI Host Controller
[ 0.978404] ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 3
[ 0.978442] ohci_hcd 0000:00:03.1: irq 21, io mem 0xdfff5000
[ 1.034113] usb usb3: configuration #1 chosen from 1 choice
[ 1.034158] hub 3-0:1.0: USB hub found
[ 1.034175] hub 3-0:1.0: 3 ports detected
[ 1.034261] alloc irq_desc for 22 on node -1
[ 1.034265] alloc kstat_irqs on node -1
[ 1.034275] ohci_hcd 0000:00:03.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 1.034299] ohci_hcd 0000:00:03.2: OHCI Host Controller
[ 1.034369] ohci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 4
[ 1.034407] ohci_hcd 0000:00:03.2: irq 22, io mem 0xdfff6000
[ 1.090128] usb usb4: configuration #1 chosen from 1 choice
[ 1.090175] hub 4-0:1.0: USB hub found
[ 1.090192] hub 4-0:1.0: 2 ports detected
[ 1.090284] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.090446] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[ 1.090450] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 1.090595] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.090939] ata3.00: ATAPI: LITE-ON DVDRW LH-18A1P, GL0F, max UDMA/66
[ 1.091222] mice: PS/2 mouse device common for all mice
[ 1.091361] rtc_cmos 00:02: RTC can wake from S4
[ 1.091428] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[ 1.091461] rtc0: alarms up to one month, 114 bytes nvram
[ 1.091641] device-mapper: uevent: version 1.0.3
[ 1.091849] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@...
[ 1.092034] device-mapper: multipath: version 1.1.0 loaded
[ 1.092040] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.092309] EISA: Probing bus 0 at eisa.0
[ 1.092348] EISA: Detected 0 cards.
[ 1.092459] cpuidle: using governor ladder
[ 1.092463] cpuidle: using governor menu
[ 1.093228] TCP cubic registered
[ 1.093408] NET: Registered protocol family 10
[ 1.094030] lo: Disabled Privacy Extensions
[ 1.094444] NET: Registered protocol family 17
[ 1.094517] Bluetooth: L2CAP ver 2.13
[ 1.094520] Bluetooth: L2CAP socket layer initialized
[ 1.094524] Bluetooth: SCO (Voice Link) ver 0.6
[ 1.094525] Bluetooth: SCO socket layer initialized
[ 1.094604] Bluetooth: RFCOMM TTY layer initialized
[ 1.094608] Bluetooth: RFCOMM socket layer initialized
[ 1.094611] Bluetooth: RFCOMM ver 1.11
[ 1.094674] Using IPI No-Shortcut mode
[ 1.094812] PM: Resume from disk failed.
[ 1.094835] registered taskstats version 1
[ 1.094956] Magic number: 5:546:984
[ 1.095059] rtc_cmos 00:02: setting system clock to 2009-12-12 11:58:41 UTC (1260619121)
[ 1.095064] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.095067] EDD information not available.
[ 1.109925] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 1.120403] ata3.00: configured for UDMA/66
[ 1.228064] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.236375] ata1.00: ATA-6: ST380011AS, 3.00, max UDMA/133
[ 1.236379] ata1.00: 156301488 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 1.252383] ata1.00: configured for UDMA/133
[ 1.252593] scsi 0:0:0:0: Direct-Access ATA ST380011AS 3.00 PQ: 0 ANSI: 5
[ 1.252825] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.252928] sd 0:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB)
[ 1.253012] sd 0:0:0:0: [sda] Write Protect is off
[ 1.253017] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.253058] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.253297] sda: sda1 sda2 sda3 sda4
[ 1.282796] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.480012] usb 2-1: new low speed USB device using ohci_hcd and address 2
[ 1.582857] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.583993] scsi 2:0:0:0: CD-ROM LITE-ON DVDRW LH-18A1P GL0F PQ: 0 ANSI: 5
[ 1.589251] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[ 1.589258] Uniform CD-ROM driver Revision: 3.20
[ 1.589436] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 1.589533] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 1.693161] usb 2-1: configuration #1 chosen from 1 choice
[ 1.744125] Freeing unused kernel memory: 540k freed
[ 1.744948] Write protecting the kernel text: 4568k
[ 1.744982] Write protecting the kernel read-only data: 1836k
[ 2.010711] Linux agpgart interface v0.103
[ 2.014353] agpgart-sis 0000:00:00.0: SiS chipset [1039/0661]
[ 2.021678] Floppy drive(s): fd0 is 1.44M
[ 2.040270] FDC 0 is a post-1991 82077
[ 2.084400] agpgart-sis 0000:00:00.0: AGP aperture is 64M @ 0xe0000000
[ 2.084583] <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 2.084630] 8139cp 0000:00:0b.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
[ 2.093681] 8139too Fast Ethernet driver 0.9.28
[ 2.093769] 8139too 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 2.094962] eth0: RealTek RTL8139 at 0xee00, 00:17:31:15:fd:e9, IRQ 19
[ 2.213259] usbcore: registered new interface driver hiddev
[ 2.237356] input: Logitech Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:03.0/usb2/2-1/2-1:1.0/input/input4
[ 2.237491] generic-usb 0003:046D:C018.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech Logitech USB Optical Mouse] on usb-0000:00:03.0-1/input0
[ 2.237526] usbcore: registered new interface driver usbhid
[ 2.237531] usbhid: v2.6:USB HID core driver
[ 3.701246] PM: Starting manual resume from disk
[ 3.701255] PM: Resume from partition 8:3
[ 3.701257] PM: Checking hibernation image.
[ 3.701517] PM: Resume from disk failed.
[ 3.729378] EXT4-fs (sda2): barriers enabled
[ 3.738146] kjournald2 starting: pid 329, dev sda2:8, commit interval 5 seconds
[ 3.738182] EXT4-fs (sda2): delayed allocation enabled
[ 3.738188] EXT4-fs: file extents enabled
[ 3.739379] EXT4-fs: mballoc enabled
[ 3.739411] EXT4-fs (sda2): mounted filesystem with ordered data mode
[ 4.387647] type=1505 audit(1260619124.788:2): operation="profile_load" pid=352 name=/usr/share/gdm/guest-session/Xsession
[ 4.399095] type=1505 audit(1260619124.800:3): operation="profile_load" pid=353 name=/sbin/dhclient3
[ 4.399891] type=1505 audit(1260619124.800:4): operation="profile_load" pid=353 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 4.400357] type=1505 audit(1260619124.804:5): operation="profile_load" pid=353 name=/usr/lib/connman/scripts/dhclient-script
[ 4.429292] type=1505 audit(1260619124.832:6): operation="profile_load" pid=354 name=/usr/bin/evince
[ 4.442017] type=1505 audit(1260619124.844:7): operation="profile_load" pid=354 name=/usr/bin/evince-previewer
[ 4.449741] type=1505 audit(1260619124.852:8): operation="profile_load" pid=354 name=/usr/bin/evince-thumbnailer
[ 4.468741] type=1505 audit(1260619124.872:9): operation="profile_load" pid=356 name=/usr/lib/cups/backend/cups-pdf
[ 4.469703] type=1505 audit(1260619124.872:10): operation="profile_load" pid=356 name=/usr/sbin/cupsd
[ 5.776535] Adding 1542232k swap on /dev/sda3. Priority:-1 extents:1 across:1542232k
[ 5.977038] udev: starting version 147
[ 6.043304] EXT4-fs (sda2): internal journal on sda2:8
[ 6.766369] lp: driver loaded but no devices found
[ 7.202603] parport_pc 00:07: reported by Plug and Play ACPI
[ 7.202721] parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
[ 7.287332] lp0: using parport0 (interrupt-driven).
[ 7.376452] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 7.379192] ppdev: user-space parallel port driver
[ 7.426666] Linux video capture interface: v2.00
[ 7.678085] EXT4-fs (sda4): barriers enabled
[ 7.694431] kjournald2 starting: pid 577, dev sda4:8, commit interval 5 seconds
[ 7.694748] EXT4-fs (sda4): internal journal on sda4:8
[ 7.694753] EXT4-fs (sda4): delayed allocation enabled
[ 7.694757] EXT4-fs: file extents enabled
[ 7.695036] EXT4-fs: mballoc enabled
[ 7.695070] EXT4-fs (sda4): mounted filesystem with ordered data mode
[ 8.108303] saa7130/34: v4l2 driver version 0.2.15 loaded
[ 8.108396] alloc irq_desc for 18 on node -1
[ 8.108401] alloc kstat_irqs on node -1
[ 8.108412] saa7134 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 8.108421] saa7130[0]: found at 0000:00:0a.0, rev: 1, irq: 18, latency: 64, mmio: 0xdfff2c00
[ 8.108430] saa7130[0]: subsystem: 1131:2341, board: Encore ENLTV [card=106,autodetected]
[ 8.108461] saa7130[0]: board init: gpio is 5d31ff
[ 8.108578] input: saa7134 IR (Encore ENLTV) as /devices/pci0000:00/0000:00:0a.0/input/input5
[ 8.108656] IRQ 18/saa7130[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[ 8.260043] saa7130[0]: i2c eeprom 00: 31 11 41 23 08 20 1c 55 43 43 a9 1c 55 43 43 a9
[ 8.260058] saa7130[0]: i2c eeprom 10: ff ff 00 00 31 30 4d 4f 4f 4e 53 37 31 33 30 20
[ 8.260070] saa7130[0]: i2c eeprom 20: 41 41 48 53 ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260081] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260092] saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260102] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260113] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260124] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260135] saa7130[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260146] saa7130[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260156] saa7130[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260167] saa7130[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260178] saa7130[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260189] saa7130[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260200] saa7130[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260210] saa7130[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 8.260227] i2c-adapter i2c-0: Invalid 7-bit address 0x7a
[ 8.803768] All bytes are equal. It is not a TEA5767
[ 8.803916] tuner 0-0060: chip found @ 0xc0 (saa7130[0])
[ 8.959124] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 8.976170] tuner-simple 0-0060: creating new instance
[ 8.976178] tuner-simple 0-0060: type set to 69 (Tena TNF 5335 and similar models)
[ 9.006291] saa7130[0]: registered device video0 [v4l2]
[ 9.006338] saa7130[0]: registered device vbi0
[ 9.006376] saa7130[0]: registered device radio0
[ 9.045893] saa7134 ALSA driver for DMA sound loaded
[ 9.045902] saa7130[0]/alsa: Encore ENLTV doesn't support digital audio
[ 9.158300] Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 9.492086] intel8x0_measure_ac97_clock: measured 54041 usecs (2599 samples)
[ 9.492093] intel8x0: clocking to 48000
[ 10.224329] __ratelimit: 3 callbacks suppressed
[ 10.224335] type=1505 audit(1260637130.628:12): operation="profile_replace" pid=744 name=/usr/share/gdm/guest-session/Xsession
[ 10.227712] type=1505 audit(1260637130.628:13): operation="profile_replace" pid=745 name=/sbin/dhclient3
[ 10.228650] type=1505 audit(1260637130.632:14): operation="profile_replace" pid=745 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 10.229078] type=1505 audit(1260637130.632:15): operation="profile_replace" pid=745 name=/usr/lib/connman/scripts/dhclient-script
[ 10.239276] type=1505 audit(1260637130.640:16): operation="profile_replace" pid=746 name=/usr/bin/evince
[ 10.265696] type=1505 audit(1260637130.668:17): operation="profile_replace" pid=746 name=/usr/bin/evince-previewer
[ 10.273810] type=1505 audit(1260637130.676:18): operation="profile_replace" pid=746 name=/usr/bin/evince-thumbnailer
[ 10.288274] type=1505 audit(1260637130.692:19): operation="profile_replace" pid=754 name=/usr/lib/cups/backend/cups-pdf
[ 10.289245] type=1505 audit(1260637130.692:20): operation="profile_replace" pid=754 name=/usr/sbin/cupsd
[ 10.293706] type=1505 audit(1260637130.696:21): operation="profile_replace" pid=755 name=/usr/sbin/tcpdump
[ 13.679934] eth0: link down
[ 13.680191] ADDRCONF(NETDEV_UP): eth0: link is not ready

Module Size Used by
binfmt_misc 8356 1
iptable_filter 3100 0
snd_intel8x0 30168 2
snd_ac97_codec 101216 1 snd_intel8x0
ac97_bus 1532 1 snd_ac97_codec
snd_pcm_oss 37920 0
snd_mixer_oss 16028 1 snd_pcm_oss
saa7134_alsa 12128 0
snd_pcm 75296 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,saa7134_alsa
tuner_simple 14832 1
tuner_types 14396 1 tuner_simple
ip_tables 11692 1 iptable_filter
snd_seq_dummy 2656 0
x_tables 16544 1 ip_tables
snd_seq_oss 28576 0
snd_seq_midi 6432 0
snd_rawmidi 22208 1 snd_seq_midi
snd_seq_midi_event 6940 2 snd_seq_oss,snd_seq_midi
tea5767 6720 0
snd_seq 50224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 22276 2 snd_pcm,snd_seq
tuner 21540 1
snd_seq_device 6920 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 59204 15 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,saa7134_alsa,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 7264 1 snd
saa7134 152616 1 saa7134_alsa
snd_page_alloc 9156 2 snd_intel8x0,snd_pcm
ir_common 48512 1 saa7134
v4l2_common 17500 2 tuner,saa7134
videodev 36736 3 tuner,saa7134,v4l2_common
v4l1_compat 14496 1 videodev
videobuf_dma_sg 12544 2 saa7134_alsa,saa7134
videobuf_core 17952 2 saa7134,videobuf_dma_sg
tveeprom 11872 1 saa7134
ppdev 6688 0
shpchp 32272 0
parport_pc 31940 1
lp 8964 0
parport 35340 3 ppdev,parport_pc,lp
usbhid 38208 0
8139too 22620 0
8139cp 19260 0
mii 5212 2 8139too,8139cp
floppy 54916 0
sis_agp 6972 1
agpgart 34988 1 sis_agp

KERNEL 2.6.29 and Agere Systems Soft Modem (chipset 11c1:0620)

2009-12-12T09:19:01Z

KERNEL 2.6.29 and Agere Systems Soft Modem (chipset 11c1:0620)
==============================================================

The following is using Fedora Core11.

Using agrsm06pci-2.1.80~20090825.tar.gz as the source for
the modules to work with this modem:

Attempting to compile the modules for kernel 2.6.29 (Fedora Core 11 with its
PAE configuration) led to
agrsm06pci-2.1.80~20090825/agrsoftmodem.c:263: error: too few arguments to function `__request_region'

Examining
/usr/src/linux/include/linux/ioport.h

I see
#define request_region(start,n,name) __request_region(&ioport_resource, (start), (n), (name), 0)

#define __request_mem_region(start,n,name, excl) __request_region(&iomem_resource, (start), (n), (name), excl)

extern struct resource * __request_region(struct resource *,
resource_size_t start,
resource_size_t n,
const char *name, int flags);

#define request_mem_region_exclusive(start,n,name) \
__request_region(&iomem_resource, (start), (n), (name), IORESOURCE_EXCLUSIVE)

and it appears that __request_region has gained another argument, a flag
which may specify exclusivity along with request_region(start,n,name)
which uses a value of zero for that argument.

I changed the code

// return(request_region(start, n, name));
return(__request_region(&ioport_resource, (start), (n), (name)));

in agrsoftmodem.c to

// return(request_region(start, n, name));
// return(__request_region(&ioport_resource, (start), (n), (name)));
return(__request_region(&ioport_resource, (start), (n), (name), 0));

It seems that request_region was originally used,
then changed to use the more kernel-specific __request_region and
while request_region did not change, __request_region did.

I am no C-programmer but I *seem* to have gotten it to work.

MODPROBE:
=========
After installing I find that modprobe will not find it.
Howver,
insmod -f [filename]
is used in
/etc/init.d/agr_softmodem

/sbin/insmod -f /lib/modules`uname -r`/kernel/drivers/char/agrmodem.ko; \
/sbin/insmod -f /lib/modules/`uname -r`/kernel/drivers/char/agrserial.ko; \
/usr/lib/AgereSoftModem/AgereMdmDaemon

so one may want to edit the material on using modprobe (which cannot
find the module while insmod can specify the module by path/filename
and so the attempt to load the modules in agrsm-test.txt from
agrsm-tools-0.0.1-2.noarch.rpm using modprobe fails).

service agr_softmodem (start|stop)

can be used to start/stop it (inserting/removing the modules and so
creating/removing /dev/ttyAGS3) in Fedora Core11.

Re: Aleck, Kazakhstan kernel 2.6.24-19-generic

2009-12-11T17:49:02Z

В сообщении от 11 декабря 2009 01:52 вы написали:
> You may carefully read the following pages:

Antonio,

Thank you very much for your links.
They have helped me to find the decision without kernel update.
--
Best regards,
Aleck

Re: ALi 5451, problems only with recent ALSA driver

2009-12-11T08:42:09Z

ali5451 modem, further test results

In pcm_lib.c, in Alsa-driver 1.0.16, at line 1824, there is a test for (!avail).
It's at line 2003 in 1.0.21, to take the current version.

If I replace this condition with one taken from 1.0.15, line 1936,

(avail < runtime->control->avail_min)

the modem can successfully connect, though at a very low speed, about
one tenth of its regular speed, and only in about one in every three
attempts.

Obviously, the conditions tested are not the same.

In 1.0.16 a lot of code was removed involving xfer_align.
A test with 1.0.15 shows this code was regularly executed. Removing it
from 1.0.15 in small steps leads to connection speed decreasing more
and more.

Obviously, the xfer_align code plays an important role in making the
ali5451 work.

I do not think this issue could be addressed with a patch for the Alsa
project, because xfer_align was intentionally removed from it.
Inserting all this code again would come close to turning the clock
back to Alsa 1.0.15. I've added some quotations below about the
removal.

- Pink
------------------------------------------------------------

Some quotations about xfer_align:

Jaroslav Kysela
(http://www.mail-archive.com/alsa-devel@.../msg04238.html)

It's software only limit for read/write transfers. The direct transfers
(mmap) don't take care about this limit. The idea is to avoid using very
small transfer chunks which are inefficient. Application might change
this value from 1 (no control) to buffer_size (in samples), but values
bigger than period_size hasn't any sense anyway.

The default value for xfer_align is period_size.

Jaroslav Kysela (http://osdir.com/ml/alsa.devel/2002-09/msg00110.html)

The physical size of xfer_align * frame_size_in_bits must be multiple by 8,
of course. Adding bit copying in the kernel or library will cause a lot of
overhead.

I've added this function to library:

snd_pcm_sframes_t snd_pcm_hw_params_get_min_align(const snd_pcm_hw_params_t
*params)

Takashi Iwai (http://www.opensubscriber.com/message/linux-kernel@.../8513951.html)

The xfer_align sw_params parameter has never been used in a sane
manner, and no one understands what this does exactly. The current
implementation looks also buggy because it allows write of shorter
size than xfer_align. So, if you do partial writes, the write isn't
actually aligned at all.
Removing this parameter will make some pcm_lib_* code more readable
(and less buggy).

On 12/7/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:

> RE: the version of Alsa-driver does not affect the result of the
> slmodemd compilation, or does it?
> the slmodemd compilation can be done within the slmodem-version/modem/
> folder with command:
> make SUPPORT_ALSA=1
> wherein the SUPPORT_ALSA=1 specifies to use libalsa code from the base
> libasound library (typically installed by dedault) and additionally
> the libasound2-dev needed for ALSA competent slmodemd compilation.
>
> Packages like SLMODEMD_gcc4.4_alsa1.0.21.tar.gz are assembled by
> me/Anotnio, so a new User doesn't have to do extensive downloads
> before being able to use the modem.
>
> Usage seems to be relatively insenstive to the gcc version, but
> matching does no harm
>
> MarvS
>
> On Mon, Dec 7, 2009 at 10:02 AM, Pink SoftBunny
> <pinksoftbunny@...> wrote:
>> MarvS,
>>
>> I have written to Marino.Persico@... in Italian. While
>> waiting for an answer, looking at the ModemData.txt he had posted, I
>> think he and I are using the same hardware. As far as Puppy Linux is
>> concerned, there are many variants ("Puplets") of this system. The one
>> I downloaded, NOP, has a slmodemd without Alsa support, so I think
>> installing an Alsa-enabled slmodemd is an absolute minimum
>> prerequisite before even attempting dialling out.
>>
>> I'm still not sure whether there are any successful cases of
>> connecting with ali5451 using Alsa-driver newer than 1.0.15.
>>
>> Another question: I have seen there are compiled packages like
>> SLMODEMD_gcc4.4_alsa1.0.21.tar.gz. I imagine, but please correct me if
>> I'm wrong, that this means, compiled with gcc 4.4 after Alsa-lib
>> 1.0.21 has been compiled and installed.
>> In other words, the version of Alsa-driver does not affect the result
>> of the slmodemd compilation, or does it?
>>
>> In my tests with various kernels, I used to install Alsa-lib with the
>> same version of Alsa-driver before compiling slmodemd. However, I
>> never successfully connected unless I used the old Alsa-driver and
>> Alsa-lib 1.0.15.
>>
>> - Pink
>>
>> On 12/7/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:
>>> Pink,
>>>
>>> Thanks greatly for testing all the kernels.
>>> It you haven'r provided this information to the ALSA team, please do do.
>>> Within scanModem, I will set a URL to your email in the Archives, to
>>> be displayed when an ALI5451 card is detected.
>>>
>>> MarvS
>>>
>>> On Sun, Dec 6, 2009 at 2:06 PM, Pink SoftBunny
>>> <pinksoftbunny@...> wrote:
>>>> MarvS,
>>>>
>>>> thank you very much for writing - sorry for not replying earlier.
>>>>
>>>> I'd be happy to help with Italian transalations, when needed.
>>>>
>>>> As far as I could see, both compiled and packaged versions of slmodemd
>>>> 2.9.11 work, provided Alsa-driver and Alsa-lib are right.
>>>> Here are my experiences with some distributions:
>>>>
>>>> Knoppix 5.1.1. (2007). My first success with slmodemd. Kernel
>>>> 2.6.19.1, Alsa-driver and Alsa-lib both version 1.0.13, gcc 4.1.2.
>>>> slmodemd was not included in the distribution, but both packaged and
>>>> compiled 2.9.11 work.
>>>>
>>>> Essentially the same results with the following distributions:
>>>>
>>>> Sidux 2007: Kernel 2.6.21.3, Alsa-driver 1.0.14rc3, Alsa-lib 1.0.13, gcc
>>>> 4.1.3.
>>>>
>>>> DreamLinux 3.2, Kernel 2.6.23, Alsa-driver 1.0.14, Alsa-lib 1.0.15
>>>>
>>>> Puppy NOP 4.0, Kernel 2.6.21.3, Alsa-driver 1.0.15rc2, Alsa-lib 1.0.14
>>>>
>>>> In 2008, first problems noticed:
>>>>
>>>> Knoppix 5.3.1., Kernel 2.6.24.4, Alsa-driver 1.0.15, Alsa-lib 1.0.16,
>>>> gcc
>>>> 4.2.3.
>>>> The modem connects, but at a slow speed and disconnects again after a
>>>> short while.
>>>> Solution: used libasound.so.2.0.0 version 1.0.15, and the modem works
>>>> perfectly.
>>>>
>>>> Sidux 2008-01: closely resembles Knoppix 5.3.1, with same Kernel,
>>>> Alsa-driver, Alsa-lib and gcc versions. Same problem and same
>>>> solution.
>>>>
>>>> Then, the problems become even worse:
>>>>
>>>> Puppy NOP 4.1.2. and 4.1.3.: Kernel 2.6.25.16, Alsa-driver and
>>>> Alsa-lib 1.0.16rc2.
>>>> With this one, the only way to connect consisted in recompiling the
>>>> sound modules, using files taken from Alsa-driver 1.0.15 (control.c,
>>>> pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h), with minimal
>>>> modifications to ensure compilation. Alsa-lib 1.0.15 needed for
>>>> successful connect.
>>>>
>>>> Essentially, same experience with the following distributions:
>>>>
>>>> Puppy NOP 4.3.1, Kernel 2.6.30.5, Alsa-driver and Alsa-lib 1.0.20
>>>>
>>>> TinyCore, Kernel 2.6.29.1; tried this one also with self-compiled
>>>> Vanilla kernels 2.6.26,
>>>> 2.6.27.1, 2.6.28, 2.6.29, 2.6.30 and 2.6.31.
>>>>
>>>> Pink
>>>>
>>>> On 11/17/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:
>>>>> Pink,
>>>>>
>>>>> Your information on:
>>>>>> I only need to keep the following source files from ALSA 1.0.15:
>>>>>> control.c, pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h.
>>>>> is very useful as it may be applicable to drivers other than the
>>>>> ali5451
>>>>>
>>>>> What is your Linux distro?
>>>>> Which slmodemd are using? While the Smartlink release 2.9.11 is
>>>>> certainly appropriate,
>>>>> If might help to compile slmodemd on your own system, to get the
>>>>> optimal match of alsa resources and gcc compiler.
>>>>>
>>>>> Within the folder slmodem-2.9.11-20090222/modem/ folder, the compile
>>>>> can be done as below,
>>>>> though I suspect you have compiled your own.
>>>>>
>>>>> Would you please gzip your slmodemd and send it to "Antonio Olivares"
>>>>> <olivares14031@...>
>>>>> He has success with a slmodemd+slamr driver under 2.6.30, but not
>>>>> 2.6.31
>>>>>
>>>>> MarvS
>>>>> -------------
>>>>> slmodem-2.9.11-20090222/modem$ make SUPPORT_ALSA=1
>>>>> rebuild profile...
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_main.o -c modem_main.c
>>>>> modem_main.c: In function ‘setup_stream’:
>>>>> modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is
>>>>> deprecated (declared at /usr/include/alsa/pcm.h:1114)
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_cmdline.o -c modem_cmdline.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o
>>>>> -c modem.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_datafile.o -c modem_datafile.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_at.o -c modem_at.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_timer.o -c modem_timer.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_pack.o -c modem_pack.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_ec.o -c modem_ec.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_comp.o -c modem_comp.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_param.o -c modem_param.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_debug.o -c modem_debug.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> homolog_data.o -c homolog_data.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> dp_sinus.o -c dp_sinus.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> dp_dummy.o -c dp_dummy.c
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> sysdep_common.o -c sysdep_common.c
>>>>> gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o
>>>>> modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o
>>>>> modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o
>>>>> dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>> modem_test.o -c modem_test.c
>>>>> modem_test.c: In function ‘modem_test_start’:
>>>>> modem_test.c:110: warning: ignoring return value of ‘write’, declared
>>>>> with attribute warn_unused_result
>>>>> gcc -o modem_test modem_test.o modem_cmdline.o modem.o
>>>>> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
>>>>> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
>>>>> dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>>
>>>>> slmodem-2.9.11-20090222/modem$ ls -lh slmodemd
>>>>> -rwxr-xr-x 1 marv marv 1.3M 2009-11-17 17:51 slmodemd
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 17, 2009 at 11:39 AM, Pink SoftBunny
>>>>> <pinksoftbunny@...> wrote:
>>>>>> Dear Readers,
>>>>>>
>>>>>> my ALi 5451 modem used to work perfectly with ALSA driver version
>>>>>> 1.0.15, ALSA library 1.0.15 and slmodemd 2.9.11.
>>>>>>
>>>>>> Since newer Linux Kernels also brought newer ALSA drivers with them, I
>>>>>> have not been able to get a "CONNECT" with this modem.
>>>>>> I did a number of tests with different distributions and dialling
>>>>>> software.
>>>>>>
>>>>>> As a workaround, I compiled ALSA driver 1.0.15 for the more recent
>>>>>> Linux kernels, up to 2.6.31, the current release at the time of this
>>>>>> writing. The modem works perfectly with this workaround.
>>>>>> I only need to keep the following source files from ALSA 1.0.15:
>>>>>> control.c, pcm.c, pcm_lib.c, pcm_native.c, asound.h and pcm.h.
>>>>>>
>>>>>> However, I lack the necessary insight to determine whether the
>>>>>> problem is due to the ALSA driver, the ALSA library, slmodemd or other
>>>>>> components.
>>>>>> This problem has been submitted to ALSA as issue #0004601.
>>>>>>
>>>>>> Thank you for your assistance!
>>>>>>
>>>>>
>>>>
>>>
>>
>

RE: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic

2009-12-10T23:44:58Z

It doesn't run!

==========
mantegazza@mantegazza-laptop:~$ cd /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd -c ITALY modem:1
[sudo] password for mantegazza:
error: mdm setup: cannot stat `modem:1': No such file or directory
error: cannot setup device `modem:1'
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
===========

Claudio.

----------------------------------------

> Date: Thu, 10 Dec 2009 14:14:00 -0500
> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
> From: marvin.stodolsky@...
> To: ermante@...
> CC: jacques.goldberg@...; discuss@...; olivares14031@...
>
> Claudio,
>
> Slamr is not the preferred driver for your
>>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>>> Primary device ID: 8086:24c6
>>>>> Subsystem PCI_id 1631:d005
>>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink type
>>>>> from Archives:
> rather it is the snd-intel8x0m driver. With slmodemd already
> written to /usr/sbin/slmodemd,
> it suffices to activate it with:
> $ sudo slmodemd -c ITALY modem:1
>
> Then open a 2nd console and the modem should be found by:
> $ sudo wvdialconf
>
> MarvS
>
> On Thu, Dec 10, 2009 at 2:58 AM, Claudio Mantegazza wrote:
>>
>> I did it but i stopped in your point 12).
>> Look at what i received...
>>
>> ==============
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./setup
>>
>> Installing slmodemd helper to /usr/sbin/slmodemd
>>
>> Writing log to slmodemd_Inst.txt
>> ./setup: 14: slmodemd: not found
>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>> Version verified: 2.9.11
>> Read the slmodemd_Inst.txt
>>
>> There is already installed a slmodemd of version: 2.9.11
>> There is a file /usr/sbin/slmodemd
>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>> Version verified: 2.9.11
>> Read the slmodemd_Inst.txt
>>
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
>> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
>> error: cannot setup device `/dev/slamr0'
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe snd-intel8x0m
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
>> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
>> error: cannot setup device `/dev/slamr0'
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
>> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
>> error: cannot setup device `/dev/slamr0'
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe slamr
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
>> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
>> error: cannot setup device `/dev/slamr0'
>>
>> ==============
>> And in an other window.....
>> ==============
>>
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ wvdialconf /etc/wvdial.conf
>> Editing `/etc/wvdial.conf'.
>>
>> Scanning your serial ports for a modem.
>>
>> Modem Port Scan<*1>: S0 S1 S2 S3
>>
>>
>> Sorry, no modem was detected! Is it in use by another program?
>> Did you configure it properly with setserial?
>>
>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>>
>> If you still have problems, send mail to .
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>> ===============
>>
>> Why it doesn't detect my modem?
>> Claudio.
>>
>>
>>
>> ----------------------------------------
>>> Date: Wed, 9 Dec 2009 12:51:33 -0500
>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>>> From: marvin.stodolsky@...
>>> To: ermante@...
>>> CC: discuss@...
>>>
>>> Don't run "make", as the compile has already been done. Just do:
>>> $ sudo ./setup
>>>
>>> MarvS
>>>
>>> On Wed, Dec 9, 2009 at 5:33 AM, Claudio Mantegazza wrote:
>>>>
>>>> Marvin,Jacques, wait a minute....
>>>>
>>>> I did only a part which jacques told me...
>>>> i arrived to do all until jacques told me to continue to do what wrote in the README file at the installation but when i write the command in it i receice an error... Look at...
>>>>
>>>> =================
>>>> root@mantegazza-laptop:~# find / -iname SLMODEMD*
>>>> root@mantegazza-laptop:~# cd /home/mantegazza/Scaricati
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati# tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati# cd SLMODEMD_gcc4.4_alsa1.0.21
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# exit
>>>> exit
>>>> mantegazza@mantegazza-laptop:~$ cd /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ make
>>>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo su
>>>> [sudo] password for mantegazza:
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make
>>>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make install
>>>> make: *** Nessuna regola per creare l'obiettivo «install». Arresto.
>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21#
>>>> ===================
>>>>
>>>> So what i have to do before continue?
>>>>
>>>> Claudio.
>>>>
>>>>
>>>>
>>>> ----------------------------------------
>>>>> Date: Sat, 5 Dec 2009 16:37:08 -0500
>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>> From: marvin.stodolsky@...
>>>>> To: discuss@...
>>>>> CC: ermante@...
>>>>>
>>>>> Claudio
>>>>>
>>>>> You are missing a file with the contents below.
>>>>> Make a file with these contents, but replacing:
>>>>> DialUpNumber
>>>>> YourLoginName
>>>>> YourPassword
>>>>> This file should be named wvdial.conf, and can initially be in your home folder.
>>>>> Then after the
>>>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>>>> open a 2nd console and do:
>>>>> $ sudo wvdial -config=wvdial.conf
>>>>>
>>>>> MarvS
>>>>>
>>>>> [Dialer Defaults]
>>>>> Phone = DialUpNumber
>>>>> Username = YourLoginName
>>>>> Password = YourPassword
>>>>> Init1 = ATZ
>>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
>>>>> Modem Type = Analog Modem
>>>>> ISDN = 0
>>>>> New PPPD = yes
>>>>> Modem = /dev/ttySL0
>>>>> Carrier Check = no
>>>>> Baud = 460800
>>>>>
>>>>> On Fri, Dec 4, 2009 at 9:40 PM, Marvin Stodolsky
>>>>> wrote:
>>>>>> The modem activation command should be:
>>>>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>>>>> there should be reported creation of a port:
>>>>>> /dev/ttySL0 --> /dev/pts/N , N some number
>>>>>>
>>>>>> Only after such a success should one try;
>>>>>> $ sudo wvdial
>>>>>>
>>>>>> MarvS
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 4, 2009 at 8:06 AM, Jacques Goldberg
>>>>>> wrote:
>>>>>>> Claudio,
>>>>>>>
>>>>>>>
>>>>>>> I believe that you have reached such a mess level that it has become
>>>>>>> impossible to know which is what.
>>>>>>>
>>>>>>> Here is what I would do in your place:
>>>>>>>
>>>>>>> Because you used two versions of file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz ,
>>>>>>>
>>>>>>> 1-be root or sudo before any command
>>>>>>>
>>>>>>> 2-go into directory /usr/sbin
>>>>>>> 3-in that directory give command rm slmodemd*
>>>>>>>
>>>>>>> Make ABSOLUTELY SURE that you write slmodemd* so that there is NOTHING, NO
>>>>>>> SPACE, NOTHING ELSE, between slmodemd and the * . ABSOLUTELY SURE.
>>>>>>>
>>>>>>> Answer yes everytime you are prompted to erase a file with name starting
>>>>>>> with slmodemd and NO in any other case.
>>>>>>>
>>>>>>> 4-go into directory named SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>>
>>>>>>> 5-in that directory give command make uninstall
>>>>>>>
>>>>>>> 6-give the command cd
>>>>>>>
>>>>>>> 7-give the command find / -iname SLMODEMD* .Attention
>>>>>>> SLMODEMD in capital case.
>>>>>>>
>>>>>>> This will give a list of all the files in your computer with a name
>>>>>>> starting with SLMODEMD
>>>>>>>
>>>>>>> Erase all these files one at a time. To erase a file the command is rm ;
>>>>>>> to erase an empty directory the command is rmdir; to erase a directory which
>>>>>>> is not empty the command is rm -rf
>>>>>>> Always start with rm and then try rmdir and then rm -rf if the
>>>>>>> preceeding one is not accepted.
>>>>>>>
>>>>>>> 8-Now, in your usual directory, the one where you usually login, download
>>>>>>> the file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>
>>>>>>> Do not try to use one which has been downloaded before unless you are
>>>>>>> ABSOLUTELY sure that this is the one which I
>>>>>>>
>>>>>>> placed this morning.
>>>>>>>
>>>>>>> 9-Give the command tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>
>>>>>>> 10-Change directory with command cd SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>>
>>>>>>> 11-Do exactly, one time and one time only, what Marv has written to you to
>>>>>>> do or what is written in file README in the directory where you are starting
>>>>>>> from point 4 in INSTALLATION
>>>>>>>
>>>>>>> 12-After you have given the command slmodemd and it has succeeded, in
>>>>>>> an other window give the command
>>>>>>>
>>>>>>> wvdialconf /etc/wvdial.conf (no . in wvdialconf and a , in
>>>>>>> /etc/wvdial.conf
>>>>>>>
>>>>>>> wvdialconf will find your modem
>>>>>>>
>>>>>>> Edit /etc/wvdial.conf as explained in
>>>>>>> http://linmodems.technion.ac.il/wvdial.html . Remember that you need
>>>>>>>
>>>>>>> Carrier Check = no
>>>>>>>
>>>>>>> 13- When the file /etc/wvdial.conf has been edited and saved, in that window
>>>>>>> or any window except the one used for slmodemd, the command wvdial
>>>>>>> should start your modem.
>>>>>>>
>>>>>>> when everything works well wvdial does NOT exit but stays doing nothing.
>>>>>>>
>>>>>>> Use your browser (like Firefox) and try to surf.
>>>>>>>
>>>>>>>
>>>>>>> Please remember: every time you do something else than what we tell you to
>>>>>>> do, like installing several slmodemd , you take the risk to create the
>>>>>>> conditions for failure.
>>>>>>>
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Claudio Mantegazza wrote:
>>>>>>>
>>>>>>>> I downloaded again the new file.
>>>>>>>> i saw that there was updated 1 hour ago...
>>>>>>>> and in a new window (not the same about the
>>>>>>>> =======================
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ wvdial
>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ cd
>>>>>>>> /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ ls
>>>>>>>> 1st_Read.txt COPYING Files.txt setup slmodemd
>>>>>>>> slmodemd.txt Testing.txt wvdial.conf
>>>>>>>> Changes CountryList.txt README Slmodem-ALSA.txt
>>>>>>>> slmodemd_Inst.txt slmodem.txt Unload.txt
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo
>>>>>>>> ./setup
>>>>>>>> [sudo] password for mantegazza:
>>>>>>>> Installing slmodemd helper to /usr/sbin/slmodemd
>>>>>>>>
>>>>>>>> Writing log to slmodemd_Inst.txt
>>>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>>>> There is a file /usr/sbin/slmodemd
>>>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>>>> for version 2.9.11
>>>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>>>> Version verified: 2.9.11
>>>>>>>> Read the slmodemd_Inst.txt
>>>>>>>>
>>>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>>>> There is a file /usr/sbin/slmodemd
>>>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>>>> for version 2.9.11
>>>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>>>> Version verified: 2.9.11
>>>>>>>> Read the slmodemd_Inst.txt
>>>>>>>>
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>>> wvdial
>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>>> =======================
>>>>>>>>
>>>>>>>> but if in this windows i write the slmodem command:
>>>>>>>>
>>>>>>>> ======================
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>>> slmodemd --alsa -c YOUR_COUNTRY modem:1 error: mixer setup: attach hw:1
>>>>>>>> error: No such file or directory
>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid argument
>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>>> ======================
>>>>>>>>
>>>>>>>> I receive this error....
>>>>>>>>
>>>>>>>> and if i return in the other folder and i write...
>>>>>>>>
>>>>>>>> ================
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ cd
>>>>>>>> /home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem
>>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/slmodem-2.9.11-20090222/modem$
>>>>>>>> sudo su
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> wvdial
>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> slmodemd -c ITALY modem:1
>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> make SUPPORT_ALSA=1
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> slmodemd -c ITALY modem:1
>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> cp slmodemd /usr/sbin
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> slmodemd -c ITALY modem:1
>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> ================
>>>>>>>>
>>>>>>>> Have you got other ideas?
>>>>>>>>
>>>>>>>> Claudio.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Date: Fri, 4 Dec 2009 11:17:52 +0200
>>>>>>>>> From: Jacques.Goldberg@...
>>>>>>>>> To: ermante@...
>>>>>>>>> CC: olivares14031@...; discuss@...;
>>>>>>>>> marvin.stodolsky@...
>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel
>>>>>>>>> 2.6.31-15-generic
>>>>>>>>>
>>>>>>>>> Claudio,
>>>>>>>>>
>>>>>>>>> Did you download the file again today within about one hour back from
>>>>>>>>> now?
>>>>>>>>>
>>>>>>>>> I ask because this would then be after I installed the file with alsa
>>>>>>>>> stuff included.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Now, reading your report, I have a question about:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> wvdial
>>>>>>>>>
>>>>>>>>> Did you give the wvdial command in the same window where you had given
>>>>>>>>> before the command slmodemd?
>>>>>>>>>
>>>>>>>>> If yes, then to give wvdial you must have stopped slmodemd with CTRL-C
>>>>>>>>> which would explain why wvdial did not find the file /dev/ttySL0 : this
>>>>>>>>> file exists ONLY while slmodemd is running.
>>>>>>>>>
>>>>>>>>> If my guess is correct, then remember to ALWAYS start wvdial IN AN OTHER
>>>>>>>>> FREE WINDOW, not the one where slmodemd runs.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jacques
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Claudio Mantegazza wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I made again the command you told me and in this time i didn't receive
>>>>>>>>>> any errors....
>>>>>>>>>> Look at the command i wrote:
>>>>>>>>>>
>>>>>>>>>> =========================
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> lsdp_dummy.c Makefile modem_comp.c modem_defs.h modem_main.o modem_test
>>>>>>>>>> sysdep_common.c
>>>>>>>>>> dp_dummy.o Makefile.20080401 modem_comp.o modem_dp.h modem.o
>>>>>>>>>> modem_test.c sysdep_common.o
>>>>>>>>>> dp_sinus.c modem_at.c modem_datafile.c modem_ec.c modem_pack.c
>>>>>>>>>> modem_test.o
>>>>>>>>>> dp_sinus.o modem_at.o modem_datafile.o modem_ec.o modem_pack.o
>>>>>>>>>> modem_timer.c
>>>>>>>>>> dsplibs.o modem.c modem_debug.c modem.h modem_param.c modem_timer.h
>>>>>>>>>> homolog_data.c modem_cmdline.c modem_debug.h modem_homolog.h
>>>>>>>>>> modem_param.h modem_timer.o
>>>>>>>>>> homolog_data.o modem_cmdline.o modem_debug.o modem_main.c modem_param.o
>>>>>>>>>> slmodemd
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> modprobe snd-intel8x0m
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> aplay -l
>>>>>>>>>> **** Lista di PLAYBACK dispositivi hardware ****
>>>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 0: Intel ICH
>>>>>>>>>> [Intel 82801DB-ICH4]
>>>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 4: Intel ICH -
>>>>>>>>>> IEC958 [Intel 82801DB-ICH4 - IEC958]
>>>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>>
>>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>>> wvdial
>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>
>>>>>>>>>> =========================
>>>>>>>>>>
>>>>>>>>>> But i cannot be able to connect....
>>>>>>>>>>
>>>>>>>>>> Claudio.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ----------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Date: Thu, 3 Dec 2009 14:14:59 -0600
>>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>> To: ermante@...
>>>>>>>>>>> CC: discuss@...; marvin.stodolsky@...
>>>>>>>>>>>
>>>>>>>>>>> Claudio,
>>>>>>>>>>>
>>>>>>>>>>> What happens when you try
>>>>>>>>>>> $ sudo slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>>
>>>>>>>>>>> and try from the recently compiled slmodemd in
>>>>>>>>>>> slmodem-2.9.11-20090222/modem folder?
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Antonio
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Dec 3, 2009 at 8:01 AM, Claudio Mantegazza wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Antonio,
>>>>>>>>>>>> i'm very sorry but it didn't run...
>>>>>>>>>>>>
>>>>>>>>>>>> i made all that you told me but at the last command:
>>>>>>>>>>>>
>>>>>>>>>>>> =========
>>>>>>>>>>>> # make SUPPORT_ALSA=1
>>>>>>>>>>>> rebuild profile...
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_main.o -c modem_main.c
>>>>>>>>>>>> modem_main.c: In function ‘setup_stream’:
>>>>>>>>>>>> modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is
>>>>>>>>>>>> deprecated (declared at /usr/include/alsa/pcm.h:1116)
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_cmdline.o -c modem_cmdline.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o
>>>>>>>>>>>> -c modem.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_datafile.o -c modem_datafile.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_at.o -c modem_at.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_timer.o -c modem_timer.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_pack.o -c modem_pack.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_ec.o -c modem_ec.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_comp.o -c modem_comp.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_param.o -c modem_param.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_debug.o -c modem_debug.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> homolog_data.o -c homolog_data.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> dp_sinus.o -c dp_sinus.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> dp_dummy.o -c dp_dummy.c
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> sysdep_common.o -c sysdep_common.c
>>>>>>>>>>>> gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o
>>>>>>>>>>>> modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o
>>>>>>>>>>>> modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
>>>>>>>>>>>> /usr/lib/libasound.so
>>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>>> modem_test.o -c modem_test.c
>>>>>>>>>>>> modem_test.c: In function ‘modem_test_start’:
>>>>>>>>>>>> modem_test.c:110: warning: ignoring return value of ‘write’, declared
>>>>>>>>>>>> with attribute warn_unused_result
>>>>>>>>>>>> gcc -o modem_test modem_test.o modem_cmdline.o modem.o
>>>>>>>>>>>> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
>>>>>>>>>>>> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
>>>>>>>>>>>> dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> =========
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>>>>
>>>>>>>>>>>> =========
>>>>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>> =========
>>>>>>>>>>>> # wvdial
>>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>> =========
>>>>>>>>>>>>
>>>>>>>>>>>> it seems not like it...
>>>>>>>>>>>>
>>>>>>>>>>>> And now?
>>>>>>>>>>>> what can i do?
>>>>>>>>>>>>
>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ...............................................................................................................
>>>>>>>>>>>>
>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Date: Thu, 3 Dec 2009 07:11:57 -0600
>>>>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>> CC: marvin.stodolsky@...; jacques.goldberg@...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>
>>>>>>>>>>>>> If you want to build SLMODEMD on your own for your system, Please do
>>>>>>>>>>>>> the following:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Download:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>>>> Copy it to your linux partition/working directory, untar it with
>>>>>>>>>>>>> $ tar -zxvf slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>>>> $ cd slmodem-2.9.11-20090222
>>>>>>>>>>>>> $ cd modem
>>>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>>>>
>>>>>>>>>>>>> as show in README
>>>>>>>>>>>>>
>>>>>>>>>>>>> ====================
>>>>>>>>>>>>> 3. Build application 'slmodemd' with ALSA support. For this in
>>>>>>>>>>>>> slmodem-2.9.x dir:
>>>>>>>>>>>>>
>>>>>>>>>>>>> $ cd modem
>>>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>>>> ====================
>>>>>>>>>>>>>
>>>>>>>>>>>>> After this is successfull, then there will be a slmodemd file in that
>>>>>>>>>>>>> directory, copy it over to /usr/sbin
>>>>>>>>>>>>>
>>>>>>>>>>>>> and try the
>>>>>>>>>>>>> $ sudo slmodemd -c ITALY modem:1
>>>>>>>>>>>>>
>>>>>>>>>>>>> command again and hopefully it works this time around.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>
>>>>>>>>>>>>> PS.
>>>>>>>>>>>>> I hope that the "NO CARRIER" error shows up like it did for me with
>>>>>>>>>>>>> 2.6.31.X kernels but slamr module.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 12/3/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I untar the new one you sent me.
>>>>>>>>>>>>>> i exec the command:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ===============
>>>>>>>>>>>>>> # ./slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>>>>> ALSA support is not compiled in (see README for howto).
>>>>>>>>>>>>>> ===============
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now. how can i compile the ALSA support?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> P.s. i just installed the package libasound2-dev
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 14:18:11 -0500
>>>>>>>>>>>>>>> Subject: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>>>>> kernel
>>>>>>>>>>>>>>> 2.6.31-15-generic
>>>>>>>>>>>>>>> From: marvin.stodolsky@...
>>>>>>>>>>>>>>> To: ermante@...; Jacques.Goldberg@...;
>>>>>>>>>>>>>>> olivares14031@...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Used the attached SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jacques
>>>>>>>>>>>>>>> for the smartlink/ folder
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> MarvS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Dec 2, 2009 at 8:52 AM, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> because i didn't find which u told me... and this one is the last
>>>>>>>>>>>>>>>> one...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>>>> Not Found
>>>>>>>>>>>>>>>> The requested URL /packages/smartlink/SLMODEMD.gcc4.4.tar.gz was
>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>> found on this server.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Apache/2.0.52 (Red Hat) Server at linmodems.technion.ac.il Port 80
>>>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Maybe i don't understand something?
>>>>>>>>>>>>>>>> Can you tell me better where i can download the right file,
>>>>>>>>>>>>>>>> please?
>>>>>>>>>>>>>>>> give me the correct link....
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 07:15:13 -0600
>>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>>> CC: discuss@...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid
>>>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> why did you get the SLMODEMD_gcc4.4_alsa1.0.18.tar.gz?
>>>>>>>>>>>>>>>>> If your alsa verion is 1.0.20?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are:
>>>>>>>>>>>>>>>>> scheda 1: Modem [Intel 82801DB-ICH4 Modem], dispositivo 0: Intel
>>>>>>>>>>>>>>>>> ICH -
>>>>>>>>>>>>>>>>> Modem [Intel 82801DB-ICH4 Modem - Modem]
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>>> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem :
>>>>>>>>>>>>>>>>> playback
>>>>>>>>>>>>>>>>> 1 : capture 1
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>>> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 Modem at irq 5
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> If you have downloaded the recommended SLMODEMD: the package
>>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Does the same thing happen?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On 12/2/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1':
>>>>>>>>>>>>>>>>>> Invalid
>>>>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>>> mant@mant-laptop:~/Scaricati$ wvdial
>>>>>>>>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>>> It doen't work!
>>>>>>>>>>>>>>>>>> the drivers doesn't load fine!
>>>>>>>>>>>>>>>>>> ....
>>>>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Date: Tue, 1 Dec 2009 07:10:24 -0600
>>>>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>>>>> CC: marvin.stodolsky@...; stephenpinker79@...;
>>>>>>>>>>>>>>>>>>> discuss@...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> scanModem reports that your modem is supported via
>>>>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> For candidate modem in: 00:1f.6
>>>>>>>>>>>>>>>>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>>>> Primary device ID: 8086:24c6
>>>>>>>>>>>>>>>>>>> Subsystem PCI_id 1631:d005
>>>>>>>>>>>>>>>>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink
>>>>>>>>>>>>>>>>>>> type
>>>>>>>>>>>>>>>>>>> from Archives:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> This is a NEW softmodem case! Please send the output
>>>>>>>>>>>>>>>>>>> ModemData.txt
>>>>>>>>>>>>>>>>>>> to DISCUSS@... to enrich the Archive and help others!
>>>>>>>>>>>>>>>>>>> If further assistance is not needed, please use email Subject:
>>>>>>>>>>>>>>>>>>> New Case Only
>>>>>>>>>>>>>>>>>>> -------------------------------------------
>>>>>>>>>>>>>>>>>>> Support type needed or chipset: slmodemd
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> An ALSA (Advanced Linux Sound Architecture) modem driver:
>>>>>>>>>>>>>>>>>>> snd-intel8x0m
>>>>>>>>>>>>>>>>>>> provides Low Level support enabling contact with the modem
>>>>>>>>>>>>>>>>>>> hardware.
>>>>>>>>>>>>>>>>>>> For all BUT Conexant chip soft modems (using hsfmodem software)
>>>>>>>>>>>>>>>>>>> complementary High Level support is through a Smartlink
>>>>>>>>>>>>>>>>>>> utility:
>>>>>>>>>>>>>>>>>>> slmodemd
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Download from
>>>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/
>>>>>>>>>>>>>>>>>>> the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd.
>>>>>>>>>>>>>>>>>>> Unpack
>>>>>>>>>>>>>>>>>>> under Linux with:
>>>>>>>>>>>>>>>>>>> $ tar zxf SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>>>> and read instructions therein. But briefly, the modem is setup
>>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>>> command:
>>>>>>>>>>>>>>>>>>> sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
>>>>>>>>>>>>>>>>>>> reporting dynamic creation of ports:
>>>>>>>>>>>>>>>>>>> /dev/ttySL0 --> /dev/pts/N , with N some number
>>>>>>>>>>>>>>>>>>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for
>>>>>>>>>>>>>>>>>>> follow
>>>>>>>>>>>>>>>>>>> through guidance.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> If you have downloaded the package SLMODEMD.gcc4.4.tar.gz and
>>>>>>>>>>>>>>>>>>> tried
>>>>>>>>>>>>>>>>>>> the above instructions and are not getting anywhere/(modem does
>>>>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>>>>> respond) it could be because of
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> For candidate card in slot 00:1f.6, firmware information and
>>>>>>>>>>>>>>>>>>> bootup
>>>>>>>>>>>>>>>>>>> diagnostics are:
>>>>>>>>>>>>>>>>>>> PCI slot PCI ID SubsystemID Name
>>>>>>>>>>>>>>>>>>> ---------- --------- --------- --------------
>>>>>>>>>>>>>>>>>>> 00:1f.6 8086:24c6 1631:d005 Modem: Intel Corporation
>>>>>>>>>>>>>>>>>>> 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Modem interrupt assignment and sharing:
>>>>>>>>>>>>>>>>>>> 5: 137 XT-PIC-XT yenta, Intel 82801DB-ICH4, Intel
>>>>>>>>>>>>>>>>>>> 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
>>>>>>>>>>>>>>>>>>> [ 0.071472] pci 0000:00:1f.6: reg 10 io port: [0xe300-0xe3ff]
>>>>>>>>>>>>>>>>>>> [ 0.071480] pci 0000:00:1f.6: reg 14 io port: [0xe400-0xe47f]
>>>>>>>>>>>>>>>>>>> [ 0.071521] pci 0000:00:1f.6: PME# supported from D0 D3hot
>>>>>>>>>>>>>>>>>>> D3cold
>>>>>>>>>>>>>>>>>>> [ 0.071525] pci 0000:00:1f.6: PME# disabled
>>>>>>>>>>>>>>>>>>> [ 0.956536] serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI
>>>>>>>>>>>>>>>>>>> 5
>>>>>>>>>>>>>>>>>>> (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>>>> [ 0.956547] serial 0000:00:1f.6: PCI INT B disabled
>>>>>>>>>>>>>>>>>>> [ 3186.856643] Intel ICH Modem 0000:00:1f.6: PCI INT B ->
>>>>>>>>>>>>>>>>>>> Link[LNKB]
>>>>>>>>>>>>>>>>>>> -> GSI 5 (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>>>> [ 3186.856669] Intel ICH Modem 0000:00:1f.6: setting latency
>>>>>>>>>>>>>>>>>>> timer to
>>>>>>>>>>>>>>>>>>> 64
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> The PCI slot 00:1f.6 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@...
>>>>>>>>>>>>>>>>>>> if help is needed.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Let us know if the package SLMODEMD.gcc4.4.tar.gz works or not,
>>>>>>>>>>>>>>>>>>> and if
>>>>>>>>>>>>>>>>>>> the driver loads fine but does not respond, follow the above
>>>>>>>>>>>>>>>>>>> instructions to see if it can work or not.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _________________________________________________________________
>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _________________________________________________________________
>>>>>>>> I tuoi amici sempre a portata di clic, sul nuovo Web Messenger
>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>> _________________________________________________________________
>>>> Scopri tuttele novità di Internet Explorer 8
>>>> http://www.microsoft.com/italy/windows/internet-explorer/msn.aspx
>>
>> _________________________________________________________________
>> 25 Gigabyte per le tue foto online
>> http://www.windowslive.it/foto.aspx

_________________________________________________________________
Di che umore sei oggi? Dillo con le Emoticon
http://intrattenimento.it.msn.com/emoticon

Re: what is my modem chipset and model

2009-12-10T17:39:27Z

Seyed,

scanModem detects that your modem is an hsfmodem:

For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 1025:0136
Softmodem codec or chipset from diagnostics: 0x14f12c06
from Archives:
The HDA card softmodem chip is 0x14f12c06

Support type needed or chipset: hsfmodem

Writing DOCs/Intel.txt

For owners of a Dell PCs with Conexant HSF modems, a driver source
package with full speed enabled is available, but requires driver
compiling. Read DOCs/Conexant.txt

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.28_11_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.

scanModem also reports that you don't have wvdial installed:

The dialer utility package WVDIAL does not appear to be installed on
your System.
For Ubuntu Jaunty users, there are at the bottom of
http://linmodems.technion.ac.il/packages/:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your
Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

Regards,

Antonio

On 12/10/09, seyyed hassan mousavi nazar <s.ha.mousavi.nazar@...> wrote:
> hello
> please help me to connect internet with linux ubuntu 9.04
>

what is my modem chipset and model

2009-12-10T13:51:26Z

hello
please help me to connect internet with linux ubuntu 9.04

Only plain text email is forwarded by the Discuss@... List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.28-11-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@... 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.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
scanModem update of: 2009_12_07

The dialer utility package WVDIAL does not appear to be installed on your System.
For Ubuntu Jaunty users, there are at the bottom of http://linmodems.technion.ac.il/packages/:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

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

There are no blacklisted modem drivers in /etc/modprobe* files

Potentially useful modem drivers now loaded are:
cdc_acm snd_hda_intel

Attached USB devices are:
ID 09da:000a A4 Tech Co., Ltd Port Mouse
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@...

For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:284b 1025:0136 Audio device: Intel Corporation 82801H

Modem interrupt assignment and sharing:
22: 2652 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.524558] pci 0000:00:1b.0: reg 10 64bit mmio: [0x58300000-0x58303fff]
[ 0.524656] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.524665] pci 0000:00:1b.0: PME# disabled
[ 13.592310] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 13.592451] 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@...
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.18
The modem cards detected by "aplay -l" are: None

The /proc/asound/pcm file reports:
-----------------------
00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1

about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x58300000 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.28-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko
The modem codec file for the HDA card is: /proc/asound/card0/codec#1
--------------------------------------------------------
Codec: Conexant ID 2c06
Address: 1
Vendor Id: 0x14f12c06
Subsystem Id: 0x10250136
Revision Id: 0x100000
Modem Function Group: 0x2

The audio card hosts a softmodem chip: 0x14f12c06

14f1 is the Conexant Vendor ID, and 0x14f12c06 a softmodem chipset.
Get a hsfmodem package through http://www.linuxant.com

If not a Conexant modem, the driver hsfmodem-drivers 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 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1025:0136
IRQ=22
HDA=8086:284b
SOFT=8086:284b.HDA
HDAchipVendorID=14f1
CHIP=0x14f12c06
IDENT=hsfmodem
Driver=hsfmodem-drivers

For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 1025:0136
Softmodem codec or chipset from diagnostics: 0x14f12c06
from Archives:
The HDA card softmodem chip is 0x14f12c06

Support type needed or chipset: hsfmodem

Writing DOCs/Intel.txt

For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.28_11_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.

The directions following below need only be pursued, if the above procedures are not adequate.

Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion: 2.6.28_11_generic
They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

Support for Conexant chips hosted on High Definition Audio cards may require
installation of additional packages, one of the alsa-driver-linuxant packages
on http://www.linuxant.com/alsa-driver/ At the same time download the
alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the
hsfmodem install, there will be a message if there is necessary installation of
alsa-driver-linuxant

The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

There may a message that "Dependencies" are not satisfied. In this case the Ubuntu/Debian packages to be installed are linux-libc-dev & libc6-dev. Package
names may be different for other Linuxes. If not on your install CD, these
packages can be searched for at http://packages.ubuntu.com. After download,
they can be coinstalled with:
sudo dpkg -i li*.deb
Again try the alsa-driver-linuxant

There may be a message that the patch must be applied. In this case get the
ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
Under Linux, this package is unpacked with:
$ tar jxf alsa*.tar.bz2
Next the patch is applied with:
$ patch -p0 < alsa-driver-1.0.17-1.patch

See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
for details on compiling and installing replacement snd-hda-intel + its
dependent drivers.
After the installation is completed, rerun the hsfmodem installation.
Reboot and try to detect the modem with Root permission:
sudo wvdialconf /etc/wvdial.conf

Read DOCs/Conexant.txt

Writing DOCs/Conexant.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.3
and the compiler used in kernel assembly: 4.3.3

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.28-11-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 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.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

Re: help to me

2009-12-10T11:20:11Z

The dialer utility package WVDIAL does not appear to be installed on
your System.
For Ubuntu users, there are at the bottom of
http://linmodems.technion.ac.il/packages/:
wvdial_karnic_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your
Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.31_16_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt & Conexant.txt for details.

MarvS

On Thu, Dec 10, 2009 at 9:16 AM, Ubuntu Family <ubuntu0098@...> wrote:

> Only plain text email is forwarded by the Discuss@... List
> Server,
> as HTML can contain viruses. Use as the email Subject Line:
> YourName, YourCountry kernel 2.6.31-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@... 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.31-16-generic (buildd@rothera) (gcc version
> 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009
> scanModem update of: 2009_12_07
>
> The dialer utility package WVDIAL does not appear to be installed on your
> System.
> For Ubuntu Jaunty users, there are at the bottom of
> http://linmodems.technion.ac.il/packages/:
> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
> wvdial_jaunty_i386.zip for 32 bit systems.
> These are about 1 MB in size. After downloaded and copied into your Linux
> partition:
> $ unzip wv*.zip
> Within the new folder:
> $ sudo dpkg -i *.deb
> will complete the wvdial installation
> Please read Modem/DOCs/wvdial.txt for usage information.
>
> The dkms driver upgrade utilities are installed,
>
> 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 0b05:620a ASUSTek Computer, Inc. Remote NDIS Device
> ID 08ff:2810 AuthenTec, Inc.
> ID 413c:8156 Dell Computer Corp.
> ID 413c:8158 Dell Computer Corp.
> ID 413c:8157 Dell Computer Corp.
> ID 0a5c:4500 Broadcom Corp.
> 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@...
>
> 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 1028:0263 Audio device: Intel Corporation 82801I
>
> Modem interrupt assignment and sharing:
> 21: 16838 15623 IO-APIC-fasteoi uhci_hcd:usb4, uhci_hcd:usb7,
> HDA Intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [ 0.364901] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf6afc000-0xf6afffff]
> [ 0.364962] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [ 0.364966] pci 0000:00:1b.0: PME# disabled
> [ 17.138742] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low) ->
> IRQ 21
> [ 17.138769] HDA Intel 0000:00:1b.0: setting latency timer to 64
> [ 17.224177] input: HDA Digital PCBeep as
> /devices/pci0000:00/0000:00:1b.0/input/input10
> [ 17.313641] input: HDA Intel Mic at Ext Right Jack as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
> [ 17.313706] input: HDA Intel Line Out at Sep Left Jack as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
> [ 17.313759] input: HDA Intel HP Out at Ext Right Jack as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
>
> 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@...
> 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.20
> The modem cards detected by "aplay -l" are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 2
> 00-01: STAC92xx Digital : STAC92xx Digital : playback 1
> 00-03: INTEL HDMI : INTEL HDMI : playback 1
>
> about /proc/asound/cards:
> ------------------------
> 0 [Intel ]: HDA-Intel - HDA Intel
> HDA Intel at 0xf6afc000 irq 21
>
> PCI slot 00:1b.0 has a High Definition Audio Card
> The drivers are in the kernel modules tree at:
> /lib/modules/2.6.31-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko
> /lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
> The modem codec file for the HDA card is: /proc/asound/card0/codec#1
> --------------------------------------------------------
> Codec: Conexant ID 2c06
> Address: 1
> Function Id: 0x2
> Vendor Id: 0x14f12c06
> Subsystem Id: 0x14f1000f
> Revision Id: 0x100000
> Modem Function Group: 0x2
>
> The audio card hosts a softmodem chip: 0x14f12c06
>
> 14f1 is the Conexant Vendor ID, and 0x14f12c06 a softmodem chipset.
> Get a hsfmodem package through http://www.linuxant.com
>
> If not a Conexant modem, the driver hsfmodem-drivers 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=1028:0263
> IRQ=21
> HDA=8086:293e
> SOFT=8086:293e.HDA
> HDAchipVendorID=14f1
> CHIP=0x14f12c06
> IDENT=hsfmodem
> Driver=hsfmodem-drivers
>
> For candidate modem in: 00:1b.0
> 0403 Audio device: Intel Corporation 82801I
> Primary device ID: 8086:293e
> Subsystem PCI_id 1028:0263
> Softmodem codec or chipset from diagnostics: 0x14f12c06
> from Archives:
> The HDA card softmodem chip is 0x14f12c06
>
> Support type needed or chipset: hsfmodem
>
>
> Writing DOCs/Intel.txt
>
> For owners of a Dell PCs with Conexant HSF modems, a driver source package
> with full speed enabled is available, but requires driver compiling. Read
> DOCs/Conexant.txt
>
> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
> download hsfmodem-7.80.02.05full_k2.6.31_16_generic_ubuntu_i386.deb.zip
> Under Linux unpack with:
> $ unzip hsfmodem*.zip
> Then install with:
> $ sudo dpkg -i hsfmodem*.deb
> Subsequently, the modem should be found with
> $ sudo wvdialconf /etc/wvdial.conf
> Edit in your personal information with:
> $ sudo gedit /etc/wvdial.conf
> and try dialing out with:
> $ sudo wvdial.
> See DOCs/Testing.txt for details.
>
> The directions following below need only be pursued, if the above procedures
> are not adequate.
>
> Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find
> the
> hsfmodem package matching your System. For several Linux distros, there are
> precompiled drivers matched to specific kernels. These have within the
> FileName,
> your KernelVersion: 2.6.31_16_generic
> They can be found through
> http://www.linuxant.com/drivers/hsf/full/downloads.php
> A more precise location may be given a few paragraphs below.
> If an EXACT Match with your your KernelVersion is not found, one of the
> "Generic packages with source" near the bottom of the page must be used.
> Downloaded packages must be moved into the Linux partition (home folder is
> OK)
> and unzipped with:
> unzip hsf*.zip
> The installation command for a .deb suffic packages is, with root/adm
> permission:
> sudo dpkg -i hsf*.deb
> while for .rpm suffix it is, with:
> rpm -i hsf*.rpm
>
> Support for Conexant chips hosted on High Definition Audio cards may require
> installation of additional packages, one of the alsa-driver-linuxant
> packages
> on http://www.linuxant.com/alsa-driver/ At the same time download the
> alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the
> hsfmodem install, there will be a message if there is necessary installation
> of
> alsa-driver-linuxant
>
> The installation command for a .deb suffic packages is, with root/adm
> permission:
> sudo dpkg -i hsf*.deb
> while for .rpm suffix it is, with:
> rpm -i hsf*.rpm
>
> There may a message that "Dependencies" are not satisfied. In this case the
> Ubuntu/Debian packages to be installed are linux-libc-dev & libc6-dev.
> Package
> names may be different for other Linuxes. If not on your install CD, these
> packages can be searched for at http://packages.ubuntu.com. After download,
> they can be coinstalled with:
> sudo dpkg -i li*.deb
> Again try the alsa-driver-linuxant
>
> There may be a message that the patch must be applied. In this case get the
> ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
> Under Linux, this package is unpacked with:
> $ tar jxf alsa*.tar.bz2
> Next the patch is applied with:
> $ patch -p0 < alsa-driver-1.0.17-1.patch
>
> See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
> for details on compiling and installing replacement snd-hda-intel + its
> dependent drivers.
> After the installation is completed, rerun the hsfmodem installation.
> Reboot and try to detect the modem with Root permission:
> sudo wvdialconf /etc/wvdial.conf
>
> Read DOCs/Conexant.txt
>
> Writing DOCs/Conexant.txt
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.4.1
> and the compiler used in kernel assembly: 4.4.1
>
>
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.4
> linuc_headers base folder /lib/modules/2.6.31-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 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 277352 2009-02-20 20:55 /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 eth1
> usb0
> 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 --------
>
>

Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic

2009-12-10T11:14:00Z

Claudio,

Slamr is not the preferred driver for your
>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>> Primary device ID: 8086:24c6
>>>> Subsystem PCI_id 1631:d005
>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink type
>>>> from Archives:
rather it is the snd-intel8x0m driver. With slmodemd already
written to /usr/sbin/slmodemd,
it suffices to activate it with:
$ sudo slmodemd -c ITALY modem:1

Then open a 2nd console and the modem should be found by:
$ sudo wvdialconf

MarvS

On Thu, Dec 10, 2009 at 2:58 AM, Claudio Mantegazza <ermante@...> wrote:

>
> I did it but i stopped in your point 12).
> Look at what i received...
>
> ==============
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./setup
>
> Installing slmodemd helper to /usr/sbin/slmodemd
>
> Writing log to slmodemd_Inst.txt
> ./setup: 14: slmodemd: not found
> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
> Version verified:    2.9.11
> Read the slmodemd_Inst.txt
>
> There is already installed a slmodemd of version:    2.9.11
> There is a file /usr/sbin/slmodemd
> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
> Version verified:    2.9.11
> Read the slmodemd_Inst.txt
>
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
> error: cannot setup device `/dev/slamr0'
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe snd-intel8x0m
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
> error: cannot setup device `/dev/slamr0'
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
> error: cannot setup device `/dev/slamr0'
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe slamr
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
> error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
> error: cannot setup device `/dev/slamr0'
>
> ==============
> And in an other window.....
> ==============
>
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ wvdialconf /etc/wvdial.conf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> Modem Port Scan<*1>: S0   S1   S2   S3
>
>
> Sorry, no modem was detected! Is it in use by another program?
> Did you configure it properly with setserial?
>
> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>
> If you still have problems, send mail to <wvdial-list@...>.
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
> ===============
>
> Why it doesn't detect my modem?
> Claudio.
>
>
>
> ----------------------------------------
>> Date: Wed, 9 Dec 2009 12:51:33 -0500
>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>> From: marvin.stodolsky@...
>> To: ermante@...
>> CC: discuss@...
>>
>> Don't run "make", as the compile has already been done. Just do:
>> $ sudo ./setup
>>
>> MarvS
>>
>> On Wed, Dec 9, 2009 at 5:33 AM, Claudio Mantegazza wrote:
>>>
>>> Marvin,Jacques, wait a minute....
>>>
>>> I did only a part which jacques told me...
>>> i arrived to do all until jacques told me to continue to do what wrote in the README file at the installation but when i write the command in it i receice an error... Look at...
>>>
>>> =================
>>> root@mantegazza-laptop:~# find / -iname SLMODEMD*
>>> root@mantegazza-laptop:~# cd /home/mantegazza/Scaricati
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati# tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati# cd SLMODEMD_gcc4.4_alsa1.0.21
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# exit
>>> exit
>>> mantegazza@mantegazza-laptop:~$ cd /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ make
>>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo su
>>> [sudo] password for mantegazza:
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make
>>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make install
>>> make: *** Nessuna regola per creare l'obiettivo «install». Arresto.
>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21#
>>> ===================
>>>
>>> So what i have to do before continue?
>>>
>>> Claudio.
>>>
>>>
>>>
>>> ----------------------------------------
>>>> Date: Sat, 5 Dec 2009 16:37:08 -0500
>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>>>> From: marvin.stodolsky@...
>>>> To: discuss@...
>>>> CC: ermante@...
>>>>
>>>> Claudio
>>>>
>>>> You are missing a file with the contents below.
>>>> Make a file with these contents, but replacing:
>>>> DialUpNumber
>>>> YourLoginName
>>>> YourPassword
>>>> This file should be named wvdial.conf, and can initially be in your home folder.
>>>> Then after the
>>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>>> open a 2nd console and do:
>>>> $ sudo wvdial -config=wvdial.conf
>>>>
>>>> MarvS
>>>>
>>>> [Dialer Defaults]
>>>> Phone = DialUpNumber
>>>> Username = YourLoginName
>>>> Password = YourPassword
>>>> Init1 = ATZ
>>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
>>>> Modem Type = Analog Modem
>>>> ISDN = 0
>>>> New PPPD = yes
>>>> Modem = /dev/ttySL0
>>>> Carrier Check = no
>>>> Baud = 460800
>>>>
>>>> On Fri, Dec 4, 2009 at 9:40 PM, Marvin Stodolsky
>>>> wrote:
>>>>> The modem activation command should be:
>>>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>>>> there should be reported creation of a port:
>>>>> /dev/ttySL0 --> /dev/pts/N , N some number
>>>>>
>>>>> Only after such a success should one try;
>>>>> $ sudo wvdial
>>>>>
>>>>> MarvS
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Dec 4, 2009 at 8:06 AM, Jacques Goldberg
>>>>> wrote:
>>>>>> Claudio,
>>>>>>
>>>>>>
>>>>>> I believe that you have reached such a mess level that it has become
>>>>>> impossible to know which is what.
>>>>>>
>>>>>> Here is what I would do in your place:
>>>>>>
>>>>>> Because you used two versions of file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz ,
>>>>>>
>>>>>> 1-be root or sudo before any command
>>>>>>
>>>>>> 2-go into directory /usr/sbin
>>>>>> 3-in that directory give command rm slmodemd*
>>>>>>
>>>>>> Make ABSOLUTELY SURE that you write slmodemd* so that there is NOTHING, NO
>>>>>> SPACE, NOTHING ELSE, between slmodemd and the * . ABSOLUTELY SURE.
>>>>>>
>>>>>> Answer yes everytime you are prompted to erase a file with name starting
>>>>>> with slmodemd and NO in any other case.
>>>>>>
>>>>>> 4-go into directory named SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>
>>>>>> 5-in that directory give command make uninstall
>>>>>>
>>>>>> 6-give the command cd
>>>>>>
>>>>>> 7-give the command find / -iname SLMODEMD* .Attention
>>>>>> SLMODEMD in capital case.
>>>>>>
>>>>>> This will give a list of all the files in your computer with a name
>>>>>> starting with SLMODEMD
>>>>>>
>>>>>> Erase all these files one at a time. To erase a file the command is rm ;
>>>>>> to erase an empty directory the command is rmdir; to erase a directory which
>>>>>> is not empty the command is rm -rf
>>>>>> Always start with rm and then try rmdir and then rm -rf if the
>>>>>> preceeding one is not accepted.
>>>>>>
>>>>>> 8-Now, in your usual directory, the one where you usually login, download
>>>>>> the file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>
>>>>>> Do not try to use one which has been downloaded before unless you are
>>>>>> ABSOLUTELY sure that this is the one which I
>>>>>>
>>>>>> placed this morning.
>>>>>>
>>>>>> 9-Give the command tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>
>>>>>> 10-Change directory with command cd SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>
>>>>>> 11-Do exactly, one time and one time only, what Marv has written to you to
>>>>>> do or what is written in file README in the directory where you are starting
>>>>>> from point 4 in INSTALLATION
>>>>>>
>>>>>> 12-After you have given the command slmodemd and it has succeeded, in
>>>>>> an other window give the command
>>>>>>
>>>>>> wvdialconf /etc/wvdial.conf (no . in wvdialconf and a , in
>>>>>> /etc/wvdial.conf
>>>>>>
>>>>>> wvdialconf will find your modem
>>>>>>
>>>>>> Edit /etc/wvdial.conf as explained in
>>>>>> http://linmodems.technion.ac.il/wvdial.html   . Remember that you need
>>>>>>
>>>>>> Carrier Check = no
>>>>>>
>>>>>> 13- When the file /etc/wvdial.conf has been edited and saved, in that window
>>>>>> or any window except the one used for slmodemd, the command wvdial
>>>>>> should start your modem.
>>>>>>
>>>>>> when everything works well wvdial does NOT exit but stays doing nothing.
>>>>>>
>>>>>> Use your browser (like Firefox) and try to surf.
>>>>>>
>>>>>>
>>>>>> Please remember: every time you do something else than what we tell you to
>>>>>> do, like installing several slmodemd , you take the risk to create the
>>>>>> conditions for failure.
>>>>>>
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>>
>>>>>> Claudio Mantegazza wrote:
>>>>>>
>>>>>>> I downloaded again the new file.
>>>>>>> i saw that there was updated 1 hour ago...
>>>>>>> and in a new window (not the same about the
>>>>>>> =======================
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ wvdial
>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ cd
>>>>>>> /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ ls
>>>>>>> 1st_Read.txt COPYING Files.txt setup slmodemd
>>>>>>> slmodemd.txt Testing.txt wvdial.conf
>>>>>>> Changes CountryList.txt README Slmodem-ALSA.txt
>>>>>>> slmodemd_Inst.txt slmodem.txt Unload.txt
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo
>>>>>>> ./setup
>>>>>>> [sudo] password for mantegazza:
>>>>>>> Installing slmodemd helper to /usr/sbin/slmodemd
>>>>>>>
>>>>>>> Writing log to slmodemd_Inst.txt
>>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>>> There is a file /usr/sbin/slmodemd
>>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>>> for version 2.9.11
>>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>>> Version verified: 2.9.11
>>>>>>> Read the slmodemd_Inst.txt
>>>>>>>
>>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>>> There is a file /usr/sbin/slmodemd
>>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>>> for version 2.9.11
>>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>>> Version verified: 2.9.11
>>>>>>> Read the slmodemd_Inst.txt
>>>>>>>
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>> wvdial
>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>> =======================
>>>>>>>
>>>>>>> but if in this windows i write the slmodem command:
>>>>>>>
>>>>>>> ======================
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>> slmodemd --alsa -c YOUR_COUNTRY modem:1 error: mixer setup: attach hw:1
>>>>>>> error: No such file or directory
>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid argument
>>>>>>> error: cannot setup device `modem:1'
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>>> ======================
>>>>>>>
>>>>>>> I receive this error....
>>>>>>>
>>>>>>> and if i return in the other folder and i write...
>>>>>>>
>>>>>>> ================
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ cd
>>>>>>> /home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem
>>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/slmodem-2.9.11-20090222/modem$
>>>>>>> sudo su
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> wvdial
>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> slmodemd -c ITALY modem:1
>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>> error: cannot setup device `modem:1'
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> make SUPPORT_ALSA=1
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> slmodemd -c ITALY modem:1
>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>> error: cannot setup device `modem:1'
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> cp slmodemd /usr/sbin
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> slmodemd -c ITALY modem:1
>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>> error: cannot setup device `modem:1'
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> ================
>>>>>>>
>>>>>>> Have you got other ideas?
>>>>>>>
>>>>>>> Claudio.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------
>>>>>>>
>>>>>>>>
>>>>>>>> Date: Fri, 4 Dec 2009 11:17:52 +0200
>>>>>>>> From: Jacques.Goldberg@...
>>>>>>>> To: ermante@...
>>>>>>>> CC: olivares14031@...; discuss@...;
>>>>>>>> marvin.stodolsky@...
>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel
>>>>>>>> 2.6.31-15-generic
>>>>>>>>
>>>>>>>> Claudio,
>>>>>>>>
>>>>>>>> Did you download the file again today within about one hour back from
>>>>>>>> now?
>>>>>>>>
>>>>>>>> I ask because this would then be after I installed the file with alsa
>>>>>>>> stuff included.
>>>>>>>>
>>>>>>>>
>>>>>>>> Now, reading your report, I have a question about:
>>>>>>>>
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> wvdial
>>>>>>>>
>>>>>>>> Did you give the wvdial command in the same window where you had given
>>>>>>>> before the command slmodemd?
>>>>>>>>
>>>>>>>> If yes, then to give wvdial you must have stopped slmodemd with CTRL-C
>>>>>>>> which would explain why wvdial did not find the file /dev/ttySL0 : this
>>>>>>>> file exists ONLY while slmodemd is running.
>>>>>>>>
>>>>>>>> If my guess is correct, then remember to ALWAYS start wvdial IN AN OTHER
>>>>>>>> FREE WINDOW, not the one where slmodemd runs.
>>>>>>>>
>>>>>>>>
>>>>>>>> Jacques
>>>>>>>>
>>>>>>>>
>>>>>>>> Claudio Mantegazza wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> I made again the command you told me and in this time i didn't receive
>>>>>>>>> any errors....
>>>>>>>>> Look at the command i wrote:
>>>>>>>>>
>>>>>>>>> =========================
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> lsdp_dummy.c Makefile modem_comp.c modem_defs.h modem_main.o modem_test
>>>>>>>>> sysdep_common.c
>>>>>>>>> dp_dummy.o Makefile.20080401 modem_comp.o modem_dp.h modem.o
>>>>>>>>> modem_test.c sysdep_common.o
>>>>>>>>> dp_sinus.c modem_at.c modem_datafile.c modem_ec.c modem_pack.c
>>>>>>>>> modem_test.o
>>>>>>>>> dp_sinus.o modem_at.o modem_datafile.o modem_ec.o modem_pack.o
>>>>>>>>> modem_timer.c
>>>>>>>>> dsplibs.o modem.c modem_debug.c modem.h modem_param.c modem_timer.h
>>>>>>>>> homolog_data.c modem_cmdline.c modem_debug.h modem_homolog.h
>>>>>>>>> modem_param.h modem_timer.o
>>>>>>>>> homolog_data.o modem_cmdline.o modem_debug.o modem_main.c modem_param.o
>>>>>>>>> slmodemd
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> modprobe snd-intel8x0m
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> aplay -l
>>>>>>>>> **** Lista di PLAYBACK dispositivi hardware ****
>>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 0: Intel ICH
>>>>>>>>> [Intel 82801DB-ICH4]
>>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 4: Intel ICH -
>>>>>>>>> IEC958 [Intel 82801DB-ICH4 - IEC958]
>>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>
>>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>>> wvdial
>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>
>>>>>>>>> =========================
>>>>>>>>>
>>>>>>>>> But i cannot be able to connect....
>>>>>>>>>
>>>>>>>>> Claudio.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ----------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Date: Thu, 3 Dec 2009 14:14:59 -0600
>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>> From: olivares14031@...
>>>>>>>>>> To: ermante@...
>>>>>>>>>> CC: discuss@...; marvin.stodolsky@...
>>>>>>>>>>
>>>>>>>>>> Claudio,
>>>>>>>>>>
>>>>>>>>>> What happens when you try
>>>>>>>>>> $ sudo slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>
>>>>>>>>>> and try from the recently compiled slmodemd in
>>>>>>>>>> slmodem-2.9.11-20090222/modem folder?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Antonio
>>>>>>>>>>
>>>>>>>>>> On Thu, Dec 3, 2009 at 8:01 AM, Claudio Mantegazza wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Antonio,
>>>>>>>>>>> i'm very sorry but it didn't run...
>>>>>>>>>>>
>>>>>>>>>>> i made all that you told me but at the last command:
>>>>>>>>>>>
>>>>>>>>>>> =========
>>>>>>>>>>> # make SUPPORT_ALSA=1
>>>>>>>>>>> rebuild profile...
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_main.o -c modem_main.c
>>>>>>>>>>> modem_main.c: In function ‘setup_stream’:
>>>>>>>>>>> modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is
>>>>>>>>>>> deprecated (declared at /usr/include/alsa/pcm.h:1116)
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_cmdline.o -c modem_cmdline.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o
>>>>>>>>>>> -c modem.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_datafile.o -c modem_datafile.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_at.o -c modem_at.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_timer.o -c modem_timer.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_pack.o -c modem_pack.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_ec.o -c modem_ec.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_comp.o -c modem_comp.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_param.o -c modem_param.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_debug.o -c modem_debug.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> homolog_data.o -c homolog_data.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> dp_sinus.o -c dp_sinus.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> dp_dummy.o -c dp_dummy.c
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> sysdep_common.o -c sysdep_common.c
>>>>>>>>>>> gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o
>>>>>>>>>>> modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o
>>>>>>>>>>> modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
>>>>>>>>>>> /usr/lib/libasound.so
>>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>>> modem_test.o -c modem_test.c
>>>>>>>>>>> modem_test.c: In function ‘modem_test_start’:
>>>>>>>>>>> modem_test.c:110: warning: ignoring return value of ‘write’, declared
>>>>>>>>>>> with attribute warn_unused_result
>>>>>>>>>>> gcc -o modem_test modem_test.o modem_cmdline.o modem.o
>>>>>>>>>>> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
>>>>>>>>>>> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
>>>>>>>>>>> dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> =========
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>>>
>>>>>>>>>>> =========
>>>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>> =========
>>>>>>>>>>> # wvdial
>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>> =========
>>>>>>>>>>>
>>>>>>>>>>> it seems not like it...
>>>>>>>>>>>
>>>>>>>>>>> And now?
>>>>>>>>>>> what can i do?
>>>>>>>>>>>
>>>>>>>>>>> Claudio.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ...............................................................................................................
>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Date: Thu, 3 Dec 2009 07:11:57 -0600
>>>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>> CC: marvin.stodolsky@...; jacques.goldberg@...
>>>>>>>>>>>>
>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>
>>>>>>>>>>>> If you want to build SLMODEMD on your own for your system, Please do
>>>>>>>>>>>> the following:
>>>>>>>>>>>>
>>>>>>>>>>>> Download:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>>> Copy it to your linux partition/working directory, untar it with
>>>>>>>>>>>> $ tar -zxvf slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>>> $ cd slmodem-2.9.11-20090222
>>>>>>>>>>>> $ cd modem
>>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>>>
>>>>>>>>>>>> as show in README
>>>>>>>>>>>>
>>>>>>>>>>>> ====================
>>>>>>>>>>>> 3. Build application 'slmodemd' with ALSA support. For this in
>>>>>>>>>>>> slmodem-2.9.x dir:
>>>>>>>>>>>>
>>>>>>>>>>>> $ cd modem
>>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>>> ====================
>>>>>>>>>>>>
>>>>>>>>>>>> After this is successfull, then there will be a slmodemd file in that
>>>>>>>>>>>> directory, copy it over to /usr/sbin
>>>>>>>>>>>>
>>>>>>>>>>>> and try the
>>>>>>>>>>>> $ sudo slmodemd -c ITALY modem:1
>>>>>>>>>>>>
>>>>>>>>>>>> command again and hopefully it works this time around.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Antonio
>>>>>>>>>>>>
>>>>>>>>>>>> PS.
>>>>>>>>>>>> I hope that the "NO CARRIER" error shows up like it did for me with
>>>>>>>>>>>> 2.6.31.X kernels but slamr module.
>>>>>>>>>>>>
>>>>>>>>>>>> On 12/3/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I untar the new one you sent me.
>>>>>>>>>>>>> i exec the command:
>>>>>>>>>>>>>
>>>>>>>>>>>>> ===============
>>>>>>>>>>>>> # ./slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>>>> ALSA support is not compiled in (see README for howto).
>>>>>>>>>>>>> ===============
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now. how can i compile the ALSA support?
>>>>>>>>>>>>>
>>>>>>>>>>>>> P.s. i just installed the package libasound2-dev
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks...
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 14:18:11 -0500
>>>>>>>>>>>>>> Subject: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>>>> kernel
>>>>>>>>>>>>>> 2.6.31-15-generic
>>>>>>>>>>>>>> From: marvin.stodolsky@...
>>>>>>>>>>>>>> To: ermante@...; Jacques.Goldberg@...;
>>>>>>>>>>>>>> olivares14031@...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Used the attached SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Jacques
>>>>>>>>>>>>>> for the smartlink/ folder
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> MarvS
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Dec 2, 2009 at 8:52 AM, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> because i didn't find which u told me... and this one is the last
>>>>>>>>>>>>>>> one...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>>> Not Found
>>>>>>>>>>>>>>> The requested URL /packages/smartlink/SLMODEMD.gcc4.4.tar.gz was
>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>> found on this server.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Apache/2.0.52 (Red Hat) Server at linmodems.technion.ac.il Port 80
>>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Maybe i don't understand something?
>>>>>>>>>>>>>>> Can you tell me better where i can download the right file,
>>>>>>>>>>>>>>> please?
>>>>>>>>>>>>>>> give me the correct link....
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 07:15:13 -0600
>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>> CC: discuss@...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid
>>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> why did you get the SLMODEMD_gcc4.4_alsa1.0.18.tar.gz?
>>>>>>>>>>>>>>>> If your alsa verion is 1.0.20?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are:
>>>>>>>>>>>>>>>> scheda 1: Modem [Intel 82801DB-ICH4 Modem], dispositivo 0: Intel
>>>>>>>>>>>>>>>> ICH -
>>>>>>>>>>>>>>>> Modem [Intel 82801DB-ICH4 Modem - Modem]
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem :
>>>>>>>>>>>>>>>> playback
>>>>>>>>>>>>>>>> 1 : capture 1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>>> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>> Intel 82801DB-ICH4 Modem at irq 5
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> If you have downloaded the recommended SLMODEMD: the package
>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Does the same thing happen?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 12/2/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1':
>>>>>>>>>>>>>>>>> Invalid
>>>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>> mant@mant-laptop:~/Scaricati$ wvdial
>>>>>>>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>>> It doen't work!
>>>>>>>>>>>>>>>>> the drivers doesn't load fine!
>>>>>>>>>>>>>>>>> ....
>>>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Date: Tue, 1 Dec 2009 07:10:24 -0600
>>>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>>>> CC: marvin.stodolsky@...; stephenpinker79@...;
>>>>>>>>>>>>>>>>>> discuss@...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> scanModem reports that your modem is supported via
>>>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> For candidate modem in: 00:1f.6
>>>>>>>>>>>>>>>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>>> Primary device ID: 8086:24c6
>>>>>>>>>>>>>>>>>> Subsystem PCI_id 1631:d005
>>>>>>>>>>>>>>>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink
>>>>>>>>>>>>>>>>>> type
>>>>>>>>>>>>>>>>>> from Archives:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> This is a NEW softmodem case! Please send the output
>>>>>>>>>>>>>>>>>> ModemData.txt
>>>>>>>>>>>>>>>>>> to DISCUSS@... to enrich the Archive and help others!
>>>>>>>>>>>>>>>>>> If further assistance is not needed, please use email Subject:
>>>>>>>>>>>>>>>>>> New Case Only
>>>>>>>>>>>>>>>>>> -------------------------------------------
>>>>>>>>>>>>>>>>>> Support type needed or chipset: slmodemd
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> An ALSA (Advanced Linux Sound Architecture) modem driver:
>>>>>>>>>>>>>>>>>> snd-intel8x0m
>>>>>>>>>>>>>>>>>> provides Low Level support enabling contact with the modem
>>>>>>>>>>>>>>>>>> hardware.
>>>>>>>>>>>>>>>>>> For all BUT Conexant chip soft modems (using hsfmodem software)
>>>>>>>>>>>>>>>>>> complementary High Level support is through a Smartlink
>>>>>>>>>>>>>>>>>> utility:
>>>>>>>>>>>>>>>>>> slmodemd
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Download from
>>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/
>>>>>>>>>>>>>>>>>> the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd.
>>>>>>>>>>>>>>>>>> Unpack
>>>>>>>>>>>>>>>>>> under Linux with:
>>>>>>>>>>>>>>>>>> $ tar zxf SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>>> and read instructions therein. But briefly, the modem is setup
>>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> command:
>>>>>>>>>>>>>>>>>> sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
>>>>>>>>>>>>>>>>>> reporting dynamic creation of ports:
>>>>>>>>>>>>>>>>>> /dev/ttySL0 --> /dev/pts/N , with N some number
>>>>>>>>>>>>>>>>>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for
>>>>>>>>>>>>>>>>>> follow
>>>>>>>>>>>>>>>>>> through guidance.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> If you have downloaded the package SLMODEMD.gcc4.4.tar.gz and
>>>>>>>>>>>>>>>>>> tried
>>>>>>>>>>>>>>>>>> the above instructions and are not getting anywhere/(modem does
>>>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>>>> respond) it could be because of
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> For candidate card in slot 00:1f.6, firmware information and
>>>>>>>>>>>>>>>>>> bootup
>>>>>>>>>>>>>>>>>> diagnostics are:
>>>>>>>>>>>>>>>>>> PCI slot PCI ID SubsystemID Name
>>>>>>>>>>>>>>>>>> ---------- --------- --------- --------------
>>>>>>>>>>>>>>>>>> 00:1f.6 8086:24c6 1631:d005 Modem: Intel Corporation
>>>>>>>>>>>>>>>>>> 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Modem interrupt assignment and sharing:
>>>>>>>>>>>>>>>>>> 5: 137 XT-PIC-XT yenta, Intel 82801DB-ICH4, Intel
>>>>>>>>>>>>>>>>>> 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
>>>>>>>>>>>>>>>>>> [ 0.071472] pci 0000:00:1f.6: reg 10 io port: [0xe300-0xe3ff]
>>>>>>>>>>>>>>>>>> [ 0.071480] pci 0000:00:1f.6: reg 14 io port: [0xe400-0xe47f]
>>>>>>>>>>>>>>>>>> [ 0.071521] pci 0000:00:1f.6: PME# supported from D0 D3hot
>>>>>>>>>>>>>>>>>> D3cold
>>>>>>>>>>>>>>>>>> [ 0.071525] pci 0000:00:1f.6: PME# disabled
>>>>>>>>>>>>>>>>>> [ 0.956536] serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI
>>>>>>>>>>>>>>>>>> 5
>>>>>>>>>>>>>>>>>> (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>>> [ 0.956547] serial 0000:00:1f.6: PCI INT B disabled
>>>>>>>>>>>>>>>>>> [ 3186.856643] Intel ICH Modem 0000:00:1f.6: PCI INT B ->
>>>>>>>>>>>>>>>>>> Link[LNKB]
>>>>>>>>>>>>>>>>>> -> GSI 5 (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>>> [ 3186.856669] Intel ICH Modem 0000:00:1f.6: setting latency
>>>>>>>>>>>>>>>>>> timer to
>>>>>>>>>>>>>>>>>> 64
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> The PCI slot 00:1f.6 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@...
>>>>>>>>>>>>>>>>>> if help is needed.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Let us know if the package SLMODEMD.gcc4.4.tar.gz works or not,
>>>>>>>>>>>>>>>>>> and if
>>>>>>>>>>>>>>>>>> the driver loads fine but does not respond, follow the above
>>>>>>>>>>>>>>>>>> instructions to see if it can work or not.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _________________________________________________________________
>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _________________________________________________________________
>>>>>>> I tuoi amici sempre a portata di clic, sul nuovo Web Messenger
>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>
>>>>>>
>>>>>
>>>
>>> _________________________________________________________________
>>> Scopri tuttele novità di Internet Explorer 8
>>> http://www.microsoft.com/italy/windows/internet-explorer/msn.aspx
>
> _________________________________________________________________
> 25 Gigabyte per le tue foto online
> http://www.windowslive.it/foto.aspx

Re: Larry, U.S.A. kernel 2.6.27-7-generic

2009-12-10T11:06:43Z

Larry,

Move between folders with the command
cd
for change directory. cd by itself returns you to your home folder.
cd Desktop
would move you to your Desktop from your home folder
If martian-full-20080625.tar.gz was unpacked in your home folder,
cd martian-full-20080625
will move your into that folder.
ls
will display the folder contents

make clean
make
will compile the drivers.

MarvS

On Thu, Dec 10, 2009 at 11:29 AM, Larry Hager <larrymeditates@...> wrote:

> I don't know how to execute a command within a folder. Can you tell me how to do this? Thanks!
>
> Larry
>
>
> --- On Tue, 12/8/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:
>
>> From: Marvin Stodolsky <marvin.stodolsky@...>
>> Subject: Re: Larry, U.S.A. kernel 2.6.27-7-generic
>> To: "Larry Hager" <larrymeditates@...>
>> Cc: discuss@...
>> Date: Tuesday, December 8, 2009, 4:06 PM
>> Larry
>>
>> Before doing the make commands, you must be in the
>> folder martian-full-20080625
>> Therein there will be shown by
>> $ ls
>> at least the files/ and/or folders/:
>> ChangeLog Cleaning.txt Concept
>> INSTALL kmodule Makefile
>> martian.h modem README
>> sample.txt scripts
>>
>> the "make something" commands must be executed in a folder
>> containg a
>> Makefile/makefile.
>>
>> MarvS
>>
>> >
>> > MarvS
>> >
>> > $ make clean
>>
>> On Tue, Dec 8, 2009 at 11:06 AM, Larry Hager <larrymeditates@...>
>> wrote:
>> > I tried entering the commands below and when I began
>> with $ make clean
>> > I got the message "No rule to make target 'clean' I
>> also tried cutting and pasting the commands as a whole but
>> with no success. What did I do wrong?
>> >
>> >
>> > Larry
>> >
>> >
>> > --- On Sun, 12/6/09, Marvin Stodolsky <marvin.stodolsky@...>
>> wrote:
>> >
>> >> From: Marvin Stodolsky <marvin.stodolsky@...>
>> >> Subject: Re: Larry, U.S.A. kernel
>> 2.6.27-7-generic
>> >> To: "Larry Hager" <larrymeditates@...>
>> >> Cc: discuss@...
>> >> Date: Sunday, December 6, 2009, 8:21 PM
>> >> Larry
>> >>
>> >> You must do the make commands within the folder
>> >> martian-full-20080625
>> >> per illustration below.
>> >>
>> >> MarvS
>> >>
>> >> $ make clean
>> >> make -C kmodule/ clean
>> >> make[1]: Entering directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> >> make -C /lib/modules/2.6.28-16-generic/build
>> >>
>> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
>> >> clean
>> >> make[2]: Entering directory
>> >> `/usr/src/linux-headers-2.6.28-16-generic'
>> >>
>> >>
>> CLEAN /usr/src/pkg/martian/martian-full-20080625/kmodule/.tmp_versions
>> >>
>> >>
>> CLEAN /usr/src/pkg/martian/martian-full-20080625/kmodule/Module.symvers
>> >> make[2]: Leaving directory
>> >> `/usr/src/linux-headers-2.6.28-16-generic'
>> >> make[1]: Leaving directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> >> make -C modem/ clean
>> >> make[1]: Entering directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> >> RM OBJS
>> >> RM BINS
>> >> RM TOOLS
>> >> make[1]: Leaving directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> >>
>> >> Thus having cleaned out any old file debris, do
>> the compile
>> >> with
>> >> $ make all
>> >> make -C kmodule/ modules
>> >> make[1]: Entering directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> >> make -C /lib/modules/2.6.28-16-generic/build
>> >>
>> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
>> >> modules
>> >> make[2]: Entering directory
>> >> `/usr/src/linux-headers-2.6.28-16-generic'
>> >> CC [M]
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.o
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:
>> >> In
>> >> function ‘martian_isr’:
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:131:
>> >> warning: value computed is not used
>> >> CC [M]
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.o
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:358:
>> >> warning: ‘mars_read_register_rem’ defined but
>> not used
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:371:
>> >> warning: ‘mars_write_register_rem’ defined but
>> not
>> >> used
>> >> CC [M]
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/mfifo.o
>> >> LD [M]
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.o
>> >> Building modules, stage 2.
>> >> MODPOST 1 modules
>> >> CC
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.mod.o
>> >> LD [M]
>> >>
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.ko
>> >> make[2]: Leaving directory
>> >> `/usr/src/linux-headers-2.6.28-16-generic'
>> >> make[1]: Leaving directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> >> make -C modem/ all
>> >> make[1]: Entering directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> >> CC main.o
>> >> CC dumpers.o
>> >> CC log.o
>> >> CC session.o
>> >> CC mport.o
>> >> CC pty.o
>> >> CC sysdep.o
>> >> CC isr.o
>> >> CC smp.o
>> >> CC core_if.o
>> >> CC coresubst.o
>> >> CC link.o
>> >> CC tweakrelocsdynamic.o
>> >> CC coreadd.o
>> >> CC elf386tweakrelocs
>> >> LD marscore.o
>> >> TWEAK marscore.o
>> >> LD martian_modem
>> >> make[1]: Leaving directory
>> >>
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> >>
>> >> Lastly do the installation of the products with
>> root/adm
>> >> authority:
>> >> $ sudo make install
>> >>
>> >> On Sun, Dec 6, 2009 at 4:43 PM, Larry Hager <larrymeditates@...>
>> >> wrote:
>> >> > I've installed the packages. I then checked
>> the
>> >> martian file "install" which suggests starting
>> with $ make
>> >> all
>> >> > I got the message: "No rule to make target
>> 'all'
>> >> .Stop. Is this the right step to take next?
>> What should
>> >> I do now?
>> >> >
>> >> > Take care,
>> >> >
>> >> > Larry
>> >> >
>> >> >
>> >> > --- On Wed, 12/2/09, Marvin Stodolsky <marvin.stodolsky@...>
>> >> wrote:
>> >> >
>> >> >> From: Marvin Stodolsky <marvin.stodolsky@...>
>> >> >> Subject: Re: Larry, U.S.A. kernel
>> >> 2.6.27-7-generic
>> >> >> To: "Larry Hager" <larrymeditates@...>
>> >> >> Cc: discuss@...
>> >> >> Date: Wednesday, December 2, 2009, 8:22
>> PM
>> >> >> Larry,
>> >> >>
>> >> >> The linux-libc-dev and libc6-dev must
>> be in
>> >> the
>> >> >> same folder, wherein
>> >> >> you execute
>> >> >> $ sudo dpkg -i lib*.deb
>> >> >> Your personal folder is OK.
>> >> >> The packages should be displayer by
>> >> >> $ ls *.deb
>> >> >> Note that $ is the command prompt, but
>> not part of
>> >> the
>> >> >> command: sudo
>> >> >> dpkg -i lib*.deb
>> >> >>
>> >> >> MarvS
>> >> >>
>> >> >> On Wed, Dec 2, 2009 at 11:12 PM, Larry
>> Hager
>> >> <larrymeditates@...>
>> >> >> wrote:
>> >> >> > I'm using Ubuntu 8.10 and trying to
>> set up a
>> >> modem and
>> >> >> was told to download packages:
>> linux-libc-dev and
>> >> libc6-dev.
>> >> >> I downloaded the files to my desktop
>> but when I
>> >> entered
>> >> >> the command $sudo dpkg -i lib*.deb I got
>> the
>> >> message: error
>> >> >> processing lib* (--install): cannot
>> access
>> >> archive: no such
>> >> >> file or directory. What am I doing
>> wrong?
>> >> >> >
>> >> >> > Thank you for your help!
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > Take care,
>> >> >> >
>> >> >> > Larry
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>

Re: Aleck, Kazakhstan kernel 2.6.24-19-generic

2009-12-10T10:58:57Z

Aleck,

From http://packages.ubuntu.com/hardy/linux-image-2.6.24-24-generic
you can start the download of a
2.6.24-24-generic kernel+modules package.
Also get the corresponding hsfmodem package for 2.6.24-24-generic.
After installing the new kernel and rebooting into it, install the
hsfmodem package.
That should suffice to get you online.

MarvS
scanModem maintainer

On Thu, Dec 10, 2009 at 9:07 AM, Aleck Mueller <aleckm@...> wrote:

> В сообщении от 10 декабря 2009 07:06 вы написали:
>> Your other option is to get a source based generic package:
>>
>> http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.05full/hs
>>fmodem_7.80.02.05full_i386.deb.zip
>
> Antonio,
>
> Thank you for your response.
>
> I think (based on what scanModem said) the chipset of my modem is Conexant
> chipset and the modem is hosted on High Definition Audio card. Am I right?
>
> I had bought this Dell notebook with factory Ubuntu installation and then
> re-installed Ubuntu 8.04.1 (newer version) from applied DVD (to re-build HDD
> partitions). Unfortunately, I have not burnt Dell DVD rescue disc from
> factory installation. Now I cannot get on to Internet from this notebook.
> (The seller's guarantee service cannot help: first, they sent me driver
> xxx.exe for Windows, and after my explanations it did not fit they sent
> sl-modem-daemon package which did not help, too; all that drove me to
> linmodems.org.) Looking for acceptable decision I have found out the
> following.
>
> Conexant.txt says:
> Dell is providing hsfmodem package for its PCs:
> http://linux.dell.com/files/ubuntu/modem-drivers/ .
> with the folder http://linux.dell.com/files/ubuntu/modem-drivers/hsf-custom/
> having the version 7.68 needed for your ALSA version 1.0.4
> hsfmodem-7.68.00.06tst1oem-1.i386.rpm 18-Jan-2008 16:24 1.4M
> hsfmodem-7.68.00.06tst1oem.tar.gz 18-Jan-2008 16:24 1.4M
> hsfmodem_7.68.00.06tst1oem-1_i386.deb 18-Jan-2008 16:24 1.3M
>
> But ModemData.txt says:
> The ALSA verion is 1.0.16
>
> And the folder
> http://linux.dell.com/files/ubuntu/modem-drivers/hsf-custom/
> does not exist but there is the folder
> http://linux.dell.com/files/ubuntu/hardy/modem-drivers/hsf/
>
> And there is not the package
> hsfmodem_7.68.00.06tst1oem-1_i386.deb
> there but there is the package
> hsfmodem_7.68.00.09oem_i386.deb
> I have tried the last but sound has broken :-( and I re-install Ubuntu.
>
> Conexant.txt also says:
> Jonathan <modem.support@...> provides support for Conexant chipset
> modems.
>
> But I continue to address myself to you trying to sort out my case; if that is
> against any rules I beg your pardon.
> --
> Best regards,
> Aleck
>
>

Re: Larry, U.S.A. kernel 2.6.27-7-generic

2009-12-10T08:29:43Z

I don't know how to execute a command within a folder. Can you tell me how to do this? Thanks!

Larry

--- On Tue, 12/8/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:

> From: Marvin Stodolsky <marvin.stodolsky@...>
> Subject: Re: Larry, U.S.A. kernel 2.6.27-7-generic
> To: "Larry Hager" <larrymeditates@...>
> Cc: discuss@...
> Date: Tuesday, December 8, 2009, 4:06 PM
> Larry
>
> Before doing the make commands, you must be in the
> folder martian-full-20080625
> Therein there will be shown by
> $ ls
> at least the files/ and/or folders/:
> ChangeLog Cleaning.txt Concept
> INSTALL kmodule Makefile
> martian.h modem README
> sample.txt scripts
>
> the "make something" commands must be executed in a folder
> containg a
> Makefile/makefile.
>
> MarvS
>
> >
> > MarvS
> >
> > $ make clean
>
> On Tue, Dec 8, 2009 at 11:06 AM, Larry Hager <larrymeditates@...>
> wrote:
> > I tried entering the commands below and when I began
> with $ make clean
> > I got the message "No rule to make target 'clean' I
> also tried cutting and pasting the commands as a whole but
> with no success. What did I do wrong?
> >
> >
> > Larry
> >
> >
> > --- On Sun, 12/6/09, Marvin Stodolsky <marvin.stodolsky@...>
> wrote:
> >
> >> From: Marvin Stodolsky <marvin.stodolsky@...>
> >> Subject: Re: Larry, U.S.A. kernel
> 2.6.27-7-generic
> >> To: "Larry Hager" <larrymeditates@...>
> >> Cc: discuss@...
> >> Date: Sunday, December 6, 2009, 8:21 PM
> >> Larry
> >>
> >> You must do the make commands within the folder
> >> martian-full-20080625
> >> per illustration below.
> >>
> >> MarvS
> >>
> >> $ make clean
> >> make -C kmodule/ clean
> >> make[1]: Entering directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
> >> make -C /lib/modules/2.6.28-16-generic/build
> >>
> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
> >> clean
> >> make[2]: Entering directory
> >> `/usr/src/linux-headers-2.6.28-16-generic'
> >>
> >>
> CLEAN /usr/src/pkg/martian/martian-full-20080625/kmodule/.tmp_versions
> >>
> >>
> CLEAN /usr/src/pkg/martian/martian-full-20080625/kmodule/Module.symvers
> >> make[2]: Leaving directory
> >> `/usr/src/linux-headers-2.6.28-16-generic'
> >> make[1]: Leaving directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
> >> make -C modem/ clean
> >> make[1]: Entering directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/modem'
> >> RM OBJS
> >> RM BINS
> >> RM TOOLS
> >> make[1]: Leaving directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/modem'
> >>
> >> Thus having cleaned out any old file debris, do
> the compile
> >> with
> >> $ make all
> >> make -C kmodule/ modules
> >> make[1]: Entering directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
> >> make -C /lib/modules/2.6.28-16-generic/build
> >>
> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
> >> modules
> >> make[2]: Entering directory
> >> `/usr/src/linux-headers-2.6.28-16-generic'
> >> CC [M]
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.o
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:
> >> In
> >> function ‘martian_isr’:
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:131:
> >> warning: value computed is not used
> >> CC [M]
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.o
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:358:
> >> warning: ‘mars_read_register_rem’ defined but
> not used
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:371:
> >> warning: ‘mars_write_register_rem’ defined but
> not
> >> used
> >> CC [M]
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/mfifo.o
> >> LD [M]
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.o
> >> Building modules, stage 2.
> >> MODPOST 1 modules
> >> CC
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.mod.o
> >> LD [M]
> >>
> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.ko
> >> make[2]: Leaving directory
> >> `/usr/src/linux-headers-2.6.28-16-generic'
> >> make[1]: Leaving directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
> >> make -C modem/ all
> >> make[1]: Entering directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/modem'
> >> CC main.o
> >> CC dumpers.o
> >> CC log.o
> >> CC session.o
> >> CC mport.o
> >> CC pty.o
> >> CC sysdep.o
> >> CC isr.o
> >> CC smp.o
> >> CC core_if.o
> >> CC coresubst.o
> >> CC link.o
> >> CC tweakrelocsdynamic.o
> >> CC coreadd.o
> >> CC elf386tweakrelocs
> >> LD marscore.o
> >> TWEAK marscore.o
> >> LD martian_modem
> >> make[1]: Leaving directory
> >>
> `/usr/src/pkg/martian/martian-full-20080625/modem'
> >>
> >> Lastly do the installation of the products with
> root/adm
> >> authority:
> >> $ sudo make install
> >>
> >> On Sun, Dec 6, 2009 at 4:43 PM, Larry Hager <larrymeditates@...>
> >> wrote:
> >> > I've installed the packages. I then checked
> the
> >> martian file "install" which suggests starting
> with $ make
> >> all
> >> > I got the message: "No rule to make target
> 'all'
> >> .Stop. Is this the right step to take next?
> What should
> >> I do now?
> >> >
> >> > Take care,
> >> >
> >> > Larry
> >> >
> >> >
> >> > --- On Wed, 12/2/09, Marvin Stodolsky <marvin.stodolsky@...>
> >> wrote:
> >> >
> >> >> From: Marvin Stodolsky <marvin.stodolsky@...>
> >> >> Subject: Re: Larry, U.S.A. kernel
> >> 2.6.27-7-generic
> >> >> To: "Larry Hager" <larrymeditates@...>
> >> >> Cc: discuss@...
> >> >> Date: Wednesday, December 2, 2009, 8:22
> PM
> >> >> Larry,
> >> >>
> >> >> The linux-libc-dev and libc6-dev must
> be in
> >> the
> >> >> same folder, wherein
> >> >> you execute
> >> >> $ sudo dpkg -i lib*.deb
> >> >> Your personal folder is OK.
> >> >> The packages should be displayer by
> >> >> $ ls *.deb
> >> >> Note that $ is the command prompt, but
> not part of
> >> the
> >> >> command: sudo
> >> >> dpkg -i lib*.deb
> >> >>
> >> >> MarvS
> >> >>
> >> >> On Wed, Dec 2, 2009 at 11:12 PM, Larry
> Hager
> >> <larrymeditates@...>
> >> >> wrote:
> >> >> > I'm using Ubuntu 8.10 and trying to
> set up a
> >> modem and
> >> >> was told to download packages:
> linux-libc-dev and
> >> libc6-dev.
> >> >> I downloaded the files to my desktop
> but when I
> >> entered
> >> >> the command $sudo dpkg -i lib*.deb I got
> the
> >> message: error
> >> >> processing lib* (--install): cannot
> access
> >> archive: no such
> >> >> file or directory. What am I doing
> wrong?
> >> >> >
> >> >> > Thank you for your help!
> >> >> >
> >> >> >
> >> >> >
> >> >> > Take care,
> >> >> >
> >> >> > Larry
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> >
>

help to me

2009-12-10T06:16:58Z

Only plain text email is forwarded by the Discuss@... List
Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.31-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@... 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.31-16-generic (buildd@rothera) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu8) ) #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009
scanModem update of: 2009_12_07

The dialer utility package WVDIAL does not appear to be installed on
your System.
For Ubuntu Jaunty users, there are at the bottom of
http://linmodems.technion.ac.il/packages/:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your
Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

The dkms driver upgrade utilities are installed,

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 0b05:620a ASUSTek Computer, Inc. Remote NDIS Device
ID 08ff:2810 AuthenTec, Inc.
ID 413c:8156 Dell Computer Corp.
ID 413c:8158 Dell Computer Corp.
ID 413c:8157 Dell Computer Corp.
ID 0a5c:4500 Broadcom Corp.
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@...

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 1028:0263 Audio device: Intel Corporation
82801I

Modem interrupt assignment and sharing:
21: 16838 15623 IO-APIC-fasteoi uhci_hcd:usb4,
uhci_hcd:usb7, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.364901] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf6afc000-0xf6afffff]
[ 0.364962] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.364966] pci 0000:00:1b.0: PME# disabled
[ 17.138742] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 21 (level, low)
-> IRQ 21
[ 17.138769] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 17.224177] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input10
[ 17.313641] input: HDA Intel Mic at Ext Right Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 17.313706] input: HDA Intel Line Out at Sep Left Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 17.313759] input: HDA Intel HP Out at Ext Right Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input13

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@...
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.20
The modem cards detected by "aplay -l" are: None

The /proc/asound/pcm file reports:
-----------------------
00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 2
00-01: STAC92xx Digital : STAC92xx Digital : playback 1
00-03: INTEL HDMI : INTEL HDMI : playback 1

about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf6afc000 irq 21

PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.31-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
The modem codec file for the HDA card is: /proc/asound/card0/codec#1
--------------------------------------------------------
Codec: Conexant ID 2c06
Address: 1
Function Id: 0x2
Vendor Id: 0x14f12c06
Subsystem Id: 0x14f1000f
Revision Id: 0x100000
Modem Function Group: 0x2

The audio card hosts a softmodem chip: 0x14f12c06

14f1 is the Conexant Vendor ID, and 0x14f12c06 a softmodem chipset.
Get a hsfmodem package through http://www.linuxant.com

If not a Conexant modem, the driver hsfmodem-drivers 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=1028:0263
IRQ=21
HDA=8086:293e
SOFT=8086:293e.HDA
HDAchipVendorID=14f1
CHIP=0x14f12c06
IDENT=hsfmodem
Driver=hsfmodem-drivers

For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801I
Primary device ID: 8086:293e
Subsystem PCI_id 1028:0263
Softmodem codec or chipset from diagnostics: 0x14f12c06
from Archives:
The HDA card softmodem chip is 0x14f12c06

Support type needed or chipset: hsfmodem

Writing DOCs/Intel.txt

For owners of a Dell PCs with Conexant HSF modems, a driver source
package with full speed enabled is available, but requires driver
compiling. Read DOCs/Conexant.txt

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.31_16_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.

The directions following below need only be pursued, if the above
procedures are not adequate.

Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to
find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the
FileName,
your KernelVersion: 2.6.31_16_generic
They can be found through
http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder
is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm
permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

Support for Conexant chips hosted on High Definition Audio cards may require
installation of additional packages, one of the alsa-driver-linuxant
packages
on http://www.linuxant.com/alsa-driver/ At the same time download the
alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the
hsfmodem install, there will be a message if there is necessary
installation of
alsa-driver-linuxant

The installation command for a .deb suffic packages is, with root/adm
permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

There may a message that "Dependencies" are not satisfied. In this case
the Ubuntu/Debian packages to be installed are linux-libc-dev &
libc6-dev. Package
names may be different for other Linuxes. If not on your install CD, these
packages can be searched for at http://packages.ubuntu.com. After download,
they can be coinstalled with:
sudo dpkg -i li*.deb
Again try the alsa-driver-linuxant

There may be a message that the patch must be applied. In this case get the
ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
Under Linux, this package is unpacked with:
$ tar jxf alsa*.tar.bz2
Next the patch is applied with:
$ patch -p0 < alsa-driver-1.0.17-1.patch

See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
for details on compiling and installing replacement snd-hda-intel + its
dependent drivers.
After the installation is completed, rerun the hsfmodem installation.
Reboot and try to detect the modem with Root permission:
sudo wvdialconf /etc/wvdial.conf

Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt

Completed candidate modem analyses.

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

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

Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.31-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 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 277352 2009-02-20 20:55 /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 eth1
usb0
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 --------

Re: Aleck, Kazakhstan kernel 2.6.24-19-generic

2009-12-10T06:07:23Z

В сообщении от 10 декабря 2009 07:06 вы написали:
> Your other option is to get a source based generic package:
>
> http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.05full/hs
>fmodem_7.80.02.05full_i386.deb.zip

Antonio,

Thank you for your response.

I think (based on what scanModem said) the chipset of my modem is Conexant
chipset and the modem is hosted on High Definition Audio card. Am I right?

I had bought this Dell notebook with factory Ubuntu installation and then
re-installed Ubuntu 8.04.1 (newer version) from applied DVD (to re-build HDD
partitions). Unfortunately, I have not burnt Dell DVD rescue disc from
factory installation. Now I cannot get on to Internet from this notebook.
(The seller's guarantee service cannot help: first, they sent me driver
xxx.exe for Windows, and after my explanations it did not fit they sent
sl-modem-daemon package which did not help, too; all that drove me to
linmodems.org.) Looking for acceptable decision I have found out the
following.

Conexant.txt says:
Dell is providing hsfmodem package for its PCs:
http://linux.dell.com/files/ubuntu/modem-drivers/ .
with the folder http://linux.dell.com/files/ubuntu/modem-drivers/hsf-custom/
having the version 7.68 needed for your ALSA version 1.0.4
hsfmodem-7.68.00.06tst1oem-1.i386.rpm 18-Jan-2008 16:24 1.4M
hsfmodem-7.68.00.06tst1oem.tar.gz 18-Jan-2008 16:24 1.4M
hsfmodem_7.68.00.06tst1oem-1_i386.deb 18-Jan-2008 16:24 1.3M

But ModemData.txt says:
The ALSA verion is 1.0.16

And the folder
http://linux.dell.com/files/ubuntu/modem-drivers/hsf-custom/
does not exist but there is the folder
http://linux.dell.com/files/ubuntu/hardy/modem-drivers/hsf/

And there is not the package
hsfmodem_7.68.00.06tst1oem-1_i386.deb
there but there is the package
hsfmodem_7.68.00.09oem_i386.deb
I have tried the last but sound has broken :-( and I re-install Ubuntu.

Conexant.txt also says:
Jonathan <modem.support@...> provides support for Conexant chipset
modems.

But I continue to address myself to you trying to sort out my case; if that is
against any rules I beg your pardon.
--
Best regards,
Aleck

RE: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic

2009-12-09T23:58:54Z

I did it but i stopped in your point 12).
Look at what i received...

==============
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./setup

Installing slmodemd helper to /usr/sbin/slmodemd

Writing log to slmodemd_Inst.txt
./setup: 14: slmodemd: not found
Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
Version verified:    2.9.11
Read the slmodemd_Inst.txt

There is already installed a slmodemd of version:    2.9.11
There is a file /usr/sbin/slmodemd
Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking for version 2.9.11
SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
Version verified:    2.9.11
Read the slmodemd_Inst.txt

mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe snd-intel8x0m
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo ./slmodemd
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo modprobe slamr
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo slmodemd --country=ITALY /dev/slamr0
error: mdm setup: cannot stat `/dev/slamr0': No such file or directory
error: cannot setup device `/dev/slamr0'

==============
And in an other window.....
==============

mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ wvdialconf /etc/wvdial.conf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0   S1   S2   S3

Sorry, no modem was detected! Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@...>.
mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
===============

Why it doesn't detect my modem?
Claudio.

----------------------------------------

> Date: Wed, 9 Dec 2009 12:51:33 -0500
> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
> From: marvin.stodolsky@...
> To: ermante@...
> CC: discuss@...
>
> Don't run "make", as the compile has already been done. Just do:
> $ sudo ./setup
>
> MarvS
>
> On Wed, Dec 9, 2009 at 5:33 AM, Claudio Mantegazza wrote:
>>
>> Marvin,Jacques, wait a minute....
>>
>> I did only a part which jacques told me...
>> i arrived to do all until jacques told me to continue to do what wrote in the README file at the installation but when i write the command in it i receice an error... Look at...
>>
>> =================
>> root@mantegazza-laptop:~# find / -iname SLMODEMD*
>> root@mantegazza-laptop:~# cd /home/mantegazza/Scaricati
>> root@mantegazza-laptop:/home/mantegazza/Scaricati# tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>> root@mantegazza-laptop:/home/mantegazza/Scaricati# cd SLMODEMD_gcc4.4_alsa1.0.21
>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# exit
>> exit
>> mantegazza@mantegazza-laptop:~$ cd /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ make
>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo su
>> [sudo] password for mantegazza:
>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make
>> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make install
>> make: *** Nessuna regola per creare l'obiettivo «install». Arresto.
>> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21#
>> ===================
>>
>> So what i have to do before continue?
>>
>> Claudio.
>>
>>
>>
>> ----------------------------------------
>>> Date: Sat, 5 Dec 2009 16:37:08 -0500
>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>>> From: marvin.stodolsky@...
>>> To: discuss@...
>>> CC: ermante@...
>>>
>>> Claudio
>>>
>>> You are missing a file with the contents below.
>>> Make a file with these contents, but replacing:
>>> DialUpNumber
>>> YourLoginName
>>> YourPassword
>>> This file should be named wvdial.conf, and can initially be in your home folder.
>>> Then after the
>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>> open a 2nd console and do:
>>> $ sudo wvdial -config=wvdial.conf
>>>
>>> MarvS
>>>
>>> [Dialer Defaults]
>>> Phone = DialUpNumber
>>> Username = YourLoginName
>>> Password = YourPassword
>>> Init1 = ATZ
>>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
>>> Modem Type = Analog Modem
>>> ISDN = 0
>>> New PPPD = yes
>>> Modem = /dev/ttySL0
>>> Carrier Check = no
>>> Baud = 460800
>>>
>>> On Fri, Dec 4, 2009 at 9:40 PM, Marvin Stodolsky
>>> wrote:
>>>> The modem activation command should be:
>>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>>> there should be reported creation of a port:
>>>> /dev/ttySL0 --> /dev/pts/N , N some number
>>>>
>>>> Only after such a success should one try;
>>>> $ sudo wvdial
>>>>
>>>> MarvS
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Dec 4, 2009 at 8:06 AM, Jacques Goldberg
>>>> wrote:
>>>>> Claudio,
>>>>>
>>>>>
>>>>> I believe that you have reached such a mess level that it has become
>>>>> impossible to know which is what.
>>>>>
>>>>> Here is what I would do in your place:
>>>>>
>>>>> Because you used two versions of file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz ,
>>>>>
>>>>> 1-be root or sudo before any command
>>>>>
>>>>> 2-go into directory /usr/sbin
>>>>> 3-in that directory give command rm slmodemd*
>>>>>
>>>>> Make ABSOLUTELY SURE that you write slmodemd* so that there is NOTHING, NO
>>>>> SPACE, NOTHING ELSE, between slmodemd and the * . ABSOLUTELY SURE.
>>>>>
>>>>> Answer yes everytime you are prompted to erase a file with name starting
>>>>> with slmodemd and NO in any other case.
>>>>>
>>>>> 4-go into directory named SLMODEMD_gcc4.4_alsa1.0.21
>>>>>
>>>>> 5-in that directory give command make uninstall
>>>>>
>>>>> 6-give the command cd
>>>>>
>>>>> 7-give the command find / -iname SLMODEMD* .Attention
>>>>> SLMODEMD in capital case.
>>>>>
>>>>> This will give a list of all the files in your computer with a name
>>>>> starting with SLMODEMD
>>>>>
>>>>> Erase all these files one at a time. To erase a file the command is rm ;
>>>>> to erase an empty directory the command is rmdir; to erase a directory which
>>>>> is not empty the command is rm -rf
>>>>> Always start with rm and then try rmdir and then rm -rf if the
>>>>> preceeding one is not accepted.
>>>>>
>>>>> 8-Now, in your usual directory, the one where you usually login, download
>>>>> the file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>
>>>>> Do not try to use one which has been downloaded before unless you are
>>>>> ABSOLUTELY sure that this is the one which I
>>>>>
>>>>> placed this morning.
>>>>>
>>>>> 9-Give the command tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>
>>>>> 10-Change directory with command cd SLMODEMD_gcc4.4_alsa1.0.21
>>>>>
>>>>> 11-Do exactly, one time and one time only, what Marv has written to you to
>>>>> do or what is written in file README in the directory where you are starting
>>>>> from point 4 in INSTALLATION
>>>>>
>>>>> 12-After you have given the command slmodemd and it has succeeded, in
>>>>> an other window give the command
>>>>>
>>>>> wvdialconf /etc/wvdial.conf (no . in wvdialconf and a , in
>>>>> /etc/wvdial.conf
>>>>>
>>>>> wvdialconf will find your modem
>>>>>
>>>>> Edit /etc/wvdial.conf as explained in
>>>>> http://linmodems.technion.ac.il/wvdial.html . Remember that you need
>>>>>
>>>>> Carrier Check = no
>>>>>
>>>>> 13- When the file /etc/wvdial.conf has been edited and saved, in that window
>>>>> or any window except the one used for slmodemd, the command wvdial
>>>>> should start your modem.
>>>>>
>>>>> when everything works well wvdial does NOT exit but stays doing nothing.
>>>>>
>>>>> Use your browser (like Firefox) and try to surf.
>>>>>
>>>>>
>>>>> Please remember: every time you do something else than what we tell you to
>>>>> do, like installing several slmodemd , you take the risk to create the
>>>>> conditions for failure.
>>>>>
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>>>>> Claudio Mantegazza wrote:
>>>>>
>>>>>> I downloaded again the new file.
>>>>>> i saw that there was updated 1 hour ago...
>>>>>> and in a new window (not the same about the
>>>>>> =======================
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ wvdial
>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ cd
>>>>>> /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ ls
>>>>>> 1st_Read.txt COPYING Files.txt setup slmodemd
>>>>>> slmodemd.txt Testing.txt wvdial.conf
>>>>>> Changes CountryList.txt README Slmodem-ALSA.txt
>>>>>> slmodemd_Inst.txt slmodem.txt Unload.txt
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo
>>>>>> ./setup
>>>>>> [sudo] password for mantegazza:
>>>>>> Installing slmodemd helper to /usr/sbin/slmodemd
>>>>>>
>>>>>> Writing log to slmodemd_Inst.txt
>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>> There is a file /usr/sbin/slmodemd
>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>> for version 2.9.11
>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>> Version verified: 2.9.11
>>>>>> Read the slmodemd_Inst.txt
>>>>>>
>>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>>> There is a file /usr/sbin/slmodemd
>>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>>> for version 2.9.11
>>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>>> Version verified: 2.9.11
>>>>>> Read the slmodemd_Inst.txt
>>>>>>
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>> wvdial
>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>> =======================
>>>>>>
>>>>>> but if in this windows i write the slmodem command:
>>>>>>
>>>>>> ======================
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>> slmodemd --alsa -c YOUR_COUNTRY modem:1 error: mixer setup: attach hw:1
>>>>>> error: No such file or directory
>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid argument
>>>>>> error: cannot setup device `modem:1'
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>>> ======================
>>>>>>
>>>>>> I receive this error....
>>>>>>
>>>>>> and if i return in the other folder and i write...
>>>>>>
>>>>>> ================
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ cd
>>>>>> /home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem
>>>>>> mantegazza@mantegazza-laptop:~/Scaricati/slmodem-2.9.11-20090222/modem$
>>>>>> sudo su
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> wvdial
>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> slmodemd -c ITALY modem:1
>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>> error: cannot setup device `modem:1'
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> make SUPPORT_ALSA=1
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> slmodemd -c ITALY modem:1
>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>> error: cannot setup device `modem:1'
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> cp slmodemd /usr/sbin
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> slmodemd -c ITALY modem:1
>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>> error: cannot setup device `modem:1'
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> ================
>>>>>>
>>>>>> Have you got other ideas?
>>>>>>
>>>>>> Claudio.
>>>>>>
>>>>>>
>>>>>>
>>>>>> ----------------------------------------
>>>>>>
>>>>>>>
>>>>>>> Date: Fri, 4 Dec 2009 11:17:52 +0200
>>>>>>> From: Jacques.Goldberg@...
>>>>>>> To: ermante@...
>>>>>>> CC: olivares14031@...; discuss@...;
>>>>>>> marvin.stodolsky@...
>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel
>>>>>>> 2.6.31-15-generic
>>>>>>>
>>>>>>> Claudio,
>>>>>>>
>>>>>>> Did you download the file again today within about one hour back from
>>>>>>> now?
>>>>>>>
>>>>>>> I ask because this would then be after I installed the file with alsa
>>>>>>> stuff included.
>>>>>>>
>>>>>>>
>>>>>>> Now, reading your report, I have a question about:
>>>>>>>
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> wvdial
>>>>>>>
>>>>>>> Did you give the wvdial command in the same window where you had given
>>>>>>> before the command slmodemd?
>>>>>>>
>>>>>>> If yes, then to give wvdial you must have stopped slmodemd with CTRL-C
>>>>>>> which would explain why wvdial did not find the file /dev/ttySL0 : this
>>>>>>> file exists ONLY while slmodemd is running.
>>>>>>>
>>>>>>> If my guess is correct, then remember to ALWAYS start wvdial IN AN OTHER
>>>>>>> FREE WINDOW, not the one where slmodemd runs.
>>>>>>>
>>>>>>>
>>>>>>> Jacques
>>>>>>>
>>>>>>>
>>>>>>> Claudio Mantegazza wrote:
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> I made again the command you told me and in this time i didn't receive
>>>>>>>> any errors....
>>>>>>>> Look at the command i wrote:
>>>>>>>>
>>>>>>>> =========================
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> lsdp_dummy.c Makefile modem_comp.c modem_defs.h modem_main.o modem_test
>>>>>>>> sysdep_common.c
>>>>>>>> dp_dummy.o Makefile.20080401 modem_comp.o modem_dp.h modem.o
>>>>>>>> modem_test.c sysdep_common.o
>>>>>>>> dp_sinus.c modem_at.c modem_datafile.c modem_ec.c modem_pack.c
>>>>>>>> modem_test.o
>>>>>>>> dp_sinus.o modem_at.o modem_datafile.o modem_ec.o modem_pack.o
>>>>>>>> modem_timer.c
>>>>>>>> dsplibs.o modem.c modem_debug.c modem.h modem_param.c modem_timer.h
>>>>>>>> homolog_data.c modem_cmdline.c modem_debug.h modem_homolog.h
>>>>>>>> modem_param.h modem_timer.o
>>>>>>>> homolog_data.o modem_cmdline.o modem_debug.o modem_main.c modem_param.o
>>>>>>>> slmodemd
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> modprobe snd-intel8x0m
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> aplay -l
>>>>>>>> **** Lista di PLAYBACK dispositivi hardware ****
>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 0: Intel ICH
>>>>>>>> [Intel 82801DB-ICH4]
>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 4: Intel ICH -
>>>>>>>> IEC958 [Intel 82801DB-ICH4 - IEC958]
>>>>>>>> Sottoperiferiche: 1/1
>>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>
>>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>>> wvdial
>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>
>>>>>>>> =========================
>>>>>>>>
>>>>>>>> But i cannot be able to connect....
>>>>>>>>
>>>>>>>> Claudio.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Date: Thu, 3 Dec 2009 14:14:59 -0600
>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>> From: olivares14031@...
>>>>>>>>> To: ermante@...
>>>>>>>>> CC: discuss@...; marvin.stodolsky@...
>>>>>>>>>
>>>>>>>>> Claudio,
>>>>>>>>>
>>>>>>>>> What happens when you try
>>>>>>>>> $ sudo slmodemd --alsa -c ITALY modem:1
>>>>>>>>>
>>>>>>>>> and try from the recently compiled slmodemd in
>>>>>>>>> slmodem-2.9.11-20090222/modem folder?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Antonio
>>>>>>>>>
>>>>>>>>> On Thu, Dec 3, 2009 at 8:01 AM, Claudio Mantegazza wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Antonio,
>>>>>>>>>> i'm very sorry but it didn't run...
>>>>>>>>>>
>>>>>>>>>> i made all that you told me but at the last command:
>>>>>>>>>>
>>>>>>>>>> =========
>>>>>>>>>> # make SUPPORT_ALSA=1
>>>>>>>>>> rebuild profile...
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_main.o -c modem_main.c
>>>>>>>>>> modem_main.c: In function ‘setup_stream’:
>>>>>>>>>> modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is
>>>>>>>>>> deprecated (declared at /usr/include/alsa/pcm.h:1116)
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_cmdline.o -c modem_cmdline.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o
>>>>>>>>>> -c modem.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_datafile.o -c modem_datafile.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_at.o -c modem_at.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_timer.o -c modem_timer.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_pack.o -c modem_pack.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_ec.o -c modem_ec.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_comp.o -c modem_comp.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_param.o -c modem_param.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_debug.o -c modem_debug.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> homolog_data.o -c homolog_data.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> dp_sinus.o -c dp_sinus.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> dp_dummy.o -c dp_dummy.c
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> sysdep_common.o -c sysdep_common.c
>>>>>>>>>> gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o
>>>>>>>>>> modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o
>>>>>>>>>> modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
>>>>>>>>>> /usr/lib/libasound.so
>>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>>> modem_test.o -c modem_test.c
>>>>>>>>>> modem_test.c: In function ‘modem_test_start’:
>>>>>>>>>> modem_test.c:110: warning: ignoring return value of ‘write’, declared
>>>>>>>>>> with attribute warn_unused_result
>>>>>>>>>> gcc -o modem_test modem_test.o modem_cmdline.o modem.o
>>>>>>>>>> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
>>>>>>>>>> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
>>>>>>>>>> dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> =========
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>>
>>>>>>>>>> =========
>>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>> =========
>>>>>>>>>> # wvdial
>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>> =========
>>>>>>>>>>
>>>>>>>>>> it seems not like it...
>>>>>>>>>>
>>>>>>>>>> And now?
>>>>>>>>>> what can i do?
>>>>>>>>>>
>>>>>>>>>> Claudio.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ...............................................................................................................
>>>>>>>>>>
>>>>>>>>>> ----------------------------------------
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Date: Thu, 3 Dec 2009 07:11:57 -0600
>>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>> To: ermante@...
>>>>>>>>>>> CC: marvin.stodolsky@...; jacques.goldberg@...
>>>>>>>>>>>
>>>>>>>>>>> Claudio,
>>>>>>>>>>>
>>>>>>>>>>> If you want to build SLMODEMD on your own for your system, Please do
>>>>>>>>>>> the following:
>>>>>>>>>>>
>>>>>>>>>>> Download:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>> Copy it to your linux partition/working directory, untar it with
>>>>>>>>>>> $ tar -zxvf slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>>> $ cd slmodem-2.9.11-20090222
>>>>>>>>>>> $ cd modem
>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>>
>>>>>>>>>>> as show in README
>>>>>>>>>>>
>>>>>>>>>>> ====================
>>>>>>>>>>> 3. Build application 'slmodemd' with ALSA support. For this in
>>>>>>>>>>> slmodem-2.9.x dir:
>>>>>>>>>>>
>>>>>>>>>>> $ cd modem
>>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>> ====================
>>>>>>>>>>>
>>>>>>>>>>> After this is successfull, then there will be a slmodemd file in that
>>>>>>>>>>> directory, copy it over to /usr/sbin
>>>>>>>>>>>
>>>>>>>>>>> and try the
>>>>>>>>>>> $ sudo slmodemd -c ITALY modem:1
>>>>>>>>>>>
>>>>>>>>>>> command again and hopefully it works this time around.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Antonio
>>>>>>>>>>>
>>>>>>>>>>> PS.
>>>>>>>>>>> I hope that the "NO CARRIER" error shows up like it did for me with
>>>>>>>>>>> 2.6.31.X kernels but slamr module.
>>>>>>>>>>>
>>>>>>>>>>> On 12/3/09, Claudio Mantegazza wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I untar the new one you sent me.
>>>>>>>>>>>> i exec the command:
>>>>>>>>>>>>
>>>>>>>>>>>> ===============
>>>>>>>>>>>> # ./slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>>> ALSA support is not compiled in (see README for howto).
>>>>>>>>>>>> ===============
>>>>>>>>>>>>
>>>>>>>>>>>> Now. how can i compile the ALSA support?
>>>>>>>>>>>>
>>>>>>>>>>>> P.s. i just installed the package libasound2-dev
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 14:18:11 -0500
>>>>>>>>>>>>> Subject: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>>> kernel
>>>>>>>>>>>>> 2.6.31-15-generic
>>>>>>>>>>>>> From: marvin.stodolsky@...
>>>>>>>>>>>>> To: ermante@...; Jacques.Goldberg@...;
>>>>>>>>>>>>> olivares14031@...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Used the attached SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jacques
>>>>>>>>>>>>> for the smartlink/ folder
>>>>>>>>>>>>>
>>>>>>>>>>>>> MarvS
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Dec 2, 2009 at 8:52 AM, Claudio Mantegazza wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> because i didn't find which u told me... and this one is the last
>>>>>>>>>>>>>> one...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>> Not Found
>>>>>>>>>>>>>> The requested URL /packages/smartlink/SLMODEMD.gcc4.4.tar.gz was
>>>>>>>>>>>>>> not
>>>>>>>>>>>>>> found on this server.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Apache/2.0.52 (Red Hat) Server at linmodems.technion.ac.il Port 80
>>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Maybe i don't understand something?
>>>>>>>>>>>>>> Can you tell me better where i can download the right file,
>>>>>>>>>>>>>> please?
>>>>>>>>>>>>>> give me the correct link....
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 07:15:13 -0600
>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>> CC: discuss@...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid
>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> why did you get the SLMODEMD_gcc4.4_alsa1.0.18.tar.gz?
>>>>>>>>>>>>>>> If your alsa verion is 1.0.20?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are:
>>>>>>>>>>>>>>> scheda 1: Modem [Intel 82801DB-ICH4 Modem], dispositivo 0: Intel
>>>>>>>>>>>>>>> ICH -
>>>>>>>>>>>>>>> Modem [Intel 82801DB-ICH4 Modem - Modem]
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem :
>>>>>>>>>>>>>>> playback
>>>>>>>>>>>>>>> 1 : capture 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>>> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
>>>>>>>>>>>>>>> Intel 82801DB-ICH4 Modem at irq 5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If you have downloaded the recommended SLMODEMD: the package
>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Does the same thing happen?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 12/2/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1':
>>>>>>>>>>>>>>>> Invalid
>>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>> mant@mant-laptop:~/Scaricati$ wvdial
>>>>>>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>>> It doen't work!
>>>>>>>>>>>>>>>> the drivers doesn't load fine!
>>>>>>>>>>>>>>>> ....
>>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Date: Tue, 1 Dec 2009 07:10:24 -0600
>>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>>> CC: marvin.stodolsky@...; stephenpinker79@...;
>>>>>>>>>>>>>>>>> discuss@...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> scanModem reports that your modem is supported via
>>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> For candidate modem in: 00:1f.6
>>>>>>>>>>>>>>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>> Primary device ID: 8086:24c6
>>>>>>>>>>>>>>>>> Subsystem PCI_id 1631:d005
>>>>>>>>>>>>>>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink
>>>>>>>>>>>>>>>>> type
>>>>>>>>>>>>>>>>> from Archives:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This is a NEW softmodem case! Please send the output
>>>>>>>>>>>>>>>>> ModemData.txt
>>>>>>>>>>>>>>>>> to DISCUSS@... to enrich the Archive and help others!
>>>>>>>>>>>>>>>>> If further assistance is not needed, please use email Subject:
>>>>>>>>>>>>>>>>> New Case Only
>>>>>>>>>>>>>>>>> -------------------------------------------
>>>>>>>>>>>>>>>>> Support type needed or chipset: slmodemd
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> An ALSA (Advanced Linux Sound Architecture) modem driver:
>>>>>>>>>>>>>>>>> snd-intel8x0m
>>>>>>>>>>>>>>>>> provides Low Level support enabling contact with the modem
>>>>>>>>>>>>>>>>> hardware.
>>>>>>>>>>>>>>>>> For all BUT Conexant chip soft modems (using hsfmodem software)
>>>>>>>>>>>>>>>>> complementary High Level support is through a Smartlink
>>>>>>>>>>>>>>>>> utility:
>>>>>>>>>>>>>>>>> slmodemd
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Download from
>>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/
>>>>>>>>>>>>>>>>> the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd.
>>>>>>>>>>>>>>>>> Unpack
>>>>>>>>>>>>>>>>> under Linux with:
>>>>>>>>>>>>>>>>> $ tar zxf SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>>> and read instructions therein. But briefly, the modem is setup
>>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>> command:
>>>>>>>>>>>>>>>>> sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
>>>>>>>>>>>>>>>>> reporting dynamic creation of ports:
>>>>>>>>>>>>>>>>> /dev/ttySL0 --> /dev/pts/N , with N some number
>>>>>>>>>>>>>>>>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for
>>>>>>>>>>>>>>>>> follow
>>>>>>>>>>>>>>>>> through guidance.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> If you have downloaded the package SLMODEMD.gcc4.4.tar.gz and
>>>>>>>>>>>>>>>>> tried
>>>>>>>>>>>>>>>>> the above instructions and are not getting anywhere/(modem does
>>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>>> respond) it could be because of
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> For candidate card in slot 00:1f.6, firmware information and
>>>>>>>>>>>>>>>>> bootup
>>>>>>>>>>>>>>>>> diagnostics are:
>>>>>>>>>>>>>>>>> PCI slot PCI ID SubsystemID Name
>>>>>>>>>>>>>>>>> ---------- --------- --------- --------------
>>>>>>>>>>>>>>>>> 00:1f.6 8086:24c6 1631:d005 Modem: Intel Corporation
>>>>>>>>>>>>>>>>> 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Modem interrupt assignment and sharing:
>>>>>>>>>>>>>>>>> 5: 137 XT-PIC-XT yenta, Intel 82801DB-ICH4, Intel
>>>>>>>>>>>>>>>>> 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
>>>>>>>>>>>>>>>>> [ 0.071472] pci 0000:00:1f.6: reg 10 io port: [0xe300-0xe3ff]
>>>>>>>>>>>>>>>>> [ 0.071480] pci 0000:00:1f.6: reg 14 io port: [0xe400-0xe47f]
>>>>>>>>>>>>>>>>> [ 0.071521] pci 0000:00:1f.6: PME# supported from D0 D3hot
>>>>>>>>>>>>>>>>> D3cold
>>>>>>>>>>>>>>>>> [ 0.071525] pci 0000:00:1f.6: PME# disabled
>>>>>>>>>>>>>>>>> [ 0.956536] serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI
>>>>>>>>>>>>>>>>> 5
>>>>>>>>>>>>>>>>> (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>> [ 0.956547] serial 0000:00:1f.6: PCI INT B disabled
>>>>>>>>>>>>>>>>> [ 3186.856643] Intel ICH Modem 0000:00:1f.6: PCI INT B ->
>>>>>>>>>>>>>>>>> Link[LNKB]
>>>>>>>>>>>>>>>>> -> GSI 5 (level, low) -> IRQ 5
>>>>>>>>>>>>>>>>> [ 3186.856669] Intel ICH Modem 0000:00:1f.6: setting latency
>>>>>>>>>>>>>>>>> timer to
>>>>>>>>>>>>>>>>> 64
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The PCI slot 00:1f.6 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@...
>>>>>>>>>>>>>>>>> if help is needed.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Let us know if the package SLMODEMD.gcc4.4.tar.gz works or not,
>>>>>>>>>>>>>>>>> and if
>>>>>>>>>>>>>>>>> the driver loads fine but does not respond, follow the above
>>>>>>>>>>>>>>>>> instructions to see if it can work or not.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _________________________________________________________________
>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>> _________________________________________________________________
>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> _________________________________________________________________
>>>>>> I tuoi amici sempre a portata di clic, sul nuovo Web Messenger
>>>>>> http://www.windowslive.it/foto.aspx
>>>>>
>>>>>
>>>>
>>
>> _________________________________________________________________
>> Scopri tuttele novità di Internet Explorer 8
>> http://www.microsoft.com/italy/windows/internet-explorer/msn.aspx

_________________________________________________________________
25 Gigabyte per le tue foto online
http://www.windowslive.it/foto.aspx

Re: Navin, Thailand Linux Mint 8 Helena - Main Edition kernel 2.6.31-14-generic

2009-12-09T21:44:03Z

Navin

From the PCI bus data, your System seems to be an older type.
To detect a serial port modem, try running:
$ sudo wvdialconf

Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems

If the above tests fail, please provide any independent information
available on your modem.
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. From the Driver Details TAB, copy out the
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

MarvS

On Wed, Dec 9, 2009 at 10:03 PM, navin kingkaew <navinking2000@...> wrote:

> Only plain text email is forwarded by the Discuss@...
> List Server,
> as HTML can contain viruses. Use as the email Subject Line:
> YourName, YourCountry Linux Mint 8 Helena - Main Edition
> kernel 2.6.31-14-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@... 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 Mint 8 Helena - Main Edition
> Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1
> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
> scanModem update of: 2009_11_26
>
>
> The dkms driver upgrade utilities are installed,
>
> There are no blacklisted modem drivers in /etc/modprobe* files
>
> Potentially useful modem drivers now loaded are:
>
> If a USB modem or cellphone is attached and was not detected, please
> provide available information in your request to discuss@...
>
> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>
> A candidate modem is not evident among the PCI devices:
> ------------------------------------------------
> 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
> 00:10.0 Multimedia audio controller: Ensoniq 5880B [AudioPCI] (rev 04)
> 01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2
> MX/MX 400] (rev b2)
> ------------------------------------------------
> with USB and bridge devices not displayed.
>
> If your modem is connected by an external serial cable,
> or mounted internally on an ISA card, scanModem would not access it.
> Try with Root permission
> $ wvdialconf /etc/wvdial.conf
> to detect these modem types and some USB modems.
> If the detection is successful, read the DOCs/wvdial.txt .
> Edit the /etc/wvdial.conf with Root permission:
> gedit /etc/wvdial.conf
> will be able to dial out with Root permission:
> wvdial
>
> Many modems for which scanModem fails have Conexant chips.
> From http://www.linuxant.com/drivers/modemident.php
> get the ListModem tool, which will report on Conexant chipset modems
>
> If the above tests fail, please provide any independent information
> available on your modem.
> 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. From the Driver Details TAB, copy out the
> 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.
>
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.4.1
> and the compiler used in kernel assembly: 4.4.1
>
>
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.4
> linuc_headers base folder /lib/modules/2.6.31-14-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.
>
>
>
> For Debian and some related distributions, a package
> kernel-kbuild-2.6-31 may be needed to support driver compiling.
>
>
> 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 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
>
>
> 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 --------
>

Navin, Thailand Linux Mint 8 Helena - Main Edition kernel 2.6.31-14-generic

2009-12-09T19:03:38Z

Only plain text email is forwarded by the Discuss@...
List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry Linux Mint 8 Helena - Main Edition
kernel 2.6.31-14-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@... 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 Mint 8 Helena - Main Edition
Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
scanModem update of: 2009_11_26

The dkms driver upgrade utilities are installed,

There are no blacklisted modem drivers in /etc/modprobe* files

Potentially useful modem drivers now loaded are:

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@...

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

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:10.0 Multimedia audio controller: Ensoniq 5880B [AudioPCI] (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2
MX/MX 400] (rev b2)
------------------------------------------------
with USB and bridge devices not displayed.

If your modem is connected by an external serial cable,
or mounted internally on an ISA card, scanModem would not access it.
Try with Root permission
$ wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
gedit /etc/wvdial.conf
will be able to dial out with Root permission:
wvdial

Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems

If the above tests fail, please provide any independent information
available on your modem.
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. From the Driver Details TAB, copy out the
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.

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

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

Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.31-14-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.

For Debian and some related distributions, a package
kernel-kbuild-2.6-31 may be needed to support driver compiling.

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 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

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 --------

Re: Aleck, Kazakhstan kernel 2.6.24-19-generic

2009-12-09T17:06:18Z

Aleck,

You are absolutely right. There is no such package there :(

There are only for -16 kernels and others.

2.6.24-26-generic *
hsfmodem_7.80.02.05full_k2.6.24_26_generic_ubuntu_i386.deb.zip 1.3M
da3602d40d1be28a82d989b8675e6afc
2.6.24-26-386 *
hsfmodem_7.80.02.05full_k2.6.24_26_386_ubuntu_i386.deb.zip 1.3M
ee2676443c5f74b0a0e6d4f2d0d51650
2.6.24-26-server *
hsfmodem_7.80.02.05full_k2.6.24_26_server_ubuntu_i386.deb.zip 1.3M
47d5d11213fb61cd808278eda62e07f7
2.6.24-25-generic *
hsfmodem_7.80.02.05full_k2.6.24_25_generic_ubuntu_i386.deb.zip 1.3M
e7b55c5dd11d62992eeb1e3f90d1bee6
2.6.24-25-386 *
hsfmodem_7.80.02.05full_k2.6.24_25_386_ubuntu_i386.deb.zip 1.3M
fbe7893a5a917ff3defc9e467af65534
2.6.24-25-server *
hsfmodem_7.80.02.05full_k2.6.24_25_server_ubuntu_i386.deb.zip 1.3M
4609e1ba793e347cf37f0e0d2cbdf242
2.6.24-24-generic *
hsfmodem_7.80.02.05full_k2.6.24_24_generic_ubuntu_i386.deb.zip 1.3M
738d381940710917ee3c2557ae0b5288
2.6.24-24-386 *
hsfmodem_7.80.02.05full_k2.6.24_24_386_ubuntu_i386.deb.zip 1.3M
c7dd0a0fac39896a4d437f11ac5c3cfd
2.6.24-24-server *
hsfmodem_7.80.02.05full_k2.6.24_24_server_ubuntu_i386.deb.zip 1.3M
f129a7ef235bcd13b4d4e9522bf3a6e5
2.6.24-16-generic *
hsfmodem_7.80.02.05full_k2.6.24_16_generic_ubuntu_i386.deb.zip 1.3M
d37dd0d8cc1f12277ff99ec1c24e95a3
2.6.24-16-386 *
hsfmodem_7.80.02.05full_k2.6.24_16_386_ubuntu_i386.deb.zip 1.3M
ae4757338c125f8dad3ddfbc2ef60749
2.6.24-16-server *
hsfmodem_7.80.02.05full_k2.6.24_16_server_ubuntu_i386.deb.zip 1.3M
aaec8b0e16ba4f827b4982439d61a2a1
2.6.22-16-generic
hsfmodem_7.80.02.05full_k2.6.22_16_generic_ubuntu_i386.deb.zip

Please choose only the package matching exactly your system's kernel
version below.

You can determine your kernel version with the following
case-sensitive shell command:

uname -r
If your exact kernel version is not listed, we recommend that you
upgrade to the latest available kernel for your distribution. If you
are using a special enterprise/secure/SMP or custom (self-compiled)
kernel, or the package does not work, you can try one of the generic
packages with source instead.

Your other option is to get a source based generic package:

http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.05full/hsfmodem_7.80.02.05full_i386.deb.zip

Regards,

Antonio

On 12/9/09, Aleck Mueller <aleckm@...> wrote:

> Computer: notebook Dell Vostro A860
> OS: fresh-installed from the attached to the computer Ubuntu 8.04 LTS DVD.
>
> ModemData.txt says:
> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
> download hsfmodem-7.80.02.05full_k2.6.24_19_generic_ubuntu_i386.deb.zip
>
> But there are not file
> hsfmodem-7.80.02.05full_k2.6.24_19_generic_ubuntu_i386.deb.zip there.
>
> What should I do?
> --
> Best regards,
> Aleck
>

Aleck, Kazakhstan kernel 2.6.24-19-generic

2009-12-09T14:27:41Z

Computer: notebook Dell Vostro A860
OS: fresh-installed from the attached to the computer Ubuntu 8.04 LTS DVD.

ModemData.txt says:
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.24_19_generic_ubuntu_i386.deb.zip

But there are not file
hsfmodem-7.80.02.05full_k2.6.24_19_generic_ubuntu_i386.deb.zip there.

What should I do?
--
Best regards,
Aleck

Only plain text email is forwarded by the Discuss@... List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.24-19-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@... 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-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008
scanModem update of: 2009_11_26

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

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 413c:8140 Dell Computer Corp.
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@...

For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:284b 1028:029a Audio device: Intel Corporation 82801H

Modem interrupt assignment and sharing:
19: 385 367 IO-APIC-fasteoi uhci_hcd:usb2, uhci_hcd:usb4, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 29.143448] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 19
[ 29.143480] PCI: Setting latency timer of device 0000:00:1b.0 to 64

===== 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.16
The modem cards detected by "aplay -l" are: None

The /proc/asound/pcm file reports:
-----------------------
00-01: Conexant Digital : Conexant Digital : playback 1
00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1

about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf6dfc000 irq 19

PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.24-19-generic/ubuntu/sound/alsa-driver/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 00:1b.0:
Modem chipset detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1028:029a
IRQ=19
HDA=8086:284b
SOFT=8086:284b.HDA
IDENT=hsfmodem
Driver=hsfmodem-drivers

For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801H
Primary device ID: 8086:284b
Subsystem PCI_id 1028:029a
Softmodem codec or chipset from diagnostics:
from Archives:

Support type needed or chipset: hsfmodem

Writing DOCs/Intel.txt

For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt

From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.05full_k2.6.24_19_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.

The directions following below need only be pursued, if the above procedures are not adequate.

Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion: 2.6.24_19_generic
They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

Support for Conexant chips hosted on High Definition Audio cards may require
installation of additional packages, one of the alsa-driver-linuxant packages
on http://www.linuxant.com/alsa-driver/ At the same time download the
alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During the
hsfmodem install, there will be a message if there is necessary installation of
alsa-driver-linuxant

The installation command for a .deb suffic packages is, with root/adm permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm

There may a message that "Dependencies" are not satisfied. In this case the Ubuntu/Debian packages to be installed are linux-libc-dev & libc6-dev. Package
names may be different for other Linuxes. If not on your install CD, these
packages can be searched for at http://packages.ubuntu.com. After download,
they can be coinstalled with:
sudo dpkg -i li*.deb
Again try the alsa-driver-linuxant

There may be a message that the patch must be applied. In this case get the
ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2
Under Linux, this package is unpacked with:
$ tar jxf alsa*.tar.bz2
Next the patch is applied with:
$ patch -p0 < alsa-driver-1.0.17-1.patch

See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html
for details on compiling and installing replacement snd-hda-intel + its
dependent drivers.
After the installation is completed, rerun the hsfmodem installation.
Reboot and try to detect the modem with Root permission:
sudo wvdialconf /etc/wvdial.conf

Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt

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

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.2
linuc_headers base folder /lib/modules/2.6.24-19-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 269256 2007-10-05 01: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 --------

Re: Instalación del modem

2009-12-09T11:41:01Z

Francisco,

Descarga el archivo scanModem.gz de la pagina de LinModems Resource page:

http://linmodems.technion.ac.il/packages/scanModem.gz

Lo pasas a la particion de Ubuntu o tu directorio de home y lo extraes

$ gunzip scanModem.gz
$ chmod +x scanModem
$ sudo ./scanModem

Cuando termine te pone un folder con varios archivos, nomas busca el
ModemData.txt dentro del Modem/ y envialo para lista
(discuss@...)

Puedes leer la siguiente pagina y la puedes buscar en español

http://linmodems.technion.ac.il/linmodems_support_sp.html

Saludos,

Antonio

Translation:

recommend Francisco download scanModem.gz file from LinModems Resource Page
run
$ gunzip scanModem.gz
$ chmod +x scanModem
$ sudo ./scanModem

Look at the files generated by scanModem and send/Attach ModemData.txt
back to list so we can recommend a driver for his modem if it is
supported.

Regards,

Antonio

http://linmodems.technion.ac.il/first.html

2009/12/9 Francisco Martín <pamartinzamora@...>:
> Buenas tardes:
> Hace unos días he instalado Ubuntu 9.10 y soy incapaz de conectarme a
> internet, tengo un modem de 56 Ks, marca Zoltrix V.90. Me pueden indicar
> como realizarlo, muchas gracias.
> Atentamente
>

Instalación del modem

2009-12-09T10:54:17Z

Buenas tardes:
Hace unos días he instalado Ubuntu 9.10 y soy incapaz de
conectarme a internet, tengo un modem de 56 Ks, marca Zoltrix V.90. Me
pueden indicar como realizarlo, muchas gracias.
Atentamente

Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic

2009-12-09T09:51:33Z

Don't run "make", as the compile has already been done. Just do:
$ sudo ./setup

MarvS

On Wed, Dec 9, 2009 at 5:33 AM, Claudio Mantegazza <ermante@...> wrote:

>
> Marvin,Jacques, wait a minute....
>
> I did only a part which jacques told me...
> i arrived to do all until jacques told me to continue to do what wrote in the README file at the installation but when i write the command in it i receice an error... Look at...
>
> =================
> root@mantegazza-laptop:~#     find / -iname   SLMODEMD*
> root@mantegazza-laptop:~# cd /home/mantegazza/Scaricati
> root@mantegazza-laptop:/home/mantegazza/Scaricati# tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
> root@mantegazza-laptop:/home/mantegazza/Scaricati#       cd SLMODEMD_gcc4.4_alsa1.0.21
> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# exit
> exit
> mantegazza@mantegazza-laptop:~$ cd /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ make
> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo su
> [sudo] password for mantegazza:
> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make
> make: *** Nessun obiettivo specificato e nessun makefile trovato. Arresto.
> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21# make install
> make: *** Nessuna regola per creare l'obiettivo «install». Arresto.
> root@mantegazza-laptop:/home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21#
> ===================
>
> So what i have to do before continue?
>
> Claudio.
>
>
>
> ----------------------------------------
>> Date: Sat, 5 Dec 2009 16:37:08 -0500
>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel 2.6.31-15-generic
>> From: marvin.stodolsky@...
>> To: discuss@...
>> CC: ermante@...
>>
>> Claudio
>>
>> You are missing a file with the contents below.
>> Make a file with these contents, but replacing:
>> DialUpNumber
>> YourLoginName
>> YourPassword
>> This file should be named wvdial.conf, and can initially be in your home folder.
>> Then after the
>> $ sudo slmodemd -c ITALY --alsa modem:1
>> open a 2nd console and do:
>> $ sudo wvdial -config=wvdial.conf
>>
>> MarvS
>>
>> [Dialer Defaults]
>> Phone = DialUpNumber
>> Username = YourLoginName
>> Password = YourPassword
>> Init1 = ATZ
>> Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
>> Modem Type = Analog Modem
>> ISDN = 0
>> New PPPD = yes
>> Modem = /dev/ttySL0
>> Carrier Check = no
>> Baud = 460800
>>
>> On Fri, Dec 4, 2009 at 9:40 PM, Marvin Stodolsky
>> wrote:
>>> The modem activation command should be:
>>> $ sudo slmodemd -c ITALY --alsa modem:1
>>> there should be reported creation of a port:
>>> /dev/ttySL0 --> /dev/pts/N , N some number
>>>
>>> Only after such a success should one try;
>>> $ sudo wvdial
>>>
>>> MarvS
>>>
>>>
>>>
>>>
>>> On Fri, Dec 4, 2009 at 8:06 AM, Jacques Goldberg
>>> wrote:
>>>> Claudio,
>>>>
>>>>
>>>> I believe that you have reached such a mess level that it has become
>>>> impossible to know which is what.
>>>>
>>>> Here is what I would do in your place:
>>>>
>>>> Because you used two versions of file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz ,
>>>>
>>>> 1-be root or sudo before any command
>>>>
>>>> 2-go into directory /usr/sbin
>>>> 3-in that directory give command rm slmodemd*
>>>>
>>>> Make ABSOLUTELY SURE that you write slmodemd* so that there is NOTHING, NO
>>>> SPACE, NOTHING ELSE, between slmodemd and the * . ABSOLUTELY SURE.
>>>>
>>>> Answer yes everytime you are prompted to erase a file with name starting
>>>> with slmodemd and NO in any other case.
>>>>
>>>> 4-go into directory named SLMODEMD_gcc4.4_alsa1.0.21
>>>>
>>>> 5-in that directory give command make uninstall
>>>>
>>>> 6-give the command cd
>>>>
>>>> 7-give the command find / -iname SLMODEMD* .Attention
>>>> SLMODEMD in capital case.
>>>>
>>>> This will give a list of all the files in your computer with a name
>>>> starting with SLMODEMD
>>>>
>>>> Erase all these files one at a time. To erase a file the command is rm ;
>>>> to erase an empty directory the command is rmdir; to erase a directory which
>>>> is not empty the command is rm -rf
>>>> Always start with rm and then try rmdir and then rm -rf if the
>>>> preceeding one is not accepted.
>>>>
>>>> 8-Now, in your usual directory, the one where you usually login, download
>>>> the file SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>
>>>> Do not try to use one which has been downloaded before unless you are
>>>> ABSOLUTELY sure that this is the one which I
>>>>
>>>> placed this morning.
>>>>
>>>> 9-Give the command tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>
>>>> 10-Change directory with command cd SLMODEMD_gcc4.4_alsa1.0.21
>>>>
>>>> 11-Do exactly, one time and one time only, what Marv has written to you to
>>>> do or what is written in file README in the directory where you are starting
>>>> from point 4 in INSTALLATION
>>>>
>>>> 12-After you have given the command slmodemd and it has succeeded, in
>>>> an other window give the command
>>>>
>>>> wvdialconf /etc/wvdial.conf (no . in wvdialconf and a , in
>>>> /etc/wvdial.conf
>>>>
>>>> wvdialconf will find your modem
>>>>
>>>> Edit /etc/wvdial.conf as explained in
>>>> http://linmodems.technion.ac.il/wvdial.html   . Remember that you need
>>>>
>>>> Carrier Check = no
>>>>
>>>> 13- When the file /etc/wvdial.conf has been edited and saved, in that window
>>>> or any window except the one used for slmodemd, the command wvdial
>>>> should start your modem.
>>>>
>>>> when everything works well wvdial does NOT exit but stays doing nothing.
>>>>
>>>> Use your browser (like Firefox) and try to surf.
>>>>
>>>>
>>>> Please remember: every time you do something else than what we tell you to
>>>> do, like installing several slmodemd , you take the risk to create the
>>>> conditions for failure.
>>>>
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>>> Claudio Mantegazza wrote:
>>>>
>>>>> I downloaded again the new file.
>>>>> i saw that there was updated 1 hour ago...
>>>>> and in a new window (not the same about the
>>>>> =======================
>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ wvdial
>>>>> --> WvDial: Internet dialer version 1.60
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> mantegazza@mantegazza-laptop:~/Scaricati$ cd
>>>>> /home/mantegazza/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ ls
>>>>> 1st_Read.txt COPYING Files.txt setup slmodemd
>>>>> slmodemd.txt Testing.txt wvdial.conf
>>>>> Changes CountryList.txt README Slmodem-ALSA.txt
>>>>> slmodemd_Inst.txt slmodem.txt Unload.txt
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ sudo
>>>>> ./setup
>>>>> [sudo] password for mantegazza:
>>>>> Installing slmodemd helper to /usr/sbin/slmodemd
>>>>>
>>>>> Writing log to slmodemd_Inst.txt
>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>> There is a file /usr/sbin/slmodemd
>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>> for version 2.9.11
>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>> Version verified: 2.9.11
>>>>> Read the slmodemd_Inst.txt
>>>>>
>>>>> There is already installed a slmodemd of version: 2.9.11
>>>>> There is a file /usr/sbin/slmodemd
>>>>> Moving /usr/sbin/slmodemd to /usr/sbin/slmodemd.2.9.11
>>>>> Copying slmodemd to /usr/sbin/slmodemd, making exectuable, and checking
>>>>> for version 2.9.11
>>>>> SmartLink Soft Modem: version 2.9.11 Dec 3 2009 16:59:30
>>>>> Version verified: 2.9.11
>>>>> Read the slmodemd_Inst.txt
>>>>>
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>> wvdial
>>>>> --> WvDial: Internet dialer version 1.60
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>> =======================
>>>>>
>>>>> but if in this windows i write the slmodem command:
>>>>>
>>>>> ======================
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>> slmodemd --alsa -c YOUR_COUNTRY modem:1 error: mixer setup: attach hw:1
>>>>> error: No such file or directory
>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid argument
>>>>> error: cannot setup device `modem:1'
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$
>>>>> ======================
>>>>>
>>>>> I receive this error....
>>>>>
>>>>> and if i return in the other folder and i write...
>>>>>
>>>>> ================
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/SLMODEMD_gcc4.4_alsa1.0.21$ cd
>>>>> /home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem
>>>>> mantegazza@mantegazza-laptop:~/Scaricati/slmodem-2.9.11-20090222/modem$
>>>>> sudo su
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> wvdial
>>>>> --> WvDial: Internet dialer version 1.60
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>> --> Cannot open /dev/modem: No such file or directory
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> slmodemd -c ITALY modem:1
>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>> error: cannot setup device `modem:1'
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> make SUPPORT_ALSA=1
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> slmodemd -c ITALY modem:1
>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>> error: cannot setup device `modem:1'
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> cp slmodemd /usr/sbin
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> slmodemd -c ITALY modem:1
>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>> error: cannot setup device `modem:1'
>>>>>
>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>> ================
>>>>>
>>>>> Have you got other ideas?
>>>>>
>>>>> Claudio.
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------
>>>>>
>>>>>>
>>>>>> Date: Fri, 4 Dec 2009 11:17:52 +0200
>>>>>> From: Jacques.Goldberg@...
>>>>>> To: ermante@...
>>>>>> CC: olivares14031@...; discuss@...;
>>>>>> marvin.stodolsky@...
>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy kernel
>>>>>> 2.6.31-15-generic
>>>>>>
>>>>>> Claudio,
>>>>>>
>>>>>> Did you download the file again today within about one hour back from
>>>>>> now?
>>>>>>
>>>>>> I ask because this would then be after I installed the file with alsa
>>>>>> stuff included.
>>>>>>
>>>>>>
>>>>>> Now, reading your report, I have a question about:
>>>>>>
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> # slmodemd -c ITALY modem:1
>>>>>>
>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>> wvdial
>>>>>>
>>>>>> Did you give the wvdial command in the same window where you had given
>>>>>> before the command slmodemd?
>>>>>>
>>>>>> If yes, then to give wvdial you must have stopped slmodemd with CTRL-C
>>>>>> which would explain why wvdial did not find the file /dev/ttySL0 : this
>>>>>> file exists ONLY while slmodemd is running.
>>>>>>
>>>>>> If my guess is correct, then remember to ALWAYS start wvdial IN AN OTHER
>>>>>> FREE WINDOW, not the one where slmodemd runs.
>>>>>>
>>>>>>
>>>>>> Jacques
>>>>>>
>>>>>>
>>>>>> Claudio Mantegazza wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> I made again the command you told me and in this time i didn't receive
>>>>>>> any errors....
>>>>>>> Look at the command i wrote:
>>>>>>>
>>>>>>> =========================
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> lsdp_dummy.c Makefile modem_comp.c modem_defs.h modem_main.o modem_test
>>>>>>> sysdep_common.c
>>>>>>> dp_dummy.o Makefile.20080401 modem_comp.o modem_dp.h modem.o
>>>>>>> modem_test.c sysdep_common.o
>>>>>>> dp_sinus.c modem_at.c modem_datafile.c modem_ec.c modem_pack.c
>>>>>>> modem_test.o
>>>>>>> dp_sinus.o modem_at.o modem_datafile.o modem_ec.o modem_pack.o
>>>>>>> modem_timer.c
>>>>>>> dsplibs.o modem.c modem_debug.c modem.h modem_param.c modem_timer.h
>>>>>>> homolog_data.c modem_cmdline.c modem_debug.h modem_homolog.h
>>>>>>> modem_param.h modem_timer.o
>>>>>>> homolog_data.o modem_cmdline.o modem_debug.o modem_main.c modem_param.o
>>>>>>> slmodemd
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> modprobe snd-intel8x0m
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> aplay -l
>>>>>>> **** Lista di PLAYBACK dispositivi hardware ****
>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 0: Intel ICH
>>>>>>> [Intel 82801DB-ICH4]
>>>>>>> Sottoperiferiche: 1/1
>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>> scheda 0: I82801DBICH4 [Intel 82801DB-ICH4], dispositivo 4: Intel ICH -
>>>>>>> IEC958 [Intel 82801DB-ICH4 - IEC958]
>>>>>>> Sottoperiferiche: 1/1
>>>>>>> Sottoperiferica #0: subdevice #0
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>
>>>>>>> root@mantegazza-laptop:/home/mantegazza/Scaricati/slmodem-2.9.11-20090222/modem#
>>>>>>> wvdial
>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>
>>>>>>> =========================
>>>>>>>
>>>>>>> But i cannot be able to connect....
>>>>>>>
>>>>>>> Claudio.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Date: Thu, 3 Dec 2009 14:14:59 -0600
>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>> From: olivares14031@...
>>>>>>>> To: ermante@...
>>>>>>>> CC: discuss@...; marvin.stodolsky@...
>>>>>>>>
>>>>>>>> Claudio,
>>>>>>>>
>>>>>>>> What happens when you try
>>>>>>>> $ sudo slmodemd --alsa -c ITALY modem:1
>>>>>>>>
>>>>>>>> and try from the recently compiled slmodemd in
>>>>>>>> slmodem-2.9.11-20090222/modem folder?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>>
>>>>>>>> Antonio
>>>>>>>>
>>>>>>>> On Thu, Dec 3, 2009 at 8:01 AM, Claudio Mantegazza wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Antonio,
>>>>>>>>> i'm very sorry but it didn't run...
>>>>>>>>>
>>>>>>>>> i made all that you told me but at the last command:
>>>>>>>>>
>>>>>>>>> =========
>>>>>>>>> # make SUPPORT_ALSA=1
>>>>>>>>> rebuild profile...
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_main.o -c modem_main.c
>>>>>>>>> modem_main.c: In function ‘setup_stream’:
>>>>>>>>> modem_main.c:429: warning: ‘snd_pcm_sw_params_set_xfer_align’ is
>>>>>>>>> deprecated (declared at /usr/include/alsa/pcm.h:1116)
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_cmdline.o -c modem_cmdline.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o modem.o
>>>>>>>>> -c modem.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_datafile.o -c modem_datafile.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_at.o -c modem_at.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_timer.o -c modem_timer.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_pack.o -c modem_pack.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_ec.o -c modem_ec.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_comp.o -c modem_comp.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_param.o -c modem_param.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_debug.o -c modem_debug.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> homolog_data.o -c homolog_data.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> dp_sinus.o -c dp_sinus.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> dp_dummy.o -c dp_dummy.c
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> sysdep_common.o -c sysdep_common.c
>>>>>>>>> gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o
>>>>>>>>> modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o
>>>>>>>>> modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o
>>>>>>>>> /usr/lib/libasound.so
>>>>>>>>> gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -DSUPPORT_ALSA=1 -o
>>>>>>>>> modem_test.o -c modem_test.c
>>>>>>>>> modem_test.c: In function ‘modem_test_start’:
>>>>>>>>> modem_test.c:110: warning: ignoring return value of ‘write’, declared
>>>>>>>>> with attribute warn_unused_result
>>>>>>>>> gcc -o modem_test modem_test.o modem_cmdline.o modem.o
>>>>>>>>> modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o
>>>>>>>>> modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o
>>>>>>>>> dp_dummy.o dsplibs.o sysdep_common.o /usr/lib/libasound.so
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> =========
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> # cp slmodemd /usr/sbin
>>>>>>>>>
>>>>>>>>> =========
>>>>>>>>> # slmodemd -c ITALY modem:1
>>>>>>>>> error: mdm setup: cannot stat `modem:1': No such file or directory
>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>> =========
>>>>>>>>> # wvdial
>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>> =========
>>>>>>>>>
>>>>>>>>> it seems not like it...
>>>>>>>>>
>>>>>>>>> And now?
>>>>>>>>> what can i do?
>>>>>>>>>
>>>>>>>>> Claudio.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ...............................................................................................................
>>>>>>>>>
>>>>>>>>> ----------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Date: Thu, 3 Dec 2009 07:11:57 -0600
>>>>>>>>>> Subject: Re: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>> kernel 2.6.31-15-generic
>>>>>>>>>> From: olivares14031@...
>>>>>>>>>> To: ermante@...
>>>>>>>>>> CC: marvin.stodolsky@...; jacques.goldberg@...
>>>>>>>>>>
>>>>>>>>>> Claudio,
>>>>>>>>>>
>>>>>>>>>> If you want to build SLMODEMD on your own for your system, Please do
>>>>>>>>>> the following:
>>>>>>>>>>
>>>>>>>>>> Download:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>> Copy it to your linux partition/working directory, untar it with
>>>>>>>>>> $ tar -zxvf slmodem-2.9.11-20090222.tar.gz
>>>>>>>>>> $ cd slmodem-2.9.11-20090222
>>>>>>>>>> $ cd modem
>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>>
>>>>>>>>>> as show in README
>>>>>>>>>>
>>>>>>>>>> ====================
>>>>>>>>>> 3. Build application 'slmodemd' with ALSA support. For this in
>>>>>>>>>> slmodem-2.9.x dir:
>>>>>>>>>>
>>>>>>>>>> $ cd modem
>>>>>>>>>> $ make SUPPORT_ALSA=1
>>>>>>>>>> ====================
>>>>>>>>>>
>>>>>>>>>> After this is successfull, then there will be a slmodemd file in that
>>>>>>>>>> directory, copy it over to /usr/sbin
>>>>>>>>>>
>>>>>>>>>> and try the
>>>>>>>>>> $ sudo slmodemd -c ITALY modem:1
>>>>>>>>>>
>>>>>>>>>> command again and hopefully it works this time around.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Antonio
>>>>>>>>>>
>>>>>>>>>> PS.
>>>>>>>>>> I hope that the "NO CARRIER" error shows up like it did for me with
>>>>>>>>>> 2.6.31.X kernels but slamr module.
>>>>>>>>>>
>>>>>>>>>> On 12/3/09, Claudio Mantegazza wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I untar the new one you sent me.
>>>>>>>>>>> i exec the command:
>>>>>>>>>>>
>>>>>>>>>>> ===============
>>>>>>>>>>> # ./slmodemd --alsa -c ITALY modem:1
>>>>>>>>>>> ALSA support is not compiled in (see README for howto).
>>>>>>>>>>> ===============
>>>>>>>>>>>
>>>>>>>>>>> Now. how can i compile the ALSA support?
>>>>>>>>>>>
>>>>>>>>>>> P.s. i just installed the package libasound2-dev
>>>>>>>>>>>
>>>>>>>>>>> Thanks...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Date: Wed, 2 Dec 2009 14:18:11 -0500
>>>>>>>>>>>> Subject: SLMODEMD_gcc4.4_alsa1.0.21.tar.gz, Re: Claudio, Italy
>>>>>>>>>>>> kernel
>>>>>>>>>>>> 2.6.31-15-generic
>>>>>>>>>>>> From: marvin.stodolsky@...
>>>>>>>>>>>> To: ermante@...; Jacques.Goldberg@...;
>>>>>>>>>>>> olivares14031@...
>>>>>>>>>>>>
>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>
>>>>>>>>>>>> Used the attached SLMODEMD_gcc4.4_alsa1.0.21.tar.gz
>>>>>>>>>>>>
>>>>>>>>>>>> Jacques
>>>>>>>>>>>> for the smartlink/ folder
>>>>>>>>>>>>
>>>>>>>>>>>> MarvS
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Dec 2, 2009 at 8:52 AM, Claudio Mantegazza wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> because i didn't find which u told me... and this one is the last
>>>>>>>>>>>>> one...
>>>>>>>>>>>>>
>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>> Not Found
>>>>>>>>>>>>> The requested URL /packages/smartlink/SLMODEMD.gcc4.4.tar.gz was
>>>>>>>>>>>>> not
>>>>>>>>>>>>> found on this server.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Apache/2.0.52 (Red Hat) Server at linmodems.technion.ac.il Port 80
>>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>>
>>>>>>>>>>>>> Maybe i don't understand something?
>>>>>>>>>>>>> Can you tell me better where i can download the right file,
>>>>>>>>>>>>> please?
>>>>>>>>>>>>> give me the correct link....
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ----------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Date: Wed, 2 Dec 2009 07:15:13 -0600
>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>> CC: discuss@...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1': Invalid
>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> why did you get the SLMODEMD_gcc4.4_alsa1.0.18.tar.gz?
>>>>>>>>>>>>>> If your alsa verion is 1.0.20?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are: None
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>> ===== 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.20
>>>>>>>>>>>>>> The modem cards detected by "aplay -l" are:
>>>>>>>>>>>>>> scheda 1: Modem [Intel 82801DB-ICH4 Modem], dispositivo 0: Intel
>>>>>>>>>>>>>> ICH -
>>>>>>>>>>>>>> Modem [Intel 82801DB-ICH4 Modem - Modem]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The /proc/asound/pcm file reports:
>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
>>>>>>>>>>>>>> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC :
>>>>>>>>>>>>>> capture 1
>>>>>>>>>>>>>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
>>>>>>>>>>>>>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 :
>>>>>>>>>>>>>> playback 1
>>>>>>>>>>>>>> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem :
>>>>>>>>>>>>>> playback
>>>>>>>>>>>>>> 1 : capture 1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> about /proc/asound/cards:
>>>>>>>>>>>>>> ------------------------
>>>>>>>>>>>>>> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
>>>>>>>>>>>>>> Intel 82801DB-ICH4 with ALC202 at irq 5
>>>>>>>>>>>>>> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
>>>>>>>>>>>>>> Intel 82801DB-ICH4 Modem at irq 5
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> If you have downloaded the recommended SLMODEMD: the package
>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Does the same thing happen?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 12/2/09, Claudio Mantegazza wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I downloaded
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.18.tar.gz
>>>>>>>>>>>>>>> but the install doesn't go: have a look...
>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>> mant@mant-laptop:~$ sudo slmodemd -c ITALY --alsa modem:1
>>>>>>>>>>>>>>> [sudo] password for mant:
>>>>>>>>>>>>>>> error: mixer setup: attach hw:1 error: No such file or directory
>>>>>>>>>>>>>>> ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1
>>>>>>>>>>>>>>> ALSA lib pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM modem:1
>>>>>>>>>>>>>>> error: alsa setup: cannot open playback device 'modem:1':
>>>>>>>>>>>>>>> Invalid
>>>>>>>>>>>>>>> argument
>>>>>>>>>>>>>>> error: cannot setup device `modem:1'
>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>> mant@mant-laptop:~/Scaricati$ wvdial
>>>>>>>>>>>>>>> --> WvDial: Internet dialer version 1.60
>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>> --> Cannot open /dev/ttySL0: No such file or directory
>>>>>>>>>>>>>>> =================================================
>>>>>>>>>>>>>>> It doen't work!
>>>>>>>>>>>>>>> the drivers doesn't load fine!
>>>>>>>>>>>>>>> ....
>>>>>>>>>>>>>>> Claudio.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Date: Tue, 1 Dec 2009 07:10:24 -0600
>>>>>>>>>>>>>>>> Subject: Re: Claudio, Italy kernel 2.6.31-15-generic
>>>>>>>>>>>>>>>> From: olivares14031@...
>>>>>>>>>>>>>>>> To: ermante@...
>>>>>>>>>>>>>>>> CC: marvin.stodolsky@...; stephenpinker79@...;
>>>>>>>>>>>>>>>> discuss@...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Claudio,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scanModem reports that your modem is supported via
>>>>>>>>>>>>>>>> SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>> :
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> For candidate modem in: 00:1f.6
>>>>>>>>>>>>>>>> 0703 Modem: Intel Corporation 82801DB/DBL/DBM
>>>>>>>>>>>>>>>> Primary device ID: 8086:24c6
>>>>>>>>>>>>>>>> Subsystem PCI_id 1631:d005
>>>>>>>>>>>>>>>> Softmodem codec or chipset from diagnostics: SIL22, a Smartlink
>>>>>>>>>>>>>>>> type
>>>>>>>>>>>>>>>> from Archives:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This is a NEW softmodem case! Please send the output
>>>>>>>>>>>>>>>> ModemData.txt
>>>>>>>>>>>>>>>> to DISCUSS@... to enrich the Archive and help others!
>>>>>>>>>>>>>>>> If further assistance is not needed, please use email Subject:
>>>>>>>>>>>>>>>> New Case Only
>>>>>>>>>>>>>>>> -------------------------------------------
>>>>>>>>>>>>>>>> Support type needed or chipset: slmodemd
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> An ALSA (Advanced Linux Sound Architecture) modem driver:
>>>>>>>>>>>>>>>> snd-intel8x0m
>>>>>>>>>>>>>>>> provides Low Level support enabling contact with the modem
>>>>>>>>>>>>>>>> hardware.
>>>>>>>>>>>>>>>> For all BUT Conexant chip soft modems (using hsfmodem software)
>>>>>>>>>>>>>>>> complementary High Level support is through a Smartlink
>>>>>>>>>>>>>>>> utility:
>>>>>>>>>>>>>>>> slmodemd
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Download from
>>>>>>>>>>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/
>>>>>>>>>>>>>>>> the package SLMODEMD.gcc4.4.tar.gz having a compiled slmodemd.
>>>>>>>>>>>>>>>> Unpack
>>>>>>>>>>>>>>>> under Linux with:
>>>>>>>>>>>>>>>> $ tar zxf SLMODEMD.gcc4.4.tar.gz
>>>>>>>>>>>>>>>> and read instructions therein. But briefly, the modem is setup
>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> command:
>>>>>>>>>>>>>>>> sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
>>>>>>>>>>>>>>>> reporting dynamic creation of ports:
>>>>>>>>>>>>>>>> /dev/ttySL0 --> /dev/pts/N , with N some number
>>>>>>>>>>>>>>>> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for
>>>>>>>>>>>>>>>> follow
>>>>>>>>>>>>>>>> through guidance.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> If you have downloaded the package SLMODEMD.gcc4.4.tar.gz and
>>>>>>>>>>>>>>>> tried
>>>>>>>>>>>>>>>> the above instructions and are not getting anywhere/(modem does
>>>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>> respond) it could be because of
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> For candidate card in slot 00:1f.6, firmware information and
>>>>>>>>>>>>>>>> bootup
>>>>>>>>>>>>>>>> diagnostics are:
>>>>>>>>>>>>>>>> PCI slot PCI ID SubsystemID Name
>>>>>>>>>>>>>>>> ---------- --------- --------- --------------
>>>>>>>>>>>>>>>> 00:1f.6 8086:24c6 1631:d005 Modem: Intel Corporation
>>>>>>>>>>>>>>>> 82801DB/DBL/DBM
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Modem interrupt assignment and sharing:
>>>>>>>>>>>>>>>> 5: 137 XT-PIC-XT yenta, Intel 82801DB-ICH4, Intel
>>>>>>>>>>>>>>>> 82801DB-ICH4 Modem
>>>>>>>>>>>>>>>> --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
>>>>>>>>>>>>>>>> [ 0.071472] pci 0000:00:1f.6: reg 10 io port: [0xe300-0xe3ff]
>>>>>>>>>>>>>>>> [ 0.071480] pci 0000:00:1f.6: reg 14 io port: [0xe400-0xe47f]
>>>>>>>>>>>>>>>> [ 0.071521] pci 0000:00:1f.6: PME# supported from D0 D3hot
>>>>>>>>>>>>>>>> D3cold
>>>>>>>>>>>>>>>> [ 0.071525] pci 0000:00:1f.6: PME# disabled
>>>>>>>>>>>>>>>> [ 0.956536] serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI
>>>>>>>>>>>>>>>> 5
>>>>>>>>>>>>>>>> (level, low) -> IRQ 5
>>>>>>>>>>>>>>>> [ 0.956547] serial 0000:00:1f.6: PCI INT B disabled
>>>>>>>>>>>>>>>> [ 3186.856643] Intel ICH Modem 0000:00:1f.6: PCI INT B ->
>>>>>>>>>>>>>>>> Link[LNKB]
>>>>>>>>>>>>>>>> -> GSI 5 (level, low) -> IRQ 5
>>>>>>>>>>>>>>>> [ 3186.856669] Intel ICH Modem 0000:00:1f.6: setting latency
>>>>>>>>>>>>>>>> timer to
>>>>>>>>>>>>>>>> 64
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The PCI slot 00:1f.6 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@...
>>>>>>>>>>>>>>>> if help is needed.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Let us know if the package SLMODEMD.gcc4.4.tar.gz works or not,
>>>>>>>>>>>>>>>> and if
>>>>>>>>>>>>>>>> the driver loads fine but does not respond, follow the above
>>>>>>>>>>>>>>>> instructions to see if it can work or not.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _________________________________________________________________
>>>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _________________________________________________________________
>>>>>>>>> 25 Gigabyte per le tue foto online
>>>>>>>>> http://www.windowslive.it/foto.aspx
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> _________________________________________________________________
>>>>>>> Giochi, radio, TV... E tutti i tuoi amici. Cercali su Messenger
>>>>>>> http://www.messenger.it/home_comunica.aspx
>>>>>>>
>>>>>
>>>>>
>>>>> _________________________________________________________________
>>>>> I tuoi amici sempre a portata di clic, sul nuovo Web Messenger
>>>>> http://www.windowslive.it/foto.aspx
>>>>
>>>>
>>>
>
> _________________________________________________________________
> Scopri tuttele novità di Internet Explorer 8
> http://www.microsoft.com/italy/windows/internet-explorer/msn.aspx

Re: What about ubunto 9.04 i386?

2009-12-09T05:08:32Z

Fawzy,

scanModem reports that it has not found a modem among PCI devices:

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
PCI Fast Ethernet (rev 90)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:0a.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
------------------------------------------------
with USB and bridge devices not displayed.

If your modem is connected by an external serial cable,
or mounted internally on an ISA card, scanModem would not access it.
Try with Root permission
$ sudo wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
sudo gedit /etc/wvdial.conf
will be able to dial out with Root permission:
sudo wvdial

It also tells you that:

Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems

If the above tests fail, please provide any independent information
available on your modem.
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. From the Driver Details TAB, copy out the
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/9/09, fawzy esmail <lordfawzy22@...> wrote:
> From: fawzy esmail [lordfawzy22@...]
> Sent: Thursday, 9 December 2009
> Content-Type: text/plain; charset=US-ASCII; name="ModemData.txt"
> Content-Disposition: attachment; filename="ModemData.txt"
> Content-Transfer-Encoding: base64
> X-Attachment-Id: file0
>

What about ubunto 9.04 i386?

2009-12-09T01:29:25Z

From: fawzy esmail [lordfawzy22@...]
Sent: Thursday, 9 December 2009
Content-Type: text/plain; charset=US-ASCII; name="ModemData.txt"
Content-Disposition: attachment; filename="ModemData.txt"
Content-Transfer-Encoding: base64
X-Attachment-Id: file0

Only plain text email is forwarded by the Discuss@... List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.28-11-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@... 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.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
scanModem update of: 2009_12_07

The dialer utility package WVDIAL does not appear to be installed on your System.
For Ubuntu Jaunty users, there are at the bottom of http://linmodems.technion.ac.il/packages/:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

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

There are no blacklisted modem drivers in /etc/modprobe* files

Potentially useful modem drivers now loaded are:

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@...

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

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:0a.0 Multimedia audio controller: ESS Technology ES1969 Solo-1 Audiodrive
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
------------------------------------------------
with USB and bridge devices not displayed.

If your modem is connected by an external serial cable,
or mounted internally on an ISA card, scanModem would not access it.
Try with Root permission
$ sudo wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
sudo gedit /etc/wvdial.conf
will be able to dial out with Root permission:
sudo wvdial

Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems

If the above tests fail, please provide any independent information available on your modem.
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. From the Driver Details TAB, copy out the 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.

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

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

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.28-11-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 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.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 --------

Re: help with modem Encore enf656-esw-mop

2009-12-08T16:13:19Z

Carlos,

If your modem is internal, try as a best guess:
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.02full_k2.6.31_15_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See DOCs/Testing.txt for details.

report back presently.

MarvS
scanModem maintainer

On Tue, Dec 8, 2009 at 4:57 PM, Antonio Olivares
<olivares14031@...> wrote:

> Carlos,
>
> scanModem did not find a modem within the PCI devices:
>
> A candidate modem is not evident among the PCI devices:
> ------------------------------------------------
> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
> Integrated Graphics Controller (rev 10)
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
> Definition Audio Controller (rev 01)
> 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
> Controller (rev 01)
> 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family)
> SATA IDE Controller (rev 01)
> 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
> 01:00.0 Ethernet controller: Attansic Technology Corp. Atheros
> AR8121/AR8113/AR8114 PCI-E Ethernet Controller (rev b0)
> 03:01.0 Network controller: RaLink RT2600 802.11 MIMO
> ------------------------------------------------
> with USB and bridge devices not displayed.
>
> If your modem is connected by an external serial cable,
> or mounted internally on an ISA card, scanModem would not access it.
> Try with Root permission
> $ sudo wvdialconf /etc/wvdial.conf
> to detect these modem types and some USB modems.
> If the detection is successful, read the DOCs/wvdial.txt .
> Edit the /etc/wvdial.conf with Root permission:
> sudo gedit /etc/wvdial.conf
> will be able to dial out with Root permission:
> sudo wvdial
>
> If the above tests fail, please provide any independent information
> available on your modem.
> 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. From the Driver Details TAB, copy out the
> 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 Tue, Dec 8, 2009 at 3:51 PM, Carlos Ernesto Pruna Capdevila
> <carlosepc.swl@...> wrote:
>> --
>> =======
>> Carlos Ernesto Pruna Capdevila
>>
>

Re: Larry, U.S.A. kernel 2.6.27-7-generic

2009-12-08T16:06:52Z

Larry

Before doing the make commands, you must be in the folder martian-full-20080625
Therein there will be shown by
$ ls
at least the files/ and/or folders/:
ChangeLog Cleaning.txt Concept INSTALL kmodule Makefile
martian.h modem README sample.txt scripts

the "make something" commands must be executed in a folder containg a
Makefile/makefile.

MarvS

>
> MarvS
>
> $ make clean

On Tue, Dec 8, 2009 at 11:06 AM, Larry Hager <larrymeditates@...> wrote:

> I tried entering the commands below and when I began with $ make clean
> I got the message "No rule to make target 'clean' I also tried cutting and pasting the commands as a whole but with no success. What did I do wrong?
>
>
> Larry
>
>
> --- On Sun, 12/6/09, Marvin Stodolsky <marvin.stodolsky@...> wrote:
>
>> From: Marvin Stodolsky <marvin.stodolsky@...>
>> Subject: Re: Larry, U.S.A. kernel 2.6.27-7-generic
>> To: "Larry Hager" <larrymeditates@...>
>> Cc: discuss@...
>> Date: Sunday, December 6, 2009, 8:21 PM
>> Larry
>>
>> You must do the make commands within the folder
>> martian-full-20080625
>> per illustration below.
>>
>> MarvS
>>
>> $ make clean
>> make -C kmodule/ clean
>> make[1]: Entering directory
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> make -C /lib/modules/2.6.28-16-generic/build
>> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
>> clean
>> make[2]: Entering directory
>> `/usr/src/linux-headers-2.6.28-16-generic'
>>
>> CLEAN   /usr/src/pkg/martian/martian-full-20080625/kmodule/.tmp_versions
>>
>> CLEAN   /usr/src/pkg/martian/martian-full-20080625/kmodule/Module.symvers
>> make[2]: Leaving directory
>> `/usr/src/linux-headers-2.6.28-16-generic'
>> make[1]: Leaving directory
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> make -C modem/ clean
>> make[1]: Entering directory
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> RM    OBJS
>> RM    BINS
>> RM    TOOLS
>> make[1]: Leaving directory
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>>
>> Thus having cleaned out any old file debris, do the compile
>> with
>> $ make all
>> make -C kmodule/ modules
>> make[1]: Entering directory
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> make -C /lib/modules/2.6.28-16-generic/build
>> M="/usr/src/pkg/martian/martian-full-20080625/kmodule"
>> modules
>> make[2]: Entering directory
>> `/usr/src/linux-headers-2.6.28-16-generic'
>> CC [M]
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.o
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:
>> In
>> function ‘martian_isr’:
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian.c:131:
>> warning: value computed is not used
>> CC [M]
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.o
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:358:
>> warning: ‘mars_read_register_rem’ defined but not used
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/marsio.c:371:
>> warning: ‘mars_write_register_rem’ defined but not
>> used
>> CC [M]
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/mfifo.o
>> LD [M]
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.o
>> Building modules, stage 2.
>> MODPOST 1 modules
>> CC
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.mod.o
>> LD [M]
>> /usr/src/pkg/martian/martian-full-20080625/kmodule/martian_dev.ko
>> make[2]: Leaving directory
>> `/usr/src/linux-headers-2.6.28-16-generic'
>> make[1]: Leaving directory
>> `/usr/src/pkg/martian/martian-full-20080625/kmodule'
>> make -C modem/ all
>> make[1]: Entering directory
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>> CC    main.o
>> CC    dumpers.o
>> CC    log.o
>> CC    session.o
>> CC    mport.o
>> CC    pty.o
>> CC    sysdep.o
>> CC    isr.o
>> CC    smp.o
>> CC    core_if.o
>> CC    coresubst.o
>> CC    link.o
>> CC    tweakrelocsdynamic.o
>> CC    coreadd.o
>> CC    elf386tweakrelocs
>> LD    marscore.o
>> TWEAK    marscore.o
>> LD    martian_modem
>> make[1]: Leaving directory
>> `/usr/src/pkg/martian/martian-full-20080625/modem'
>>
>> Lastly do the installation of the products with root/adm
>> authority:
>> $ sudo make install
>>
>> On Sun, Dec 6, 2009 at 4:43 PM, Larry Hager <larrymeditates@...>
>> wrote:
>> > I've installed the packages. I then checked the
>> martian file "install" which suggests starting with $ make
>> all
>> > I got the message: "No rule to make target 'all'
>> .Stop. Is this the right step to take next? What should
>> I do now?
>> >
>> > Take care,
>> >
>> > Larry
>> >
>> >
>> > --- On Wed, 12/2/09, Marvin Stodolsky <marvin.stodolsky@...>
>> wrote:
>> >
>> >> From: Marvin Stodolsky <marvin.stodolsky@...>
>> >> Subject: Re: Larry, U.S.A. kernel
>> 2.6.27-7-generic
>> >> To: "Larry Hager" <larrymeditates@...>
>> >> Cc: discuss@...
>> >> Date: Wednesday, December 2, 2009, 8:22 PM
>> >> Larry,
>> >>
>> >> The linux-libc-dev and libc6-dev must be in
>> the
>> >> same folder, wherein
>> >> you execute
>> >> $ sudo dpkg -i lib*.deb
>> >> Your personal folder is OK.
>> >> The packages should be displayer by
>> >> $ ls *.deb
>> >> Note that $ is the command prompt, but not part of
>> the
>> >> command: sudo
>> >> dpkg -i lib*.deb
>> >>
>> >> MarvS
>> >>
>> >> On Wed, Dec 2, 2009 at 11:12 PM, Larry Hager
>> <larrymeditates@...>
>> >> wrote:
>> >> > I'm using Ubuntu 8.10 and trying to set up a
>> modem and
>> >> was told to download packages: linux-libc-dev and
>> libc6-dev.
>> >> I downloaded the files to my desktop but when I
>> entered
>> >> the command $sudo dpkg -i lib*.deb I got the
>> message: error
>> >> processing lib* (--install): cannot access
>> archive: no such
>> >> file or directory. What am I doing wrong?
>> >> >
>> >> > Thank you for your help!
>> >> >
>> >> >
>> >> >
>> >> > Take care,
>> >> >
>> >> > Larry
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>