Mark Johnson wrote:
Kyle McDonald wrote:
Mark Johnson wrote:
Then, when you boot, you will be at the kmdb prompt. Do
the following
> moddebug?W 0x80000000
> :c
Then see what the last module to load was...
Last to 'load' was c2audit, but last to 'install' was sockfs.
Which seems to cancel out my bge theory.
I"m starting to wonder about the timing too. This serial connection
is only running aat 19200?
Have you tried to ping the machine to make sure it's
just not the console which is failing.. i.e. maybe the
machine boots up all the way..
I'm pretty sure it just the console connection that is failing. But no I
haven't been able to verify that. I'll try that next.
If solaris itself was totally crashing, wouldn't I see a panic?
Have you updated the console to run @ 19200?
svccfg -s console-login setprop ttymon/label = 19200
svcadm refresh console-login ; svcadm restart console-login
Yes, but not like that. The boot that is failing right now is the
JumpStart network boot. So there aren't any console-login properties to
set. However I do have this in the grub menu:
title Solaris NVb125 JumpStart
kernel$ /Sol/sNV/b125_X86/platform/i86pc/kernel/$ISADIR/unix -
install -B
console=ttyb,ttyb-mode='19200,8,n,1,-',install_config=172.30.171.30:/ex/Inst,sysid_config=172.30.171.30:/ex/Inst/SysID/Def,install_media=172.30.171.30:/ex/OSI/Sol/sNV/b125_X86
module$ /Sol/sNV/b125_X86/$ISADIR/x86.miniroot
So yes the console is configured for 19200.
The s10 Jumpstart is configured exactly the same and it works fine. Not
the same syntax, but the RHEL 4 and 5 kickstarts are all set to 19200,
and they work too.
There's something in Nevada that is different than s10 that is
triggering this, but I'm lost as to what it is.
-Kyle
MRJ
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
