gnokii-users
[Top][All Lists]
Advanced

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

Re: huawei e220 problem


From: Pawel Kot
Subject: Re: huawei e220 problem
Date: Thu, 31 Mar 2011 09:28:40 +0200

Hi,

On Thu, Mar 31, 2011 at 02:44, ASTI Patron, Oliver L.
<address@hidden> wrote:
> Initializing AT capable mobile phone ...
> Serial device: opening device /dev/ttyUSB0
> Gnokii serial_open: open: No such file or directory
> Couldn't open ATBUS device: No such file or directory

Quite frankly it looks to me as gnokii unrelated problem.

> [223012.941607] usb 1-5: USB disconnect, address 7
> [223012.943289] option 1-5:1.0: device disconnected
> [223012.943492] option1 ttyUSB1: GSM modem (1-port) converter now 
> disconnected from ttyUSB1
> [223012.960010] option 1-5:1.1: device disconnected
> [223013.200017] usb 1-5: new high speed USB device using ehci_hcd and address 
> 8
> [223013.368114] usb 1-5: configuration #1 chosen from 1 choice
> [223013.404071] usb-storage: probe of 1-5:1.0 failed with error -5
> [223013.469219] usb 1-5: USB disconnect, address 8
> [223018.276016] usb 1-5: new high speed USB device using ehci_hcd and address 
> 9
> [223018.442048] usb 1-5: configuration #1 chosen from 1 choice
> [223018.476430] usb-storage: probe of 1-5:1.0 failed with error -5
> [223018.476450] option 1-5:1.0: GSM modem (1-port) converter detected
> [223018.476600] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1
> [223018.484059] usb-storage: probe of 1-5:1.1 failed with error -5
> [223018.484080] option 1-5:1.1: GSM modem (1-port) converter detected
> [223018.484193] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB2
> [223018.492508] usb-storage: probe of 1-5:1.2 failed with error -1
> [223018.503117] usb-storage: probe of 1-5:1.3 failed with error -1
> [223022.925965] option1 ttyUSB0: GSM modem (1-port) converter now 
> disconnected from ttyUSB0

For some reason the driver disconnects a port and then connects to the
other. I believe it started happening after kernel upgrade. So what I
can recommend is to find the last working kernel and report the
problem against the kernel.

-- 
Pawel Kot



reply via email to

[Prev in Thread] Current Thread [Next in Thread]