f11 alpha install failure

[David L]

f11 alpha failed to install using the graphical installer.  I haven't
tried a text install.  I attempted a graphical hard drive install on
this system:

http://www.smolts.org/client/show/pub_f24c96f9-7884-4d14-a298-63a2847d0c0e

I've filed this bugzilla report:

https://bugzilla.redhat.com/show_bug.cgi?id=484276

The computer hung completely after a few anaconda screens
both times I tried it.  I heard the CPU fan which is usually an
indication of very high CPU loading on this computer.  I'm not
sure if the hang was related to the graphics problem or a separate
bug, but I suspect they were related.


                 David

[Leon Stringer]

David L wrote:
>  f11 alpha failed to install using the graphical installer.  I
> haven't
>  tried a text install.  I attempted a graphical hard drive install on
>  this system:
>  
>  http://www.smolts.org/client/show/pub_f24c96f9-7884-4d14-a298-63a2847d0c0e
>  
>  I've filed this bugzilla report:
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=484276
>   
Did you manage to install F10 on the same computer? I have a different 
Intel VGA controller (82845G/GL) and had a similar problem, Anaconda 
becoming corrupt during the early stages of installation eventually 
locking up:

https://bugzilla.redhat.com/show_bug.cgi?id=470371

That's why I'm stuck on F9...

[David L]

On Thu, Feb 5, 2009 at 1:09 PM, Leon Stringer  wrote:
>  David L wrote:
> >
> > f11 alpha failed to install using the graphical installer.  I haven't
> > tried a text install.  I attempted a graphical hard drive install on
> > this system:
> >
> > http://www.smolts.org/client/show/pub_f24c96f9-7884-4d14-a298-63a2847d0c0e
> >
> > I've filed this bugzilla report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=484276
> >
>
>  Did you manage to install F10 on the same computer? I have a different Intel
>  VGA controller (82845G/GL) and had a similar problem, Anaconda becoming
>  corrupt during the early stages of installation eventually locking up:
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=470371
>
>  That's why I'm stuck on F9... 
I did get f10 installed with some difficulty.  I can't remember
the details, but I remember it was a challenge.  And there
was some screen corruption after I did manage to get it
installed.  The screen corruption got a little better after
trying the recommendation in comment #9 of this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=471537

