Successful Debian install on 1GB CF

Chris Knadle <[email protected]> Tue, 9 Sep 2003 15:22:04 -0400
Newsgroups gmane.comp.hardware.openbrick.general
Organization Aeroflex
Message-ID <[email protected]>
Greetings.

   I'm pleased to report that I've been able to do an installation of Debian 
Woody (Stable) on a 1GB Lexar CF card.

Card used:  	
Lexar Media CF1GB-32-380 1GB CF Pro Series 32x Write Acceleration

Note that this is a 3.3v CF card, so it requires a jumper setting change, and 
it is also probably not suitable to run as a slave simultaneously with a hard 
drive because of the voltage used.  I briefly used this card in the 5V 
setting (accidentily) and the card seems to have survived the event, but I 
would not recommend using that mode.

Also:
   I did not use the new-debian.tgz installation file for the install.  
Instead I did a two-step Debian Woody (Stable) install.  First I installed 
Debian Woody to a partion on a hard disk on a laptop.  (Was required in this 
case: Debian will not load PCMCIA drivers until after the / partition is 
mounted, and then it's too late.)
   After the Debian install, I booted my laptop to a Knoppix live CD, and made 
partitions + ext2 filesystems onto the CF card, and did a recursive copy of 
all of the files of the Debian installation onto the card after mounting it.  
(I've been using this trick for a while.)

   In addition, I experimented with booting the OpenBrick-E to an IDE cd-rom 
on connected on the 40-pin IDE port using an external AT power supply, and 
was able to boot the Knoppix live cd.  The graphical desktop, sound, and 
networking all worked !  Pretty cool.  That means with an OpenBrick and a USB 
CD-ROM you've got an instant thin client with no hard drive.

   There are a bunch of details that I need to document and make available on 
the procedure.  When I have them I will post a link here, as well as post the 
details of how I did it right here if it is desired.



   If anyone has questions concerning the above, please feel free to ask them.

	- Chris

-- 
Chris Knadle
[email protected]