Thanks for all your help, hopefully my problem is now
resolved.
I am using the idle=pass argument in my lilo.conf
(reading man lilo.conf made me realize my prior
mistake) and ACPI is not compiled in my kernel (in
fact, no power management modules are). I never did
figure out how to use the hdparm
S. Alan Ezust wrote:
If it's years old, then it's still not fixed yet, because I get lockups during
actual disk-checks and boot sequences, and even during the installer
executions, way before any sound drivers are initialized. In both mandrake 9
and knoppix 3.3. I really doubt it had anything t
If it's years old, then it's still not fixed yet, because I get lockups during
actual disk-checks and boot sequences, and even during the installer
executions, way before any sound drivers are initialized. In both mandrake 9
and knoppix 3.3. I really doubt it had anything to do with a sound uti
Alan Ezust wrote:
You might also want to try adding a mem=nopentium - that seemed to
get rid of or reduce the lockup rate for me. I read about this on a
mandrake/nvidia faq back when I was using mandrake...
This is years old, and applies to a different scenario.
AMD CPUs were being blamed for
You might also want to try adding a mem=nopentium - that seemed to
get rid of or reduce the lockup rate for me. I read about this on a
mandrake/nvidia faq back when I was using mandrake...
On April 24, 2004 09:50 pm, Daniel Asarnow wrote:
> acpi=off, idle=poll give un "unrecognized token" error
acpi=off, idle=poll give un "unrecognized token" error
upon running lilo. Is there a specific stanza these
need to be in? I have lilo 22.5.9.
How exactly do I change UDMA3 with hdparm? I am still
unsure as to how this is done. I do not think it is
necessary for me to use acpi=off, since all powe
I had problems with lockups with X using nvidia driver until I
started booting with "acpi=off".
On Fri, Apr 23, 2004 at 12:35:26AM -0700, Daniel Asarnow wrote:
> Hi all,
> I'm sure many of you have heard of or experienced the
> nForce lockup problem. I was going through hell
> because of it, t
Thanks for responding!
I tried adding idle=poll to lilo.conf, but when I run
lilo to upadte it I get an "unrecognized token 'idle'
at or above line X' Is there a specific stanza where
this needs to be added? I thought it might be a lilo
versioning issue, but I seem to have the newest
version (22.
Dominique,
>
> You can also try to boot with idle=poll parameter (in your lilo.conf).
>
> With this parm my nforce2 mobo is stable.
Off course, you are correct. I didn't have time yet to test that..
Pim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
"Pim Bliek | PingWings.nl" <[EMAIL PROTECTED]> writes:
> Try changing your udma settings to udma3 f.i. Do this with
> hdparm. Worked for me. Theoretically this might be slower on your
> HDD performance, but it is a working workaround for the hangs.
You can also try to boot with idle=poll paramete
On Fri, Apr 23, 2004 at 12:35:26AM -0700, Daniel Asarnow wrote:
> to kernel 2.6.5 (from 2.6.4). I built my kernel and
> rebooted. I began to reinstall the nVidia drivers,
> and it locked up while building the nVidia kernel (I
If by 'nforce' you only are refering to the mobo chipset and not the v
We had some topics on this a week or two before.
Try changing your udma settings to udma3 f.i. Do this with hdparm. Worked
for me. Theoretically this might be slower on your HDD performance, but it
is a working workaround for the hangs.
Pim
> Hi all,
> I'm sure many of you have heard of or exper
Hi all,
I'm sure many of you have heard of or experienced the
nForce lockup problem. I was going through hell
because of it, then fixed the problem by recompiling
without APIC (or whatever that advanced power thing
is). Everything was great until I decided to upgrade
to kernel 2.6.5 (from 2.6.4).
13 matches
Mail list logo
