From: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
To: linux-mips@linux-mips.org
Subject: Re: O2 and 128Mb
Date: Fri, 21 Jan 2005 21:19:35 +0100 [thread overview]
Message-ID: <1106338775.4760.17.camel@localhost> (raw)
In-Reply-To: <41E6CB5B.6080303@total-knowledge.com>
Il giorno gio, 13-01-2005 alle 11:26 -0800, Ilya A. Volynets-Evenbakh ha
scritto:
> Please set up serial console, and find out where kernel crashes.
> It is pretty obvious that happens before gbefb is initialized, but
> after ip32-reset is setup (which sets up timer to blink the LED),
> thus should be able to give you some output on serial port.
Sorry for being late,
I tried: I found a laptop equipped with serial port, plugged a nullmodem
serial cable on the laptop serial port and on the serial port labeled "1"
of the O2 machine. I started minicom on the laptop and selected ttyS0, 9600,
8bit, noparity, 1 stop bit.
Then changed in /etc/arcboot.conf, my append line from
append="root=/dev/sda1" to
append="root=/dev/sda1 console=ttyS0,9600n8 console=tty0"
shutdown the O2, unplugged power cable, waited, plugged, swithed on.
Then I changed the OSLoadFilename correctly, and typed "boot".
During the supposed boot, minicom doesn't display *any* character. It
just change the online label from "00:00" to "00:01". Nothing more,
Then, as already explained, the red led on the SGI O2 starts blinking.
I then tried the same "append" line with my working kernel and it worked
as expected: writing to both the serial console and the O2 screen.
How may I better debug the problem? Anyone have a working kernel or,
maybe, a newer arcboot?
Thanks,
Giuseppe
Il giorno gio, 13-01-2005 alle 11:26 -0800, Ilya A. Volynets-Evenbakh ha
scritto:
> Please set up serial console, and find out where kernel crashes.
> It is pretty obvious that happens before gbefb is initialized, but
> after ip32-reset is setup (which sets up timer to blink the LED),
> thus should be able to give you some output on serial port.
>
> Oh, and what does it have to do with fact you have 128M of RAM?
> Giuseppe Sacco wrote:
>
> >Il giorno mer, 12-01-2005 alle 23:49 -0800, Ilya A. Volynets-Evenbakh ha
> >scritto:
> >
> >
> >>"Cannot boot" is not very good describtion of the problem.
> >>
> >>
> >>
> >
> >You are right.
> >Arcboot is Debian version 0.3.8.4. I select the stanza arcboot should
> >use, with 'setenv OSLoadFilename <stanza>" and the kernel is loaded.
> >Then it s ran and the only change I see is the red led blinking. The
> >screen messages are:
> >
> >Loading program segment 1 at 0x80004000, offset=0x4000, size = 0x3df086
> >Zeroing memory at 0x803e3086, size = 0x2bf9a
> >Starting 32-bit kernel
> >
> >Bye,
> >Giuseppe
> >
> >
> >
> >
>
next prev parent reply other threads:[~2005-01-21 20:22 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 [this message]
2005-01-21 20:40 ` Ilya A. Volynets-Evenbakh
2005-01-21 21:25 ` Giuseppe Sacco
2005-01-22 2:46 ` Kumba
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=1106338775.4760.17.camel@localhost \
--to=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