Bug#264715: Package: installation-reports
Package: installation-reports
Debian-installer-version: August 9, 2004 (RC1 Installer CD i386 image)
uname -a: Could not reach shell
Date: August 9, 2004 at 9:45pm PST (started)
Method: Installed via RC1 Installer boot CD image through NAT'd network (Mitel
e-smith server), static IP ADSL line, no proxy.
Machine: DFI LanParty nForce2 MB (homebuilt machine)
Processor: AMD Athlon 1.2ghz CPU
Memory: 785,908KB
Root Device: IDE /dev/hda
Root Size/partition table: Single 17gb logical partition on dual-boot Win2K machine
Output of lspci: Could not reach shell
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
1. Booted, boot messages were going by, right after hardware detection the
screen went blank. No recovery possible. Manually rebooted.
2. Booted, boot messages were going by, right after hardware detection the
screen went blank. No recovery possible. Manually rebooted. Vowed to remember
recovery mode next time. ;)
3. Booted recovery mode, boot messages were going by, very quickly screen went
blank. No recovery possible. Manually rebooted.
4. Booted into Windows to make sure my other partitions were still okay. They
were. Are. Whew.
I am currently assuming that the issue is my NVidia GeForce MX200 DVI-output
video card and Gateway FPD1500 LCD monitor, which many Linux distributions have
historically had a problem with (as the monitor reports its' settings
incorrectly). XandrOS and Linspire have no difficulties with this video
hardware, but Suse 8.2 and Debian woody did (both required manual modification
of X config to work). I assume that if I were able to boot Debian into console
mode, I would be able to work around this issue -- sadly, recovery mode does not
appear to allow this. Would be grateful to learn that I am wrong.
Reply to: