Gene Heskett a écrit :
Hmmm. Indeed the nforce2 has had a number of problems, but I'm not sure
why it would have changed recently. Can you bound at all the kernel
versions where it worked and where it broke? Additionally, do be sure
you have the most recent BIOS, I've seen a number of nforce2 issues be
resolved with a BIOS update.
I've already put more powerdown cycles (60 some) on my hard drives
fighting with the recent tv card problem, I'd like to get some uptime
in. All I know for sure is if I build 2.6.15-rc5 with acpi, ntpd
doesn't work. ntpdate does, but ntpd doesn't. And both dmesg and the
ntp.log (and -d's passed at launch time do not make it more verbose,
they just keep it from starting) are silent as to the diffs other than
the interrupt number shuffling in dmesg when its on. But I suspect it
may have started with 2.6.15-rc2, and I didn't build rc1. And I *think*
it worked as recently as 2.6.14.1 with it turned on. I've cleaned house
in /usr/src's so I don't have anything older. Sorry.
I have to agree with John Stultz. I am one with a nForce2 chipset where
updating to the latest BIOS have totaly solved the excatly same ntpd
problem.
Regards,
--
Jean-Christian de Rivaz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
