David Hollenberg wrote: > I installed RC2a and wanted to share my experiences. First, let me say that > this version is a *tremendous* improvement over preview 2. Really very > impressive. > > Hardware is Asus A8N-SLI Premium motherboard, 2 GB RAM, AMD Athlon 64 X2 > dual core 4200+ CPU. > > 1. I tried to burn the .iso image to a CD but it wouldn't fit. I used > "cdrw -i <iso_file>". Writer is a NEC-3550A CD/DVD writer. Output was: > > # cdrw -i 0805rc2a.iso: > Looking for CD devices... > Initializing device...done. > Size required (719120384 bytes) is greater than available space (681986048 > bytes > ). >
Either add the -C option to cdrw or cdrecord. > 2. The install seemed slower than in preview 2 but I didn't time it. It's going to be ~15% longer just because there's more stuff to copy. If it's much more than that, then we'd be interested in the log (it's /var/sadm/system/logs/install_log after installation). > But the map for timezone selection is nice. The installation went > smoothly. > Something I did during the install created a core file. Mdb showed the > stack trace to be: > > ::stack > 0xfa3df32c(84469b0) > libxpcom_core.so`__1cNnsCOMPtr_baseSassign_with_AddRef6MpnLnsISupports__v_+0x38( > 83e7710, 0) > libxpcom_core.so`__1cSfactory_ClearEntry6FpnMPLDHashTable_pnPPLDHashEntryHdr__v_ > +0x35(80f7bc8, 80f9e28) > libxpcom_core.so`PL_DHashTableFinish+0x5f(80f7bc8) > libxpcom_core.so`__1cWnsComponentManagerImplIShutdown6M_I_+0x8d(80f7ba0) > libxpcom_core.so`NS_ShutdownXPCOM_P+0x193(0) > libxpcom.so`NS_ShutdownXPCOM+0x1b(0) > libgtkembedmoz.so`NS_TermEmbedding+0x4d(80f0c88, 80b80a0, fa3df328, 8066d19, > 804 > 79e8, fa3beddc) > libgtkembedmoz.so`__1cMEmbedPrivateKPopStartup6F_v_+0xa7(80be458, 80479f8, > feffd > e48, 80479f8, 8066d19, c70) > libgtkembedmoz.so`gtk_moz_embed_pop_startup+0x18(c70, 806e5a4, 8047a0c, > 80675eb, > 0, 86bc670) > yelp_gecko_shutdown+0x29(0, 86bc670, feffde48, 8047aec, 806e5a9, 8047ba8) > yelp_html_shutdown+0xb(8047ba8, 8047ad4, feffb7cc, 8047a38, fefd36c9, > feffde48) > main+0x525(2, 8047b18, 8047b24) > _start+0x7a(2, 8047c10, 8047c1b, 0, 8047c4a, 8047c7e) > Which application generated the core? Please file a bug against it. > 3. When booting after install, it is quite difficult to tell which item is > highlighted in the GRUB menu, due to dark background color. > Bug 1534 > 4. After entering username and password at the login screen, the desktop > background remains black for awhile. During this time, I can hear the > floppy drive being accessed and the light for it is also on (there is > no floppy in the drive). After perhaps 20-30 seconds this stops and then > the desktop background appears. > > 5. After the desktop background appears, the top panel is still blank. > It stays blank for many minutes. Running prstat shows that gnome-panel is > using one whole CPU. Killing gnome-panel causes the top panel menu items > etc to appear as expected and then everything works fine. I ran truss > and attached it to the process and it looks like it is repeating the same > sequence of calls with a small number of files (mostly access, open64, > fstat64, read and close calls). I can provide a section of the truss > output if this is not a known issue and if it would be useful. > I'm suspicious of gamin on both of these. Dave _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
