SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just done a clean install on slackware64-current and I am suffering some graphics problems.
I have an ATI Mobility Radeon HD3200 card in my Laptop (Never been an issue before), however, the issue begins before I even start X server.
On the first boot, the screen went purple then entirely blank.
Second boot got me to a login, so I logged in and installed my packages. I started my WM (Ratpoison) and any attempt to start any windows resulted in an x-server crash and the message:
Module fbdev not available (Paraphrasing here).
Is anyone else suffering this?
I will note that everything works flawlessly on the previous current build.
x/xf86-video-ati-6.14.0-x86_64-1.txz: Upgraded.
This new driver requires KMS, which is set by default in the new kernel.
Otherwise, create /etc/modprobe.d/radeon.conf with this content:
options radeon modeset=1
Also, the kernel should be booted with vga=normal.
Problems have been observed when trying to use KMS after starting a VESA
framebuffer console. Sorry about the penguins.
make sure that you didn't pass any VGA= options to kernel from lilo (read the changelog). If after that situation doesn't resolve, post your dmesg output and X.org.log
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.