Re: [Fwd: Re: Mulet CUBA 2.6.24-21-386]

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

 



Hi, I finally could fix the audio problems that appear trying to install
the modem. I went to

/etc/modprobe.d/alsa-base

and commented the following options

#options snd-atiixp-modem index=-2
#options snd-intel8x0m index=-2
#options snd-via82xx-modem index=-2

Of course, my modem is not working yet. Trying again modprobe I found once
more problems with the sound. Any idea?
Yours

Mulet


> Mulet
>
> Have you any idea what this is due to:
> [ 3094.053573] ALSA
> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/intel8x0.c:564:
> codec_read 0: semaphore is not ready for register 0x32
>
> It is a very unusual PATH for module drivers.
>
> MarvS
>
> On Sun, Oct 5, 2008 at 2:07 PM,  <mulet@xxxxxxxxxxxx> wrote:
>> Dear Antonio:
>>
>> I tried this, but it didn't work. Moreover, I just noted that now
>> (probably it happen before but i havent tried it then), I have problems
>> also with the sound drivers. I can't listen the music. In particular
>> gnome-mplayer gets stuck. Probably both stuff are connected and this
>> information may also help.
>>
>> Yours again
>>
>> Mulet
>>
>>
>>> Mulet,
>>>
>>> since lsmod shows three potential modules taking the modem slot:
>>>
>>> snd_atiixp_modem       16008  0
>>> snd_via82xx_modem      14984  0
>>> snd_intel8x0m          17804  0
>>>
>>> You can remove them
>>> $ sudo modprobe -r snd_atiixp_modem
>>> $ sudo modprobe -r snd_via82xx_modem
>>> $ sudo modprobe -r snd_intel8x0m
>>>
>>> and modrobe the last one back
>>> $ sudo modprobe snd_intel8x0m
>>>
>>> Then try slmodemd command back, it might work.  Marv usually advices
>>> this in some cases.  I hope it works, otherwise Marv will give you a
>>> better solution.
>>>
>>> Regards,
>>>
>>> Antonio
>>>
>>>
>>> On Sun, Oct 5, 2008 at 10:41 AM, Antonio Olivares
>>> <olivares14031@xxxxxxxxx> wrote:
>>>>
>>>> [   38.143116] ALSA
>>>> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:846:
>>>> Unable to initialize codec #0
>>>>
>>>> [   66.267687] ALSA
>>>> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/intel8x0.c:564:
>>>> codec_read 0: semaphore is not ready for register 0x2c
>>>> [   66.267699] ALSA
>>>> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/intel8x0.c:564:
>>>> codec_read 0: semaphore is not ready for register 0x20
>>>> [   68.220773] eth0: no IPv6 routers present
>>>> [ 3094.053561] ALSA
>>>> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/intel8x0.c:550:
>>>> codec_write 0: semaphore is not ready for register 0x32
>>>> [ 3094.053573] ALSA
>>>> /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-386/sound/alsa-driver/pci/intel8x0.c:564:
>>>> codec_read 0: semaphore is not ready for register 0x32
>>>>
>>>> lsmod shows several "modems" modules
>>>>
>>>> snd_atiixp_modem       16008  0
>>>> snd_via82xx_modem      14984  0
>>>> snd_intel8x0m          17804  0
>>>>
>>>> HTH,
>>>>
>>>> Marv hopefully can advice how to solve these issues.
>>>>
>>>> Antonio
>>>>
>>>>
>>>> --- On Sat, 10/4/08, mulet@xxxxxxxxxxxx <mulet@xxxxxxxxxxxx> wrote:
>>>>
>>>>> From: mulet@xxxxxxxxxxxx <mulet@xxxxxxxxxxxx>
>>>>> Subject: [Fwd: Re: Mulet CUBA 2.6.24-21-386]
>>>>> To: discuss@xxxxxxxxxxxxx
>>>>> Date: Saturday, October 4, 2008, 9:11 PM
>>>>> Attached you may find also the dmes.txt
>>>>>
>>>>> Thank you in advanced
>>>>>
>>>>>
>>>>> ---------------------------- Original Message
>>>>> ----------------------------
>>>>> Subject: Re: Mulet CUBA 2.6.24-21-386
>>>>> From:    "Antonio Olivares"
>>>>> <olivares14031@xxxxxxxxx>
>>>>> Date:    Sat, October 4, 2008 21:33
>>>>> To:      mulet@xxxxxxxxxxxx
>>>>> Cc:      discuss@xxxxxxxxxxxxx
>>>>> --------------------------------------------------------------------------
>>>>>
>>>>> Mulet,
>>>>>
>>>>> Please also forward this to list, they can see things that
>>>>> I might not
>>>>> see.  I do not know how to advice, but more users that have
>>>>> encountered this error before may be able to help.  You can
>>>>> also send
>>>>> us dmesg.txt, the part which recommends you do this:
>>>>>
>>>>>  Modem interrupt assignment and sharing:
>>>>>   10:        121    XT-PIC-XT        ehci_hcd:usb4,
>>>>> ohci1394, Intel
>>>>>  82801DB-ICH4, eth1
>>>>>   --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
>>>>>  [   10.155032] ACPI: PCI Interrupt 0000:00:1f.6[B] ->
>>>>> Link [LNKB] -> GSI
>>>>>  10 (level, low) -> IRQ 10
>>>>>  [   10.155041] ACPI: PCI interrupt for device 0000:00:1f.6
>>>>> disabled
>>>>>  [   37.890938] ACPI: PCI Interrupt 0000:00:1f.6[B] ->
>>>>> Link [LNKB] -> GSI
>>>>>  10 (level, low) -> IRQ 10
>>>>>  [   37.890958] PCI: Setting latency timer of device
>>>>> 0000:00:1f.6 to 64
>>>>>  [   38.143428] ACPI: PCI interrupt for device 0000:00:1f.6
>>>>> disabled
>>>>>  [   38.143576] Intel ICH Modem: probe of 0000:00:1f.6
>>>>> failed with error
>>>>>  -13
>>>>>
>>>>>  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@xxxxxxxxxxxxx
>>>>> if help is needed.
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Antonio
>>>>>
>>>>> On 10/4/08, mulet@xxxxxxxxxxxx <mulet@xxxxxxxxxxxx>
>>>>> wrote:
>>>>> > Antonio, I get the following error message. Any idea?
>>>>> >
>>>>> >
>>>>> > 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:2145:(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'
>>>>> >
>>>>> >
>>>>> >
>>>>> >> Mulet,
>>>>> >>
>>>>> >> Your modem is supported:
>>>>> >>
>>>>> >> 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.2.tar.gz having a
>>>>> compiled slmodemd. Unpack
>>>>> >> under Linux with:
>>>>> >>        $ tar zxf SLMODEMD.gcc4.2.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.
>>>>> >>
>>>>> >>
>>>>> >> However, you might run into trouble
>>>>> >>
>>>>> >>  Modem interrupt assignment and sharing:
>>>>> >>  10:        121    XT-PIC-XT        ehci_hcd:usb4,
>>>>> ohci1394, Intel
>>>>> >> 82801DB-ICH4, eth1
>>>>> >>  --- Bootup diagnostics for card in PCI slot
>>>>> 00:1f.6 ----
>>>>> >> [   10.155032] ACPI: PCI Interrupt 0000:00:1f.6[B]
>>>>> -> Link [LNKB] -> GSI
>>>>> >> 10 (level, low) -> IRQ 10
>>>>> >> [   10.155041] ACPI: PCI interrupt for device
>>>>> 0000:00:1f.6 disabled
>>>>> >> [   37.890938] ACPI: PCI Interrupt 0000:00:1f.6[B]
>>>>> -> Link [LNKB] -> GSI
>>>>> >> 10 (level, low) -> IRQ 10
>>>>> >> [   37.890958] PCI: Setting latency timer of
>>>>> device 0000:00:1f.6 to 64
>>>>> >> [   38.143428] ACPI: PCI interrupt for device
>>>>> 0000:00:1f.6 disabled
>>>>> >> [   38.143576] Intel ICH Modem: probe of
>>>>> 0000:00:1f.6 failed with error
>>>>> >> -13
>>>>> >>
>>>>> >>  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@xxxxxxxxxxxxx
>>>>> >>  if help is needed.
>>>>> >>
>>>>> >>
>>>>> >> Regards,
>>>>> >>
>>>>> >> Antonio
>>>>> >>
>>>>> >> On Thu, Oct 2, 2008 at 3:35 PM,
>>>>> <mulet@xxxxxxxxxxxx> wrote:
>>>>> >>> --------------------------  System information
>>>>> >>> ----------------------------
>>>>> >>> CPU=i686,
>>>>> >>> Linux version 2.6.24-21-386 (buildd@palmer)
>>>>> (gcc version 4.2.3 (Ubuntu
>>>>> >>> 4.2.3-2ubuntu7)) #1 Mon Aug 25 16:58:26 UTC
>>>>> 2008
>>>>> >>>  scanModem update of:  2008_08_26
>>>>> >>> The modem symbolic link is /dev/modem ->
>>>>> ttySL0
>>>>> >>>  There are no blacklisted modem drivers in
>>>>> /etc/modprobe*  files
>>>>> >>> Attached USB devices are:
>>>>> >>>  ID 04b4:6560 Cypress Semiconductor Corp.
>>>>> CY7C65640 USB-2.0 "TetraHub"
>>>>> >>>  ID 04d9:0499 Holtek Semiconductor, Inc.
>>>>> >>>
>>>>> >>> USB modems not recognized
>>>>> >>>
>>>>> >>> 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       1025:0051
>>>>>  Modem: Intel Corporation
>>>>> >>> 82801DB/DBL/DBM
>>>>> >>>
>>>>> >>>  Modem interrupt assignment and sharing:
>>>>> >>>  10:        121    XT-PIC-XT
>>>>> ehci_hcd:usb4, ohci1394, Intel
>>>>> >>> 82801DB-ICH4, eth1
>>>>> >>>  --- Bootup diagnostics for card in PCI slot
>>>>> 00:1f.6 ----
>>>>> >>> [   10.155032] ACPI: PCI Interrupt
>>>>> 0000:00:1f.6[B] -> Link [LNKB] -> GSI
>>>>> >>> 10 (level, low) -> IRQ 10
>>>>> >>> [   10.155041] ACPI: PCI interrupt for device
>>>>> 0000:00:1f.6 disabled
>>>>> >>> [   37.890938] ACPI: PCI Interrupt
>>>>> 0000:00:1f.6[B] -> Link [LNKB] -> GSI
>>>>> >>> 10 (level, low) -> IRQ 10
>>>>> >>> [   37.890958] PCI: Setting latency timer of
>>>>> device 0000:00:1f.6 to 64
>>>>> >>> [   38.143428] ACPI: PCI interrupt for device
>>>>> 0000:00:1f.6 disabled
>>>>> >>> [   38.143576] Intel ICH Modem: probe of
>>>>> 0000:00:1f.6 failed with error
>>>>> >>> -13
>>>>> >>>
>>>>> >>>  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@xxxxxxxxxxxxx
>>>>> >>>  if help is needed.
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> ===== Advanced Linux Sound Architecture (ALSA)
>>>>> diagnostics =====
>>>>> >>> The ALSA packages provide audio support and
>>>>> also drivers for some
>>>>> >>> modems.
>>>>> >>> ALSA diagnostics are written during bootup to
>>>>> /proc/asound/ folders.
>>>>> >>>
>>>>> >>> The ALSA verion is 1.0.16
>>>>> >>> The modem cards detected by "aplay
>>>>> -l"  are: None
>>>>> >>>
>>>>> >>>
>>>>> >>> The /proc/asound/pcm file reports:
>>>>> >>> -----------------------
>>>>> >>> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4
>>>>> - IEC958 : playback 1
>>>>> >>> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 -
>>>>> ADC2 : capture 1
>>>>> >>> 00-02: Intel ICH - MIC2 ADC : Intel
>>>>> 82801DB-ICH4 - MIC2 ADC : capture 1
>>>>> >>> 00-01: Intel ICH - MIC ADC : Intel
>>>>> 82801DB-ICH4 - MIC ADC : capture 1
>>>>> >>> 00-00: Intel ICH : Intel 82801DB-ICH4 :
>>>>> playback 1 : capture 1
>>>>> >>>
>>>>> >>> about /proc/asound/cards:
>>>>> >>> ------------------------
>>>>> >>>  0 [I82801DBICH4   ]: ICH4 - Intel
>>>>> 82801DB-ICH4
>>>>> >>>                      Intel 82801DB-ICH4 with
>>>>> ALC202 at irq 10
>>>>> >>> === Finished firmware and bootup diagnostics,
>>>>> next deducing cogent
>>>>> >>> software. ===
>>>>> >>>
>>>>> >>> Predictive  diagnostics for card in bus
>>>>> 00:1f.6:
>>>>> >>>        Modem chipset  detected on
>>>>> >>> NAME="Modem: Intel Corporation
>>>>> 82801DB/DBL/DBM "
>>>>> >>> CLASS=0703
>>>>> >>> PCIDEV=8086:24c6
>>>>> >>> SUBSYS=1025:0051
>>>>> >>> IRQ=10
>>>>> >>> SOFT=8086:24c6.MC97
>>>>> >>> CodecArchived=SIL27
>>>>> >>> IDENT=slmodemd
>>>>> >>> SLMODEMD_DEVICE=modem:1
>>>>> >>> Driver=snd-intel8x0m
>>>>> >>>
>>>>> >>>  For candidate modem in:  00:1f.6
>>>>> >>>   0703 Modem: Intel Corporation
>>>>> 82801DB/DBL/DBM
>>>>> >>>      Primary device ID:  8086:24c6
>>>>> >>>    Subsystem PCI_id  1025:0051
>>>>> >>>    Softmodem codec or chipset from
>>>>> diagnostics:
>>>>> >>>                               from
>>>>> Archives: SIL27
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> 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.2.tar.gz having a
>>>>> compiled slmodemd. Unpack
>>>>> >>> under Linux with:
>>>>> >>>        $ tar zxf SLMODEMD.gcc4.2.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.
>>>>> >>>
>>>>> >>> ----------------end Softmodem section
>>>>> --------------
>>>>> >>>
>>>>> >>> Writing DOCs/Intel.txt
>>>>> >>> 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.2.3
>>>>> >>>             and the compiler used in kernel
>>>>> assembly: 4.2.4
>>>>> >>>
>>>>> >>>  linux-headers-2.6.24-21-386 resources needed
>>>>> for compiling are not
>>>>> >>> manifestly ready!
>>>>> >>>
>>>>> >>>  If compiling is necessary packages must be
>>>>> installed, providing:
>>>>> >>>         linux-headers-2.6.24-21-386
>>>>> >>> Compressed files at: /usr/src/sl-modem.tar.bz2
>>>>> >>>
>>>>> >>>
>>>>> >>> If a driver compilation fails, with message
>>>>> including some lack of some
>>>>> >>> FileName.h (stdio.h for example), then
>>>>> >>> Some additional kernel-header files need
>>>>> installation to /usr/include.
>>>>> >>> The
>>>>> >>> minimal additional packages are libc6-dev
>>>>> >>> and any of its dependents, under Ubuntu
>>>>> linux-libc-dev
>>>>> >>>
>>>>> >>> If an alternate ethernet connection is
>>>>> available,
>>>>> >>> $  apt-get update
>>>>> >>> $  apt-get -s install linux-kernel-devel
>>>>> >>> will install needed packages.
>>>>> >>> For Debian/Ubuntu related distributions, run
>>>>> the following command to
>>>>> >>> display the needed package list:
>>>>> >>>
>>>>> >>> Otherwise packages have to be found through
>>>>> http://packages.ubuntu.com
>>>>> >>> Once downloaded and transferred into a Linux
>>>>> partition,
>>>>> >>> they can be installed alltogether with:
>>>>> >>> $ sudo dpkg -i *.deb
>>>>> >>>
>>>>> >>>
>>>>> >>> Checking pppd properties:
>>>>> >>>        -rwsr-xr-- 1 root dip 269256 2007-10-04
>>>>> 15:57 /usr/sbin/pppd
>>>>> >>>
>>>>> >>> In case of an "error 17"
>>>>> "serial loopback" problem, see:
>>>>> >>>
>>>>> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
>>>>> >>>
>>>>> >>> To enable dialout without Root permission do:
>>>>> >>>        $ su - root  (not for Ubuntu)
>>>>> >>>        sudo chmod a+x /usr/sbin/pppd
>>>>> >>> or under Ubuntu related Linuxes
>>>>> >>>        sudo chmod a+x /usr/sbin/pppd
>>>>> >>>
>>>>> >>> Checking settings of:   /etc/ppp/options
>>>>> >>> asyncmap 0
>>>>> >>> noauth
>>>>> >>> crtscts
>>>>> >>> lock
>>>>> >>> hide-password
>>>>> >>> modem
>>>>> >>> proxyarp
>>>>> >>> lcp-echo-interval 30
>>>>> >>> lcp-echo-failure 4
>>>>> >>> noipx
>>>>> >>>
>>>>> >>> In case of a message like:
>>>>> >>>   Warning: Could not modify
>>>>> /etc/ppp/pap-secrets: Permission denied
>>>>> >>> see
>>>>> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
>>>>> >>>
>>>>> >>> Read Modem/DOCs/YourSystem.txt concerning
>>>>> other COMM channels: eth0
>>>>> >>> Which can interfere with Browser naviagation.
>>>>> >>>
>>>>> >>>  Don't worry about the following, it is
>>>>> for experts should trouble
>>>>> >>> shooting be necessary.
>>>>> >>>
>>>>> ==========================================================
>>>>> >>>
>>>>> >>> # start/stop the daemon when the USB modem is
>>>>> connected
>>>>> >>> KERNEL=="slusb[0-9]*",
>>>>> GROUP="dialout",
>>>>> >>> RUN+="/etc/init.d/sl-modem-daemon"
>>>>> >>>  Checking for modem support lines:
>>>>> >>>  --------------------------------------
>>>>> >>>     /device/modem symbolic link:   lrwxrwxrwx
>>>>> 1 root root 6 2008-10-02
>>>>> >>> 11:21 /dev/modem -> ttySL0
>>>>> >>> slmodemd created symbolic link /dev/ttySL0:
>>>>> >>>     Within /etc/udev/ files:
>>>>> >>> /etc/udev/rules.d/030_sl-modem-daemon.rules:#
>>>>> start/stop the daemon when
>>>>> >>> the USB modem is connected
>>>>> >>>
>>>>> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>>>>> >>> GROUP="dialout",
>>>>> RUN+="/etc/init.d/sl-modem-daemon"
>>>>> >>> /etc/udev/sl-modem-daemon.rules:# start/stop
>>>>> the daemon when the USB
>>>>> >>> modem
>>>>> >>> is connected
>>>>> >>>
>>>>> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
>>>>> GROUP="dialout",
>>>>> >>> RUN+="/etc/init.d/sl-modem-daemon"
>>>>> >>>     Within /etc/modprobe.conf files:
>>>>> >>> /etc/modprobe.d/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
>>>>> >>>
>>>>> /etc/modprobe.d/sl-modem-daemon.modutils:install slamr
>>>>> modprobe
>>>>> >>> --ignore-install ungrab-winmodem ;  modprobe
>>>>> --ignore-install slamr;
>>>>> >>> test
>>>>> >>> -e /dev/slamr0 || (/bin/mknod -m 660
>>>>> /dev/slamr0 c 242 0 2>/dev/null &&
>>>>> >>> chgrp dialout /dev/slamr0)
>>>>> >>>     Within any ancient /etc/devfs files:
>>>>> >>>
>>>>> >>>     Within ancient kernel 2.4.n
>>>>> /etc/module.conf files:
>>>>> >>>
>>>>> >>> --------- end modem support lines --------
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> -----------------------------------------
>>>>> >>> This email was sent using SquirrelMail.
>>>>> >>>
>>>>> >>> --
>>>>> >>> This message has been scanned for viruses and
>>>>> >>> dangerous content by MailScanner, and is
>>>>> >>> believed to be clean.
>>>>> >>>
>>>>> >>>
>>>>> >>
>>>>> >> --
>>>>> >> This message has been scanned for viruses and
>>>>> >> dangerous content by MailScanner, and is
>>>>> >> believed to be clean.
>>>>> >>
>>>>> >
>>>>> >
>>>>> >
>>>>> > -----------------------------------------
>>>>> > This email was sent using SquirrelMail.
>>>>> >
>>>>> > --
>>>>> > This message has been scanned for viruses and
>>>>> > dangerous content by MailScanner, and is
>>>>> > believed to be clean.
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>>>> This message has been scanned for viruses and
>>>>> dangerous content by MailScanner, and is
>>>>> believed to be clean.
>>>>>
>>>>>
>>>>>
>>>>> -----------------------------------------
>>>>> This email was sent using SquirrelMail.
>>>>> --
>>>>> This message has been scanned for viruses and
>>>>> dangerous content by MailScanner, and is
>>>>> believed to be clean.
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by MailScanner, and is
>>> believed to be clean.
>>>
>>
>>
>>
>> -----------------------------------------
>> This email was sent using SquirrelMail.
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>



-----------------------------------------
This email was sent using SquirrelMail.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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

  Powered by Linux