Samer & Rob, The attachment has some details. First here is a success report for a problem of your type: http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00862.html Re: The folder "SLMODEMD.gcc4.2" is within my home directory. The only functional component is the slmodemd. Per the directions, it should be copied: $ sudo cp slmodemd /usr/sbin/ activated: $ sudo chmod +x /usr/sbin/slmodemd Now it is on the COMMAND path and you can do: $ slmodemd --help $ slmodemd --version And after the ALSA update hopefully installed a competent snd-hda-intel audio+modem driver, the modem would setup by $ sudo slmodemd -c GERMANY --alsa hw:0,6 with the 6 just being a current guess. New diagnostics will reveal the correct number is all else is OK the slmodemd within SLMODEMD.gcc4.2/ can then be deleted. But best to keep the residual informative text files re: Is slmodemd the same like sl-modem-daemon NO The sl-modem-daemon package is a set of scripts for automating driver loading and modem setup using slmodemd. It is only marginally useful even with a functioning snd-hda-intel driver, because this driver autoloads on boot in support of sound. Also sl-modem-daemon installs a version 2.9.9e slmodemd as contrasted to the version 2.9.11 in my SLMODEMD.4.2 package However automation is NOT desirable in the trouble shooting phase you are in, and would do NOTHING to alleviate the ALSA update situation RE: linux-image-2.6.24-18-generic There is no need to uninstall this kernel+modules package and associated files, And it would kill bootup for 2.6.24-18-generic If at all necessary to replace the component alsa drivers $ sudo dpkg -i linux-image-2.6.24-18-generic*.deb will simply replace the existing package, including the alsa drivers. While there is no harm in compiling in your home folder The typical place for compiling modules in in a folder of /urs/src/modules. For example on my System the are folders: $ ls /usr/src/modules/ /usr/src/modules/agrsm /usr/src/modules/alsa-1.0.16 /usr/src/modules/hsfmodem-7.68.00.06tst1oem /usr/src/modules/intel-537EP_secure-2.60.80.0 /usr/src/modules/madwifi-0.9.4 /usr/src/modules/martian-full-20071011 /usr/src/modules/martian-full-20080407 /usr/src/modules/martian-stephan /usr/src/modules/pctel-0.9.7-9-rht-9 /usr/src/modules/slmodem-2.9.11-20080401 /usr/src/modules/ungrab-winmodem-20080322 You can: $ sudo mkdir -p /usr/src/modules Then within your home folder $ sudo mv alsa /usr/src/modules $ sudo chown -R robert:robert /usr/src/modules which gives robert to act within: /usr/src/modules without using sudo. MarvS On Mon, Jun 9, 2008 at 7:36 AM, Robert Fischer <robertfischer@xxxxxxxxxxx> wrote: > Dear Marvin, > > may I ask you some very simple questions? > > 1) Where to put my tar.gz files for slmodemd/alsa and were to create the > appropriate folders: in my home directory, my desktop, the root directory or > somewhere else? > > The folder "SLMODEMD.gcc4.2" is within my home directory. The folders > "alsa-driver-1.0.16" + "alsa-lib-1.0.16" within a folder named "alsa" are on > my desktop. I coppied slmodemd into /usr/sbin/ and yesterday night I > installed alsa driver and alsa lib. There is still no sound and my modem > does not work. > > I do not like the folders (alsa and SLMODEMD.gcc4.2) on my desktop/home > directory. May I delet them? Does this prevent # make uninstall? > > 2) Is slmodemd the same like sl-modem-daemon? sl-modem-daemon is available > by synaptic and was suggested on ubuntuusers.de. > > 3) Searching for the term "generic" within synaptic there are: > linux-headers-2.6.24-16-generic > linux-headers-2.6.24-17-generic > linux-headers-2.6.24-18-generic > linux-image-2.6.24-16-generic > linux-image-2.6.24-17-generic > linux-image-2.6.24-18-generic > and others marked as installed. > > You suggested "You can simple reverse the install if desirable, by > reinstalling the package linux-image-2.6.24-18-generic". When I mark this > package for deinstallation in synaptic I am ask to deinstallate > linux-generic, linux-image-generic, > linux-restricted-modules-2.6.24-18-generic, linux-restricted-modules-generic > and linux-ubuntu-modules-2.6.24-18-generic". I have fear to accept. What > should be done with xxx-2.6.24-16-generic and xxx-2.6.24-17? > > With kind regards, > > Robert Fischer > > Because there is still no sound I tried within the folder alsa-driver-1.0.16 > # make uninstall > witch results in "Permission denied". I am not sure to repeat with sudo > command. > > -----Ursprüngliche Nachricht----- > Von: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] > Gesendet: Montag, 9. Juni 2008 03:55 > An: Robert Fischer > Betreff: Re: Fischer, Germany, kernel 2.6.24-16-generic > > Robert, > > With respect to your questions. > 1) Updating alsa will in no way hurt your System > the worst case is that sould will continue to not work. > Lots of folks have done this type of upgrade, with many thus acquiring > modem function > You can simple reverse the install if desirable, by reinstalling the > package > linux-image-2.6.24-18-generic , which will replace the original ALSA drivers > > 2) If you installed the alsa tarballs with Root permission , > you have to use > $ sudo COMMAND_NAME > to work inside those folders > . > Remember the HEADERS= definition has to be done with every reboot. > Probably also worth installing the packages bintutils and libc6-dev > as they way be needed in the compile. I don't know what is installed > on your System > > These can be found through: http://packages.ubuntu.com > Use the package search panel. After download to Linux, they can be > coinstalled with: > $ sudo dpkg -i *.deb > > MarvS > > > On Sun, Jun 8, 2008 at 9:45 AM, Robert Fischer > <robertfischer@xxxxxxxxxxx> wrote: >> Dear Marc, >> >> thank you for your Email. I understand that it might help to update the > alsa >> drivers. I read the Browse Instructions for upgrading snd-hda-intel and > its >> dependent driver set. Then I made the download of alsa-driver-1.0.16 and >> alsa-lib-1.0.16 and unpacked them in a folder named alsa on my desktop. >> >> Following the Instructions I run into the following error massage: >> marigold7@lenovo:~/Desktop/alsa$ >> HEADERS=/lib/modules/2.6.24-18-generic/build >> marigold7@lenovo:~/Desktop/alsa$ ls $HEADERS >> arch Documentation include Kbuild Makefile net security >> block drivers init kernel mm samples sound >> crypto fs ipc lib Module.symvers scripts usr >> marigold7@lenovo:~/Desktop/alsa$ cd alsa-driver-1.0.16 >> marigold7@lenovo:~/Desktop/alsa/alsa-driver-1.0.16$ ls >> acinclude.m4 hal2 pci SUPPORTED_KERNELS >> aclocal.m4 hgcompile pcmcia synth >> acore i2c ppc test >> alsa-kernel include README TODO >> aoa INSTALL Rules.make toplevel.config >> arm install-sh Rules.make1 toplevel.config.in >> CARDS-STATUS isa scripts usb >> configure kconfig-vers sh utils >> configure.in Makefile snddevices version >> COPYING Makefile.conf.in snddevices.in version.in >> cvscompile mips soc WARNING >> doc misc sound >> drivers modules sparc >> FAQ parisc support >> marigold7@lenovo:~/Desktop/alsa/alsa-driver-1.0.16$ make clean >> rm -f .depend *.o snd.map* >> rm -f /*.ver >> rm -f modules/*.o modules/*.ko >> make[1]: Betrete Verzeichnis >> '/home/marigold7/Desktop/alsa/alsa-driver-1.0.16/acore' >> Makefile:6: /home/marigold7/Desktop/alsa/alsa-driver-1.0.16/Makefile.conf: >> No such file or directory >> /home/marigold7/Desktop/alsa/alsa-driver-1.0.16/Rules.make:75: > /Rules.make1: >> No such file or directory >> make[1]: *** Keine Regel, um »/Rules.make1« zu erstellen. Schluss. >> make[1]: Verlasse Verzeichnis >> '/home/marigold7/Desktop/alsa/alsa-driver-1.0.16/acore' >> make: *** [clean] Fehler 1 >> marigold7@lenovo:~/Desktop/alsa/alsa-driver-1.0.16$ >> >> What is wrong? >> >> I think at this stage I should pronounce that I only want to use my >> computer. I do not want to become an expert. However, to use my computer I >> think that sound and modem were essential. Presently, I see two options: >> a) erase Ubuntu from my hard disk and never use linux again >> b) to solve the two problems and then not to touch the running system for >> the next three years >> >> Yesterday, I opend synaptic, followed the help links and wrote: >> >> "Dear Ladies and Gentlemen, >> >> attached is one letter probably giving the solution of my problem, but I >> feel unable to perform the suggested set up. I am new with Linux/Ubuntu > and >> I would prefer using the updates by synaptic. >> >> It was told me that my ALSA drivers were not mature for my sound card and >> that I should go to the ALSA homepage and download the current driver and >> lib packages. Going to the suggested web page http://www.alsa-project.org/ > I >> have found: >> >> Driver (alsa-driver) 1.0.16 Kernel drivers >> Firmware (alsa-firmware)1.0.16 Firmware for cards that require it >> Library (alsa-lib) 1.0.16 Userspace library >> Plugins (alsa-plugins) 1.0.16 Additional library plugins >> Eg.jack, pulse, maemo ... >> Utilities (alsa-utils) 1.0.16 Utilities >> aplay,arecord,amixer etc >> Tools (alsa-tools) 1.0.16 Tools >> PyALSA (pyalsa) 1.0.16 Python bindings > for >> ALSA lib >> OSS compat lib(alsa-oss)1.0.15 OSS compatibility library >> >> Looking into synaptic with the key word "alsa" there were packages like: >> (alsa-firmware) 1.0.15-2ubuntu4 >> (alsa-utils) 1.0.15-3ubuntu2 >> (alsa-tools) 1.0.15-2ubuntu4 >> (alsa-oss) 1.0.15-1 >> >> As you see the version for ALSA is 1.0.16 but using synaptic only 1.0.15. >> >> I would feel very uncomfortable to do the manipulation (compilations) on a >> running system. All trials I have done so far ended in error messages. I >> have a big lack in knowledge (e. g. I do not know basics like were to put >> the decompressed files - to the desktop, my home or root directory). >> >> Therefore I feel better to wait until the updates were available by >> synaptic. >> >> Please tell me, who is responsible for maintaining the updates or forward > my >> report to this person. Here, I describe not a real bug but my notebook > gives >> no sound / failure to use slmodemd. How long it will probably take to get >> the required ALSA update by synaptic? >> >> With best wishes, >> >> Robert Fischer" >> >> Todays answer was: " Hi, >> >> Thanks for your report. As this is more of a query than a bug, I will be >> closing the bug. See below for an explanation of Ubuntu's development >> process. >> >> Ubuntu works by building on the work of the Debian distribution >> (www.debian.org). Every six months the Ubuntu developers mirror the > packages >> in Debian Unstable. Ubuntu developers then make sure the packages are >> useable and polished. At a certain point the packages are "freezed" and no >> longer accept updates. >> >> This happens every six months. >> >> Inclusion of Alsa 1.0.16 depends on if Debian Unstable have it, or if it > has >> features that the Ubuntu developers see as critical. I have checked the >> Debian Unstable package list and alsa 1.0.16 is there, so the best answer > I >> can give is that it should be included in the next version of Ubuntu >> (Intrepid Ibex). Once Intrepid Ibex is out the new version of Alsa will be >> installed by default. >> >> Lookin at the Alsa page on Launchpad there does not seem to be a single >> person responsible for Alsa in ubuntu but a few contributors >> (https://launchpad.net/alsa). If you have more concerns then I suggest you >> contact one of them. >> >> Kind Regards," >> >> Furthermore, I tried to ask questions in the ubuntuusers.de forum (I am >> speaking German): >> http://forum.ubuntuusers.de/topic/179101/?highlight= >> http://forum.ubuntuusers.de/topic/179059/?highlight= >> >> There is help but it does not solve my problems. Your answer makes sense > but >> I am unable to resolve it. I am not an expert. >> >> With best wishes, >> >> Robert Fischer >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] >> Gesendet: Dienstag, 3. Juni 2008 00:58 >> An: marigold7 >> Cc: Discuss@xxxxxxxxxxxxx >> Betreff: Re: Fischer, Germany, kernel 2.6.24-16-generic >> >> For >> Predictive diagnostics for card in bus 00:1b.0: >> Modem chipset detected on >> CLASS="Class 0403: 8086:284b" >> NAME="Audio device: Intel Corporation 82801H " >> SUBSYS=17aa:384e >> PCIDEV=8086:284b >> IRQ=22 >> HDA=8086:284b >> SOFT=8086:284b.HDA >> CodecArchived=10573055 >> ArchivedChip=0x10573055 >> IDENT=slmodemd >> >> Your modem should in principle be supported by the snd-hda-intel >> audio+modem driver, complemented by: >> $ sudo slmodemd -c GERMANY --alsa hw:0,1 (or 6) >> >> however your audio problems and lack of a modem line in: >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-00: ALC861VD Analog : ALC861VD Analog : playback 1 : capture 1 >> whereas >> 00-01 (or 06) would be expected for a functional modem. >> >> Indicates that ALSA support is not yet mature for ALC861VD Analog >> Browse Instructions for upgrading snd-hda-intel and its dependent >> driver set are at: >> http://linmodems.technion.ac.il/archive-seventh/msg00282.html about >> upgrading your ALSA version to the version 1.0.16 with resources at >> http://www.alsa-project.org/main/index.php/Main_Page >> >> MarvS >> scanModem maintainer >> >> >> On Mon, Jun 2, 2008 at 2:32 PM, marigold7 <marigold7@xxxxxxxxxx> wrote: >>> Dear Ladies and Gentlemen, >>> >>> currently, I have two problems: >>> 1)my computer does not gives any sound from it >>> 2)my modem seems to work not properly (attached is the ModemData.txt > file) >>> >>> ------------------------------------------------------------------- >>> At first I tried to get the modem running: >>> a) scanModem >>> >>> b) http://linmodems.technion.ac.il/packages/smartlink/ >>> $ tar zxf slmodemd.gcc4.2.tar.gz >>> >>> c) folder slmodemd.gcc4.2 containing slmodemd >>> sudo cp slmodemd /usr/sbin/ >>> sudo g+x /usr/sbin/slmodemd >>> sudo o+x /usr/sbin/slmodemd >>> >>> d) sudo slmodemd -c GERMANY --alsa modem:1 >>> results in: >>> error: mixer setup: attach hw:1 error: No such file or directory >>> ALSA lib confmisc.c:768:(parse_card) cannot find card '1' >>> ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_card_driver >>> returned error: No such file or directory >>> ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings >>> ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_concat >>> returned error: No such file or directory >>> ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name >>> ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_refer >> returned >>> error: No such file or directory >>> ALSA lib conf.c:3985:(snd_config_expand) Evaluate error: No such file or >>> directory >>> ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM >>> cards.pcm.phoneline:CARD=1,DEV=0 >>> error: alsa setup: cannot open playback device 'modem:1': No such file or >>> directory >>> error: cannot setup device `modem:1' >>> >>> Then I tried, >>> e) sudo modprobe -r snd-intel8x0m >>> sudo modprobe snd-intel8x0m >>> >>> f) sudo alsamixer >>> >>> g) sudo gedit /etc/modules >>> and I put snd-intel8x0m at the end of the list (later I removed it > because >>> there was still no sound) >>> >>> h) then I have found a useful hint in the 1stRead.txt document belonging >> to >>> the slmodemd: "There are RARE instances that the ALSA audio sound driver >> is >>> absent, though the modem driver is present. In these cases the device >> name >>> "modem:1" may fail but "hw:0" may be successful. It is the usually the >>> device name dynamically assigned to the audio card." >>> >>> sudo slmodemd -c GERMANY --alsa hw:0 >>> produced: >>> [sudo] password for marigold7: >>> error: mixer setup: Off-hook switch not found for card hw:0 >>> SmartLink Soft Modem: version 2.9.11 Feb 25 2008 18:25:57 >>> symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. >>> modem `hw:0' created. TTY is `/dev/pts/1' >>> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >>> >>> It seems that the modem is running. BUT I HAVE THE FOLLOWING PROBLEM WITH >>> IT: WHY THE MODEM IS NOT USING modem1? IS THERE REALLY NO ALSA AUDIO > SOUND >>> DRIVER??? >>> >>> Then, using wvdial there was some failure: >>> marigold7@lenovo:/$ sudo 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 >>> --> Sending: AT+GCI=<hexadecimal modem code> >>> AT+GCI=<hexadecimal modem code> >>> ERROR >>> --> Bad init string. >>> >>> >>> remark to g): >>> in /etc/modprobe.d/alsa-base I read: >>> # Prevent abnormal drivers from grabbing index 0 >>> options bt87x index=-2 >>> options cx88_alsa index=-2 >>> options saa7134-alsa index=-2 >>> options snd-atiixp-modem index=-2 >>> options snd-intel8x0m index=-2 >>> >>> What means index=-2 ? >>> ------------------------------------------------------------------------ >>> I am more dependent from the sound on my machine. Here, I tried the >>> following: >>> a) $ sudo modprobe snd-hda-intel >>> seems to be OK >>> >>> b) $ alsamixer >>> alsamixer appears, it is possible to change the parameters >>> >>> c) $ sudo gedit /etc/modules >>> I put >>> snd-hda-intel model=lenovo index=0 >>> at the end of the list >>> >>> d) $ sudo gedit /etc/modprobe.d/alsa-base >>> I put >>> options snd-hda-intel model=lenovo >>> at the end of the list >>> >>> e) I installed pulseaudio, libasound2-plugins, pavucontrol, paprefs >>> and made >>> $ asoundconf set-pulseaudio >>> >>> PulseAudio Volume Control shows: >>> Playback: "No Streams Available" >>> Output Devices: ALSA PCM on front:0 (ALC861VD Analog) via DMA >>> Input Devices: ALSA PCM on front:0 (ALC861VD Analog) via DMA >>> >>> All attemps to get sound out of my laptop failed? Please, can you help > me. >>> >>> With best wishes, >>> >>> Robert Fischer >>> (marigold7) >>> >>> >>> ------------------------------------------------------------------------ >>> To provide you with some details concerning my laptop I have done: >>> >>> marigold7@lenovo:~$ hwinfo --sound >>> 28: PCI 1b.0: 0403 Audio device >>> [Created at pci.296] >>> UDI: /org/freedesktop/Hal/devices/pci_8086_284b >>> Unique ID: u1Nb.cOzUFd_gaWF >>> SysFS ID: /devices/pci0000:00/0000:00:1b.0 >>> SysFS BusID: 0000:00:1b.0 >>> Hardware Class: sound >>> Model: "Lenovo HD Audio Controller" >>> Vendor: pci 0x8086 "Intel Corporation" >>> Device: pci 0x284b "HD Audio Controller" >>> SubVendor: pci 0x17aa "Lenovo" >>> SubDevice: pci 0x384e >>> Revision: 0x03 >>> Driver: "HDA Intel" >>> Driver Modules: "snd_hda_intel" >>> Memory Range: 0xfc300000-0xfc303fff (rw,non-prefetchable) >>> IRQ: 22 (944 events) >>> Module Alias: "pci:v00008086d0000284Bsv000017AAsd0000384Ebc04sc03i00" >>> Driver Info #0: >>> Driver Status: snd_hda_intel is active >>> Driver Activation Cmd: "modprobe snd_hda_intel" >>> Config Status: cfg=new, avail=yes, need=no, active=unknown >>> >>> marigold7@lenovo:~$ lspci -vvxxx >>> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio >>> Controller (rev 03) >>> Subsystem: Lenovo Unknown device 384e >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- >>> Stepping- SERR+ FastB2B- >>> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- >>> <TAbort- <MAbort- >SERR- <PERR- >>> Latency: 0, Cache Line Size: 64 bytes >>> Interrupt: pin A routed to IRQ 22 >>> Region 0: Memory at fc300000 (64-bit, non-prefetchable) [size=16K] >>> Capabilities: <access denied> >>> 00: 86 80 4b 28 06 01 10 00 03 00 03 04 10 00 00 00 >>> 10: 04 00 30 fc 00 00 00 00 00 00 00 00 00 00 00 00 >>> 20: 00 00 00 00 00 00 00 00 00 00 00 00 aa 17 4e 38 >>> 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 0 >>> >>> >>> >> >> > >
The accumulated experience we have with cases like yours can be easily summarized. When a modem on a HIgh Definition Audio (HDA) card is not working reliably, try upgrading the driver to a more recent release. The snd-hda-intel driver is being continually improved, and some List members have acquired reliable function through driver upgrades. After an upgrade if the problem persists, a bug report should be sent to the snd-hda-intel maintainer at ALSA Here is a success report: http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00862.html Here at the upgrade instructions for a Ubuntu System Check for the presence of two necessary packages on your System with $ sudo apt-get install binutils libc6-dev whose output on my System includes: ------------- binutils is already the newest version. libc6-dev is already the newest version. ------------- If not similarly reported on your System, these packages must be installed For Debian/Ubuntu linux-libc-dev must be installed as a dependent of libc6-dev It not on your install CD, they can be searched out at http://packages.ubuntu.com Once downloaded and copied into your Linux partition, all can be co-installed with: $ sudo *.deb Make a working folder $ sudo mkdir -p /usr/src/modules/alsa Assuming your login name is John, $ sudo chown -R john:john /usr/src/modules/ This make it permissible to work therein without "sudo" thereafter in modules/ and its sub folders You will need to download from http://www.alsa-project.org/main/index.php/Main_Page the current stable packages, now the alsa-driver-1.0.16 and alsa-lib-1.0.16 $ cd /usr/src/modules/alsa to unpack therein. Prefix the PATH_to the package, to unpack with commands: $ tar jxf PATH_to/alsa-driver*.tar.bz2 $ tar jxf PATH_to/alsa-lib*.tar.bz2 with the j calling the needed bunzip2 action. Move into the driver folder $ cd alsa-driver-1.0.16 where the work will be done, with calls to the parallel alsa-lib-1.0.16/ folder Browse a bit. Set a useful termporary defintion HEADERS=/lib/modules/2.6.22-14-generic/build Check for validity with: $ ls $HEADERS should show files like: arch include lib scripts block init Makefile security crypto ipc mm sound drivers fs kernel net usr ---------------- This definition does not survive a shutdown and must be redone upon reboot, when a new driver compiling is necessary. $ make clean Do the configuration with with the following command on ONE LINE: $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel Get some coffee while it runs. If the configuration is successful, the driver set will be compiled with: $ make Get more coffee. When completed the replacement driver set is displayed by: $ ls modules and installed by $ sudo make install Then reboot to have the new drivers used. Run again: $ ./scanModem If all is well, the diagnostics will instruct the number N to use in a modem activation line like: $ sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,N MarvS
