[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FreeBSD



> It could be almost anything, really.  Memory is usually the worst - did
> you remove the previous memory and try new memory, or just add memory?
> If you just added, I'd try without the previous memory.
I put in new memory and I tried them one by one singly then in combination
to make sure there was no problem.
> 
> Otherwise, I'd try with a different motherboard, and if that doesn't fix
> it (or isn't possible), try without any non-essential stuff (network
> cards, &c.).
Problem is that all my motherboards are the same. So I guess that doesn't
help me much besides the machine is new.
> 
> My first bet is usually memory, then motherboard, then hardware
> conflicts (on older machines usually), and finally other hardware
> failure.
All the hardware is new andit worked fine when I tested it with SuSE linux
just to be sure. But well you never know. Someone was suggesting that 4.0
has a problem with realtek 8139 cards do you think this is true?
> 
> If you don't trust your hard drive, or if you get 'ad0: READ ERROR'
> message on FreeBSD 4.0, try 'sysctl -w hw.atamodes=pio,pio,pio'.
Nah! I trust my hard drive it is a brand new seagate.
> 
> Otherwise, if diagnosis evades you, a copy of /var/run/dmesg.boot, your
> kernel configuration, your exact FreeBSD version, and a full run-down of
> your hardware will be necessary.  You will probably get a good response
> from questions at FreeBSD.org if you include all this detail (I read that,
> but you can feel free to Cc: it to me).
> 
> Good luck,
> 
> Neil
> -- 
> Neil Blakey-Milner
> Sunesi Clinical Systems
> nbm at mithrandr.moria.org
> 

 Noah
ksemat at eahd.or.ug
 



-----
This is the afnog mailing list, managed by Majordomo 1.94.4

To send a message to this list, e-mail afnog at afnog.org
To send a requet to majordomo, e-mail majordomo at afnog.org and put
your request in the body of the message (i.e use "help" for help)

This list is mantained by owner-afnog at afnog.org