CMD IDE & waffle on graphics startup crap

Richard Mark Hemsley (rmh@Cs.Nott.AC.UK)
Fri, 28 Mar 97 19:04:01 GMT


I have a rather thick CMD 640 IDE card.
Compiling the kernel with CMD640 support is ok,
but if I stick the flag IDE..whatever... in the bootparams
it just gets to 'Buggy CMD640 interface on IDE....'
Kernel is 2.0.18.

Also, I just got a 2.5G Western Digital Caviar.
Some geezer was asking if over 2G works w/ linux.
It certainly does. LILO complains, but I'm using loadlin
on a diddy 10M partition so I can initialise my sound card.
fdisk does _not_ like the big drive. Don't worry, cfdisk
copes just fine.

This is related actually cos the reason I want my CMD
working is to get the PIO modes set on my drives.
My 1G & 2.5G both support PIO4 but don't get it.

I did an hdparm -T -t on the 2.5G and the drive transfer
time was a pedestrian 600K/s. The same as my old faithful
340M Maxtor.

Help appreciated.
Rik

++++++++++++++++++++++++ ignore past here for graphic boot debate

Yes the graphical boot thing is a stupid idea but yes
it would be something to think about if linux ever starts
becoming popular like windoze.. For now, forget it, what's the
point in hiding all the info that's kinda useful if your bootup fails
which is not uncommon when changing drivers, patching kernel whatever.

I'm in the process of writing a GUI for linux, like a mini X..
Personally I like the text & ALT-Fx-ing between terms, but there
are people who want an interface that is usable for their type of
applications, e.g. wordprocessing w/ wysiwyg.

If stuff like StarOffice starts being used seriously, then we may have
a home user operating system on our hands all of a sudden, and making
it accessible and friendly to the lay user will become important.
Until then, think what's more important- solidity or icing..

++++++++++++++++++++++++ end of spiel