2001-02-12 00:28:13

by Jan Niehusmann

[permalink] [raw]
Subject: /dev/rtc not working on ASUS A7V133

If my ASUS A7V133-based computer got started by the bios automatic
startup timer, /dev/rtc doesn't work properly. /proc/drivers/rtc
shows sane values, but IRQ 8 is not triggered causing programms like
'hwclock' to hang.

I assume this is not a kernel bug but a BIOS problem, but it would be
nice if a kernel workaround was possible. Does anybody have an
idea what I could try to reenable the interrupts?

Jan


2001-02-12 01:15:56

by Guest section DW

[permalink] [raw]
Subject: Re: /dev/rtc not working on ASUS A7V133

On Mon, Feb 12, 2001 at 01:27:55AM +0100, Jan Niehusmann wrote:

> If my ASUS A7V133-based computer got started by the bios automatic
> startup timer, /dev/rtc doesn't work properly. /proc/drivers/rtc
> shows sane values, but IRQ 8 is not triggered causing programms like
> 'hwclock' to hang.
>
> I assume this is not a kernel bug but a BIOS problem, but it would be
> nice if a kernel workaround was possible. Does anybody have an
> idea what I could try to reenable the interrupts?

I suppose you could give hwclock --directisa ?

2001-02-12 09:03:33

by Jan Niehusmann

[permalink] [raw]
Subject: Re: /dev/rtc not working on ASUS A7V133

On Mon, Feb 12, 2001 at 02:15:32AM +0100, Guest section DW wrote:
> I suppose you could give hwclock --directisa ?

I didn't try --directisa, but I did remove /dev/rtc, which, according
to hwclock's manpage should have the same effect.

Afterwards hwclock does work well.

But I have a correction: The problem does not only occurr if the system
was started automatically by the bios, a manual 'soft off/soft on' sequence
shows the same effect. Only 'hard off/hard on' (using the switch directly
on the power supply) seems to work every time.

Jan

2001-02-14 10:13:52

by Paul Gortmaker

[permalink] [raw]
Subject: Re: /dev/rtc not working on ASUS A7V133

Jan Niehusmann wrote:

> But I have a correction: The problem does not only occurr if the system
> was started automatically by the bios, a manual 'soft off/soft on' sequence
> shows the same effect. Only 'hard off/hard on' (using the switch directly
> on the power supply) seems to work every time.

Can you run the following program when things are working and then when
they are not - i.e.

cmosdump > b4
# soft off / on
cmosdump > after
diff -u b4 after

The low registers (0, & 2 IIRC) are for sec and min, so expect changes
there - but of interest will be any changes in reg 0x0a and 0x0b.

Paul.

/*
*
* A quick hack to dump the CMOS RAM values from 0x0 to 0x7f. Note that
* some CMOS are only 0x40 in size, so edit accordingly. Released to
* the public under the terms and conditions of the Gnu General Public
* License (GPL) included herein by reference.
*
* Compile with:
* gcc -s -N -Wall -O cmosdump.c -o cmosdump
*
* Paul Gortmaker 07/95
*/

#define CMOS_SIZE 0x80

#include <stdio.h>
#include <asm/io.h>
#include <unistd.h>
#include <errno.h>

/*
* <linux/rtc.h> was <linux/mc146818rtc.h> on kernels prior to 2.2.19, so
* just define CMOS_READ/WRITE here independently and avoid the hassle.
*/

#define RTC_PORT(x) (0x70 + (x))
#define CMOS_READ(addr) ({ \
outb_p((addr),RTC_PORT(0)); \
inb_p(RTC_PORT(1)); \
})
#define CMOS_WRITE(val, addr) ({ \
outb_p((addr),RTC_PORT(0)); \
outb_p((val),RTC_PORT(1)); \
})


void binprint (unsigned short value);

void main(void) {

unsigned short addr, val;

val= iopl(3);
if (val) {
perror("iopl");
exit(errno);
}

printf("Addr:\tHex\tDec.\tBinary\n");

for (addr = 0; addr < CMOS_SIZE; addr++) {
val = CMOS_READ(addr);
printf("0x%X:\t0x%X\t%d\t",addr, val, val);
binprint(val);
printf("\n");
}

iopl(0);

} /*end*/

void binprint(unsigned short value) {

int bit;

for (bit=128;bit>0;bit/=2)
printf("%s", (value & bit) ? "1" : "0");

} /* end binprint */



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com