Hi,
> > Anyway, now that I have wised up to the fact that the etch install kernels
> > are
> > still at 2.6.18 (how backwards is that ...) I'm quite confident that all
> > that's
> > needed to fix the SCSI problems is my old 2.6.18 patch (back in 2.6.18, I
> > could
> > still fudge the SCSI midlevel timers). I seem to have done a version for
> > 2.6.21
> > but not 2.6.18 - will do that ASAP.
>
> There was an etch 2.6.24, but m68k never built it (or much of anything else
> for etch).
Tried to cross-build 2.6.18 as is currently in the archive (2.6.18.dfsg.1-12),
without much success. I assume you built the etch-m68k kernels from that
source? Do all the patches up to 12-extra get applied?
I noticed two problems, one of which must have happened while I tried to feed
my patches upstream:
m68k-atari-scsi.patch and m68k-atari-scsi2.patch were supposed to be applied on
top of each other instead of exclusive. m68k-atari-scsi2.patch fails to apply
in
this situation so Christian must have backed out the first one. Now the first
one is the one that unmarks the Atari SCSI driver as broken - backing it out
would result in the SCSI driver not getting built.
The other one is with the IDE code - from the 2.6.18.dfsg.1-12 source, I would
expect to get loads of ide_release_lock: bug messages, plus the IDE interrupt
handler is registered twice.
The di kernels appear to have both SCSI and a warning-free IDE driver, so what
am I doing wrong here?
> That's once of the reasons I want some form of lenny: etch, how old is that?
> ;)
>
> Maybe next week.
Should we focus on testing the sid installer then? Anything you would like me
to help with lenny?
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
