Thank you Mary.

I didn't know 125 was available. Can I upgrade from 118 to 
25 using the same instructions you sent me yesterday?


     beadm create <be-name>
     beadm mount <be-name> /mnt
     pkg -R /mnt install entire at 0.5.11-0.122 
<------------- 0.5.11-0.125
     bootadm update-archive -R /mnt
     beadm umount <be-name>
     beadm activate <be-name>


mary ding wrote:
> Kostas:
> 
> If I ran into this, I will do the following:
> 
> In the grub menu, disable happy boot as follow:
> 
> The workaround is to remove the the following line:
> splashimage /boot/solaris.xpm  - need to use d
> foreground d25f00  - need to use d
> background 115d93" lines  - need to use d
> and ",console=graphics" in kernel$ line from the GRUB menu - need to use e
> 
> If it still hangs, then you need to boot kmdb and see which module cause 
> the hang:
> 
> On x86, in the GRUB item, type "e" (for edit) and
> then another "e" and then add "-k -d "    to the end of the kernel line
> or before the -B options.  Finally, press return to boot this entry.
> 
> This will cause the kernel debugger to load
> 
>          Loading kmdb...
> 
>          Welcome to kmdb
>          kmdb: unable to determine terminal type: assuming `vt100'
>          Loaded modules: [ unix krtld genunix ]
>          [0]>
> 
> At the prompt, enter "moddebug/W 0x80000000", <return> and then ":c",
> <return> which will then print out each module as it's being loaded.
> 
> 
> Instead of spending time on osol_122 which is out of date, I will also 
> pkg image-update to the latest available osol build and see whether the 
> issue still exist.  I had been using osol_125 on a couple of x86 laptops 
> and they work fine.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Kostas Oikonomou wrote:
>> Well, I chose snv122 from the GRUB menu and the machine started 
>> booting, but it is stuck in the blue screen with the orange slider, 
>> and it doesn't matter how many times I hit ESC.
>> It's frozen.  Ideas welcome.
>>
>> Juanita Heieck wrote:
>>> This happened to me when I did image-update recently.
>>> I hit esc and I had to enable /network/physical:nwam and
>>> reboot. Then I was able to get to the login prompt.
>>> Your issue might be different though.
>>>
>>> Nita
>>>
>>> Alan Coopersmith wrote:
>>>> Yes - the bar will continue until either an X server starts or the user
>>>> hits a key to drop to the text console.   If the text console has an 
>>>> error
>>>> message telling you what's wrong, it will sit there hidden behind 
>>>> the slider
>>>> bar until you hit a key to see it.
>>>>
>>>>     -Alan Coopersmith-           alan.coopersmith at sun.com
>>>>      Sun Microsystems, Inc. - X Window System Engineering
>>>>
>>>>
>>>> Kostas Oikonomou wrote:
>>>>  
>>>>> What I mean is that the machine sits there with the orange slider 
>>>>> going
>>>>> back and forth for more than 15 minutes.  That is not normal.
>>>>>
>>>>> Are you saying to hist ESC, even so?
>>>>>
>>>>>                 Kostas
>>>>>
>>>>> mary ding wrote:
>>>>>  
>>>>>> Kostas:
>>>>>>
>>>>>> It is not hang, osol using happy face boot. You can hit Esc to 
>>>>>> disable
>>>>>> happy face boot and you should see normal boot messages.
>>>>>>
>>>>>>
>>>>>> Kostas Oikonomou wrote:
>>>>>>    
>>>>>>> I finished the upgrade, but when the machine tries to boot 
>>>>>>> snv122, it
>>>>>>> hangs on the splash screen  (where the slider moves across the blue
>>>>>>> screen).
>>>>>>>
>>>>>>> This is strange, as I have an identical machine at home running
>>>>>>> snv122.  The only difference is that the machine that's hanging has
>>>>>>> 4GB of memory and a 500GB disk, whereas the home machine that works
>>>>>>> fine has 2GB memory and 320GB disk.
>>>>>>>
>>>>>>> Any ideas?
>>>>>>>
>>>>>>>             Kostas
>>>>>>>
>>>>>>> mary ding wrote:
>>>>>>>      
>>>>>>>> Kostas:
>>>>>>>>
>>>>>>>> According to the notes that I have, you can do this:
>>>>>>>>
>>>>>>>>
>>>>>>>>     beadm create <be-name>
>>>>>>>>     beadm mount <be-name> /mnt
>>>>>>>>     pkg -R /mnt install entire at 0.5.11-0.122
>>>>>>>>     bootadm update-archive -R /mnt
>>>>>>>>     beadm umount <be-name>
>>>>>>>>     beadm activate <be-name>
>>>>>>>>
>>>>>>>> but it only upgrades the bits from your opensolaris.org 
>>>>>>>> publisher, and
>>>>>>>> nothing from /extra, /contrib, etc.  You'll have to do those by 
>>>>>>>> hand.
>>>>>>>>
>>>>>>>>
>>>>>>>> Kostas Oikonomou wrote:
>>>>>>>>        
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I just received a new HP machine and replaced its Windows Vista
>>>>>>>>> with snv 118 from a DVD I had.
>>>>>>>>> Now I'd like to upgrade to a later release, but I know that snv 
>>>>>>>>> 124
>>>>>>>>> has some problems that to me are critical.
>>>>>>>>>
>>>>>>>>> So I would like to install snv 122.  But how do I do this? Can it
>>>>>>>>> be done with package manager?
>>>>>>>>>
>>>>>>>>> Thanks for your help.
>>>>>>>>>
>>>>>>>>>             Kostas
>>>>>>>>> _______________________________________________
>>>>>>>>> install-discuss mailing list
>>>>>>>>> install-discuss at opensolaris.org
>>>>>>>>> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>>>>>>>>>             
>>>>> _______________________________________________
>>>>> install-discuss mailing list
>>>>> install-discuss at opensolaris.org
>>>>> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>>>>>     
>>>>
>>>>
>>>> _______________________________________________
>>>> install-discuss mailing list
>>>> install-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>>>>   
>>>
> 

Reply via email to