--On April 3, 2009 11:52:34 AM +0200 Alexander Vlasov
wrote:
Basically, U20 is supported and should work fine -- and it does, we have
lots of them.
You should probably boot solaris with -kdv flags and take a look at kmdb
output
Thanks. That's good to hear and what I thought should be the cas
--On April 3, 2009 9:16:35 AM -0400 James Carlson
wrote:
Yes. At boot time, edit the grub entry (with 'e'), select the kernel
entry, and edit (again, 'e') to add "-m milestone=none" (for instance).
Thanks very much for letting me know. I will try this next time it fails.
Since I need the c
The failsafe does not appear to understand the 'boot' command. I tried setting
the svcadm milestone -d none: svcadm Repository is read-only. Exiting. Init 6
and rebooting puts me back to the same problem. Can I edit grub to do this?
--
This message posted from opensolaris.org
___
OK. How does one go about doing that? (sorry)
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I am having lots of problems with my machine. Yesterday I had a crash (black
screen) and afterward it would load the nge0 interface in either BE (posted to
network). Unable to resolve this issue, I decided to do a clean install using
snv_110. Prior to doing this I sent my zpool to an external di
I had a bad crash (black screen) on snv_109 yesterday and it would not load the
nge0 interface (I've posted that on the network discussion list) afterward,
making the system non-usable as a workstation. This is an Ultra 20 (original)
with two internal drives.
Today I gave up and decided to do
