Red Hat Bugzilla – Bug 120539
(AGP)Installer hangs when loading agpart
Last modified: 2015-01-04 17:05:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
Description of problem:
When trying to run "linux mediacheck","linux memtest86", the
graphical version of the installer, or text only version, it stops on
the line "agpart: maximum main memory to use for agp memory: 941M".
The problem repeats each and every time I restart and try to install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Restart and try to install or use any options
Intel Pentium 4 2.8C with HT enabled
ASUS P4S800D-E Deluxe with SIS 655TX chipset
Seagate 120G Serial ATA drive
1024M PC3700 OCZ Gold Rev. 2
ATI Radeon 9000 Pro
Memorex 52x24x52x CD-RW
Interesting....when I changed the AGP aperture size from 128M to 64M,
it booted without a problem.
That is very odd. I'll bug folks at SiS and hopefully get some docs
out of them.
I'm also seeing this problem on a Toshiba Magnia Z310R server with
Core 2 test 3. It has a P3 1.266, with 1GB Ram. The bios does not
seem to have a place to change the AGP aperture size.
agpgart: VIA Apollo Pro 133 chipset
agpgart: Maximum Main memory to use for agp memory: 942M
as of fc3 you can boot with agp=off, but I'm going to leave this bug open until
I find out more info about the cause of this hang.
out of curiousity, does the hang with 64M still happen with the latest kernels ?
there were some fixes to sis-agp, which should be unrelated, but its a long-shot..
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.