Xun Ni:
I was away and just got back.
You can use DC to include driver/storage/scu in the dc_text_sparc.xml
and dc_text_x86.xml
i.e:
You need to add it to here:
<software_data action="install">
<name>pkg:/entire@latest</name>
<name>pkg:/group/system/solaris-large-server</name>
<name>pkg:/system/install/text-install</name>
<name>pkg:/driver/storage/lsc</name>
<name>pkg:/system/install/media/internal</name>
</software_data>
On 03/31/12 12:05 AM, xunni wrote:
Hi, Mary:
currently we have a new driver 'lsc' driver/storage/lsc, it
doesn't exist in the 'server_install' group. but we want to test the
installation. is there any way to use the TI to create the DVD to
perform the test?
Thanks,
Xun
Xun Ni:
If you look at http://ipkg.us.oracle.com and seach for
driver/storage/scu, it is in:
auto_install
slim_install
server_install
redistributable
So AI should work.
http://ipkg.us.oracle.com/solaris11/dev/en/search.shtml?token=driver%2Fstorage%2Fscu+&action=Search
On 05/25/11 08:09 PM, xun.ni wrote:
root@solaris:~# pkg info scu
Name: driver/storage/scu
Summary: Intel SCU SAS/SATA HBA driver
Description: Intel Storage Controller Unit (SCU) SAS/SATA HBA Driver
Category: Drivers/Storage
State: Installed
Publisher: on-nightly
Version: 0.5.11
Build Release: 5.11
Branch: 0.166
Packaging Date: Wed May 25 06:13:57 2011
Size: 884.76 kB
FMRI:
pkg://on-nightly/driver/storage/[email protected],5.11-0.166:20110525T061357Z
is this command? but i still can't find which group pkgs
On 05/26/11 11:02, Mary Ding wrote:
Xun Ni:
You can bring up the pkg repo and search to see where scu is in.
On 05/25/11 07:58 PM, xun.ni wrote:
is there a way to see which group packages my driver in? my
driver name is scu
Thanks,
Xun
On 05/26/11 10:20, Mary Ding wrote:
Xun ni:
I had included Karen on this and she is more famillar with DC.
If this is with TI, is your driver included in the server_install
group packages. If it does, then the install should work.
You can easily confirm this by booting the TI image and check it
out.
On 05/25/11 07:13 PM, xun.ni wrote:
Hi, Marry:
Thanks for your help, I need another confirm that if i have a
new controller, and an old driver already in s11
but the driver don't support installation on the controller.
After we modify the code , it supports the installation,
And i use the DC to modify the publisher to my workspace, build
an ISO, is this ISO support the installation.
You know that if the driver support installation, the driver
should be updated in both the repo and the ramdisk(miniroot),
does the DC update both the repo and the ramdisk(miniroot)?
Thanks,
Xun
On 05/19/11 02:25, Mary Ding wrote:
Xun Ni:
You cannot use a dc xml to do AI install.
If you want to test your binaries, I will suggest you do a TI
build. You make a copy of the dc_text_x86.xml, modify the repo
just like you did for the AI build. Remove the entire and do
the TI build.
Then you can boot the iso or usb and test TI install and it is
easier to test your bits.
On 05/18/11 04:30 AM, xun.ni wrote:
Hi, Marry
is it ok to remove the entire? I build the ISO successfully.
I create the DVD and boot from dvd, choose the custom boot
menu, but it seems that the installation failed due to can't
find manifest?
should i choose the custom menu, other menu seems ok but i
am not sure, the following is the log:
===============================================
Hostname: solaris3, 2011, Oracle and/or its affiliates. All
rights reserved.
Remounting root read/write
Probing for device nodes ...
Preparing image for use
Done mounting image
Configuring devices.
WARNING: No randomness provider enabled for /dev/random. Use
cryptoadm(1M) to enable a provider.
Enter the URL for the AI manifest [HTTP, default]:
Obtaining manifest from the following location:
/net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml
/net/coloraxe.cn.oracle.com/builds/xunni/dc_ai_x86.xml: Scheme
missing.
solaris console login:
Automated Installation started
The progress of the Automated Installation can be followed by
viewing
the logfile at /tmp/install_log
solaris console login: Invalid or incompatible manifest provided
Please refer to the
/var/svc/log/application-auto-installer:default.log file for
details
Mar 8 23:33:21 solaris svc.startd[8]:
application/auto-installer:default failed fatally:
transitioned to maintenance (see 'svcs -xv' for details)
root@solaris:~# cat
/var/svc/log/application-auto-installer:default.log
[ Mar 8 23:33:15 Executing start method
("/lib/svc/method/auto-installer"). ]
Automated Installation started
The progress of the Automated Installation can be followed by
viewing
the logfile at /tmp/install_log
Error instantiating manifest tree:
Error creating in-memory copy of Manifest data.
Error parsing xml file /tmp/ai.xml
Invalid or incompatible manifest provided
Please refer to the
/var/svc/log/application-auto-installer:default.log file for
details
[ Mar 8 23:33:21 Method "start" exited with status 95. ]
Thanks,
Xun
On 05/18/11 11:27, Mary Ding wrote:
This will not work:
1. You will need to add the on-extra nightly before solaris
<publisher name="on-nightly">
<origin name="file:///root/nightly/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
</publisher>
2. You will need to remove entire from the xml in order for
the build to work.
On 05/17/11 08:24 PM, xun.ni wrote:
Hi, Marry:
I set my repo before the 'solaris' publisher, see
<publisher name="on-nightly">
<origin name="file:///root/nightly/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
</publisher>
but the log show failed:
10:59:46 No matching version of entire can be installed:
Reject:
pkg://solaris/[email protected],5.11-0.151:20101027T142141Z
Reason: All versions matching 'require' dependency
pkg:/consolidation/osnet/osnet-incorporation are rejected
Reject:
pkg://on-nightly/consolidation/osnet/[email protected],5.11-0.166:20110517T104016Z
Reason: Excluded by proposed incorporation 'entire'
Reject:
pkg://solaris/consolidation/osnet/[email protected],5.11-0.151:20101026T180317Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.151.0.1:20101104T230646Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.152:20101112T165745Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.153:20101118T212652Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.154:20101203T190550Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.155:20101220T213006Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.156:20101230T214548Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.157:20110114T201511Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.158:20110127T191809Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.159:20110214T040231Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.160:20110226T064127Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.161:20110315T051502Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.162:20110325T170554Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.163:20110410T031009Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.164:20110422T153115Z
pkg://solaris/consolidation/osnet/[email protected],5.11-0.165:20110510T013316Z
On 05/18/11 05:11, Mary Ding wrote:
Xun Ni:
You did not do this correctly.
I will suggest you use the following repo instead of using
a custom script to replace the scu package:
For your local repo where you had your package, you need to
list that first before the solaris repo:
e.g:
When I test my install nightly repo, this is what I did:
<source>
<publisher name="install-nightly">
<origin
name="file:/export/home/ding/sunstudio12u1patch/slim_source/packages/i386/nightly-nd/repo.redist"/>
</publisher>
<publisher name="solaris">
<origin name="http://ipkg.us.oracle.com/solaris11/dev"/>
On 05/15/11 11:32 PM, xun.ni wrote:
Hi, Dave:
I need to replace my package scu(driver/storage/scu)
with the lastest using the DC, and currently my
dc_ai_x86.xml and the custom script is in the attachment,
The key error point is "Unable to install
pkg://solaris/scu", my step is that i create a local IPS
server with "/usr/lib/pkg.depotd -d
/root/nightly/repo.redist/ -p 10000" and it contain the
lastest package, and then i run "/usr/bin/distro_const
build -v /root/dc_ai_x86.xml". I set a custom script to
replace the package with my own but it failed, can you
help me to figure out why it fail?
The output error is
2011-05-16 13:17:29,012 InstallationLogger.custom-script
INFO === Executing Custom Script Checkpoint ===
2011-05-16 13:17:29,012 InstallationLogger.custom-script
INFO Custom Script provided is:
'/export/home/scu_script.sh {PKG_IMAGE_PATH} scu'
2011-05-16 13:17:29,012 InstallationLogger.custom-script
INFO Custom Script to run is:
'/export/home/scu_script.sh
/export/home/dc/ai/build_data/pkg_image scu'
2011-05-16 13:17:29,013 InstallationLogger.custom-script
DEBUG Executing: /export/home/scu_script.sh
/export/home/dc/ai/build_data/pkg_image scu
2011-05-16 13:17:29,712 InstallationLogger.custom-script
DEBUG /usr/bin/pkg -R
/export/home/dc/ai/build_data/pkg_image uninstall scu
2011-05-16 13:17:30,161 InstallationLogger.custom-script
ERROR pkg: The image cannot be modified as it is
currently in use by another package client: pkg on
glasspaper.cn, pid 1257.
2011-05-16 13:17:30,202 InstallationLogger.custom-script
ERROR /export/home/scu_script.sh: Unable to install
pkg://solaris/scu
2011-05-16 13:17:30,254 InstallationLogger ERROR
Error occurred during execution of 'custom-script'
checkpoint.
Thanks,
Xun
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
