Date: Wed, 21 Jul 2010 11:56:50 +0100 From: "Dave" <dave@g8kbv.demon.co.uk> To: Bruce Cran <bruce@cran.org.uk> Cc: freebsd-questions@freebsd.org Subject: Re: system hangs on; "Probing devices, please wait (this can take a while)... " Message-ID: <4C46E082.2568.4BA5F993@dave.g8kbv.demon.co.uk> In-Reply-To: <20100720234607.00002478@unknown> References: <4c455351.iveHHylYsmZKh9Xe%mueller6727@bellsouth.net>, <117437.98621.qm@web81103.mail.mud.yahoo.com>, <20100720234607.00002478@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Jul 2010 at 23:46, Bruce Cran wrote: > On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) > Rich <rl001@pacbell.net> wrote: > > > Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. > > Every other OS besides FreeBSD boots up and installs. What else can > > I check? > > It looks like it's stopping/spinning at the section where it parses > the slices/partitions. I don't know why it would be getting stuck > there, though. > > -- > Bruce Cran > Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. I know someone mentioned memory tests, but I didn't see what results they came up with, or how much memory you have. I do know however from my own frustrating experience in the past, that often some software will run just fine on bad memory, if the problems don't screw up the code or it's workspace. Where as other software will crash badly, making you think the program is bad. The same is sadly true of hard disk errors too! Did you run a recent memtest86 (self boot CD) and let it do several "Full" passes (can take many many hours per pass if you have lots of ram! And or a not so fast CPU) ? Just idle musings. Dave B.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C46E082.2568.4BA5F993>