lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1273442132.12665.28.camel@angel>
Date:	Sun, 09 May 2010 22:55:32 +0100
From:	Peter Hicks <peter.hicks@...gs.co.uk>
To:	Nils Radtke <lkml@...nk-Future.de>
Cc:	linux-kernel@...r.kernel.org
Subject: RE: option.ko: ZTE MF636 support

Hi Nils

On Sun, 2010-05-09 at 16:22 +0200, Nils Radtke wrote:

> Similar symptoms are the long delay on opening of devices 0 and 2.
> /dev/ttyUSB0: status port
> /dev/ttyUSB2: modem port (not working)

Does "echo > /dev/ttyUSB0" return immediately, and "echo > /dev/ttyUSB2"
take around 15 seconds to return?

> What has been your solution to get the ZTE working?

I've blacklisted devices 0, 1 and 2 using the attached patch, taken
against 2.6.34-rc6.  It should be quite straightforward to modify this
for your device.

Without the patch, I'm able to use wvdial against ttyUSB3 to dial up,
but the device is unresponsive to anything apart from a PPP LCP
disconnect.

Regards,


Peter


View attachment "zte-mf636-blacklist.patch" of type "text/x-patch" (1351 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