Re: [CentOS] baby blue screen of permanent death

2013-10-26 Thread Michael Hennebry
On Sun, 27 Oct 2013, Rob Kampen wrote: > On 10/27/2013 07:03 AM, Michael Hennebry wrote: >> Absent other ideas, I might try re-installing CentOS or re-installing X. >> I have a pretty good idea how to do the former, >> but the latter might be harder despite, in principle, being less intrusive. >>

Re: [CentOS] baby blue screen of permanent death

2013-10-26 Thread Rob Kampen
On 10/27/2013 07:03 AM, Michael Hennebry wrote: Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive. My understand is that unistalling X will normally t

Re: [CentOS] baby blue screen of permanent death

2013-10-26 Thread Michael Hennebry
Absent other ideas, I might try re-installing CentOS or re-installing X. I have a pretty good idea how to do the former, but the latter might be harder despite, in principle, being less intrusive. My understand is that unistalling X will normally take all its dependents will it. That means That I

Re: [CentOS] baby blue screen of permanent death

2013-10-24 Thread Michael Hennebry
On Thu, 24 Oct 2013, Steve Clark wrote: > Have you looked at /var/log/Xorg.0.log file - it sounds like there is a > problem with X. I have now, but I do not know what to do with the information. I understand line 15 and 111. Any ideas? [root@localhost log]# grep -n EE Xorg.0.log 15: (WW) wa

Re: [CentOS] baby blue screen of permanent death

2013-10-24 Thread Michael Hennebry
n Thu, 24 Oct 2013, Steve Clark wrote: > Have you looked at /var/log/Xorg.0.log file - it sounds like there is a > problem with X. Not yet, but I will. > Also someone mentioned editing /etc/inittab and setting the run level to 3. > id:5:initdefault: - change the 5 to a 3. > If it boots > to a

Re: [CentOS] baby blue screen of permanent death

2013-10-24 Thread Steve Clark
On 10/23/2013 12:01 AM, Michael Hennebry wrote: > On Tue, 22 Oct 2013, Scott Robbins wrote: > >> To view the startup, when you boot, hit any key, then hit e as in edit (I >> think--otherwise, just use the arrow key to get down to the line beginning >> with Linux and when you highlight that line hit

Re: [CentOS] baby blue screen of permanent death

2013-10-23 Thread Michael Hennebry
On Tue, 22 Oct 2013, John R Pierce wrote: > On 10/22/2013 2:24 PM, Michael Hennebry wrote: >> How do I change passwords on an install, e.g. my F14, >> into which I cannot login? >> I can edit the files from either Knoppix or from a CentoS terminal. > > edit /mnt/.../etc/shadow and delete the pa

Re: [CentOS] baby blue screen of permanent death

2013-10-22 Thread Michael Hennebry
On Tue, 22 Oct 2013, Scott Robbins wrote: > To view the startup, when you boot, hit any key, then hit e as in edit (I > think--otherwise, just use the arrow key to get down to the line beginning > with Linux and when you highlight that line hit e to edit. > > At the end of that line you will see r

Re: [CentOS] baby blue screen of permanent death

2013-10-22 Thread Scott Robbins
On Tue, Oct 22, 2013 at 04:24:08PM -0500, Michael Hennebry wrote: > > What is the incantation to get a text view of the start up > so that I can get a hint of what CentOS is waiting for? To view the startup, when you boot, hit any key, then hit e as in edit (I think--otherwise, just use the arrow

Re: [CentOS] baby blue screen of permanent death

2013-10-22 Thread Michael Hennebry
On Tue, 22 Oct 2013, John R Pierce wrote: > On 10/22/2013 2:24 PM, Michael Hennebry wrote: >> How do I change passwords on an install, e.g. my F14, >> into which I cannot login? >> I can edit the files from either Knoppix or from a CentoS terminal. > > edit /mnt/.../etc/shadow and delete the pa

Re: [CentOS] baby blue screen of permanent death

2013-10-22 Thread John R Pierce
On 10/22/2013 2:24 PM, Michael Hennebry wrote: > How do I change passwords on an install, e.g. my F14, > into which I cannot login? > I can edit the files from either Knoppix or from a CentoS terminal. edit /mnt/.../etc/shadow and delete the password hash between the first two :'s, so it looks