Install from .iso Fails

[Polytropon]

On Sun, 1 Sep 2019 12:37:21 -0700, Thomas D. Dean wrote:
> 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.

You should verify that the network can be reached, routing
and name resolution work. If you see no error message, you
_could_ take that for granted, but it's always useful to
make sure it _really_ works.

This is the primary reason I use DVD #1: It allows me to
install a fully working OS, a point from where I can configure
network as needed, and then perform installation from external
sources. No "half-baked" things. ;-)



> I did not choose to install a MBR, maybe this is some default?

Did you choose automatic layout? Today, MBR is not the
default anymore. GPT is. There are only very few reasons
one would choose to use MBR partitioning.



> Killing all the install processes BEFORE they did anything should not 
> cause a problem.

Depends on when a certain step is being performed, e. g.,
editing or creating a partition table before initializing
filesystems, initializing filesystems before copying files.



> 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.

Yes, this is a problem sometimes.




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...