reblair

With respect to the audio missing, it is true there is a mic equipped camera plugged in and oddly the issue must be intermittent because a reboot fixed it and it hasn't recurred after a day of running and occasional audio use (the camera still connected).

The network issue appears resolved as of the gxl patches submitted a day or two ago. I have enabled usb sound (modules), camera and cifs and ecryptfs. I have one issue the hdmi sound works sometimes and not others, The only messages that show up that might be related in syslog are: Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write. Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: Most likely this is a bug in the ALSA driver '(null)'. Please report this issue to the ALSA developers. Dec 21 08:08:39 localhost pulseaudio[12024]: [alsa-sink-meson-i2s-dai.0.auto-i2s-hifi i2s-hifi-0] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read. Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers. Dec 21 09:40:38 localhost pulseaudio[12024]: [alsa-source-USB Audio] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Is this unique to me or have others seen hdmi stop working?

I'm happy to test any patches. I can reliably hose the network either by running kodi or tarring up data off one of my shares. In general other activity is very stable.

I see the network dropping while testing for cifs support on the lepotato. I'm using a build meson64 next 4.14.5 with the cifs module added in the config, but I saw similar lockups with the 4.14.2 release (which had no cifs.ko to test). The interface loses its IP after heavy usage. Has the AMLOGIC patch (or the equivalent) already been applied or is there a patch out there for this problem? I also notice that the MAC for this device is random unless it is set manually in /etc/network/interfaces with the hwaddr directive. Is this normal? I have never seen this behavior on a number of raspberrypi's, an odroid nor on a bananapi.

I just set up a Le Potato and am running the latest release kernel: Linux lepotato 4.14.2-meson64 #8 SMP PREEMPT Fri Nov 24 19:43:01 CET 2017 aarch64 aarch64 aarch64 GNU/Linux It seems this kernel was built with very limited fs support (i.e. some I normally use: cifs and ecryptfs which have no corresponding modules under /lib/modules/../kernel/fs). Is this related to the above, an oversight or by design? I set up to build a kernel and am glad to help if thus would be useful but I guess it would be good to have any background associated before diving in. Thanks in advance!