Another FC3test2 candidate tree

[Phil Schaffner]

On Thu, 2004-09-09 at 01:23 -0400, Charles R. Anderson wrote: 
> On Wed, Sep 08, 2004 at 10:08:11PM -0400, Elliot Lee wrote:
> > The previous bug reports on the re0903.0 tree were very helpful - 
> > here's another one to chew on:
> > http://fedora.linux.duke.edu/FC3-re0908.0/
> 
> I tried a fresh install on an IBM ThinkPad T42p with the 1600x1200 15"
> LCD and 128MB ATI FireGL Mobility T2 graphics card.
>
> Install went better this time around.  Graphical installer worked.  I
> did a Custom install from CD's, Manual partition, formatting all
> system partitions from my previous install.

Fresh install on ThinkPad A21p (1600x1200 with ATI Technologies Inc Rage
Mobility M3 AGP 2x) at least started graphical install, unlike
candidate-1, but then froze during openoffice.org-i18n installation as
in BZ #124221 from FC2.

Text-mode install completed, also custom install from CD's, manual
partition, re-formatted existing partitions except M$ WinXP; however,
eth0 problem (BZ #131293, thread "FC3T2 candidate") is still present.
Not a surprise as it is still kernel 541 - but one can always hope.

> A few points:
> 
> 1. In rc0903, bootup hung on firstboot.  Ctrl-Alt-Backspace was needed
> to continue bootup, skipping firstboot.  Now in rc0908, bootup
> continues right past firstboot.  I assume firstboot failed to run, but
> at least it didn't hang this time.  The rhgb graphics displayed,
> followed by what looked like the X server reinitializing and the
> screen clearing to black.  Then the X server was reinitialized again,
> and GDM appeared.  /var/log/boot.log says: "firstboot: failed".

Similar behavior here - no firstboot.

> 2. Possibly due to the above, switching from graphical login on VT7 to
> the text consoles on VT1-VT6 displayed blank text screens with a
> blinking cursor.  The cursor moved with keyboard input.  Mingetty was
> actually running, so I was able to login blind.  After logging in as
> root, the text screen was "reset" somehow (by an /etc/profile
> script?), and all the previous and current text appeared...

Something strange about the graphics as the text mode on the VCs is now
gray-on-black rather than white-on-black, but did work after 1st login.

> 3. dmesg says "kernel: radeonfb: Non-DDC laptop panel detected", but
> then says "kernel: radeonfb: detected LVDS panel size from BIOS:
> 1600x1200".  However, xorg-x11 always starts in 800x600.  Perhaps
> firstboot would offer the correct default resolution of 1600x1200 if
> it had worked?  This is easily remedied by using System
> Settings->Display after logging in, changing Monitor Type from
> "Unknown monitor" to "Generic LCD Display / LCD Panel 1600x1200", and
> selecting Resolution: 1600x1200, and re-logging in.

Tried this approach, set display type and resolution, but logout never
completed and attempt to change to a text console resulted in a slow
fade to a white screen - again like BZ #124221.

> 4. Double-clicking the battery applet gives an error dialog:
>         "The Suspend command '/usr/bin/apm -s' was unsuccessful."
> 
> 5. I see xcdroast was replaced by k3b in the menu.  This is good,
> because re0903's xcdroast didn't work (it spewed some error about
> /dev/sg* not found).  I also found xcdroast hard to use (this was my
> first time seeing it).
> 
> However, why is k3b in "Sound & Video" and not "System Tools" or
> perhaps "Accessories"?  It seems silly that k3b would be considered
> solely a Sound or Video application...  Once I found k3b, I was
> impressed with its ease of use and proper functioning.  I erased a
> CD-RW and burned an ISO image with no trouble or configuration
> required.
> 
> Good work so far--FC3 is going to be an exciting release.  I'll
> find/file bugs for these issues soon...

Pretty much a show-stopper for me.  No network, flaky graphics.  Don't
see anything new that's not been Bugzilla'd already.

That's life in the fast lane.  Going back to FC3T1 (or FC2, or maybe
this is a good time to try WhiteBox on this box) to get the system
working again for now.

Phil