[x86_64] Cannot Install Feisty Fawn Herd 5 - Black Screen

What about "acpi=off"? Does that make any difference? Can you try removing the "quiet splash" options from the kernel's command live on the CD and try again? Does it proceed any farther? If so, can you post a photograph of what's on the screen or write down a few details and transcribe it here?

Cheers,
 Kyle

I went for the transcribe option though I never wrote everything down. I'll give you what I've got and try and get prepared for photos later. Apologies if that means some of the details are not there as I had to try and write things down as it was booting so accuracy depended on the speed of the booting. I have tried to use my judgement on what might be important.

First attempt:

Removing "quiet splash" option only:
Seems to go through a full load i.e. reads CD properly and is loading linux, loads many things, gets far as brining up network interfaces and more
 a few sample lines:
[42.406257] SCSI deivce SDA.........................
[42.4....] etho: forcedeth.c so would appear to know nForce4?
[44.3..........] squashfs version 3.1
yada
[97.56......] kernel log
does HAL
Bluetooth
then does local boot scripts and VERY soon after monitor loses signal, tho the CD is continued to be read for a short while and the num lock lights do not flash as before. It kinda feels like linux has in fact loaded it just isn't displaying. For instance, pressing power button does not shutdown machine unless it is held for a few seconds unlike in original bug it was shutting down on immediate press of power button.

Second attempt

"acpi=off" only

reacts exactly as in bug description i.e. blacks screens after vmlinux, no reading of CD, num lock and scroll lock lights flash. Also shuts down immediately after power press i.e. does not need to be held

Third attempt

"acpi=off" and "quiet splash" removed
sample lines:
[47.7...] Disabling IRQ #10

/bin/sh: can't access tty; job control turnoff
initamfs [77.688704] ata2.00: qc timeout (cmd 0xef)
[77.628732] ata2.00:failed to set xfer mode (err_mask = 0x4)

[113.111750] ata2.00 qc timeout (cmd 0xef)
[113.111824] ata2:failed to recover some devices, retrying in 5 secs

[118.590998] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

[148.598802 ata2.00 qc timeout

[149.102762] sata_nv 0000:00:08_0 using ADMA mode

[149.414688] ata3: SATA link down (SSstatus 0 SControl 300)

[149.737645] hdc:ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(66)
[149.727837] Uniform CD-ROM drive Revision: 3.20
HANGS

Hope this helps. I'll try and get photos uploaded but it's a Rugby 6 nations weekend so can't promise anything ;-)

Cheers,

Alan

Sorry I was very busy in the last wee while.

I tried the "adma_enabled=0" option because I found this change in kernel 2.6.20 for nForce4 boards http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fbbb262d9ea9bdbd79d7058271560e9990bc62d3
 That never helped.

Redhat have updated the Fedora Core 6 kernels, and kernel-2.6.20-1.2925.fc6 works fine on my FC6 x86_64 install. I /think/ that this corresponds to 2.6.20.3-rc1 in the real world because of the output of the following:

rpm -q --changelog kernel-2.6.20-1.2925.fc6 | head -10
* Sat Mar 10 2007 Chuck Ebbert <email address hidden>
- 2.6.20.3-rc1.

So maybe it has already been fixed in one of the later 2.6.20 releases and that's why FC6 is ok?

Do you still need photos? Will I just try and take as many as I can whilst its booting, or do you think the last one when it has errored will be the useful one? Or perhaps the transcript above was useful enough?

Cheers,

Alan

Out of date. Recent versions boot correctly.