On 09/30/2014 04:19 PM, Ed Greshko wrote:
On 10/01/14 06:14, jd1008 wrote:
On 09/30/2014 04:04 PM, Ed Greshko wrote:
Now the you have connectivity and have taken this to the list.... I should
tell the list what has been found so far...
As I said, I'm fairly certain you're having problems due to this in your
Xorg.log
[ 29.862] (EE) [drm] KMS not enabled
[ 29.862] (EE) open /dev/dri/card0: No such file or directory
[ 29.862] (WW) Falling back to old probe method for modesetting
Looking down further you see it is falling back and using the VESA driver and
not nouveau.
[ 29.863] (II) Module int10: vendor="X.Org Foundation"
[ 29.863] compiled for 1.14.4, module version = 1.0.0
[ 29.863] ABI class: X.Org Video Driver, version 14.1
[ 29.863] (II) VESA(0): initializing int10
[ 29.864] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 29.919] (II) VESA(0): VESA BIOS detected
[ 29.919] (II) VESA(0): VESA VBE Version 3.0
[ 29.919] (II) VESA(0): VESA VBE Total Mem: 14336 kB
So, that is the problem.... That, I believe, is often caused by another
driver being loaded and interfering in things.
It can also be caused by having a parameter set in the boot line....but I see
that is not the case as you have...
[ 29.631] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.3-200.fc20.x86_64
root=UUID=691db345-e126-4dc7-8846-95545a9422f7 ro
vconsole.font=latarcyrheb-sun16 rhgb quiet quiet splash acpi=off
Sooo....
What is the output of "lsmod"?
$ lsmod
Module Size Used by
fuse 91446 2
ip6table_filter 12815 0
ip6_tables 26809 1 ip6table_filter
ebtable_nat 12807 0
ebtables 30758 1 ebtable_nat
<snip>
As you can see from the output of lsmod the "nouveau" is not being loaded.
We've established, off list, that there is no blacklist-nouveau.conf file in
/usr/lib/modprobe.d either. You've rebuilt your initramfs and still don't get nouveau.
At the moment I can't think of what else would cause the issue.
Which was my intent - I do not want the non-fedora and non-free nvidia
packages from rpmfusion.
But the screen is being treated as a 1280x768 which is strange, and it
is not clear which
"wrong" driver is being used instead of the original one when I upgraded
to and booted fc20.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
