[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RTC problems in Debian on PowerEdge 1950

Daniel Akulenok wrote:

-----Original Message-----
From: Aenoch Lynn [mailto:aenoch.lynn@ucsf.edu] Sent: 16. oktober 2007 06:30 
To: Daniel Akulenok; debian-user@lists.debian.org
Subject: Re: RTC problems in Debian on PowerEdge 1950

I've had to do this on lots of my dell servers:

http://lists.debian.org/debian-kernel/2004/12/msg00378.html



[snip]


Hi Aenoch,
Do you know if this will also fix the errors that vmware spits out?
Kind regards,
Dak.


Hi Daniel,
I have a DELL desktop and I'm experiencing the same rtc problem. Anyway, it seems that the problem is basically related to the rtc kernel module not working properly on DELL systems. 

As stated in the man page of hwclock:

--directisa
[snip] Without this option, hwclock will try to use the /dev/rtc device (which it assumes to be driven by the rtc device driver). If it is unable to open the device (for read), it will use the explicit I/O instructions anyway.
Indeed, after removing the rtc kernel module with "modprobe -r rtc", hwclock works without adding "--directisa" on my DELL.
That said, I don't think that the solution kindly proposed by Aenoch will fix vmware's errors if it tries to access the hardware clock via /dev/rtc, but it *may* be possible that vmware uses a similar workaround to access the hardware clock if /dev/rtc is not available. It may be worth a try... 

Cheers,
izio
Reply to: