From:
"Patrick Bartek" <bartek047(a)yahoo.com>
To:
"Community support for Fedora users"
<users(a)lists.fedoraproject.org>
--- On Mon, 3/29/10, Nermin Celik <n.celik00(a)gmail.com> wrote:
I installed Fedora 12 x86-64 onto Hp Z800 workstation, had a problem
with software updates so used
$su -c 'yum update',
problem was fixed. Installed Adobe Acrobat Reader. Downloaded few other
programs but did not install them. Then, the screen froze. Tried
Ctrl-Alt-Del to restart, didn't work, so reset the machine from the
power button. Then someting very interesting happened - machine went
into a loop mode, started, failed to boot fedora, shutdown, restarted
by itself, failed to boot fedora, shutdown...etc about six times. Then
I just shut the machine off. Before fedora could be loaded, the pc just
shutdown in each case. At start tried pressing F10 but didn't work.
Has anyone else experinced a similar problem?
No. Never had anything like that happen, and I've been using Fedora as my primary OS
since Core 3.
How
did you "install" Acrobat Reader? Did you use yum and the Adobe repo?
How did you download the other programs that you didn't install? Yum?
Or did you download the rpm's directly from a non-repo site?
Really,
since you just installed 12, save yourself a lot of time: Do a clean
reinstall of 12 overwriting everything. At the first boot, before
updating, disable selinux, then in the terminal of your choice: enter
'su -'
give
the root password, and do your 'yum update'. After completing, set up
the other repos that you want, and install your other apps. The
following link will help a lot:
http://www.mjmwired.net/resources/
This can happen if you decide to take the bios properties and do what is called pushing to
get the last bit of performance. During the boot process, memory timing fails, and the
system crashes. Set the bios parameters to default and restart your system.
How do I know. I was experimenting at trying to boost system performance, and had this
happen to me. I could only increase performance by about 5% safely. Overclocking, and
pushing memory access is a trial and error exercise. Best to go with system defaults.
------------------
Regards
Leslie
Mr. Leslie Satenstein
mailto:lsatenstein@yahoo.com
mailto leslies(a)itbms.biz
www.itbms.biz