Also, when running 2.0.31 (without any patches...) I got the following
error:
Nov 14 23:18:12 unixcorn kernel: Inode i_mmap ring corrupted
The message repeated 50 or so times during the copying of a large (100 meg
or so) file before I shutdown to single user mode and e2fsck'd the system.
In that case e2fsck did ask if I wanted to fix the summary information,
but it didn't list what was wrong when it did its passes.
Is this a known problem with 2.0.31? (I remember that there were some, I
just don't recall what they were... :/)
One final thing:
I like to run my console at 132x44. When I boot to 2.1.64 it doesn't
recognize vga=8 as a valid mode. It doesn't list 132x44 at all. When I
run 'scan' however it does, and lists it as mode 'b'. When I tried to
edit lilo to specify mode 'b' it wouldn't accept it claiming that it was
not a numeric value. Obviously it isn't, but how can I specify this mode
for boot up? (Unless I do 'scan' it won't accept 'b' as a valid mode even
when vga=ask.) I dual boot my machine so it would be helpful to have
a way to force it to take the 132x44 without me having to specify every
time. :)
My system: Dual Pentium Classic 166mhz processors, 430HX ASUS P65UP5
motherboard, 4MB ATI Expert@play graphics card.
Thanks for your help,
Peter McLachlan
My beautiful! my beautiful!
That standest meekly by
With thy proudly arched and glossy neck,
And dark and fiery eye;
"An Arab's Farewell to his Steed"-Caroline Norton