Am 30.06.2010 09:09, schrieb Andrea Conti:
>> 1. On boot up, the screen goes completely black until the xserver is
>> started.
>
> KMS provides its own framebuffer console driver -- disable any other
> framebuffer drivers such as (u)vesafb and enable
> FRAMEBUFFER_CONSOLE_DETECT_PRIMARY under driv
> 1. On boot up, the screen goes completely black until the xserver is
> started.
KMS provides its own framebuffer console driver -- disable any other
framebuffer drivers such as (u)vesafb and enable
FRAMEBUFFER_CONSOLE_DETECT_PRIMARY under drivers/graphics
support/console display driver support.
On Tue, Jun 29, 2010 at 08:49:38PM +0200, Florian Philipp wrote:
> What, you mean after going blank? Not that I would have noticed. If you
> mean after the xserver crash, see three sentences below ;)
Oh, my bad. So I assumed that you also checked the kernel logs then. Are
you sure there's no kerne
Am 29.06.2010 13:48, schrieb Willie Wong:
> On Mon, Jun 28, 2010 at 06:47:42PM +0200, Florian Philipp wrote:
>> 1. On boot up, the screen goes completely black until the xserver is
>> started. While I know my system long enough to recognize common boot
>> errors by watching the disk and peripheral
On Mon, Jun 28, 2010 at 06:47:42PM +0200, Florian Philipp wrote:
> 1. On boot up, the screen goes completely black until the xserver is
> started. While I know my system long enough to recognize common boot
> errors by watching the disk and peripheral device activity, I wouldn't
> like to make a fi
Hi list!
I ran into a massive problem when I tried to update to xorg-server-1.8:
When I tried to start it, the x-server didn't come up and wrote this
error: "(EE) intel(0): No kernel modesetting driver detected".
So I activated modesetting by default in the kernel and tried it again.
Now I have t
6 matches
Mail list logo
