On Mon, 13 Nov 2006 22:17:17 -0500
"Stephen M. Rumble" <stephen.rumble@utoronto.ca> wrote:

> Quoting George Harvey <fr30@dial.pipex.com>:
> 
> > I'm trying to install 3.1 on a Challenge S (IP2x) but unfortunately
> > the SCSI probe fails when talking to my IBM DNES-309170 disk. I'm
> > aware that this is a known problem with some drives and that it has
> > recently been fixed (Ben Harris's message on this list on 24th
> > Sept.). I guess the fixes came too late for 3.1 but would it be
> > possible for me to back-port them into a custom kernel for my
> > system, and if so, which files do I need? I have successfully
> > installed 3.1 on an O2 so can use that to build a kernel for my
> > Challenge S.
> 
> It would probably be easier to just build a -current kernel and  
> install it on the 3.1 system.

I tried that and it's not so simple, 'config' fails right away with
syntax errors in some of the files. There was a message in another
thread (possibly another platform) that said you needed an updated
toolchain in order to build a current kernel. However, I've realised
that -current is indeed the way to go, I'll need it to support my G130
Ethernet card as well. (note for Steve, I've replaced the Set
Engineering 100Mb card with a G130 since I ran your test kernels in
September)

> At the very least, I'd recommend booting a -current kernel just to be 
>  sure that the wd33c93 changes actually allow your drive to be
>  properly detected.

I tried the test kernel mentioned in Ben's message and that booted OK.

Tonight I tried the install kernel from the NetBSD-4 daily build but
that still fails with SCSI errors. Next I tried an install kernel from
the HEAD daily build but that wouldn't unzip, gzip says it isn't a gzip
file :(

For my next attempt, I think I'll try updating my O2 from the NetBSD-4
daily build. That will hopefully give me a toolchain which can compile a
-current kernel for the Challenge S.

Regards,
George