Red Hat Bugzilla – Bug 113087
system hangs on firstboot after anaconda completes.
Last modified: 2007-11-30 17:10:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
See bug 75693. In summary, i've tried installing Fedora Core 1 on a
Celeron, 566Mhz, 96MB RAM, intel i810 graphics. anaconda works fine.
after completion, it prompts for a reboot. after this reboot, the
text-based startup appears to go smoothly, but then the screen goes
blank (the monitor is in standby). this condition persists until you
manually turn the monitor off and on, at which point one can see the
firstboot screen, but cannot interact with the system by either mouse
i turned the system off manually and rebooted. the next morning, the
fedora core login prompt was available, and the system appeared to
behave normally. having not completed the firstboot process (and,
having not yet figured out that there was one...), i just logged in as
i shut it down and rebooted once more, and the firstboot program had
the same problem as before.
a new fresh install of the system produced the same results.
i initially posted this as an addendum to an existing bug report, as
referenced above, but did not realise i was adding to a Red Hat 8.0
thread. interstingly, the person who reported that bug was also using
the i810 graphics chipset.
i performed an identical instal on a different computer and have no
problems with it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install fedora Core 1, choose to delete all existing data on HD.
2. at completion of anaconda install, reboot.
3. wait for screen blank.
Actual Results: computer becomes unresponsive. screen can only be
visualised by power cycling the monitor.
Expected Results: monitor should wake from standby and present
firstboot process. computer should accept input from user.
Can you attache the /var/log/messages file after the problem occurs?
unfortunately, no. as i mentioned in my comments on the other bug
report, i switched to another distribution (mandrake) which did not
(perhaps obviously) have the same problem. if you look at the thread
from the other bug report (75693), the previous reporter posted not
one, but two logs.
i'm new to linux and didn't know how to switch runlevels and so-on a
week ago, when this happened. i've got that all under control now. if
absolutely necessary, i'll wipe the computer once more and post logs
for you, but that will take some time as i'm in a different city now
for a couple months.
it's worth adding that i didn't see any note that the previous bug
was resolved, and from my (amateur) analysis of the logs posted in
that report, it's not a problem with agpgart being unavailable, as is
widely reported with older kernels, and distributions such as debian
stable 3.0r2 which use those older kernels, but something else...
thanks for your help. i wish i could provide you more detail.
Ok, well, please reopen this bug report if you ever get a
/var/log/messages that may shed some more light on the problem.