Delaj, Two additional packages are needed for the HCF driver compile to succeed.At http://packages.ubuntu.com/search for "libc6-dev"This will lead to http://packages.ubuntu.com/gutsy/libc6-dev>From there start the download of inux-libc-dev and libc6-devThey can be co-installed with:$ sudo dpkg -i inux-libc-dev libc6-dev Then uninstall and the hsfmodem package andrerty the hcflinmodem compile. MarvS On Wed, May 7, 2008 at 2:17 AM, delaunois <jacques.delaunois@xxxxxxxxx> wrote:> Hello,>> With hsfmodem-7.68.00.09full.tar.gz, I got the hereunder result.>> Moreover, I didn't find usbconfig.>> This afternoon, I'll try the hcf way>> Jacques D.>> delaj@Maxelo:/usr/sbin$ sudo hsfconfig>> Conexant HSF softmodem driver, version 7.68.00.09full>> If you need license keys, assistance or more information, please go to:> http://www.linuxant.com/>> When reporting a problem for the first time, please send> us the file generated by "hsfconfig --dumpdiag".>> Warning: existing driver modules found under:>> /lib/modules/2.6.22-14-generic/> Would you like to keep using them? [no]>> Would you like to use the replacement HDA modules? [yes] y>>> No pre-built modules for: Ubuntu-7.10 linux-2.6.22-14-generic i686-SMP>> Trying to automatically build the driver modules...> (this requires a C compiler and proper kernel sources to be installed)>> Where is the linux source build directory that matches your running> kernel?> [/lib/modules/2.6.22-14-generic/build]>> WARNING: Building older built-in HDA driver; some audio/modem issues may> occur.> If this is the case, please try the latest alsa-driver-linuxant package> available from http://www.linuxant.com/alsa-driver>> Building modules for kernel 2.6.22-14-generic, using source directory> /lib/modules/2.6.22-14-generic/build. Please wait...>> Warning: Module snd_hda_intel is in use> Warning: Module snd_hda_intel is in use> Warning: Module snd_hda_intel is in use> Warning: Module snd_hda_intel is in use> Warning: Module snd_hda_intel is in use> Warning: Module snd_hda_intel is in use> done.>> Warning: no device detected by hsf driver - HDA modems may require> reboot>> Note: HDA support not compiled in the driver>> Note: kernel module snd-via82xx-modem overridden by hsfmc97via> Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis> Note: kernel module snd-atiixp-modem overridden by hsfmc97ati>> Le mardi 06 mai 2008 à 11:00 +0300, Jacques Goldberg a écrit :>>> > Jacques,> >> > 1-Marv and I read the discussion list immediately. There is no need to> > add his and mine address on the mail as both copies arrive on the screen> > at the same time.> >> > 2-You did not select the right driver anyway. What you selected is> > precompiled for internal PCI modems with the HSF chipset. It by> > definition cannot serve an USB modem.> > What you must try is (HSF then HCF if fails or reversed order) the> > GENERIC source driver to be installed with method C, from location> > http://www.linuxant.com/drivers/hsf/full/downloads.php> > file: hsfmodem-7.68.00.09full.tar.gz> >> > I have never tried the deb version of the same file which is easier for> > Ubuntu.> > I have used the rpm version of the same file with RedHat but I do not> > remember if it offers or not the choice to start usbconfig instead of> > pciconfig.> > I know that the tar version does it, which is why I recommend to use> > that file - but of course you can try the deb version (method B) with> > file hsfmodem_7.68.00.09full_i386.deb.zip> > Remember to unzip hsfmodem_7.68.00.09full_i386.deb.zip or> > gunzip hsfmodem_7.68.00.09full.tar.gz> > before applying the installation instructions found on the Linuxant Web> > site.> > Also if you start with HSF, fail, and want to try HCF, remember to> > remove the HSF work (uninstall).> >> > Jacques G.> >> >> > Jacques Delaunois wrote:> > > Hello,> > >> > > I don't know when /dev/ttySHF was installed : before asking for help I 've> > > tried a lot of things...(as you may guess I'm new to Linux)> > >> > > Anyway, I've tried to install the HSF driver et met the following problem :> > > when unzipping the HSF driver (I didn't find a tar driver), I got the> > > followings messages :> > >> > >> > > *dpkg - avertissement : hsfmodem mis à jour de la version> > > 7.68.00.09full-k2.6.22-14-generic-1.ubuntu vers l'ancienne version> > > 7.68.00.09full-k2.6.22-14-386-1.ubuntu.**> > > (Lecture de la base de données... 98987 fichiers et répertoires déjà> > > installés.)> > > Préparation du remplacement de hsfmodem> > > 7.68.00.09full-k2.6.22-14-generic-1.ubuntu (en utilisant> > > hsfmodem_7.68.00.09full_k2.6.22_14_386_ubuntu_i386.deb) ...> > >> > > Removing hsf driver from /lib/modules/2.6.22-14-generic/> > > Warning: Module snd_hda_intel is in use> > > Warning: Module snd_hda_intel is in use> > > Warning: Module snd_hda_intel is in use> > > Warning: Module snd_hda_intel is in use> > > Warning: Module snd_hda_intel is in use> > > Warning: Module snd_hda_intel is in use> > > Dépaquetage de la mise à jour de hsfmodem ...> > > Paramétrage de hsfmodem (7.68.00.09full-k2.6.22-14-386-1.ubuntu) ...> > > Conexant HSF softmodem driver, version 7.68.00.09full> > >> > > If you need license keys, assistance or more information, please go to:> > > http://www.linuxant.com/> > >> > > When reporting a problem for the first time, please send> > > us the file generated by "hsfconfig --dumpdiag".> > >> > >> > > No pre-built modules for: Ubuntu-7.10 linux-2.6.22-14-generic i686-SMP> > >> > > Please obtain the appropriate variant of this package for your system> > > or try the generic DEB or tar version.*> > >> > >> > > What is the appropriate variant or where can I get the tar version ?> > >> > > Many thanks> > >> > > Jacques> > >> > > 2008/5/5 Jacques Goldberg <Jacques.Goldberg@xxxxxxx>:> > >> > >> That one is intereting indeed.> > >> Who has installed these /dev/ttySHF nodes?> > >> In spite of what> > >> http://linmodems.technion.ac.il/bigarch/archive-sixth/msg03048.html> > >> says (HCFUSB) , perhaps there is a good reason to try the HSFUSB> > >> counterpart of HCFUSB.> > >> Just as I outlined in my previous mail, except using HSF instead of HCF> > >> all the way.> > >>> > >> Jacques G.> > >>> > >>> > >> delaunois wrote:> > >>> > >>> Sorry, my modem was'nt detected> > >>>> > >>> delaj@Maxelo:~$ sudo wvdialconf /etc/wvdial.conf> > >>> Editing `/etc/wvdial.conf'.> > >>>> > >>> Scanning your serial ports for a modem.> > >>>> > >>> Modem Port Scan<*1>: Scanning ttySHSF0 first, /dev/modem is a link to> > >>> it.> > >>> Modem Port Scan<*1>: SHSF0 S0 S1 S2 S3 SHSF1 SHSF2 SHSF3 Modem> > >>> Port Scan<*1>: SHSF4 SHSF5 SHSF6 SHSF7> > >>>> > >>> 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>.> > >>>> > >>>> > >>>> > >>> Le lundi 05 mai 2008 à 08:50 -0400, Marvin Stodolsky a écrit :> > >>>> > >>> Delaj,> > >>>> If> > >>>> 0baf:6112 U.S. Robotics FaxModem Model 5633> > >>>> is your only modem, try detecting it with:> > >>>> $ sudo wvdialconf /etc/wvdial.conf> > >>>>> > >>>> If there is also an internal modem, it is probably a Conexnant type in> > >>>> the SUbsystem of:> > >>>> Class 0403: 8086:284b Audio device: Intel Corporation 82801H> > >>>> Primary device ID: 8086:284b> > >>>> Subsystem PCI_id 103c:2a36> > >>>> Then under Ubuntu 2.6.22-14-generic, it would be supported following> > >>>> the instructions in Conexnant.txt> > >>>> From> > >>>> http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php> > >>>> download> > >>>> hsfmodem-7.68.00.07full_k2.6.22_14_generic_ubuntu_i386.deb.zip> > >>>> Under Linux unpack with:> > >>>> $ unzip hsfmodem*.zip> > >>>> Then install with:> > >>>> $ sudo dpkg -i hsfmodem*.deb> > >>>> Subsequently, the modem should be found with> > >>>> $ sudo wvdialconf /etc/wvdial.conf> > >>>> Edit in your personal information with:> > >>>> $ sudo gedit /etc/wvdial.conf> > >>>> and try dialing out with:> > >>>> $ sudo wvdial.> > >>>>> > >>>> Please report back presently.> > >>>>> > >>>> MarvS> > >>>>> > >>>>> > >>>>> > >>>> On Mon, May 5, 2008 at 5:30 AM, delaunois <jacques.delaunois@xxxxxxxxx>> > >>>> wrote:> > >>>>> > >>>>> Hello,> > >>>>>> > >>>>> Is it possible to get my modem operating under ubuntu ? I have'nt> > >>>>> found> > >>>>> anyhere how to do.> > >>>>>> > >>>>> Hereunder my modemdata file> > >>>>>> > >>>>> Many thanks for any idea.> > >>>>>> > >>>>> delaj> > >>>>>> > >>>>>> > >>>>> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxxxxxx> > >>>>> Server,> > >>>>> as HTML can contain viruses. Use as the email Subject Line:> > >>>>> YourName, YourCountry kernel 2.6.22-14-generic> > >>>>> With this Subject Line cogent experts will be alerted, and useful> > >>>>> case> > >>>>> names left in the Archive.> > >>>>> YourCountry will enable Country specific guidance. Your contry's> > >>>>> local> > >>>>> Linux experts> > >>>>> 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,> > >>>>> Linux version 2.6.22-14-generic (buildd@terranova) (gcc version> > >>>>> 4.1.3> > >>>>> 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12> > >>>>> 07:42:25> > >>>>> UTC 2008> > >>>>> scanModem update of: 2008_05_02> > >>>>> The modem symbolic link is /dev/modem -> ttySL0> > >>>>> There are no blacklisted modem drivers in /etc/modprobe* files> > >>>>> Attached USB devices are:> > >>>>> ID 0d49:7110 Maxtor> > >>>>> ID 058f:6362 Alcor Micro Corp.> > >>>>> ID 0409:005a NEC Corp.> > >>>>> ID 03f0:0b0c Hewlett-Packard> > >>>>> ID 03f0:6004 Hewlett-Packard DeskJet 5550> > >>>>> ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub> > >>>>> ID 0baf:6112 U.S. Robotics FaxModem Model 5633> > >>>>>> > >>>>> USB modems not recognized> > >>>>> For candidate card in slot 00:1b.0, firmware information and bootup> > >>>>> diagnostics are:> > >>>>> PCI slot PCI ID SubsystemID Name> > >>>>> ---------- --------- --------- --------------> > >>>>> 00:1b.0 8086:284b 103c:2a36 Audio device: Intel> > >>>>> Corporation> > >>>>> 82801H> > >>>>>> > >>>>>> > >>>>> Modem interrupt assignment and sharing:> > >>>>> 22: 295628 0 IO-APIC-fasteoi HDA Intel> > >>>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----> > >>>>> [ 75.242202] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22> > >>>>> (level,> > >>>>> low) ->> > >>>>> IRQ 22> > >>>>> [ 75.242219] PCI: Setting latency timer of device 0000:00:1b.0 to> > >>>>> 64> > >>>>>> > >>>>>> > >>>>> ===== 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.> > >>>>> PCI slot 00:1b.0 has a High Definition Audio Card> > >>>>> ---ALSA bootup diagnostics ---> > >>>>>> > >>>>> The ALSA verion is 1.0.14> > >>>>> The modem cards detected by "aplay -l" are:> > >>>>>> > >>>>>> > >>>>> The /proc/asound/pcm file reports:> > >>>>> -----------------------> > >>>>> 00-02: ALC882 Analog : ALC882 Analog : capture 2> > >>>>> 00-01: ALC882 Digital : ALC882 Digital : playback 1 : capture 1> > >>>>> 00-00: ALC882 Analog : ALC882 Analog : playback 1 : capture 2> > >>>>> 01-00: SAA7134 PCM : SAA7134 PCM : capture 1> > >>>>>> > >>>>> about /proc/asound/cards:> > >>>>> ------------------------> > >>>>> 0 [Intel ]: HDA-Intel - HDA Intel> > >>>>> HDA Intel at 0xfdff4000 irq 22> > >>>>> 1 [SAA7134 ]: SAA7134 - SAA7134> > >>>>> saa7133[0] at 0xfdeff000 irq 21> > >>>>> === Finished firmware and bootup diagnostics, next deducing cogent> > >>>>> software.> > >>>>> ===> > >>>>>> > >>>>> A candidate modem is not evident among the PCI devices:> > >>>>> ------------------------------------------------> > >>>>> 00:19.0 Ethernet controller: Intel Corporation 82562V 10/100> > >>>>> Network> > >>>>> Connection (rev 02)> > >>>>> 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD> > >>>>> Audio> > >>>>> Controller (rev 02)> > >>>>> 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID> > >>>>> Controller> > >>>>> (rev 02)> > >>>>> 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus> > >>>>> Controller> > >>>>> (rev> > >>>>> 02)> > >>>>> 01:00.0 VGA compatible controller: ATI Technologies Inc RV516 XT> > >>>>> Radeon> > >>>>> X1600 Series (Primary)> > >>>>> 01:00.1 Display controller: ATI Technologies Inc RV516 XT Radeon> > >>>>> X1600> > >>>>> Series (Secondary)> > >>>>> 03:00.0 Multimedia controller: Philips Semiconductors> > >>>>> SAA7133/SAA7135> > >>>>> Video> > >>>>> Broadcast Decoder (rev d1)> > >>>>> 03:01.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)> > >>>>> 03:04.0 Ethernet controller: Atheros Communications, Inc. AR5413> > >>>>> 802.11abg> > >>>>> NIC (rev 01)> > >>>>> ------------------------------------------------> > >>>>> with USB and bridge devices not displayed.> > >>>>>> > >>>>> If your modem is connected by an external serial cable,> > >>>>> or mounted internally on an ISA card, scanModem would not access> > >>>>> it.> > >>>>> Try with Root permission> > >>>>> $ sudo wvdialconf /etc/wvdial.conf> > >>>>> to detect these modem types and some USB modems.> > >>>>> If the detection is successful, read the wvdial.txt .> > >>>>> Edit the /etc/wvdial.conf with Root permission:> > >>>>> sudo gedit /etc/wvdial.conf> > >>>>> will be able to dial out with Root permission:> > >>>>> sudo wvdial> > >>>>>> > >>>>> Many modems for which scanModem fails have Conexant chips.> > >>>>> From http://www.linuxant.com/drivers/modemident.php> > >>>>> get the ListModem tool, which will report on Conexant chipset> > >>>>> modems> > >>>>>> > >>>>> If the above tests fail, please provide any independent information> > >>>>> available on your modem.> > >>>>> 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.> > >>>>>> > >>>>> The /proc/asound/ audio+modem diagostics are being copied.> > >>>>> Finished copy to Modem/ALSAdelaj.tgz> > >>>>>> > >>>>> Predictive diagnostics for card in bus 00:1b.0:> > >>>>> Modem chipset not detected on> > >>>>> CLASS="Class 0403: 8086:284b"> > >>>>> NAME="Audio device: Intel Corporation 82801H "> > >>>>> SUBSYS=103c:2a36> > >>>>> PCIDEV=8086:284b> > >>>>> IRQ=22> > >>>>> HDA=8086:284b> > >>>>> SOFT=8086:284b.HDA> > >>>>>> > >>>>>> > >>>>> High Definition Audio (HDA) cards MAY host a modem chip in their> > >>>>> Subsystem,> > >>>>>> > >>>>> and many are supported by the ALSA audio+modem driver snd-hda-intel> > >>>>> A modem was not detected on HDA card 8086:284b.> > >>>>> If another modem card is present, then most likely 8086:284b does> > >>>>> not> > >>>>> host> > >>>>> a modem.> > >>>>> If another modem card has not been detected, then possibilities> > >>>>> are:> > >>>>> 1) A Conexant modem chip is present on 8086:284b, as Conexant> > >>>>> chips> > >>>>> are frequently not detectable by ALSA diagnostics> > >>>>> 2) The modem may be of the older non-PCI Controller Chipset> > >>>>> (hardware)> > >>>>> type.> > >>>>> Try detection with Root permission:> > >>>>> sudo wvdialconf /etc/wvdial.conf> > >>>>>> > >>>>> For candidate modem in: 00:1b.0> > >>>>> Class 0403: 8086:284b Audio device: Intel Corporation 82801H> > >>>>> Primary device ID: 8086:284b> > >>>>> Subsystem PCI_id 103c:2a36> > >>>>> Softmodem codec or chipset from diagnostics:> > >>>>> from Archives:> > >>>>>> > >>>>>> > >>>>>> > >>>>> Support type needed or chipset:> > >>>>>> > >>>>> Support can likely be achieved through two mutually exclusive> > >>>>> alternatives:> > >>>>> 1) The hsfmodem software for Conexant chipset modems: Read> > >>>>> Conexant.txt> > >>>>> The following ALSA alternative CANNOT work with Conexant modems.> > >>>>>> > >>>>> 2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for> > >>>>> details,> > >>>>> and> > >>>>> to test get the package SLMODEMD.gcc4.1.tar.gz from:> > >>>>> http://linmodems.technion.ac.il/packages/smartlink/> > >>>>>> > >>>>> ----------------end Softmodem section --------------> > >>>>>> > >>>>> Writing Intel.txt> > >>>>>> > >>>>> For owners of a Dell PCs with Conexant HSF modems, a driver source> > >>>>> package> > >>>>> with full speed enabled is available, but requires driver> > >>>>> compiling.> > >>>>> Read> > >>>>> Conexant.txt> > >>>>>> > >>>>> Read Conexant.txt> > >>>>>> > >>>>> Writing Conexant.txt> > >>>>>> > >>>>> Writing Smartlink.txt> > >>>>> ============ end Smartlink section =====================> > >>>>>> > >>>>>> > >>>>> The base of the UDEV device file system is: /dev/.udev> > >>>>>> > >>>>> Versions adequately match for the compiler installed: 4.1.3> > >>>>> and the compiler used in kernel assembly: 4.1.3> > >>>>>> > >>>>>> > >>>>>> > >>>>> Minimal compiling resources appear complete:> > >>>>> make utility - /usr/bin/make> > >>>>> Compiler version 4.1> > >>>>> linuc_headers base folder /lib/modules/2.6.22-14-generic/build> > >>>>>> > >>>>> However some compilations and executable functions may need> > >>>>> additional> > >>>>> files,> > >>>>> in the FileNames.h (so called kernel "h"eaders) collection> > >>>>> installed in> > >>>>> /usr/include/ .> > >>>>> For martian_modem, additional required packages are libc6-dev (and> > >>>>> for> > >>>>> Debian/Ubuntu, linux-libc-dev). The also required headers of> > >>>>> package> > >>>>> libc6> > >>>>> are commonly installed by default. When compiling ALSA drivers, the> > >>>>> utility> > >>>>> "patch" will also be needed.> > >>>>>> > >>>>>> > >>>>>> > >>>>> 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 package> > >>>>> 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 21: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> > >>>>>> > >>>>>> > >>>>> 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> > >>>>> 2008-05-05> > >>>>> 07:42 /dev/modem -> ttySL0> > >>>>> slmodemd created symbolic link /dev/ttySL0:> > >>>>> Within /etc/udev/ files:> > >>>>> /etc/udev/rules.d/hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"> > >>>>> /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/hsf.conflicts:install snd-via82xx-modem /bin/true #> > >>>>> temporarily disabled by hsf - conflicts with hsfmc97via> > >>>>> /etc/modprobe.d/hsf.conflicts:install snd-atiixp-modem /bin/true #> > >>>>> temporarily disabled by hsf - conflicts with hsfmc97ati> > >>>>> /etc/modprobe.d/hsf:alias /dev/modem /dev/ttySHSF> > >>>>> /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> > >>>>> Within any ancient /etc/devfs files:> > >>>>> /etc/devfs/conf.d/hsf.conf:LOOKUP ^(ttySHSF[0-9]|modem$) EXECUTE> > >>>>> nice> > >>>>> /sbin/modprobe /dev/ttySHSF> > >>>>> /etc/devfs/conf.d/hsf.conf:REGISTER ^ttySHSF0$ CFUNCTION GLOBAL> > >>>>> symlink> > >>>>> $devname modem> > >>>>> /etc/devfs/conf.d/hsf.conf:UNREGISTER ^ttySHSF0$ CFUNCTION> > >>>>> GLOBAL> > >>>>> unlink> > >>>>> modem> > >>>>> Within ancient kernel 2.4.n /etc/module.conf files:> > >>>>>> > >>>>> --------- end modem support lines --------> > >>>>>> > >>>>>> > >>>>>>>
