You are not logged in.
I think I worded the subject right, I apologise if I did not.
I have an AMD graphics card and I'm using the xf86-video-ati drivers. Whenever I boot I get a black screen unless I disable KMS. The wiki has a solution for this problem, passing "fbcon:map=0" to the kernel. It works fine every now and then, but sometimes I still get the black screens. Passing "fbcon:map=1" instead fixes this. This is of course pretty annoying. Is there some way to avoid having to go reboot whenever the issue occurs?
Offline
You seem to have multiple framebuffer devices/drivers being assigned to /dev/fb{0,1} in a random order. Try writing a udev .rules file that matches at least one of them and assigns it to one of fb{0,1}:
http://stackoverflow.com/questions/3978 … gn-dev-fbx
You can completely avoid having to reboot by blacklisting radeon, and loading it manually later, but then you're limited to a 640x480 basic VGA tty, and the screen will go black when you load radeon later if it grabs the wrong framebuffer. Write the udev rule instead.
Offline
You seem to have multiple framebuffer devices/drivers being assigned to /dev/fb{0,1} in a random order. Try writing a udev .rules file that matches at least one of them and assigns it to one of fb{0,1}:
http://stackoverflow.com/questions/3978 … gn-dev-fbxYou can completely avoid having to reboot by blacklisting radeon, and loading it manually later, but then you're limited to a 640x480 basic VGA tty, and the screen will go black when you load radeon later if it grabs the wrong framebuffer. Write the udev rule instead.
I have the built-in graphics card in my mobo as well as a stick-in AMD card. But I think that the built-in one is disabled (I have no clear/straight forward to disable that ouput, I can just dedicate bits of RAM to it to act as VRAM). Either way, I've never written udev rules before, and I'm not really sure what I'm supposed to write (or really where I'm supposed to place the file).
Edit: reading the wiki article related to it.
Last edited by lurvik (2015-04-18 17:16:21)
Offline
I've been messing with different init systems and just got around to figuring out how udev works for the first time ever.
What you want seems to be
DRIVERS=="radeon", NAME="fb1"and fbcon:map=1 in the kernel params. This should be safe if you don't know the integrated driver, even if fb0 gets allocated first.
Last edited by mojangsta (2015-04-24 02:57:53)
Offline
I've been messing with different init systems and just got around to figuring out how udev works for the first time ever.
What you want seems to be
DRIVERS=="radeon", NAME="fb1"and fbcon:map=1 in the kernel params. This should be safe if you don't know the integrated driver, even if fb0 gets allocated first.
I've completely forgotten about this thread, because I've just kept my computer running (it's so quiet that I've never bothered turning it off). But where exactly should I put that, and what exactly should I put in?
Offline