Dell Poweredge Possible keyboard/HDD conflict, immediately after install
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Dell Poweredge Possible keyboard/HDD conflict, immediately after install
poweredge 1300 PIII 550 (1998-1999) w/786-896megs memory (trying to figure out if there's onboard base memory, the 786megs are pure memory sticks), HD 500gig seagate barracuda 7200.1, PATA controller, PS/2 keyboard, DVD burner
One of the system's problems is that its "case has been opened / system intrusion" warning cannot be made to go away in the BIOS -- the CMOS battery is "borderline" and but still works, so each time the system reboots, is powered down or loses power (funny, put aside ice storms, that does happen here once a year) I have to hit the F1 key. Changing the "Intrusion Detection" in the BIOS doesn't work, it still comes back.
I've had centos 4.7 and F11 on it with a different drive. I could not get the system to mount the 500 gig drive.
The current installation has had F9 on it; I had F11 on it with the 500 gig drive but I never got past the installation; during the first reboot the keyboard appeared to be non-responsive. The keyboard worked fine during the installation. I have also reproduced the problem with another keyboard known to work on another system, with the same result. Neither keyboard is USB.
I have done several reboots and have determined that the keyboard is powered up (changed the bios setting to have the num lock light on); if I do the timing correctly, the F2 key works to get into the BIOS setup, and the keyboard works fine there. Continuously holding the F1 gives a keyboard error; slowly hitting it eventually gets a beeping sound every time I hit any key, the keyboard buffer appears to have filled up. A Fedora 9 liveCD also works. A check in the CentOS 4.4 liveCD shows that the F1 key indeed does work properly.
I then did an installation from my old CentOS 5.1 cd's with the intention of doing all of the updates.
I have since tried a CentOS 4.4 liveCD I have sitting around, and it works just fine. Using the CentOS 4.4 liveCD I am able to mount the 500 gig drive; interestingly it shows up as 106megs, currently with 82megs free. A quick check in Anaconda confirms that it recognizes a drive with 476938MB, and the drive ID is ST3500630A
I have been told that there is probably an IRQ conflict between the two, due to the recentness of the HD being mixed with an older keyboard on an old motherboard.
The source of my suspicion that it's a conflict between the keyboard and the HD stems from the fact that up until a month or two ago when I changed back to the 500gig HD (purchased NEW in August 2008) and reformatted it from its Fedora 9 boot (it worked just fine) to Fedora 11 and had the problem listed earlier; initially I assumed that the fact that I could not mount it under F11, on a separate drive, was due to the fact that the two drives spin at different rates. When I formatted the 500gig drive under F11, I had the problem as described, and presumed that F11 may be too advanced for the Frankenstein construction and the 8-10 year difference in age between the drive and the rest of most of the system, hence my desire to try using the CentOS 5.1 setup (which as stated earlier would updated to 5.4 ASAP). However, the difficulty is identical.
CentOS 5 would probably be a better solution given the longer life left to the product -- I think there's still another 4-5 years or more left -- vs. having to update every 13 months or so (at this point I would feel obliged to install F12 now that it's out, putting things back out of sync, which was what I had wanted to do by bringing all my computers in line with F11 back in June, instead of going through installation cycles every 6 months or so on varying systems. It would be much more preferable to keep this system stable if only because it's such a large HD it would be a shame to have to keep on reformatting it, and I don't need to have up to date versions of OO.o etc. on it.
Does anyone have any clues how to address this so that I can get past the initial rebooting?
I'm a bit intimidated by your long post and a bit puzzled what your problem right now is. You described a lot.
One thing that I can address is the "Intrusion Detection" message from the BIOS:
Some BIOS have an option that negates every change to options. Does yours have one? Nother thing to try would be to load fail safe defaults and see what happens.
When it comes to the drive not being showed with the right size I'm a bit lost beside that maybe the bios can't handle such biggies (like you pointed out). If this is a IRQ thing with your keyboard see if you can find some thing in bios to alter IRQ's
My approach to this would to first get a clean BIOS, then see that you can get the harddisk to be reconed to it's full potential. Either with a live cd or during setup.
Hope this helps. To further get you going please write down some exact questions.
First, you should place the long data or list(s) within vbcode tags # or quote. The tags are at the top of the reply window, # for code and the balloon at the left of # for quotes. By using the code tags it will make your post cleaner therefore easier to read.
Replace the button battery to get the intrusion settings cleared. The switch is a dual action unit which you can pull the actuator plunger outwards gently to disable the switch thus the warning while the case is open. Once you close the case then reenter the BIOS and then save settings to boot. The message should not be there once this is done.
While in the BIOS, look at the memory shown by the system.
I suggest that you get a LiveCD like 'SystemRescueCD' or 'UBCD' which have system diagnostics that can be used to aid in finding solutions to potential problems. Either one is good to have on hand to maintain the system or diagnose system problems.
If you boot either diagnostic Livecds then choose 'memtest86' to test your memory. Note what is recognized by the program.
For hdd, I would use the manufacture diagnostics first but then you could select from the varied tests on the LiveCD of choice.
The above links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!
If the BIOS won't take settings a real possibility on a 10 year old box is that it simply has been rewritten too often. Another is low voltages, which can cause erratic hardware behaviour. With a 10 year old box, You'd need a memory like an elephant to remember when CHS etc. came in. LBA imposed size limits, and this may be the disk issue.
If this is your box, and you want to do this, fine. If it is a company machine it is certainly _past_ end of life, and this is proved by the fact that it still isn't going while you are have been farting about with it for some time, by the sound of it. Do Dell still support something from the last millenium? Please don't post half a mile of useless stuff (every line of lspci -vvvv). Keep output as concise as possible.
In my experience things of a certain age are best left undisturbed except when necessary. The first rule in hardware is "If it ain't broke, don't fix it!" You fixed it, and now it _is_ broke :-(.