Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
Carl: I set the date in the BIOS directly, now all that stuff, appartenly icluding mktime, all seem to WORK! Many thanks! David On 10 Feb 2000, Carl Johnson wrote: > David Teague <[EMAIL PROTECTED]> writes: > > > Kevin and Nate: > > > > Thanks for the suggestions. I'll live with the problem > > until I can find time to upgrade to Potato, rather than > > mess with fixing dependencies or looking for a board. > > > > Upgrading is easy enough, I just did it 2 weeks ago on > > my main machines. Besides, I have all my data backed up on > > tape, so even if I wind up needing to wipeand reistall, > > I'll be OK. > > > > Meanwhile, I'll look for the RTC board that Nate mentioned > > in his message. I need a couple of them at least, as I have > > 4 machines that have this problem. > > > > Again thanks, this is why I choose Debian- the help is > > quick, freely given and almost _always_ works. > > Just in case... Have you tried re-booting and manually setting the > year from the BIOS menu? I had the same problem on an old portable > computer and it worked for me. > > -- > Carl Johnson [EMAIL PROTECTED] > --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)
Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
Kevin and Nate: Thanks for the suggestions. I'll live with the problem until I can find time to upgrade to Potato, rather than mess with fixing dependencies or looking for a board. Upgrading is easy enough, I just did it 2 weeks ago on my main machines. Besides, I have all my data backed up on tape, so even if I wind up needing to wipeand reistall, I'll be OK. Meanwhile, I'll look for the RTC board that Nate mentioned in his message. I need a couple of them at least, as I have 4 machines that have this problem. Again thanks, this is why I choose Debian- the help is quick, freely given and almost _always_ works. --David On Thu, 10 Feb 2000, Kevin A. Foss wrote: > On Wed, Feb 09, 2000 at 01:54:59PM -0500, David Teague wrote: > > > > The machine is quite old, still has an ISA bus, circa 1993, running > > Linux 2.0. Ihe hwclock version is ... lesseee > > > > # hwclock --show > > mktime() failed unexpectedly (rc -1). Aborting. > > # hwclock --version > > hwclock 2.1/util-linux 2.6 > > > > OK? This didn't occur before the millenium, and may be similar to > > your situation. I HOPE you know a fix. If now, I will put another > > MB in it. > > Yeah, this is a rather old version of hwclock, the version in potato is > 2.4/2.10 I think. The easiest thing would be to get a newer > util-linux, or if that would require a lot of dependencies for you, > download the source and just compile a newer hwclock for yourself. > > It may have got messed up on 1/1/2000 because somehow the century > byte got changed in an unexpected fashion when it changed. > > -Kevin > -- > Kevin A. Foss [EMAIL PROTECTED] > --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)
Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
On Wed, Feb 09, 2000 at 01:54:59PM -0500, David Teague wrote: > > The machine is quite old, still has an ISA bus, circa 1993, running > Linux 2.0. Ihe hwclock version is ... lesseee > > # hwclock --show > mktime() failed unexpectedly (rc -1). Aborting. > # hwclock --version > hwclock 2.1/util-linux 2.6 > > OK? This didn't occur before the millenium, and may be similar to > your situation. I HOPE you know a fix. If now, I will put another > MB in it. Yeah, this is a rather old version of hwclock, the version in potato is 2.4/2.10 I think. The easiest thing would be to get a newer util-linux, or if that would require a lot of dependencies for you, download the source and just compile a newer hwclock for yourself. It may have got messed up on 1/1/2000 because somehow the century byte got changed in an unexpected fashion when it changed. -Kevin -- Kevin A. Foss [EMAIL PROTECTED]
Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
On Wed, 9 Feb 2000, David Teague wrote: dbt ># hwclock --show dbt >mktime() failed unexpectedly (rc -1). Aborting. dbt ># hwclock --version dbt >hwclock 2.1/util-linux 2.6 dbt > dbt >OK? This didn't occur before the millenium, and may be similar to dbt >your situation. I HOPE you know a fix. If now, I will put another there are those RTC expansion cards(typically ISA based) you may wanna try one of those they are cheap..never tried em myself, but it may be easier then finding a replacement MB for a machine that old! :/ nate [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 12:58pm up 174 days, 1:12, 1 user, load average: 1.08, 1.03, 1.01
Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
On Fri, 4 Feb 2000, Kevin A. Foss wrote: > On Fri, Feb 04, 2000 at 02:14:24PM -0500, David Teague wrote: > > > > My system is an OLD (circa 1990) 486/66 with ISA motherboard and > > 64K Cache, 32 MB RAM, and 4 Gig IDE disk. > [...] > > gandalf# /sbin/hwclock -w > > mktime() failed unexpectedly (rc -1). Aborting. > > You didn't mention the version of hwclock/util-linux you were using, > but older (slink-era) versions will fail on some CMOS because of where > the century byte is stored. I know I used to get exactly this error > when I first tried to get hwclock to work on a PS/2, for example. Hi Kevin The machine is quite old, still has an ISA bus, circa 1993, running Linux 2.0. Ihe hwclock version is ... lesseee # hwclock --show mktime() failed unexpectedly (rc -1). Aborting. # hwclock --version hwclock 2.1/util-linux 2.6 OK? This didn't occur before the millenium, and may be similar to your situation. I HOPE you know a fix. If now, I will put another MB in it. --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)
Re: Why? mktime() failed unexpectedly (rc -1). Aborting.
On Fri, Feb 04, 2000 at 02:14:24PM -0500, David Teague wrote: > Hi > > My system is an OLD (circa 1990) 486/66 with ISA motherboard and > 64K Cache, 32 MB RAM, and 4 Gig IDE disk. [...] > gandalf# /sbin/hwclock -w > mktime() failed unexpectedly (rc -1). Aborting. You didn't mention the version of hwclock/util-linux you were using, but older (slink-era) versions will fail on some CMOS because of where the century byte is stored. I know I used to get exactly this error when I first tried to get hwclock to work on a PS/2, for example. -Kevin -- Kevin A. Foss [EMAIL PROTECTED]
Why? mktime() failed unexpectedly (rc -1). Aborting.
Hi My system is an OLD (circa 1990) 486/66 with ISA motherboard and 64K Cache, 32 MB RAM, and 4 Gig IDE disk. When I try to set the hardware clock, I get the error message indicated in the subject line. The entire exchange that brought this to mind is: gandalf# /usr/sbin/netdate time_a.timefreq.bldrdoc.gov time_a.timefreq.bldrdoc.gov -0.801 Fri Feb 4 14:01:28.000 gandalf# /sbin/hwclock -w mktime() failed unexpectedly (rc -1). Aborting. Can someone advise what is causing mktime() to fail? What I can do to fix this? I hate not being able to automate the setting of the hardware clock. CMOS seems to remember the setting and so doesn't give me grief aobut rebooting. --David David Teague, [EMAIL PROTECTED] Debian GNU/Linux Because software support is free, timely, useful, technically accurate, and friendly. (I'm hoping this is all of the above!)