For /dev/rtc issue try this.
http://forums.remote-exploit.org/bt4...tml#post121123
Maybe a bug: /dev/rtc
When I type "hwclock" I get the following at the commandline:
OK, so then I go and type "hwclock --debug", and I get:Code:Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method.
I'd like if a few more people could try this at the commandline to see whether this is something unique to my own machine, or whether it's an actual bug in BT4beta.Code:hwclock from util-linux-ng 2.14 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.
Ask questions on the open forums, that way everybody benefits from the solution, and everybody can be corrected when they make mistakes. Don't send me private messages asking questions that should be asked on the open forums, I won't respond. I decline all "Friend Requests".
For /dev/rtc issue try this.
http://forums.remote-exploit.org/bt4...tml#post121123
Magnificent, thanks a lot, works perfect now.
The solution's been added to my Beef Up program.
Ask questions on the open forums, that way everybody benefits from the solution, and everybody can be corrected when they make mistakes. Don't send me private messages asking questions that should be asked on the open forums, I won't respond. I decline all "Friend Requests".
Posting Permissions