Re: Andrew, United States, kernel 3.0.0-12-generic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Folks.

This report:
[   20.615687] 537ep:softcore_init_struct: Unregistering serial driver.
[  268.245922] Modules linked in: Intel537(+) bnep rfcomm bluetooth ppdev
snd_ca0106 snd_seq_midi snd_rawmidi snd_intel8x0 snd_ac97_codec ac97_bus
snd_pcm snd_seq_midi_event binfmt_misc dcdbas snd_seq snd_timer
snd_seq_device snd soundcore snd_page_alloc i915 parport_pc drm_kms_helper
drm shpchp i2c_algo_bit video lp parport usbhid hid firewire_ohci e100
usb_storage uas firewire_core crc_itu_t floppy [last unloaded: Intel537] [
268.246128]  [<f932e693>] sound_init+0xb3/0x190 [Intel537] [  268.246226]
[<f932ae58>] core_init_module+0x38/0x50 [Intel537] [  268.246331]
[<f974a008>] init_536+0x8/0x1000 [Intel537] [  268.246376] Intel 537EP card
found [  301.827656] 537: Loaded [ 1537.609618] PM: Syncing filesystems ...
done
------------
Is I suspect a major problem, and I doubt that anything else will work
until it is bypassed.

My suggestion is to proceed as follows.  Shutdown and detach a much
external hardware as possible.
Reboot and check the loaded modules with
$ lsmod
Starting with:
$ sudo modprobe -r 537ep
and otherwise proceeding from the top of the lsmod list, unload as
many modules as possible, shuting down processes as necessary.   Below
is the script I use for this purpose on my Mac Airbook but it will be
different for PCs
When as many modules as possible are unloaded,
$ modprobe 537ep
then
$ dmesg | grep 537
to asses if the module linking problem has been by passed.

MarvS

#!/bin/sh
# script name is:   stops
# activate with:  chmod +x stops
# run with:   sudo  ./stops
sudo modprobe -r joydev
sudo modprobe -r wl
sudo modprobe -r uvcvideo
sudo modprobe -r applesmc
sudo /etc/init.d/networking stop
sudo modprobe -r rfcomm
sudo modprobe -r btusb
sudo modprobe -r bnep
sudo /etc/init.d/pulseaudio stop
sudo modprobe -r snd-hda-intel
sudo modprobe -r parport_pc
sudo modprobe -r ppdev
sudo modprobe -r snd_seq_midi
sudo modprobe -r mei
sudo modprobe -r lp
sudo avahi-daemon --kill
sudo /etc/init.d/cups stop
sudo /etc/init.d/resolvconf stop
modprobe -r michael_mic
modprobe -r arc4
modprobe -r snd_hda_codec_hdmi
modprobe -r snd_hda_codec_cirrus
# end





