On Sun, Nov 09, 2008 at 11:14:41PM +0100, Michael Schmitz wrote: > 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.
Christian handled the etch kernels. They are probably in 2-extra of <http://svn.debian.org/viewsvn/kernel/dists/etch/linux-2.6/debian/patches/series/> > The di kernels appear to have both SCSI and a warning-free IDE driver, so > what > am I doing wrong here? We have been in essense using the lenny installer to install etch-m68k for quite some time. The di kernels are 2.6.26 and I've been patching them per Geert's queue and your requests. > > 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? I'd like to focus on testing the sid/lenny installer, but perl is currently busted so we can't actually bootstrap sid or lenny. Any ideas there would be greatly appreciated. It sounds like vivaldi came back up successfully, so I'm going to update it and try to re-build perl when I get time. Other than that, I've no idea what I'm doing. ;) If you're game, feel free to point hobbes and perl and see if you can get it working. (It built fine, but perl-base dies horribly on installation.) Peace, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
