(08-01-2016, 09:53 AM)Monochrome Wrote: [ -> ] after update no audio device is detected. If you need any log please let me know.
Mhm i do not see how that could be related.
Please post the outputs of
aplay -l
and
lsmod
and the full output of `dmesg` after fresh boot.
Thanks
(07-31-2016, 03:57 PM)xalius Wrote: [ -> ]I had not luck so far with enabling armsoc-drv with X, with the version from the PPA I get a kernel oops,
Finally figured out that problem. Launchpad build is updated - should work fine with 1.4.0-0ubuntu2+0sunxi5. Thanks for testing!
Ok seems to work now with the version from the PPA, thanks! Back to fixing the allocation problem I guess
aplay: device_list:268: no soundcards found...
debian@pine64:~$ lsmod
Module Size Used by
bnep 17511 2
bluetooth 195943 5 bnep
vfe_v4l2 747618 0
vfe_io 34085 1 vfe_v4l2
mali 238217 0
ir_lirc_codec 12756 0
lirc_dev 17032 1 ir_lirc_codec
videobuf2_dma_contig 17668 1 vfe_v4l2
videobuf2_memops 12546 1 videobuf2_dma_contig
ir_sony_decoder 12489 0
ir_sanyo_decoder 12491 0
ir_jvc_decoder 12487 0
ir_mce_kbd_decoder 12628 0
ir_rc6_decoder 12520 0
ir_rc5_decoder 12487 0
ir_nec_decoder 12487 0
videobuf2_core 30952 1 vfe_v4l2
sunxi_ir_rx 12902 0
deinterlace 18524 0
cedar_ve 17368 0
ss 33083 0
8723bs 1365012 0
cfg80211 374207 1 8723bs
dmesg http://pastebin.com/vi0bgg0p
(08-01-2016, 11:54 AM)Monochrome Wrote: [ -> ]dmesg http://pastebin.com/vi0bgg0p
Ok the DMESG shows the error
[ 13.552150] sndhdmi sound.7: ASoC: can't create pcm SUNXI-HDMIAUDIO :-12
[ 13.571547] sndhdmi sound.7: ASoC: failed to instantiate card -12
[ 13.590409] sndhdmi sound.7: snd_soc_register_card() failed: -12
[ 13.609061] sndhdmi: probe of sound.7 failed with error -12
As of why i have no clue. Anyone else gets this?
Btw its supposed to look like this:
root@pine64:~# dmesg|grep -i sndhdmi
[ 12.454417] sndhdmi sound.7: sndhdmi <-> 1c22800.daudio mapping ok
[ 12.625219] #0: sndhdmi
(08-01-2016, 11:40 AM)xalius Wrote: [ -> ]Ok seems to work now with the version from the PPA, thanks! Back to fixing the allocation problem I guess
Something is not right with the continues memory allocation of the drm driver. I am not particularly keen to dig into this. A possible workaround is to add
to your /boot/uEnv.txt - do not restart X11 to often and it is fine
(and have Allwinner fix their driver)
Ok. So I tried every possible way [from forum] to change resolution from 4K to 1080p. Nothing worked. Once [don't know why] it booted with desktop in 720p. I checked sound card and it was present. I can't replicate it. Somehow I think maybe the 4k is the problem based on what happened.
Wait do we have a timeline for the Mali Blobs?
If they are IP isn't it game over?
BTW, thanks for all the images and work.. having a lot of fun working with these now.
The source is licensed.
... the blob is being tested, and there are issue to sort... be patient.
(08-01-2016, 03:06 PM)longsleep Wrote: [ -> ]Maybe - you can play around with the various KMS parameters - some work, others don't. See https://wiki.archlinux.org/index.php/ker...de_setting for a rather good summary.
Also when in X11, xrandr works fine to change the resolution.
Thanks for the link. I will read it but I do not think I can get much out of it. With xrandr I'm getting "xrandr failed to get size of gamma for output default". Probably doing something wrong but sadly I just can't get it to work.