Date: Sat, 09 Dec 2006 21:02:58 +0100 From: Jes <argonaut@vodafone.es> To: Volker <volker@vwsoft.com> Cc: Jes <argonaut@vodafone.es>, freebsd-usb@freebsd.org Subject: Re: Huawei E220 3G devices Message-ID: <20061209210258.396ec13e@zurich.theworld.es> In-Reply-To: <4576C724.8080401@vwsoft.com> References: <4576C724.8080401@vwsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Volker: I can do that but not now. I lend the E220 to a friend. As soon as I get it I'll send you. But... if you have umass as module and you don't load it on boot then I guess the E220 should be detected as an another usb modem... the problem is that you get it the device (/dev/ttyU0) but a strange message is shown when the E220 is detected: ucom0: Could not find interrupt in and /dev/ttyU0 cannot be accessed, nor minicom, nor ppp, .... The E220 has the same (umass) problem in Linux, but the trick (load usb_serial module before usb-storage) can be do it to get it work... and it works! Maybe Joao Barros have more info about... Greetings, Jes On Wed, 06 Dec 2006 14:35:32 +0100 Volker <volker@vwsoft.com> wrote: > Hi folks, > > I found something in the archives about trouble using an E220 Huawei > device. I'm wondering if somebody can send me the verbose output of > `usbctl' for that device as I don't have one? > > To me it seems this device is being detected by umass because of a > feature used under Windows. The E220 should be real plug'n play as > if a Windows user is plugging the device, the (Win) drivers are > installed straight from the box (no CDROM is necessary). I suspect > this is being done by a umass emulation. > > Supporting this device with it's basic functionality should be as > easy as defining vendor-ID and device-ID in ubsa and we're done. > > Again, is anybody able to provide me with the output of usbctl for > that device? > > Greetings, > > Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061209210258.396ec13e>