Hide Forgot
Description of problem: I installed it first in my desktop x86_64 and noticed it, but i got too busy with other bugs. Today i installed it to my netbook (i386 via unetbootin) and it happened again, so i reported it. I set the severity to urgent because it is in the iso image. After installing F15 Alpha & rebooting, at firstboot the mouse does not work (there is no pointer). Version-Release number of selected component (if applicable): firstboot 1.117-2.fc15.i686 How reproducible: allways (i installed f15 alpha two times, one in each machine and it happened it both machines). x86_64 (usb mouse) & i386 (netbook, touchpad) Steps to Reproduce: 1. install (custom partition, only / & /boot) 2. keyboard is set to spanish 3. Actual results: keyboard does work correctly mouse does NOT work (no pointer) Expected results: mouse & keyboard Additional info: * using live-cd-kde
I tried this with dvd install, gnome live cd and kde live cd, and I cannot reproduce your problem. But still, I don't think firstboot has anything with the mouse not working. The problem must be somewhere else.
I just tested it again in another machine (also 64-bit) and effectively there is no pointer and the mouse does not work for firstboot. (before & and after, it does work). I was unable to reproduce it with virtual machines. # sha256sum Fedora-15-Alpha-x86_64-Live-KDE.iso 7615063d65354c010e72ac4e3ab630b05ae1ece0e1b39d2b5a04d16eadb24bf3 Fedora-15-Alpha-x86_64-Live-KDE.iso ----- PC#1 AMD PhenomII AM3 PC#2 AMD Athlon64 S754 LAP#1 MSI Wind U100 ATOM N270 ----- this is the mouse: Bus 003 Device 004: ID 0458:003a KYE Systems Corp. (Mouse Systems) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0458 KYE Systems Corp. (Mouse Systems) idProduct 0x003a bcdDevice 1.00 iManufacturer 1 Genius iProduct 2 Optical Mouse iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 HID-compliant MOUSE bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 62 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 10 Device Status: 0x0000 (Bus Powered)
And when GDM is run after firstboot, is the mouse working there?
i use KDM. yes, with KDM it does. the mouse does not work (there is no pointer) only during firstboot. before and after firstboot, there is no problem. i will test again with the beta. (there is no other way to test it that with an updated iso?
Hi, can you please try the following: During the first boot when mouse is not working, switch to vt2, with ctrl+alt+f2, login as root, and reboot the machine. After the reboot firstboot should run again, and let me know if the mouse is working or not the second time. Thanks.
> During the first boot when mouse is not working, switch to vt2, with > ctrl+alt+f2, login as root, and reboot the machine. > After the reboot firstboot should run again, and let me know if the mouse is > working or not the second time. Firstboot detects the input device if you boot the box a SECOND time, YES. This was tested on a MSI Wind U100 netbook, with a selenic? touchpad. ---- In the first boot, the input device never shows up, on al F15 instalations i ever performed. ---- This was tested with the same install media (alpha, kde-livecd)
Update: Installed F15 beta on both my desktop and netbook and the issue was not present, so it seems fixed. Firstboot pointer/mouse worked as expected.
F15 was released i do not experienced the issue whatsoever. Since F15 is released and the issue is fixed should the bug-report be closed?