3c9424e7-ec4f-4814-afdf-2c18951bf474__www.smolts.org pub_36ce35ea-9740-4427-be66-ab61e6898dc6 IIRC, anaconda reported v15.25. Installation vmlinuz and initrd.img timestamped March 30 loaded via Grub for HTTP installation from mirrors.kernel.org. Steps to Reproduce: 1.Try to install on i845G connected to CRT with bad EDID Actual results: 1-hang a-first try using vga=791 on cmdline happened on location and time screen deselecting UTC clock b-2nd try using video=1024x768 on cmdline happened on final screen, after report of 188 of 188 packages completed, and display of "performing post-install configuration". c-3rd try locked up in partitioning -> device selection Expected results: Installation runs to completion, then reboots.
Dup of the bug 693480? Felix if you start the installer with 'sshd' on the kernel bootline, can you ssh into the installation after the lock up occurs?
(In reply to comment #1) > Dup of the bug 693480? I don't see any connection between this and that. Partitioning and formatting I do before starting any Linux installation. > Felix if you start the installer with 'sshd' on the kernel bootline, can you > ssh into the installation after the lock up occurs? On try d with sshd appended to cmdline, anaconda started at post-install configuration, then finished. On try e with appended: nodmraid nofirewire noipv6 noselinux selinux=0 nousb resolution=1024x768 splash=verbose sshd Anaconda ran start to finish without any apparent problem. :-p Before rebooting I tried 'ssh 192.168.0.22', but got "ssh: connect to host 192.168.0.22 port 22: no route to host". I see no option here to undo NEEDINFO.
(In reply to comment #2) > (In reply to comment #1) > > Dup of the bug 693480? > > I don't see any connection between this and that. Partitioning and formatting I > do before starting any Linux installation. The connection could be a random hang. > Anaconda ran start to finish without any apparent problem. :-p Before rebooting > I tried 'ssh 192.168.0.22', but got "ssh: connect to host 192.168.0.22 port 22: > no route to host". The machine needs to be connected to a network and the interface must be accessible. If this is a DVD installation try appending ksdevice=eth0 (or whatever name of the device is, see 'ip addr' on tty2) to the command line.
(In reply to comment #3) > The machine needs to be connected to a network and the interface must be > accessible. If this is a DVD installation try appending ksdevice=eth0 (or > whatever name of the device is, see 'ip addr' on tty2) to the command line. Should any of that be relevant for the type installation specified in comment 0 (HTTP)? F15 is now running. I need to do other things and leave further installation attempts for some later time.
Bug 692293 likely has same root cause.
*** This bug has been marked as a duplicate of bug 692293 ***
Turns out this has nothing to do with EDID. With good EDID it comes up in the display's preferred 1600x1200 mode, and still locks up at random times. I tried i915.modeset=0, which didn't help. I tried switching to a tty prior to lockups more than once, and each time was irrecoverably greeted by black screens. Text mode is useless, because it offers no option to select the correct partition to install to. Same machine is happy to run F14, openSUSE 11.4, and several other distro versions.
F17RC? installed without a problem to the comment 0 machine 2 weeks ago.