Chris, For Debian and some related distributions, a package kernel-kbuild-2.6-26 may be needed to support driver compiling. Please check Also try from http://linmodems.technion.ac.il/packages/Intel/Philippe.Vouters/ the alternate intel-5337EP_secure-2.60.80.0_2009_02_08.tar.bz2 Unpack with: tar jxf intel*.tar.bz2 MarvS On Tue, May 5, 2009 at 3:38 PM, <chris@xxxxxxxxxxx> wrote: > Greetings - Please call me Chris... > > Environment: PIII 800MHz 192MB RAM Debian Lenny > Everything seems to be working just fine. I'm connected via ethernet, but > this machine will end up being used by my brother who only has dialup. So > I'm setting that up. > > scanModem results are below, plus compile errors. > linux-headers-2.6.26-2-686.deb is installed as source. > I even symlinked it to /usr/src/linux thinking that might help. (No > difference.) > I had to do an export MODEMTYPE=537EP because it couldn't seem to > recognize the modem during the first make. > Any help greatly appreciated. > > Chris > > > =====compile errors===== > debian:/home/rod/Desktop/intel-537EP_secure-2.60.80.0# export > MODEM_TYPE=537EP > debian:/home/rod/Desktop/intel-537EP_secure-2.60.80.0# make clean > cd coredrv; make clean > make[1]: Entering directory > `/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv' > rm -f *.ko *.o .*.o.cmd *.mod.c *~ core .*.ko.cmd Module.* modules.* > rm -rf .tmp_versions > make[1]: Leaving directory > `/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv' > rm -f *.o *.ko > debian:/home/rod/Desktop/intel-537EP_secure-2.60.80.0# make 537 > Module precompile check > Current running kernel is: 2.6.26-2-686 > /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.26-2-686 > make[1]: Entering directory > `/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv' > make -C /lib/modules/2.6.26-2-686/build > SUBDIRS=/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv modules > make[2]: Entering directory `/usr/src/linux-headers-2.6.26-2-686' > CC [M] /home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv/coredrv.o > CC [M] /home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv/clmmain.o > /home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv/clmmain.c:86: > error: expected ‘)’ before ‘(’ token > make[3]: *** > [/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv/clmmain.o] Error 1 > make[2]: *** > [_module_/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-2-686' > make[1]: *** [537core_26] Error 2 > make[1]: Leaving directory > `/home/rod/Desktop/intel-537EP_secure-2.60.80.0/coredrv' > 2.6.26-2-686 > Failed to build driver > debian:/home/rod/Desktop/intel-537EP_secure-2.60.80.0# > > > > =====ModemData.txt===== > _______________________________________________ > > 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 kernel 2.6.26-2-686 > 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, > Linux version 2.6.26-2-686 (Debian 2.6.26-15) (dannf@xxxxxxxxxx) (gcc > version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu Mar 26 > 01:08:11 UTC 2009 > scanModem update of: 2009_04_28 > > There are no blacklisted modem drivers in /etc/modprobe* files > Potentially useful modem drivers now loaded are: > > > If a USB modem or cellphone is attached and was not detected, please > provide available information in your request to discuss@xxxxxxxxxxxxx > > For candidate card in slot 01:07.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 01:07.0 8086:1080 8086:1000 Modem: Intel Corporation FA82537EP 56K V.92 > Data/Fax Modem PCI > > Modem interrupt assignment and sharing: > 9: 0 XT-PIC-XT acpi > --- Bootup diagnostics for card in PCI slot 01:07.0 ---- > [ 2.178891] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [LNKA] -> GSI 9 > (level, low) -> IRQ 9 > [ 2.179400] 0000:01:07.0: ttyS2 at I/O 0xec08 (irq = 9) is a 16450 > [ 2.179655] 0000:01:07.0: ttyS3 at I/O 0xec10 (irq = 9) is a 8250 > [ 2.179776] Couldn't register serial port 0000:01:07.0: -28 > > === Finished firmware and bootup diagnostics, next deducing cogent > software. === > > Predictive diagnostics for card in bus 01:07.0: > Modem chipset detected on > NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI " > CLASS=0703 > PCIDEV=8086:1080 > SUBSYS=8086:1000 > IRQ=9 > IDENT=INTEL537EP > > For candidate modem in: 01:07.0 > 0703 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI > Primary device ID: 8086:1080 > Support type needed or chipset: INTEL537EP > > > > Since 2006, Intel appears to have ceased its modem code updates for Linux. > The outdated official Intel support packages can be accessed through: > http://developer.intel.com/design/modems/support/drivers.htm > Beneficially, Philippe Vouters has been provided updates as the Linux > kernel evolves. > But intensive personal support is not feasible, see: > http://archives.linmodems.org/24939 > The code for the INTEL537 and INTEL536 chipset modems is at > http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/ > > For Ubuntu Linux users with Intel 536 and 537 chipsets, there are driver > installation packages available thru > http://groups.google.com/group/ubuntu-modems > > Read DOCs/Intel.txt and Modem/DOCs/YourSystem.txt for follow through > guidance. > > > Writing DOCs/Intel.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.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.26-2-686/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 needed. The also > required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev > packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at > http://packages.ubuntu.com > or comparable Repository for other Linux distros. > When compiling ALSA drivers, the utility "patch" will also be needed. > > > Compressed files at: /usr/src/linux-source-2.6.26.tar.bz2 > > For Debian and some related distributions, a package kernel-kbuild-2.6-26 > may be needed to support driver compiling. > > > 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: > -rwsr-xr-- 1 root dip 269156 2008-11-28 12:48 /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 > asyncmap 0 > auth > 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 > > Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1 > 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/80-drivers.rules:SUBSYSTEM=="atm", RUN+="dsl-modem.agent" > Within /etc/modprobe.conf files: > /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 > /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 -------- > > For Debian users, the linux-headers-2.6.26-2-686.deb can be used instead > of kernel-source/ > > >
