Gutsy hwclock now operates as expected with the Nvidia 6100 chipset.
--directisa no longer necessary.
I will change the status as fixed released.
** Changed in: linux-meta (Ubuntu)
Status: New => Fix Released
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad
Hello Robbie
On my Nvidia 6100 chipset, the --directisa switch seems to work.
#> hwclock --directisa --systohc
I'd say there is a bug somewhere given we need a --directisa switch. The
API to write and read the system clock should be consistent at the
software level irrespective of hardware. So a
I have the same problem. My system info is here:
Software
Ubuntu 7.04 32bit
Kernel 2.6.20-16-386
Hareware
Acer 5595i
I tried use CLOCKFLAGS="--directisa", invoke /sbin/hwclock command, suggested
by thread
http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-04/4968.h
Kernel version
uname -r
2.6.22-8-386
re-attached hwinfo.tar - Last one doesn't view easily in archive
manager.
** Attachment added: "hwinfo.tar"
http://launchpadlibrarian.net/8579603/hwinfo.tar
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
Y
I said:
This functions correctly with a fully updated Gutsy running on a VIA chipset,
which has interrupt 3 assigned
Please ignore that. First col 8 second col 3 on Via.
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
You received this bug notific
lspci -v
lshw
cat /proc/interruipts
cat /proc/ioports
dmesg
** Attachment added: "hwinfo.tar.gz"
http://launchpadlibrarian.net/8579113/hwinfo.tar.gz
--
Real time clock will not set with Nvidia 6100 chipset
https://bugs.launchpad.net/bugs/128616
You received this bug notification because you
