[Letux-kernel] compile problems

[H. Nikolaus Schaller]

> Am 23.07.2018 um 17:05 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> Hi,
> 
> 
> On Mon, 23 Jul 2018 10:02:47 +0200
> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> 
>> Hi Andreas,
>> I now have merged & built letux-4.18-rc6 (not yet pushed).
>> 
>>> Am 23.07.2018 um 07:47 schrieb Andreas Kemnade
>>> <andreas at kemnade.info>:
>>> 
>>> On Sun, 22 Jul 2018 22:17:05 +0200
>>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>>> 
>>> 
>>>>> [    9.171325] [drm] Supports vblank timestamp caching Rev 2
>>>>> (21.10.2013). [    9.178253] [drm] No driver support for vblank
>>>>> timestamp query. [    9.198577] omapdrm omapdrm.0: Tiled buffers
>>>>> require DMM [    9.207733] fbcon_init: detected unhandled
>>>>> fb_set_par error, error code -16
>>> 
>>> = display problems!
>>>>> [    9.207733] Console: switching to colour frame buffer device
>>>>> 60x40 [    9.227874] omapdrm omapdrm.0: fb0: omapdrm frame buffer
>>>>> device
>> 
>> Haven't seen this:
> 
> Sometimes I have just a white screen and nothing more, sometimes a
> blinking cursor.

Strange. Well, we can only hope that it disappears if we upgrade to
next -rc.
> 
>> 
>> [    7.691253] wwan_on_off_set_power: state 1
>> [    7.695892] wwan_on_off_set_power: done
>> [    7.764709] wwan_on_off_probe: successfully probed
>> [    8.408447] omapdrm omapdrm.0: DMM not available, disable DMM
>> support [    8.460174] [drm] Supports vblank timestamp caching Rev 2
>> (21.10.2013). [    8.502227] [drm] No driver support for vblank
>> timestamp query. [    8.508758] omapdrm omapdrm.0: Tiled buffers
>> require DMM [    8.615325] Console: switching to colour frame buffer
>> device 60x40 [    8.691711] omapdrm omapdrm.0: fb0: omapdrm frame
>> buffer device [    8.716918] cfg80211: Loading compiled-in X.509
>> certificates for regulatory database [    8.726501] [drm] Initialized
>> omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0 [    8.767608]
>> cfg80211: Loaded X.509 cert 'sforshee:
>> 00b28ddf47aef9cea7' [    8.785064] platform regulatory.0: Direct
>> firmware load for regulatory.db failed with error -2 [    8.796966]
>> cfg80211: failed to load regulatory.db
>> 
>>>>> [    9.234252] ---[ end trace 8c96d4db1da6a489 ]---
>>>>> [    9.262847] [drm] Initialized omapdrm 1.0.0 20110917 for
>>>>> omapdrm.0 on minor 0 [    9.418731] cfg80211: Loading compiled-in
>>>>> X.509 certificates for regulatory database [    9.486663]
>>>>> cfg80211: Loaded X.509 cert 'sforshee:
>>>>> 00b28ddf47aef9cea7' [    9.543640] platform regulatory.0: Direct
>>>>> firmware load for regulatory.db failed with error -2
>>>>> [    9.571105] cfg80211: failed to load regulatory.db
>> 
>> And I haven't seen the iio related error. Maybe something spurious or
>> is it repeatable for you? Then it could be an effect based on
>> different boot procedure (assuming you boot through serial/usb - I
>> did boot from U-Boot with Josuas and your DFU fixes in NAND and
>> kernel on µSD).
>> 
> At that time I did an ordinary mmc boot on the gta04a5, The 4.18-rc5
> only booted once to the point where I could login via usb.
> I had issues with my bt keyboard (which I wanted to use on my trip, to
> save the real estate on the screen needed for the virtual keyboard
> else. So I have not tested it that intensively, but first wanted to
> find out if the keyboard is fixed with a more current kernel. But my
> keyboard works well with 4.17.2.
> I will do more tests

Ok.

BR,
Nikolaus

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.goldelico.com/pipermail/letux-kernel/attachments/20180723/93c97bda/attachment.asc>