You need to care about the _actual_ error, not the report there is an
error. The error is (usually) reported to the console. Reboot the
computer and type this:
dmesg -c > /dev/null
modprobe ztdummy
dmesg
The output of the second dmesg will show you exactly what the error
message is.
Being that you have 'hpet' enabled, it's going to be 'Input/Output
error'. There's code in the kernel rtc driver that doesn't let you use
it if hpet is on:
--snippy--
int rtc_register(rtc_task_t *task)
{
#ifndef RTC_IRQ
return -EIO;
#else
if (task == NULL || task->func == NULL)
return -EINVAL;
--snippy--
[From your kernel config]
> >>CONFIG_HPET_RTC_IRQ=y
So. Turn that off, and recompile the rtc module and it'll start working
--Rob
_______________________________________________
--Bandwidth and Colocation sponsored by Easynews.com --
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
