> The serial cable has pin 2 connected to pin 3 on the
> other
> end (and vice versa); i.e. is it a null modem cable?
Ok I think it might actually be a straight through cable, I'll grab a null
modem cable or an adapter when I next get the chance and see what happens.
--
This message posted from
> Btw should I be pressing "Call" or
> "Wait for call" in Hyperterminal? I tried both
> methods either way.
I defined a new connection in hyperterminal on my laptop,
using the com1 serial port on the laptop.
"Call" in hyperterminal works for me.
When I start Solaris with "-B console=ttya -kv",
> Ok I tried that but couldn't get anything to show up
> in Hyperterminal. Tried a number of different entries
> in the grub file from searching other forum posts,
> but still nothing. Hypterminal would say "connected"
> but would only display a constant flashing cursor,
> nothing else.
The serial
> Set it to 9600 baud, 8 bit, no parity (9600,8n1).
>
> Boot the Solaris box, and edit the grub menu entry;
> add "-B console=ttya" at the end of the kernel$
> line.
> When you boot the modified entry, the kernel loads
> and should use the console on ttya (com0).
>
> X should start on the vga ada
> > The A8n-SLI deluxe seems to have a 9-pin
> > serial port header, on the mainboard.
> > (see page 2-24 in the A8N-SLI deluxe manual)
> >
> > You need a special cable to get the standard
> > DB9 connector from the onboard serial port
> > connector.
>
> You're completely right, I forgot about th
> The A8n-SLI deluxe seems to have a 9-pin
> serial port header, on the mainboard.
> (see page 2-24 in the A8N-SLI deluxe manual)
>
> You need a special cable to get the standard
> DB9 connector from the onboard serial port
> connector.
You're completely right, I forgot about that. I've dug aroun
> > Does that system have an isa legacy serial port?
> >
> > Could you retry the uadmin 3 22 on the console,
> > when the console is redirected to the serial port?
>
> No the system does not have a serial port.
The A8n-SLI deluxe seems to have a 9-pin
serial port header, on the mainboard.
(see p
> Does that system have an isa legacy serial port?
>
> Could you retry the uadmin 3 22 on the console,
> when the console is redirected to the serial port?
No the system does not have a serial port.
> Without a serial port console, you could try the
> uadmin 3 22 from the ascii text console. Bu
> Ok I just tried that script (without the pm_debug
> line, it seemed to cause mdb to complain about an
> unknown symbol name)
Yep, pm_debug is available with a
debug kernel only.
> but had the exact same result
> when executed . System tries to suspend, display
> turns off etc., had to reset t
Ok I just tried that script (without the pm_debug line, it seemed to cause mdb
to complain about an unknown symbol name) but had the exact same result when
executed . System tries to suspend, display turns off etc., had to reset to
bring it back up. Nothing new in /var/adm/messages, just the sam
> Actually, that command checks whether the driver implements quiesce()
Yep.
> which is needed to suspend and resume as well as fast reboot
quiesce() is needed for fast reboot. suspend / resume uses the
attach(DDI_RESUME) / detach(DDI_SUSPEND) driver entry points.
A driver might share code bet
i stand corrected, i dont know why i thought it was required, i just
checked quiesce(9E) and it only talks about fast reboot
2009/7/15 John Martin :
> Ignacio Marambio Catán wrote:
>>
>> Actually, that command checks whether the driver implements quiesce()
>> which is needed to suspend and resume
Ignacio Marambio Catán wrote:
Actually, that command checks whether the driver implements quiesce()
which is needed to suspend and resume as well as fast reboot,
quiesce() has nothing to do with S3 suspend/resume.
A driver can support S3 s/r without implementing quiesce().
Actually, that command checks whether the driver implements quiesce()
which is needed to suspend and resume as well as fast reboot, it
should tell you what drivers have problems,
uadmin 3 22 worked in my laptop but suspend and resume didn't
the problem was in masa's bfe driver which i no longer use
Ignacio Marambio Catán wrote:
> On Wed, Jul 15, 2009 at 10:12 AM, Gordon wrote:
> > I'm running svn_111b and my system will not enter suspend mode.
> try reboot -f dryrun
> after that check dmesg, that should tell you what driver has problems
Nope, that reboot command tests if the system is
able
try reboot -f dryrun
after that check dmesg, that should tell you what driver has problems
On Wed, Jul 15, 2009 at 10:12 AM, Gordon wrote:
> I'm running svn_111b and my system will not enter suspend mode. Mobo is an
> ASUS A8N-SLI Deluxe, CPU is an AMD Athlon 64 and the video card is a GeForce
>
I'm running svn_111b and my system will not enter suspend mode. Mobo is an ASUS
A8N-SLI Deluxe, CPU is an AMD Athlon 64 and the video card is a GeForce 6600GT.
When I press Suspend, the video display turns off and I think I can hear
atleast one hard drive go into standby, but the system still st
17 matches
Mail list logo
