On 4/13/06, Debbie Deutsch <fedoralist@xxxxxxxxxxxx> wrote: > Perhaps someone can suggest some troubleshooting tips (or even a fix!) > for a problem I have encountered. Basically, I installed FC5 on a > system. After the install I did the first boot configuration. It told > me to reboot. Ever since then, booting hangs after an attempt is made > to start avahi-daemon. I get a screen with a blue background and > then.... the system hangs. > > Here are more details about the hardware and system configuration. > > The system: FC5 (86_64) freshly installed (no other OS or version) on > the only hard drive in a very simple system. There is an optical drive > (shares the IDE bus with the hard drive). The processor is 2.66 GHz > Intel 64-bit single-core. There is a gig of RAM. The chipsets are > Intel ICH6 and 915GL. The video is integrated on the motherboard (Intel > Graphics Media Accelerator 900). > 1. Are you using Cable Select? If yes, is the hard drive located at the end of the cable? I, personally, do not trust Cable Select. Not because Cable Select does not work, but because I do not trust mixing old with new. There old products around which do not fully comply with today's standards. On any drive on an IDE chain I make sure that jumpers are used to configure the master and slave device. I recommend that you do the same. 2. Move the optical drive to the secondary IDE channel. Make it the master. Yes, use a jumper. Any interference in operation between the hard drive and the optical will be removed and in the process you will improve the data transfer between the optical and hard drive. > The hard drive previously had FC3 installed. That installation was for > a 32-bit Pentium processor. (It was a 450 MHz Pentium II, fwiw.) I > removed the hard drive from its original system and put it in the system > described above. Everything worked fine, except it was FC3 and I wanted > FC5. So I backed up the files that I wanted to save, and did an install > of FC5. > > 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. > > TIA, > > Debbie Deutsch > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >
