Date: Tue, 03 Apr 2007 18:52:47 -0400 From: drgerlists@gmail.com (Dr. Gary E. RAFE) To: dougb@FreeBSD.org Cc: freebsd-usb@freebsd.org Subject: Re: Question!!! Message-ID: <4612dabf.1b6mzM7SsHPCaj3Q/ZWPFAUO@lmrmac.uhw.utoledo.edu> In-Reply-To: <45775CAB.1030606@FreeBSD.org> References: <4572FCFC.6010105@efir.od.ua> <20061203.120628.-116096346.imp@bsdimp.com> <45775CAB.1030606@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <dougb@FreeBSD.org> wrote: !> Try loading ucom, uftdi, uplcom and umodem. Chances are good one of !> these three is for your phone. ! !Thanks! The combination of ucom and umodem is enough to get power to !my Motorola Razr V3 so I can now recharge the battery while running !FreeBSD. :) Can I ask how you're using ucom(4), either compiled into a custom kernel or loaded as a kernel module ? In the case of the former, are you using this on a portable that interacts with ACPI or APM suspend/resume ? In the latter case, are you able to unload ucom.ko after you're done using it (and, presumably, umodem.ko ) ? I ask because I've had difficulty in the past with USB coming back after an APM suspend/resume cycle on Toshiba notebooks when USB devices are compiled into a custom kernel. OTOH, I haven't figured out why "kldunload ucom.ko" will not, complaining that the "device is busy" (most recently on a 6.1-R system). Regards, -- Dr Gary E RAFE: drgerlists at gmail dot com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4612dabf.1b6mzM7SsHPCaj3Q/ZWPFAUO>