Don't sweat it. It's not a problem at all as long as you put "mem=nopentium" in your lilo boot parameters. As I said in my previous post, there is no noticeable performance degridation.
_john_
I only got the lockup while playing OpenGL games, and then just occasionally. The mem= option definitely fixed it, with no real visible loss of performance, though I haven't run any benchmarks.
Maybe I'll give 2.4.19 without it a whirl and see what happens.
_john_
I see one change log item related to AMD processors. Does anyone know if this or any other fix in this kernel fixes the nvidia/amd lockup problem (which can be worked around in 2.4.18 with the mem=nopentium boot parameter)?
_john_
Slashdot Mirror
next you will be telling me PowerPoint doesn't make you dumb after all either ;)
Don't sweat it. It's not a problem at all as long as you put "mem=nopentium" in your lilo boot parameters. As I said in my previous post, there is no noticeable performance degridation. _john_
I only got the lockup while playing OpenGL games, and then just occasionally. The mem= option definitely fixed it, with no real visible loss of performance, though I haven't run any benchmarks. Maybe I'll give 2.4.19 without it a whirl and see what happens. _john_
I see one change log item related to AMD processors. Does anyone know if this or any other fix in this kernel fixes the nvidia/amd lockup problem (which can be worked around in 2.4.18 with the mem=nopentium boot parameter)? _john_