Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133)

> The .iso files are for a dvd install. If you want to use a usb, download
> the .img files.
> 
> FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img
> <https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-memstick.img>

The FreeBSD projects amd64 .iso images are hybrid now,
they should work both as a memstick image and as a burned .iso.

IFF this is failing it is a bug and should be addressed.

file FreeBSD-13.0-CURRENT-amd64-20181213-r342020-disc1.iso
FreeBSD-13.0-CURRENT-amd64-20181213-r342020-disc1.iso: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1758779 sectors

file FreeBSD-12.0-CURRENT-amd64-20171206-r326622-disc1.iso
FreeBSD-12.0-CURRENT-amd64-20171206-r326622-disc1.iso: ISO 9660 CD-ROM filesystem data '12_0_CURRENT_AMD64_CD' (bootable)


> ( or get the .xz version and extract it on your machine - it's smaller)
> 
> This "mount root" problem got me too, so don't feel alone.
> 
> Clay
> clay_at_fbsd13:~ $ uname -a
> FreeBSD fbsd13 13.0-CURRENT FreeBSD 13.0-CURRENT r350322 GENERIC  amd64
> 
> 
> On Mon, Jul 29, 2019 at 4:03 PM Nick Wolff <darkfiberiru_at_gmail.com> wrote:
> 
> > I just tested the snapshot from 20190725 and still am getting the root
> > mount rating for "boot on boot. I think something deeper broke between
> > r349133 and r349160 because even when I turn off wait for Root Mount on usb
> > root via a loader variable boot just get's stuck later on in the process.
> >
> > This is all happening on an x11-dpi-nt board.
> >
> >
> > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso
> >
> > On Mon, Jul 22, 2019 at 12:57 PM Nick Wolff <darkfiberiru_at_gmail.com>
> > wrote:
> >
> > > Hans,
> > >
> > > I'm building r350003  at the moment which is after the acpi change was
> > > moved into an unloaded module.
> > >
> > >
> > >
> > > On Mon, Jul 22, 2019 at 12:13 PM Hans Petter Selasky <hps_at_selasky.org>
> > > wrote:
> > >
> > >> On 2019-07-22 17:23, Nick Wolff wrote:
> > >> > Sorry for email spam but I was wrong. Just gets stuck now during
> > >> reproping
> > >> > a pci device after init happens(this is actually a trueos build which
> > is
> > >> > why you see openrc). That device it's getting stuck on is "Sky Lake-E
> > >> CBDMA
> > >> > Registers" which shouldn't have a driver attached.
> > >> >
> > >>
> > https://drive.google.com/file/d/19NFI0Dcupu3ZcVxbcr2vYFZ-iDqiIzkx/view?usp=sharing
> > >> >
> > >> > Though it maybe something else getting stuck at this point and that
> > just
> > >> > happens to be the last thing on the screen.
> > >> >
> > >>
> > >> There was a recent change to add an ACPI wrapper for the USB HUB driver,
> > >> but that was a bit premature and introduced some bugs. For now the ACPI
> > >> USB HUB wrapper is not enabled by default. Do you experience issues with
> > >> the latest -current ?
> > >>
> > >> --HPS
> > >>
> > >>
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> >
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

-- 
Rod Grimes                                                 rgrimes_at_freebsd.org