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.
Hello all, I have a bit of a problem with installing all flavours of linux on an HP NetServer LH II. This particular machine exhibits a wide range of symptoms when introduced to each flavour. For example, with Gentoo I boot from the install disk and load the default kernel: gentoo. It loads the kernel package into memory, then reboots. Same happens if i load the gentoo-nofb kernel, which I have no idea how it's different from the standard kernel. Anyway, neither works but I can boot into Memtest86 on that same cd. Move to Dyne:Bolic Live CD. The system boots to kernel but fails to make it all the way to the GUI and halts at a shell wherein I can not log into. Finally, trying a version of Mandrake I've had for a while (version 10.0, yes I know, I'll upgrade the kernel after install) I am yielded a less cryptic response. The system boots from the CD then begins it's process of detecting all the devices on the system. However, when I get to the point where it detects the CD-ROM drive that it just booted from it doesn't find the device and I can proceed no further. I've tried specifying the AIC-78xx driver so that it can use the SCSI interface the CD-ROM is hooked into but it fails each time. It's a Toshiba SCSI CD-ROM if that makes a bit of difference. Please help!
First off, thanks for pointing out the glaring obvious. I have already run a forum search using a few dozen keywords. If you have a forum thread to link to that I couldn't find, that'd be great. Anyway, here are the versions as I have them written on the CDs:
Mandrake 10.0 (known stable release)
I have also tried out Slackware, the version you suggested. The system crashed when it tried to load up the interface and halted.
I ran a memory stress test and CPU stress test on this machine to check to see if it was failing hardware, and benched both components for 48 hours apiece. Both checked out.
May I suggest that you remove the (optional) plug-in RAID controller, connect one HDD cage RAID cable directly to the single channel SCSI controller integrated into the planar board (so you have HDDs on which to install an OS), and try installing Red Hat 9 or 8.
It will be interesting to see if the install is successful with the RAID controller removed.
If successful, then reinstall the plug-in RAID controller with only one HDD cage cable isntalled (ie HDDs on a single channel), and repeat the test.
Onebuck, I wish I could tell you what that error was, but there is no error. Everything just stops dead. It will sit on "loading vmlinuz" for a couple hours.
It seems to be a non-issue now, because the server is dead. The CPUs sorta died . . . no, they literally died. The thermal compound burned if that gives you an idea. It's now not an issue of this server not booting from linux, it's a matter of not booting at all. What a shame.