Slava Bizyayev wrote:
>I use kernel-2.6.10-1.770_FC3 on my HP OmniBook XE2 pretty happily.
>After updating kernel to kernel-2.6.11-1.14_FC3 I experience a strange
>behavior -- in the end of the boot (instead of X-login screen) machine
>freezes, and I cannot even get the terminal access with ctrl-alt-F1. Has
>someone experienced something similar? What's the work around?
On Tue, 2005-04-19 at 18:25, Yuandan Zhang wrote:
THANKS to John DeDourek.
Look at following post by John. It offers me a quick fix. try to stop
the default boot. Prior to boot, edit the boot command option, remove
rhgb from the boot command line. It will boot without the graphic boot
window. After started, edit grub.conf file, remove rhgb option.
Good luck,
Yuandan
[clip...]
The rhgb thing was introduced to show a "prettier" view while booting,
Apparently the rhgb provides the pretty image by firing up an X
server
early in the boot
process, or in any case switching to graphical mode on the display
adapter. However,
the "full desktop" can't be introduced that early in the boot process.
If using the default
login style (known as run level 5) then at some point the "early X
server" must be shut
down and the "real X server" fired up during the boot process. Prior to
FC3, it was
done in the order just stated, i.e. stop X, start X. Unfortunately,
this leaves a fraction
of a second where the display has gone from graphical mode to text mode
and then
back to graphical mode, causing an annoying flicker in the screen.
Apparently, starting with FC3 (or some update of it), the order was
reversed. The
"early X server" is started on one "virtual console". Then later in
the
boot process,
the "real X server" is started on another "virtual console". Then
the
screen is switched
from the early to the late console; this results in very little flicker
because both of these
consoles are in graphical mode. Then the "early X server" is stopped.
This, unfortunately results in a brief period when two graphical mode X
servers are
running in parallel on separate virtual consoles. Apparently this is no
problem for
some video card drivers. On the other hand, some programmers of video card
drivers never considered that the driver might be called on to maintain
two virtual
consoles simultaneously.
This sounds very realistic for me. So, I just edited /etc/sysconfig/init
commenting 'GRPHICAL=yes' line, and this did the trick -- I have no
problem since then.
Thanks to everyone,
--
Slava
--
http://www.dynagzip.com/
+44(0)208-923-5913 AIM: SlavaBizyayev
+44(0)794-766-4131 - mobile
slava(a)cpan.org
http://www.lastmileisp.com/