Re: Fibonacci, Colombia, 2.6.35-24-generic

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

 



The slamr driver is definitely not appropriate.
It should be unloaded.
Under Ubuntu, the snd-intel-hda driver cannot be easily unloaded,
because its services to the Sound System override.

Anton

MarvS

On Sun, Jan 23, 2011 at 9:20 AM, Antonio Olivares
<olivares14031@xxxxxxxxx> wrote:
> Fibonacci,
>
> There are two conflicting drivers here:
>
> ÂPotentially useful modem drivers now loaded are:
>   Âsnd_hda_intel  slamr
>
> Try to do the following:
>
> $ sudo modprobe -r slamr
> $ sudo modprobe -r snd_hda_intel
> then reload the latter one
> $ sudo modprobe snd_hda_intel
> $ sudo slmodemd -c USA --alsa hw:0,6
>
> Leave this running in the background, fire up another terminal shell/tab and run
> $ sudo wvdialconf /etc/wvdial.conf
>
> to be safe you may run
> $ dmesg | grep 'sl*' and output of
> $ sudo tail -f /var/log/messages
> last few lines when running the above commands. ÂReport back presently.
>
> Regards,
>
> Antonio
>
> On Sun, Jan 23, 2011 at 2:43 AM, Fibonacci Prower
> <fibonacci.prower@xxxxxxxxx> wrote:
>> 2011/1/23 Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>:
>>> Fibonacci
>>>
>>> Please disconnect the USB devices as much as possible, and take out
>>> any PCMCIA cards
>>> Your System seems low on RAM. ÂAgain run scanModem
>>> On your first round the important ALSA diagnostics did not get written
>>> to ModemData.txt
>>> even the directions to use slmodemd seem correct.
>>>
>>
>> No user-removable USB devices or PCMCIA cards were connnected at the
>> time I ran scanModem.
>> The new ModemData.txt is on the bottom.
>>
>>> The logic in my scanModem script is not sophisticated enought to
>>> always succeed when there on two candidate COMM cards.
>>>
>>> But as I read it, there is an Agere chip
>>> CHIP=0x11c13026, hosted on the Subsystem of Âthe High Defintion Audio card
>>> with the real smarts in the Âslmodemd helper using the dynamically created
>>> SLMODEMD_DEVICE=hw:0,6
>>> corresponding to /dev/ttySL0 -> /dev/pts/2 (the real port)
>>>
>>> You can first try:
>>> $ lsmod
>>> to display drivers, then starting from the top of list, try removing
>>> non-essential drivers with
>>> $ sudo modprobe -r DriverNames
>>>
>>
>> How do I know which driver does what?
>>
>>> A first functionality test is detecting the modem with:
>>> $ sudo wvdialconf
>>>
>>
>> This is what I get:
>>
>> Editing `/etc/wvdial.conf'.
>>
>> Scanning your serial ports for a modem.
>>
>> Modem Port Scan<*1>: S0 Â S1
>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
>> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
>> Modem Port Scan<*1>: 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@xxxxxxxxxxxx>.
>>
>>> Try these and report back
>>>
>>> MarvS
>>> scanModem maintainer
>>> On Sun, Jan 23, 2011 at 2:15 AM, Fibonacci Prower
>>> <fibonacci.prower@xxxxxxxxx> wrote:
>>>> Hello.
>>>>
>>>> I'm trying to use the modem which came with my laptop to connect to
>>>> the internet. Unfortunately it's a winmodem, like most.
>>>> The output of scanModem (attached) is not clear enough as to which
>>>> driver should be used on this modem. I finally installed and
>>>> configured sl-modem-daemon - but I still don't know which country
>>>> should I specify, since Colombia (where I currently live) is not one
>>>> of the available options.
>>>> It appears, nevertheless, that my system is talking to the modem. I
>>>> can't connect to the internet, though, since I always get this message
>>>> with either Gnome-PPP or WvDial:
>>>>
>>>> --> WvDial: Internet dialer version 1.60
>>>> --> Cannot get information for serial port.
>>>> --> Initializing modem.
>>>> --> Sending: ATZ
>>>> ATZ
>>>> OK
>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
>>>> OK
>>>> --> Modem initialized.
>>>> --> Sending: ATM1L3DT019479472323
>>>> --> Waiting for carrier.
>>>> ATM1L3DT019479472323
>>>> NO CARRIER
>>>> --> No Carrier! Trying again.
>>>>
>>>> That happens even after I've set Carrier Check = no on wvdial.conf, so
>>>> I'm stuck here.
>>>>
>>>> After rebooting, I get the following error message from both Gnome-PPP
>>>> and WvDial:
>>>>
>>>> --> 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
>>>>
>>>> Problem is, /dev/ttySL0 is there and world-writable. OK, then, I'll
>>>> try restarting slmodemd:
>>>>
>>>> $ sudo slmodemd -c USA --alsa hw:0,6
>>>> error: locked memory limit too low:
>>>> error: need 8388608 bytes, have 65536 bytes
>>>> error: try 'ulimit -l 8192'
>>>>
>>>> Oh well. Since sudo ulimit doesn't work, I need to start a root shell,
>>>> THEN run the ulimit code suggested, THEN slmodemd -c USA --alsa
>>>> hw:0,6, and THEN... nothing. I'm right back at square one - no
>>>> carrier.
>>>>
>>>> Also: the exact same setup works under Windows XP, so I know there's
>>>> nothing wrong with my hardware.
>>>>
>>>> The full content of ModemData.txt follows:
>>>>
>>>> ÂOnly plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
>>>> Âas HTML can contain viruses. Use as the email Subject Line:
>>>>  YourName, YourCountry kernel 2.6.35-24-generic
>>>> ÂWith this Subject Line cogent experts will be alerted, and useful
>>>> case names left in the Archive.
>>>> ÂYourCountry will enable Country specific guidance. Linux experts in YourCountry
>>>> Âcan be found through: http://www.linux.org/groups/index.html.
>>>> They will know your Country's modem code, which may be essential for
>>>> dialup service.
>>>> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an
>>>> Internet Provider mail filters.
>>>> ÂSo in a day, also check the Archived responses at http://www.linmodems.org
>>>> --------------------------Â System information ----------------------------
>>>> CPU=i686, Ubuntu , ALSA_version=1.0.23
>>>> Linux version 2.6.35-24-generic (buildd@vernadsky) (gcc version 4.4.5
>>>> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #42-Ubuntu SMP Thu Dec 2 01:41:57
>>>> UTC 2010
>>>> ÂscanModem update of:Â 2010_12_12
>>>> The modem symbolic link is /dev/modem -> ttySL0
>>>> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2
>>>> Distrib_ID=Ubuntu
>>>> DistribCodeName=maverick
>>>> AptRepositoryStem=http://ubuntu.wikimedia.org/ubuntu/
>>>>
>>>>
>>>> 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 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
>>>> ÂID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface
>>>> [Integrated Module]
>>>> ÂID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270
>>>> HSDPA/HSUPA Modem
>>>> ÂID 0781:5406 SanDisk Corp. Cruzer Micro U3
>>>> If a cellphone is not detected, see
>>>> http://ubuntuforums.org/archive/index.php/t-878554.html
>>>> A sample report is:
>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
>>>>
>>>> If a USB modem or cellphone is attached and was not detected, please
>>>> provide available information in your request to discuss@xxxxxxxxxxxxx
>>>>
>>>> Candidate PCI devices with modem chips are:
>>>> 02:06.4 Communication controller: Texas Instruments PCIxx12 GemCore
>>>> based SmartCard controller
>>>> 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High
>>>> Definition Audio Controller (rev 01)
>>>> High Definition Audio cards can host modem chips.
>>>>
>>>> For candidate card in slot 02:06.4, firmware information and bootup
>>>> diagnostics are:
>>>> ÂPCI slotÂÂÂ PCI IDÂÂÂ ÂÂÂ SubsystemIDÂÂÂ Name
>>>> Â----------ÂÂÂ ---------ÂÂÂ ---------ÂÂÂ --------------
>>>> Â02:06.4ÂÂÂ 104c:803dÂÂÂ 103c:30acÂÂÂ Communication controller: Texas
>>>> Instruments PCIxx12 GemCore based SmartCard controller
>>>>
>>>> ÂModem interrupt assignment and sharing:
>>>> Â--- Bootup diagnostics for card in PCI slot 02:06.4 ----
>>>> [ÂÂÂ 0.293990] pci 0000:02:06.4: reg 10: [mem 0xe420a000-0xe420afff]
>>>> [ÂÂÂ 0.294000] pci 0000:02:06.4: reg 14: [mem 0xe420b000-0xe420bfff]
>>>> [ÂÂÂ 0.294070] pci 0000:02:06.4: supports D1 D2
>>>> [ÂÂÂ 0.294072] pci 0000:02:06.4: PME# supported from D0 D1 D2 D3hot
>>>> [ÂÂÂ 0.294078] pci 0000:02:06.4: PME# disabled
>>>>
>>>> ÂThe PCI slot 02:06.4 of the modem card may be disabled early in
>>>> Âa bootup process, but then enabled later. If modem drivers load
>>>> Âbut the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
>>>> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>>>> Âif help is needed.
>>>>
>>>>
>>>> For candidate card in slot 00:1b.0, firmware information and bootup
>>>> diagnostics are:
>>>> ÂPCI slotÂÂÂ PCI IDÂÂÂ ÂÂÂ SubsystemIDÂÂÂ Name
>>>> Â----------ÂÂÂ ---------ÂÂÂ ---------ÂÂÂ --------------
>>>> Â00:1b.0ÂÂÂ 8086:27d8ÂÂÂ 103c:30acÂÂÂ Audio device: Intel Corporation
>>>> N10/ICH 7 Family High Definition Audio Controller
>>>>
>>>> ÂModem interrupt assignment and sharing:
>>>> Â45:ÂÂÂÂÂ 16836ÂÂÂÂÂÂÂÂÂ 0ÂÂ PCI-MSI-edgeÂÂÂÂÂ hda_intel
>>>> Â--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>>>> [ÂÂÂ 0.290686] pci 0000:00:1b.0: reg 10: [mem 0xe4700000-0xe4703fff 64bit]
>>>> [ÂÂÂ 0.290750] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>>>> [ÂÂÂ 0.290755] pci 0000:00:1b.0: PME# disabled
>>>> [ÂÂ 28.827744] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
>>>> [ÂÂ 28.827779] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
>>>> [ÂÂ 28.827788] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
>>>> low) -> IRQ 16
>>>> [ÂÂ 28.827858] HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X
>>>> [ÂÂ 28.827891] HDA Intel 0000:00:1b.0: setting latency timer to 64
>>>>
>>>> ÂThe PCI slot 00:1b.0 of the modem card may be disabled early in
>>>> Âa bootup process, but then enabled later. If modem drivers load
>>>> Âbut the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
>>>> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>>>> Âif help is needed.
>>>>
>>>>
>>>> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>>>>
>>>> Predictive diagnostics for card in bus 02:06.4:
>>>>  Modem chipset detected on
>>>> NAME="Communication controller: Texas Instruments PCIxx12 GemCore
>>>> based SmartCard controller"
>>>> CLASS=0780
>>>> PCIDEV=104c:803d
>>>> SUBSYS=103c:30ac
>>>> IRQ=11
>>>> HDA2=00:1b.0
>>>> HDAchipVendorID=11c1
>>>> CHIP=0x11c13026
>>>> IDENT=slmodemd
>>>> SLMODEMD_DEVICE=hw:0,6
>>>> Driver=snd-hda-intel
>>>> package=agrsm-11c11040
>>>>
>>>> ÂFor candidate modem in:Â 02:06.4
>>>> ÂÂ 0780 Communication controller: Texas Instruments PCIxx12 GemCore
>>>> based SmartCard controller
>>>> ÂÂÂÂÂ Primary device ID:Â 104c:803d
>>>> ÂSupport type needed or chipset:ÂÂÂ slmodemd
>>>>
>>>>
>>>> ÂAn ALSA (Advanced Linux Sound Architecture) modem driver:Â snd-hda-intel
>>>> Â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_alsa1.0.23.tar.gz having a compiled
>>>> slmodemd. Unpack under Linux with:
>>>> ÂÂÂÂ $ tar zxf SLMODEMD_gcc4.4_alsa1.0.23.tar.gz
>>>> Âand read instructions therein. But briefly, the modem is setup with command:
>>>> ÂÂÂÂ sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6
>>>> Â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.
>>>>
>>>>
>>>> Writing DOCs/Intel.txt
>>>> Writing DOCs/Smartlink.txt
>>>> ============ end Smartlink section =====================
>>>>
>>>> The AgereSystems/LSI agrsm code supports compiling of a agrmodem +
>>>> agrserial driver pair.
>>>> There are a few different chipsets which use this driver pair, but
>>>> they use different code resources:
>>>> ChipsetsÂÂÂ ÂÂÂ ÂÂÂ KV*ÂÂÂ PackageNames (most current as of November 2009)
>>>> ----------------------------------------------------------------------------------------------
>>>> 11c1:048c and 11c1:048fÂÂÂÂÂÂÂÂ 2.6.29
>>>> agrsm048pci-2.1.60_20100108_i386.deb or
>>>> agrsm048pci-2.1.60_20100108.tar.gz
>>>> 11c1:0620ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 2.6.31
>>>> agrsm06pci-2.1.80_20100106_i386.deb or
>>>> agrsm06pci-2.1.80~20100106.tar.gz !!
>>>> 11c11040 (on HDA audio cards)ÂÂ 2.6.31
>>>> agrsm-11c11040_20091225_i386.deb or
>>>> agrsm-11c11040-2.1.80~20091225.tar.bz2Â !!
>>>> ÂÂ All available at:
>>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
>>>> Additionally there are;
>>>> automation & testingÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ agrsm-tools_0.0.1_all.deb or
>>>> agrsm-tools-0.0.1-2.noarch.rpm
>>>> General backgroundÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ agrsm_howto.txt
>>>> ------------------------------------------------------------------------------------------------
>>>> * KV == latest kernel release with a reported success
>>>> !! Latest update with major credit to Nikolay Zhuravlev
>>>> ÂÂ But see conflict issue:
>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html
>>>> ÂÂ For the 11c11040 chip with kernels 2.6.31 and later a change in a
>>>> modules loading settingmay be necessary.
>>>>  Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for
>>>> your Distro), change the phrase:
>>>> ÂÂÂÂÂ options snd-hda-intel power_save=10
>>>> ÂÂ to:
>>>> ÂÂÂÂÂ options snd-hda-intel power_save=0
>>>> ÂÂ or the agrsm drivers will not function. For Ubuntu related systems
>>>> this can be done with:
>>>> ÂÂ $ sudo gedit /etc/modprobe.d/alsa-base.conf
>>>>
>>>> Report from Bjorn Wielens:
>>>> Please note- trying to load the modules on a OpenSuSE 11.2 system gives
>>>> Âan error about the module_version symbol. Using:
>>>> # modprobe --force agrmodem
>>>> # modprobe --force agrserial
>>>> is necessary to load the drivers, and does not appear to cause ill effects.
>>>>
>>>>
>>>> All of the above packages are dkms competent. This means that if your
>>>> Linux distros dkms package
>>>> is previously installed, if provides for future updates matching
>>>> forthcoming kernels.
>>>>
>>>> -------------- end Agere Systems section -------------------
>>>>
>>>>
>>>> Predictive diagnostics for card in bus 00:1b.0:
>>>> ÂÂÂ Modem chipset not detected on
>>>> NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition
>>>> Audio Controller "
>>>> CLASS=0403
>>>> PCIDEV=8086:27d8
>>>> SUBSYS=103c:30ac
>>>> IRQ=45
>>>>
>>>> ÂFor candidate modem in:Â 00:1b.0
>>>> ÂÂ 0403 Audio device: Intel Corporation N10/ICH 7 Family High
>>>> Definition Audio Controller
>>>> ÂÂÂÂÂ Primary device ID:Â 8086:27d8
>>>> ÂSupport type needed or chipset:
>>>>
>>>>
>>>> ÂCompleted candidate modem analyses.
>>>>
>>>> ÂThe base of the UDEV device file system is: /dev/.udev
>>>>
>>>> ÂVersions adequately match for the compiler installed: 4.4.5
>>>> ÂÂÂÂÂÂÂÂÂÂÂÂ and the compiler used in kernel assembly: 4.4.5
>>>>
>>>> Âlinux-headers-2.6.35-24-generic resources needed for compiling are
>>>> not manifestly ready!
>>>>
>>>> ÂIf compiling is necessary packages must be installed, providing:
>>>> ÂÂÂ Âlinux-headers-2.6.35-24-generic
>>>>
>>>>
>>>> If a driver compilation fails, with message including some lack of
>>>> some FileName.h (stdio.h for example), then
>>>> Some additional kernel-header files need installation to /usr/include.
>>>> The minimal additional packages are libc6-dev
>>>> and any of its dependents, under Ubuntu linux-libc-dev
>>>>
>>>> If an alternate ethernet connection is available,
>>>> $Â apt-get update
>>>> $Â apt-get -s install linux-kernel-devel
>>>> will install needed packages.
>>>> For Debian/Ubuntu related distributions, run the following command to
>>>> display the needed package list:
>>>>
>>>> Otherwise packages have to be found through http://packages.ubuntu.com
>>>> Once downloaded and transferred into a Linux partition,
>>>> they can be installed alltogether with:
>>>> $ sudo dpkg -i *.deb
>>>>
>>>> Checking settings of:ÂÂÂ /etc/ppp/options
>>>> asyncmap 0
>>>> noauth
>>>> crtscts
>>>> lock
>>>> hide-password
>>>> modem
>>>> proxyarp
>>>> lcp-echo-interval 30
>>>> lcp-echo-failure 4
>>>> noipx
>>>>
>>>> In case of a message like:
>>>> ÂÂ Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
>>>> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
>>>>
>>>> For guidance on FAX usage, get from
>>>> http://linmodems.technion.ac.il/packages/Â; get faxing.tar.gz
>>>> It has samples for a modem using port /dev/ttySL0, which must be
>>>> changed to match your modem's port.
>>>>
>>>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth2 ppp0
>>>> Which can interfere with Browser naviagation.
>>>>
>>>> ÂDon't worry about the following, it is for experts should trouble
>>>> shooting be necessary.
>>>> ==========================================================
>>>>
>>>> ÂChecking for modem support lines:
>>>> Â--------------------------------------
>>>> ÂÂÂÂ /device/modem symbolic link:ÂÂ lrwxrwxrwx 1 root root 6
>>>> 2010-12-21 22:43 /dev/modem -> ttySL0
>>>> slmodemd created symbolic link /dev/ttySL0:Â lrwxrwxrwx 1 root root 10
>>>> 2010-12-21 22:43 /dev/ttySL0 -> /dev/pts/2
>>>> ÂÂÂÂ 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/sl-modem.conf:install slamr /sbin/modprobe -qb
>>>> ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e
>>>> /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) ||
>>>> (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout
>>>> /dev/slamr0)
>>>> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb
>>>> ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e
>>>> /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) ||
>>>> (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout
>>>> /dev/slusb0)
>>>> /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 --------
>>>>
>>>>
>>>> --
>>>> $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m",
>>>> chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',(
>>>> $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39"
>>>> ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz
>>>>
>>>
>>
>> This is ModemData.txt:
>>
>> ÂOnly plain text email is forwarded by the ÂDiscuss@xxxxxxxxxxxxx List Server,
>> Âas HTML can contain viruses. Use as the email Subject Line:
>> Â Â Â Â Â YourName, YourCountry Âkernel 2.6.35-25-generic
>> ÂWith this Subject Line cogent experts will be alerted, and useful
>> case names left in the Archive.
>> ÂYourCountry will enable Country specific guidance. Linux experts in
>> YourCountry
>> Âcan be found through: http://www.linux.org/groups/index.html.
>> They will know your Country's modem code, which may be essential for
>> dialup service.
>> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an
>> Internet Provider mail filters.
>> ÂSo in a day, also check the Archived responses at http://www.linmodems.org
>> -------------------------- ÂSystem information ----------------------------
>> CPU=i686, ÂUbuntu , ÂALSA_version=1.0.23
>> Linux version 2.6.35-25-generic (buildd@roseapple) (gcc version 4.4.5
>> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #43-Ubuntu SMP Thu Jan 6 22:25:16
>> UTC 2011
>> ÂscanModem update of: Â2010_12_12
>> The modem symbolic link is /dev/modem -> ttySL0
>> Distrib_ID=Ubuntu
>> DistribCodeName=maverick
>> AptRepositoryStem=http://ubuntu.wikimedia.org/ubuntu/
>>
>>
>> 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  slamr
>>
>> Attached USB devices are:
>> ÂID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
>> ÂID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface
>> [Integrated Module]
>> If a cellphone is not detected, see
>> http://ubuntuforums.org/archive/index.php/t-878554.html
>> A sample report is:
>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
>>
>> If a USB modem or cellphone is attached and was not detected, please
>> provide available information in your request to discuss@xxxxxxxxxxxxx
>>
>> Candidate PCI devices with modem chips are:
>> 02:06.4 Communication controller: Texas Instruments PCIxx12 GemCore
>> based SmartCard controller
>> 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High
>> Definition Audio Controller (rev 01)
>> High Definition Audio cards can host modem chips.
>>
>> For candidate card in slot 02:06.4, firmware information and bootup
>> diagnostics are:
>> ÂPCI slot    PCI ID     ÂSubsystemID   Name
>> Â---------- Â Â --------- Â Â Â --------- Â Â Â --------------
>> Â02:06.4    Â104c:803d    103c:30ac    Communication controller: Texas
>> Instruments PCIxx12 GemCore based SmartCard controller
>>
>> ÂModem interrupt assignment and sharing:
>> Â--- Bootup diagnostics for card in PCI slot 02:06.4 ----
>> [ Â Â0.287491] pci 0000:02:06.4: reg 10: [mem 0xe420a000-0xe420afff]
>> [ Â Â0.287502] pci 0000:02:06.4: reg 14: [mem 0xe420b000-0xe420bfff]
>> [ Â Â0.287572] pci 0000:02:06.4: supports D1 D2
>> [ Â Â0.287574] pci 0000:02:06.4: PME# supported from D0 D1 D2 D3hot
>> [ Â Â0.287580] pci 0000:02:06.4: PME# disabled
>>
>> ÂThe PCI slot 02:06.4 of the modem card may be disabled early in
>> Âa bootup process, Âbut then enabled later. If modem drivers load
>> Âbut the Âmodem is not responsive, read DOCs/Bootup.txt about possible fixes.
>> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>> Âif help is needed.
>>
>>
>> For candidate card in slot 00:1b.0, firmware information and bootup
>> diagnostics are:
>> ÂPCI slot    PCI ID     ÂSubsystemID   Name
>> Â---------- Â Â --------- Â Â Â --------- Â Â Â --------------
>> Â00:1b.0    Â8086:27d8    103c:30ac    Audio device: Intel Corporation N10/ICH 7
>> Family High Definition Audio Controller
>>
>> ÂModem interrupt assignment and sharing:
>> Â45:    1004     Â0  PCI-MSI-edge   Âhda_intel
>> Â--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>> [ Â Â0.284217] pci 0000:00:1b.0: reg 10: [mem 0xe4700000-0xe4703fff 64bit]
>> [ Â Â0.284281] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>> [ Â Â0.284286] pci 0000:00:1b.0: PME# disabled
>> [ Â 18.824476] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
>> [ Â 18.824512] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
>> [ Â 18.824522] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
>> low) -> IRQ 16
>> [ Â 18.824602] HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X
>> [ Â 18.824636] HDA Intel 0000:00:1b.0: setting latency timer to 64
>>
>> ÂThe PCI slot 00:1b.0 of the modem card may be disabled early in
>> Âa bootup process, Âbut then enabled later. If modem drivers load
>> Âbut the Âmodem is not responsive, read DOCs/Bootup.txt about possible fixes.
>> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>> Âif help is needed.
>>
>>
>> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>>
>> Predictive Âdiagnostics for card in bus 02:06.4:
>> Â Â Â ÂModem chipset Âdetected on
>> NAME="Communication controller: Texas Instruments PCIxx12 GemCore
>> based SmartCard controller"
>> CLASS=0780
>> PCIDEV=104c:803d
>> SUBSYS=103c:30ac
>> IRQ=11
>> HDA2=00:1b.0
>> HDAchipVendorID=11c1
>> CHIP=0x11c13026
>> IDENT=slmodemd
>> SLMODEMD_DEVICE=hw:0,6
>> Driver=snd-hda-intel
>> package=agrsm-11c11040
>>
>> ÂFor candidate modem in: Â02:06.4
>> Â 0780 Communication controller: Texas Instruments PCIxx12 GemCore
>> based SmartCard controller
>> Â Â ÂPrimary device ID: Â104c:803d
>> ÂSupport type needed or chipset: Â Â Â Âslmodemd
>>
>>
>> ÂAn ALSA (Advanced Linux Sound Architecture) modem driver: Âsnd-hda-intel
>> Â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_alsa1.0.23.tar.gz having a compiled
>> slmodemd. Unpack under Linux with:
>> Â Â Â Â$ tar zxf SLMODEMD_gcc4.4_alsa1.0.23.tar.gz
>> Âand read instructions therein. But briefly, the modem is setup with command:
>> Â Â Â Âsudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6
>> Â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.
>>
>>
>> Writing DOCs/Intel.txt
>> Writing DOCs/Smartlink.txt
>> ============ end Smartlink section =====================
>>
>> The AgereSystems/LSI agrsm code supports compiling of a agrmodem +
>> agrserial driver pair.
>> There are a few different chipsets which use this driver pair, but
>> they use different code resources:
>> Chipsets            ÂKV*   PackageNames (most current as of November 2009)
>> ----------------------------------------------------------------------------------------------
>> 11c1:048c and 11c1:048f
>> 2.6.29 Âagrsm048pci-2.1.60_20100108_i386.deb or
>> agrsm048pci-2.1.60_20100108.tar.gz
>> 11c1:0620 Â Â Â Â Â Â Â Â Â Â Â 2.6.31
>> agrsm06pci-2.1.80_20100106_i386.deb or
>> agrsm06pci-2.1.80~20100106.tar.gz !!
>> 11c11040 (on HDA audio cards) Â 2.6.31
>> agrsm-11c11040_20091225_i386.deb or
>> agrsm-11c11040-2.1.80~20091225.tar.bz2 Â!!
>> Â All available at:
>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/
>> Additionally there are;
>> automation & testing          Âagrsm-tools_0.0.1_all.deb or
>> agrsm-tools-0.0.1-2.noarch.rpm
>> General background           Âagrsm_howto.txt
>> ------------------------------------------------------------------------------------------------
>> * KV == latest kernel release with a reported success
>> !! Latest update with major credit to ÂNikolay Zhuravlev
>> Â But see conflict issue:
>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html
>> Â For the 11c11040 chip with kernels 2.6.31 and later a change in a
>> modules loading settingmay be necessary.
>> Â Within the file /etc/modprobe.d/alsa-base.conf Â(or equivalent for
>> your Distro), change the phrase:
>> Â Â Âoptions snd-hda-intel power_save=10
>> Â to:
>> Â Â Âoptions snd-hda-intel power_save=0
>> Â or the agrsm drivers will not function. For Ubuntu related systems
>> this can be done with:
>> Â $ sudo gedit /etc/modprobe.d/alsa-base.conf
>>
>> Report from ÂBjorn Wielens:
>> Please note- trying to load the modules on a OpenSuSE 11.2 system gives
>> Âan error about the module_version symbol. Using:
>> # modprobe --force agrmodem
>> # modprobe --force agrserial
>> is necessary to load the drivers, and does not appear to cause ill effects.
>>
>>
>> All of the above packages are dkms competent. ÂThis means that if your
>> Linux distros dkms package
>> is previously installed, if provides for future updates matching
>> forthcoming kernels.
>>
>> -------------- end Agere Systems section -------------------
>>
>>
>> Predictive Âdiagnostics for card in bus 00:1b.0:
>> Â Â Â ÂModem chipset not detected on
>> NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition
>> Audio Controller "
>> CLASS=0403
>> PCIDEV=8086:27d8
>> SUBSYS=103c:30ac
>> IRQ=45
>>
>> ÂFor candidate modem in: Â00:1b.0
>> Â 0403 Audio device: Intel Corporation N10/ICH 7 Family High
>> Definition Audio Controller
>> Â Â ÂPrimary device ID: Â8086:27d8
>> ÂSupport type needed or chipset:
>>
>>
>> ÂCompleted candidate modem analyses.
>>
>> ÂThe base of the UDEV device file system is: /dev/.udev
>>
>> ÂVersions adequately match for the compiler installed: 4.4.5
>> Â Â Â Â Â Â and the compiler used in kernel assembly: 4.4.5
>>
>> Âlinux-headers-2.6.35-25-generic resources needed for compiling are
>> not manifestly ready!
>>
>> ÂIf compiling is necessary packages must be installed, providing:
>> Â Â Â Â linux-headers-2.6.35-25-generic
>>
>>
>> If a driver compilation fails, with message including some lack of
>> some FileName.h (stdio.h for example), then
>> Some additional kernel-header files need installation to /usr/include.
>> The minimal additional packages are libc6-dev
>> and any of its dependents, under Ubuntu linux-libc-dev
>>
>> If an alternate ethernet connection is available,
>> $ Âapt-get update
>> $ Âapt-get -s install linux-kernel-devel
>> will install needed packages.
>> For Debian/Ubuntu related distributions, run the following command to
>> display the needed package list:
>>
>> Otherwise packages have to be found through http://packages.ubuntu.com
>> Once downloaded and transferred into a Linux partition,
>> they can be installed alltogether with:
>> $ sudo dpkg -i *.deb
>>
>>
>> Checking pppd properties:
>> Â Â Â Â-rwsr-xr-- 1 root dip 273248 2010-07-09 11:41 /usr/sbin/pppd
>>
>> In case of an "error 17" "serial loopback" problem, see:
>> Â Âhttp://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
>>
>> To enable dialout without Root permission do:
>> Â Â Â Â$ su - root Â(not for Ubuntu)
>> Â Â Â Âsudo chmod a+x /usr/sbin/pppd
>> or under Ubuntu related Linuxes
>> Â Â Â Âsudo chmod a+x /usr/sbin/pppd
>>
>> Checking settings of: Â /etc/ppp/options
>> asyncmap 0
>> noauth
>> crtscts
>> lock
>> hide-password
>> modem
>> proxyarp
>> lcp-echo-interval 30
>> lcp-echo-failure 4
>> noipx
>>
>> In case of a message like:
>> Â Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
>> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
>>
>> For guidance on FAX usage, get from
>> http://linmodems.technion.ac.il/packages/ Âget faxing.tar.gz
>> It has samples for a modem using port /dev/ttySL0, which must be
>> changed to match your modem's port.
>>
>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth2
>> Which can interfere with Browser naviagation.
>>
>> ÂDon't worry about the following, it is for experts should trouble
>> shooting be necessary.
>> ==========================================================
>>
>> ÂChecking for modem support lines:
>> Â--------------------------------------
>> Â Â /device/modem symbolic link: Â lrwxrwxrwx 1 root root 6
>> 2011-01-23 02:10 /dev/modem -> ttySL0
>> 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/sl-modem.conf:install slamr /sbin/modprobe -qb
>> ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e
>> /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) ||
>> (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout
>> /dev/slamr0)
>> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb
>> ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e
>> /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) ||
>> (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout
>> /dev/slusb0)
>> /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 --------
>>
>>
>> --
>> $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m",
>> chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',(
>> $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39"
>> ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz
>>
>



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

  Powered by Linux