Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Feb 1996 02:23:09 +0500
From:      dbradt@ford.com (Dennis Bradt (R))
Message-ID:  <199602060719.AA14828@internet-mail.ford.com>

next in thread | raw e-mail | index | archive | help
Earlier this morning I was trying to compile a new kernel to allow for compatibility with linux and IBCS2. I followed the faq exactly. I placed into MYKERNEL 

options "COMPAT_LINUX"
options "COMPAT_IBCS2"
options LKM
options ATAPI

I then executed the following procedure

config MYKERNEL
cd ../../compile/MYKERNEL
make depend 
make all
When I did make all it got to

.<</../ufs/ufs/ufs_ihash.c 

and it said it did not know how to make it. I typed again 

make all

and it compiled 

../../ufs/ufs/ufs_ihash.c

{note: the two files and there paths are not typos but actually when was said the compiler} it went further into the compilation at which time it decided to reboot the system. fsck revealed all sorts of corruption and /dev/wd0a was now unrecognizable and will not boot at all.

What should be done in order to prevent this from happening next time? Is there a safe way to compile this Kernel without it blowing up? 

Also I need to know how I can get the system to recognize the cdrom which I have installed. I have tried everything except for successfully compiling the kernel. My cdrom is a soundblaster situated on a secondary IDE interface card. There is no setting on the card itself for making it a master rather than slave drive. The port at which it is located is 0x250. In order to give it this port address I gave the parameter at boot

boot: -c

and then I typed visual and inserted the port address into the matcd0 device. The cdrom is a 2x speed cdrom. 

When I was first installing I did the above and it looks like the kernel recognized the cd 

matushita/panasonic

but when it came to the install it said no such device existed and I had to eventually install it from a msdos partition.

please email with any info.

-Dennis Bradt 
 dbradt@pt8186.pto.ford.com

ps. The type of system I have is an AMD386 40MHz with  
floppy, hard disk controller and  2 serial, parallel, and game port on one card
a Western Digital Caviar 1.2Gig hard drive partition 300M dos and
           rest freebsd2.1
SoundBlaster 2x CD on IDE interface card
US Robotics 14.4 fax/voice/modem
TEAC floppy tape drive using 3010 cartridges
8M Ram using 3 chip simms 32 pins 70ns.

pss. I am not sure if the hardware is defective, possibly the motherboard, but I have changed the hard disk floppy controller at least two times because It looked like whenever I tried to change IRQ settings for the com devices, they do not take effect. I don't really want to change all my hardware if I don't have to. In windows3.1 the system still works despite the com irq settinqs on the controller assuming everthing else is configured correctly. 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602060719.AA14828>