Bug 328861

Should have mentioned earlier, this happens w/ the Fedora 7 installer, not
fc6test3 as was my best/only option in the menu when I filed this, sorry ....

mbd in this case was/is Gigabyte P965 DS3, newly purchased, w/ Q6600 CPU & 8 GB
of RAM (4X2GB sticks) max. It ran memtest86 for ~22 hours w/ all 8 GB installed,
7 passes, 0 errors.

This seems like an isolated report, unless Chuck saw something...
Could you take a picture of the screen (after vga=ask and selecting
smaller letters)? As it is, there's no telling what is happening.

Not without going back & duplicating the install on what is now an up-&-running
server-ish box :-). I have had this problem *VERY* consistently over the years,
w/ SuSE 8.2/9.2 years back, then FC5 on a 933 MHz box that I still have. I
always have to remove RAM to get down to some smallish amount for the
installation kernel to boot correctly. I also filed, then withdrew a bug about
the installed kernel doing the same thing, which it has done for me on 2
different boxen, 1 Intel Q6600 based (a few weeks ago, same time frame as this
bug) & 1 Intel E6600 box (yesterday). That was solved (in both cases) by a
kernel upgrade (yum -y upgrade kernel) immediately after installation in both
cases (bug 328871, filed & withdrawn).

Fedora 7 respins (up-to-date installation DVD/CD sets) are at:

http://spins.fedoraunity.org/spins

Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.

Yes definitely still happens, has been happening in 1 form or another for me for
years (under Mandrake, SuSE, & now RedHat). I think it is something generic to
Linux, not particular to RH, but still irritating. It also complicates
converting to Linux. I haven't done any mew installs in a few months which is
why I haven't commented further, but, yes, it happened the last time I tried
(FC7 install from DVD onto Intel Q6600 box w/ 8 GB RAM). In years past the limit
was 1 GB of RAM, and lower than that farther back, but it has always been
(irritatingly) present. It is a hassle to have to open up & partially strip the
box to install Linux :-( ....

Could you attach output from the following commands as separate text/plain
attachments to this bug:

# dmidecode
lspci -vvxxx
dmesg

Cheers
Chris

Created attachment 291674 [details]
output from 3 commands ....

OK, here you are. let me know if you need more ....

There is a BIOS upgrade for your motherboard available which you may wish to
consider, though it does not specifically indicate this will resolve the issue.

Your BIOS indicates 4 GB is the maximum, not 8 GB. Please try booting/installing
with:

acpi=off

as described here:

http://fedoraproject.org/wiki/KernelCommonProblems

Hmmmmm .... the box runs AOK (after kernel upgrade) w/ 8 GB onboard, & ran
memtest86+ for 20-ish hours w/ all 8 GB before installation. I'll look into the
BIOS upgrade, though I am having no indications of problems at the moment. My
manual (& NewEgg) said 8 GB max when I bought the board, that was 1 of the
criteria (> 4 GB RAM capable) when I was shopping ....

Differences between box and their contents are not unknown to me either I'm
afraid. Anyway from dmidecode:

Handle 0x001B, DMI type 16, 15 bytes.
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 4 GB
	Error Information Handle: Not Provided
	Number Of Devices: 4

Good to know its running better - setting back to NEEDINFO - please close when
you're happy or update if it recurs.

This problem should be solvable by adding "mem=2000M" to the boot options during
install...