-   Slackware (
-   -   automatic fsck on boot. fsck errors. (

nixel 05-16-2004 10:11 PM

automatic fsck on boot. fsck errors.
i was booting up linux and got this error while it was checking the hd:

Losing too many ticks!
TCS cannot be used as timesource
  Youre running with Speedstop
  You don't have DMA enabled (see hdparm)
  Incorrect TCS synchronization on an SMP system (see dmesg)

Falling back to sane timesource now.
spurious 8259A interrupt:  IRQ7

now i did hdparm and found that dma wasnt enabled. then i did an 'hdparm -d1 /dev/hdc1'.and got this:

setting using_dma to 1 (on)
HDIO_SET_DMA failed: Invalid argument
using_dma = 0 (off)

i searched and found this thread:

i will try recompiling the 2.6.5 kernel for this problem but i have questions about the compile. since i already have a current version of 2.6.5 it has a directory for its modules in /lib/modules/2.6.5. now, if i recompile this kernel, ill have 2 (supposedly) working kernels with ONE directory for both its modules? or will it overwrite the ones already in?

as far as the TCS error that im getting what is that?
if there are any other suggestions to fix these errors please reply. thanks and sorry for the lengthy post. :D

adz 05-17-2004 07:51 AM

If you recompile it as is then the old modules will be overwritten. This is not necessarily a bad thing since you'll probably not need them anyway. If you want to hold on to your old modules, you can always edit the Makefile and put something in the EXTRAVERSION field. That way the kernel will be called 2.6.5-<extra version> and the moduels will be put in the directory /lib/modules/2.6.5-<extra version>. The old kernel will probably (almost definetly) not be able to load the new modules.

All times are GMT -5. The time now is 03:35 AM.