Description of problem: If I boot the machine with no external USB mouse connected, the machine does not show the Fedora spash screen, and then there is no way to log into a session. Version-Release number of selected component (if applicable): Fedora 17, x86_64, kernel 3.5.4-1.fc17.x86_64 on an HP Pavilion dm1 laptop computer. Output of lspci for this card: 00:01.0 VGA compatible controller: ATI Technologies Inc AMD Radeon HD 6310 Graph icsATI How reproducible: Just boot the machine without the external USB mouse. Steps to Reproduce: 1. Unplug the external USB mouse 2. Boot the machine. 3. Actual results: No image at all. Expected results: To see the login screen at the end of the boot process. Additional info:
The assumption of the need of an external USB mouse was a mistake. The screen appears when it wants, the existence of an external USB mouse does not affect the appearance or not of the login screen. Something really strange is that this happens only with the last kernel (when I had the previous kernel this used to happen too), but if I use the previous one, I can see the login screen properly. Thanks, and best regards, HeCSa.
Upgraded to kernel 3.5.4-2.fc17.x86_64, and the errors remains. Randomly, the splash screen appears, or not, letting me log in, or not. When I cannot login, there is no other solution than hardware reset the machine. This is my "lsmod" output, just in case somebody need it to diagnose this problem: [hecsa@zentraedy-l helpdesk3]$ lsmod Module Size Used by fuse 77952 3 rfcomm 68709 4 bnep 19584 2 nf_conntrack_ipv4 14744 2 nf_defrag_ipv4 12673 1 nf_conntrack_ipv4 ip6t_REJECT 12939 2 nf_conntrack_ipv6 14341 3 nf_defrag_ipv6 18177 1 nf_conntrack_ipv6 xt_state 12578 5 nf_conntrack 83563 3 xt_state,nf_conntrack_ipv4,nf_conntrack_ipv6 ip6table_filter 12815 1 ip6_tables 26942 1 ip6table_filter snd_hda_codec_idt 70209 1 uvcvideo 76826 0 snd_hda_codec_hdmi 36103 1 videobuf2_vmalloc 12967 1 uvcvideo videobuf2_memops 13354 1 videobuf2_vmalloc videobuf2_core 31992 1 uvcvideo videodev 116207 2 uvcvideo,videobuf2_core snd_hda_intel 37587 2 snd_hda_codec 126728 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel media 20444 2 uvcvideo,videodev snd_hwdep 17650 1 snd_hda_codec btusb 23870 0 snd_seq 64844 0 snd_seq_device 14136 1 snd_seq arc4 12529 2 bluetooth 298929 24 bnep,btusb,rfcomm rt2800pci 18528 0 snd_pcm 97292 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel rt2800lib 56802 1 rt2800pci rt2x00pci 13995 1 rt2800pci rt2x00lib 66421 3 rt2x00pci,rt2800lib,rt2800pci eeprom_93cx6 13088 1 rt2800pci mac80211 521833 3 rt2x00lib,rt2x00pci,rt2800lib cfg80211 192203 2 mac80211,rt2x00lib crc_ccitt 12573 1 rt2800lib hp_wmi 18048 0 snd_page_alloc 18101 2 snd_pcm,snd_hda_intel hp_accel 25976 0 sparse_keymap 13526 1 hp_wmi rfkill 21384 6 cfg80211,hp_wmi,bluetooth snd_timer 28690 2 snd_pcm,snd_seq snd 79242 13 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device lis3lv02d 19487 1 hp_accel soundcore 14491 1 snd sp5100_tco 13697 0 input_polldev 13646 1 lis3lv02d r8169 61608 0 mii 13527 1 r8169 i2c_piix4 13694 0 k10temp 13126 0 kvm 412517 0 microcode 23435 0 uinput 17673 0 binfmt_misc 17463 1 wmi 18697 1 hp_wmi video 18936 0 ums_realtek 17949 0 usb_storage 56353 1 ums_realtek radeon 890783 3 i2c_algo_bit 13257 1 radeon drm_kms_helper 40253 1 radeon ttm 79760 1 radeon drm 259168 5 ttm,drm_kms_helper,radeon i2c_core 38177 6 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,radeon,videodev [hecsa@zentraedy-l helpdesk3]$ Thanks for your time & attention. HeCSa.
Assigning to a more appropriate component. Are you still seeing this issue with the latest F17 updates? If so, can you provide the information listed at https://fedoraproject.org/wiki/How_to_debug_Xorg_problems ? Thanks!
Since some of the last updates, this issue no longer exists. You can safely close this bug. Thanks, and best regards, HeCSa.
Great, thanks for getting back to us, and sorry about the delay - I just noticed there were a bunch of bugs filed against xorg-x11-drivers and went through them. In case you have problems in future, it's best to file bugs with graphics against the relevant xorg-x11-drv component - so, for an ATI/AMD adapter, xorg-x11-drv-ati. Thanks!