Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I upgraded to F18 a few weeks ago. I think was working OK. I ran several updates and was up to 3.8.3-203. I think it was the next time I powered up after this update that the problem started. It starts to boot up, but, stalls when it gets to the point where there is an f in a circle in the middle of a blue screen. Also,I there was a problem shutting down one time. I don't remember if it was the time before started. There were errors when shutting down and the system hung. had to shut down with the power switch. I tried to boot with 3.8.3-201 and 3.6.2-206, but, it still had the problem. I saw other people had similar problems and it seems to be a video driver problem. I could get into a terminal by pressing cntrl-alt-shft I. I tried running lshw at the command prompt to find my video card info, but the letters that showed up on the screen weren't the ones I entered. I.I can also get in the grub command line, but, lshw isn't one of the available commands. I have a Leno voice r61i laptop.
Can you give us a bit more information on the hang during boot up? Hit escape as soon as the graphics come up to see the console underneath. A picture of the output might be helpful.
Created attachment 716276 [details] Picture of where console output stops after pressing esc Here is a picture of the console output after it stops when I press the escape key when the first graphics show up during boot. Hope this helps. I have another picture of the same thing, but, I think this is the more legible of the two.
Did the picture help?
No, unfortunately it didn't. Please remove 'rhgb' and 'quiet' from the kernel command line and see if you can get more information. You might also verify that you have a corresponding initramfs file in /boot, that is it of similar size, and that it is listed in the 'initrd' line of the grub configuration file for that kernel.
Thanks for the reply. I had surgery done last week and I'm a bit backed up. I hope to take a look this weekend. I do have a question though: could you elaborate on "remove 'rhgb' and 'quiet' from the kernel command line"? Thanks
(In reply to comment #6) > Thanks for the reply. I had surgery done last week and I'm a bit backed up. > I hope to take a look this weekend. > > I do have a question though: could you elaborate on "remove 'rhgb' and > 'quiet' from the kernel command line"? > > Thanks It took me awhile to find the time to do this. I pressed e at the grub boot menu and edited out "quiet" and "rhgb". I get this error message: [FAILED] Failed to start Wait for Plymouth Boot Screen to Quit. See 'systemmctl status plymouth-quit-wait. service' for details. And I took a couple pictures of the screen
Created attachment 741705 [details] Error and top part of screen where it stops
Created attachment 741706 [details] Bottom of screen where it stalls
Are you still seeing this with 3.9.8 or newer? If so, what kind of graphics card do you have?
I can't boot up into X or as far in command line as is needed to get my wifi network connected. I'm still at 3.8.3-203. Right now I have a hard disk in it with windows on it. This is the information I get on the graphics card: Adapter Type Mobile Intel(R) 965 Express Chipset Family Adapter Information Chip Type: Mobile Intel(R) 965 Express Chipset Family DAC Type: Internal Adapter String:` Mobile Interl(R) GMA X3100 Bios Information: Intel Video BIOS Total Available Graphics Memory: 358 MB Dedicated Video Memory: 0 MB System Video Memory: 64 MB Shared System Memory: 294 MB
Created attachment 768086 [details] Xorg.0.log file New Attachment
Created attachment 768089 [details] Bootup log file Another new bootup log file
[ 100.124] Parse error on line 1 of section InputClass in file /etc/X11/xorg.conf.d/00-enable-taps.conf "›Lºû#ßWf‰þe†÷ÊlÊ™#Î#ç?óÁ#àBðCƒ™í]Äôˆ—눃^4ÓpXô=Eá?·è¡.„ü#z»ÐÓf §©ÀYÝo#?#;¼3]#úô#^ä½¼#Ú?^{ïTbtî,Óµ" is not a valid keyword in this section. [ 100.125] (EE) Problem parsing the config file [ 100.125] (EE) Error parsing the config file [ 100.125] Can you remove /etc/X11/xorg.conf.d/00-enable-taps.conf and see if things progress further? Also, can you just attach the messages as a plain text file, not as a zip archive? It fails to extract here.
Created attachment 769453 [details] Boot log july 5 after removing /etc/X11/xorg.conf.d/00-enable-taps.conf
Created attachment 769454 [details] Xorg.0 log file july 5 after removing /etc/X11/xorg.conf.d/00-enable-taps.conf
Created attachment 769455 [details] messages log file july 5 after removing /etc/X11/xorg.conf.d/00-enable-taps.conf
Created attachment 769456 [details] older messages log file not zipped up
Created attachment 769457 [details] Older dmsg log file not zipped up
I removed /etc/X11/xorg.conf.d/00-enable-taps.conf by renaming it. I think things might have gone a little further. I've attached the latest log files after doing this and also the older files that I sent zipped up. I removed quiet and rhgb and added a 1 to the grub boot file so that it would boot up the the command prompt as root.
(In reply to Tom from comment #16) > Created attachment 769454 [details] > Xorg.0 log file july 5 after removing > /etc/X11/xorg.conf.d/00-enable-taps.conf [ 688.953] Parse error on line 1 of section InputClass in file /etc/X11/xorg.conf.d/00-enable-taps.conf "›LºûßWf‰þe†÷ÊlÊ™ÎçóÁàBðCƒ™í]Äôˆ—눃^4ÓpXô=Eá·è¡.„üz»ÐÓf §©ÀYÝo;¼3]úô^ä½¼Ú^{ïTbtî,Óµ" is not a valid keyword in this section. [ 688.955] (EE) Problem parsing the config file Please remove the file entirely, or move it to a directory not under /etc/X11. You seem to have some sort of corruption in a number of files on your system. This can be seen in your messages file with lines like: Jul 5 20:07:46 localhost gdm[652]: /etc/profile: line 1: `¼5#177Ž[?_{D½»Ç™ƒ®¨TªJóûí.õ•î„tRøŸ;V!DiÀ\º]#021}¢ÖùÓ:åá»2g•ìñà#006!DqHwÊ3(#017 #036Q#034|#0372Ñ#034ò¸’kÛ#004#013σ#027#024êé3Cz*ù½Â—±ÿ…”ó#010¹#031ÒKÉf`%Á'Ðû#030½²ð½Á> žŸ~èÏ@Ÿð#013é#017?#032^²Ÿ#0312€ú#003Á'Á§@Ü*äiägÀgÁÁàs ¸©#031ò#002ò#020Úí§dýV=3äEx;Ù#037ÒGÈKðÍ„æ¡23d¨ðÞ#015ðÍ#025š!Ì£×>HÙ#037Ü=ä#025%™!¯‚¯Qÿm%k_3C^‡#037#011OÖ#017y#003þuxí7obo#030ø#026z2/*mZî#036ŸµL¹{|ÊT[ÏÎâCëýñÁŸ_ÕÙYºÓS]{–#011Z©»`eñ7#026O+œ{_Åwk#016ìšõSò'›¬#032DS•¿ìêÖ#003#004ß#013^“á›UNK³¾›Šw6·*ú#027#030#027áqÛ*gÑ?#007_C¡Yå#034üNxÜ«Êßð[ák£/nmV#021·6#002¥_fÀFÊ¥]³Ê%ê'Q_²ŠYEÿRCÜÇÙeª\‘úÚmªüƒ½«à¿à5ð:x#003Ô—¢#022Ž#036ÏWð\Š:#017•ƒçk#017ïB%ëß3šU¼R#036òšBãæaô}‚#022M#036³j#011ä’2N¯deýd¾Y5^ÜÄ9‹W-#005/á¡#036#035µÜå™í£”»<³:Ŷk»K»Öef–y§l߯>±¿ùö7>¸Ã]Þ[?oÓÌ#026±•–„#024mŽ|³†Ý4I=ô[»ú#177Ý%ô;–C»#013Ù%t#035üiUϹ#024#011Õ7&²ák(4C׃¸a(n9»#0367#010ÍAÞ$X#0267#011ÝL{#037)^ÿË#014ÕGý‰ðlÒ¡ú¨o³ù†æŠÝPɶf#025Ü!ô#007x9K›¡?"ï#177#002#177#006ÅíÍÐ]ô«³â=#036ÍïFï#027…FÑ4)ׇ›Ð<ÊóÁ_]åÜoöê¬Ë®#024Êó5Þ¡¢oï|–#033#014[• 8PeeÛ#015F>0aö¬þž¥³«g¬_öä#021+#033;›ä{;<ئ}§#025#016mº#0227ç-{HOH7Â8Z:W’¥á{2L‰"Ç[ÃzÁ_¤;$ó0mÍ&ŒÍ&¬/öúýAÕm#031Æf#022ö$üSà ÚÑÉše#016{#032~‚Òs²BØ3ðãàµþ³ðcák(4Ãx¡ƒOú¥çÊ#014c<¡,#177#030›T˜D¡#0316„ú/‚/²<fØËȯ€¯‚l*¾8%[§n…Fb#001åzsÉ¥¼#033ü#033"k7' Jul 5 20:07:44 localhost ip6tables.init[585]: /etc/sysconfig/ip6tables-config: line 1: `¹½±Û#007¾™ï˜íFûu?ÊûÓÞ#017Jv#036éÉå;fïZxâ7a*ú™ðø{î@øOá‰ßÜ'áçÀ[~mmKßï#177Rp‹ò+{[ÚýÉèÌY#025ÿšŸÐéñ™¯Åg¾¤C×Ú–¶lî±mvAQµ7·iq4`ú8Ë#024aµ]_ÚJúòx#036WÍ#030Ûõíþ#0254‹;nÏ’î8o„#02371¶Ë0íßJý\—#033nÿ#016»ëÀlp=¸#001»#022f#036}X×÷]·sgÊY†¡jø¿Ü#8i‚mÇž†Wÿ¼\úá˜[y=«ý½¬ÿ»Õ¬t-3oMƇ‡®»#021üGÌ¡Ä?#026Ü^1~¢Uƒì±“#007vœÝùEÛœÇØY†n}¢d§#035¼¾Fé#013O#026Ü©ïß#022=zšw’uw’uw’uw’uwVÄ.Yv'Yv§¶‹×í$›îäÛ#004#037YOß¾ÞY#005o™K¿Ä[Nv©¡¦éd—mÞž¦Ùß-8»aò›§Kvß÷MЗ¡oÝ1M+ž©4ªÄs?–k1óöú©Ÿ®îeÕ ‰îÒß}io!)-¶fÙú#030‹½LW®’ß\íâA#002ßdx’ù®¡è¿#016O²Ýõ2¼žFÝþ+JÏØÉtìzUä]¯bÇØõ#006ò›à0Ð#032¦õ1v#015Ç~¨’wu;·—OÂ[ö¬`»2ßòZ#033;©ñÚÓwmT™7>#034#020Ñm]þÌ£gFÏ»cú.ÌJüqóûõóÛLnVÿö¶F‰–)öšÝúö¬kúv#023#004»u#020èé‹RÝ0vëÛ²ŸÑ-rôn}É6#020þ~ôs#030žìEÎÃã»7I¹{zvo¦#036{øîÈÒ#017c÷6dÉqÆîíÈ?‚;@}‰%Ëã<ç³Z#177©ò—ÒSÏi•hýhé#037òíi}´ôšú6oOkt̵}O~0}Íî#033]½·òSþ¸cZcÞ#032#026^)eËéjÝÂ;üÝ1ã#035«êÛÒlžõÿÖÇÈ{#027|OPßßÉ#033ÇtÜP¼¶iä#031è›àx)×Gß¼#011ðïSÿ‚”“PŒ¼#017(·#023‰Ýþ$…Ζ•÷¡ð9LŸ>êçMÆ^¡èëÇmò¦ˆ~ÞT—iÅdm?þˆþ#026à0vJQ#177:ö÷Áß#005?CdƧí#030y3Ñß…~ú³àey+̼ٔ'P®ÝU×›CùG‚î÷¸åIr2foEÏŠ#036ëcäÙ¡baf¦`Þ|…þ~.#020~6îç~_[ÞÇÔ“dmä}Šœ$¨_#036œ·#020~#021(aeä%‹œ(ódL#177PÉNû®·¾#032yŸS?#005üBpöo' I don't see any kernel problems here specifically. You might try looking for corrupted files in /etc (and possibly elsewhere) and fixing them.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days