Bookmarks Bookmarks Digg del. October 12th, I just tried using the analog port with the same results. Let me know what I can do to help. If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the ‘version’ to a later Fedora version.
|Date Added:||5 May 2009|
|File Size:||12.70 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
There appear to be some discrepancies between this and some data interpreted by X. But the solution provided in: Please wait for system to check BIOS file. See full activity log.
Results 1 to 6 of 6. I’m especially interested in the dmesg output.
ASUS M2A-VM – coreboot
However I had to roll-back to 7. Having a problem logging in? If it is not in the man pages v, the how-to’s this is the place!
X does start, with the Fedora logo, then quits with this error. Not that surprising as a garbage is spewed by a kernel module and these options apply on an X level. Version-Release number of selected component if applicable: Using vrefresh ranges from config file. Click Here to receive this Complete Guide absolutely free. After switching the affected machine to Fedora 16 with 3. Bookmarks Bookmarks Digg del.
Asus M2A-VM +linux
Errors are no longer displaying. If you’d like to contribute content, let us know. Also, I am upgraded to Ubuntu Are you new to LinuxQuestions. In Red Hat BugzillaFedora fedora-redhat-bugs wrote on No kernel params or MB configs that I have found will allow 64bit to work.
This explanation is from the official ASUS website. I think you’re right, I have both bugs.
They hope these examples will help you to get a better understanding of the Linux system and that you lunux encouraged to try out things on your own. Could you please test the fixed kernel on your system and provide me with the results? Thanks again – I was pretty stuck before I found these comments.
BTW – recorded in Xorg. Brad Figg brad-figg on If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on “Clone This Bug” top right of this page and open it against that version of Fedora.
Reset to the default setting of the bios and Make sure when updating using ez flash, no one should interrupt the process. Bug Watch Updater bug-watch-updater on I’m not using the nomodeset kernel option, yet my server crashes.