Subject: RE: Re: RAQ2 boot problem
To: None <port-cobalt@netbsd.org>
From: None <paulmac2@aol.com>
List: port-cobalt
Date: 09/05/2005 09:29:32
----------MailBlocks_8C78034FC0C9AFC_4CC_82DB_mblk-d33.sysops.aol.com
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
>> --- Urspr=FCngliche Nachricht ---
>> Von: paulmac2@aol.com
>> An: port-cobalt@netbsd.org
>> Betreff: RAQ2 boot problem
>> Datum: Sun, 04 Sep 2005 16:10:22 -0400
>>=20
>> Finally getting around to installing NetBSD 2.0.2 on my RAQ2 using the
>> method
>> suggested 7/26 by Andy from this list, but feeling very frustrated at the
>> moment.
>> =20
>> I am using Tsutsui-san's NetBSD/cobalt bootloader 2.0G (20040902) to get
>> around
>> the max kernel size problem. As it starts loading the kernel all seems
>> well until it
>> waits for the SCSI bus devices to settle, and then...
>> =20
>> Kernelized RAIDframe activated
>> scsibus0: waiting 2 seconds for devices to settle...
>> wd0 at atabus0 drive 0INTRF
>> panic: siop_intr: I shouldn't be there !
>> Stopped at netbsd:cpu_Debugger+0x4: jr ra
>> bdslot: nop
>> =20
>Hi paul.
>
>That's funny - but i had this prob with the original Restore CD.
>Then i upgraded the nfsroot (packages that will be installed)=20
>to Current (somewhere in May, June..) and it worked.=20
>That's why i made a more current version of the cd.
>
>May i ask a question. Does the kernel panic when trying to install
>the raq (netbooting from the restore cd) or after a successful=20
>install on the first "normal" boot?
This is a RAQ2 that already has 1.6 running on it. I had planned to build
a 2.0.2 system on it by first booting the new kernel with rc_configured=3DNO=
,
mounting the other filesystems, then untarring the new sets over them. I
tested this in advance on another platform (NetBSD/vax) and it worked fine.
By doing it that way instead of using the Restore CD I thought I could keep
the filesystems and data intact instead of starting from scratch.
--
:p.
----------MailBlocks_8C78034FC0C9AFC_4CC_82DB_mblk-d33.sysops.aol.com
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><BODY><DIV style=3D'font-family: "Verdana"; font-size: 10pt;'><DIV>>=
;> --- Urspr=FCngliche Nachricht ---<BR>>> Von: <A href=3D"mailto:p=
aulmac2@aol.com">paulmac2@aol.com</A><BR>>> An: <A href=3D"mailto:port=
-cobalt@netbsd.org">port-cobalt@netbsd.org</A><BR>>> Betreff: RAQ2 boo=
t problem<BR>>> Datum: Sun, 04 Sep 2005 16:10:22 -0400<BR>>> <BR=
>>> Finally getting around to installing NetBSD 2.0.2 on my RAQ2 using=
the<BR>>> method<BR>>> suggested 7/26 by Andy from this list, b=
ut feeling very frustrated at the<BR>>> moment.<BR>>> <BR>=
>> I am using Tsutsui-san's NetBSD/cobalt bootloader 2.0G (20040902) t=
o get<BR>>> around<BR>>> the max kernel size problem. As i=
t starts loading the kernel all seems<BR>>> well until it<BR>>>=20=
waits for the SCSI bus devices to settle, and then...<BR>>> <BR>=
>> Kernelized RAIDframe activated<BR>>> scsibus0: waiting 2 seco=
nds for devices to settle...<BR>>> wd0 at atabus0 drive 0INTRF<BR>>=
> panic: siop_intr: I shouldn't be there !<BR>>> Stopped at netbsd:=
cpu_Debugger+0x4: jr ra<BR>>> bdslot: nop<BR>>> <BR>>Hi=
paul.<BR>><BR>>That's funny - but i had this prob with the original R=
estore CD.<BR>>Then i upgraded the nfsroot (packages that will be install=
ed) <BR>>to Current (somewhere in May, June..) and it worked. <BR>>Tha=
t's why i made a more current version of the cd.<BR>><BR>>May i ask a=20=
question. Does the kernel panic when trying to install<BR>>the raq (netbo=
oting from the restore cd) or after a successful <BR>>install on the firs=
t "normal" boot?<BR></DIV>
<DIV>This is a RAQ2 that already has 1.6 running on it. I had planned=20=
to build</DIV>
<DIV>a 2.0.2 system on it by first booting the new kernel with rc_configured=
=3DNO,</DIV>
<DIV>mounting the other filesystems, then untarring the new sets over them.&=
nbsp; I</DIV>
<DIV>tested this in advance on another platform (NetBSD/vax) and it worked f=
ine.</DIV>
<DIV>By doing it that way instead of using the Restore CD I thought I could=20=
keep</DIV>
<DIV>the filesystems and data intact instead of starting from scratch.<=
BR>--</DIV>
<DIV>:p.</DIV></DIV></BODY></HTML>
----------MailBlocks_8C78034FC0C9AFC_4CC_82DB_mblk-d33.sysops.aol.com--