Bernhard, See guidance below are replacing your snd-hda-intel and dependent drivers. I expect this will cure the Motorola chipset problems. Please report back. MarvS On 6/5/07, Bernhard Bauer <Bernhard-Bauer@xxxxxx> wrote:
Hello, I have seen, that www.alsa-project.org has released their new stable release 1.0.14. My question: Does the hda-modem Motorola work with alsa-driver 1.0.14 and alsa-lib 1.0.14 and how install it? Is their also a patch necessary? Yours sincerely Bernhard Bauer
On 5/30/07, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
Ste, A set of several drivers which snd-hda-intel depends on also has to be replaced Here is the procedure for ALSA release 1.0.2, and could be similarly followed for say 1.0.14rc3 From http://www.alsa-project.org/ get the version 1.0.2 driver and lib packages. Make a folder, say alsa/. $ mkdir alsa Unpack both packages in the alsa/ folder $ tar jxf alsa*.tar.bz2 will unpack both. To compile the driver set, move into the driver folder: $ cd alsa-driver-1.0.12 Look around: $ ls $ make clean Make a transient (must be redone after a reboot) definition HEADERS=/lib/modules/2.6.20-15-generic/build Check with $ ls $HEADERS the base of the linux-headers folder should be displayed Do the configuration with with the following command on ONE LINE: $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel If the configuration is successful, the driver set will be compiled with: $ make Do nothing in the alsa-lib-1.0.12/ folder. But it is used during the compile. The new driver set is displayed by: $ ls modules and installed by $ sudo make install THen reboot to have the new drivers used. as the existing set usually cannot be unloaded. MarvS On 5/30/07, ste <ste@xxxxxxxxxxxxxxxxx> wrote: > Hello Marvin, > > I replaced snd-hda-intel.ko with the one from the edgy partition (alsa > 1.0.11) with the result that sound was broken at all and slmodem did not > find hw:0,6 and produced three lines of errors... > > regards and thanks for now > > ste > > Marvin Stodolsky ha scritto: > > Ste, > > > > If you are using the slmodemd from SLMODEMD-1.0.13.tar.gz, then > >> error: period size 48 is not supported by playback (64) > > This seems to be a bug arising within the ALSA 1.0.13 release. > > Your report is the most complete we have received, so please file a > > bug report through http://www.alsa-project.org/ > > > > In the mean time you can replace your snd-hda-intel.ko + complementing > > drivers > > with those compiled from 1.0.12 code or the most recent 1.0.14rcN > > release. > > > > I recall you have already done such replacement processes, but inform > > me if you need the instuctions again. > > > > Please report back on the results of your tests. > > > > MarvS > > > > On 5/27/07, ste <ste@xxxxxxxxxxxxxxxxx> wrote: > >> Hello everybody, > >> > >> the internal modem worked well (but only at 33600) with edgy eft and > >> slmodemd and now with feisty I get a list of this error (one for every > >> dialing attempt) while wvdial ( same .conf with carrier check = off) > >> gives "no carrier" messages very fastly: > >> error: period size 48 is not supported by playback (64) > >> error: period size 48 is not supported by playback (64) > >> error: period size 48 is not supported by playback (64) > >> > >> Browsed your archives but I didn' find a solution. Alsa version is > >> 1.0.13 > >> Thanks for help. > >> > >> stefano > >> > >> -------------------------- System information > >> ---------------------------- > >> CPU=i686, Ubuntu 7.04 > >> Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2 (Ubuntu > >> 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007 > >> scanModem update of: 2007_May_11 > >> The modem symbolic link is /dev/modem -> ttySL0 > >> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2 > >> > >> ALSAversion 1.0.13 > >> USB modem not detected by lsusb > >> > >> Modem or host audio card candidates have firmware information: > >> > >> PCI slot PCI ID SubsystemID Name > >> ---------- --------- --------- -------------- > >> 00:1b.0 8086:27d8 1179:0001 Audio device: Intel Corporation > >> 82801G > >> > >> Modem interrupt assignment and sharing: > >> 23: 9828 0 IO-APIC-fasteoi HDA Intel > >> > >> --- Bootup diagnositcs for card in PCI slot 00:1b.0 ---- > >> [ 15.080000] PCI: Enabling device 0000:00:1b.0 (0000 -> 0002) > >> [ 15.080000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, > >> low) -> IRQ 23 > >> [ 15.080000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > >> > >> === Finished modem firmware and bootup diagnostics section. === > >> === Next deducing cogent software === > >> > >> 8086:27d8 is a High Definition Audio card, possibly hosting a soft > >> modem. > >> HDAmodemChip=0x11c13026 > >> For candidate modem in PCI bus: 00:1b.0 > >> Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > >> Primary PCI_id 8086:27d8 > >> Subsystem PCI_id 1179:0001 > >> Softmodem codec or Vendor from diagnostics: > >> from Archives: 11c1, an AgereSystems > >> type. > >> The HDA card softmodem chip is 0x11c13026 > >> > >> Lacking a dsp (digital signal processing) chip, the modem is a software > >> intensive or "softmodem" type. Its primary controller manages the > >> traffic > >> with the CPU. But the software needed is specified in the Subsystem. > >> ----------------------------------------- > >> 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-1.0.13.tar.gz having a compiled slmodemd. Unpack > >> under Linux with: > >> $ tar zxf SLMODEMD-1.0.13.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 Smartlink.txt and Modem/YourSystem.txt for follow through > >> guidance. > >> > >> #this worked well on edgy eft > >> > >> Already loaded into the kernel is snd-hda-intel and audio drivers it > >> depends on, > >> displayed by: lsmod | grep snd_hda_intel > >> Module Size Used by > >> ------------------------------------- > >> snd_hda_intel 21912 7 > >> snd_hda_codec 205440 1 snd_hda_intel > >> snd_pcm 79876 10 > >> snd_atiixp_modem,snd_via82xx_modem,snd_intel8x0m,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm_oss > >> > >> snd 54020 24 > >> snd_atiixp_modem,snd_via82xx_modem,snd_intel8x0m,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device > >> > >> snd_page_alloc 10888 5 > >> snd_atiixp_modem,snd_via82xx_modem,snd_intel8x0m,snd_hda_intel,snd_pcm > >> > >> > >> The diagnostic outputs for this softmodem section have their raw > >> information in > >> folders and text files under /proc/asound/ which you can browse. The > >> information > >> is from files: > >> /proc/asound/pcm > >> ------------------------------- > >> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 > >> 00-02: ALC262 Analog : ALC262 Analog : capture 2 > >> 00-00: ALC262 Analog : ALC262 Analog : playback 1 : capture 2 > >> > >> /proc/asound/modules > >> ------------------------------- > >> 0 snd_hda_intel > >> and from the command: > >> aplay -l | grep -i modem > >> scheda 0: Intel [HDA Intel], dispositivo 6: Si3054 Modem [Si3054 Modem] > >> > >> ----------------end Softmodem section -------------- > >> > >> Writing Intel.txt > >> The modem is supported by the Smartlink slamr driver > >> plus the slmodemd helper utility. Read the > >> Smartlink.txt and Modem/YourSystem.txt for follow through guidance. > >> > >> Writing 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.1.2 > >> and the compiler used in kernel assembly: 4.1.2 > >> > >> Kernel-header resources needed for compiling are not manifestly ready! > >> > >> If compiling is necessary packages must be installed, providing: > >> linux-headers-2.6.20-15-generic > >> > >> > >> Checking pppd properties: > >> -rwsr-xr-- 1 root dip 269224 2007-04-05 05:41 /usr/sbin/pppd > >> > >> In case of an "error 17" "serial loopback" problem, see: > >> http://phep2.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 > >> auth > >> crtscts > >> lock > >> hide-password > >> modem > >> mru 542 > >> proxyarp > >> lcp-echo-interval 30 > >> lcp-echo-failure 10 > >> 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/YourSystem.txt concerning other COMM channels: eth0 eth0:avah > >> Which can interfere with Browser naviagation. > >> > >> Don't worry about the following, it is for the experts > >> should trouble shooting be necessary. > >> ========================================================== > >> > >> # start/stop the daemon when the USB modem is connected > >> KERNEL=="slusb[0-9]*", GROUP="dialout", > >> RUN+="/etc/init.d/sl-modem-daemon" > >> Checking for modem support lines: > >> -------------------------------------- > >> /device/modem symbolic link: lrwxrwxrwx 1 root root 6 2007-05-23 > >> 21:38 /dev/modem -> ttySL0 > >> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 > >> 2007-05-23 21:40 /dev/ttySL0 -> /dev/pts/2 > >> Within /etc/udev/ files: > >> /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when > >> the USB modem is connected > >> /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > >> GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > >> /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB > >> modem is connected > >> /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", > >> RUN+="/etc/init.d/sl-modem-daemon" > >> Within /etc/modprobe.conf files: > >> /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > >> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > >> /etc/modprobe.d/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) > >> /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 -------- > >> > >> > > > > > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - > www.vogliaditerra.com/ > > Photoblog: www.vogliaditerra.com/photoblog.html > > skype: contadinoste > >
