Rich Reynolds writes:
I had a similar problem on different hardware, and found that hand
plumbing the interface and re-enable nwam served as a sufficient work
around...
svcadm clear nwam is the simpler work-around.
The real problem here isn't nwam, but the device subsystem, which
no it was clear the problem was not nwam, but its maintainance state,
was a good indicator as to the real problem...
and as with many problems, a bigger hammer usually helps...
thanx,
rich
James Carlson wrote:
Rich Reynolds writes:
I had a similar problem on different hardware, and found
Folks;
trying to boot (or even install) a recent OpenSolaris build (off
genunix.org) on an x4150 machine, but so far failed in a rather simple way:
Booting up the machine using the live medium works well, but in the end, a
text based console is all I eventually get on this machine, also no
On Mon, Feb 16, 2009 at 1:24 PM, Kristian Rink kaw...@zimmer428.net wrote:
Folks;
trying to boot (or even install) a recent OpenSolaris build (off
genunix.org) on an x4150 machine, but so far failed in a rather simple way:
Booting up the machine using the live medium works well, but in the
Hi Martin;
and first off thanks a bunch for your hint.
Martin Bochnig schrieb:
[...]
Hello, as far as I know Indiana still lacks a text/console mode installer.
However, in case your box has whatever graphics card you can simply
use the vesa driver (as replacement for a native driver, which
Hello,
this is known P2 bug, see
http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
Actually nwam fails and machin doesn't boots up into normal state.
Kristian Rink wrote:
Folks;
trying to boot (or even install) a recent OpenSolaris build (off
genunix.org) on an x4150 machine, but so
Hi all -
I had a similar problem on different hardware, and found that hand
plumbing the interface and re-enable nwam served as a sufficient work
around...
hth,
rich
Alexander Vlasov wrote:
Hello,
this is known P2 bug, see
http://defect.opensolaris.org/bz/show_bug.cgi?id=6331
Actually