JB <jb.123abc <at> yahoo.com> writes: > > > > Hi, > > > is that what you are asking about ? > > > http://fedoraproject.org/wiki/Common_F13_bugs > > > 5 Hardware-related issues. > > > Miscellaneous graphical problems. > > > To use the vesa driver during installation, ... > > > > > Followed the instructions, but the screen is still not correct when > > trying to use the Live CD for FC13. > > I added the xdriver=vesa nomodeset kernel variables to the end of the > > line (which was long enough.) Should I be placing them somewhere else > > in the line. The FAQ states to add them. > > > > I'll try booting with Disk 1 and see what happens. (It did work for FC9 > > but Disk 2 was corrupt as well as Disk 4.) > > > > James McKenzie > > > Hi, > I tested it with f12 live-cd. > > You will get a boot display like: > ... going to start in 7 seconds ... > quickly hit any key, and you will get a menu display like > Boot > ... > Memory test > ... > hit Tab key to display kernel line > add to the end of kernel line > xdriver=vesa nomodeset > and hit Enter. > > This will boot and set up your desktop. > > Open a terminal and input 'su'. > > verify that kernel actually took your vesa parameters > # cat /var/log/dmesg |grep -i vesa > Kernel command line: ... xdriver=vesa nomodeset ... > > verify that vesa driver is utilized by Xorg > # cat /var/log/Xorg.0.log |grep -i vesa > Kernel command line: ... xdriver=vesa nomodeset ... > ... Driver "vesa" > ... > (II) Load Module: "vesa" > ... > > You are set. > JB > Sorry, I was too fast ... It did not work with f12 live cd. I found a ref to this document: http://fedoraproject.org/wiki/Fedora_13_QA_Retrospective ... adamwill - a validation test for booting live image with 'xdriver=vesa' to get VESA driver; I realized after release we don't test this and aren't even sure if it's still present / meant to be present ... I emailed this person (Adam Williamson works for Red Hat) and I will post as soon as I get an answer. I tried with f13 live cd - it interrupts its process on tty1 and leaves it in an undetermined state (text screen), without any info for a user about what happened, but when I switched to tty2 (tty3, etc) I was greated with a text login screen, where I input root (perhaps hitting Enter was enough ...) and was let in with a bash root prompt #. I also tried to find an anser on IRC #fedora - I talked to a guy who suggested rdblacklist=i915 option (my intel graphics card module) in the hope that this would force us into vesa (default) mode, but it did not happen. So we will not speculate about this feature and instead wait for an email. JB -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
