Best,
Christopher Svanefalk
On Sat, Aug 11, 2012 at 10:56 PM, Eddie G. O'Connor Jr. <eoconnor25@xxxxxxxxx> wrote:
On 08/07/2012 12:12 PM, Georgios Petasis wrote:
When it comes to Windows related hardware, that's going to be the solution 9 times out of 10! Save yer' data and re-install! Mind you there has been a time or two when I've had to re-install a Linux OS but it was almost always "Operator Error" than the hardware / software.Στις 2/8/2012 14:28, ο/η Heinz Diehl έγραψε:
On 02.08.2012, Georgios Petasis wrote:I am glad that the motherboard maker (Gigabyte) found a nice solution for me. This is their reply:
So, this is a processor bug? I would expect that Linux should detect theseIf I remember all correctly, there were two mainly independend issues
automatically...
with C1E in Linux, one which is processor-related, and one
BIOS-related. Processor-bugs are adressed by loading fixes via
microcode updates at boot-time. Check your dmesg output if this is the
case with your CPU. There should be something like that (laptop with i5 cpu):
[root@wildsau ~]# dmesg | grep microcode
microcode: CPU0 sig=0x20655, pf=0x10, revision=0x2
microcode: CPU0 updated to revision 0x3, date = 2011-09-01
microcode: CPU1 sig=0x20655, pf=0x10, revision=0x2
microcode: CPU1 updated to revision 0x3, date = 2011-09-01
microcode: CPU2 sig=0x20655, pf=0x10, revision=0x2
microcode: CPU2 updated to revision 0x3, date = 2011-09-01
microcode: CPU3 sig=0x20655, pf=0x10, revision=0x2
microcode: CPU3 updated to revision 0x3, date = 2011-09-01
microcode: Microcode Update Driver: v2.00 <tigran@xxxxxxxxxxxxxxxxxxxx>, Peter Oruba
So, my AMD 920 cpu is not only slow, it has also some errata incompatibleNearly all CPUs have errata :-)
with Fedora. Nice :D
The problem you encounter is not a Fedora one, it's most likely a
BIOS-problem, or the E400 routines in the kernel doesn't get triggered
by your hardware. It's impossible for me to see where the problem
finally originates in your case. The AMD people are generally cute ones and really
interested in such thing, so if you care to dig into this further, you
could consider mailing Borislav Petkov directly
(borislav.petkov@xxxxxxx).
If I remember that right, there was a fix pending around april/may
2011 for this, and a quick look into process.c shows that the E400
case is taken care of by the kernel. Look into your dmesg output and
boot.log (and other logfiles: /var/log/messages etc.) for "AMD E400
aware idle routine" or something similar/related.
Dear George Petasis,
Thank you for your kindly mail. Since all GIGABYTE MBs can fully support Windows OS without any problem. We suggest you can back up your data and reintall genuine Windows OS and then you can install supporting driver to run your system. However, your valuable feedback regarding to Linux will be noted to improve our future hardware design.
If you still have any further question or suggestion about our products/service, please do not hesitate to contact us. We will try our best to help you resolve the problem ASAP.
Best Regards,
GIGABYTE
Actually their answer to linux not booting without acpi_skip_timer_override, is "install windows".
But after backing up your data :D
Regards,
EGO I
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