But last week, my old CRT monitor died and I replaced
it with a new flat panel.  After that, the screen corruption
came back.  That's why I was trying f11 to see if it would
be any better.  So far, it's not looking good.  Each release
since f6, the i810 driver has been worse for me.  :(

Good luck,

           David

[Felix Miata]

On 2009/02/05 13:18 (GMT-0800) David L composed:

>  But last week, my old CRT monitor died and I replaced
>  it with a new flat panel.  After that, the screen corruption
>  came back.  That's why I was trying f11 to see if it would
>  be any better.  So far, it's not looking good.  Each release
>  since f6, the i810 driver has been worse for me.  :( 
i810 became an alias for intel, I think over a year ago now. 845, 855 & 945
chips seem to be the most troublesome for the recent intel drivers.
-- 
"Do not let any unwholesome talk come out of your
mouths, but only what is helpful for building
others up."			Ephesians 4:29 NIV

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

[David L]

On Thu, Feb 5, 2009 at 1:36 PM, Felix Miata wrote:
>  On 2009/02/05 13:18 (GMT-0800) David L composed:
>
> > But last week, my old CRT monitor died and I replaced
> > it with a new flat panel.  After that, the screen corruption
> > came back.  That's why I was trying f11 to see if it would
> > be any better.  So far, it's not looking good.  Each release
> > since f6, the i810 driver has been worse for me.  :(
>
>  i810 became an alias for intel, I think over a year ago now. 845, 855 & 945
>  chips seem to be the most troublesome for the recent intel drivers. 
I have this chipset:

(II) intel(0): Integrated Graphics Chipset: Intel(R) 865G
(--) intel(0): Chipset: "865G"

and it has also been quite troublesome.

I've successfully done a text mode installation, but the system hung
after startx.  I got a bug buddy window with some corruption (I don't
know what crashed) after X started and then nothing for several minutes.
The mouse moved a corrupt little fedora wait icon around the screen,
but there were no other signs of life.  I didn't check if I could ping or
ssh into it.  I couldn't ctrl-alt-del to reboot and ctrl-alt-backspace didn't
work (although I think I saw in the release notes that it doesn't do
anything by default anymore).  In the end, I power cycled and booted
back to the f10 partition (where there is still X corruption but no
hangs).  I'm pretty sure the f11 hangs are graphics driver related.

                  David

[Bob Arendt]

David L wrote:
>  On Thu, Feb 5, 2009 at 1:36 PM, Felix Miata wrote:
> > On 2009/02/05 13:18 (GMT-0800) David L composed:
> >
> >> But last week, my old CRT monitor died and I replaced
> >> it with a new flat panel.  After that, the screen corruption
> >> came back.  That's why I was trying f11 to see if it would
> >> be any better.  So far, it's not looking good.  Each release
> >> since f6, the i810 driver has been worse for me.  :(
> > i810 became an alias for intel, I think over a year ago now. 845, 855 & 945
> > chips seem to be the most troublesome for the recent intel drivers.
>  
>  I have this chipset:
>  
>  (II) intel(0): Integrated Graphics Chipset: Intel(R) 865G
>  (--) intel(0): Chipset: "865G"
>  
>  and it has also been quite troublesome.
>  
>  I've successfully done a text mode installation, but the system hung
>  after startx.  I got a bug buddy window with some corruption (I don't
>  know what crashed) after X started and then nothing for several minutes.
>  The mouse moved a corrupt little fedora wait icon around the screen,
>  but there were no other signs of life.  I didn't check if I could ping or
>  ssh into it.  I couldn't ctrl-alt-del to reboot and ctrl-alt-backspace didn't
>  work (although I think I saw in the release notes that it doesn't do
>  anything by default anymore).  In the end, I power cycled and booted
>  back to the f10 partition (where there is still X corruption but no
>  hangs).  I'm pretty sure the f11 hangs are graphics driver related.
>  
>                    David
>   
Yep - Still struggling with 845G myself  , Bugzilla 469292
You might try copying the xorg.conf file from your F10 install.
If that doesn't work, try adding
   Option "NoAccel" "True"
to the driver section.  Xorg may have hung and taken the keyboard
with it (Test: does the CapsLock light work when you toggle CapsLock?)
-Bob

[David L]

On Thu, Feb 5, 2009 at 2:57 PM, Robert Arendt <rda(a)rincon.com&gt; wrote:
>  David L wrote: 
<snip>
> > I have this chipset:
> >
> > (II) intel(0): Integrated Graphics Chipset: Intel(R) 865G
> > (--) intel(0): Chipset: "865G"
> >
> > and it has also been quite troublesome.
> >
> > I've successfully done a text mode installation, but the system hung
> > after startx.  I got a bug buddy window with some corruption (I don't
> > know what crashed) after X started and then nothing for several minutes.
> > The mouse moved a corrupt little fedora wait icon around the screen,
> > but there were no other signs of life.  I didn't check if I could ping or
> > ssh into it.  I couldn't ctrl-alt-del to reboot and ctrl-alt-backspace
> > didn't
> > work (although I think I saw in the release notes that it doesn't do
> > anything by default anymore).  In the end, I power cycled and booted
> > back to the f10 partition (where there is still X corruption but no
> > hangs).  I'm pretty sure the f11 hangs are graphics driver related.
> >
> >                  David
> >
>  Yep - Still struggling with 845G myself  , Bugzilla 469292
>  You might try copying the xorg.conf file from your F10 install.
>  If that doesn't work, try adding
>   Option "NoAccel" "True" 
Thanks for the tip... I'll try
that.  Right now, I'm happily running
X with the vesa driver in place of the intel driver.

>  to the driver section.  Xorg may have hung and taken the keyboard
>  with it (Test: does the CapsLock light work when you toggle CapsLock?) 
I'm
pretty sure the caps lock was dead when it was in that state.

                     David

[Michal Jaegermann]

On Thu, Feb 05, 2009 at 02:30:43PM -0800, David L wrote:
>  On Thu, Feb 5, 2009 at 1:36 PM, Felix Miata wrote:
>  > On 2009/02/05 13:18 (GMT-0800) David L composed:
>  >
>  >> But last week, my old CRT monitor died and I replaced
>  >> it with a new flat panel.  After that, the screen corruption
>  >> came back.  That's why I was trying f11 to see if it would
>  >> be any better.  So far, it's not looking good.  Each release
>  >> since f6, the i810 driver has been worse for me.  :(
>  >
>  > i810 became an alias for intel, I think over a year ago now. 845, 855 & 945
>  > chips seem to be the most troublesome for the recent intel drivers.
>  
>  I have this chipset:
>  
>  (II) intel(0): Integrated Graphics Chipset: Intel(R) 865G
>  (--) intel(0): Chipset: "865G"
>  
>  and it has also been quite troublesome. 
That most likely will be this:
https://bugzilla.redhat.com/show_bug.cgi?id=469292
As there is no real way to pass X server configuration to anaconda
you have to do installation/upgrades in a text mode.  Once done
making up xorg.conf with "NoAccel" set will get you graphics if not
the greatest ones.  I do have a laptop where this was necessary and
it works.

Some machines may also require such treatment:
https://bugzilla.redhat.com/show_bug.cgi?id=476609
This time passing to anaconda 'clocksource=jiffies' is easy.
If your clock is going crazy and/or multiple strokes are required
before a key is recognized then you have a "candidate" on hands.

   Michal