Re: [sisuite-users] How can I see the System Imager error message?

2010-08-04 Thread Patrick Nolan
Tristam MacDonald wrote:
> On Tue, Aug 3, 2010 at 3:56 PM, Patrick Nolan 
> mailto:patrick.no...@stanford.edu>> wrote:
> 
> I tried capturing the boot messages by echoing them out a serial port.
> (The AMI BIOS allows that.)  It works up to a point, but the output
> quits when the kernel boots.
> 
> 
> Did you also tell your *kernel* to output over the console? If my memory 
> serves correctly, you need to add something like console=ttyS0,57600 to 
> the APPEND line in your pxelinux.cfg/.
> 
Aha!  That did the trick.  I'm constantly learning new things.

Now I can get down to debugging.  The relevant messages are below.
This appears to confirm my suspicion that the kernel doesn't have the
necessary ethernet driver (igb for Intel 82576 controller) in place.
Is it necessary to compile a custom kernel, or can this be done by
configuration?  If the latter, is it an OSCAR configuration or a System
Imager configuration?

::  Boot messages:

--

Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
Intel(R) PRO/10GbE Network Driver - version 1.0.126-k2
Copyright (c) 1999-2006 Intel Corporation.
dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 
11/16/96 03:45:15
FW Version=$Version$
pcnet32.c:v1.33 27.Jun.2006 tsbog...@alpha.franken.de
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
sk98lin: driver has been replaced by the skge driver and is scheduled 
for removal
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
myri10ge: Version 1.3.0-1.233
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
winbond-840.c:v1.01-e (2.4 port) Sep-11-2006  Donald Becker 

   http://www.scyld.com/network/drivers.html
uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29)



init started:  BusyBox v1.1.1 (2007.12.06-11:09+) multi-call binary

switch_root_to_tmpfs

Loading tmpfs...
Didn't load -- assuming it's built into the kernel.

parse_tmpfs_opts

mount_proc

switching root to tmpfs...

mount_proc

mount_sys

mount_pts

get_arch

adjust_arch

ifconfig_loopback

load_my_modules

start_udevd
bin dev etc init lib lib64 linuxrc my_modules old_root proc root sbin 
sys tmp usr var Starting kernel event manager...
...done.
bin dev etc init lib lib64 linuxrc my_modules old_root proc root sbin 
sys tmp usr var Loading hardware drivers...
...done.

start_hotplug
bin dev etc init lib lib64 linuxrc my_modules old_root proc root sbin 
sys tmp usr var Starting hotplug subsystem...
...done.

variableize_kernel_append_parameters

read_kernel_append_parameters

read_local_cfg
skipping local.cfg: option SKIP_LOCAL_CFG=y has been specified

read_kernel_append_parameters

start_network
SIOCSIFADDR: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device


BusyBox v1.1.1 (2007.12.06-11:09+) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

sh: can't access tty; job control turned off
/my_modules #
I couldn't configure the network interface using your pre-boot settings:
DEVICE: eth0
IPADDR: 192.168.0.101
NETMASK: 255.255.255.0
BROADCAST: 192.168.0.255

Killing off running processes.

write_variables

This is the SystemImager autoinstall system

Your autoinstall has failed. You can use the shell prompt to try and see
what happened. You may be able to use the + keys to scroll
back and see the text that has passed off the top of the screen. You can use
+, , or  to work at an alternate shell prompt and preserve
your messages on the main screen, which is on +. Then go back and
re-read the documentation to see if your problem is described there.
You have read the documentation, right? :-)

If you absolutely cannot figure it out, visit the SystemImager support page
at http://systemimager.org. There you can search the email list archives,
ask your question on IRC, or even join a mailing list to ask your question.
There's a good chance someone else has experienced this very same issue and
can help answer your question. If you find the answer and it's not in the
documentation, or if you identify a bug, please submit a bug report at the
SystemImager support page.

Have fun! http://systemimager.org



/my_modules

--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.ne

Re: [sisuite-users] sisuite-users Digest, Vol 50, Issue 1

2010-08-04 Thread Chuck Ritter
> From: Patrick Nolan 
> Subject: Re: [sisuite-users] How can I see the System Imager error
>        message?
>
> Tristam MacDonald wrote:
>> Did you try shift+pageup to use the kernel's built-in scrolling capabilities?
>>
>
> Yes.  That's one of the things mentioned in the page of advice.  There
> doesn't seem to be a kernel running at that point.  Nothing gets any
> sort of response except the Reset button on the front panel.
>
What version of boel is installed on Oscar 5.1? Could new hardware be
crashing an old boel? Anyone know how to identify the version?

Maybe a way forward would be to test that boel will boot on a node
without crashing? Can systemimager cause the node to pxeboot boel
without running the autoinstall? Maybe then you can probe around and
discover the cause of the crash.

--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [sisuite-users] How can I see the System Imager error message?

2010-08-04 Thread Tristam MacDonald
On Tue, Aug 3, 2010 at 3:56 PM, Patrick Nolan wrote:

> Tristam MacDonald wrote:
> > Did you try shift+pageup to use the kernel's built-in scrolling
> capabilities?
>
> Yes.  That's one of the things mentioned in the page of advice.  There
> doesn't seem to be a kernel running at that point. Nothing gets any sort of
> response except the Reset button on the front panel.


There certainly is a full kernel running by the time that failure message is
printed, so it sounds like you have an actual hard crash on your hands.


> I tried capturing the boot messages by echoing them out a serial port.
> (The AMI BIOS allows that.)  It works up to a point, but the output
> quits when the kernel boots.
>

Did you also tell your *kernel* to output over the console? If my memory
serves correctly, you need to add something like console=ttyS0,57600 to the
APPEND line in your pxelinux.cfg/.

-- 
Tristam MacDonald
http://swiftcoder.wordpress.com/
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users