2.6.18 hangs during boot on ASUS M2NPV-VM motherboard
Ok - I don't understand why this bug is being ignored. It appears that this bug applies to many models of motherboards all using the new nVidia chipset for AM2 socket AMD processors causing these motherboards to lock up on boot. This bug has been reported for a long time and it appears that there seems to be some understanding as to what the problem is. Yet no one is fixing it.
So what's up with that? I know this is free software but I would think that someone would want to put out some effort to make Linux run on the AM2 systems. So why is this being ignored?
I compiled 2.6.18 and setting acpi_skip_timer_override to 0 instead of 1 makes the problem go away. Obviously the logic needs to e a little more complex than is but this shouldn't be that hard to resolve.
Quoted 4 lines · On Thu, 28 Sep 2006 09:52:24 -0700 Marc Perkel <[email protected]> wrote:
Ok - I don't understand why this bug is being ignored. It appears that this bug applies to many models of motherboards all using the new nVidia chipset for AM2 socket AMD processors causing these motherboards to lock up on boot. This bug has been reported for a long time and it appears that there seems to be some understanding as to what the problem is. Yet no one is fixing it.
Quoted 8 lines
So what's up with that? I know this is free software but I would think that someone would want to put out some effort to make Linux run on the AM2 systems. So why is this being ignored?
I compiled 2.6.18 and setting
acpi_skip_timer_overrideto 0 instead of 1 makes the problem go away. Obviously the logic needs to e a little more complex than is but this shouldn't be that hard to resolve.
I think the kernel _should_ be enabling acpi_skip_timer_override by itself, but isn't doing that for some reason.
Perhaps Andy can help. He may not even be aware of this problem...
Am Donnerstag 28 September 2006 22:14 schrieb Andrew Morton:
Quoted 8 lines
Quoted 5 lines
I compiled 2.6.18 and setting
acpi_skip_timer_overrideto 0 instead of 1 makes the problem go away. Obviously the logic needs to e a little more complex than is but this shouldn't be that hard to resolve.I think the kernel _should_ be enabling
acpi_skip_timer_overrideby itself, but isn't doing that for some reason.
Other way round. It should only enable it for broken chipsets. But it hasn't been defined what _are_ the broken chipsets.... currently it is enabled for all chipsets.
Quoted 2 lines
Perhaps Andy can help. He may not even be aware of this problem...
Na, he just choses not to say anything.
http://marc.theaimsgroup.com/?l=linux-kernel&m=115675009906807&w=2
Signature · 3 lines
(°= =°) //\ Prakash Punnoor /\\ V_/ \_V