Date: Sun, 1 Sep 2019 12:37:21 -0700 From: "Thomas D. Dean" <tomdean@wavecable.com> To: freebsd-questions@freebsd.org Subject: Re: Install from .iso Fails Message-ID: <4f85bc7f-ace1-457c-211a-207acbb755a2@wavecable.com> In-Reply-To: <7ebb0c1b-335e-8b8e-0c1e-1e95ffe050b9@gmail.com> References: <74e749a3-b544-9bd5-d33a-31a05ede550d@wavecable.com> <0aa49415-4e1b-afe8-8e2a-b14935838ba0@wavecable.com> <c63846ca-74cd-510a-6262-9ba01e70918a@wavecable.com> <7ebb0c1b-335e-8b8e-0c1e-1e95ffe050b9@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/1/19 3:17 AM, MJ wrote: > > > On 1/09/2019 2:49 pm, Thomas D. Dean wrote: >> On 8/31/19 8:58 PM, Thomas D. Dean wrote: >>> On 8/31/19 8:49 PM, Thomas D. Dean wrote: >>>> I tried to install FreeBSD and failed. >>>> >>>> I downloaded FreeBSD-12.0-RELEASE-amd64-bootonly.iso, burned a CD, >>>> and booted. >>>> >>>> The boot sequence did not complete. It was in a loop >>>> ... >>>> xchi resetting the controller >>>> ... >>>> xchi resetting the controller >>>> >>>> I could get to the ptty that was logged in as root. ps -ax seemed OK. >>>> >>>> I think I had FreeBSD on this machine several years ago. >>>> >>>> Motherboard ASUS P9X79 PRO >>>> Intel(R) Core(TM) i7-3930K CPU >>>> >>>> Any ideas? >>>> >>>> Tom Dean >>> >>> Typo: xhci rather than xchi. >>> >>> From a Linux console, >>> >>> > lsusb >>> Bus 002 Device 005: ID 0cf3:3005 Atheros Communications, Inc. AR3011 >>> Bluetooth >>> Bus 002 Device 004: ID 04f2:0939 Chicony Electronics Co., Ltd >>> Bus 002 Device 003: ID 045e:0768 Microsoft Corp. Sidewinder X4 >>> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching >>> Hub >>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> Bus 006 Device 002: ID 2109:0810 VIA Labs, Inc. VL81x Hub >>> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>> Bus 005 Device 002: ID 2109:3431 VIA Labs, Inc. Hub >>> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching >>> Hub >>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> _______________________________________________ >> >> I switched to ttyv3 and killed all the bsdinstall processes. Then, I >> started bsdinstall. Looked good. When bsdinstalled started looking >> on the web for components to install, all the components were not found. >> >> pub/FreeBSD/releases/amd64/amd64/12.0-RELEASE/base.txz no address >> record found. >> > > I wouldn't go around killing install processes and then expect to have a > cogent system. > > If you are stuck with something, like the XHCI error, try a verbose boot: > > https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-start.html > > > It may, or may not, illuminate the issue a bit more. > >> But, the install did do one thing. >> >> I tried to install on ata3. bsdinstall actually created partitons on >> that disk. >> >> BUT, BSDINSTALL ALSO STABBED ATA0 AND MADE IT UNBOOTABLE. Thanks. > > Yikes, boot manager perhaps? Is this a multi-OS system? What's the boot > manager you are using? > >> >> I guess FreeBSD install is just broken. > > Maybe the web-based-install-everything-by-download is, but I doubt it. > Is the network showing an IP when you're booting and what's its route > table look like? Can you ping a known web site, ie, google.com > (indicating name resolution & some network operation)? > I chose DHCP to start the network and did not see any error messages. I did not ping anything. I did not choose to install a MBR, maybe this is some default? Killing all the install processes BEFORE they did anything should not cause a problem. Looking back over several years' notes I think this is a USB 3.0 problem. USB 3.0 is why I switched to Linux. It is necessary for some of my projects. I want to use FreeBSD because everything else is becoming windoze. I will wait until USB 3.0 is fixed... Tom Dean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f85bc7f-ace1-457c-211a-207acbb755a2>