Skylark 5.2 for Dreamcatcher 3


#21

I noticed the same problem here. My board is out in the garage, so I don’t use the screen much. I was just walking by and touched the screen and nothing happened. Everything else appeared operational with all the LED’s etc. I used the button to shut it down and restart and everything is normal. I’m not sure how long it had been that way, as it had been up since the new upgrade. I didn’t think much about it, thinking it was probably just a one time glitch. I’ll try to notice it more ans see if it happens. again.


#22

how long was it off, approximately - do you know?


#23

I’m not sure. I noticed the screen unresponsive a couple of days ago, I think. I just rebooted today.


#24

I see you met the other cases of it and yes it responds normally everything works except for the touchscreen will not wake up it might take it a week to get that way that is the time frame when i found it before


#25

Mine usually takes about a minute, sometimes.


#26

I just found the screen unresponsive again this morning after checking OK yesterday. It appears other things in the system are also locked up. System uptime still shows up and counting at 15:41:50 up 2 days, 23:56, tuner status screen is not updating, System messages shows last extraction at May 10 11:38:42, Just “starting cleanup… nothing to do” messages hourly since, the last at 14:47:17. Is there anything else you would like for me to look check?


#27

I saw this behavior too in 5.1, RE the tuner locking up. Screen wasn’t fully functional in that version so this wouldn’t have been a symptom in that release. I haven’t had much ease of success with this setup like with the L-Band. I also haven’t had time to make a ‘cone’ for the LNB.


#28

thanks. Thats extremely helpful!

Tuner status is not updating both on Ui as well as inside the Skylark webgui?

Do you see the packet LED blinking?

I expect the heartbeat LED is blinking, cause otherwise skylark won’t work - but could you confirm that, just in case?


#29

The tuner does lock up - esp when signal levels are low.

But it should start up again in 10-15 seconds. Unless the signal level is low enough that it never receives any packets. Whenever tuner locks up - could you observe (and report) what the Packet LED is doing? When it locks up as well as 15-30 seconds after the lockup.


#30

The packet LED is not blinking and yes the heartbeat LED is blinking. The Ui screen on the board is nonfunctional, the Skylark webgui is not updating, but stuck on the last good numbers. Would some the last few lines from the Kernel Messages help?


#31

yes, please. Just the last 10-15 lines both from the kernel messages as well as the system messages.


#32

Kernel Messages
[ 10.257505] udevd[227]: starting version 3.1.5
[ 11.204304] [drm] Initialized
[ 12.025935] 8192cu: loading out-of-tree module taints kernel.
[ 12.310638] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 12.317290] [drm] No driver support for vblank timestamp query.
[ 12.323708] sun4i-drm display-engine: bound 1e60000.display-backend (ops cleanup_module [sun4i_backend])
[ 12.333278] sun4i-drm display-engine: Failed to initialize drm fb helper.
[ 12.340060] sun4i-drm display-engine: Couldn’t create our framebuffer
[ 12.346598] sun4i-drm display-engine: master bind failed: -22
[ 12.352391] sun4i-drm: probe of display-engine failed with error -22
[ 12.416489] usbcore: registered new interface driver rtl8192cu
[ 41.442754] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 42.166305] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 43.771988] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[83493.960033] spi_master spi32764: spi32764.0: timeout transferring 64 [email protected] for 110(100)ms
[83493.969194] spidev spi32764.0: SPI transfer failed: -110
[83493.974554] spi_master spi32764: failed to transfer one message from queue
[83624.270051] spi_master spi32764: spi32764.0: timeout transferring 64 [email protected] for 110(100)ms
[83624.279226] spidev spi32764.0: SPI transfer failed: -110
[83624.284621] spi_master spi32764: failed to transfer one message from queue
[83695.460042] spi_master spi32764: spi32764.0: timeout transferring 64 [email protected] for 110(100)ms
[83695.469255] spidev spi32764.0: SPI transfer failed: -110
[83695.474615] spi_master spi32764: failed to transfer one message from queue
[89147.710163] spi_master spi32764: spi32764.0: timeout transferring 64 [email protected] for 110(100)ms
[89147.719366] spidev spi32764.0: SPI transfer failed: -110
[89147.724750] spi_master spi32764: failed to transfer one message from queue
[95359.590083] spi_master spi32764: spi32764.0: timeout transferring 64 [email protected] for 110(100)ms
[95359.599254] spidev spi32764.0: SPI transfer failed: -110
[95359.604617] spi_master spi32764: failed to transfer one message from queue


#33

System Messages
May 10 11:38:40 outernet user.notice root: Discovered /mnt/downloads/opaks/1bbe-Barisan_Nasional.html.tbz2, extracting…
May 10 11:38:41 outernet user.info ondd[648]: [carousel] completed: opaks/1bbe-Barisan_Nasional.html.tbz2
May 10 11:38:42 outernet user.notice root: Discovered /mnt/downloads/opaks/23f9-messages-2018-05-10_11_37.txt.tbz2, extracting…
May 10 11:38:42 outernet user.info ondd[648]: [carousel] completed: opaks/23f9-messages-2018-05-10_11_37.txt.tbz2
May 10 11:47:14 outernet user.notice cleanup: Starting cleanup
May 10 11:47:14 outernet user.notice cleanup: Needs 409600 KiB, but there is already 13491304 KiB, nothing to do
May 10 12:47:14 outernet user.notice cleanup: Starting cleanup
May 10 12:47:15 outernet user.notice cleanup: Needs 409600 KiB, but there is already 13491616 KiB, nothing to do
May 10 13:47:15 outernet user.notice cleanup: Starting cleanup
May 10 13:47:16 outernet user.notice cleanup: Needs 409600 KiB, but there is already 13492120 KiB, nothing to do
May 10 14:47:16 outernet user.notice cleanup: Starting cleanup
May 10 14:47:17 outernet user.notice cleanup: Needs 409600 KiB, but there is already 13492720 KiB, nothing to do
May 10 15:47:17 outernet user.notice cleanup: Starting cleanup
May 10 15:47:17 outernet user.notice cleanup: Needs 409600 KiB, but there is already 13493292 KiB, nothing to do


#34

what was the approx packet rate/bitrate you were getting ~4-5 hours back - when the files were still coming down fine. Do you happen to recall? Or even the SNR?


#35

Locked screen was showing SNR -10.5 and bitrate was 20022.


#36

Could you check if theres any change now?


#37

Yes! The Skylark tuner screen is no longer locked is updating, the packet LED is flashing again and I’m receiving files. But the Board display is still unresponsive. What did you do?


#38

While I was away from desk for a bit, the carrier went down :confused:

The fact that you had full signal and then zilch made me go look. So thanks for all the data!

Unrelated to the display not-turning-on-issue though :expressionless:

In general if tuner is frozen for a more than 30 seconds, its cause packets are not coming in - tuner only updates when a packet comes in.


#39

OK. Glad we got that solved! It did seem strange, as last time when the display went blank, I though all the other LED’s were operating normally, although I didn’t log in with Skylark and check anything before rebooting. It had me starting to rethink myself!


#40

Do the Kernel messages offer any hint about the display problem?