Tobel wrote:EE:
AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
Disabling Keyboard0
Possibly an extraneous keyboard definition in your Xconfig - if your keyboard works fine then not a problem!
Tobel wrote:WW:
Unknown vendor-specific block f (multiple times throughout the log)
Probably a graphics driver issue - though might be something random but graphics drivers are the worst for this

Tobel wrote:Those are the only types of messages I see with the EE/WW prefix.
That was the xorg.0.log, there is also a .1 log. Not sure what the difference is.
Log rotation - the .1 log is an older .0 log ... you may have an xorg.log as well (that is the newest) depending on how your logs rotate.
Tobel wrote:The .1 has a few more
EE:
Unable to locate/open config file
Open /dev/fb0
Something is trying to open the floppy drive (I think) - strange, but since it's not in the newer one mayhave been fixed by an update - how often do you reboot?
Tobel wrote:WW:
Falling back to old probe method for vesa/fbdev
Although this is an old message that isn't a good sign ... VESA is a graphics standard so outdated it is barely supported any more, though I believe Linux supports it becauseif there are any graphics issues it will drop back to that standard since every piece of hardware and software built in the last ten years can manage it... it may be this that causes a lack of graphics memory and/or placing grpahics memory in the system RAM.
Can you have a look in the xorg.log's again to see if you can find where OpenGL and DRI start up correctly? If you can't find those then it may be that you've a problem with using the wrong graphics driver that is then causing your graphics system to drop back into VESA mode (which OpenGL won't run under without a large mini-computer to power it).
If you can identify exactly which graphics chip-set you have (the command "sudo lshw -C video" (give it a minute) will give you all the details you need if you have it on the system - else try "lspci" which definitely should be there) - then you can trace a driver for it for your system - usually just googling for it will turn up something and then sift for a reputable site to grab it from.
I hope this is of help - any queires feel free to reply again

River
