Sorry, I don't know enough about the Community Express editions. So I was 
blindly trying my best, and downloaded the 78-DVD, started the installer, found 
the installed Developer Edition, clicked 'Upgrade'. It went through almost to 
the end. There it said: (shown are all 'failed')
[i] 
...
Installation of <SUNWadmap> was successful.
Doing pkgadd of SUNWiiimr to /
pkgadd: ERROR: unable to open </cdrom/Solaris_11/Product/SUNWiiimr/reloc/etc/amd
64/gtk-2.0/gtk.immodules> for reading: (2) No such file or directory
pkgadd: ERROR: unable to open </cdrom/Solaris_11/Product/SUNWiiimr/reloc/etc/gtk
-2.0/gtk.immodules> for reading: (2) No such file or directory
474 blocks
Installation of <SUNWiiimr> partially failed.
pkgadd return code = 2
Doing pkgadd of SUNWiso-codes to /
1844 blocks
...
Doing pkgadd of SUNWxsvc to /
153 blocks
devfsadm: open failed for /etc/dev/.devfsadm_dev.lock: Read-only file system
Warning: Driver (xsvc) successfully added to system but failed to attach
...
stage1 written to partition 1 sector 0 (abs 594405)
stage2 written to partition 1, 260 sectors starting at 50 (abs 594455)
/sbin/bootadm update-menu -R /a -o /dev/rdsk/c0d0s0

The messages printed to the screen by this upgrade have been saved to:

        /a/var/sadm/system/logs/upgrade_log

After this system is rebooted, the upgrade log can be found in the file:

        /var/sadm/system/logs/upgrade_log


The following packages failed to install correctly


SUNWiiimr
Please examine the file:

        /a/var/sadm/system/data/upgrade_cleanup
It contains a list of actions that may need to be performed to complete
the upgrade.  After this system is rebooted, this file can be found at:

        /var/sadm/system/data/upgrade_cleanup

After performing cleanup actions, you must reboot the system.Creating ram disk f
or /a
updating /a/platform/i86pc/boot_archive...this may take a minute
updating /a/platform/i86pc/amd64/boot_archive...this may take a minute
        - Environment variables (/etc/default/init)
<EOF>
 [/i]

I have checked that file, but could not find any specifics (being an amateur in 
this business) what I was supposed to do.


Rebooted full faith.
At reboot, it brought the message
[i] elfexec WARNING: elfcore: core d.....iled  for process 462; address space 
is changing[/i]
but went through.

Finally, X could not be started:
[i]
X-server cannot be started on display:0 ...
/var/dt/Xerrors for details[/i]
In there, you'll find a lot of sessions. Here is the last one:
[i]
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: SunOS 5.11 snv_75 i86pc 
Current Operating System: SunOS solU 5.11 snv_78 i86pc
Build Date: 07 November 2007

Solaris ABI: 64-bit
SUNWxorg-server package version: 6.9.0.5.11.7800,REV=0.2007.11.07
SUNWxorg-graphics-ddx package version: 6.9.0.5.11.7800,REV=0.2007.11.07
SUNWxorg-mesa package version: 6.9.0.5.11.7800,REV=0.2007.11.07
        Before reporting problems, check http://sunsolve.sun.com/
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 21 08:48:05 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "type1" is no longer provided  - using "freetype" instead
(II) Module "bitstream" is no longer provided  - using "freetype" instead
(EE) No devices detected.

Fatal server error:
no screens found
XIO:  fatal IO error 146 (Connection refused) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

Fri Dec 21 08:48:05 2007
error (pid 663): Server for display :0 can't be started.
[/i]

Again, if this is not supposed to work, my excuses for taking your time.
On the other hand, if this shows some bugs, I will gladly furnish more info.

Uwe
 
 
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]

Reply via email to