System: IBM ThinkPad A30p
When starting the fc4test1 install (regardless of the mode), the last thing I
see is "running /sbin/loader", after that the screen goes black, and nothing
Well, actually nothing happens until I luckily happened to press "Fn+F7" which
on this laptop cycles between LCD/CRT/LCD+CRT video out.
The system seems to be left in the LCD mode (but as said, with a black screen):
the first Fn+F7 switches to CRT (which I don't have connected here), the second
switches to LCD+CRT, the third back into LCD only, etc. In the two latter
modes, the media check UI is visible again. But as said, this requires hitting
Fn+F7 a couple of times, the initial LCD mode when starting the installer is
blank for some reason.
*** Bug 151481 has been marked as a duplicate of this bug. ***
Does booting with 'linux nofb' help?
Yes, that works. In case it's useful, the video chip here is:
01:00.0 Class 0300: 1002:4c59
Flags: bus master, stepping, fast Back2Back, 66Mhz, medium devsel,
latency 66, IRQ 11
Memory at e0000000 (32-bit, prefetchable) [size=128M]
I/O ports at 3000 [size=256]
Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
Capabilities:  AGP version 2.0
Capabilities:  Power Management version 2
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY
(prog-if 00 [VGA])
Subsystem: IBM ThinkPad A30/A30p (2652/2653)
Problem persists in FC4t2.
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
Problem persists also in FC4t3 and FC4 final.
FC4 Final. All disks pass media checks. On Toshiba Satellite Model 1805S,
when installer tries to start up in X mode, I get a blank white screen. The
cursor appears briefly then blinks out. Nothing further happens.
I powered off and proceeded with a Text mode install which appeared to
succeed, but following reboot I'm left with a blank screen again and cannot
seem to escape out of it into console mode.
I'm launching the installer with the following command-line:
linux nofb idebus=66 vga=791
In the meantime ... I'm going back to FC3 ...
FC4 is now 2/2 in fatal installation failures for me (IBM 300PL with S3
video, Toshiba 1805S notebook) ... I won't even try it on an old P233 ...
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
Hm, I don't know how to test FC4 _installer_ issues using this update...
hmm, tricky. your best bet is probably going to be checking whether rawhide has
been fixed or not, and waiting until FC5. (Or, install FC3, and upgrade to FC4
Both involve pain of some degree sadly.
http://fedora.isphuset.no/ contains an unofficial Fedora 4.1, which may get you
up and running, as it has a install kernel based on one of the errata kernels.
Same problem with the isphuset ISOs.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Sorry, I'll have to just bump back from NEEDINFO, see comments 13 and
earlier. OTOH I see isphuset has a new FC4.2 five ISO set which is said to
contain 2.6.13-1.1532_FC4, but I don't feel like downloading 2.7GB at 25kB/s
Tested with the isphuset FC 4.2 ISOs, problem persists (2.6.13-1.1532_FC4).
Due to the overhead involved in creating new ISOs (which is what would be
required for fixing bugs seen at installation time that don't have workarounds),
this bug has been closed.
For more information and suggestions, please see bug 169613
Seems to be fixed in FC5test1.