On Fri, Jun 22, 2012 at 7:29 PM, Andrew Merczynski-Hait
<andrewmh20@xxxxxxxxxx> wrote:
> Okay, I realized that (I think) with Grub2 it’s a different file. I'll edit
> that as per the scan modem suggestions and let you know what happens. If
> that doesn't work I'll take a look at the archived thread and see what I can
> do.
>
> Thanks,
> Andrew
>
> -----Original Message-----
> From: Andrew Merczynski-Hait [mailto:andrewmh20@xxxxxxxxxx]
> Sent: Friday, June 22, 2012 7:02 PM
> To: 'Antonio Olivares'
> Cc: 'Philippe Vouters'; 'Linmodems'; 'Marvin Stodolsky'
> Subject: RE: Andrew, United States, kernel 3.0.0-12-generic
>
> I moved the pci card. Also, bootup.txt suggests that I add options to the
> kernel boot up line. However, for some reason there is no file
> "/boot/grub/menu.lst"
>
> I still get:
>
> andrew@ubuntu-11:~$ efax -i M2L3 -vewinchmart
> efax: Fri Jun 22 18:59:12 2012 efax v 0.9a-001114 Copyright 1999 Ed Casas
> efax: Fri Jun 22 18:59:12 2012 efax v 0.9a-001114 Copyright 1999 Ed Casas
> efax: 59:12 compiled Jun 21 2006 05:59:09
> efax: 59:12 argv[0]=efax
> efax: 59:12 argv[1]=-i
> efax: 59:12 argv[2]=M2L3
> efax: 59:12 argv[3]=-vewinchmart
> efax: 59:14 opened /dev/modem
> efax: 59:14 command  "Q0V1"
> efax: 59:14 waiting 2.0 s
> efax: 59:17 waiting 2.0 s
> efax: 59:17 .542 [ATQ0V1<CR><CR><LF>]
> efax: 59:17 .602 [OK<CR><LF>]
> efax: 59:17 response "OK"
> efax: 59:17 waiting 2.0 s
> efax: 59:19 command  "Q0V1"
> efax: 59:19 waiting 2.0 s
> efax: 59:19 .722 [ATQ0V1<CR><CR><LF>]
> efax: 59:19 .782 [OK<CR><LF>]
> efax: 59:19 response "OK"
> efax: 59:19 command  "M2L3"
> efax: 59:19 waiting 5.0 s
> efax: 59:19 .902 [ATM2L3<CR><CR><LF>]
> efax: 59:19 .962 [OK<CR><LF>]
> efax: 59:19 response "OK"
> efax: 59:20 command  "E0"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .083 [ATE0<CR><CR><LF>]
> efax: 59:20 .135 [OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:20 command  "I3"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .283 [<CR><LF>537EP <CR><LF>]
> efax: 59:20 .302 [<CR><LF>OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:20 command  "+FCLASS=?"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .454 [<CR><LF>0,1,2,2.0,8<CR><LF>]
> efax: 59:20 .474 [<CR><LF>OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:20 command  "+FCLASS=2.0"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .642 [<CR><LF>OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:20 command  "+FMI?"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .794 [<CR><LF>Intel Corporation<CR><LF>]
> efax: 59:20 .814 [<CR><LF>OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:20 command  "+FMM?"
> efax: 59:20 waiting 5.0 s
> efax: 59:20 .963 [<CR><LF>Intel V92 Data Fax Voice<CR><LF>]
> efax: 59:20 .963 [<CR><LF>H.324 video-ready rev. 1.0<CR><LF>]
> efax: 59:20 .982 [<CR><LF>OK<CR><LF>]
> efax: 59:20 response "OK"
> efax: 59:21 command  "+FMR?"
> efax: 59:21 waiting 5.0 s
> efax: 59:21 .134 [<CR><LF>RSA REV 4.04 <CR><LF>]
> efax: 59:21 .155 [<CR><LF>OK<CR><LF>]
> efax: 59:21 response "OK"
> efax: 59:21 using 537EP Intel Corporation Intel V92 Data Fax Voice RSA REV
> 4.04 in class 2.0
> efax: 59:21 command  "+FIP"
> efax: 59:21 waiting 5.0 s
> efax: 59:21 .314 [<CR><LF>ERROR<CR><LF>]
> efax: 59:21 response "ERROR"
> efax: 59:21 Warning: wrong response after command:  +FIP
>
>
> -----Original Message-----
> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
> Sent: Friday, June 22, 2012 6:17 PM
> To: Andrew Merczynski-Hait
> Cc: Philippe Vouters; Linmodems; Marvin Stodolsky
> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>
> Dear Andrew,
>
> Maybe you would need to try and move the Modem to another PCI slot?
> and/or try to follow the IRQ advice on the output of scanModem:
>
> ==============================================
> 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.
> ==============================================
>
> and try the same commands again.  Also try to run ungrab-winmodem before the
> efax call and post all the messages from your commands not just that it does
> the same:
>
> $ sudo modprobe ungrab-winmodem
> $ efax
>
> Copy and paste them and email them to us.
>
> Regards,
>
>
> Antonio
>
> On Fri, Jun 22, 2012 at 5:12 PM, Andrew Merczynski-Hait
> <andrewmh20@xxxxxxxxxx> wrote:
>> Disabling the serial port doesn't do anything either. Should I leave
>> it disabled, or put it back how it was?
>>
>> ~Andrew
>>
>> -----Original Message-----
>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>> Sent: Friday, June 22, 2012 5:42 PM
>> To: Andrew Merczynski-Hait; 'Antonio Olivares'
>> Cc: 'Linmodems'; 'Marvin Stodolsky'
>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>
>> Dear Andrew,
>>
>> There is an IRQ conflict between the serial driver and the Intel 537EP
>> driver. They both interrupt at PCI INT A -> GSI 22 (level, low) -> IRQ 22.
>> Can you look attentively at the specs of your modem board to watch out
>> for a possible jumper which would select another IRQ ? This can
>> explain the error returned on AT+FIP and the observed NO CARRIER.
>>
>> Dear Antonio,
>>
>> Do you know a way to prevent the serial driver from acting ? It
>> conflicts with the Intel 537EP driver.
>>
>> Dear Andrew, Antonio,
>>
>> A possible solution is to either invalidate the serial driver or
>> change the Intel 537EP modem IRQ.
>>
>> Philippe Vouters (Fontainebleau/France)
>> URL: http://vouters.dyndns.org/
>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>
>> Le 22/06/2012 23:17, Andrew Merczynski-Hait a écrit :
>>> andrew@ubuntu-11:~$ dmesg | grep IRQ
>>> [    0.000000] ACPI: IRQ0 used by override.
>>> [    0.000000] ACPI: IRQ2 used by override.
>>> [    0.000000] ACPI: IRQ9 used by override.
>>> [    0.000000] NR_IRQS:2304 nr_irqs:712 16 [    0.264046] ACPI: PCI
>>> Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12
>>> 15)
>>> [    0.264357] ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 6 7 9 10
>>> 11 12
>>> 15)
>>> [    0.264667] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10
>>> 11 12
>>> 15)
>>> [    0.264975] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10
>>> 11 12
>>> 15)
>>> [    0.265283] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10
>>> 11 12
>>> 15)
>>> [    0.265591] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10
>>> 11 12
>>> 15)
>>> [    0.265898] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10
>>> 11 12
>>> 15)
>>> [    0.266207] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10
>>> 11 12
>>> 15)
>>> [    0.267074] PCI: Using ACPI for IRQ routing [    0.267438] hpet0:
>>> at MMIO 0xfed00000, IRQs 2, 8, 0 [    0.464138] Serial: 8250/16550
>>> driver, 32 ports, IRQ sharing enabled [    0.640333] serial
>>> 0000:01:01.0: PCI INT A -> GSI 22 (level, low) ->
>> IRQ
>>> 22
>>> [    0.651008] ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level,
>>> low) -> IRQ 18 [    0.657120] ehci_hcd 0000:00:1d.7: PCI INT D -> GSI
>>> 23 (level, low) -> IRQ 23 [    0.728663] uhci_hcd 0000:00:1d.0: PCI
>>> INT A -> GSI 16 (level, low) -> IRQ 16 [    0.729019] uhci_hcd
>>> 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 0.729343]
>>> uhci_hcd 0000:00:1d.3: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [
>>> 1.422812] e100 0000:01:08.0: PCI INT A -> GSI 20 (level,
>>> low) -> IRQ
>> 20
>>> [    1.473846] firewire_ohci 0000:01:00.0: PCI INT A -> GSI 21
>>> (level,
>> low)
>>> -> IRQ 21
>>> [   19.275485] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) ->
>>> IRQ
>> 16
>>> [   20.860201] CA0106 0000:01:02.0: PCI INT A -> GSI 17 (level, low)
>>> ->
>> IRQ
>>> 17
>>> [   21.570776] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level,
>>> low) -> IRQ 17 [  129.505453] pci 0000:01:01.0: PCI INT A -> GSI 22
>>> (level, low) -> IRQ 22
>>>
>>> -----Original Message-----
>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>> Sent: Friday, June 22, 2012 5:13 PM
>>> To: Andrew Merczynski-Hait
>>> Cc: 'Linmodems'; 'Antonio Olivares'; 'Marvin Stodolsky'
>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>
>>> Andrew,
>>>
>>> Now what does happen if you do:
>>> $ dmesg | grep IRQ ?
>>>
>>> Philippe Vouters (Fontainebleau/France)
>>> URL: http://vouters.dyndns.org/
>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>
>>> Le 22/06/2012 22:24, Andrew Merczynski-Hait a écrit :
>>>>              CPU0
>>>>     0:         49   IO-APIC-edge      timer
>>>>     1:        145   IO-APIC-edge      i8042
>>>>     4:          4   IO-APIC-edge
>>>>     6:          3   IO-APIC-edge      floppy
>>>>     7:          0   IO-APIC-edge      parport0
>>>>     8:          1   IO-APIC-edge      rtc0
>>>>     9:          0   IO-APIC-fasteoi   acpi
>>>>    14:          0   IO-APIC-edge      ata_piix
>>>>    15:        186   IO-APIC-edge      ata_piix
>>>>    16:        828   IO-APIC-fasteoi   uhci_hcd:usb2, uhci_hcd:usb4,
>>>> i915
>>>>    17:        306   IO-APIC-fasteoi   snd_ca0106, Intel ICH5
>>>>    19:        692   IO-APIC-fasteoi   uhci_hcd:usb3
>>>>    20:        135   IO-APIC-fasteoi   eth0
>>>>    21:          4   IO-APIC-fasteoi   firewire_ohci
>>>>    23:      23981   IO-APIC-fasteoi   ehci_hcd:usb1
>>>> NMI:          0   Non-maskable interrupts
>>>> LOC:      14182   Local timer interrupts
>>>> SPU:          0   Spurious interrupts
>>>> PMI:          0   Performance monitoring interrupts
>>>> IWI:          0   IRQ work interrupts
>>>> RES:          0   Rescheduling interrupts
>>>> CAL:          0   Function call interrupts
>>>> TLB:          0   TLB shootdowns
>>>> TRM:          0   Thermal event interrupts
>>>> THR:          0   Threshold APIC interrupts
>>>> MCE:          0   Machine check exceptions
>>>> MCP:          1   Machine check polls
>>>> ERR:          0
>>>> MIS:          0
>>>>
>>>>
>>>> Thanks,
>>>> Andrew
>>>> -----Original Message-----
>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>> Sent: Friday, June 22, 2012 4:14 PM
>>>> To: Andrew Merczynski-Hait
>>>> Cc: 'Linmodems'; 'Antonio Olivares'; 'Marvin Stodolsky'
>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>
>>>> Andrew,
>>>>
>>>> The modem answers with:
>>>>
>>>> efax: 18:09 waiting 120.0 s
>>>> efax: 19:40 .532 [<CR><LF>NO CARRIER<CR><LF>]
>>>> efax: 19:40 response "NO CARRIER"
>>>> efax: 19:40 Error: unable to answer call
>>>> efax: 19:40 command  "Q0V1"
>>>> efax: 19:40 waiting 2.0 s
>>>>
>>>> Can you send us the following:
>>>> $ sudo cat /proc/interrupts
>>>> ???
>>>> Thank you in advance
>>>>
>>>> Philippe Vouters (Fontainebleau/France)
>>>> URL: http://vouters.dyndns.org/
>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>
>>>> Le 22/06/2012 21:22, Andrew Merczynski-Hait a écrit :
>>>>> Yes, if I hook up a phone to it I get a dial tone. My modem has two
>>>>> physical ports on the back, so now I switched where the phone line
>>>>> goes in to just to be sure. I still get the same error though. If I
>>>>> listen to the phone while running it, I can hear the line ring
>>>>> twice, and
>>>> then stop.
>>>>> If I don't terminate after that error after a while I get this:
>>>>>
>>>>> efax: 18:09 command  "+FNR=1,1,1,0"
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .132 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "+FLO=1"
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .304 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "+FBO=0"
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .472 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "+FCR=1"
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .644 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "+FIS?"
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .692 [<CR><LF>1,5,0,2,0,0,0,0<CR><LF>]
>>>>> efax: 18:09 .712 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "+FLI="                    ""
>>>>> efax: 18:09 waiting 5.0 s
>>>>> efax: 18:09 .784 [<CR><LF>OK<CR><LF>]
>>>>> efax: 18:09 response "OK"
>>>>> efax: 18:09 command  "A"
>>>>> efax: 18:09 waiting 120.0 s
>>>>> efax: 19:40 .532 [<CR><LF>NO CARRIER<CR><LF>]
>>>>> efax: 19:40 response "NO CARRIER"
>>>>> efax: 19:40 Error: unable to answer call
>>>>> efax: 19:40 command  "Q0V1"
>>>>> efax: 19:40 waiting 2.0 s
>>>>> efax: 19:40 .712 [<CR><LF>OK<CR><LF>]
>>>>> efax: 19:40 response "OK"
>>>>> efax: 19:40 command  "H"
>>>>> efax: 19:40 waiting 5.0 s
>>>>> efax: 19:41 .572 [<CR><LF>OK<CR><LF>]
>>>>> efax: 19:41 response "OK"
>>>>> efax: 19:41 done, returning 3 (invalid modem response
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>>> Sent: Friday, June 22, 2012 3:06 PM
>>>>> To: Andrew Merczynski-Hait
>>>>> Cc: 'Linmodems'; 'Antonio Olivares'; Marvin Stodolsky
>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>
>>>>> Andrew,
>>>>>
>>>>> With efax, you get this:
>>>>> efax: 47:42 command "Q0V1"
>>>>> efax: 47:42 waiting 2.0 s
>>>>> efax: 47:43 .072 [<CR><LF>NO CARRIER<CR><LF>]
>>>>> efax: 47:43 response "NO CARRIER"
>>>>> efax: 47:43 waiting 2.0 s
>>>>> efax: 47:45 command "Q0V1"
>>>>> efax: 47:45 waiting 2.0 s
>>>>> efax: 47:45 .252 [<CR><LF>OK<CR><LF>]
>>>>> efax: 47:45 response "OK"
>>>>>
>>>>> Are you sure your537EP modem is physically connected to a phone line ?
>>>>>
>>>>> Marv,
>>>>>
>>>>> I need your help for Ubuntu. Unlike Fedora, there is no
>>> /var/log/messages.
>>>>> Where does syslog logs on Ubuntu ????
>>>>>
>>>>> Philippe Vouters (Fontainebleau/France)
>>>>> URL: http://vouters.dyndns.org/
>>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>>
>>>>> Le 22/06/2012 20:49, Andrew Merczynski-Hait a écrit :
>>>>>> andrew@ubuntu-11:~$ efax -i M2L3 -vewinchmart
>>>>>> efax: Fri Jun 22 14:46:09 2012 efax v 0.9a-001114 Copyright 1999
>>>>>> Ed Casas
>>>>>> efax: Fri Jun 22 14:46:09 2012 efax v 0.9a-001114 Copyright 1999
>>>>>> Ed Casas
>>>>>> efax: 46:09 compiled Jun 21 2006 05:59:09
>>>>>> efax: 46:09 argv[0]=efax
>>>>>> efax: 46:09 argv[1]=-i
>>>>>> efax: 46:09 argv[2]=M2L3
>>>>>> efax: 46:09 argv[3]=-vewinchmart
>>>>>> efax: 46:11 opened /dev/modem
>>>>>> efax: 46:11 command  "Q0V1"
>>>>>> efax: 46:11 waiting 2.0 s
>>>>>> efax: 46:15 waiting 2.0 s
>>>>>> efax: 46:15 .120 [ATQ0V1<CR><CR><LF>]
>>>>>> efax: 46:15 .180 [OK<CR><LF>]
>>>>>> efax: 46:15 response "OK"
>>>>>> efax: 46:15 waiting 2.0 s
>>>>>> efax: 46:17 command  "Q0V1"
>>>>>> efax: 46:17 waiting 2.0 s
>>>>>> efax: 46:17 .300 [ATQ0V1<CR><CR><LF>]
>>>>>> efax: 46:17 .360 [OK<CR><LF>]
>>>>>> efax: 46:17 response "OK"
>>>>>> efax: 46:17 command  "M2L3"
>>>>>> efax: 46:17 waiting 5.0 s
>>>>>> efax: 46:17 .480 [ATM2L3<CR><CR><LF>]
>>>>>> efax: 46:17 .540 [OK<CR><LF>]
>>>>>> efax: 46:17 response "OK"
>>>>>> efax: 46:17 command  "E0"
>>>>>> efax: 46:17 waiting 5.0 s
>>>>>> efax: 46:17 .660 [ATE0<CR><CR><LF>]
>>>>>> efax: 46:17 .712 [OK<CR><LF>]
>>>>>> efax: 46:17 response "OK"
>>>>>> efax: 46:17 command  "I3"
>>>>>> efax: 46:17 waiting 5.0 s
>>>>>> efax: 46:17 .860 [<CR><LF>537EP <CR><LF>]
>>>>>> efax: 46:17 .880 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:17 response "OK"
>>>>>> efax: 46:17 command  "+FCLASS=?"
>>>>>> efax: 46:17 waiting 5.0 s
>>>>>> efax: 46:18 .032 [<CR><LF>0,1,2,2.0,8<CR><LF>]
>>>>>> efax: 46:18 .052 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:18 response "OK"
>>>>>> efax: 46:18 command  "+FCLASS=2.0"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:18 .220 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:18 response "OK"
>>>>>> efax: 46:18 command  "+FMI?"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:18 .372 [<CR><LF>Intel Corporation<CR><LF>]
>>>>>> efax: 46:18 .392 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:18 response "OK"
>>>>>> efax: 46:18 command  "+FMM?"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:18 .540 [<CR><LF>Intel V92 Data Fax Voice<CR><LF>]
>>>>>> efax: 46:18 .540 [<CR><LF>H.324 video-ready rev. 1.0<CR><LF>]
>>>>>> efax: 46:18 .560 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:18 response "OK"
>>>>>> efax: 46:18 command  "+FMR?"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:18 .712 [<CR><LF>RSA REV 4.04 <CR><LF>]
>>>>>> efax: 46:18 .732 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:18 response "OK"
>>>>>> efax: 46:18 using 537EP Intel Corporation Intel V92 Data Fax Voice
>>>>>> RSA REV
>>>>>> 4.04 in class 2.0
>>>>>> efax: 46:18 command  "+FIP"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:18 .892 [<CR><LF>ERROR<CR><LF>]
>>>>>> efax: 46:18 response "ERROR"
>>>>>> efax: 46:18 Warning: wrong response after command:  +FIP THEN IT
>>>>>> HANGS AND I TERMINATE IT AND GET THIS:
>>>>>>
>>>>>> ^Cefax: 46:18 command  "+FNR=1,1,1,0"
>>>>>> efax: 46:18 waiting 5.0 s
>>>>>> efax: 46:19 .060 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "+FLO=1"
>>>>>> efax: 46:19 waiting 5.0 s
>>>>>> efax: 46:19 .232 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "+FBO=0"
>>>>>> efax: 46:19 waiting 5.0 s
>>>>>> efax: 46:19 .400 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "+FCR=1"
>>>>>> efax: 46:19 waiting 5.0 s
>>>>>> efax: 46:19 .572 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "+FIS?"
>>>>>> efax: 46:19 waiting 5.0 s
>>>>>> efax: 46:19 .620 [<CR><LF>1,5,0,2,0,0,0,0<CR><LF>]
>>>>>> efax: 46:19 .640 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "+FLI="                    ""
>>>>>> efax: 46:19 waiting 5.0 s
>>>>>> efax: 46:19 .712 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 46:19 response "OK"
>>>>>> efax: 46:19 command  "A"
>>>>>> efax: 46:19 waiting 120.0 s
>>>>>> efax: 47:42 Error: terminating on signal 2
>>>>>> efax: 47:42 command  "Q0V1"
>>>>>> efax: 47:42 waiting 2.0 s
>>>>>> efax: 47:43 .072 [<CR><LF>NO CARRIER<CR><LF>]
>>>>>> efax: 47:43 response "NO CARRIER"
>>>>>> efax: 47:43 waiting 2.0 s
>>>>>> efax: 47:45 command  "Q0V1"
>>>>>> efax: 47:45 waiting 2.0 s
>>>>>> efax: 47:45 .252 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 47:45 response "OK"
>>>>>> efax: 47:45 command  "H"
>>>>>> efax: 47:45 waiting 5.0 s
>>>>>> efax: 47:46 .112 [<CR><LF>OK<CR><LF>]
>>>>>> efax: 47:46 response "OK"
>>>>>> efax: 47:46 done, returning 5 (terminated by signal)
>>>>>>
>>>>>>
>>>>>> There is no such file or directory /var/log/messages
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>>>> Sent: Friday, June 22, 2012 9:41 AM
>>>>>> To: Andrew Merczynski-Hait; Linmodems; Antonio Olivares
>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>
>>>>>> Andrew,
>>>>>>
>>>>>> Can you cut and paste the full efax dialog along with $ tail -f
>>>>>> /var/log/messages started in another terminal ?
>>>>>>
>>>>>> Philippe Vouters (Fontainebleau/France)
>>>>>> URL: http://vouters.dyndns.org/
>>>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>>>
>>>>>> Le 22/06/2012 02:19, Andrew Merczynski-Hait a écrit :
>>>>>>> Okay, using efax it seems that it sees the modem. It stops with,
>>>>> "Warning:
>>>>>>> wrong response after command: +FIP"
>>>>>>>
>>>>>>> What can I provide now to help?
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>>>>> Sent: Thursday, June 21, 2012 5:01 PM
>>>>>>> To: Andrew Merczynski-Hait
>>>>>>> Cc: 'Antonio Olivares'; 'Jacques Goldberg'; 'Marvin Stodolsky'
>>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>>
>>>>>>> Andrew,
>>>>>>>
>>>>>>> Can you follow the steps at
>>>>>>> http://vouters.dyndns.org/Intel/Intel-Readme.html ???
>>>>>>> It starts with testing using efax.
>>>>>>> Do not yet use wvdialconf unless you know what you do.
>>>>>>>
>>>>>>> Philippe Vouters (Fontainebleau/France)
>>>>>>> URL: http://vouters.dyndns.org/
>>>>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>>>>
>>>>>>> Le 21/06/2012 22:52, Andrew Merczynski-Hait a écrit :
>>>>>>>> andrew@ubuntu-11:~/Downloads/intel-536-537$ sudo wvdialconf
>>>>>>>> [sudo] password for andrew:
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>> $ dmesg | grep '537'
>>>>>>>> [   20.615679] Intel 537EP card found [   20.615683]
>>>>>>>> 537ep:softcore_init_struct: driver serial already
>>>>>> allocated
>>>>>>>> device.
>>>>>>>> [   20.615687] 537ep:softcore_init_struct: Unregistering serial
>>> driver.
>>>>>>>> [  268.245922] Modules linked in: Intel537(+) bnep rfcomm
>>>>>>>> bluetooth ppdev
>>>>>>>> snd_ca0106 snd_seq_midi snd_rawmidi snd_intel8x0 snd_ac97_codec
>>>>>>>> ac97_bus snd_pcm snd_seq_midi_event binfmt_misc dcdbas snd_seq
>>>>>>>> snd_timer snd_seq_device snd soundcore snd_page_alloc i915
>>>>>>>> parport_pc drm_kms_helper drm shpchp i2c_algo_bit video lp
>>>>>>>> parport usbhid hid firewire_ohci e100 usb_storage uas
>>>>>>>> firewire_core crc_itu_t floppy [last unloaded: Intel537] [
>>>>>>>> 268.246128] [<f932e693>]
>>>>>>>> sound_init+0xb3/0x190 [Intel537] [  268.246226] [<f932ae58>]
>>>>>>>> core_init_module+0x38/0x50 [Intel537] [  268.246331]
>>>>>>>> [<f974a008>]
>>>>>>>> init_536+0x8/0x1000 [Intel537] [  268.246376] Intel 537EP card
>>>>>>>> found [
>>>>>>> 301.827656] 537: Loaded [ 1537.609618] PM: Syncing filesystems ...
>>>>>>>> done.
>>>>>>>> [ 1537.613013] PM: Preparing system for mem sleep [ 1538.155375]
>>>>>>>> firewire_ohci 0000:01:00.0: restoring config space at offset 0x4
>>>>>>>> (was 0x0, writing 0xfeafd000)
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Antonio Olivares [mailto:olivares14031@xxxxxxxxx]
>>>>>>>> Sent: Thursday, June 21, 2012 4:44 PM
>>>>>>>> To: Andrew Merczynski-Hait
>>>>>>>> Cc: Philippe Vouters; Jacques Goldberg; Marvin Stodolsky
>>>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>>>
>>>>>>>> Dear Andrew,
>>>>>>>>
>>>>>>>> The driver is the same need not worry here.  After the
>>>>>>>> installation is apparently successful, please do as this and
>>>>>>>> send us the output of
>>>>>>>>
>>>>>>>> andrew@ubuntu-11:~/Downloads/intel-536-537$ sudo wvdialconf
>>>>>>>>
>>>>>>>> The modem driver should be loaded and the output of $ dmesg |
>>>>>>>> grep
>>>> '537'
>>>>>>>> in case that wvdialconf does not find the modem port.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>>
>>>>>>>> Antonio
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jun 21, 2012 at 3:20 PM, Andrew Merczynski-Hait
>>>>>>>> <andrewmh20@xxxxxxxxxx> wrote:
>>>>>>>>> Is that link any different than what I had earlier? The
>>>>>>>>> filenames are the same. I had to have it downloaded already in
>>>>>>>>> order to extract and build the driver……
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>>>>>>> Sent: Thursday, June 21, 2012 2:06 PM
>>>>>>>>> To: Andrew Merczynski-Hait
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cc: 'Jacques Goldberg'; 'Antonio Olivares'; 'Marvin Stodolsky'
>>>>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Dear Andrew,
>>>>>>>>>
>>>>>>>>> First of all, did you download
>>>>>>>>> http://vouters.dyndns.org/Intel/intel-536EP-537EP_2012_05_19.ta
>>>>>>>>> r
>>>>>>>>> .bz2
>>> ?
>>>>>>>>> Next I suggest you a reboot and afterwards:
>>>>>>>>> $ rm -rf /path/to/intel-536-537/ $ cd /path/to $ tar -jxvf
>>>>>>>>> intel-536EP-537EP_2012_05_19.tar.bz2
>>>>>>>>> $ cd intel-536-537/
>>>>>>>>> $ sudo make uninstall
>>>>>>>>> $ make 537
>>>>>>>>> $ sudo make install
>>>>>>>>> $ dmesg | grep 537
>>>>>>>>> $ stty -F /dev/modem -a
>>>>>>>>> $ dmesg | grep 537
>>>>>>>>>
>>>>>>>>> Yours truly,
>>>>>>>>>
>>>>>>>>> Philippe Vouters (Fontainebleau/France)
>>>>>>>>>
>>>>>>>>> URL: http://vouters.dyndns.org/
>>>>>>>>>
>>>>>>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>>>>>>
>>>>>>>>> Le 21/06/2012 19:36, Andrew Merczynski-Hait a écrit :
>>>>>>>>>
>>>>>>>>> $ dmesg | grep 536
>>>>>>>>>
>>>>>>>>> [    0.000000] Inode-cache hash table entries: 65536 (order: 6,
>>> 262144
>>>>>>>>> bytes)
>>>>>>>>>
>>>>>>>>> [    0.343343] TCP bind hash table entries: 65536 (order: 7,
>>>>>>>>> 524288
>>>>>>>>> bytes)
>>>>>>>>>
>>>>>>>>> [    0.343681] TCP: Hash tables configured (established 131072
>>>>>>>>> bind
>>>>>>>>> 65536)
>>>>>>>>>
>>>>>>>>> [    0.736536] NET: Registered protocol family 17
>>>>>>>>>
>>>>>>>>> [    2.453621] sd 2:0:0:0: [sda] Write cache: disabled, read cache:
>>>>>>>>> enabled, doesn't support DPO or FUA
>>>>>>>>>
>>>>>>>>> [   15.780536] EXT4-fs (sda1): mounted filesystem with ordered
>>>>>>>>> data
>>>>>> mode.
>>>>>>>>> Opts: (null)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I know you probably know what you’re doing J but I am using a
>>>>>>>>> 537 modem not
>>>>>>>>> 536 so I also did this:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> $ dmesg | grep 537
>>>>>>>>>
>>>>>>>>> [    0.647537] agpgart-intel 0000:00:00.0: Intel 865 Chipset
>>>>>>>>>
>>>>>>>>> [   19.664474] Intel 537EP card found
>>>>>>>>>
>>>>>>>>> [   19.664478] 537ep:softcore_init_struct: driver serial
>>>>>>>>> already allocated device.
>>>>>>>>>
>>>>>>>>> [   19.664482] 537ep:softcore_init_struct: Unregistering serial
>>>> driver.
>>>>>>>>>
>>>>>>>>> Thanks Andrew
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> From: Philippe Vouters [mailto:philippe.vouters@xxxxxxxxxxx]
>>>>>>>>> Sent: Thursday, June 21, 2012 4:17 AM
>>>>>>>>> To: Andrew Merczynski-Hait
>>>>>>>>> Cc: 'Jacques Goldberg'; 'Antonio Olivares'; 'Marvin Stodolsky'
>>>>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Andrew,
>>>>>>>>>
>>>>>>>>> Can you cut'n paste and send us the following:
>>>>>>>>> $ dmesg | grep 536
>>>>>>>>> Yours truly,
>>>>>>>>> Philippe
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Philippe Vouters (Fontainebleau/France)
>>>>>>>>>
>>>>>>>>> URL: http://vouters.dyndns.org/
>>>>>>>>>
>>>>>>>>> SIP: sip:Vouters@xxxxxxxxxxxxxxxx
>>>>>>>>>
>>>>>>>>> Le 21/06/2012 04:22, Andrew Merczynski-Hait a écrit :
>>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I apologize for causing an issue and I really do appreciate
>>>>>>>>> your
>>> help.
>>>>>>>>> I do realize you have a lot to deal with. (Incidentally, I did
>>>>>>>>> make sure to put uname –r  in quotes, I just didn’t know they
>>>>>>>>> were back
>>>>>>>>> quotes.)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> After copying over the autoconf.h file I seem to get a
>>>>>>>>> successful build and install. However, gnome-ppp and wvdial
>>>>>>>>> still cannot see that there is a modem installed. I see in the
>>>>>>>>> readme that for unknown distributions the modules and utilities
>>>>>>>>> will install but not the boot scripts. I presume that is
>>>>>>>>> probably an issue; can it be fixed? Would it simplify things a
>>>>>>>>> lot if I installed a different distro for the purpose
>>>>>>>> of using the modem?
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Andrew
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> From: Jacques Goldberg [mailto:goldberg@xxxxxxxxxxxxxxxxxxxx]
>>>>>>>>> Sent: Wednesday, June 20, 2012 1:41 PM
>>>>>>>>> To: Andrew Merczynski-Hait
>>>>>>>>> Cc: 'Antonio Olivares'; 'Philippe Vouters'; 'Marvin Stodolsky'
>>>>>>>>> Subject: Re: Andrew, United States, kernel 3.0.0-12-generic
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>
>>>
>>
>>
>



[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux