On Fri, Jun 12, 2015 at 03:12:43PM -0600, jd1008 wrote:> I have not been able to enter the edit screen to edit the boot > options and add inst.txtIt is 'inst.text'. Not 'inst.txt'. Read this for setting up custom boot options to the installer: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html -- Jonathan Billings <billings at negate.org>
I have not been able to enter the edit screen to edit the boot options and add inst.txt On 06/09/2015 10:55 AM, Jonathan Billings wrote:> On Tue, Jun 09, 2015 at 09:16:07AM -0700, JD wrote: >> The screen image I took with my camera can be viewed at >> https://www.sendspace.com/file/4828ej >> >> The questions I have are: >> why VNC ??? VNC is a horribly insecure protocol. >> Why would I want someone from outside viewing my installation? >> Why is the X server looking for display :1 ?? >> I only have one display screen on the laptop, so the display is :0 >> >> This is a horribly broken ISO spin. > Looked at your image. > > It appears the graphical installation failed to start. Did you read > the text? Did you try the suggestion? I'll retype it here: > > * if the graphical installation fails to start, try again with the > inst.text bootoption to start text installation > > I suspect that for whatever reason, the graphical installer is failing > on your laptop, probably because it doesn't support your video card. > Try the text-based installer. Sadly, laptops are so varied its quite > often that the video hardware simply isn't supported during install, > and needs a 3rd-party driver to even work. > > Don't get too excited about the VNC suggestion. Anaconda (the > software performing the install) has the option to use VNC for a > graphical install if you are installing a headless server. You're > just seeing anaconda log a comment that it wouldn't be available since > you didn't configure networking in the anaconda boot options. So it's > not even trying it. You're just seeing a verbose log entry. >
On 06/12/2015 09:03 AM, Jonathan Billings wrote:> On Fri, Jun 12, 2015 at 03:12:43PM -0600, jd1008 wrote: >> I have not been able to enter the edit screen to edit the boot >> options and add inst.txt > It is 'inst.text'. Not 'inst.txt'. > > Read this for setting up custom boot options to the installer: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html > >I found a web page that outlines step by step the process to upgrade from 6.x to 7. See http://linuxsysconfig.com/2014/07/upgrade-to-centos-7/ I installed the rpms it provides links for and I will try to upgrade after I have done the necessary backup. Cheers, JD
On 06/12/2015 09:03 AM, Jonathan Billings wrote:> On Fri, Jun 12, 2015 at 03:12:43PM -0600, jd1008 wrote: >> I have not been able to enter the edit screen to edit the boot >> options and add inst.txt > It is 'inst.text'. Not 'inst.txt'. > > Read this for setting up custom boot options to the installer: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html > >Too dangerous!!! This is why: |inst.text| Forces the installation program to run in text mode instead of graphical mode. The text user interface is limited, for example, *it does not allow you to modify the partition layout* or set up LVM.