> I then tried reinstalling aboot, as I thought that might be where the
> problem was hidden - but that didn't change a thing.
> Then I tried installing a noncompressed kernel image, as I found out that
> aboot (0.7 and 0.7a) aparently has some issues with compressed kernels
> where kernel version >= 2.2.16 .
Please forward whatever you find out to the list regarding aboot and
compressed kernels. I haven't experienced any problems on my two
machines, but that is certainly not a large enough sample size. If we
need to move to some other version of aboot to fix all these kernel
issues, that's not such a big thing.
> I will continue to try and build a kernel that will boot on this machine
> so we can fix this issue properly.
> At least we now know that compressed kernels can be a problem. Any clues
> about how to fix the ”failed to send Read” problem???
Not really. In fact, I'm going to have to plead ignorance on a lot of
Alpha kernel stuff. I'm neither an Alpha guru nor a great kernel hacker.
So it might be slow going. I think it's time for me to dig through
2.2.18pre changelogs and mailing lists.
> I'll keep looking for answers and solutions, but if you have any
> input/ideas then please let me know :-)
I had a few ideas in an email I just sent to Octave and cc:'ed to the
list. Check those out. Maybe one of them will work. Additionally, if
you can track down a Debian or SuSE config file (since their kernels
apparently work), try building one of those under Slackware and booting
it. If it runs, we need to diff them and figure out what's giving these
problems.
--
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