> Check your startup messages closely; do they say anything about your ramdisks
> being limitted to 0 bytes?
>
> I had a problem in that my /etc/lilo.conf had something like "ramsize = 0" (i
> forget the exact variable), as a "sanity check" as they put it. ARG! So
> maybe check your /etc/lilo.conf?
>
*That* might explain it! In the old days, a kernel with a
ramdisk that wasn't zero built in would take up whatever memory it was
built with... now of course that totally breaks the driver ;)
(Good thing I left that printout in after I made sure my sizing
changes worked...)
- Chad,
who ought to revise the documentation or something...