[osol-discuss] Build 134 won't boot after an update from 133

2010-03-25 Thread Christian Pélissier
After an update from build 133 (BE opensolaris-2) my Dell D630 laptop boot to build 134 when I do pfexec init 6 from the build 133 BE (no BIOS transition in this case) and build 134 works well. After a poweroff, booting from Grub the 134 build (opensolaris-3) display the blue OpenSolaris

Re: [osol-discuss] Build 134 won't boot after an update from 133

2010-03-25 Thread Alan Coopersmith
Christian Pélissier wrote: After an update from build 133 (BE opensolaris-2) my Dell D630 laptop boot to build 134 when I do pfexec init 6 from the build 133 BE (no BIOS transition in this case) and build 134 works well. After a poweroff, booting from Grub the 134 build (opensolaris-3)

Re: [osol-discuss] Build 134 won't boot after an update from 133

2010-03-25 Thread Luca Ferrari
On Thursday 25 March 2010 02:24:47 pm Christian Pélissier's cat walking on the keyboard wrote: After an update from build 133 (BE opensolaris-2) my Dell D630 laptop boot to build 134 when I do pfexec init 6 from the build 133 BE (no BIOS transition in this case) and build 134 works well.

Re: [osol-discuss] Build 134 won't boot after an update from 133

2010-03-25 Thread Christian Pélissier
Thanks for your help. Some feedback. First pfexec init 6 from 133 was booting 134 because in this case the boot was in text mode. So removing ,console=graphics is the solution I do the following in /rpool/boot/grub/menu.lst ... #splashimage /boot/solaris.xpm #kernel$

Re: [osol-discuss] Build 134 Won't boot

2010-03-10 Thread alan pae
Apparently this is a known bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6932552 alan -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Build 134 Won't boot

2010-03-10 Thread Bob Palowoda
Apparently this is a known bug: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bu g_id=6932552 alan Wow a lot of people are hitting this bug. Hopefully it's marked as a stopper. ---Bob -- This message posted from opensolaris.org ___

Re: [osol-discuss] Build 134 Won't boot

2010-03-10 Thread Enrico Perla
Yes, it is exactly that bug. I'm going to fix it by moving the progressbar_start() call (which leads down to the call to cv_reltimedwait()) after callout_init() has been called. The fix will be integrated soon. - Enrico -- This message posted from opensolaris.org

[osol-discuss] Build 134 Won't boot

2010-03-09 Thread alan pae
This post will mimic http://opensolaris.org/jive/thread.jspa?threadID=125445tstart=0 Instead of booting a Live CD I already have the 64-bit version of build 133 loaded so I used pfexec pkg image-update --be-name name and let it do it's thing. Usually there is about a twenty minute wait from

Re: [osol-discuss] Build 134 Won't boot

2010-03-09 Thread alan pae
After removing the 133 boot environment then the system went back to the non booting again. So I had to modify menu.lst again and set console=text and then all was well. alan Message was edited by: alan_pae -- This message posted from opensolaris.org

Re: [osol-discuss] Build 134 Won't boot

2010-03-09 Thread Paul Gress
On 03/ 9/10 08:50 PM, alan pae wrote: After removing the 133 boot environment then the system went back to the non booting again. So I had to modify menu.lst again and set console=text and then all was well. Saved me tonight. I had just upgraded from b133 to b134 and also was getting