From owner-freebsd-hackers@freebsd.org Fri Dec 1 15:02:17 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EBC7E5D348 for ; Fri, 1 Dec 2017 15:02:17 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57FAF647DF for ; Fri, 1 Dec 2017 15:02:16 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vB1F2oln058374; Fri, 1 Dec 2017 07:02:56 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <160118029ff.ingegneriaforense@alice.it> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "ingegneriaforense@alice.it>" Subject: Re: USB_ERR_IOERR: is usb controller electrically "broken" ? Date: Fri, 01 Dec 2017 07:02:56 -0800 Message-Id: <07eaaf4997c405f5547d78b8ba80fc43@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:02:17 -0000 On Fri, 1 Dec 2017 10:55:08 +0100 (CET) "ingegneriaforense@alice=2Eit>" said > Hello everybody, > I'm new of this list=2E I'm installing the freebsd from CDROM=2E >=20 > During the installation I receive some messages: >=20 > >> usbd_req_re_enumerate: addre=3D3, set address failed (USB_ERR_IOERROR, > > ignored) > >> usbd_setup_device_desc: getting device descriptor at addr 3 failed, > > USB_ERR_IOERROR=20 > >> ugen0=2E3: at usbus0 (disconnected) > >> uhub_reattach_port: could not allocate new device >=20 > QUESTIONS: >=20 > 1=2E Please, can you tell me what this means ? Maybe is the USB controller > electrically "broken" or is due to a no correct software configuration of= its > parameters ? > These messages are shown during the whole installation process overwritin= g my > terminal and the sysinstall windows also=2E > Is a way to avoid this behaviour, configuring the freebsd installation ? >=20 > 2=2E Is there a way to take a screenshot of boot messages that are shown on= the > monitor during the installation process ? > Thanks very much in advance=2E As memory serves, I *think* this is the result of booting with the *verbose= *=20 switch set=2E One of the options available in the boot menu=2E This will also o= ccur should you have set: boot_verbose=3D"YES" in your loader=2Econf(5)=2E Solution: don't do that, if you don't want to receive those massages=2E :) >=20 > I apologize with you if my question is not related to the topics of this > mailing list=2E No apologies necessary=2E If there were an issue, you would have been gently directed to the correct mailing list=2E :) Oh, and welcome to the list, Vincenzo! :) >=20 > Vincenzo=2E --Chris >=20 > Forensic Consultant > Tribunale di Lecce >=20 > Studio: Strada di Garibaldi - Contrada Paradisi > 73010 Lequile (LE) >=20 > cell: 339=2E7968555 > skype: vincenzo=2Edi_salvo > _______________________________________________ > freebsd-hackers@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd=2Eorg= "