Franco Sorry, overlooked in your original ModemData.txt: "if compiling is necessary packages must be installed, providing: gcc-4.1" Just install this package and retry. It is installed by default on Ubuntu Linux systems. Send further messages to the List where others can help with Fedora specific problems, and will be on line when I am not MarvS On Sat, Jun 7, 2008 at 6:16 AM, Franco <gfb@xxxxxxxxxxxxxxxx> wrote: > FAILED > > is is the results > > > [root@home intel-537EP_secure-2.60.80.0]# make clean > cd coredrv; make clean > make[1]: Entering directory > `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' > rm -f *.ko *.o .*.o.cmd *.mod.c *~ core .*.ko.cmd Module.symvers > rm -rf .tmp_versions > make[1]: Leaving directory > `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' > rm -f *.o *.ko > [root@home intel-537EP_secure-2.60.80.0]# export MODEM_TYPE=537 > [root@home intel-537EP_secure-2.60.80.0]# make 537 > Module precompile check > Current running kernel is: 2.6.25.4-10.fc8 > /lib/modules... autoconf.h exists > diff: /boot/vmlinuz.autoconf.h: No such file or directory > autoconf.h matches running kernel > diff: /boot/vmlinuz.version.h: No such file or directory > version.h matches running kernel > 2.6.25.4-10.fc8 > make[1]: Entering directory > `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' > make -C /lib/modules/2.6.25.4-10.fc8/build > SUBDIRS=/data/intel/intel-537EP_secure-2.60.80.0/coredrv modules > /usr/src/kernels/2.6.25.4-10.fc8-i686/scripts/gcc-version.sh: line 25: gcc: > command not found > /usr/src/kernels/2.6.25.4-10.fc8-i686/scripts/gcc-version.sh: line 26: gcc: > command not found > make[2]: gcc: Command not found > make[2]: Entering directory `/usr/src/kernels/2.6.25.4-10.fc8-i686' > CC [M] /data/intel/intel-537EP_secure-2.60.80.0/coredrv/coredrv.o > /bin/sh: gcc: command not found > make[3]: *** [/data/intel/intel-537EP_secure-2.60.80.0/coredrv/coredrv.o] > Error 127 > make[2]: *** [_module_/data/intel/intel-537EP_secure-2.60.80.0/coredrv] > Error 2 > make[2]: Leaving directory `/usr/src/kernels/2.6.25.4-10.fc8-i686' > make[1]: *** [537core_26] Error 2 > make[1]: Leaving directory > `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' > 2.6.25.4-10.fc8 > Failed to build driver > > > > > > > > > Marvin Stodolsky wrote: >> >> Franco >> >> Just add in the extra step, because your modem was not autodected >> >> $ make clean >> $ export MODEM_TYPE=537 >> $ make >> which will read MODEM_TYPE=537 from memory >> Only if "make" is successful, should you proceed with: >> >> $ su root >> # make install >> >> Read the associated documentation. >> Report back if you need further help. >> >> MarvS >> >> >> On Fri, Jun 6, 2008 at 10:05 PM, Franco <gfb@xxxxxxxxxxxxxxxx> wrote: >> >>> >>> Did what you said and is not working. >>> >>> >>> >>> Here are the results: >>> >>> [root@home intel-537EP_secure-2.60.80.0]# make clean >>> cd coredrv; make clean >>> make[1]: Entering directory >>> `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' >>> rm -f *.ko *.o .*.o.cmd *.mod.c *~ core .*.ko.cmd Module.symvers >>> rm -rf .tmp_versions >>> make[1]: Leaving directory >>> `/data/intel/intel-537EP_secure-2.60.80.0/coredrv' >>> rm -f *.o *.ko >>> >>> [root@home intel-537EP_secure-2.60.80.0]# make 537 >>> Module precompile check >>> Current running kernel is: 2.6.25.4-10.fc8 >>> /lib/modules... autoconf.h exists >>> diff: /boot/vmlinuz.autoconf.h: No such file or directory >>> autoconf.h matches running kernel >>> diff: /boot/vmlinuz.version.h: No such file or directory >>> version.h matches running kernel >>> Modem type not determined. >>> $ export MODEM_TYPE=<type> >>> with type=537 or 537EP or 537SP or 537EA or 537AA >>> >>> [root@home intel-537EP_secure-2.60.80.0]# make install >>> rm -f /usr/sbin/hamregistry.bin >>> bash 537_inst >>> running kernel 2.6.25.4-10.fc8 >>> installing hamregistry, used for persistant storage >>> installing usrsound, a soft buzzer >>> installing 537 module >>> install: cannot stat `Intel537.ko': No such file or directory >>> make: *** [install] Error 1 >>> >>> >>> >>> Thanks again for your help >>> >>> >>> >>> >>> Marvin Stodolsky wrote: >>> >>>> >>>> Linuxant software cannot serve >>>> >>>> >>>>> >>>>> CLASS="Class 0780: e159:0001" >>>>> NAME="Communication controller: Tiger Jet Network Inc. Tiger3XX >>>>> >>>>> >>>> >>>> It is necessary to use >>>> >>>> >>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/intel-537EP_secure-2.60.80.0_2008_03_22.tar.bz2 >>>> >>>> Unpack under Linux with: >>>> $ tar jxf int*.tar.bz2 >>>> >>>> Within the new folder >>>> $ make clean >>>> $ make 537 >>>> $ su root >>>> # make install >>>> Read the associated documentation. >>>> Report back if you need further help. >>>> >>>> MarvS >>>> >>>> >>>> On Fri, Jun 6, 2008 at 5:24 PM, Antonio Olivares >>>> <olivares14031@xxxxxxxxx> wrote: >>>> >>>> >>>>> >>>>> Franco, >>>>> >>>>> for one of the modem cards present, the other might not be, but I am >>>>> not >>>>> sure >>>>> <quote> >>>>> Predictive diagnostics for card in bus 01:05.0: >>>>> Modem chipset detected on >>>>> CLASS="Class 0780: e159:0001" >>>>> NAME="Communication controller: Tiger Jet Network Inc. Tiger3XX >>>>> Modem/ISDN interface" >>>>> SUBSYS=8086:0003 >>>>> PCIDEV=e159:0001 >>>>> IRQ=10 >>>>> IDENT=INTEL537 >>>>> >>>>> For candidate modem in: 01:05.0 >>>>> Class 0780: e159:0001 Communication controller: Tiger Jet Network >>>>> Inc. Tiger3XX Modem/ISDN interface >>>>> Primary device ID: e159:0001 >>>>> Support type needed or chipset: INTEL537 >>>>> </quote> >>>>> >>>>> It reports an INTEL537 for which you may find drivers at >>>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/ >>>>> >>>>> with the latest one being >>>>> >>>>> >>>>> >>>>> http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/intel-537EP_secure-2.60.80.0_2008_03_22.tar.bz2 >>>>> >>>>> I have seen several reports here about such modems, but in the end the >>>>> linuxant/conexant drivers end up serving, so I'll forward this to Marv >>>>> and hope that he can provide better advice than I can, because I am >>>>> not 100% sure that the INTEL537 driver is the one that you need. >>>>> >>>>> Regards, >>>>> >>>>> Antonio >>>>> >>>>> On 6/6/08, Franco <gfb@xxxxxxxxxxxxxxxx> wrote: >>>>> >>>>> >>>>>> >>>>>> I am very new to the linux environment and I need help >>>>>> >>>>>> I am using fedora core 8 and I would like to setup hylafax on it. >>>>>> >>>>>> I plugged in the Fax/modem (PCI) to the computer and installed fedora >>>>>> core 8 >>>>>> >>>>>> At this point I have no idea what to do. >>>>>> >>>>>> I have some knowledge of linux as I have setup my web and mail server >>>>>> correctly >>>>>> >>>>>> Thank you for your help. >>>>>> >>>>>> >>>>>> here is the modemdata.txt file generated >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List >>>>>> Server, >>>>>> as HTML can contain viruses. Use as the email Subject Line: >>>>>> YourName, YourCountry Fedora release 8 (Werewolf) >>>>>> Kernel kernel 2.6.25.4-10.fc8 >>>>>> With this Subject Line cogent experts will be alerted, and useful >>>>>> case >>>>>> names left in the Archive. >>>>>> YourCountry will enable Country specific guidance. Linux experts in >>>>>> YourCountry >>>>>> 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, Fedora release 8 (Werewolf) >>>>>> Kernel >>>>>> Linux version 2.6.25.4-10.fc8 >>>>>> (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx) >>>>>> (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu May 22 >>>>>> 23:34:09 EDT 2008 >>>>>> scanModem update of: 2008_06_05 >>>>>> >>>>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>>>> Attached USB devices are: >>>>>> ID 1d6b:0002 >>>>>> ID 1d6b:0001 >>>>>> >>>>>> USB modems not recognized >>>>>> >>>>>> For candidate card in slot 01:05.0, firmware information and bootup >>>>>> diagnostics are: >>>>>> PCI slot PCI ID SubsystemID Name >>>>>> ---------- --------- --------- -------------- >>>>>> 01:05.0 e159:0001 8086:0003 Communication controller: Tiger >>>>>> Jet Network Inc. Tiger3XX Modem/ISDN interface >>>>>> >>>>>> Modem interrupt assignment and sharing: >>>>>> --- Bootup diagnostics for card in PCI slot 01:05.0 ---- >>>>>> >>>>>> For candidate card in slot 00:05.0, firmware information and bootup >>>>>> diagnostics are: >>>>>> PCI slot PCI ID SubsystemID Name >>>>>> ---------- --------- --------- -------------- >>>>>> 00:05.0 10de:03f0 1019:2151 Audio device: nVidia Corporation >>>>>> MCP61 High Definition Audio >>>>>> >>>>>> Modem interrupt assignment and sharing: >>>>>> 22: 209 IO-APIC-fasteoi ehci_hcd:usb1, HDA Intel >>>>>> --- Bootup diagnostics for card in PCI slot 00:05.0 ---- >>>>>> pci 0000:00:05.0: Enabling HT MSI Mapping >>>>>> ACPI: PCI Interrupt 0000:00:05.0[B] -> Link [AAZA] -> GSI 22 (level, >>>>>> low) -> IRQ 22 >>>>>> PCI: Setting latency timer of device 0000:00:05.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:05.0 has a High Definition Audio Card >>>>>> >>>>>> The ALSA verion is 1.0.15 >>>>>> The modem cards detected by "aplay -l" are: None >>>>>> >>>>>> >>>>>> The /proc/asound/pcm file reports: >>>>>> ----------------------- >>>>>> 00-01: ALC662 Digital : ALC662 Digital : playback 1 >>>>>> 00-00: ALC662 Analog : ALC662 Analog : playback 1 : capture 1 >>>>>> >>>>>> about /proc/asound/cards: >>>>>> ------------------------ >>>>>> 0 [NVidia ]: HDA-Intel - HDA NVidia >>>>>> HDA NVidia at 0xfe028000 irq 22 >>>>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>>>> software. === >>>>>> >>>>>> Predictive diagnostics for card in bus 01:05.0: >>>>>> Modem chipset detected on >>>>>> CLASS="Class 0780: e159:0001" >>>>>> NAME="Communication controller: Tiger Jet Network Inc. Tiger3XX >>>>>> Modem/ISDN interface" >>>>>> SUBSYS=8086:0003 >>>>>> PCIDEV=e159:0001 >>>>>> IRQ=10 >>>>>> IDENT=INTEL537 >>>>>> >>>>>> For candidate modem in: 01:05.0 >>>>>> Class 0780: e159:0001 Communication controller: Tiger Jet Network >>>>>> Inc. Tiger3XX Modem/ISDN interface >>>>>> Primary device ID: e159:0001 >>>>>> Support type needed or chipset: INTEL537 >>>>>> >>>>>> >>>>>> ----------------end Softmodem section -------------- >>>>>> >>>>>> >>>>>> Predictive diagnostics for card in bus 00:05.0: >>>>>> Modem chipset not detected on >>>>>> CLASS="Class 0403: 10de:03f0" >>>>>> NAME="Audio device: nVidia Corporation MCP61 High Definition Audio " >>>>>> SUBSYS=1019:2151 >>>>>> PCIDEV=10de:03f0 >>>>>> IRQ=22 >>>>>> HDA=10de:03f0 >>>>>> SOFT=10de:03f0.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 10de:03f0. >>>>>> If another modem card is present, then most likely 10de:03f0 does not >>>>>> host a modem. >>>>>> If another modem card has not been detected, then possibilities are: >>>>>> 1) A Conexant modem chip is present on 10de:03f0, 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: >>>>>> wvdialconf /etc/wvdial.conf >>>>>> >>>>>> For candidate modem in: 00:05.0 >>>>>> Class 0403: 10de:03f0 Audio device: nVidia Corporation MCP61 High >>>>>> Definition Audio >>>>>> Primary device ID: 10de:03f0 >>>>>> Subsystem PCI_id 1019:2151 >>>>>> 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 >>>>>> DOCs/Conexant.txt >>>>>> The following ALSA alternative CANNOT work with Conexant modems. >>>>>> >>>>>> 2) An ALSA modem driver plus slmodemd. Read DOCs/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 DOCs/Smartlink.txt >>>>>> ============ end Smartlink section ===================== >>>>>> >>>>>> Completed candidate modem analyses. >>>>>> >>>>>> The base of the UDEV device file system is: /dev/.udev >>>>>> >>>>>> The kernel was compiled with gcc version 4.1.2 and a compiler is not >>>>>> installed >>>>>> >>>>>> linux-headers-2.6.25.4-10.fc8 resources needed for compiling are not >>>>>> manifestly ready! >>>>>> >>>>>> If compiling is necessary packages must be installed, providing: >>>>>> gcc-4.1 kernel-source-2.6.25.4-10.fc8 >>>>>> >>>>>> >>>>>> 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: >>>>>> -r-xr-xr-x 1 root root 312332 2006-12-01 07:54 /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) >>>>>> chmod a+x /usr/sbin/pppd >>>>>> or under Ubuntu related Linuxes >>>>>> chmod a+x /usr/sbin/pppd >>>>>> >>>>>> Checking settings of: /etc/ppp/options >>>>>> lock >>>>>> >>>>>> 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. >>>>>> ========================================================== >>>>>> >>>>>> Checking for modem support lines: >>>>>> -------------------------------------- >>>>>> /device/modem symbolic link: >>>>>> slmodemd created symbolic link /dev/ttySL0: >>>>>> Within /etc/udev/ files: >>>>>> /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", >>>>>> NAME="modems/mwave", GROUP="uucp" >>>>>> Within /etc/modprobe.conf files: >>>>>> >>>>>> Within any ancient /etc/devfs files: >>>>>> >>>>>> Within ancient kernel 2.4.n /etc/module.conf files: >>>>>> >>>>>> --------- end modem support lines -------- >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> globe <http://www.solutionbyte.com>Gianfranco Baggio >>>>>> gfb@xxxxxxxxxxxxxxxx >>>>>> >>>>>> >>>>>> >>>> >>>> >>> >>> -- >>> globe <http://www.solutionbyte.com>Gianfranco Baggio >>> gfb@xxxxxxxxxxxxxxxx >>> >>> >> >> > > -- > globe <http://www.solutionbyte.com>Gianfranco Baggio > gfb@xxxxxxxxxxxxxxxx >
