Date: Sun, 12 Dec 2010 12:08:39 -0500 From: Michael Voorhis <mvoorhis@cs.wpi.edu> To: freebsd-stable@freebsd.org Subject: Re: 8.2-BETA1 sysinstall: No USB devices found Message-ID: <4D050197.8010600@cs.wpi.edu> In-Reply-To: <AANLkTing5fjhL_Vzqh4ppbep_A_oQLDnqkqHn41fL-MC@mail.gmail.com> References: <AANLkTi=QBayVHr6YG4jCEv5H-Qo71Ztv1An0DKGYOV4R@mail.gmail.com> <20101212151704.197dddee@core.draftnet> <AANLkTing5fjhL_Vzqh4ppbep_A_oQLDnqkqHn41fL-MC@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/12/2010 11:28 AM, Brandon Gooch wrote: > How difficult would it be for the installer to automatically re-scan > for devices when USB is selected as install or Fix-it media? Ditto this. I do all my OS installs via a USB CD reader and it took me a little while to come up with the rescan-fix. I don't order rack servers with optical disk readers that I'll only be using once to install the OS, so all the stuff I build is installed from USB disc readers. My initial response was "how can we not know there's a CD reader when I just booted and read the installer from it." One of the 1st things sysinstall does is run a device scan deviceGetAll(), but that misses the USB device, apparently. The deviceRescan() calls the same function, but preceeds it with deviceReset(). All this stuff is in src/usr.sbin/sysinstall/devices.c. I'm not smart enough to make my own install disks right now; what would happen if the reset were inserted in front of the rescan (in main.c) at the beginning of sysinstall execution? That seems to be the only difference between the initial scan and the "option" scan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D050197.8010600>