problems compiling a kernel: from a newbie
Dear list: I'm sure I'm doing something wrong, but don't know what it is or how to solve it. I've gotten to the make dep part of making a kernel kernel and several dependencies seem unfulfilled. In particular it cannot find stddef.h (which seems to be sitting in /usr/include/linux) and a file called stdarg.h which seems to be buried away in /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include) and it complains that it cannot find the file limits.h which is included in limits.h This all started when I upgraded to redhat 8.0 (or tried to). The installer said we recommend you change to an ext3 filesystem, but it seemed to forget to include ext3 support in the kernel with the install. So.. none of the filesystems want to mount. I have booted using Tomsrtbt, mounted the filesystems appropriately, chroot, and I'm trying to build kernel 2.4.20 to get around this problem. thanks, Darren --------- Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: weird hard drive failure
Hi Darren, although I'm inclined to say that the settings you used CANNOT harm the hardware, this is too much of a coincidence. Hi Edward. I didn't think it could harm the hardware either. They were running ok beforehand. weird. How long were they running OK before you enabled this DMA? Are the drives under warranty? yes. thanks for asking. These drives aren't in the bung batch IBM released somewhere near July last year? The drives are 2.5 years old. They would have been released in the late spring or summer of 2000. Darren --------- Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: weird hard drive failure
Dear Todd: Thanks for your reply. I did read the documentation, but -c1 seemed to work. I did set keep over reset (uh oh). I cannot access these drives now even at the BIOS level, even with DOS tools and this is way before DMA gets turned on. Does the keep over reset change something in the drive or some other bit of hardware? Is there some way to reset these drives, like resetting a motherboard? Darren At 05:21 PM 2/4/2003 -0800, you wrote: On Tue, 4 Feb 2003, Darren R. Gitelman wrote: > /sbin/hdparm -c1 -d1 /dev/hdb It often pays to read the documentation: -c Query/enable (E)IDE 32-bit I/O support. A numeric parameter can be used to enable/disable 32-bit I/O support: Currently supported values include 0 to disable 32-bit I/O support, 1 to enable 32-bit data transfers, and 3 to enable 32-bit data transfers with a special sync sequence required by many chipsets. The value 3 works with nearly all 32-bit IDE chipsets, but incurs slightly more overhead. Note that "32-bit" refers to data transfers across a PCI or VLB bus to the interface card only; all (E)IDE drives still have only a 16-bit connection over the ribbon cable from the interface card. If you haven't set keep-over-reset, try changing the value of I/O support to -c3 instead of -c1. If you are completely unable to access your drives, even with DMA turned off at boot, you may need to find out how good Dell's technical support or warranty service really is. --------- Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
weird hard drive failure
I've had 2 hard drives fail on 2 different Dell precision workstations (420) within the last week. Wondering if anyone has ever seen the scenario below: Both drives were IBM Deskstar 60 GB. Both drives were configured as stand-alone (i.e., not part of raid), and had 2 partitions, one swap the other data. Neither drive was a boot drive (they contained data). I turned on dma access to speed up the drive /sbin/hdparm -c1 -d1 /dev/hdb All seemed to work fine on check /sbin/hdparm /dev/hda I/O support = 1 (32-bit) using_dma = 1 (on) 1 day later for one drive and 2 minutes later for the other there are read errors on the drive and it is no longer recognized by the system, like it's not even there anymore. On boot up the bios doesn't see the drive. I've tried switching the connector, setting the drive to master or slave, using tomsrtbt to start the system and seeing if it can see the drive, using Dell Diagnostics which runs in DOS. The drive cannot be seen but it sounds as if it turns on. This does not seem to be a case of corrupt data. Any thoughts? Darren --------- Darren R. Gitelman, M.D. Cognitive Neurology and Alzheimer¹s Disease Center E-mail: [EMAIL PROTECTED] WWW: http://www.brain.northwestern.edu Voice: (312) 908-9023 Fax: (312) 908-8789 Northwestern Univ., 320 E. Superior St., Searle 11-470, Chicago, IL 60611 - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
