Timothy Murphy wrote: > Debbie Deutsch wrote: > >> The install of FC5 went flawlessly. After the install, I rebooted and >> went through the first-boot configuration. One thing that I did was to >> turn off SELinux. (Let's save that conversation for a different thread. >> :-)) I also changed the display resolution to the same value I had >> been using under FC3. Everything else was very vanilla. You know the >> rest. :-( It appears that something changed as a result of the first >> boot configuration and is causing this problem. >> >> Does anyone have any suggestions regarding a fix for this? Or >> additional troubleshooting that I should do before submitting a bug >> report? Since the system ran FC3 just fine, I doubt this problem is due >> to hardware. > > The advice to turn off avaha-daemon seems sensible to me. > > If that doesn't work you could try running in text mode > (answer "linux text" to the boot prompt > or append "text" after answering "a" when the grub prompt appears). > Maybe it has something to do with the change you made in X. > > Ps I am not a guru"! > Thanks to both of you for your help so far. I have experimented similar to what was suggested. Like Mike, I now believe the problem has something to do with X. Here is what I tried. Instead of typing a boot command, I used the "type I to enter interactive mode" feature during boot. I tried this twice. One time I said "no" to starting avahi-daemon. The other time I said "no" to starting the first-time boot service. (I have noticed that that always runs, even when it is not the first boot after install. At least that's the case on my other FC5 machine.) Anyway, the results were: - not running the avahi-daemon didn't change anything. The system hung at the same point with the same blank grayish-blue screen. - not starting the first time boot service did let boot get past the avahi-daemon. However it did not fix the problem. It eventually did hang with a (mostly) blank grayish-blue screen that had junk in a narrow band across the top. Based on this, I am thinking the problem has something to do with X. The strange thing is that I have no problems with the same monitor and display settings when I use my other FC5 machine that has an nVidia nForce4 chipset. (That machine is still on the original kernel that came with the FC5 distro because of a dmraid bug, so it still has the original driver that came with the distro, not the updated nVidia driver.) OTOH, I am not seeing any reports of problems with the Intel chipset that is in this system. Also, this monitor has worked perfectly with FC4 and FC3. I am thinking that maybe my next step should be to go into rescue mode and try to see what the config file says about my video adaptor and monitor. It can't hurt. If that doesn't reveal the problem, I just may try reinstalling and see what happens if I don't change SELinux and don't change the monitor settings. Debbie P.S. I am going through a KVM switch to share the monitor among machines. That has not been an issue for FC3, FC4, or FC5 on my other Linux box.
