Re: Tapan Chugh, India kernel 2.6.27.5-117.fc10.i686

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

 



Philippe Vouters wrote:
> Dear Tapan,
>
> The message "Couldn't register serial port " in the dmesg log does NOT
> come from the Intel 537 driver but from another driver.
> [philippe@victor ~]$ grep "Couldn't register serial port "
> intel-536-537/*    
> [philippe@victor ~]$ grep "Couldn't register serial port "
> intel-536-537/*/*.c
> [philippe@victor ~]$ 
> Regards,
> -  
> http://vouters.dyndns.org:8080/
> Philippe Vouters (Fontainebleau/France)
>
>
> Le jeudi 18 juin 2009 à 09:07 +0530, Tapan Chugh a écrit :
>   
>>    
>> Dear Philippe,
>>
>> I found this line interesting in the dmesg log
>>
>> "Couldn't register serial port 0000:04:00.0: -28"
>>
>> also the modem is on 04:00.0 as detected by lspci
>>
>> "04:00.0 Modem: SILICON Laboratories Intel 537 [Winmodem] (rev 04)"
>>
>>
>>     
>
>
>   
    Dear Philippe,

The problem is that the modem does not work. The output of all the
commands matches. However efax does not work even now.

As  told by you,

I executed the command 

efax -vewinchmart

efax: Thu Jun 18 15:04:33 2009 efax v 0.9a-001114 Copyright 1999 Ed Casas
efax: Thu Jun 18 15:04:33 2009 efax v 0.9a-001114 Copyright 1999 Ed Casas
efax: 04:33 compiled Oct 24 2008 10:36:30
efax: 04:33 argv[0]=efax
efax: 04:33 argv[1]=-v
efax: 04:33 argv[2]=ewinchmart
efax: 04:33 Error: can't open serial port /dev/modem: Bad address
efax: 04:33 done, returning 2 (unrecoverable error)



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

  Powered by Linux