• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Red Hat 7.2---Installed just fine, but kernel panics during boot...[UPDATED: Fixed it!]

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
I agree completely, but I've seen enough broken packages that I've needed it a few times.

Guess I've been using Debian long enough I've forgotten about broken packages =)
 
Here we go: in order for me to get this joker workin, I had to INSTALL red hat underclocked down to 800 and with all my bios settings at safe. It installed fine, and when I rebooted, it worked fine.

Then I tried overclocking and performance tweaking back to where I was(before i set everything to safe).

It won't boot for me unless i have "Enhance Chip Performance" disabled in the bios. Everything else is the same as I was using for win2k overclocking.

Again, thank you everyone who helped.

zs

[enhance chip performance has to do with the northbridge, not with my proc, so i think this one is a VIA issue, but I'm not complaining 🙂]
 


<< Here we go: in order for me to get this joker workin, I had to INSTALL red hat underclocked down to 800 and with all my bios settings at safe. It installed fine, and when I rebooted, it worked fine.

Then I tried overclocking and performance tweaking back to where I was(before i set everything to safe).

It won't boot for me unless i have "Enhance Chip Performance" disabled in the bios. Everything else is the same as I was using for win2k overclocking.

Again, thank you everyone who helped.

zs

[enhance chip performance has to do with the northbridge, not with my proc, so i think this one is a VIA issue, but I'm not complaining 🙂]
>>



Did you try running the 686 optimized kernel instead of the Athlon optimized kernel?
 
Back
Top