USB keyboard in FreeBSD 10 amd64 installer
jrlokken at gmail.com
Thu Apr 17 19:28:16 UTC 2014
Thanks for all the suggestions, guys!
I ended up getting it to boot from USB, wireless keyboard worked great,
went off without a hitch, and I'm [very] happily rid of my last Winbox :)
I have a feeling that the combination of:
1) a very old, power hungry nVidia GPU
2) a very inexpensive PSU
3) my consistent bad luck with optical drives
were causing my issues with this machine. GoldMem found no issues with the
of Corsair after a couple of hundred passes. Thanks again.
On Thu, Apr 10, 2014 at 2:29 AM, Dave B <g8kbvdave at googlemail.com> wrote:
> Subject: Re: USB keyboard in FreeBSD 10 amd64 installer
> > On Tue, Apr 8, 2014 at 12:10 PM, Christian Campbell
> > <dcamp at alumni.ufl.edu>wrote:
> > One more point to check may be memory chips .
> > I have encountered such a case :
> > In a computer Windows XP was running successfully .
> > When I tried a FreeBSD or Linux , no one of them worked properly (
> > they were crashing unexpectedly ) . My opinion was that there were
> > incompatibilities between FreeBSD or Linux and its mainboard which was
> > a correct expectation .
> > Later on , even Windows XP started to crash .
> > The reason was a progressive memory chip defect .
> > Different operating systems may use different memory parts . One of
> > them may fail but others may work .
> > In such cases verifying correct functioning of memory chips may be
> > useful .
> > Even other computer parts may cause such problems because of order of
> > using parts or not using all of the parts or using different parts .
> > Thank you very much .
> > Mehmet Erol Sanliturk
> Yep!... Seen that sort of thing too.
> In my case, another XP box that had got stuck trying to do one particular
> update (I forget what it was for.)
> Long story short, after trying all the usual stuff, I eventualy booted a
> Memtest86 CD.
> After a long time (not the quickest PC, and it had at that time 384Meg of
> not much even for XP) it failed on one sticky bit, right at the top of
> memory, but
> only with the very last (most complex) test!...
> I isolated which memory stick was the issue by removing one and retesting,
> then swapping and testing again.
> On talking with the owner, they accepted my suggestion to max out the RAM
> anyway as it would be cheaper at that time, than trying to replace a single
> 256Meg stick. 1G of new ram later, it ran like a new machine!
> (And the suspect update applied itself with no error.)
> In your USB keyboard case, I'm not saying that memory issues will be the
> cause, just agreeing that it could be a posible cause.
> (I didn't know however, that the 64 bit versions of FBSD install disks,
> startup in
> 32 bit mode, that needs documenting somewhere, or on screen as you begin
> the process.)
> Memtest86 will boot and run on just about anything with an Intel or AMD
> 32 or 64 bit. Well worth having a copy in your toolkit.
> It can often be found on some Linux distro install CD's too, as an option
> to test
> the system before kicking off the main install, or booting to a live
> version of the
> The only downside, on a large ram system, even with a slick CPU, it can
> take "An age" to complete. That's the nature of real diagnositcs though.
> No affiliation, just another happy user.
> Regards to All.
> Dave B.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions