If it's any help, I've recently done a lot of installs of FC2 on our number crunching cluster and a few workstations, and I've noticed that on a dual CPU system, the boot up appears to hang at the "Red Hat nash..." line for a considerable period - over a minute on many of the systems - before boot up continues normally. Occasionally - about 1 in 6 new builds - the system does actually hang at that point (> 30 minutes left to itself), but on all occasions (so far) a power cycle gets past it. Since the systems still boot fine, I haven't looked too hard at this behaviour, but I have noticed that single CPU systems don't do it. It's a bit annoying when you are building a load of systems against a deadline, but it's no big deal. Incidentally, the clock speed on these systems covers the range 1.6G to 2.8G, so it's not related to the 'power' of the machine. Oh, and before someone asks, I am using the SMP kernel on the SMP machines and the UP kernel on the UP machines. :o) Paul. On Tue, 2004-09-07 at 18:37, Alexander Dalloz wrote: > Am Di, den 07.09.2004 schrieb Jeremy Conlin um 18:54: > > > I recently installed Fedora Core 2 on a dual processor Dell PowerEdge > > 2400. This machine was running Red Hat 9 prior to Fedora Core 2. > > Installation appeared to proceed normally. When I rebooted to run > > Fedora for the first time, it hung. The last lines on the screen > > were/are: > > > > agpgart: unable to determine aperture size. > > agpgart: unable to determine aperture size. > > Red Hat nash version 3.5.22 starting > > This does not indicate a nash problem. > > > Then nothing happens. > > > Has anyone else had this problem? Is there a fix? Does Fedora support > > two processors? > > Sure. Why do you think there is an SMP kernel? > > > Jeremy Conlin > > Try booting without RHGB, the graphical boot. At grub boot prompt enter > "a" and erase in the kernel line the "rhgb quiet" and enter a "3" to > boot into runlevel 3 (all actions without the quotes). > > Alexander >
