Update: I spoke with @ayufan on IRC, and let him know.  He is going to address the situation.

Hi,

I have been using the Ayufun pre-release kernel with great results.  Recently, I am seeing an error when I perform an apt-get update.  Here is what appears:

Just a heads up; Firefox 57 is out and its really fast on the Pinebook - massive performance increase over 56 even on sites riddled with horrible ads. 

Using the tweaks I posted some time back it makes for really usable browsing.

I'm using my Pinebook on a daily base. Actually, this is my No#1 portable, taking it everywhere with me.
I use it extensively for web browsing, email, remote controlling Linux and Windows desktops (FreeRDP, X2Go).

So, it is in real production use.

I'm not sure if it arrived like this or changed over time but I realized that it has a kind of pixel errors now.
These are larges ares, I mean more pixel than one. They are lighter then their surroundings and are best visible
when the screen is white.

I made a photo of it (slightly enhanced in GIMP).

What could it be? Will it be worse?



thanks
Robert

Hi, I often get an error spinlock lockup suspected on CPU#X where x is cpu core number from 0 to 3, one after another. When that occurs in terminal everything freezes and the only way is to reboot the device using force poweroff. It's popping up only under stress (at least 30-50% of all cores) in Chrome for instance. I'm using a 13x13x10 mm radiator with average quality thermal paste. Temperature is about 50-65 Celsius degrees. I'm using latest Ubuntu Artful build. Is it possible that it's caused by thermal issue? Hardware Issue? Or maybe it's because unstable distro?


Please go easy on me, I'm rather beginner.

Please help make that happen.

So I have pi this and pi that, I bought them from uncle Ma, I'll like to try rock64 2G. Please help make that happen, maybe put one on uncle Ma's "SALTFISH"?   please?

Hi, i'm looking to replace my rPi that is home server with plex, transmission, flexget and samba. #
It does get sdcard corruption almost anytime I update plex server.
I have another one running plex client and cec-client script that is solving super annoying first world problem - when when I turn off ps4 it does not turn off TV, and even worse, when I would turn TV on, it would wake up PS4 again instead of going to some homescreen of input selection, oh, the horror, right?

So my idea is to get rid of both rPis and get one rock64 and SSD instead of 3.5 HDD, that i use currently, as I no longer hoard movies, to get rid of the noise and had it all in one.

Rock64 is one device I found that, at least on HW side checks almost all the boxes - low power, can be powered from USB, does have 4k hdmi, does have usb3, does have gigabit ethernet, does have EMMC. Really only hw box it does not check is to have all the ports on one side.
Another option would be odroid xu4, but it is more power hungry and i don't really see any advantage to chose it.

My questions:
[*]will rasplex/openelec run on rock64 - i'm looking into kodi plex client now, so that might be a way
[*]Would kodi UI run in 4k?
[*]does cec-client work on rock64 - this is really my main concern
[*]I have aukey/crdc power source I use right now, it maxs out at 5V/3A on single port, but I could probably hack something up to connect to two ports at once - will 3A be enough to power sata 2.5 SSD connected to usb3 port?
[*]Do i need emmc to USB thing or can i flash EMMC directly from PC when it is connected on rock64 board?

I've been doing lots of research in preparation of receiving my ROCK64    Has anyone tried dual-booting from a single SD Card yet? I'm hoping to find something that works on this platform that's similar to NOOBS Companion for the RPI, allowing me to easily jump back and forth between LibreELEC (KODI) and LAKKA. Anyone have any experience with this topic yet?

https://www.theregister.co.uk/2017/11/12..._released/

http://opensource.rock-chips.com/wiki_Status_Matrix

While updating some packages to the debian stable versions, I managed to break audio in the process.
Pulseaudio is running and shows output in the volume. So I'm assuming the problem is somewhere in alsa.

Can someone post the full output of "amixer -c0" of a working sound output of a pinebook 14"? I'm currently assuming it's one of those many settings that is wrong.