**** BEGIN LOGGING AT Wed Oct 11 02:59:56 2006 Oct 11 07:14:04 hi to all Oct 11 07:14:58 anyone knows why, after i change my date setting on openslug 3.10, the system returns to "Thu Jan 1 01:08:34 CET 1970" at the next boot ?? Oct 11 07:32:01 anyone knows why, after i change my date setting on openslug 3.10, the system returns to "Thu Jan 1 01:08:34 CET 1970" at the next boot ?? Oct 11 08:23:32 anyone knows why, after i change my date setting on openslug 3.10, the system returns to "Thu Jan 1 01:08:34 CET 1970" at the next boot ?? Oct 11 08:24:16 hooney: it looks like your irc client is broken Oct 11 08:24:28 hooney: it keeps inserting the same line over and over again Oct 11 08:25:28 sorry, anyone know a solution for that problem ? Oct 11 11:19:54 anyone knows why, after i change my date setting on openslug 3.10, the system returns to "Thu Jan 1 01:08:34 CET 1970" at the next boot ?? Oct 11 14:16:57 2 Oct 11 14:17:06 3 Oct 11 14:18:55 oops, sorry, hit a key by accident or so Oct 11 14:39:27 anyone knows why, after i change my date setting on openslug 3.10, the system returns to "Thu Jan 1 01:08:34 CET 1970" at the next boot ?? Oct 11 14:44:21 hooney: you need to write the date back to the hw register Oct 11 14:44:28 sethwrtc or something like that Oct 11 14:45:59 is it in soma package ? Oct 11 14:46:04 is it in some package ? Oct 11 14:46:50 i think it is present always Oct 11 14:47:12 checking Oct 11 14:47:57 actually the program is called hwclock and resides in /sbin Oct 11 14:48:19 you need to invoke the prog with -w (try invoking without args to get the help msg) Oct 11 14:53:45 it tells me Oct 11 14:53:54 hwclock: Could not access RTC: No such file or directory Oct 11 14:57:01 anu idea ? Oct 11 14:57:05 any idea ? Oct 11 15:04:40 sorry didn't see your msg (window obscured) Oct 11 15:04:51 are you logged in as root. Only root can set the hw clock Oct 11 15:05:52 sure Oct 11 15:05:54 you might also check with hwclock what the actual clock setting is. If it is set, and after a reboot you still get jan 1 1970 then the clock is not read. Oct 11 15:05:54 i am root Oct 11 15:06:35 yeah, the RTC on my slug quit working for a while. Oct 11 15:06:35 even if i call hwclock -r to read actual time Oct 11 15:06:37 i get Oct 11 15:06:38 hwclock: Could not access RTC: No such file or directory Oct 11 15:06:45 I had to remove and replace the battery to get it to work again. Oct 11 15:06:45 if you are root and cannot set the clock it seems that /dev/rtc or so is missing. Can't help you with that on top of my head, and in a minute or so i need to go for dinner Oct 11 15:07:01 I don't have this problem anymore as I managed to burn both i2c pins! :( Oct 11 15:07:35 So I now live in the 70's permanently! :) Oct 11 15:07:35 yup, battery remove can be needed if the clock is stuck; battery replace can be needed if it is worn out (but it should last a vew hrs) Oct 11 15:07:35 so i can try remove and reset the internal battery ? Oct 11 15:07:51 VoodooZ_work: just set the clock from ntp Oct 11 15:07:54 nah. It' s a mobile robot so no point really. Oct 11 15:08:20 that would require network access which is not always available. Oct 11 15:08:21 Not a big deal really. Oct 11 15:08:28 there must be a way to set date/time on our slug! Oct 11 15:09:29 In my case I'll have to remove the RTC /dev/entry and other crap as It's broken and just taking up memory Oct 11 15:09:52 hooney, there appearsa to be a problem with your /dev/rtc or module. Oct 11 15:11:09 i think the problem i releted with newer updates of 3.10 kernel feeds Oct 11 15:11:23 as i remember that with a fresh 3.10 firmware Oct 11 15:11:36 i had no problems with clock setup.. Oct 11 17:25:06 NAiL, do any of the links I posted look useful to you though? (especially the second one with the .bb file) Oct 11 17:40:17 hi! I've got problems configuring upslug2. The error message is "configure.ac: 8: required file `./[config.h].in' not found" but the file is here. What am I missing? Oct 11 17:50:46 I need not to compile it, I've found an .deb file. so - ignore my prev. post Oct 11 18:03:29 ibert, this is not an upslug support channel. Try #nslu2-general Oct 11 18:07:45 joshin: sorry & thanks. I've already solved it. Oct 11 18:42:02 later **** ENDING LOGGING AT Thu Oct 12 02:59:56 2006