Last night I wanted to test the CD for installing College Linux I made . The first thing you are asked is to configure the Keyboard. Last night I did this no problem . It was late so I quit the install. Now I am getting to the Keyboard selection and I get no response when I hit enter. My key board does work when the CD is started and I choose to install College Linux.

It is a standard Microsoft natural PS 2 keyboard made by Dell.

have a try using a different key map.... you can change the keymap when the system has installed...

that is a good suggestion but I can't. It just does not work. I don't F'ing get it, works fine when I hit enter to begin the process. Then nothing...I even made sure that the number lock key is lit. After the installer runs it goes blank.

... this is an annoying one...

if possible try a different keybord...
reed up on what 'kernel options' you can pass at boot, there should be one to probe hardware et all... (it may not make a difference but it may)

i dont understand how it worked one night and not the next tho... frustrating....

hang in there, if alll else fails. try a different version/distro

it funny you should mention another distrabution. I have two...I tried College Linux first last night got past the keyboard selection then quit. I wanted to test the other(skolelinux) that I made so I put it in and that was the first time all this happened. Lst night I thought who cares because College Linux is the one I like the best and the CD works. But I quit when keyboard did not respond.

This is off the subject(WinXP) but I was looking through the boot options and saw that "Video DAC Snoop" is disabled. Anyone know what this is? Sounds Creepy.

any luck passing random messages to the kernel...?

aslo.. if you want a good starting distrobution try mandrake... its big and slow, but it works.... or fedora core 2.... less big and slow... but also works... IMHO


as to your aside.. DAC stands for Digital Analougue Converter/tion.. so its probably not THAT sinister.....
cource i could be wrong... and they could be watching you right now ! ! :P

You said that you quit in the middle of the install. Since you haven't done anything with it yet, why not just wipe out the drive and do the install again from the start?

Because I have to keep WinXP in my stable. that does bring up a question I wanted to ask earlier,
What if I create a partition using Windows? Install the Linux on the unused partition.

I don't have the info infront of me but NTFS is not recommended, right? 1 partition about 128 mb and another for the actuall Linux OS. I will start downloading Mandrake now. Thank you for the suggestion.

theres nothign wrong with using windows to set up the partision, just dont write any file system to it, or linux will just have to over-write it anyway, use fdisk or partision majic (costs money ) to set up the linux partision from windows

linux cant (easily) write to NTFS as microsoft wont tell us how!... (its also a bit slow and generally poo)

in summery... yea, partision using windows, then install linux on the partision.

FAT32?

*HEY I GOT Morphix on my pc...now I can say a distro was installed on my pc*

Anyway...I made another CD of College Linux, just in case. So, I will now try this with a fresh partition and a fresh CD. What about the 3rd partition am I correct about this; swap partition? 128 MB?

a good idea is to have twicwe as much swop as ram... (unless you have millions of ram, ive got 512, i dont think ive swopped yet... but better safe then sorry i supose

It would probably be best to remove the empty partition, where you want to install linux, and let the installer format the unused drive space. You may also want to reserve some space for an extra fat32 partition that both linux and window can write to.

Usually, linux partitions will be either ext3 or reiserfs. There are other types also, but these are the two most common linux filesystems. Do not use NTFS or fat32 for installing linux. Linux doesn't write to NTFS and the fat32 doesn't save the attributes you will need to run linux such as UID, GID, access times, etc.