From owner-freebsd-questions@FreeBSD.ORG Fri Jan 16 11:09:07 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0CF51065672 for ; Fri, 16 Jan 2009 11:09:07 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from mail.unitedinsong.com.au (202-172-126-254.cpe.qld-1.comcen.com.au [202.172.126.254]) by mx1.freebsd.org (Postfix) with ESMTP id 7B8498FC1C for ; Fri, 16 Jan 2009 11:09:07 +0000 (UTC) (envelope-from rock_on_the_web@comcen.com.au) Received: from [192.168.0.199] (unknown [192.168.0.199]) by mail.unitedinsong.com.au (Postfix) with ESMTP id C964A40CC for ; Fri, 16 Jan 2009 12:50:40 +1000 (EST) From: Da Rock To: freebsd-questions@freebsd.org Content-Type: text/plain Date: Fri, 16 Jan 2009 12:49:17 +1000 Message-Id: <1232074157.22938.66.camel@laptop2.herveybayaustralia.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: USB problem during install X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 11:09:08 -0000 I was just running a check to see if I could install FreeBSD on my tv server and check the driver situation, but the cdboot failed with a usb issue- address not found. This occurred for 7.1, 7.0, and even 6.4. In my search I found many different reasons why it could be, but they were several years old (related to 5.x etc). Its always the same address 0x7fef1620, and I believe its the same port too. Currently the usb devices connected are an APC UPS, a Shintaro usb wireless keyboard with builtin mouse, a multi card reader, and I have two dvico tuner cards (dual fusions) which a dual dibcomms on each card connected to the system via their own usb chip. Based on my observations its actually hard to say which port is the problem, as the drivers are loaded and fork their own processes, so the error can show up later. Any ideas? Cheers