Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Two additional things I can think of:
1 - verify your install media by running an md5sum on the CD and your downloaded image and verify them against the official sums.
2 - This is a x86_64 OS. This is probably a dumb question, but are you using a 64 bit capable system?
after googling since afternoon i managed to boot and login to the system. The solution
was to use a switch "acpi=off"(don't know exactly what it does).
ACPI is a set of a set of power management functions and features. See this wikipedia link for info. Unfortunately, it is also something that appears to have been poorly implemented in terms of standardization and this causes a lot of trouble for the end user as you have just witnessed.
I doubt it for the most part. You may have issues with things like suspend to ram or hibernate or variable fan control. As far as operational stuff, I wouldn't worry too much about it. Your system specs, though, look like it is a fairly modern system so it kind of surprises me that ACPI would cause you problems.
Here is a link to a site on Linux and ACPI. I didn't review if fully, but it may help to explain what some of the functions (that you disabled) do.
I have a follow up question to this thread. Do you have the option to boot using different kernels? I ask because a kernel panic on boot often times indicates that there is a missing module. Re-reading your initial post, you indicated that it installed correctly, which I assume was running a copy of RHEL6 when it did so. Based upon my experience with other distributions, typically the initial install will use a kernel version with a lot of extra stuff compiled in because one never knows what hardware it will find. Part of the installation process is to load a "generic" kernel that doesn't have these modules. An initram image is then added to the boot process to bring the modules required for your particular hardware. If you don't have all the modules, a kernel panic will ensue. This is quite common, for example, in Slackware with EXT4 drives - one must use the huge kernel and make an appropriate initram image. In Slackwre, this is the user's responsibility. Undoubtedly Red Hat does the same thing, just automatically for you.
What I am getting at is if you can load a full / huge kernel and that works fine, then you may be able to re-make the correct module add-on for your system and restore the ACPI functionality.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.