Created attachment 107464 [details] system logs Description of problem: Kernel regression: the system uses VESA due the following error in /var/log/Xorg.0.log (EE) [drm] KMS not enabled with older kernel 3.11.10-301 the bug did not happen. I also tried booting the system with option "nouveau.config=VBIOS=PRAMIN" but it did not solve the problem. ===Kernel Version=== kernel-3.16.2-200.fc20.x86_64 ===Fedora bugreport=== https://bugzilla.redhat.com/show_bug.cgi?id=1141898
Can you attach a dmesg when booting with nouveau.config=VBIOS=PRAMIN No need to compress it (that just makes it harder to see in a browser, these files are never big enough for it to matter).
Created attachment 107513 [details] dmesg using nouveau.config=VBIOS=PRAMIN # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.3-200.fc20.x86_64 root=UUID=d8b272ae-a143-4600-9f50-7a5b31c35293 ro vconsole.font=latarcyrheb-sun16 nouveau.config=VBIOS=PRAMIN LANG=it_IT.UTF-8
Created attachment 107514 [details] Xorg.0.log using nouveau.config=VBIOS=PRAMIN
(In reply to Germano Massullo from comment #2) > Created attachment 107513 [details] > dmesg using nouveau.config=VBIOS=PRAMIN > > # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.3-200.fc20.x86_64 > root=UUID=d8b272ae-a143-4600-9f50-7a5b31c35293 ro > vconsole.font=latarcyrheb-sun16 nouveau.config=VBIOS=PRAMIN LANG=it_IT.UTF-8 Oh right. nouveau.config=NvBios=PRAMIN See http://nouveau.freedesktop.org/wiki/KernelModuleParameters/ (Also, just dmesg is relevant... nouveau drm isn't loading so X never has a chance.)
(In reply to Ilia Mirkin from comment #4) > Oh right. > > nouveau.config=NvBios=PRAMIN I will do the test in next message. Are there any other tests I can execute? I am asking that because the machine is not mine so everytime I have to meet the owner to retrieve logs.
I have no longer access to the affected machine, nor I had any feedback from component developers. I close the bugreport as wontfix
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.