Thanks Philippe, I am certain I have a single core that is multithreaded as I have built it many years ago. Here is the output of ./efax -vewinchmart [root@pb3000 efax]# ./efax -vewinchmart ./efax: Thu Jan 5 15:40:42 2012 efax v 0.9a-001114 Copyright 1999 Ed Casas ./efax: Thu Jan 5 15:40:42 2012 efax v 0.9a-001114 Copyright 1999 Ed Casas efax: 40:42 compiled Jan 5 2012 15:13:30 efax: 40:42 argv[0]=./efax efax: 40:42 argv[1]=-vewinchmart efax: 40:42 using built-in 128x0 font efax: 40:43 opened /dev/modem efax: 40:43 command "Q0V1" efax: 40:43 waiting 2.0 s efax: 40:44 .681 [ATQ0V1<CR><CR><LF>] efax: 40:44 .741 [OK<CR><LF>] efax: 40:44 response "OK" efax: 40:44 command "E0" efax: 40:44 waiting 5.0 s efax: 40:44 .761 [ATE0<CR><CR><LF>] efax: 40:44 .811 [OK<CR><LF>] efax: 40:44 response "OK" efax: 40:44 command "I3" efax: 40:44 waiting 5.0 s efax: 40:44 .861 [<CR><LF>537EP <CR><LF>] efax: 40:44 .881 [<CR><LF>OK<CR><LF>] efax: 40:44 response "OK" efax: 40:44 command "+FCLASS=?" efax: 40:44 waiting 5.0 s efax: 40:44 .931 [<CR><LF>0,1,2,2.0,8<CR><LF>] efax: 40:44 .951 [<CR><LF>OK<CR><LF>] efax: 40:44 response "OK" efax: 40:44 command "+FCLASS=2.0" efax: 40:44 waiting 5.0 s efax: 40:45 .021 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FMI?" efax: 40:45 waiting 5.0 s efax: 40:45 .071 [<CR><LF>Intel Corporation<CR><LF>] efax: 40:45 .091 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FMM?" efax: 40:45 waiting 5.0 s efax: 40:45 .141 [<CR><LF>Intel V92 Data Fax Voice<CR><LF>] efax: 40:45 .142 [<CR><LF>H.324 video-ready rev. 1.0<CR><LF>] efax: 40:45 .161 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FMR?" efax: 40:45 waiting 5.0 s efax: 40:45 .211 [<CR><LF>RSA REV 4.04 <CR><LF>] efax: 40:45 .231 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 using 537EP Intel Corporation Intel V92 Data Fax Voice RSA REV 4.04 in class 2.0 efax: 40:45 command "+FIP" efax: 40:45 waiting 5.0 s efax: 40:45 .291 [<CR><LF>ERROR<CR><LF>] efax: 40:45 response "ERROR" efax: 40:45 Warning: wrong response after command: +FIP efax: 40:45 command "+FNR=1,1,1,0" efax: 40:45 waiting 5.0 s efax: 40:45 .361 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FLO=1" efax: 40:45 waiting 5.0 s efax: 40:45 .431 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FBO=0" efax: 40:45 waiting 5.0 s efax: 40:45 .501 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FCR=1" efax: 40:45 waiting 5.0 s efax: 40:45 .571 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FIS?" efax: 40:45 waiting 5.0 s efax: 40:45 .721 [<CR><LF>1,5,0,2,0,0,0,0<CR><LF>] efax: 40:45 .741 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "+FLI=" "" efax: 40:45 waiting 5.0 s efax: 40:45 .911 [<CR><LF>OK<CR><LF>] efax: 40:45 response "OK" efax: 40:45 command "A" efax: 40:45 waiting 120.0 s Message from syslogd@pb3000 at Jan 5 15:40:47 ... kernel:[ 5123.808623] Disabling IRQ #19 efax: 42:16 .671 [<CR><LF>NO CARRIER<CR><LF>] efax: 42:16 response "NO CARRIER" efax: 42:16 Error: unable to answer call efax: 42:16 command "Q0V1" efax: 42:16 waiting 2.0 s efax: 42:16 .751 [<CR><LF>OK<CR><LF>] efax: 42:16 response "OK" efax: 42:16 command "H" efax: 42:16 waiting 5.0 s efax: 42:17 .621 [<CR><LF>OK<CR><LF>] efax: 42:17 response "OK" efax: 42:17 done, returning 3 (invalid modem response) and the output from subsequent dmesg: [ 583.232354] Intel 537 card found [ 583.240834] 8021q: 802.1Q VLAN Support v1.8 [ 592.290014] br0: no IPv6 routers present [ 592.338009] p3p1: no IPv6 routers present [ 2501.619746] pci 0000:01:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 2501.641799] 537: Loaded [ 5119.557097] 537: Loaded [ 5123.808126] irq 19: nobody cared (try booting with the "irqpoll" option) [ 5123.808185] Pid: 0, comm: swapper Not tainted 3.1.6-1.fc16.i686 #1 [ 5123.808188] Call Trace: [ 5123.808199] [<c090411b>] ? printk+0x2d/0x2f [ 5123.808206] [<c04af1b9>] __report_bad_irq+0x29/0xd0 [ 5123.808211] [<c04af41e>] note_interrupt+0x11e/0x1d0 [ 5123.808324] [<f9e1b367>] ? AfeIRQ+0x17/0x40 [Intel537] [ 5123.808330] [<c04afba0>] ? unmask_irq+0x30/0x30 [ 5123.808334] [<c04ad79e>] handle_irq_event_percpu+0x9e/0x200 [ 5123.808339] [<c04afba0>] ? unmask_irq+0x30/0x30 [ 5123.808343] [<c04ad932>] handle_irq_event+0x32/0x60 [ 5123.808348] [<c04afba0>] ? unmask_irq+0x30/0x30 [ 5123.808352] [<c04afbe7>] handle_fasteoi_irq+0x47/0xb0 [ 5123.808355] <IRQ> [<c0404d02>] ? do_IRQ+0x42/0xc0 [ 5123.808367] [<c0452f49>] ? irq_exit+0x69/0xa0 [ 5123.808373] [<c041e509>] ? smp_apic_timer_interrupt+0x59/0x90 [ 5123.808379] [<c09148b0>] ? common_interrupt+0x30/0x38 [ 5123.808385] [<c091007b>] ? kprobe_exceptions_notify+0x29b/0x420 [ 5123.808390] [<c040a49c>] ? mwait_idle+0x7c/0x1d0 [ 5123.808394] [<c04022d6>] ? cpu_idle+0xa6/0xe0 [ 5123.808399] [<c0477c43>] ? timer_list_show+0x923/0xec0 [ 5123.808405] [<c08ed515>] ? rest_init+0x5d/0x68 [ 5123.808411] [<c0bc3787>] ? start_kernel+0x352/0x358 [ 5123.808415] [<c0bc31c6>] ? loglevel+0x2b/0x2b [ 5123.808419] [<c0bc30a9>] ? i386_start_kernel+0xa9/0xaf [ 5123.808422] handlers: [ 5123.808442] [<c0741210>] ata_bmdma_interrupt [ 5123.808477] [<c0760320>] usb_hcd_irq [ 5123.808591] [<f9e156f0>] interrupt_handler [ 5123.808623] Disabling IRQ #19 [ 5214.377297] ------------[ cut here ]------------ [ 5214.377311] WARNING: at kernel/softirq.c:159 local_bh_enable_ip+0x60/0x90() [ 5214.377314] Hardware name: [ 5214.377316] Modules linked in: 8021q garp Intel537 bridge stp llc it87 hwmon_vid nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack joydev ppdev parport_pc parport snd_hda_codec_realtek netjet isdnhdlc snd_hda_intel snd_hda_codec snd_hwdep crc_ccitt mISDNipac mISDN_core snd_seq snd_seq_device r8169 mii snd_pcm iTCO_wdt iTCO_vendor_support i2c_i801 serio_raw microcode snd_timer snd soundcore snd_page_alloc uinput usb_storage firewire_ohci firewire_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan] [ 5214.377379] Pid: 2367, comm: efax Not tainted 3.1.6-1.fc16.i686 #1 [ 5214.377382] Call Trace: [ 5214.377389] [<c090411b>] ? printk+0x2d/0x2f [ 5214.377396] [<c044c122>] warn_slowpath_common+0x72/0xa0 [ 5214.377401] [<c0452950>] ? local_bh_enable_ip+0x60/0x90 [ 5214.377406] [<c0452950>] ? local_bh_enable_ip+0x60/0x90 [ 5214.377411] [<c044c172>] warn_slowpath_null+0x22/0x30 [ 5214.377416] [<c0452950>] local_bh_enable_ip+0x60/0x90 [ 5214.377421] [<c090d182>] _raw_spin_unlock_bh+0x12/0x20 [ 5214.377529] [<f9e17942>] linux_MT_ReleaseLock_timer_task+0x12/0x20 [Intel537] [ 5214.377622] [<f9e16c73>] RTS_Disable+0x33/0x40 [Intel537] [ 5214.377714] [<f9e16565>] clm_terminate+0x15/0x70 [Intel537] [ 5214.377720] [<c06cafb9>] ? tty_ldisc_flush+0x39/0x50 [ 5214.377811] [<f9e1540d>] close+0xd/0x30 [Intel537] [ 5214.377905] [<f9e188f7>] softserial_close+0x77/0xb0 [Intel537] [ 5214.377910] [<c06c4f8f>] tty_release+0x10f/0x4e0 [ 5214.377916] [<c0500fe4>] ? remove_vma+0x44/0x60 [ 5214.377920] [<c0500fe4>] ? remove_vma+0x44/0x60 [ 5214.377925] [<c050385f>] ? exit_mmap+0xcf/0x120 [ 5214.377930] [<c05293ea>] fput+0xba/0x220 [ 5214.377936] [<c0525eb4>] filp_close+0x54/0x80 [ 5214.377941] [<c044f72b>] put_files_struct+0x6b/0xb0 [ 5214.377946] [<c044f7ff>] exit_files+0x3f/0x50 [ 5214.377950] [<c044fc85>] do_exit+0x195/0x7c0 [ 5214.377955] [<c049f5a1>] ? audit_syscall_entry+0x1e1/0x2c0 [ 5214.377960] [<c0450547>] do_group_exit+0x37/0xa0 [ 5214.377965] [<c04505c8>] sys_exit_group+0x18/0x20 [ 5214.377969] [<c090d4f4>] syscall_call+0x7/0xb [ 5214.377973] ---[ end trace 3f5e2974f9d89aa2 ]--- so I do see [ 5214.377529] [<f9e17942>] linux_MT_ReleaseLock_timer_task+0x12/0x20 [Intel537] Regards, Patrick On Thu, Jan 05, 2012 at 09:02:36PM +0100, Philippe Vouters wrote: > Patrick, > > Thank you so much for this detailled call stack. If you read http://www.linuxgrill.com/anonymous/fire/netfilter/kernel-hacking-HOWTO-5.html, > the spinlock chapter, one driver's spinlock being involved in your > case, would it happen you run an SMP Fedora 16 distribution (as per > indicated by uname -a) on a single CPU configuration ? > > From your previous $ cat /proc/interrupts, IRQ 20 looks to be free > and there should not be any longer an IRQ conflict. > > Please provide me with the output of a command like $ sensors. Here > is what it tells for me: > > $ sensors > coretemp-isa-0000 > Adapter: ISA adapter > Core 0: +56.0 C (high = +86.0 C, crit = +100.0 C) > Core 1: +56.0 C (high = +86.0 C, crit = +100.0 C) > > So I am sure my processor is a dual core. I need to know with a > simple command output fact whether your processor is single or > multicore. Well note I am just in the preliminary phase of my > investigations. > > I fear we may also need efax to satisfy you. Can you download > http://vouters.dyndns.org/Intel/efax.zip ? > > $ unzip -aa efax.zip > $ cd efax > $ make -f Makefile_orig > $ ./efax -vewinchmart > > After efax run, do you still have in your Call Trace: > [<f9e07942>] linux_MT_ReleaseLock_timer_task+0x12/0x20 [Intel537] > ??? > > For the moment I prefer you run efax on your computer as I shall be > able to perform the very same test on my Dual Core processor. If we > can compare comparible things, it much ease troubleshooting. > > Philippe > > Le 05/01/2012 20:01, Patrick Boyadjian a écrit : > >Well I tried make uninstall and install again and it still fails...here is my dmesg output > > > >[ 694.046650] sound enabled > >[ 694.046664] Intel 537 card found > >[ 727.461869] pci 0000:01:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 > >[ 727.483870] 537: Loaded > >[ 744.163496] ------------[ cut here ]------------ > >[ 744.163511] WARNING: at kernel/softirq.c:159 local_bh_enable_ip+0x60/0x90() > >[ 744.163514] Hardware name: > >[ 744.163517] Modules linked in: Intel537 fuse 8021q garp bridge stp llc it87 hwmon_vid nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack joydev ppdev microcode snd_hda_codec_realtek netjet isdnhdlc crc_ccitt mISDNipac snd_hda_intel snd_hda_codec r8169 snd_hwdep mISDN_core mii snd_seq snd_seq_device serio_raw iTCO_wdt iTCO_vendor_support i2c_i801 snd_pcm parport_pc parport snd_timer snd soundcore snd_page_alloc uinput usb_storage firewire_ohci firewire_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: scsi_wait_scan] > >[ 744.163582] Pid: 2168, comm: wvdial Not tainted 3.1.6-1.fc16.i686 #1 > >[ 744.163585] Call Trace: > >[ 744.163592] [<c090411b>] ? printk+0x2d/0x2f > >[ 744.163599] [<c044c122>] warn_slowpath_common+0x72/0xa0 > >[ 744.163604] [<c0452950>] ? local_bh_enable_ip+0x60/0x90 > >[ 744.163608] [<c0452950>] ? local_bh_enable_ip+0x60/0x90 > >[ 744.163613] [<c044c172>] warn_slowpath_null+0x22/0x30 > >[ 744.163618] [<c0452950>] local_bh_enable_ip+0x60/0x90 > >[ 744.163623] [<c090d182>] _raw_spin_unlock_bh+0x12/0x20 > >[ 744.163740] [<f9e07942>] linux_MT_ReleaseLock_timer_task+0x12/0x20 [Intel537] > >[ 744.163831] [<f9e06c73>] RTS_Disable+0x33/0x40 [Intel537] > >[ 744.163921] [<f9e06565>] clm_terminate+0x15/0x70 [Intel537] > >[ 744.163928] [<c06cafb9>] ? tty_ldisc_flush+0x39/0x50 > >[ 744.164030] [<f9e0540d>] close+0xd/0x30 [Intel537] > >[ 744.164125] [<f9e088f7>] softserial_close+0x77/0xb0 [Intel537] > >[ 744.164131] [<c06c4f8f>] tty_release+0x10f/0x4e0 > >[ 744.164137] [<c0434285>] ? __wake_up+0x45/0x60 > >[ 744.164141] [<c06c5ab0>] ? no_tty+0x30/0x30 > >[ 744.164146] [<c0537396>] ? do_vfs_ioctl+0x86/0x5a0 > >[ 744.164151] [<c0473f51>] ? ktime_get_ts+0xe1/0x110 > >[ 744.164156] [<c05293ea>] fput+0xba/0x220 > >[ 744.164162] [<c0525eb4>] filp_close+0x54/0x80 > >[ 744.164167] [<c0525f3c>] sys_close+0x5c/0xa0 > >[ 744.164171] [<c090d4f4>] syscall_call+0x7/0xb > >[ 744.164174] ---[ end trace c8b0b4915f88a90c ]--- > >[pboyadjian@pb3000 ~]$ > > > > > >I don't have efax installed. > > > >The recurring error message seems always to be "no info from serial port" > > > >Patrick > > > >On Thu, Jan 05, 2012 at 09:35:09AM +0100, Philippe Vouters wrote: > >>Patrick, > >> > >>With your modem board at IRQ 20 and the modem driver can gives us > >>the output of each of the commands below: > >>1/ cd intel536-537/ > >>2/ sudo make uninstall > >>3/ dmesg | tail > >>4/ sudo make install > >>5/ dmesg | tail > >>6/ sudo cat /proc/interrupt > >>7/ efax -vewinchmart > >>8/ dmesg | tail > >> > >>The more facts you can provide us is the best. > >>Philippe > >> > >>Le 05/01/2012 04:55, Patrick Boyadjian a écrit : > >>>One more piece of info: > >>> > >>>My dmesg on boot says: > >>> > >>>92.709152] [<f9df78f7>] softserial_close+0x77/0xb0 [Intel537] > >>> > >>>So I can't really do a setserial for irq 20 and that i/o port. > >>> > >>> > >>>Patrick > >>> > >>>On Wed, Jan 04, 2012 at 08:22:38PM +0100, Philippe Vouters wrote: > >>>>Hi Patrick, > >>>> > >>>>Thank so much for your long reply. > >>>> > >>>>First of all about my write up. I do first suggest to use efax to > >>>>troubleshoot for the driver's installation correctness. It does help > >>>>much highlighting most of the problems before wvdial or kppp times > >>>>attemtps to connect to Internet. And the very advantage of the efax > >>>>command I provide is that it is at no financial cost but an analog > >>>>phone line subscription. The efax command just engage your phone > >>>>line without making a real call. So, except the analog phone > >>>>subscription line, the efax test is at strictly NO additional cost > >>>>for the end-user and provides lots of very informative data, > >>>>enabling to best troubleshoot in case of problems. > >>>> > >>>>As for /dev/ttyS*, I never felt the necessity, the modem code > >>>>creating a soft link between /dev/modem and the /dev/[537 | 536ep] > >>>>real device. /dev/modem is sufficient for both wvdial and kppp. With > >>>>an example on how to set up /etc/wvdial.conf on my Web site, you are > >>>>the first one to mention wvdialconf among all the driver end-users > >>>>since I inhierd this code back in Fedora Core 4. In fact, with all > >>>>my experience with the end-users of my work, it appears that the > >>>>most delicate thing is to correctly specify the suitable AT modem > >>>>commands. > >>>> > >>>>Regarding the other technical items of your skills, could I suggest > >>>>you if possible for you to open up a public Web site on your > >>>>computer or ask for Web space to your Internet provider in order to > >>>>share with others all your acquired knowledge. You would be > >>>>surprised like I am always delighted to notice it with my Web site > >>>>that the specific work you do for someone in peticular may also > >>>>interest a vast population over the planet. This is also true with > >>>>any knowledge whichever its nature and topic. Your efforts would > >>>>then be very rewarded the very same as mines. > >>>> > >>>>Back to your IRQ problem ! Did my suggestions regarding either a > >>>>possible jumper enabling IRQ selection on your modem board or > >>>>pluging in the modem into another PCI slot help you ? > >>>> > >>>>Yours truly, > >>>> > >>>> > >>>>Le 04/01/2012 19:25, Patrick Boyadjian a écrit : > >>>>>Hi Philippe, > >>>>> > >>>>>First off, well done on this write up. An area that you may like to improve on, as you have suggested to use wvdial as a test app after installation, would be the importance of wvdial needing to see the modem device on a /dev/ttyS* link for use by the wvdialconf tool. As it stands, you have recommended to symbolically link /dev/modem to /dev/537ep which is good, however, for the sake of less tech savvy users that would simply like to run wvdialconf a symbolic link to /dev/ttyS15 (15 being the experimental one) would allow wvdialconf to run successfully - advantages would be init string validation and correctness as well as the creation of /etc/wvdial.conf for post editing of the ISP username and password of course. > >>>>> > >>>>>As far as other technical subjects, you may guffaw at what I have been able to accomplish with my experience with Linux back when I first explored it back in late 1990's. That being said here are my main uses: > >>>>> > >>>>>- openvpn with bridging to allow me to vpn in to my linux machine and obtain an IP on my subnet to see other devices on my network > >>>>>- squid to filter traffic from my kids PC on a whitelist to the internet > >>>>>- httpd to host my archive of pics, tunes and movies for access by anyone in my subnet > >>>>>- chntpw app to constantly help my friends who have forgotten their windows NT admin account passwords > >>>>>- simple ffmpeg conversions such as: > >>>>> ffmpeg -i input.wav output.mp3 > >>>>> ffmpeg -i input.avi -b 64k -s 320x240 -r 24 output.mp4 > >>>>>- sendmail.mc and access config for the mail command for my scripts below > >>>>>- mbr backup and restore scripts (dd if=blah blah) > >>>>>- samba for giving my archives access to any UNC connection on my subnet > >>>>>- tcpdump commands to sniff my network > >>>>>- I have a network attached IP camera that ftps motion detected images to my linux machine on vsftpd > >>>>>- iptables of course to firewall the entire operation > >>>>> > >>>>>scripts I use: > >>>>> > >>>>>- a tclsh script that logs all incoming calls to a text file (i.e. date, number, name) > >>>>>- current ip script that checks my external ip every 30 mins and if it changes to email me the new one > >>>>>- script to email me the previous days proxy violations from squid > >>>>>- script to email me the previous days tty login attempts > >>>>>- script to email me the previous days call log > >>>>>- lmsensors script to read the internal temperature of my PC including fan speeds and basement temperature via snmpget...typical output is: > >>>>> > >>>>>[pboyadjian@pb3000 scripts]$ temp > >>>>> > >>>>>Basement Temperature = 17 C > >>>>> > >>>>>PC Internal Temperature = 34 C > >>>>>PC Chip Fan = 672 RPM > >>>>>PC Case Fan = 1132 RPM > >>>>> > >>>>>[pboyadjian@pb3000 scripts]$ > >>>>> > >>>>> > >>>>> > >>>>>If you would like my technical documentation on any of the above I would be more than happy to offer it. > >>>>> > >>>>> > >>>>>Regards, > >>>>>Patrick > >>>>> > >>>>> > >>>>>On Wed, Jan 04, 2012 at 03:23:19PM +0100, Philippe Vouters wrote: > >>>>>>Patrick, > >>>>>> > >>>>>>>>If there is anything I can ever do to repay you please let me know! > >>>>>> > >>>>>>Yes, indeed, you can repay us by attentively redeading my > >>>>>>litterature on the Intel modems subject at > >>>>>>http://vouters.dyndns.org/Intel/Intel-Readme.html and give us your > >>>>>>feedback upon it. > >>>>>> > >>>>>>What we do expect are your detailled impressions about this document > >>>>>>clarity and informations completeness. > >>>>>> > >>>>>>Post-scriptum : if you are looking for informations on either Linux, > >>>>>>Unix, OpenVMS or Windows, you may refer to another side of my Web > >>>>>>site at http://vouters.dyndns.org/tima/ > >>>>>>If, even better, you mail me with technical subjects I can study and > >>>>>>document, you'll make the worldwide IT community happy. > >>>>>> > >>>>>>Yours truly, > >>>>>>Philippe > >>>>>> > >>>>>>Le 04/01/2012 14:46, Patrick Boyadjian a écrit : > >>>>>>>Brilliant, it works! > >>>>>>> > >>>>>>>Philippe and Antonio, thank you so much for your support in this regard! > >>>>>>> > >>>>>>>If there is anything I can ever do to repay you please let me know! > >>>>>>> > >>>>>>>Regards, > >>>>>>>Patrick > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>On Wed, Jan 04, 2012 at 12:27:39PM +0100, Philippe Vouters wrote: > >>>>>>>>My work ought to support your modem. > >>>>>>>>[philippe@victor ~]$ grep e159:0001 intel-536-537/* > >>>>>>>>intel-536-537/makefile_537: vendor_device_ids[0]="e159:0001";\ > >>>>>>>> > >>>>>>>>The alternative to modifying the bash files is to download > >>>>>>>>http://vouters.dyndns.org/Intel/intel-536EP-537EP_2012_01_04.tar.bz2 > >>>>>>>> > >>>>>>>>Please reply whether you are fully satisfied or not. > >>>>>>>> > >>>>>>>>Regards, > >>>>>>>>Philippe > >>>>>>>> > >>>>>>>>Le 04/01/2012 04:03, Patrick Boyadjian a écrit : > >>>>>>>>>Thanks for the swift reply Antonio. > >>>>>>>>> > >>>>>>>>>Well originally I had a conexant chipset for a HCF modem that the linuxant group had drivers for, however those drivers ONLY worked on pre 3.x kernels so they broke when I upgraded. Dev team from Linuxant has informed me they are aware of the API break in the driver for the newer kernel and say they should fix it sometime soon. Meanwhile I dug up the Intel modem you see below to try and get it to work. > >>>>>>>>> > >>>>>>>>>So short answer I never should have upgraded!! :) > >>>>>>>>> > >>>>>>>>>Regards, > >>>>>>>>>Patrick > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>On Tue, Jan 03, 2012 at 07:47:12PM -0600, Antonio Olivares wrote: > >>>>>>>>>>Patrick, > >>>>>>>>>> > >>>>>>>>>>I am unsure if that modem in particular is served by Phillipe's > >>>>>>>>>>driver. IT does not seem to be a true INTEL 537 modem :( > >>>>>>>>>>However, there was a recent update to the driver since it was failing > >>>>>>>>>>to build up in Ubuntu and it was working fine in Fedora 15. Did you > >>>>>>>>>>make sure that you got the latest driver available from Phillipe's > >>>>>>>>>>website? > >>>>>>>>>> > >>>>>>>>>>Oops sorry, you did get the latest one. Maybe Phillipe can comment > >>>>>>>>>>here to make sure that maybe something went wrong, or that it may be > >>>>>>>>>>specific to 537 modem, since the driver also works with 536 Intel > >>>>>>>>>>based modems. > >>>>>>>>>> > >>>>>>>>>>Regards, > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>Antonio > >>>>>>>>>> > >>>>>>>>>>BTW, > >>>>>>>>>>since you have experience with linux since the Red Hat days, did you > >>>>>>>>>>get to use this particular modem before? If you did and the drivers > >>>>>>>>>>worked, I see no reason why the modem should not work with the newer > >>>>>>>>>>kernels. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>On Tue, Jan 3, 2012 at 7:24 PM, Patrick Boyadjian > >>>>>>>>>><patrick@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > >>>>>>>>>>>Hi, > >>>>>>>>>>> > >>>>>>>>>>>This is my first attempt to contact this group so apologize in advance if I= don't provide sufficient information. > >>>>>>>>>>> > >>>>>>>>>>>I'm not exactly a newbie to linux and Fedora since I've used it back when i= t was called red hat...I've upgraded to Fedora 16 recently and boy how thin= gs have changed! Anyways, here is where I'm at: > >>>>>>>>>>> > >>>>>>>>>>>lspci shows my modem as: > >>>>>>>>>>>01:01.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISD= N interface > >>>>>>>>>>> > >>>>>>>>>>>scanModem details as: > >>>>>>>>>>>For candidate card in slot 01:01.0, firmware information and bootup diagnos= tics are: > >>>>>>>>>>>PCI slot PCI ID SubsystemID Name > >>>>>>>>>>>---------- --------- --------- -------------- > >>>>>>>>>>>01:01.0 e159:0001 8086:0003 Communication controller: Ti= > >>>>>>>>>>>ger Jet Network Inc. Tiger3XX Modem/ISDN interface > >>>>>>>>>>> > >>>>>>>>>>>Modem interrupt assignment and sharing: > >>>>>>>>>>>--- Bootup diagnostics for card in PCI slot 01:01.0 ---- > >>>>>>>>>>>[ 0.109098] pci 0000:01:01.0: [e159:0001] type 0 class 0x000780 > >>>>>>>>>>>[ 0.109120] pci 0000:01:01.0: reg 10: [io 0xa000-0xa0ff] > >>>>>>>>>>>[ 0.109133] pci 0000:01:01.0: reg 14: [mem 0xf1004000-0xf1004fff] > >>>>>>>>>>>[ 0.109200] pci 0000:01:01.0: supports D2 > >>>>>>>>>>>[ 0.109203] pci 0000:01:01.0: PME# supported from D0 D2 D3hot D3cold > >>>>>>>>>>>[ 0.109209] pci 0000:01:01.0: PME# disabled > >>>>>>>>>>> > >>>>>>>>>>>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. > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>Predictive diagnostics for card in bus 01:01.0: > >>>>>>>>>>> Modem chipset detected on > >>>>>>>>>>>NAME=3D"Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISD= N interface" > >>>>>>>>>>>CLASS=3D0780 > >>>>>>>>>>>PCIDEV=3De159:0001 > >>>>>>>>>>>SUBSYS=3D8086:0003 > >>>>>>>>>>>IRQ=3D11 > >>>>>>>>>>>HDA2=3D00:1b.0 > >>>>>>>>>>>IDENT=3DINTEL537 > >>>>>>>>>>> > >>>>>>>>>>>For candidate modem in: 01:01.0 > >>>>>>>>>>> 0780 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISD= N interface > >>>>>>>>>>> Primary device ID: e159:0001 > >>>>>>>>>>>Support type needed or chipset: INTEL537 > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>So I visited http://vouters.dyndns.org/Intel/ and heeded Philippe's note to= > >>>>>>>>>>>: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>If you execute a 3.x.y kernel, download: > >>>>>>>>>>> > >>>>>>>>>>>../Intel/intel-536EP-537EP_2011_12_11.tar.bz2<http://vouters.dyndns.org/Int= > >>>>>>>>>>>el/intel-536EP-537EP_2011_12_11.tar.bz2> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>...and continued to untar and try to build. > >>>>>>>>>>> > >>>>>>>>>>>Issuing make clean and make 537 seem to work with a warning: > >>>>>>>>>>> > >>>>>>>>>>>[root@pb3000 intel-536-537]# make clean > >>>>>>>>>>>cd coredrv; make clean > >>>>>>>>>>>make[1]: Entering directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>rm -f *.ko .*.o.cmd *.mod.c .*.ko.cmd *.o *~ core Module.* modules.* rm -rf .tmp_versions > >>>>>>>>>>>make[1]: Leaving directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>rm -f *.o *.ko > >>>>>>>>>>>[root@pb3000 intel-536-537]# make 537 > >>>>>>>>>>>cd coredrv; make clean > >>>>>>>>>>>make[1]: Entering directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>rm -f *.ko .*.o.cmd *.mod.c .*.ko.cmd *.o *~ core Module.* modules.* rm -rf .tmp_versions > >>>>>>>>>>>make[1]: Leaving directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>rm -f *.o *.ko > >>>>>>>>>>> Module precompile check > >>>>>>>>>>> Current running kernel is: 3.1.6-1.fc16.i686 > >>>>>>>>>>> /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 > >>>>>>>>>>>make[1]: Entering directory `/root/intel-536-537' > >>>>>>>>>>>Building for 537 > >>>>>>>>>>>3.1.6-1.fc16.i686 > >>>>>>>>>>>make[2]: Entering directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>make -C /lib/modules/3.1.6-1.fc16.i686/build M=3D/root/intel-536-537/coredr= v modules > >>>>>>>>>>>make[3]: Entering directory `/usr/src/kernels/3.1.6-1.fc16.i686' > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/coredrv.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/clmmain.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/rts.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/task.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/uart.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/wwh_dflt.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/locks.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/softserial_io.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/softserial_ioctl.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/softserial.o > >>>>>>>>>>> CC [M] /root/intel-536-537/coredrv/afedsp_int.o > >>>>>>>>>>> LD [M] /root/intel-536-537/coredrv/Intel537.o > >>>>>>>>>>> Building modules, stage 2. > >>>>>>>>>>> MODPOST 1 modules > >>>>>>>>>>>WARNING: could not find /root/intel-536-537/coredrv/.537core.lib.cmd for /r= oot/intel-536-537/coredrv/537core.lib > >>>>>>>>>>> CC /root/intel-536-537/coredrv/Intel537.mod.o > >>>>>>>>>>> LD [M] /root/intel-536-537/coredrv/Intel537.ko > >>>>>>>>>>>make[3]: Leaving directory `/usr/src/kernels/3.1.6-1.fc16.i686' > >>>>>>>>>>>make[2]: Leaving directory `/root/intel-536-537/coredrv' > >>>>>>>>>>>make[1]: Leaving directory `/root/intel-536-537' > >>>>>>>>>>>[root@pb3000 intel-536-537]# > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>However, make install fails complaining about kernel version: > >>>>>>>>>>> > >>>>>>>>>>>[root@pb3000 intel-536-537]# make install > >>>>>>>>>>>make[1]: Entering directory `/root/intel-536-537' > >>>>>>>>>>>rm -f /usr/sbin/hamregistry.bin > >>>>>>>>>>>bash 537_inst > >>>>>>>>>>>running kernel 3.1.6-1.fc16.i686 > >>>>>>>>>>>unsupported kernel version: only 2.4.x and 2.6.x are supported > >>>>>>>>>>>make[1]: *** [install] Error 1 > >>>>>>>>>>>make[1]: Leaving directory `/root/intel-536-537' > >>>>>>>>>>>[root@pb3000 intel-536-537]# > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>Am I missing something? Any help here is super appreciated. > >>>>>>>>>>> > >>>>>>>>>>>Patrick > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>>-- > >>>>>>>>Philippe Vouters (Fontainebleau/France) > >>>>>>>>URL: http://vouters.dyndns.org/ > >>>>>>> > >>>>>> > >>>>>>-- > >>>>>>Philippe Vouters (Fontainebleau/France) > >>>>>>URL: http://vouters.dyndns.org/ > >>>>> > >>>> > >>>>-- > >>>>Philippe Vouters (Fontainebleau/France) > >>>>URL: http://vouters.dyndns.org/ > >>> > >> > >>-- > >>Philippe Vouters (Fontainebleau/France) > >>URL: http://vouters.dyndns.org/ > > > > -- > Philippe Vouters (Fontainebleau/France) > URL: http://vouters.dyndns.org/
