> These are the exact problems that I've been running into with trying to
> make a generic kernel for slack. I have not had any luck with it as of
> yet. I hope we don't have to make box specific kernels for the install.
> That would suck.. but seeing how there are issues.. who knows. I have
> emailed the aboot people about the problems with the newer compressed
> kernels. Question... when you get a Kernel Oops.. is it right when an
> IDE device is detected... like a CDROM?
Perhaps there is a bug with the IDE detection code under 2.2.17? That
would not only affect machine with IDE devices, but those without as well.
I understand that a whole lot of work has gone into the 2.2.18pre kernels,
so maybe they have fixed some of these issues.
Try downloading the latest 2.2.18pre kernel and building that with the
generic .config file. If that doesn't work, then it's probably not an
issue with a specific kernel version. My next bet would be to try
removing support for IDE devices (if you can) and attempting to boot that.
If we have to make machine-specific kernels, that's not too bad a thing.
All I need is the proper directory structure under /kernels and a .config
file. We have scripts to automatically build all that stuff :)
--
Chris Lumens - chris@slackware.com - KG6CIH
@n=(-42,-85,-83,-19,65,2,-10,-10,-15,-3,2,-10,73,-4,8,-4,2,79,8,17,15,7,14,2);
print map{chr(-$n[$i++]+ord)} sort(split(//,'place random string here')),"\n";
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT