On Tue, Dec 21, 2004 at 12:54:55PM +0100, Erik van Konijnenburg wrote:
> On Tue, Dec 21, 2004 at 09:32:19AM +0100, Geert Stappers wrote:
<snip/>
> > Okay, that is the easy part :-)
> >
> > Does the workaround allow reboot without "apci=off"
> > and without pressing Control-C ?
>
> That worked already, util-linux-2.12h has working timeout on rtc
> failures. In d-i rc2 the hang is gone, so the only motivation
> for the workaround would be to create a working hwclock.
> Just tested reboot: as expected the timeout error is gone now.
Yes, I confirm that workaround works fine. (including reboot)
The manual page of hwclock says:
--directisa
is meaningful only on an ISA machine or an Alpha (which imple-
ments enough of ISA to be, roughly speaking, an ISA machine for
hwclock's purposes). For other machines, it has no effect.
This option tells hwclock to use explicit I/O instructions to
access the Hardware Clock. Without this option, hwclock will
try to use the /dev/rtc device (which it assumes to be driven by
the rtc device driver). If it is unable to open the device (for
read), it will use the explicit I/O instructions anyway.
The rtc device driver was new in Linux Release 2.
So this bugreport, currently filed against kernel-source,
is IMNSHO not bug a kernel bug.
It is about "special" hardware that needs "special" treatment.
And the special treatment is provided by the hwclock programm.
Cheers
Geert Stappers
Erik: Dank je wel.
None Dutch: Thank you very much.
Attachment:
signature.asc
Description: Digital signature