Hi Kevin

The 2GB is small if I want X. It is however only running the CLI. I did
indeed start with the standard minimal install and aded a few packages
from there. Biggest problem was recompiling a kernel. During module
install they exist in two places. I had to prune a few things before the
install but afterwards a make clean got me back a lot of space.

I had a further look at the 2.6 issue. Quite a few Ubuntu users seem to
have had trouble with it. Even to the point of "I upgraded my kernel to
2.6.x and it no longer boots". The 5513 kernel driver not only covers
their older products but the current stream as well. Apparently the
5513 as it was back 10 years ago is still used in one of the bridge
chips even to the point of having then same PCI ID. I had a brief look
at the 5513 kernel source code but found no obvious "we have disabled"
comments.

I tried a kernel 2.4 install and it worked fine. This partly infers it
may be a kernel problem.

Whatever the case I have now given up on it and put DSL on it for sale
at a local non profit store. Have to expose Linux to as mamy people as
possible!

All your other comments noted, thanks. I shd point out however that the
disk works fine in the PIII/500 box with piix. When plugged into the
older box it deosnt succsufully probe the 5513 like the 2.4 kernel
does.. More proof it is kernel related.. I cant actually install the 9.3
software on the older box as it has no boot CD capability and the 9.3
floppies send it into screen rolls...

Thanks for your input

Cheers Bob (Australian in East Texas)

Kevin Nathan wrote:
> /boot is the only one that you need to have with the first 1024
> cylinders. Once GRUB has loaded the kernel, the kernel takes over the
> drive detection.