Re: Clock problems

2005-06-04 Thread v0n0
Javier Kohen wrote:

El lun, 30-05-2005 a las 12:38 -0400, John Baab escribi:

  

Every time I try to use hwclock I get this error:
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.



Make sure the rtc module is loaded, or compiled in the kernel.

  

Anyone have any ideas?  Odly enough if I change my clock preferences
to use UTC then it displays the correct time.



Well, maybe it is indeed set to UTC.

  

I'm using udev, hotplug and kernel 2.6 and I get the same error. Before
last update indeed, all was right. If I modprobe rtc the hardware clock
does get updated, but I can't understand why now the module doesn't get
loaded automatically.

-- 
Alessandro Dal Grande
Student In The University Of Padua - Computer Science
Linux Registered User #359258
System: GNU/Linux Debian Sid Pure64 on [EMAIL PROTECTED]
Kernel: 2.6.8-11-amd64-k8
Mail: Thunderbird
Chat: Kopete (ICQ) 150487234

Put the fan back into computing 




signature.asc
Description: OpenPGP digital signature


Re: Clock problems

2005-05-31 Thread Ludovic watteaux
Since i don't use the package udev for my 2.6 kernel, all works great on my 
debian amd64 system the rtc modules load great, the time see by hwclock is 
the same that in the bios.

That's not only  that udev cause don't work great the system : 
- my swap can't be umounted  correctly on the shutdown.
- ...

Ludovic


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Clock problems

2005-05-31 Thread Mike Reinehr
On Monday 30 May 2005 03:53 pm, John Baab wrote:
  apt-get install ntp ntpdate

 also fixed the problem, but I would rather not have the extra service
 if its not needed.

 -Thanks for all the help, John

John,

Ntpdate, unlike ntp or ntp-simple, is not a service, per se, but just a 
program that can be run manually, or periodically from a startup script or 
with cron. It just will keep your clock from drifting too far off the time, 
if you don't need the additional accuracy of ntp.

cmr
-- 
Debian 'Sarge': Registered Linux User #241964

More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Clock problems

2005-05-30 Thread Javier Kohen
El lun, 30-05-2005 a las 12:38 -0400, John Baab escribi:

 Every time I try to use hwclock I get this error:
 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
 No usable clock interface found.
 Cannot access the Hardware Clock via any known method.

Make sure the rtc module is loaded, or compiled in the kernel.

 Anyone have any ideas?  Odly enough if I change my clock preferences
 to use UTC then it displays the correct time.

Well, maybe it is indeed set to UTC.

-- 
Javier Kohen [EMAIL PROTECTED]
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part


Re: Clock problems

2005-05-30 Thread Kurt Roeckx
On Mon, May 30, 2005 at 12:38:59PM -0400, John Baab wrote:
 Every time I try to use hwclock I get this error:
 hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
 No usable clock interface found.
 Cannot access the Hardware Clock via any known method.

cd /dev; ./MAKEDEV rtc


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Clock problems

2005-05-30 Thread K. Gysin
I had a similar problem, hwclock failing with the stated message.

Adding rtc to /etc/modules solved it for me. I do not believe it is
necessary to manually add the device to /dev (at least it wasn't for
me).

You can check this by running modprobe rtc manually, and then trying
hwclock again.

Regards,

-kurt

Am Montag, den 30.05.2005, 19:05 +0200 schrieb Kurt Roeckx:
 On Mon, May 30, 2005 at 12:38:59PM -0400, John Baab wrote:
  Every time I try to use hwclock I get this error:
  hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
  No usable clock interface found.
  Cannot access the Hardware Clock via any known method.
 
 cd /dev; ./MAKEDEV rtc
 
 
 Kurt
 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Clock problems

2005-05-30 Thread Javier Kohen
El lun, 30-05-2005 a las 19:31 +0200, K. Gysin escribi:
 I had a similar problem, hwclock failing with the stated message.
 
 Adding rtc to /etc/modules solved it for me. I do not believe it is
 necessary to manually add the device to /dev (at least it wasn't for
 me).

Not if you're using udev, devfs or anything deprecated or not that
creates the devices for you. I guess that even if you don't use those,
the file should be there unless you removed it. In this case the file
doesn't exist, so a missing module is very likely to be the culprit.

 You can check this by running modprobe rtc manually, and then trying
 hwclock again.

That will probably work.

-- 
Javier Kohen [EMAIL PROTECTED]
ICQ: blashyrkh #2361802
Jabber: [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part


Re: Clock problems

2005-05-30 Thread John Baab
 Adding rtc to /etc/modules solved it for me. I do not believe it is
 necessary to manually add the device to /dev (at least it wasn't for
 me).
 
 You can check this by running modprobe rtc manually, and then trying
 hwclock again.

Worked for me, once hwclock was working I was able to fix my time
using date and hwclock and it remained after a reboot.

 apt-get install ntp ntpdate

also fixed the problem, but I would rather not have the extra service
if its not needed.

-Thanks for all the help, John