Manuel Get the packages linux-headers-2.6.18-4 and linux-headers-2.6.18-4-686If they are on the install disks your can:# apt-get install linux-headers-2.6.18-4-686 If not get them through http://www.debian.org/distrib/packages/use the Search uitlity.After downloading they can be installed with:$ su - root# dpkg -i linux-headers* The headers install to /usr/include/linux-headers-2.6.18-4-686 /usr/include/linux-headers-2.6.18-4 Alternatively you could make headers by:$ su - root# cd /usr/src/# tar jxf linux-source-2.6.18.tar.bz2# cd linux-source-2.6.18Look aound:# ls -a# make mrproper# cp /boot/config-2.6.18-4-686 .configand be sure to include the . before the config.# make oldconfigThus configured, it will take a long time to:# make bzImage If successful set a symbolic link# cd ../# ln -s linux-source-2.6.18 /lib/modules/2.6.18-4-686/build Then try the hsfmodem package again. MarvSscanModem maintainer On 3/16/07, Manuel Vázquez Acosta <mva.led@xxxxxxxxx> wrote:> Hi all,>> I have tried to install hsfmodem in my laptop today, however it didn't work.>> I installed it with .deb (hsfmodem_7.47.00.05full_i386.deb), reboot and> found I had no sound.>> The installation complained about not finding snd-intel8x0, however it> ran and asked where to find linux headers to compile the drivers.>> After rebooting (and loosing audio), I ran hsfconfig it said it couldn't> find any modem (/dev/modem and the other were created though).>> I unistall hsfmodem, rebooted and ran scanModem. The attachment is the> ModemData.txt returned.>> Any ideas?>> Thanks in advance,> Manuel.>>>> Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.> Do use the following as the email Subject Line:> SomeName, YourCountry Debian GNU/Linux 4.0 kernel 2.6.18-4-686> This will alert cogent experts, and distinguish cases in the Archives.> YourCountry will enable Country Code guidance.> Occassionally responses are blocked by an Internet Provider mail filters.> So in a day, also check the Archived responses at http://www.linmodems.org .> Local Linux experts can be found through: http://www.linux.org/groups/index.html> -------------------------- System information ----------------------------> Debian GNU/Linux 4.0> Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-10) (waldi@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri Feb 2 15:10:49 UTC 2007> scanModem update of: 2006_November_07>>> USB modem not detected by lsusb>> Modem or host audio card candidates have firmware information:>> PCI slot PCI ID SubsystemID Name> ---------- --------- --------- --------------> 00:10.1 10de:026c 103c:30b5 Audio device: nVidia Corporation MCP51 High Definition Audio>> Modem interrupt assignment and sharing:> 58: 102609 1 IO-APIC-level HDA Intel>> --- Bootup diagnositcs for card in PCI slot 00:10.1 ----> ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LAZA] -> GSI 17 (level, high) -> IRQ 58> PCI: Setting latency timer of device 0000:00:10.1 to 64> ACPI: PCI interrupt for device 0000:00:10.1 disabled> PM: Writing back config space on device 0000:00:10.1 at offset 1 (was b00006, writing b00000)> PCI: Enabling device 0000:00:10.1 (0000 -> 0002)> ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LAZA] -> GSI 17 (level, high) -> IRQ 58> PCI: Setting latency timer of device 0000:00:10.1 to 64>> The PCI slot 00:10.1 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 Bootup.txt about possible fixes.> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx> if help is needed.>>> === Finished modem firmware and bootup diagnostics section. ===> === Next deducing cogent software ===>> For candidate modem in PCI bus: 00:10.1> Class 0403: 10de:026c Audio device: nVidia Corporation MCP51 High Definition Audio> Primary PCI_id 10de:026c> Subsystem PCI_id 103c:30b5> Softmodem codec or Vendor from diagnostics:> from Archives:>>> 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:>> Support can likely be achieved through two mutually exclusive alternatives:> 1) An ALSA modem driver plus slmodemd. Read Smartlink.txt for details, and> to test get the package SLMODEMD.gcc4.tar.gz from:> http://linmodems.technion.ac.il/packages/smartlink/> 2) The hsfmodem software for Conexant chipset modems: Read Conexant.txt>> 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.tar.gz having a compiled slmodemd. Unpack under Linux with:> $ tar zxf SLMODEMD.gcc4.tar.gz> and read instructions therein. But briefly, the modem is setup with command:> slmodemd -c YOUR_COUNTRY --alsa modem:1> 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.>>> 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-01: Conexant Digital : Conexant Digital : playback 1> 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1>> /proc/asound/modules> -------------------------------> 0 snd_hda_intel> and from the command:> aplay -l | grep -i modem>>> ----------------end Softmodem section -------------->> scanModem could not identify the Support Type needed from diagnosics or archives.> 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.> 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.>>> Formal support for Conexant chipset modems are available ONLY through> http://www.linuxant.com/drivers. Read Conexant.txt for details.> and Modem/YourSystem.txt for follow through guidance. Driver speed is limited to> 14,400 until a key is purchased. There is NO freeware alternative.> There are two support package types: hsfmodem and hcflinmodem.> http://www.lorenzobettini.it/linux/LinuxSonyVaioVGN-S5VP_B reports a> problem and solution in stalling a key, after testing of the free low> speed download.>> Read Conexant.txt>> Writing Conexant.txt>> Writing Smartlink.txt>> 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:> kernel-source-2.6.18-4-686> Compressed files at: /usr/src/linux-source-2.6.18.tar.bz2>> For Debian and some related distributions, a package kernel-kbuild-2.6-3 may be needed to support driver compiling>> Checking settings of: /etc/ppp/options>>> Read Modem/YourSystem.txt concerning other COMM channels: eth1> Which can interfere with Browser naviagation.>> Don't worry about the following, it is for the 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:options snd-atiixp-modem index=-2> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2> /etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers> /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem> /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem> Within any ancient /etc/devfs files:>> Within ancient kernel 2.4.n /etc/module.conf files:>> --------- end modem support lines -------->>>
