I will give that a try. And is 'uname - r' something I should replace with specific info, or should it be entered as "'uname - r'"? Thanks, Andrew -----Original Message----- From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx] Sent: Wednesday, June 20, 2012 11:14 AM To: Andrew Merczynski-Hait Cc: 'Marvin Stodolsky'; 'Antonio Olivares'; 'Discuss' Subject: Re: Andrew, United States, kernel 3.0.0-12-generic Andrew, just $ sudo cp /path/to/autoconf.h /lib/modules/`uname -r`/build/include/linux/autoconf.h Yours truly, Philippe Philippe Vouters (Fontainebleau/France) URL: http://vouters.dyndns.org/ SIP: sip:Vouters@xxxxxxxxxxxxxxxx Le 19/06/2012 20:31, Andrew Merczynski-Hait a écrit : > Phillipe, > > I have read that, and that’s why I brought up the fact that I was on Ubuntu. Is there any fix I can use? Can I just move the autoconf.h? > > ~Andrew > > -----Original Message----- > From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx] > Sent: Tuesday, June 19, 2012 12:51 PM > To: Marvin Stodolsky > Cc: Andrew Merczynski-Hait; Antonio Olivares; Discuss > Subject: Re: Andrew, United States, kernel 3.0.0-12-generic > > Marv, > > Read about Ubuntu and autoconf.h at > http://vouters.dyndns.org/Intel/Intel-Readme.html > I want change anything to the code about this. > > Philippe Vouters (Fontainebleau/France) > URL: http://vouters.dyndns.org/ > SIP: sip:Vouters@xxxxxxxxxxxxxxxx > > Le 19/06/2012 01:14, Marvin Stodolsky a écrit : >> Andrew, >> >> You are correct. intel-536EP-537EP_2012_05_19.tar.bz2 is only >> tarred, but not bzip2 compressed, >> though possible our System is automatically uncompressing during >> downloading, through I doubt it. >> Phillipe, please check >> >> It does open merely with: >> $ tar xf intel*.tar.bz2 >> into folder intel-536-537/ >> >> Afterward you will still have to install the package autoconf, which >> the makefile depends on, and Philipe will have to help too. >> >> Philippe, see below and >> http://askubuntu.com/questions/65073/missing-linux-autoconf-h >> Where should a fix be inserted into your makefiles? >> >> >> Marvin >> >> -------------------- >> intel-536-537$ make 537 >> cd coredrv; make clean >> make[1]: Entering directory `/home/marv/Downloads/tmp/intel-536-537/coredrv' >> rm -f *.ko .*.o.cmd *.mod.c .*.ko.cmd *.o *~ core Module.* modules.* >> into your makefilesrm -rf .tmp_versions >> make[1]: Leaving directory `/home/marv/Downloads/tmp/intel-536-537/coredrv' >> rm -f *.o *.ko >> Module precompile check >> Current running kernel is: 3.2.0-25-generic >> /lib/modules... autoconf.h does not exist >> please install kernel source >> make: *** [check] Error 1 >> >> >> >> >> On Mon, Jun 18, 2012 at 1:13 PM, Andrew Merczynski-Hait >> <andrewmh20@xxxxxxxxxx> wrote: >>> Then I get: >>> bzip2: (stdin) is not a bzip2 file. >>> Tar: Child returned status 2 >>> Tar: Error is not recoverable: exiting now >>> >>> -----Original Message----- >>> From: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] >>> Sent: Monday, June 18, 2012 1:06 PM >>> To: Andrew Merczynski-Hait >>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic >>> >>> typo, should be: >>> $ tar jxf intel*.tar.bz2 >>> >>> On Mon, Jun 18, 2012 at 1:05 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: >>>> Andrew, >>>> >>>> in your home folder with the tar ball, the proper COMMAND is; $ tar >>>> jxf intel*,tar.bz2 Then you still have to compile & install the >>>> drivers. >>>> >>>> MarvS >>>> >>>> On Mon, Jun 18, 2012 at 12:46 PM, Andrew Merczynski-Hait >>>> <andrewmh20@xxxxxxxxxx> wrote: >>>>> I tried to get rid of the previous driver attempt. When I tried to >>>>> install the .tar.bz2 driver, when attempting to extract it I got this error: >>>>> tar (child): intel-536-537EP_2012_05_19.tar.bz2: Cannot open: No >>>>> such file or directory tar (child): Error is not recoverable: >>>>> exiting now >>>>> tar: Child returned status 2 >>>>> tar: Error is not recoverable: exiting now >>>>> >>>>> Wvdial conf says: >>>>> Editing `/etc/wvdial.conf'. >>>>> >>>>> Scanning your serial ports for a modem. >>>>> >>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 >>>>> baud >>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 >>>>> baud >>>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>>> Modem Port Scan<*1>: S1 S2 S3 S4 S5 S6 S7 S8 Modem Port >>>>> Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 Modem Port Scan<*1>: >>>>> S17 S18 S19 S20 S21 S22 S23 S24 Modem Port Scan<*1>: S25 >>>>> S26 >>>>> S27 S28 S29 S30 S31 >>>>> >>>>> >>>>> 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://alumnit.ca/wiki/?WvDial >>>>> >>>>> When I had the .deb installed it didn't edit the wvdial.conf file >>>>> in any way. However, the file that supposedly says the install was >>>>> successful was created. >>>>> >>>>> I also haven't updated my system because I don't want to >>>>> accidently upgrade to a kernel that is not supported by the driver. >>>>> >>>>> Thanks, >>>>> Andrew >>>>> >>>>> -----Original Message----- >>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx] >>>>> Sent: Sunday, June 17, 2012 11:09 PM >>>>> To: Andrew Merczynski-Hait >>>>> Cc: discuss@xxxxxxxxxxxxx; Philippe Vouters >>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic >>>>> >>>>> Andrew, >>>>> >>>>> Would you mind posting posting >>>>> $ sudo wvdialconf /etc/wvdial.conf >>>>> >>>>> after the apparent successful install of the driver. If the modem >>>>> device is not found, then something else is in the way, like the >>>>> output from scanModem shows some IRQ trouble: >>>>> >>>>> \begin{QUOTE} >>>>> For candidate card in slot 01:01.0, firmware information and >>>>> bootup diagnostics are: >>>>> PCI slot PCI ID SubsystemID Name >>>>> ---------- --------- --------- -------------- >>>>> 01:01.0 8086:1080 1028:1000 Modem: Intel >>>>> Corporation FA82537EP 56K V.92 Data/Fax Modem PCI >>>>> >>>>> Modem interrupt assignment and sharing: >>>>> --- Bootup diagnostics for card in PCI slot 01:01.0 ---- [ >>>>> 0.165277] pci 0000:01:01.0: [8086:1080] type 0 class 0x000703 [ >>>>> 0.165296] pci 0000:01:01.0: reg 10: [mem 0xfeafe000-0xfeafefff] [ >>>>> 0.165306] pci 0000:01:01.0: reg 14: [io 0xde00-0xdeff] [ >>>>> 0.165366] pci 0000:01:01.0: PME# supported from D0 D3hot D3cold [ >>>>> 0.165371] pci 0000:01:01.0: PME# disabled [ 0.640344] serial >>>>> 0000:01:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ >>>>> 22 >>>>> [ 0.640536] 0000:01:01.0: ttyS5 at I/O 0xde08 (irq = 22) is a >>>>> 16450 [ 0.640645] 0000:01:01.0: ttyS6 at I/O 0xde10 (irq = 22) is >>>>> a 8250 [ 0.640751] 0000:01:01.0: ttyS7 at I/O 0xde18 (irq = 22) is >>>>> a 16450 [ 0.640860] 0000:01:01.0: ttyS8 at I/O 0xde20 (irq = 22) >>>>> is a 8250 [ 0.640969] 0000:01:01.0: ttyS9 at I/O 0xde28 (irq = 22) >>>>> is a 8250 [ 0.641611] 0000:01:01.0: ttyS16 at I/O 0xde60 (irq = >>>>> 22) is a 8250 >>>>> >>>>> The PCI slot 01:01.0 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 DOCs/Bootup.txt about possible fixes. >>>>> Send dmesg.txt along with ModemData.txt to >>>>> discuss@xxxxxxxxxxxxx if help is needed. >>>>> \end{QUOTE} >>>>> >>>>> Please send us something so we could try to find out what is going on? >>>>> >>>>> Regards, >>>>> >>>>> >>>>> Antonio >>>>> >>>>> >>>>> On Sun, Jun 17, 2012 at 9:53 PM, Andrew Merczynski-Hait >>>>> <andrewmh20@xxxxxxxxxx> wrote: >>>>>> Thank you for your help. >>>>>> >>>>>> I am not getting any errors like a kernel panic, the modem is >>>>>> just not recognized by anything. However, Scanmodem does recognize it. >>>>>> Nothing else will though. >>>>>> >>>>>> Before I posted this I did a lot of Google searching and I think >>>>>> I already tried your recommended method, and ran into problems >>>>>> because of the fact that ubuntu puts the autoconf.h file in a >>>>>> non-standard directory. I will try again and see what happens >>>>>> (and in case I had a slightly different file or something), >>>>>> however if it still doesn't work is there any way to fix the >>>>>> ubuntu issue, or will it be necessary to >>>>> install a different distro? >>>>>> Thanks, >>>>>> Andrew >>>>>> >>>>>> -----Original Message----- >>>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx] >>>>>> Sent: Sunday, June 17, 2012 10:25 PM >>>>>> To: Andrew Merczynski-Hait >>>>>> Cc: discuss@xxxxxxxxxxxxx; Philippe Vouters >>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic >>>>>> >>>>>> Dear Andrew, >>>>>> >>>>>> You have tried the driver but what do you get? >>>>>> >>>>>> You need to provide more information. We do not know if you got >>>>>> a kernel panic? a kernel mismatch? >>>>>> >>>>>> I would recommend that you uninstall the driver that you have >>>>>> installed and take a different approach, ie, >>>>>> >>>>>> Download: >>>>>> >>>>>> http://vouters.dyndns.org/Intel/intel-536EP-537EP_2012_05_19.tar. >>>>>> b >>>>>> z2 >>>>>> >>>>>> Carefully read the document: >>>>>> >>>>>> http://vouters.dyndns.org/Intel/Intel-Readme.html >>>>>> >>>>>> Then proceed to take steps to see if your modem may work. >>>>>> >>>>>> If you have downloaded the driver >>>>>> intel-536-537EP_2012_05_19.tar.bz2, >>>>>> copy it over to your Linux partition, then extract with $ tar >>>>>> -jxvf >>>>>> intel-536-537EP_2012_05_19.tar.bz2 >>>>>> $ cd intel-536-537 >>>>>> $ sudo make intel-536-537 >>>>>> $ sudo make install >>>>>> >>>>>> $ sudo wvdialconf /etc/wvdial.conf >>>>>> >>>>>> to see if scanmodem finds the modem. >>>>>> >>>>>> Let us know how this goes. >>>>>> >>>>>> Regards, >>>>>> >>>>>> >>>>>> Antonio >>>>>> >>>>>> On Sun, Jun 17, 2012 at 7:42 PM, Andrew Merczynski-Hait >>>>>> <andrewmh20@xxxxxxxxxx> wrote: >>>>>>> SCANMODEM RECOGNIZES THE MODEM, BUT NOTHING ELSE SEEMS TO. I >>>>>>> HAVE TRIED A BUNCH OF MOSTLY RANDOM STUFF, AND HAVE ALREADY >>>>>>> TRIED USING THE .DEB PACKAGED 537EP DRIVERS FROM >>>>>>> >>>>> https://sites.google.com/site/ubuntumodems/modem-driver-downloads-for-537ep. >>>>>>> THIS IS MY MODEM DATA.TXT FILE: >>>>>>> >>>>>>> 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 3.0.0-12-generic 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 m`ail filters. >>>>>>> So in a day, also check the Archived responses at >>>>>>> http://www.linmodems.org >>>>>>> -------------------------- System information >>>>>>> ---------------------------- CPU=i686, Ubuntu , >>>>>>> ALSA_version=1.0.24 Linux version 3.0.0-12-generic >>>>>>> (buildd@vernadsky) (gcc version 4.6.1 (Ubuntu/Linaro >>>>>>> 4.6.1-9ubuntu3) >>>>>>> ) #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 scanModem update of: >>>>>>> 2011_08_08 >>>>>>> >>>>>>> Distrib_ID=Ubuntu >>>>>>> DistribCodeName=oneiric >>>>>>> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >>>>>>> >>>>>>> >>>>>>> Presently install your Linux Distributions dkms package. It >>>>>>> provides for automated driver updates, following upgrade of your >>>>>>> kernel. For details see >>>>>>> http://linux.dell.com/projects.shtml#dkms >>>>>>> >>>>>>> There are no blacklisted modem drivers in /etc/modprobe* >>>>>>> files >>>>>>> >>>>>>> Potentially useful modem drivers now loaded are: >>>>>>> >>>>>>> >>>>>>> Attached USB devices are: >>>>>>> ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. >>>>>>> JM20329 SATA Bridge ID 062a:0000 Creative Labs Optical mouse If >>>>>>> a cellphone is not detected, see >>>>>>> http://ubuntuforums.org/archive/index.php/t-878554.html >>>>>>> A sample report is: >>>>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578. >>>>>>> h >>>>>>> tm >>>>>>> l >>>>>>> >>>>>>> If a USB modem or cellphone is attached and was not detected, >>>>>>> please provide available information in your request to >>>>>>> discuss@xxxxxxxxxxxxx >>>>>>> >>>>>>> Candidate PCI devices with modem chips are: >>>>>>> 01:01.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax >>>>>>> Modem PCI (rev >>>>>>> 04) High Definition Audio cards can host modem chips. >>>>>>> >>>>>>> For candidate card in slot 01:01.0, firmware information and >>>>>>> bootup diagnostics are: >>>>>>> PCI slot PCI ID SubsystemID Name >>>>>>> ---------- --------- --------- -------------- >>>>>>> 01:01.0 8086:1080 1028:1000 Modem: Intel >>>>>>> Corporation FA82537EP 56K V.92 Data/Fax Modem PCI >>>>>>> >>>>>>> Modem interrupt assignment and sharing: >>>>>>> --- Bootup diagnostics for card in PCI slot 01:01.0 ---- [ >>>>>>> 0.165277] pci 0000:01:01.0: [8086:1080] type 0 class 0x000703 [ >>>>>>> 0.165296] pci >>>>>>> 0000:01:01.0: reg 10: [mem 0xfeafe000-0xfeafefff] [ 0.165306] pci >>>>>>> 0000:01:01.0: reg 14: [io 0xde00-0xdeff] [ 0.165366] pci >>>>>>> 0000:01:01.0: PME# supported from D0 D3hot D3cold [ 0.165371] >>>>>>> pci >>>>>>> 0000:01:01.0: PME# disabled [ 0.640344] serial 0000:01:01.0: >>>>>>> PCI INT A -> GSI 22 (level, low) -> IRQ >>>>>>> 22 >>>>>>> [ 0.640536] 0000:01:01.0: ttyS5 at I/O 0xde08 (irq = 22) is a >>>>>>> 16450 [ 0.640645] 0000:01:01.0: ttyS6 at I/O 0xde10 (irq = 22) >>>>>>> is a 8250 [ 0.640751] 0000:01:01.0: ttyS7 at I/O 0xde18 (irq = >>>>>>> 22) is a 16450 [ 0.640860] 0000:01:01.0: ttyS8 at I/O 0xde20 >>>>>>> (irq = 22) is a 8250 [ 0.640969] 0000:01:01.0: ttyS9 at I/O >>>>>>> 0xde28 (irq = 22) is a 8250 [ 0.641611] 0000:01:01.0: ttyS16 at >>>>>>> I/O 0xde60 (irq = >>>>>>> 22) is a 8250 >>>>>>> >>>>>>> The PCI slot 01:01.0 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 DOCs/Bootup.txt about possible fixes. >>>>>>> Send dmesg.txt along with ModemData.txt to >>>>>>> discuss@xxxxxxxxxxxxx if help is needed. >>>>>>> >>>>>>> >>>>>>> === Finished firmware and bootup diagnostics, next deducing >>>>>>> cogent >>>>>> software. >>>>>>> === >>>>>>> >>>>>>> Predictive diagnostics for card in bus 01:01.0: >>>>>>> Modem chipset detected on >>>>>>> NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI " >>>>>>> CLASS=0703 >>>>>>> PCIDEV=8086:1080 >>>>>>> SUBSYS=1028:1000 >>>>>>> IRQ=22 >>>>>>> IDENT=INTEL537EP >>>>>>> >>>>>>> For candidate modem in: 01:01.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 now at: >>>>>>> http://vouters.dyndns.org/Intel/ , previously >>>>>>> http://x9000.fr Copies are also stored 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.6.1 >>>>>>> and the compiler used in kernel assembly: 4.6.1 >>>>>>> >>>>>>> linux-headers-3.0.0-12-generic resources needed for compiling >>>>>>> are not manifestly ready! >>>>>>> The patch utility is needed for compiling ALSA drivers, and >>>>>>> possibly others. >>>>>>> >>>>>>> If compiling is necessary packages must be installed, providing: >>>>>>> linux-headers-3.0.0-12-generic >>>>>>> >>>>>>> >>>>>>> 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 settings of: /etc/ppp/options asyncmap 0 noauth crtscts >>>>>>> lock hide-password modem 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.h >>>>>>> t >>>>>>> ml >>>>>>> >>>>>>> For guidance on FAX usage, get from >>>>>>> http://linmodems.technion.ac.il/packages/ get faxing.tar.gz It >>>>>>> has samples for a modem using port /dev/ttySL0, which must be >>>>>>> changed to match your modem's port. >>>>>>> >>>>>>> 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: >>>>>>> >>>>>>> Within /etc/modprobe.conf files: >>>>>>> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries >>>>>>> in order to blacklist unwanted modem drivers >>>>>>> /etc/modprobe.d/blacklist-modem.conf:# >>>>>>> blacklist snd-atiixp-modem >>>>>>> /etc/modprobe.d/blacklist-modem.conf:# >>>>>>> blacklist snd-via82xx-modem >>>>>>> /etc/modprobe.d/alsa-base.conf:options >>>>>>> snd-atiixp-modem >>>>>>> index=-2 /etc/modprobe.d/alsa-base.conf: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 -------- >>>>>>> >>>>>>> >>>>>>> ~Andrew Merczynski-Hait >>>>>>> >>>>>>> > >
