Two different machines.
Machine 1 - brand new Dell i7 16 Gig of memory and 2T hard-drive.
Machine 2 - old laptop (32-bit)
Downloaded Oracle EL Version 6.4 64-bit and 32-bit
Ran the 64-bit install on the Dell
Ran the 32-bit install on the laptop.
At the completion of the install, the CD pops out and the system reboots.
The progress bar moves and then stops near the end and never progresses.
Left if for 2 hours on both machine and neither progresses.
Have not tried 6.3.
Wondering if there is something with the 6.4 download.
Anyone experience this or have any ideas?
Your mileage to installing Oracle Linux on a Desktop or Laptop system will vary because it is designed for server hardware. Did you install a graphical desktop? I suggest to press any key at system startup to enter the Grub menu and add "nomodeset" to the kernel parameter line. You might also want to remove the words "rhgb" and "quiet" to get all details during the system startup to see what is happening.
Ok, for it finally loaded and I have my gui screen. Thanks.
During the load, as the info scrolled by very quickly i notice a "FAILED" notice but couldn't see which component it was.
Maybe that was preventing the load.
Is this information logged in any file so I can scan to see what failed and may be causing the issue?
Did that change actually fix anything or bypass a particular load?
Edited by: Jim on Mar 22, 2013 1:28 PM
Ok, searched and found info on nomodeset.
Simply put, the nomodeset kernel parameter disables Kernel Mode Setting. KMS provides faster mode switching for X Windows and the console. It allows the kernel to use higher resolutions than the standard VGA BIOS modes. VGA provides a text and graphics console. For some graphics drivers, KMS is requried, for some it is not compatible. It means your video adapter is not compatible with the kernel autodetection, but fortunately it works with KMS disabled. The problem is usually a failure in detecting the chipset support for 2D and 3D graphics acceleration modes, causing the video to shut down.
I think the best explanation for KMS is here:
To make the change permanent you need to edit /boot/grub/grub.conf and add "nomdeset" to the kernel parameter lines.
Thanks for every ones help.
Was able to reboot without issues a few times after updating the configuration file.
This seems to be specific to 6.4 as a number of folks used 6.3 without issues on basically the same type of box.