Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-mips@linux-mips.org
Subject: Re: O2 and 128Mb
Date: Fri, 21 Jan 2005 21:46:54 -0500	[thread overview]
Message-ID: <41F1BE9E.8070109@gentoo.org> (raw)
In-Reply-To: <1106342715.4757.27.camel@localhost>

Giuseppe Sacco wrote:
> 
> I think my O2 just blowed up :-(
> Actually it doesn't switch on. Even unplugging and plugging again the
> power cord, it stay off.

Pull the mainboard out, find the flash-clear jumper, cover it with a nearby 
jumper cap (this jumper and cap should be near the RTC, a Dallas chip).  Pop 
the board back into the system, and see if it powers on.  If it does, power 
back off, remove the jumper cap, and then power back up, and it should power 
up fine.

If nothing happens, you probably cooked the power supply.  O2's are apparently 
  known for blowing power supplies, though.  Replacements can be easily found 
on eBay.


> Fortunately, I have a second machine that I may use for tests, while
> I'll find the problem with the first one. The second machine is the same
> model of the first one. I just swapped disks and cable and made your
> test: nothing changed.

Drop minicom, I get nothing but trouble with it.  Use "xc", a small, simple 
dial program.  If it's not on your system, you'll have to install it via 
whatever means your working distro provides, then do this:

xc -l/dev/ttyS0

 > set bps <O2 baud rate>
 > t

After typing 't' and pressing enter, you'll be dropped to terminal mode.  Try 
powering on the O2 at this point, and see if you get any output.  If not, you 
may have the O2 rigged to still boot the graphical console.  To fix this, you 
will need to hook up a monitor, mouse, and keyboard, get into the PROM, and:

 > setenv console d1
 > setenv dbaud <desired baud rate>

Then poweroff, and remove the keyboard, mouse, and monitor (if the O2 PROM 
detects these as being attached, it may still boot graphical), and try to 
reboot again to see if you get anything on xc's terminal.

To boot the kernel, make sure you pass "console=ttyS0,<baud rate>" to it, 
cause for me, w/o it, the kernel will sometimes not pick up the serial port, 
and thus you won't see any output (but the kernel will still boot (or attempt 
to)).

If all else fails, replace the serial cable.  Sometimes they just don't work 
for whatever reason.


> Actually it is still blocked there: blinking the red led, while showing
> the "Starting 32-bit kernel" on the screen. How do I reset an O2?

The flashing red LED is implying the kernel booted, then paniced suddenly. 
Until you get the console working in whatever fashion, you won't know why.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: small 
hands do them because they must, while the eyes of the great are elsewhere." 
--Elrond

  reply	other threads:[~2005-01-22  2:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  7:42 O2 and 128Mb Giuseppe Sacco
2005-01-13  7:49 ` Ilya A. Volynets-Evenbakh
2005-01-13  8:34   ` Giuseppe Sacco
2005-01-13 19:26     ` Ilya A. Volynets-Evenbakh
2005-01-21 20:19       ` Giuseppe Sacco
2005-01-21 20:40         ` Ilya A. Volynets-Evenbakh
2005-01-21 21:25           ` Giuseppe Sacco
2005-01-22  2:46             ` Kumba [this message]
2005-01-22  8:21               ` Geert Uytterhoeven
2005-01-22 11:47                 ` Ulrich Teichert
2005-01-22 16:31                   ` Thiemo Seufer
2005-01-22 19:46               ` Giuseppe Sacco
2005-01-22 11:03             ` Kaj-Michael Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41F1BE9E.8070109@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=giuseppe@eppesuigoccas.homedns.org \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox