Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am using Fedora Core 4. I am not using RAID. This is just a plain HD with a single extended partition and several volumes within that. This is not the boot drive, but a second drive I want to add on a second controller (Highpoint chip) located on the mobo (DFI NFII Lanparty).
I get a weird, 4 minute pause with a HD on the Highpoint controller just after the linux kernel begins to load. (Without the drive, there is no pause.)
Like this :
Uncompressing Linux ... OK, booting the kernel.
HPT37XN unknown bus timing[69 4]
Then it stops here for around 4 minutes. At first I thought it was locking up, but it does go on, without error, if you wait. The partitions on this HD can be mounted and look perfectly fine. If I put the HD on the first controller with the boot drive, there is no problem, no pause, so there is nothing wrong with the HD. Windows has no problem with the HD on the Highpoint controller, so there is nothing wrong with the controller.
The line about "HPT37XN unknown bus timing[69 4]" gets displayed whether or not a HD is attached, and whether or not there is a 4 minute pause, so that in itself does not seem to be a problem.
I tried a later kernel, but it has exactly the same long pause. (That kernel does not print out a line about HPT37XN ...)
Does the controller card have an built-in BIOS you can use to tweak settings? Maybe something is mis-set there. Otherwise, if you're using Fedora, go into GRUB (hit 'e' at the bootloader menu) and find the kernel command line and remove the quiet and rhgb options. These options supress a lot of the devug messages that are printed on boot. Maybe if you turn them off one of the messages will provide a clue as to what's wrong.
Thanks for the info, btmiller. I didn't figure out how to get debug info on my own -I didn't even know there was any- but I did try other things that spit out error/info messages. I booted from the CD using "linux rescue." Later, I installed FC4 to the HD in question, and before the installer greeting it also kicked out error messages. (It does not do this unless a HD is connected to the Highpoint controller, so I didn't get it before.)
The error/info messages are (appoximately):
-> No known bus timing. Using timing for HPT372. (which is what I have)
-> Disabling DMA. (no wonder it takes forever.)
I suppose in order to detect the valid commands for this HD, it then attempts to access hde1, hde5, and hde6. (the right HD). The error messages say (after about a minute for each):
-> DMA timeout error. (yes, it apparently attempts to use DMA after disabling it!)
I still don't know what to do about it. I wouldn't think anything in the controller BIOS would get around this, but I will take a look. Maybe there is something to pass to the kernel on the boot line?
It took about an hour to install FC4 on the second HD, when it takes 15 minutes otherwise. It takes a good part of a minute to load up large programs in linux from this installation, so it is dead slow this way. I'm surprised I am the only one that ever ran into this.