How to get qingy?
First you need a working DirectFB. I'm recommending Uvesafb but if you have some graphical issues with it use vesafb. Qingy may not work with KMS.
https://wiki.archlinux.org/index.php/Uvesafb#GRUB2
I added a warning to the uvesafb archwiki page, noting that disabling KMS may break xorg.
It's worth noting that I do get the black screen bug as described there and that disabling KMS does in fact fix it but at the cost of breaking xorg - it is not worth it to use uvesafb.
]]>Just used it 4 days ago on a brand new install that wouldn't run "startx", which was me rushing to get things done.
I'd like to know the details of that. There's no way Xorg -configure would know more than X's auto-detection.
@atomicpookavirus: Well, that just confirms what I said, turning off KMS is never a solution. Now all you need to do is reinstall xorg-server and xf86-input-synaptics, so you'll get back the config files you deleted from /etc/X11/xorg.conf.d
]]>It's intel mobile 915GM/GMS/910GML Express Graphics Controller
]]>Just like disabling KMS, Xorg -configure is also *never* a solution. It's a relic of the past, it'll create an outdated config that won't do anything different than the auto-detection stuff already does anyway.
Just used it 4 days ago on a brand new install that wouldn't run "startx", which was me rushing to get things done.
]]>I don't see how turning KMS off would let X start, unless you have one of the fallback drivers installed, and your first log says that you don't. BTW, that link still doesn't work, so we still have no idea what kind of hardware you have. And now we have X mysteriously starting, so you must have changed something since you last posted an X log, but we don't know what. You need to be a lot more detailed in providing info. We don't have crystal balls, we can't know what's going on unless you tell us. In great details.
]]>Fbterm still works fine with KMS enabled. Qingy is still broken. It flickers when input is entered then goes black. Same behavior with v86d uvesa loaded.
]]>I'm not sure how to paste code into the web forum in text mode. I just use curlpaste. No doubt there must be some way to pipe the output of lspci -v | trepidation graphics into elinks. I am writing on an android tablet that has annoying auto correct, making grep-into trepidation and otherwise thwarts writing code.
]]>@atomicpookavirus: That link doesn't work. You don't need pastebins, you can post stuff directly here, just make sure to use code tags.
]]>$ su <----if you are not logged in as root
# Xorg -configure <----this will generate xorg.conf file if you don't have one
Then try starting X, you might need to reboot.
]]>@ Gusar: sometimes it did resolves for me.
No it didn't. They're *fallback* drivers. So you didn't resolve anything if they got used. Fallbacks are temporary workarounds, but they don't fix the actual issue.
Why it's not good turning off KMS?
Because that's how drivers nowadays work. Disabling KMS effectively means disabling the whole driver.
]]>