Re: 5000e & APM: system time wrong after suspend+resume
- Have you tried putting a VGA=794 line in /etc/lilo.conf? Works on my
1400x1050 5000e, but apparently doesn't work for everyone.
Suspend/resume now work normally for me.
--- In linux-dell-laptops@y..., klogv@y... wrote:
> > there is your problem [Dell BIOS], as soon as I got
> > the tux-top bios on my system that problem also vanished.
> Thanks Michael! Yet another reason to flash in the new bios. I
> kind of waiting around for the blessing from Dell...
> By the way, with the tuxtops bios, do you still get screen-meltdown
> you suspend & resume while in X? Or do you have to switch to a
> virtual console before suspending?
- throop@... writes:
> Have you tried putting a VGA=794 line in /etc/lilo.conf? Works on myIs the magic number still 794 if you have UXGA 1600x1200?
> 1400x1050 5000e, but apparently doesn't work for everyone.
> Suspend/resume now work normally for me.
- I also found with my I4000 that the time was wrong after coming out of
a suspend. I think there are two ways to fix this. One is, as
mentioned below, to switch over to UTC for your hardware clock. The
only potential problem with this is that if you dual boot, your
Windows installation may not know how to handle this. The other
possiblility, which is what I did, was to change the kernel
configuration option, "RTC stores time in GMT" to off (part of the APM
configuration). This was set on by default in my RedHat 6.2
configuration. This solved the problem for me. However, it does
require that you generate a new kernel and install it.
--- In linux-dell-laptops@y..., throop@c... wrote:
> I found that on my system, the hardware clock and the system clock
> were not being properly sync'd to each other after a resume. It had
> something to do with time zone issues.
> To solve it, I switched everything to UTC rather than local time.
> Change the UTC="no" entry to "yes" in /etc/sysconfig/clock file and
> see if that does it for you. I believe that you also need to set
> clock in the BIOS (at startup) to UTC.
> Good luck,
> > My 5000e system time becomes incorrect after a suspend and a
> > The OS acts as though no time has passed between the suspend and
> > resume, even if hours have in fact passed. (As if the OS doesn't
> > bother to reset the software time using the hardware clock when
> > resuming.)