19.03.2015 14:56, One Thousand Gnomes wrote:
> On Thu, 19 Mar 2015 14:09:29 +0300
> Michael Tokarev wrote:
>
>> Half a year passed since my first email in this thread, and current kernels
>> (4.0-tobe) still does not work properly. Meanwhile, I found this thread:
>> http://www.linuxquestions.org
19.03.2015 23:05, One Thousand Gnomes wrote:
>> Yes, with video=LVDS-1:d boot parameter, kernel boots fine and there is
>> graphics/video output on the screen, with the following message from kernel
>> when loading gma500_gfx:
>>
>> [6.472859] [drm] forcing LVDS-1 connector OFF
>>
>> (and a few
19.03.2015 14:56, One Thousand Gnomes wrote:
> On Thu, 19 Mar 2015 14:09:29 +0300
> Michael Tokarev wrote:
>
>> Half a year passed since my first email in this thread, and current kernels
>> (4.0-tobe) still does not work properly. Meanwhile, I found this thread:
>> http://www.linuxquestions.org
> Yes, with video=LVDS-1:d boot parameter, kernel boots fine and there is
> graphics/video output on the screen, with the following message from kernel
> when loading gma500_gfx:
>
> [6.472859] [drm] forcing LVDS-1 connector OFF
>
> (and a few others).
>
> There's one funky thing still -- th
19.03.2015 14:09, Michael Tokarev wrote:
> Half a year passed since my first email in this thread, and current kernels
Actually it was more than a year, since Feb-2014 ;)
> (4.0-tobe) still does not work properly. Meanwhile, I found this thread:
> http://www.linuxquestions.org/questions/slackwar
Half a year passed since my first email in this thread, and current kernels
(4.0-tobe) still does not work properly. Meanwhile, I found this thread:
http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-intel-desktopboard-d2500cc-4175503983/
which seems to help. I wond
On Thu, 19 Mar 2015 14:09:29 +0300
Michael Tokarev wrote:
> Half a year passed since my first email in this thread, and current kernels
> (4.0-tobe) still does not work properly. Meanwhile, I found this thread:
> http://www.linuxquestions.org/questions/slackware-installation-40/black-screen-on-i
05.08.2014 20:11, Michael Tokarev wrote:
> Hello again.
>
> It's been 4 more months since last message in this thread (which was mine).
> Now kernel 3.16 has been released, and I decided to give it a try. And it
> behaves just like all previous kernels, -- once gma500_gfx module is loaded,
> scre
Hello again.
It's been 4 more months since last message in this thread (which was mine).
Now kernel 3.16 has been released, and I decided to give it a try. And it
behaves just like all previous kernels, -- once gma500_gfx module is loaded,
screen goes blank, monitor turns off ("no signal detected
Hello again
It's been about 2 months since I sent the original debugging output. Today I
tried
out 3.14 kernel. And this one behaves quite similarly, screen goes blank right
when loading gma500_gfx module. Here's the dmesg from a freshly booted system
after doing
modprobe drm debug=6
modp
10.02.2014 14:44, One Thousand Gnomes wrote:
>> fbcon is loaded so it isn't an issue.
>>
>> I tried 3.10 kernel initially (the above messages are from it), next
>> I tried 3.13 kernel too, and that one behaves exactly the same.
>>
>> As far as I remember, this system never worked with graphics well
> fbcon is loaded so it isn't an issue.
>
> I tried 3.10 kernel initially (the above messages are from it), next
> I tried 3.13 kernel too, and that one behaves exactly the same.
>
> As far as I remember, this system never worked with graphics well.
> Previous kernel (from which I updated) was 3.
Hello.
Today I rebooted my router into a new kernel and noticed that
the screen goes blank after booting the system (initial bootup
messages are visible). After some debugging it turns out that
the screen goes blank when loading gma500_gfx module.
This is an intel D2500CC motherboard with Atom D
13 matches
Mail list logo
