Xwin with solaris 10 installed in core mode

Hello,
I've installed the Solaris 10 in core mode. The problem is that I need to use the Xmanager software but i don't know which packages must be installed to run the Xmanager . Could someone help me. Thank you in advance
Huy Nguyen

What account are logged as? You can type "who" command without the quotation. You should be logged in a root. Root has total control of the system. If you want to go to the root account type "su" command.

Similar Messages

  • Trouble with Solaris 10 install on SunBlade 100 using Media CDs from Sun

    Hello World,
    My SunBlade 100 was not reading various burned Solaris 10 media, so I purchased the media kit from Sun. The installation is successful up until the point where it asks for CD2. I didn't even hear the drive spin when I clicked "Next" after inserting CD2.
    I know it is not the CD drive since it obviously works for CD1. It is also not an intermittent problem with the CD drive because CD1 works each time I run the install. I also don't think it is the media since CD2 went right from the factory envelope to my CD drive.
    So:
    1. Has anyone encountered something like this?
    2. Can I resume the installation from the command line?
    Many Thanks,
    Greg

    Actually ...
    Yes, it can be the optical drive.
    Those factory shipped drives in the SB100's were prone to spontaneously failing, one minute to the next.
    Additionally the CD's are actually written differently, whether they are the bootable ones in the set versus the non-bootable CDs in the set.
    Data track layouts are different.
    The optical drive could commonly have difficulty reading every disk you ever insert into it.
    Borrow a replacement drive from a PeeCee.
    Jumper it the same as the current drive and just use it.
    If that works, then go buy a replacement.
    Optical read-only drives are laughably cheap.
    Optical read/write DVD drives are inexpensive, as well.

  • Help with solaris 10 instalation

    Hi,
    after installing solaris 10, its asking me for login name & password? what should I do?

    Hi
    During the installation, you were asked for the root password. So you need to login as user 'root' using this password.
    The next thing that you should do is to create an ordinary user account for yourself. There's more than one way to do this, but an easy one is to launch /usr/sbin/smc (Solaris Management Console), select 'This Computer' in the Toolboxes list, then System Configuration (left panel) -> Users. After that it's something like Action->Add User (I don't have the necessary priveleges on the machine that I'm using). Then you can logout as root and log back in as the user that you created.
    Paul

  • Simply setup client features with server installed in advanced mode...

    Hi,
    If I setup my server in standard "mode" I see that Leopard clients discover my server automatically and the server try to set all clients fatures (Mail accounts, Ical server, etc.).
    There is a way to activate this useful fature ALSO with a server installed in "advanced" mode?
    My server need to be installed in advanced mode because it's an open directory master with a DNS that serve all my lan.
    Thanks in advance...

    Hi Kranthi_06,
    According to your description, you have an environment with reporting services installed, the info given by the client they are using reportingservices with sharepoint integrated mode. In SSMS, you can see two databases with names reportserver$DEN2010 and
    reportserver$DEN2010tempdb.
    In Native Mode, in the SQL Server Installation Wizard, if we select Install and configure option, the ReportServer database will be created automatically through Setup. If we choose the Install only option, we must use the Reporting Services Configuration
    Manager to create the database manually. By default, the database format is ReportServer and ReportServerTempDB. In SharePoint Mode, we need to create at least one Reporting Services service application by using SharePoint Central Administration or Reporting
    Services PowerShell cmdlets, then three databases are created for each Reporting Services service application and the database names by default include a guid that represents the service application. The following are example names of the three SharePoint
    mode databases:
    ReportingService_90a9f37075544f22953c4a62e4a9f370
    ReportingService_90a9f37075544f22953c4a62e4a9f370TempDB
    ReportingService_90a9f37075544f22953c4a62e4a9f370_Alerting
    For SSRS 2008 R2 or early versions, we can identify report server mode using the Reporting Services Configuration Manager. For SSRS 2012 or later versions, Reporting Services Configuration Manager no longer supports Reporting Services SharePoint mode. Configuration
    of SharePoint mode is completed using SharePoint Central Administration.
    Reference:
    Verifying SharePoint integrated mode installation
    Create a Report Server Database
    If you have any more questions, please feel free to ask.
    Thanks,
    Wendy Fu

  • Does Proliant ML 370 G5 work with Solaris 10 64-bits?

    Does this server work with Solaris 10 in 64 bit mode?
    http://www.sun.com/bigadmin/hcl/data/systems/details/1891.html doesn't indicate if it is certified for 64 bits.
    and http://h71028.www7.hp.com/enterprise/cache/493913-0-0-0-121.html indicates only 32 bits.
    Message was edited by:
    Jose_Luis_Rodriguez

    Does this server work with Solaris 10 in 64 bit mode?
    http://www.sun.com/bigadmin/hcl/data/systems/details/1891.html doesn't indicate if it is certified for 64 bits.
    and http://h71028.www7.hp.com/enterprise/cache/493913-0-0-0-121.html indicates only 32 bits.
    Message was edited by:
    Jose_Luis_Rodriguez

  • Solaris Studio 12.4 ccfe signal 11 with boost::unordered_set in C  11 mode

    Using Solaris Studio 12.4 on Solaris 10 update 10 x86, the following program crashes ccfe:
    #include <boost/unordered_set.hpp>
    #include <string>
    int main(int, char **)
        boost::unordered_set<std::string> strSet;
        std::string str("test");
        strSet.insert(str);
        return 0;
    Assuming the code is saved to main.cc, build it in C++11 mode using:
    CC -v -std=c++11 -m64 -I/usr/local/include/boost-1_54 main.cc
    The output is:
    ### CC: Note: NLSPATH = /opt/solarisstudio12.4/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/solarisstudio12.4/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
    ###     command line files and options (expanded):
    ### -v -std=c++11 -m64 -I/usr/local/include/boost-1_54 main.cc
    /opt/solarisstudio12.4/lib/compilers/ccfe -xarch=amd64 -std=c++11 -D__SunOS_5_10 -D__SUNPRO_CC=0x5130 -D__unix -D__SVR4 -D__sun -D__SunOS "-D__builtin_expect(e,x)=e" -D__x86_64 -D__x86_64__ -D__amd64 -D__amd64__ -D_LP64 -D__LP64__ -D__BUILTIN_VA_STRUCT -Dunix -Dsun -D__SUN_PREFETCH -D__SUNPRO_CC_COMPAT='G' -include /opt/solarisstudio12.4/lib/compilers/include/CC/gnu/builtins.h -include /opt/solarisstudio12.4/lib/compilers/include/CC/gnu/builtins-def.h -I/usr/local/include/boost-1_54 -I-xbuiltin -I/opt/solarisstudio12.4/lib/compilers/include/CC/gnu -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2/ -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2//backward -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/include/c++/4.8.2/i386-sun-solaris2.10/amd64/ -I/opt/solarisstudio12.4/lib/compilers/include/cc -I/usr/include -I/opt/solarisstudio12.4/lib/compilers/CC-gcc/lib/gcc/i386-sun-solaris2.10/4.8.2/include// -ptf /tmp/ccfe.1422033660.29374.03.%1.%2 -ptx /opt/solarisstudio12.4/bin/CC -ptk "-v -std=c++11 -m64 -I/usr/local/include/boost-1_54 " -compat=g -xdebuginfo=%none -xdbggen=dwarf+usedonly+incl -xF=%none -xbuiltin=%none -xldscope=global -xivdep=loop -O0 -xarrayloc main.cc -o /tmp/ccfe.1422033660.29374.01.ir 2> /tmp/ccfe.1422033660.29374.02.err
    /opt/solarisstudio12.4/lib/compilers/stdlibfilt -stderr < /tmp/ccfe.1422033660.29374.02.err
    >> Signal 11:
        while processing main.cc at line 0.
    rm /tmp/ccfe.1422033660.29374.02.err
    rm /tmp/ccfe.1422033660.29374.01.ir
    I know Boost 1.54 is not the most recent version, but the only changes to unordered_set.hpp between 1.54 and the current master branch in Boost's Git repository are Visual Studio 2013 workarounds, so I strongly suspect the same problem would occur with Solaris Studio 12.4 and more recent versions of Boost.
    This problem can be avoided by using std::unordered_set instead of boost::unordered_set.  However, since the compiler actually suffers a SEGV rather than giving a nice error message I thought I'd report this in case it's a sign of a problem in the compiler that might occur under other circumstances too.

    Thanks for the help.  Yes, sorry, I should have made clear that this is after trying to use Boost in C++11 mode.  I agree that the problem doesn't occur when using Solaris Studio in C++11 mode but Boost configured not to use any C++11 features.
    I made quite a few edits to the Boost code, including the ones Steve posted in this thread.  The edit that causes this problem to occur is the one to boost/config/compiler/sunpro_cc.hpp that removes all the BOOST_NO_CXX11_* macros.
    It sounds like I should just hold off trying to use Boost in C++11 mode until the next version of Solaris Studio is out.
    The pstack from the ccfe core dump is:
    core 'core.1503' of 1503:       /opt/solarisstudio12.4/lib/compilers/ccfe -xarch=amd64 -std=c++11 -D__
    ffff0000 ???????? (8041218, 8, fcf58e0, 0)
    082b7713 __1cPtemp_name_substKsubstitute6MrknQfull_syntax_name__1_ (8041260, 8041180) + 163
    082be63d __1cKexpr_substKvisit_name6MpnJname_expr__v_ (80413c0, ad65da8, 8041348, 8275d73) + fd
    082bc775 __1cKexpr_substKsubstitute6MpknEexpr__p1_ (80413c0, f2cab18, 80413a8) + 35
    082b858b __1cPtemp_name_substQsubst_single_arg6MnPtemplate_actual__k1_ (80415d0, 8041b10, f2cab18, 103, 8041570, 0) + 2fb
    082b8e10 __1cPtemp_name_substUsubstitute_temp_args6MrknbBtemplate_actuals_collection_pknXtemplate_parameter_list__1_ (8041890, 8041b10) + 150
    082ba050 __1cPtemp_name_substPvisit_temp_args6MrknbJsyntax_name_with_template_arguments__v_ (8041b10, fc9dd80, 8041ac0, 8041964) + 30
    082ba2c8 __1cPtemp_name_substFvisit6MrknQsyntax_name_impl4eInSsyntax_name_sort_t____v_ (8041b10, fc9dd80, fcf5610, 0) + 18
    082b76d1 __1cPtemp_name_substKsubstitute6MrknQfull_syntax_name__1_ (8041bf0, 8041b10) + 121
    082b526b __1cPtemp_type_substUvisit_name_dependent6MpnEtype_pnTname_dependent_type__v_ (8041eb0, f2e1aa4, f2e1a58, f2e21f0) + 5b
    082b3930 __1cPtemp_type_substTsubstitute_ret_type6MpnJfunc_type__pnEtype__ (8041eb0, f2e2178, 8041d08, 8041d60) + 30
    082b3c2c __1cPtemp_type_substKvisit_func6MpnEtype_pnJfunc_type__v_ (8041eb0, f2e21a0, f2e2178, f2e21f0) + 25c
    082ba941 __1cPtemp_type_substTexpand_in_func_type6MpnJfunc_type__2_ (8041eb0) + 31
    0816b754 __1cIfunc_symRnew_template_spec6kMrknbBtemplate_actuals_collection_rknIposition__pnDsym__ (f2e21f0) + c4
    082c941b __1cQtemplate_matcherIgen_func6M_pnIfunc_sym__ (8042050, ad62d58, ad65960, 0) + 59b
    0828af3f ???????? (80420f4, ad65940, 80421a0, 0, ad62c50, 0)
    0828b2c9 __1cNoverload_call6FpnJcall_expr_rknJsym_array_4brknbBtemplate_actuals_collection_nEtypeKtype_class_b_2_ (8042198, ad65940, 804219c, 80421a0, 0, ad62c50) + 99
    08204c38 ???????? (ad65940)
    082086ff __1cLtypify_call6FpnJcall_expr_I_pnEexpr__ (ad65940, 4, 0, fd33148) + 9bf
    081e36a5 __1cXtypify_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8042530, ad65940, 0, 0) + 15
    081e4529 __1cGtypify6FpnEexpr_I_1_ (ad65940, 4, 0, 0) + c9
    082b1e0a __1cJexpr_stmtOpass_thru_expr6MpnEexprHvisitor__v_ (ad659a0, 80425b0, 0, 83bb23e) + 1a
    081e3cd1 __1cXtypify_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8042660, ad62b28, 8042608, 83bbbe9) + 71
    081e4529 __1cGtypify6FpnEexpr_I_1_ (ad62b28, 0, 8759ec0, fc9b740) + c9
    08266956 __1cWstore_inline_func_body6FpnIfunc_sym_pnFscope_bb_pnEexpr__ (fd2fc80, fc9b740, 1, 1) + 426
    082700c8 __1cSinline_bookkeepingOprocess_inline6MpnIfunc_sym_pnJcall_expr_pnEexpr__6_ (8d61508) + 268
    08270542 __1cSinline_bookkeepingNexpand_inline6MpnJcall_expr_pnEexpr__4_ (8d61508, ad5ecf8, 87594a8, 0) + f2
    081e10e3 ???????? (ad5ecf8, 80005, 8043208, 85a44ab)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043220, ad5ecf8, fd1e6b8, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad5ecf8, 80005, 8043288, 0) + a2
    082a94e7 ???????? (ad5ecf8, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (8043350, ad5ed58, 80432f8, 804337c) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (8043350, ad5ed58, 2211, 7fefefef) + 8f
    082b06b5 __1cRstmt_bind_visitorPvisit_statement6MpnOstatement_expr__v_ (8043350) + b5
    082a9294 __1cJstmt_bind6FpnOstatement_expr_b_v_ (ad5bef0) + b4
    081df9c6 ???????? (ad5bef0, 0, 8043428, 8272a37)
    081d6e18 __1cWbind2_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8043420, ad5bef0, 8043448, 8043494) + 98
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad5bef0, 0, 8043488, 81710d5) + a2
    082726f0 __1cSinline_bookkeepingQfinish_expansion6MrnbDfunction_definition_interface_pnEexpr__4_ (8d61508, fd2b46c, ad5bef0, 0) + 160
    081e10f9 ???????? (ad4b210, 80005, 8043528, 82759da)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043520, ad4b210, 0, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad4b210, 80005, 8043578, ad55cc0) + a2
    082a94e7 ???????? (ad4b210, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (8043650, ad4b270, fd1e668, 874cef8) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (8043650, ad4a7b0, 1, 7fefefef) + 8f
    082b06b5 __1cRstmt_bind_visitorPvisit_statement6MpnOstatement_expr__v_ (8043650) + b5
    082a9294 __1cJstmt_bind6FpnOstatement_expr_b_v_ (ad4a520) + b4
    081d6e18 __1cWbind2_dispatch_visitorPvisit_statement6MpnOstatement_expr__v_ (8043720, ad4a520, 8043748, 8043794) + 98
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad4a520, 0, 8043788, 81710d5) + a2
    082726f0 __1cSinline_bookkeepingQfinish_expansion6MrnbDfunction_definition_interface_pnEexpr__4_ (8d61508, fc7b144, ad4a520, 0) + 160
    081e10f9 ???????? (ad035e8, 80005, fd1e368, 85a4400)
    081d673e __1cWbind2_dispatch_visitorKvisit_call6MpnJcall_expr__v_ (8043820, ad035e8, acffdb8, fcb9a40) + 9e
    081d7662 __1cHbind2erKbind2_body6FpnEexpr_I_2_ (ad035e8, 80005, 8043878, 0) + a2
    082a94e7 ???????? (ad035e8, 0, 0, 0)
    082aaaf3 __1cRstmt_bind_visitorKvisit_expr6MpnJexpr_stmt__v_ (80439c0, ad03648, ad03668, 8759ec0) + 93
    082a8f2f __1cRstmt_bind_visitorOstmt_list_bind6MpnJstatement__2_ (80439c0, acf9468, 0, 82d7323) + 8f
    082afb6b __1cRstmt_bind_visitorWvisit_function_variant6MpnNfunction_stmt_b_v_ (80439c0, ad04358, 1, 8043a30) + 46b
    082afe10 __1cRstmt_bind_visitorOvisit_function6MpnNfunction_stmt__v_ (80439c0, ad04358, ad04378, 8759ec0) + 40
    082a916f __1cUstmt_bind_and_expand6FpnJstatement__1_ (ad04358, 3, fc55f4b, 80443c4) + 11f
    08257545 __1cMfunc_contextJpostamble6MrnbDfunction_definition_interface_pnNfunction_stmt__v_ (871cc98) + d5
    082e879d __1cTimmediate_func_body6FpnIfunc_sym__v_ (fbd3840, fbd3390, 8044dd0, 821b71f) + 3fd
    08266428 __1cMparse_inline6FrnbDfunction_definition_interface__v_ (fbd385c, fbd38cc, 8044eb0, 95a38d4) + 188
    084db8c8 __1cLemit_inline6FpnIsym_list__v_ (fca5328, fca5328) + 2d8
    084d88f1 __1cQcompilation_unitFclean6M_b_ (8759310) + a1
    084dd507 __1cIfinalgen6F_v_ (8c3ffa8, 8759178, 8046eb8, 815db68, 1, 8c41eb8) + 67
    082f533b __1cGanalys6Fb_v_ (1, 8c41eb8, 8046eb8, 815d5d7) + db
    0815db68 __1cHtmcplus6Fri0bpnHoptions__nHsym_set__ (8046f00, 8046ef8, 8046efc, 1, 8c4ced8, 86417b1) + 2be8
    082e5943 main     (34, 8047360, 8047434) + 283
    08153f22 _start   (34, 8047514, 804753e, 804754b, 8047556, 8047565) + 72

  • Several mysterious problems with Solaris 11 x86 install

    Hi folks,
    I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
    I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
    http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
    Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
    There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
    After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
    Many thanks,
    Chris Tidy
    Edited by: Chris Tidy on 23-Mar-2012 03:36

    Hi folks,
    I've recently installed Solaris 11 x86 as a replacement for Solaris 9 SPARC on an Ultra 2 machine. I like the operating system, but I've promptly acquired some mysterious problems. The computer is a Fujitsu Siemens Esprimo E2500 with a Pentium 4 HT 3.06 GHz processor, 2 GB RAM, an 80 GB SATA disk and a 147 GB SCSI disk.
    I have had a few occasions on which the screen goes totally blank, the monitor claims that there is no signal, and I have to restart the machine. However, with the blank screen, the hard drive activity light is sometimes still flashing. This happens predictably when I try to log off (as opposed to shutting down) and when I use Totem media player and click on anything inside the Totem window. The motherboard has built-in graphics and brief specifications can be found here:
    http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRIMO/Datasheets/ds_esprimo_edition_e2500.pdf
    Yesterday my PS/2 keyboard started causing the motherboard to beep crazily when I use it. It beeps rapidly 4 times, then prints the expected character. However, the problem doesn't occur at the initial log in screen. The mouse cursor has also gone beserk on one occasion, flying all over the screen (I had this problem with a previous PC, but a different OS, and thought it was a hardware fault, which I why I got this new computer). With the keyboard problem, the machine is basically unusable. However, it is configured as a dual boot machine, and the keyboard problem isn't present with Windows XP.
    There are also a few smaller, odd problems. Occasionally all the icons vanish from my Gnome desktop. The command prompt also mysteriously changed from $chris@pluto to $bash-4.1 just before the keyboard problem appeared, although that might have had something to do with me copying my home directory to a different disk and editing the /etc/auto_home file (moving the home directory worked fine). Also, unlike with Solaris 9 SPARC, I find that I have to have external SCSI devices switched on at boot time, should I want to use them later. That's a pain. With Solaris 9, I could run "boot -r" when I first attached the device, then switch on the SCSI devices and mount them whenever I wanted.
    After the useful advice I received here about "more" and "less", I thought I'd post these problems and see if anyone can help. I'd really appreciate some advice. Can anyone identify likely causes for these problems? Which problems can I expect to solve and which do I have to live with?
    Many thanks,
    Chris Tidy
    Edited by: Chris Tidy on 23-Mar-2012 03:36

  • AE CS5 not opening with 'installizing media core'

    I just updated my mac pro laptop to an 0SX 10.9 and installed my adobe suite cs5.
    Aftereffects gets stuck when opening with the text 'installziing media core'. I have no 3rd party apps on my computer as it's brand new. I have quicktime pro 7. Please help!

    Many thanks for your response. Miraculously CS5 is has just started working on my Mavericks, after a few failed attempts at downloading CSS.
    Date: Sat, 8 Feb 2014 07:30:31 -0800
    From: [email protected]
    To: [email protected]
    Subject: AE CS5 not opening with 'installizing media core'
        Re: AE CS5 not opening with 'installizing media core'
        created by Rick Gerard in After Effects - View the full discussion
    You should have checked the forums or at least system requirements before upgrading to Mavericks. After Effects CS5 is not compatible with Mavericks. You will have to revert or upgrade.
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6100105#6100105
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6100105#6100105
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6100105#6100105. In the Actions box on the right, click the Stop Email Notifications link.
               Start a new discussion in After Effects at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Problem while installing OEL core with nfs

    Hello,
    I'm trying to set up an minimal Installation of OEL 5
    i've got following ks file:
    #System language
    lang en_US
    #Language modules to install
    langsupport en_US
    #System keyboard
    keyboard de-latin1-nodeadkeys
    #System mouse
    mouse genericwheelps/2
    #Sytem timezone
    timezone Europe/Berlin
    #Root password
    rootpw ###################################
    #Reboot after installation
    reboot
    #Install Red Hat Linux instead of upgrade
    install
    #Install in Text Mode
    text
    #Use NFS Server
    nfs server ###.###.###.### dir /data/yum/DISK-ISO
    #System bootloader configuration
    bootloader --location=mbr
    #Clear the Master Boot Record
    zerombr yes
    #Partition clearing information
    clearpart --all
    #Disk partitioning information
    part swap size=1024 ondisk=sda
    part /tmp fstype "ext3" size=2048 --ondisk=sda
    part /var fstype "ext3" size=2048 --ondisk=sda
    part / fstype "ext3" size=4096 --ondisk=sda
    part /opt fstype "ext3" size=2048 grow ondisk=sda
    part /data fstype "ext3" size=4096 --ondisk=sda
    #System authorization infomation
    auth useshadow  enablemd5
    #Network information
    network bootproto=static ip=###.###.###.### netmask=255.255.255.0 gateway=###.###.###.### nameserver=###.###.###.### hostname=###### --device=eth0
    #Firewall configuration
    firewall --disabled
    #XWindows configuration information
    xconfig depth=24 resolution=1024x768 defaultdesktop=KDE monitor="Hitachi CM752"
    #Selinux ändern
    selinux --disabled
    #Package install information
    %packages
    @core
    rpm
    rpm-libs
    yum
    kernel
    ruby
    ruby-libs
    device-mapper
    e2fsprogs-libs
    gdbm
    keyutils-libs
    krb5-libs
    libtermcap
    openssl
    facter
    which
    ruby-rdoc
    ruby-irb
    puppet
    augeas-libs
    ruby-augeas
    ruby-shadow
    There should run the minimal os and the puppet client to set up the system by puppet.
    While installation i get following Error Message:
    You have specified that the group 'core' should be installed. This group does not exist. Would you like to continue or abort your installation?
    I Tryed to continue, and it installs a completely other Package group, but i dont know what a Group.
    The Group defenition is under DISK-ISO/Server/repodata/comps-rhel5-server-core.xml (the other files are other.xml.gz, repomd.xml, filelists.xml.gz, primary.xml.gz, TRANS.TBL)
    Hope You can help me!
    The Group core in the XML File Shows (Don't know why, but many latters are crypted (?!)):
    <group>
    <id>core</id>
    <name>Core</name>
    <name xml:lang="af">Kern</name>
    <name xml:lang="am">ማዕከላዊ ቦታ</name>
    <name xml:lang="ar">اللبّ</name>
    <name xml:lang="as">মূল</name>
    <name xml:lang="bal">هستگ</name>
    <name xml:lang="be">Падмурак</name>
    <name xml:lang="bg">Основа</name>
    <name xml:lang="bn">কোর (Core)</name>
    <name xml:lang="bn_IN">কোর</name>
    <name xml:lang="bs">Jezgra</name>
    <name xml:lang="ca">Nucli</name>
    <name xml:lang="cs">Základ</name>
    <name xml:lang="cy">Craidd</name>
    <name xml:lang="da">Grundlæggende</name>
    <name xml:lang="de">Kern</name>
    <name xml:lang="el">Πυρήνας</name>
    <name xml:lang="en_GB">Core</name>
    <name xml:lang="es">Núcleo</name>
    <name xml:lang="et">Tuum</name>
    <name xml:lang="fa">اصل</name>
    <name xml:lang="fi">Keskeiset</name>
    <name xml:lang="fr">Core</name>
    <name xml:lang="gl">Núcleo</name>
    <name xml:lang="gu">મૂળ</name>
    <name xml:lang="he">ליבה</name>
    <name xml:lang="hi">कोर</name>
    <name xml:lang="hr">Jezgra</name>
    <name xml:lang="hu">Mag</name>
    <name xml:lang="hy">Õ€Õ«Õ´Ö„</name>
    <name xml:lang="id">Inti</name>
    <name xml:lang="ilo">Bugas</name>
    <name xml:lang="is">Lágmarkskerfi</name>
    <name xml:lang="it">Principale</name>
    <name xml:lang="ja">コア</name>
    <name xml:lang="ka">ბირთვი</name>
    <name xml:lang="kn">ಅಂತಸ್ಸಾರ</name>
    <name xml:lang="ko">핵심</name>
    <name xml:lang="lv">Pamatsistēma</name>
    <name xml:lang="mk">Основни</name>
    <name xml:lang="ml">കോറ്‍</name>
    <name xml:lang="mr">कोर</name>
    <name xml:lang="ms">Teras</name>
    <name xml:lang="nb">Kjerne</name>
    <name xml:lang="ne">कोर</name>
    <name xml:lang="nl">Kern</name>
    <name xml:lang="no">Kjerne</name>
    <name xml:lang="nso">Bogare</name>
    <name xml:lang="or">ପàà¬°à¬®à‚ଖ</name>
    <name xml:lang="pa">ਮੂਲ</name>
    <name xml:lang="pl">Rdzeń</name>
    <name xml:lang="pt">Núcleo</name>
    <name xml:lang="pt_BR">Núcleo</name>
    <name xml:lang="ro">Nucleu</name>
    <name xml:lang="ru">Основа</name>
    <name xml:lang="si">න්‍යෂ්ඨිය</name>
    <name xml:lang="sk">Jadro</name>
    <name xml:lang="sl">Jedro</name>
    <name xml:lang="sr">Срж</name>
    <name xml:lang="sr@Latn">Srž</name>
    <name xml:lang="sr@latin">Srž</name>
    <name xml:lang="sv">Grund</name>
    <name xml:lang="ta">கோர்</name>
    <name xml:lang="te">అంతర్à°à°¾à°—à°‚</name>
    <name xml:lang="th">แกนหลัก</name>
    <name xml:lang="tr">Çekirdek</name>
    <name xml:lang="uk">Основа</name>
    <name xml:lang="ur">مرکز</name>
    <name xml:lang="vi">Lõi</name>
    <name xml:lang="zh_CN">核心</name>
    <name xml:lang="zh_TW">主要</name>
    <name xml:lang="zu">Okuyikhona</name>
    <description>Smallest possible installation</description>
    <description xml:lang="af">Kleinste moontlike installasie</description>
    <description xml:lang="am">ትንሹ የሚቻለው የማስገባት ሥራ</description>
    <description xml:lang="ar">أصغر تثبيت متاØ</description>
    <description xml:lang="as">ক্ষুদ্ৰতম সাম্à¦à§±à¦ªà§° সংস্থাপন</description>
    <description xml:lang="bal">هوردترین نصب ممکن</description>
    <description xml:lang="be">Найменшая з магчымых усталёўка</description>
    <description xml:lang="bg">Най-малката възможна инсталация</description>
    <description xml:lang="bn">যথাসম্à¦à¦¬ সংক্ষিপ্ত ইনস্টলেশন</description>
    <description xml:lang="bn_IN">ন্যূনতম ইনস্টলেশন</description>
    <description xml:lang="bs">Najmanja moguća instalacija</description>
    <description xml:lang="ca">La instal·lació més petita possible</description>
    <description xml:lang="cs">Nejmenšà možná instalace</description>
    <description xml:lang="cy">Arsefydliad lleiaf posib</description>
    <description xml:lang="da">Mindst mulige installation</description>
    <description xml:lang="de">Kleinstmögliche Installation</description>
    <description xml:lang="el">Μικρότερη δυνατή εγκατάσταση</description>
    <description xml:lang="en_GB">Smallest possible installation</description>
    <description xml:lang="es">Instalación lo más pequeña posible</description>
    <description xml:lang="et">Väikseim võimalik installatsioon</description>
    <description xml:lang="fa">کوچکترین نصب ممکن</description>
    <description xml:lang="fi">Pienin mahdollinen asennus</description>
    <description xml:lang="fr">Plus petite installation possible</description>
    <description xml:lang="gu">નાનામાં નાના શક્ય સ્થાપનો</description>
    <description xml:lang="he">התקנה מזערית</description>
    <description xml:lang="hi">सबसे छोटा संà¤à¤¾à¤µà¤¿à¤¤ अधिष्ठापन</description>
    <description xml:lang="hr">Najmanja moguća instalacija</description>
    <description xml:lang="hu">Minimális telepÃtés</description>
    <description xml:lang="hy">Õ“Õ¸Ö„Ö€Õ¡Õ£Õ¸Ö‚ÕµÕ¶ Õ°Õ¶Õ¡Ö€Õ¡Õ¾Õ¸Ö€ Õ¿Õ¥Õ²Õ¡Õ¤Ö€Õ¸Ö‚Õ´</description>
    <description xml:lang="id">Instalasi sekecil mungkin</description>
    <description xml:lang="is">Lágmarks uppsetning</description>
    <description xml:lang="it">Installazione minima</description>
    <description xml:lang="ja">最小限のインストール</description>
    <description xml:lang="ka">უმცირესი შესაძლო ჩადგმა</description>
    <description xml:lang="kn">ಅತ್ಯಲ್ಪಸಾಧ್ಯ ಅನುಸ್ಥಾಪನೆ</description>
    <description xml:lang="ko">가능한 최소 설치</description>
    <description xml:lang="lv">Vismazākā iespējamā instalācija</description>
    <description xml:lang="mk">Најмалата можна инсталација</description>
    <description xml:lang="ml">സാധ്യമായ ഏറ്റവും ചെറിയ ഇന്‍സ്റ്റലേഷന്‍</description>
    <description xml:lang="mr">सर्वात लहान शक्य प्रतिष्ठापन</description>
    <description xml:lang="ms">Pemasangan sekecil mungkin</description>
    <description xml:lang="nb">Minste mulige installering</description>
    <description xml:lang="ne">सम्à¤à¤¾à¤µà¤¿à¤¤ सबैà¤à¤¨à¥à¤¦à¤¾ सानो स्थापना</description>
    <description xml:lang="nl">Kleinst mogelijke installatie</description>
    <description xml:lang="no">Minste mulige installering</description>
    <description xml:lang="nso">Go tsenya mo go kgonegago go gonyenyane kudu</description>
    <description xml:lang="or">କàà¬·àà¬¦àà¬°à¬¤à¬® ସମàà¬à¬¾à¬¬àà¬¯ ସàà¬¥à¬¾à¬ªà¬¨</description>
    <description xml:lang="pa">ਘੱਟੋ-ਘੱਟ ਸੰà¨à¨µ ਇੰਸਟਾਲੇਸ਼ਨ</description>
    <description xml:lang="pl">Najmniejsza możliwa instalacja</description>
    <description xml:lang="pt">A mais pequena instalação possÃvel</description>
    <description xml:lang="pt_BR">Menor instalação possÃvel</description>
    <description xml:lang="ro">Cea mai mică instalare posibilă</description>
    <description xml:lang="ru">Минимально возможная установка</description>
    <description xml:lang="si">සිදුකල හැකි ඉà¶à·à¶¸ කුඩා ස්ථාපනය</description>
    <description xml:lang="sk">Najmenšia možná inštalácia</description>
    <description xml:lang="sl">Najmanjša možna namestitev</description>
    <description xml:lang="sr">Најмања могућа инсталација</description>
    <description xml:lang="sr@Latn">Najmanja moguća instalacija</description>
    <description xml:lang="sr@latin">Najmanja moguća instalacija</description>
    <description xml:lang="sv">Minsta möjliga installation</description>
    <description xml:lang="ta">மிக சிறிய நிறுவல்</description>
    <description xml:lang="te">సాధ్యమగు చిన్న సంస్థాపన</description>
    <description xml:lang="th">ติดตั้งให้มีขนาดเล็กที่สุดที่เป็นไปได้</description>
    <description xml:lang="tr">Olası en küçük kurulum</description>
    <description xml:lang="uk">Мінімально можливе встановлення</description>
    <description xml:lang="ur">چھو ٹی ممکن انسٹللشن </description>
    <description xml:lang="vi">Cài đặt nhỏ tối thiểu</description>
    <description xml:lang="zh_CN">最小安装</description>
    <description xml:lang="zh_TW">最小安裝</description>
    <description xml:lang="zu">Ukufakwa okuncane</description>
    <default>true</default>
    <uservisible>false</uservisible>
    <packagelist>
    <packagereq type="mandatory">authconfig</packagereq>
    <packagereq type="mandatory">basesystem</packagereq>
    <packagereq type="mandatory">bash</packagereq>
    <packagereq type="mandatory">coreutils</packagereq>
    <packagereq type="mandatory">cpio</packagereq>
    <packagereq type="mandatory">e2fsprogs</packagereq>
    <packagereq type="mandatory">ed</packagereq>
    <packagereq type="mandatory">file</packagereq>
    <packagereq type="mandatory">filesystem</packagereq>
    <packagereq type="mandatory">glibc</packagereq>
    <packagereq type="mandatory">hdparm</packagereq>
    <packagereq type="mandatory">initscripts</packagereq>
    <packagereq type="mandatory">iproute</packagereq>
    <packagereq type="mandatory">iprutils</packagereq>
    <packagereq type="mandatory">iputils</packagereq>
    <packagereq type="mandatory">kbd</packagereq>
    <packagereq type="mandatory">kudzu</packagereq>
    <packagereq type="mandatory">libgcc</packagereq>
    <packagereq type="mandatory">libhugetlbfs</packagereq>
    <packagereq type="mandatory">libtermcap</packagereq>
    <packagereq type="mandatory">mkinitrd</packagereq>
    <packagereq type="mandatory">passwd</packagereq>
    <packagereq type="mandatory">policycoreutils</packagereq>
    <packagereq type="mandatory">prelink</packagereq>
    <packagereq type="mandatory">procps</packagereq>
    <packagereq type="mandatory">readline</packagereq>
    <packagereq type="mandatory">oracle-logos</packagereq>
    <packagereq type="mandatory">enterprise-release</packagereq>
    <packagereq type="mandatory">enterprise-release-notes</packagereq>
    <packagereq type="mandatory">rootfiles</packagereq>
    <packagereq type="mandatory">rpm</packagereq>
    <packagereq type="mandatory">selinux-policy-targeted</packagereq>
    <packagereq type="mandatory">setools</packagereq>
    <packagereq type="mandatory">setserial</packagereq>
    <packagereq type="mandatory">setup</packagereq>
    <packagereq type="mandatory">shadow-utils</packagereq>
    <packagereq type="mandatory">sysklogd</packagereq>
    <packagereq type="mandatory">SysVinit</packagereq>
    <packagereq type="mandatory">termcap</packagereq>
    <packagereq type="mandatory">util-linux</packagereq>
    <packagereq type="mandatory">vim-minimal</packagereq>
    <packagereq type="default">Deployment_Guide-en-US</packagereq>
    <packagereq type="default">elilo</packagereq>
    <packagereq type="default">gnu-efi</packagereq>
    <packagereq type="default">grub</packagereq>
    <packagereq type="default">ppc64-utils</packagereq>
    <packagereq type="default">s390utils</packagereq>
    <packagereq type="default">salinfo</packagereq>
    <packagereq type="default">sysfsutils</packagereq>
    <packagereq type="default">udftools</packagereq>
    <packagereq type="default">yaboot</packagereq>
    <packagereq type="optional">ecryptfs-utils</packagereq>
    <packagereq type="optional">rsyslog</packagereq>
    <packagereq type="optional">sgpio</packagereq>
    </packagelist>
    </group>

    Problem solved.
    I had to rebuild the repodata, including the groups file:
    createrepo -g groupfilepath repopath
    That work.
    Edited by: user9086675 on 28.04.2010 09:14 Status : Answerd
    Edited by: user9086675 on 28.04.2010 09:14

  • Formatting a HDD with the Solaris 8 install when the disk space is locked.

    I added memory, a printer, and a CD Writer to my PC, and then I reinstalled solaris 8. At the point where it asks which drive to use, the only available drive, which is my C: drive, shows up with a negative disk space value. However, when I look at the partition size, it is 20 GB, and if I change it, it has no effect on the negative value. This is a reinstall of Solaris 8 onto the same drive. Is there a way to fdisk the drive. Solaris 8 won't do it, and Partition Magic seems to only work with linux, which does not seem compatible with Solaris?

    I added memory, a printer, and a CD Writer to my PC, and then I reinstalled solaris 8. At the point where it asks which drive to use, the only available drive, which is my C: drive, shows up with a negative disk space value. However, when I look at the partition size, it is 20 GB, and if I change it, it has no effect on the negative value. This is a reinstall of Solaris 8 onto the same drive. Is there a way to fdisk the drive. Solaris 8 won't do it, and Partition Magic seems to only work with linux, which does not seem compatible with Solaris?

  • Can't boot computer with 10.5 install CD or Single User Mode, or Safe Mode.

    Ive written a couple times about this and responded to people who have similiar queeries but i just havent gotten any answers.
    I cannot log onto my computer, I boot up and get a blue screen, with a nice black arrow. Thats as far as i can get. Obviously happening to lots of people..So, ive tried rebooting holding the C key and with 10.5 install CD, ive tried Unix (command-S), Ive tried resetting PR Ram, ive tried mantra recitation and cooing to my laptop; ive tried all the shortcuts in Oreilly's book and the only thing that DOES work is holding the OPTION key while rebooting. This brings up a nice icon of a padlock and a place to type letters or words and then there is another arrow in a box. Is this Open Firmware? I dont have an open firmware password...Ive tried entering my user password but it doenst accept it. ( I did change my password last week, did that create these problems???) how do i by pass that password????? Is it open firmware? (the date reads 1904 when i do the command option-O F command, and i cant get beyond that either...HELP!!

    Hello,
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Utilities from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access the Menubar at top.
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Reset Password from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Reset Password.
    Space between mount & -uw, space between -uw & the /
    rm /var/db/.applesetupdone
    Space after rm, before the 1st /

  • Problems with Solaris 11 11/11

    Hi,
    I need your help because I have problems with Solaris 11 11/11 installed in a Dell Latitude E4310.
    Here, there are the problems:
    1- No it power off with shutdown or init 5 or init 0 only work well the reboot.
    2- It can not connect to the wifi with wpa, no receive ip by dhcp, the driver of the card is "iwp"
    Thanks.
    Jorge
    Edited by: jdangelo on Nov 16, 2011 1:49 PM
    Edited by: jdangelo on Nov 17, 2011 2:51 PM

    Here is the info of my laptop;
    Manufacture name:Dell Inc.
    Manufacture model:Latitude E4310
    64 Bit:True
    OS version:SunOS solaris 5.11 11.0 i86pc i386 i86pc
    CPU Type:Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
    CPU Number:1
    Number Of Cores Per Processor:2
    Number Of Threads Per Processor:4
    Bios/Firmware Maker:Dell Inc. Version:A05 Release Date:11/20/2010
    prtconf -pv:
    System Configuration: Oracle Corporation i86pc
    Memory size: 3958 Megabytes
    System Peripherals (PROM Nodes):
    Node 0x000001
    bios-boot-device: '80'
    stdout: 00000000
    name: 'i86pc'
    Node 0x000002
    existing: 00c21000.00000000.02bc6001.00000000
    name: 'ramdisk'
    Node 0x000003
    acpi-namespace: '\_SB_.PCI0'
    compatible: 'pciex_root_complex'
    device_type: 'pciex'
    reg: 00000000.00000000.00000000.00000000.00000000
    #size-cells: 00000002
    #address-cells: 00000003
    name: 'pci'
    Node 0x000004
    reg: 00000000.00000000.00000000.00000000.00000000
    compatible: 'pci8086,44.1028.410.2' + 'pci8086,44.1028.410' + 'pci1028,410' + 'pci8086,44.2' + 'pci8086,44' + 'pciclass,060000' + 'pciclass,0600'
    model: 'Host bridge'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000000
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '0'
    class-code: 00060000
    revision-id: 00000002
    vendor-id: 00008086
    device-id: 00000044
    name: 'pci1028,410'
    Node 0x000005
    acpi-namespace: '\_SB_.PCI0.VID_'
    assigned-addresses: 83001010.00000000.f0000000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.000060b0.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
    reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
    compatible: 'pci8086,46.1028.410.2' + 'pci8086,46.1028.410' + 'pci1028,410' + 'pci8086,46.2' + 'pci8086,46' + 'pciclass,030000' + 'pciclass,0300'
    model: 'VGA compatible controller'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000000
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    device_type: 'display'
    unit-address: '2'
    class-code: 00030000
    revision-id: 00000002
    vendor-id: 00008086
    device-id: 00000046
    name: 'display'
    Node 0x000006
    acpi-namespace: '\_SB_.PCI0.GLAN'
    assigned-addresses: 8200c810.00000000.f5400000.00000000.00020000.8200c814.00000000.f5480000.00000000.00001000.8100c818.00000000.00006040.00000000.00000020
    reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
    compatible: 'pci8086,10ea.1028.410.5' + 'pci8086,10ea.1028.410' + 'pci1028,410' + 'pci8086,10ea.5' + 'pci8086,10ea' + 'pciclass,020000' + 'pciclass,0200'
    model: 'Ethernet controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '19'
    class-code: 00020000
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 000010ea
    name: 'pci1028,410'
    Node 0x000007
    acpi-namespace: '\_SB_.PCI0.EHC2'
    assigned-addresses: 8200d010.00000000.f5470000.00000000.00000400
    reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400
    compatible: 'pci8086,3b3c.1028.410.5' + 'pci8086,3b3c.1028.410' + 'pci1028,410' + 'pci8086,3b3c.5' + 'pci8086,3b3c' + 'pciclass,0c0320' + 'pciclass,0c03'
    model: 'Universal Serial Bus EHCI compliant'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1a'
    class-code: 000c0320
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b3c
    name: 'pci1028,410'
    Node 0x000008
    acpi-namespace: '\_SB_.PCI0.HDEF'
    assigned-addresses: 8300d810.00000000.f5460000.00000000.00004000
    reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
    compatible: 'pciex8086,3b57.1028.410.5' + 'pciex8086,3b57.1028.410' + 'pciex8086,3b57.5' + 'pciex8086,3b57' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,3b57.1028.410.5' + 'pci8086,3b57.1028.410' + 'pci1028,410' + 'pci8086,3b57.5' + 'pci8086,3b57' + 'pciclass,040300' + 'pciclass,0403'
    model: 'Mixed Mode device'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1b'
    class-code: 00040300
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b57
    name: 'pci1028,410'
    Node 0x000009
    acpi-namespace: '\_SB_.PCI0.RP01'
    slot-names: 00000001.746f6c53.00003333
    reg: 0000e000.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b42.5' + 'pciex8086,3b42' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b42.5' + 'pci8086,3b42' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00005000.81000000.00000000.00005000.00000000.00001000.82000000.00000000.f4000000.82000000.00000000.f4000000.00000000.01400000
    bus-range: 00000001.00000001
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000000
    devsel-speed: 00000000
    interrupts: 00000001
    unit-address: '1c'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b42
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b42'
    Node 0x00000a
    acpi-namespace: '\_SB_.PCI0.RP02'
    slot-names: 00000001.746f6c53.00003433
    reg: 0000e100.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b44.5' + 'pciex8086,3b44' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b44.5' + 'pci8086,3b44' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00004000.81000000.00000000.00004000.00000000.00001000.82000000.00000000.f2c00000.82000000.00000000.f2c00000.00000000.01400000
    bus-range: 00000002.00000002
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000001
    devsel-speed: 00000000
    interrupts: 00000002
    unit-address: '1c,1'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b44
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b44'
    Node 0x000013
    acpi-namespace: '\_SB_.PCI0.RP02.PXSX'
    assigned-addresses: 83020010.00000000.f2c00000.00000000.00002000
    reg: 00020000.00000000.00000000.00000000.00000000.03020010.00000000.00000000.00000000.00002000
    compatible: 'pciex8086,422c.8086.1321.35' + 'pciex8086,422c.8086.1321' + 'pciex8086,422c.35' + 'pciex8086,422c' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,422c.8086.1321.35' + 'pci8086,422c.8086.1321' + 'pci8086,1321' + 'pci8086,422c.35' + 'pci8086,422c' + 'pciclass,028000' + 'pciclass,0280'
    model: 'Network controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00008086
    subsystem-id: 00001321
    unit-address: '0'
    class-code: 00028000
    revision-id: 00000035
    vendor-id: 00008086
    device-id: 0000422c
    name: 'pci8086,1321'
    Node 0x00000b
    acpi-namespace: '\_SB_.PCI0.RP03'
    slot-names: 00000001.746f6c53.00000038
    reg: 0000e200.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b46.5' + 'pciex8086,3b46' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b46.5' + 'pci8086,3b46' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00003000.81000000.00000000.00003000.00000000.00001000.82000000.00000000.f1800000.82000000.00000000.f1800000.00000000.01400000
    bus-range: 00000003.00000003
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000002
    devsel-speed: 00000000
    interrupts: 00000003
    unit-address: '1c,2'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b46
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b46'
    Node 0x000014
    acpi-namespace: '\_SB_.PCI0.RP03.PXSX'
    assigned-addresses: 82030010.00000000.f1830000.00000000.00000100
    reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00000100
    compatible: 'pciex1180,e822.1028.410.1' + 'pciex1180,e822.1028.410' + 'pciex1180,e822.1' + 'pciex1180,e822' + 'pciexclass,080500' + 'pciexclass,0805' + 'pci1180,e822.1028.410.1' + 'pci1180,e822.1028.410' + 'pci1028,410' + 'pci1180,e822.1' + 'pci1180,e822' + 'pciclass,080500' + 'pciclass,0805'
    model: 'SD Host controller'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000001
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '0'
    class-code: 00080500
    revision-id: 00000001
    vendor-id: 00001180
    device-id: 0000e822
    name: 'pci1028,410'
    Node 0x00000c
    acpi-namespace: '\_SB_.PCI0.RP04'
    slot-names: 00000001.746f6c53.00000039
    reg: 0000e300.00000000.00000000.00000000.00000000
    compatible: 'pciex8086,3b48.5' + 'pciex8086,3b48' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b48.5' + 'pci8086,3b48' + 'pciclass,060400' + 'pciclass,0604'
    model: 'PCI-PCI bridge'
    ranges: 81000000.00000000.00002000.81000000.00000000.00002000.00000000.00001000.82000000.00000000.f0400000.82000000.00000000.f0400000.00000000.01400000
    bus-range: 00000004.00000009
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pciex'
    power-consumption: 00000001.00000001
    physical-slot#: 00000003
    devsel-speed: 00000000
    interrupts: 00000004
    unit-address: '1c,3'
    class-code: 00060400
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b48
    hotplug-capable:
    pci-hotplug-type: 00000001
    name: 'pci8086,3b48'
    Node 0x00000d
    acpi-namespace: '\_SB_.PCI0.EHCI'
    assigned-addresses: 8200e810.00000000.f5450000.00000000.00000400
    reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400
    compatible: 'pci8086,3b34.1028.410.5' + 'pci8086,3b34.1028.410' + 'pci1028,410' + 'pci8086,3b34.5' + 'pci8086,3b34' + 'pciclass,0c0320' + 'pciclass,0c03'
    model: 'Universal Serial Bus EHCI compliant'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1d'
    class-code: 000c0320
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b34
    name: 'pci1028,410'
    Node 0x00000e
    acpi-namespace: '\_SB_.PCI0.P0P1'
    slot-names: 0000002f.746f6c53.6c530031.0032746f.746f6c53.6c530033.0034746f.746f6c53.00000032
    reg: 0000f000.00000000.00000000.00000000.00000000
    compatible: 'pci8086,2448.a5' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
    model: 'Subtractive Decode PCI-PCI bridge'
    bus-range: 0000000a.0000000a
    #size-cells: 00000002
    #address-cells: 00000003
    device_type: 'pci'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    unit-address: '1e'
    class-code: 00060401
    revision-id: 000000a5
    vendor-id: 00008086
    device-id: 00002448
    name: 'pci8086,2448'
    Node 0x00000f
    #size-cells: 00000001
    #address-cells: 00000002
    ranges: 00000001.00000000.81000000.00000000.00000000.00000022.00000001.00000024.81000000.00000000.00000024.00000002.00000001.00000028.81000000.00000000.00000028.00000002.00000001.0000002c.81000000.00000000.0000002c.00000006.00000001.00000034.81000000.00000000.00000034.00000002.00000001.00000038.81000000.00000000.00000038.00000002.00000001.0000003c.81000000.00000000.0000003c.00000002.00000001.00000040.81000000.00000000.00000040.00000004.00000001.0000004e.81000000.00000000.0000004e.00000006.00000001.00000060.81000000.00000000.00000060.00000002.00000001.00000063.81000000.00000000.00000063.00000003.00000001.00000067.81000000.00000000.00000067.00000001.00000001.00000070.81000000.00000000.00000070.00000008.00000001.00000070.81000000.00000000.00000070.00000001.00000001.00000080.81000000.00000000.00000080.00000022.00000001.000000a4.81000000.00000000.000000a4.00000002.00000001.000000a8.81000000.00000000.000000a8.00000002.00000001.000000ac.81000000.00000000.000000ac.00000002.00000001.000000b0.81000000.00000000.000000b0.00000006.00000001.000000b8.81000000.00000000.000000b8.00000002.00000001.000000bc.81000000.00000000.000000bc.00000002.00000001.000000c0.81000000.00000000.000000c0.00000020.00000001.000000f0.81000000.00000000.000000f0.00000001.00000001.00000400.81000000.00000000.00000400.00000080.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000680.81000000.00000000.00000680.00000020.00000001.00000930.81000000.00000000.00000930.00000001.00000001.00000934.81000000.00000000.00000934.00000001.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001000.81000000.00000000.00001000.00000014.00000001.0000164e.81000000.00000000.0000164e.00000002.00000001.0000ffff.81000000.00000000.0000ffff.00000001.00000000.f54c0000.82000000.00000000.f54c0000.00001000.00000000.f8000000.82000000.00000000.f8000000.04000000.00000000.fed00000.82000000.00000000.fed00000.00000400.00000000.fed10000.82000000.00000000.fed10000.00004000.00000000.fed18000.82000000.00000000.fed18000.00002000.00000000.fed1c000.82000000.00000000.fed1c000.00024000.00000000.fed45000.82000000.00000000.fed45000.0004b000.00000000.fee00000.82000000.00000000.fee00000.00100000.00000000.ff000000.82000000.00000000.ff000000.01000000.00000000.ff000000.82000000.00000000.ff000000.01000000
    acpi-namespace: '\_SB_.PCI0.LPCB'
    device_type: 'isa'
    reg: 0000f800.00000000.00000000.00000000.00000000
    compatible: 'pci8086,3b0f.1028.410.5' + 'pci8086,3b0f.1028.410' + 'pci1028,410' + 'pci8086,3b0f.5' + 'pci8086,3b0f' + 'pciclass,060100' + 'pciclass,0601'
    model: 'ISA bridge'
    power-consumption: 00000001.00000001
    devsel-speed: 00000001
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f'
    class-code: 00060100
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b0f
    name: 'isa'
    Node 0x00001c
    unit-address: '1,60'
    interrupts: 00000001.0000000c
    reg: 00000001.00000060.00000001.00000001.00000064.00000001
    name: 'i8042'
    Node 0x00001d
    compatible: 'pnpPNP,303'
    device-type: 'keyboard'
    interrupts: 00000001.0000000c
    reg: 00000000
    acpi-namespace: '\_SB_.PCI0.LPCB.PS2K'
    model: 'System keyboard'
    name: 'keyboard'
    Node 0x00001e
    compatible: 'pnpPNP,f03'
    device-type: 'mouse'
    reg: 00000001
    interrupts: 0000000c
    acpi-namespace: '\_SB_.PCI0.LPCB.PS2M'
    model: 'PS/2 Port for PS/2-style Mice'
    name: 'mouse'
    Node 0x00001f
    interrupts: 00000004
    reg: 00000001.000003f8.00000008
    model: 'Standard serial port'
    compatible: 'PNP0500'
    name: 'asy'
    Node 0x000010
    acpi-namespace: '\_SB_.PCI0.SAT0'
    assigned-addresses: 8100fa10.00000000.00006090.00000000.00000008.8100fa14.00000000.00006080.00000000.00000004.8100fa18.00000000.00006070.00000000.00000008.8100fa1c.00000000.00006060.00000000.00000004.8100fa20.00000000.00006020.00000000.00000020.8200fa24.00000000.f5440000.00000000.00000800
    reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
    compatible: 'pci8086,3b2f.1028.410.5' + 'pci8086,3b2f.1028.410' + 'pci1028,410' + 'pci8086,3b2f.5' + 'pci8086,3b2f' + 'pciclass,010601' + 'pciclass,0106'
    model: 'SATA AHCI 1.0 Interface'
    power-consumption: 00000001.00000001
    66mhz-capable:
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,2'
    class-code: 00010601
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b2f
    name: 'pci1028,410'
    Node 0x000011
    acpi-namespace: '\_SB_.PCI0.SBUS'
    assigned-addresses: 8300fb10.00000000.f5430000.00000000.00000100.8100fb20.00000000.00006000.00000000.00000020
    reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
    compatible: 'pci8086,3b30.1028.410.5' + 'pci8086,3b30.1028.410' + 'pci1028,410' + 'pci8086,3b30.5' + 'pci8086,3b30' + 'pciclass,0c0500' + 'pciclass,0c05'
    model: 'SMBus (System Management Bus)'
    power-consumption: 00000001.00000001
    fast-back-to-back:
    devsel-speed: 00000001
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,3'
    class-code: 000c0500
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b30
    name: 'pci1028,410'
    Node 0x000012
    assigned-addresses: 8300fe10.00000000.f5420000.00000000.00001000
    reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000
    compatible: 'pci8086,3b32.1028.410.5' + 'pci8086,3b32.1028.410' + 'pci1028,410' + 'pci8086,3b32.5' + 'pci8086,3b32' + 'pciclass,118000' + 'pciclass,1180'
    model: 'DSP/DAP controllers'
    power-consumption: 00000001.00000001
    devsel-speed: 00000000
    interrupts: 00000003
    max-latency: 00000000
    min-grant: 00000000
    subsystem-vendor-id: 00001028
    subsystem-id: 00000410
    unit-address: '1f,6'
    class-code: 00118000
    revision-id: 00000005
    vendor-id: 00008086
    device-id: 00003b32
    name: 'pci1028,410'
    Node 0x000015
    device_type: 'acpirootnex'
    compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex'
    acpi-namespace: '\'
    name: 'fw'
    Node 0x000016
    unit-address: '1'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000000
    acpi-processor-id: 00000001
    acpi-namespace: '\_PR_.CPU0'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000017
    unit-address: '2'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000004
    acpi-processor-id: 00000002
    acpi-namespace: '\_PR_.CPU1'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000018
    unit-address: '3'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000001
    acpi-processor-id: 00000003
    acpi-namespace: '\_PR_.CPU2'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x000019
    unit-address: '4'
    compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
    apic-id: 00000005
    acpi-processor-id: 00000004
    acpi-namespace: '\_PR_.CPU3'
    device_type: 'acpicpu'
    name: 'cpu'
    Node 0x00001a
    unit-address: '0'
    compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex'
    acpi-namespace: '\_SB_'
    device_type: 'acpidevice'
    name: 'sb'
    Node 0x00001b
    io-space: 00000000.00000020.00000020.00000002.00000024.00000002.00000028.00000002.0000002c.00000002.0000002e.00000002.00000030.00000002.00000034.00000002.00000038.00000002.0000003c.00000002.00000040.00000004.0000004e.00000002.00000050.00000004.00000060.00000001.00000061.00000001.00000063.00000001.00000064.00000001.00000065.00000001.00000067.00000001.00000070.00000008.00000070.00000001.00000080.00000001.00000081.00000011.00000092.00000001.00000093.0000000d.000000a0.00000002.000000a4.00000002.000000a8.00000002.000000ac.00000002.000000b0.00000002.000000b2.00000002.000000b4.00000002.000000b8.00000002.000000bc.00000002.000000c0.00000020.000000f0.00000001.00000400.00000080.000004d0.00000002.00000500.00000080.00000680.00000020.00000930.00000001.00000934.00000001.00000cf8.00000008.00001000.00000004.00001004.00000010.0000164e.00000002.0000ffff.00000001
    device-memory: f54c0000.00001000.f8000000.04000000.fed00000.00000400.fed10000.00004000.fed18000.00001000.fed19000.00001000.fed1c000.00004000.fed20000.00020000.fed45000.0004b000.fee00000.00100000.ff000000.01000000.ff000000.01000000
    dma-channels: 00000004
    interrupts: 00000000.00000001.00000002.00000008.0000000c.0000000d
    name: 'used-resources'
    prtdiag:
    System Configuration: Dell Inc. Latitude E4310
    BIOS Configuration: Dell Inc. A05 11/20/2010
    ==== Processor Sockets ====================================
    Version Location Tag
    Intel(R) Core(TM) i5 CPU M 560 @ 2.67GH CPU 1
    ==== Memory Device Sockets ================================
    Type Status Set Device Locator Bank Locator
    Unknown in use 0 DIMM_A BANK 0
    unknown empty 0 DIMM_B BANK 2
    ==== On-Board Devices =====================================
    "Intel GM45 Graphics"
    NETWORK_NAME_STRING
    ==== Upgradeable Slots ====================================
    ID Status Type Description
    0 available PCI Express x16 J5C1
    1 available PCI Express J6C2
    2 in use PCI Express J6D2
    3 in use PCI Express J7C1
    4 available PCI Express J7D2
    System Information:
    Manufacturer:Dell Inc.
    Product:Latitude E4310
    BIOS Information:
    Vendor:Dell Inc.
    Version:A05
    Release Date:11/20/2010
    BIOS Revision: BIOS Revision:4.6
    Firmware Revision:
    MotherBoard Information:
    Product:0D8H24
    Manufacturer:Dell Inc.
    Version:A00
    Onboard Devices:[Video,Disabled]"Intel GM45 Graphics"
    CPU Information:
    Processor 0:
    Processor Socket Type:CPU 1
    Processor Manufacturer:Intel
    Current Voltage:0.0V
    External Clock:533MHZ
    Max Speed:4000MHZ
    Current Speed:2666MHZ
    Memory Information:
    Physical Memory: 4G (4G)
    Maximum Memory Support: 4096G
    Memory Subsystem 0:
    Array Used Function:System memory
    Memory Error Correction Supported:None
    Maximum Array Capacity:8G
    Number of Memory Devices:2
    Memory Device 0:
    Memory Device Locator:DIMM_A
    Total Width:64
    Data Width:64
    Installed Size:4096M
    Memory Device Type:Unknown
    Speed:1067MHZ
    Memory Device 1:
    [Not Installed]

  • Solaris 8 Installed, but won't run

    I�m pretty new to UNIX environments, so any advice or help in regard to the problem I�m having with Solaris 8 on my Compaq Presario would be much appreciated. It's a 1G Athlon with 128M of memory.
    I�ve installed the software, though throughout the installation I was only able to get monochrome screens after I got through the monitor/graphics adapter configuration. I have an old 14 inch SVGA 1024x768 monitor (frequency unknown) so I chose the multifrequency monitor at that resolution (interlaced) at a 14 inch screen size and the VGA 16 color graphics adapter, because my Nvidia TNT graphics card isn�t supported in the install program. I was then able to see a serviceable display test screen, though the colors were not accurate in every oval.
    The installation went smoothly after that, though as I say it was in monochrome without any depth in the graphics.
    I can now start Solaris, which proceeds through the Open Desktop Environment 1.4 screen, then freeezes at the screen with the multiple Solaris logos. This is all in monochrome by the way. No color appears. At this point the curser is a fat X (it does move when I move the mouse).
    Would I be correct that the problem is likely to be the need for a driver to support the Nvidia card? I found the Sun archive with the correct driver, but all the installation instructions seem to assume that Solaris is running and that I can get to a shell prompt, which if I can do that I don�t know how. Is there a boot option I need to use in order to get to a default shell?
    Thanks in advance for any advice.
    Paul Berk

    Try to boot into single user mode. At the following prompt...
    <pre>
    Boot path: /pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0:a
    Boot args:
    Type b [file-name] [boot-flags] <ENTER> to boot with options
    or i <ENTER> to enter boot interpreter
    or <ENTER> to boot with defaults
    <<< timeout in 5 seconds >>>
    Select (b)oot or (i)nterpreter:
    </pre>
    ... type <b><code>b -s</code></b>. Once you're in single user mode, install the latest video driver patch (109401-06). After the patch
    is installed, re-run
    <code>kdmconfig</code> to configure the video card.

  • Solaris 10 instalation in Guest Domain - Timed out waiting for TFTP reply

    I have the next trouble
    I have a Sun Fire T1000 and i want install two Guest LDOM's with Solaris10 in each one, I Install the LDOM Manager 1.0.3 and the service is "online" also the another services needed
    First Setup the 2 Guest LDOM's in the primary Domain sucesfully .... here is a desc of the configuration.
    # ldm list-bindings
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    primary active -n-cv SP 4 1G 0.1% 2h 14m
    MAC
    00:14:4f:a7:85:1e
    VCPU
    VID PID UTIL STRAND
    0 0 0.2% 100%
    1 1 0.2% 100%
    2 2 0.1% 100%
    3 3 0.1% 100%
    MAU
    ID CPUSET
    0 (0, 1, 2, 3)
    MEMORY
    RA PA SIZE
    0x8000000 0x8000000 1G
    VARIABLES
    diag-switch?=true
    security-#badlogins=0
    IO
    DEVICE PSEUDONYM OPTIONS
    pci@780 bus_a
    pci@7c0 bus_b
    VCC
    NAME PORT-RANGE
    primary-vcc0 5000-5100
    CLIENT PORT
    aplica_srss1@primary-vcc0 5001
    aplica_prod@primary-vcc0 5000
    VSW
    NAME MAC NET-DEV DEVICE MODE
    primary-vsw0 00:14:4f:a7:85:1e bge0 switch@0
    PEER MAC
    vnet2@aplica_srss1 00:14:4f:fb:f4:e0
    vnet1@aplica_prod 00:14:4f:fb:2c:60
    VDS
    NAME VOLUME OPTIONS DEVICE
    primary-vds0 vol1 /dev/dsk/c0t0d0s3
    CLIENT VOLUME
    vdisk1@aplica_prod vol1
    VCONS
    NAME SERVICE PORT
    SP
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    aplica_prod active -t--- 5000 4 2G 15% 9m
    MAC
    00:14:4f:fb:2c:60
    VCPU
    VID PID UTIL STRAND
    0 4 35% 100%
    1 5 0.0% 100%
    2 6 7.0% 100%
    3 7 84% 100%
    MEMORY
    RA PA SIZE
    0x8000000 0x48000000 2G
    VARIABLES
    auto-boot?=true
    boot-device=
    use-nvramrc?=true
    NETWORK
    NAME SERVICE DEVICE MAC
    vnet1 primary-vsw0@primary network@0 00:14:4f:fb:2c:60
    PEER MAC
    primary-vsw0@primary 00:14:4f:a7:85:1e
    vnet2@aplica_srss1 00:14:4f:fb:f4:e0
    DISK
    NAME VOLUME TOUT DEVICE SERVER
    vdisk1 vol1@primary-vds0 disk@0 primary
    VCONS
    NAME SERVICE PORT
    aplica_prod primary-vcc0@primary 5000
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    aplica_srss1 bound ----- 5001 24 13184M
    MAC
    00:14:4f:fb:ad:fb
    VCPU
    VID PID UTIL STRAND
    0 8 100%
    1 9 100%
    2 10 100%
    3 11 100%
    4 12 100%
    5 13 100%
    6 14 100%
    7 15 100%
    8 16 100%
    9 17 100%
    10 18 100%
    11 19 100%
    12 20 100%
    13 21 100%
    14 22 100%
    15 23 100%
    16 24 100%
    17 25 100%
    18 26 100%
    19 27 100%
    20 28 100%
    21 29 100%
    22 30 100%
    23 31 100%
    MEMORY
    RA PA SIZE
    0x8000000 0xc8000000 13184M
    VARIABLES
    auto-boot?=true
    boot-device=
    NETWORK
    NAME SERVICE DEVICE MAC
    vnet2 primary-vsw0@primary network@0 00:14:4f:fb:f4:e0
    PEER MAC
    primary-vsw0@primary 00:14:4f:a7:85:1e
    vnet1@aplica_prod 00:14:4f:fb:2c:60
    VCONS
    NAME SERVICE PORT
    aplica_srss1 primary-vcc0@primary 5001
    Then i mount the ISO images of The solaris OS 5/08, Later install the jumpstart server without troubles.... Here are the Configuration files needed for the properly setup of the service for a better guide

    # ./add_install_client -d -e 0:14:4f:fb:2c:60 -s Zolder:/var/jump_start/ sun4v
    cleaning up preexisting install client "0:14:4f:fb:2c:60"
    To disable 0:14:4f:fb:2c:60 in the DHCP server,
    remove the entry with Client ID 0100144FFB2C60
    To enable 0100144FFB2C60 in the DHCP server, ensure that
    the following Sun vendor-specific options are defined
    (SinstNM, SinstIP4, SinstPTH, SrootNM, SrootIP4,
    SrootPTH, and optionally SbootURI, SjumpCF and SsysidCF),
    and add a macro to the server named 0100144FFB2C60,
    containing the following option values:
    Install server (SinstNM) : Zolder
    Install server IP (SinstIP4) : 172.24.0.10
    Install server path (SinstPTH) : /var/jump_start/
    Root server name (SrootNM) : Zolder
    Root server IP (SrootIP4) : 172.24.0.10
    Root server path (SrootPTH) : /mnt/s0/Solaris_10/Tools/Boot
    Boot file (BootFile) : 0100144FFB2C60
    # cat /etc/inet/hosts // The Content of this file is exactly with ipnodes file
    127.0.0.1 localhost
    172.24.0.10 Zolder loghost
    172.24.0.9 primary-vsw0
    172.24.0.8 aplica_prod
    172.24.0.7 aplica_srss1
    # cat /etc/ethers
    00:14:4f:fb:2c:60 aplica_prod
    # cat /etc/bootparams
    aplica_prod root=Zolder:/mnt/s0/Solaris_10/Tools/Boot install=Zolder:/var/jump_start/ boottype=:in rootopts=:rsize=8192
    # cat /etc/dfs/dfstab
    share -F nfs -o ro,anon=0 /var/jump_start/
    share -F nfs -o ro,anon=0 /mnt/s0/Solaris_10/Tools/Boot
    share -F nfs -o ro,anon=0 /mnt/s1
    # ifconfig -a
    lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
    vsw0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 172.24.0.10 netmask fffffe00 broadcast 172.24.1.255
    ether 0:14:4f:a7:85:1e
    vsw0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 172.24.0.9 netmask fffffe00 broadcast 172.24.1.255
    Here i plumb up the networks interfaces and setup the vsw0 device and change the MAC address of the vsw0 for the same of the bge0 device.
    Then i Log to a Guest LDOM aplica_prod
    ----------START CONSOLE 1-------------------------------
    # telnet localhost 5000
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    Connecting to console "aplica_prod" in group "aplica_prod" ....
    Press ~? for control options ..
    ----END CONSOLE 1----
    At the same time i open another console for startup the Guest LDOM aplica_prod i make a snoop of the vsw0 interface
    ---START CONSOLE 2---
    # ldm start aplica_prod
    LDom aplica_prod started
    -bash-3.00# snoop -d vsw0 | grep aplica_prod
    Using device /dev/vsw0 (promiscuous mode)
    ---END CONSOLE 2-----
    In the other console is produced the next exit
    ----START CONSOLE 1------
    Sun Fire(TM) T1000, No Keyboard
    Copyright 2008 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.28.9, 2048 MB memory available, Serial #66792544.
    Ethernet address 0:14:4f:fb:2c:60, Host ID: 83fb2c60.
    Boot device: File and args:
    ERROR: boot-read fail
    Evaluating:
    Can't locate boot device
    {0} ok boot vnet1 install
    Boot device: /virtual-devices@100/channel-devices@200/network@0 File and args: install
    Requesting Internet Address for 0:14:4f:fa:82:17
    Requesting Internet Address for 0:14:4f:fa:82:17
    Timed out waiting for TFTP reply
    ---END CONSOLE 1-----
    in the console 2 the snoop generates an exit of the net traffic for the vsw0 device
    ----START CONSOLE 2--------
    primary-vsw0 -> aplica_prod RARP R 0:14:4f:fb:2c:60 is 172.24.0.8, aplica_prod
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    primary-vsw0 -> aplica_prod RARP R 0:14:4f:fb:2c:60 is 172.24.0.8, aplica_prod
    Zolder -> aplica_prod TFTP Error: access violation
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    Zolder -> aplica_prod TFTP Error: access violation
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    Zolder -> aplica_prod TFTP Error: access violation
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    Zolder -> aplica_prod TFTP Error: access violation
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    Zolder -> aplica_prod TFTP Error: access violation
    aplica_prod -> BROADCAST TFTP Read "AC180008" (octet)
    ----END CONSOLE 2----
    Once start the snoop to produce messages make a ping to the IP's that should be assigned in the host file and all give a succesful answer BUT without start the Solaris 10 Instalation
    # ping 172.24.0.8
    172.24.0.8 is alive
    # ping 172.24.0.9
    172.24.0.9 is alive
    # ping 172.24.0.10
    172.24.0.10 is alive
    I really need help with this trouble ..and any help or advice will be thrully appreciated
    Thanks
    PD: any other required configuration file will be provided if is needed

  • Solaris 10 Xorg dumps core

    Hello.
    I've installed Solaris 10 on an old x86 machine based around the AMD K6-2 CPU (~420 MHz), plus 3dfx Voodoo Banshee graphics card. Whether I run Xorg/Xserver or related utilities (such as xorgcfg and xorgconfig) from /usr/X11/bin, it eventually terminates with a message "Illegal Instruction - core dumped". Is this a hardware incompatibility problem I'm experiencing? Probably, any possible workarounds you could suggest to launch X and CDE on my machine?
    Thank you.

    Here the same behavior, unfortunately,
    AMD K6-2 CPU (450MHz), Solaris 10 10/08 (u6)
    SIGILL from /usr/X11/bin/xorgcfg (also from Xorg, scanpci, xorgconfig).
    SIGILL from xorgconfig occurs later after answered some questions.
    Also installing the currently latest patch 125720-32 does not solve this problem.
    It's a pity. The announced alliance sun - amd seams only to be a nice hype.
    Here it seams that special intel opcodes are delivered to us, thanx a lot!
    Have a nice day.

Maybe you are looking for

  • ITunes Match on a Synology Nas - many exclamation marks in the first row

    Hi, I transfared my entire iTunes Libary of roughly 26.000 Songs (1.000 plus bought on iTunes) to my Synology NAS.  Now when I start iTunes on my MacBook via WiFi it takes quite some time to be ready to play. Each time I open the Library on my NAS iT

  • OS 10.4.11 and HP Officejet 4500 compatibility issue (scanning)

    Hi there, I am having a compatibility issue with a G4 (OS 10.4.11) and a HP Officejet 4500 (all-in-one). (Sorry if this is a little long, but there are many specs and many attempts listed here). Problem: I cannot scan from the computer (upon opening

  • I can no longer access my itunes store account

    When I try to log into my itunes store account information, I keep getting this weird error message that says: We could not complete you iTunes store request. An unknown error has occurred (5002). There was an error in the itunes store. Please try ag

  • Calendar sync problem - eliminates events older than 2 weeks

    I sync my blackberry to my Mac using Blackberry Desktop manager.  It works fine except that it erases all events older than 2 weeks old......this is not what i want it to do.  I have adjusted the desktop manager to sync "all events" but it continues

  • Image Capture doesn't set time on digital camera

    Older versions of Mac OS X's Image Capture app had an option to synchronize the time on my camera with the computer's clock. Now I don't see this option anywhere any more. Was the feature dropped? I'm using a Canon PowerShot SD400.