Re: Ide=nodma is "loosing too many ticks"

[Richard Molen]

--- Mark  wrote:
> I got the following problem after my FC3 install:
>
> Losing too many ticks!
> TSC cannot be used as a timesource.
> Possible reasons for this are:
>   You're running with Speedstep,
>   You don't have DMA enabled for your hard disk (see hdparm),
>   Incorrect TSC synchronization on an SMP system (see dmesg).
> Falling back to a sane timesource now.

Seems I had this problem when compiling a custom kernel for an
a7n8x board recently.  hdparm couldn't enable the dma either.  It
finally worked after adding the correct IDE driver (amd/nforce)
for that mobo.  Until I corrected the problem disk performance
was quite poor.
> I have ide=nodma in the boot parameters, since I was not able to
> complete the install with that parameter.
> If I try to take this parameter out of the grub.conf, I get the below
> and the machine does not boot:

You may need to compile a custom kernel with the correct driver for
your motherboard.  Or perhaps get try an updated kernel.

--
Richard Molen

__________________________________ 
Yahoo! Messenger 
Show us what our next emoticon should look like. Join the fun. 
http://www.advision.webevents.yahoo.com/emoticontest

Ide=nodma is "loosing too many ticks"

[Mark]

Is there no easier solution that this?
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Richard Molen
> Sent: Thursday, March 31, 2005 11:30 AM
> To: For users of Fedora Core releases
> Subject: Re: Ide=nodma is "loosing too many ticks"
>
> --- Mark  wrote:
> > I got the following problem after my FC3 install:
> >
> > Losing too many ticks!
> > TSC cannot be used as a timesource.
> > Possible reasons for this are:
> >   You're running with Speedstep,
> >   You don't have DMA enabled for your hard disk (see hdparm),
> >   Incorrect TSC synchronization on an SMP system (see
>
> dmesg). Falling
> > back to a sane timesource now.
>
> Seems I had this problem when compiling a custom kernel for 
> an a7n8x board recently.  hdparm couldn't enable the dma 
> either.  It finally worked after adding the correct IDE 
> driver (amd/nforce) for that mobo.  Until I corrected the 
> problem disk performance was quite poor.
> > I have ide=nodma in the boot parameters, since I was not able to 
> > complete the install with that parameter. If I try to take this 
> > parameter out of the grub.conf, I get the below and the
>
> machine does
> > not boot:
>
> You may need to compile a custom kernel with the correct 
> driver for your motherboard.  Or perhaps get try an updated kernel.
>
> --
> Richard Molen
>
> __________________________________ 
> Yahoo! Messenger 
> Show us what our next emoticon should look like. Join the fun. 
> http://www.advision.webevents.yahoo.com/emoticontest
>
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list

Ide=nodma is "loosing too many ticks"

[Mark]

I tried this "ide=nodma ide0=dma" but it did not fix my original problem either.

When it says "Falling back to a sane timesource now", what does it fall back to?
Can't I tell it to only use that timesource in the first place?

Thanks,

MARK
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Mark
> Sent: Thursday, March 31, 2005 12:20 PM
> To: 'For users of Fedora Core releases'
> Subject: RE: Ide=nodma is "loosing too many ticks"
>
> Is there no easier solution that this?
> > -----Original Message-----
> > From: [e-mail]
> > [mailto:[e-mail]] On Behalf Of Richard Molen
> > Sent: Thursday, March 31, 2005 11:30 AM
> > To: For users of Fedora Core releases
> > Subject: Re: Ide=nodma is "loosing too many ticks"
> >
> > --- Mark  wrote:
> > > I got the following problem after my FC3 install:
> > >
> > > Losing too many ticks!
> > > TSC cannot be used as a timesource.
> > > Possible reasons for this are:
> > >   You're running with Speedstep,
> > >   You don't have DMA enabled for your hard disk (see hdparm),
> > >   Incorrect TSC synchronization on an SMP system (see
> >
> > dmesg). Falling
> > > back to a sane timesource now.
> >
> > Seems I had this problem when compiling a custom kernel for
> > an a7n8x board recently.  hdparm couldn't enable the dma 
> > either.  It finally worked after adding the correct IDE 
> > driver (amd/nforce) for that mobo.  Until I corrected the 
> > problem disk performance was quite poor.
> > > I have ide=nodma in the boot parameters, since I was not able to
> > > complete the install with that parameter. If I try to take this 
> > > parameter out of the grub.conf, I get the below and the
> >
> > machine does
> > > not boot:
> >
> > You may need to compile a custom kernel with the correct
> > driver for your motherboard.  Or perhaps get try an updated kernel.
> >
> > --
> > Richard Molen
> >
> > __________________________________
> > Yahoo! Messenger 
> > Show us what our next emoticon should look like. Join the fun. 
> > http://www.advision.webevents.yahoo.com/emoticontest
> >
> > --
> > fedora-list mailing list
> > [e-mail]
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list