Description of problem:
no keyboard after anaconda initial screen (not test media screen)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot Fedora-13-Alpha-x86_64-DVD
2. skip media test
3. welcome screen comes up and no keyboard or mouse control at this point
no keyboard or mouse
keyboard and usable mouse
tried every combination of nomodeset and vesa driver, no joy.
$ lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600 Series]
Same result using Gateway GT5426E machine (AMD Athlon x64 CPU), with NVIDEA GeForce 6158SE nForce 430 graphics controller.
Same result with trying to install f13 alpha rc1.i386 on a dell d620 laptop.
same result in any virt-installs.
Set it as F13 alpha blocker bug according to Alpha Release Requirements: 6. The installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
I think this is because of the new X server input configuration system requiring files that anaconda's image building scripts are not accounting for.
This is what I'm thinking of:
* Tue Feb 16 2010 Peter Hutterer <email@example.com> 22.214.171.1241-1.2010208
- Update to today's git master (1.8RC1)
- xserver-1.7.4-reset-sli-pointers.patch: drop, upstream
- Enable udev config, drop hal.
- Require system-setup-keyboard (renamed fedora-setup-keyboard)
We probably need to add back in our patch that drops hal and add /etc/xorg.conf.d/* to scripts/upd-instroot.
Same here. Machine is a HP d530, keyboard is a USB keyboard,
Mouse is a USB mouse with adapter to plug into the PS/2 mouse
Yes, this is likely because of the migration from hal to udev for input device configuration in X. Why does anaconda need to do special stuff with input configuration? Adding Peter Hutterer to CC, he can advise on the transition.
Fedora Bugzappers volunteer triage team
Fixed by 49f12d62f5d9c5cf213a983023000be988ffffc1, will be part of anaconda 13.29.
Oh, but there also needs to be a fix in x.org, see #566396.
(In reply to comment #8)
> Yes, this is likely because of the migration from hal to udev for input device
> configuration in X. Why does anaconda need to do special stuff with input
> configuration? Adding Peter Hutterer to CC, he can advise on the transition.
Thanks for the CC, I missed this one.
before the hal→udev transition we had most of the X server configuration in HAL's fdi files (e.g. the selection of drivers). now this configuration is only in /etc/xorg.conf.d/. Without it the server cannot detect what a device's driver should be, unlike graphics devices we don't have a default driver detection mechanism in the server for input devices.
so we at least need 00-evdev.conf so that the evdev driver is assigned to all input devices. this is essentially the same result as the 10-x11-input.fdi previously used.
This issue still happens on anaconda 13.29 of F13 alpha RC2 (i386).
Still a problem on F13 Alpha RC2 x86_64.
Indeed, the problem still persists in RC2, please see bug 566396.
anaconda-13.30-1.fc13 has been submitted as an update for Fedora 13.
vnc install succeeded. Remote syslog and selinux=0 were also specified. All worked.
anaconda-13.30-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2803
works in 13.30.
verified working on anaconda 13.31 i386 platform. X86_64 install exited for segmentation fault before stage1.
Multiple reports that this is fixed, let's close it.