3.16.x on i686

poma pomidorabelisima at gmail.com
Wed Jun 25 17:58:15 UTC 2014


On 25.06.2014 19:08, Adam Williamson wrote:
> On Wed, 2014-06-25 at 10:05 -0700, Adam Williamson wrote:
>> On Wed, 2014-06-25 at 12:02 -0400, Felix Miata wrote:
>>> On 2014-06-25 08:12 (GMT-0700) Adam Williamson composed:
>>>
>>>>> Where did you see "X initialization fails"? I've been booting with 3 on
>>>>> cmdline. Anyway, here's 2 of 3 drm.debug=15 dmesgs captured:
>>>
>>>>> http://fm.no-ip.com/Tmp/Linux/F/dmsgI865Gf21k316rc2g01.txt
>>>                                          ^^^^^
>>>
>>>> Er...this seems to be the log from the hardware you describe in your bug
>>>> comment, but:
>>>
>>>>> http://fm.no-ip.com/Tmp/Linux/F/dmsgI945Gf21k316rc2g01.txt
>>>                                          ^^^^^
>>>> What is this from?
>>>
>>> On 2014-06-24 23:54 (GMT-0400) Felix Miata composed:
>>>
>>>> It's repeatable ... on i865G, i915G and i945G
>>>
>>> And the one in the middle:
>>>
>>> http://fm.no-ip.com/Tmp/Linux/F/dmsgI915Gf21k316rc2g01.txt
>>
>> So...these are three different machines?
>>
>> I'm curious: why are you passing video= parameters on each one? Do
>> any/all of them work if you don't pass that parameter?
>
> ...and does it work if you append an 'e':
>
> video=1024x768e
>
> ?
>

"'e' will force the display to be enabled, i.e. it will override the detection
if a display is connected."
https://www.kernel.org/doc/Documentation/fb/modedb.txt

Felix:
"... Otherwise when init seems near completion, the screen goes black and
stays that way. ..."

Obviously the screen is detected and enabled, however failing at Xorg initialisation,
i.e. Xorg failing at initialisation, display just follows.
And "video" res shouldn't affect the whole scene.
Certainly not in my case, however I don't use it plymouth. :)


poma




More information about the test mailing list