I'm unable to get the fan to work on the RP64 v2.1 in the NAS case with the fan from Pine64 store. Not sure what I'm missing?
The fan is working when supplied with 12V directly. The fan does not work when plugged into the Fan port on the board.
/sys/class/hwmon/hwmon0/pwm1 exists, echoing any value from 0-255 does not have any affect. I read ATS source code to see if maybe I'm missing something. It doesn't appear so.
Also tried vanilla arch linux (the pwm-fan is under /sys/class/hwmon/hwmon1/pwm1 on linux-aarch64 (5.4.6)).
And built latest ayufan linux-mainline for arch linux. No functioning fan there either.
A multimeter at the base of Q2110 shows absolutely nothing no matter what I write to /sys/class/hwmon/hwmon0/pwm1 - my oscilliscope is currently not working so I'm unable to see if there is any PWM present on FAN_CTL_H yet - I suspect nothing.
This build is using a SATA card and two SSDs powered from the RP64's 12V header (the cables supplied with the NAS case). To rule out a power issue, I eliminated the SATA card and power to the SSDs - so only the DC power, FTDI cable, and fan are plugged into the RP64. Fan still inoperable on all images listed above.
I read every thread regarding the fan I could find on this forum - and all of them mention ATS. ATS does not work, obviously, because writing the values to /sys/class/hwmon/hwmon0/pwm1 has no effect. And yes, I'm logged in as root.
I get a CRC error when extrating the android 9 SDK. MD5sum fits the one from the website.
Even gzrecover can't help. Is it really broken or some incompatibility (Debian Buster)?
I tried to compile the ayufans kernel for the rockpro64 directly on the rockpro64 itself and on my x86 workstation. But in both cases I get a similar error:
Code:
In function 'hid_report_readreg.constprop',
inlined from 'rkvr_dev_attr_debug_show' at drivers/hid/hid-rkvr.c:826:7:
drivers/hid/hid-rkvr.c:780:3: warning: 'memcpy' forming offset 2 is out of the bounds [0, 1] of object 'mpu6500_id' with type 'u8' {aka 'unsigned char'} [-Warray-bounds]
error, forbidden warning:hid-rkvr.c:780
memcpy(data, &buf[1], readlen);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/hid/hid-rkvr.c: In function 'rkvr_dev_attr_debug_show':
drivers/hid/hid-rkvr.c:822:5: note: 'mpu6500_id' declared here
u8 mpu6500_id = 0;
^~~~~~~~~~
make[2]: *** [scripts/Makefile.build:277: drivers/hid/hid-rkvr.o] Error 1
make[1]: *** [scripts/Makefile.build:484: drivers/hid] Error 2
make[1]: *** Waiting for unfinished jobs...
I got the source code from here https://github.com/ayufan-rock64/linux-kernel and I used the branch release-4.4.190 which corresponds with the kernel running on my rockpro64. I used the config from arch/arm64/configs/rockchip_linux_defconfig.
I installed some packages on my workstation for cross compiling and tried to build the kernel with the following command, but I get the error from above.
Code:
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j24 Image
I'm able to successfully build the current mainline kernel with this command, but I haven't tried to boot from it. Because I could't cross compile the kernel from ayufan, I tried to compile it on my rockpro64, which is running the buster-minimal Image from ayufan. I installed the following packages on it.
I just received my PBP yesterday, and I'm very excited.
I started to use it and all wroks well and fine, but I have a question; is there any PDF reader? By default I didn't find one in the apps installed in the PBP, is there any way I can install one?
I wanted to change the boot splash image that is used during boot up. The Debian Swirl with the Open Sesame and Pine64 Logo did not really fit with the look and feel I have set up on the desktop, lock screen and login screen.
So I decided that I would need to change the boot splash image. To do so I had to figure out the raw format for the framebuffer image (/usr/share/backgrounds/splash.fb). After some experimenting I figure out the format of the raw file and managed to convert it to a PNG. After I had done that I was able to figure out the reverse command that would create the raw FB image from a PNG.
You can use this command to turn a PNG into the FB raw file. For this to work, your PNG has to be 1920x1080 resolution. I have not tested this with other resolutions. Make sure you have installed ImageMagick before running this:
So on reboot, I now have my own custom bootsplash. There is only one remaining issue. The console messages are still showing on the bootsplash screen. Even though /boot/extlinux/extlinux.conf has kernel options 'quiet' and 'loglevel=3' defined. These seem to be ignored to some degree because some messages are showing on the boot splash screen. Does anybody have any tips to make this completely silent?
I did install Plymouth before I used this message but I don't think that Plymouth would have any effect on the kernel messages showing. Does it?
<<UPDATE>>
It turns out that Plymouth did get in the way. After I removed the packages (plymouth, plymouth-theme-hamara and plymouth-themes) that I installed during my experimentation, no more kernel boot messages are showing on the splash screen.
I've literally just received my pinebook pro. Fortunatly most things seem to be working - the sound is definately working ok and I'm not experiencing any wifi issues; as for bluetooth however I haven't as yet tried it.
The first thing I did was to update the firmware for the keyboard and touchpad and that went without issue as well. Then it was a case of running the /usr/bin/mrfixit_update.sh . That completed ok and then it was just a case of performing a normal apt update/apt upgrade as per normal debian.
The only problem I seem to be having is with any sort of acceleration on the laptop itself. To give an example I can open (let's say) a terminal window. Moving the window seems to get a little slower if the window is large but the problem is largely with resizing windows - the pinebook pro is struggling to resize windows. Also I've noticed that if I click the menu button (bottom left) there's a big black square that appears just before the menu itself appears.
Is the pinebook not using any sort of xorg acceleration (2d) at all?
Firefox (which seems to crash a lot) also seems to be struggling and just loading a webpage exhibits similar issues; scrolling through a webpage seems to be painfully slow.
I also decided to try to check if 3d (GPU) acceleration is working. Glxgears gives me the result of 295 frames in 5.0 seconds = 59.532 fps in a window although a game like "torcs" dosen't seem to be running quite right - it is running at around 1-2fps.
One thing I did notice is I have the following in /etc/X11/xorg.conf;
So I see that the device is using modesetting/glamor but presumably it isn't quite working 100% since there seems to be a lack of any 2d (xorg) or 3d (GPU) acceleration?
Update: I have a couple of errors in /var/log/Xorg.0.log which look concering too;
Code:
$ cat /var/log/Xorg.0/log | grep error
[4.651] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so : cannot openm shared object file : No such file or directory)
[4.771] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so failed (/usr/lib/arm-gnueabihf/dri/swrast_dri.so: undefined symbol: _glapi_ tls Dispatch)
Update: I tried to run a different OS from microsd (in my case I chose q4os) -- it seemed to be a touch slower with moving windows but resizing was much better and it did not have the sluggishness surrounding the menu button.
I just received my PBP yesterday and I wanted to install a few games on it, I had an issue when I tried to run DevilutionX, I started by downloading the latest release from github (https://github.com/diasurgical/devilutionX/releases), I then extracted the archive, copied my "diabdat.mpq" file and attempted to run it but it fails with the following error :
Code:
./devilutionx: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.25' not found (required by ./devilutionx)
./devilutionx: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by ./devilutionx)
I then read the README.txt file and it seems the game requires some manual libraries installation :
Quote:# How To Install:
- Extract the files in the zip.
- Install libsdl2 libsdl2-mixer libsdl2-ttf
- Copy diabdat.mpq from your CD, or GoG install folder, to the DevilutionX install folder; Make sure it is all lowercase.
- Run ./devilutionx
Reading package lists... Doneat
Building dependency tree
Reading state information... Done
E: Unable to locate package libsdl2
E: Unable to locate package libsdl2-mixer
E: Unable to locate package libsdl2-ttf
I also tried to find the packets in synaptic and they do not appear...
The "README.txt" file specifies that this is built for raspbian so maybe the repos are not exactly the same?
Anyhow I wanted to know if anyone here attempted to run DevilutionX on their Pinebook Pro successfully and if they could provide me with some instructions or if anyone who's knowledgeable with this kind of things could help
Thanks for reading through my post and for any help you could bring up in this thread, I'm considering opening a general thread for gaming tips because none of this seem easy except if your gaming use is restricted to Retroarch and Doom
I have seen the threads on FCC and CE testing where tllim kindly outlined the timing for regulatory approval testing.
I saw no mention of regulation in Japan which has its own regulatory framework... According to this: https://www.quectel.com/product/eg25g.htm the modem is apparently TELEC (Japanese approvals agency) approved already.
I understand that Japan may not be the largest target market, but I have chatted with a few individuals who are very interested in acquiring a pinephone but will not do so unless the Technical Conformity Mark [in Japanese 技適 (giteki)] is present somewhere on the device. Without this approval using the phone may be technically illegal or at least possibly so.
Could anyone from Pine64 kindly clarify the status of regulatory approval in Japan? If said regulatory testing has not yet been applied for, are there plans to do so and if so, is there any expected timeframe?
From my research, I have discovered that even devices that have not passed the regulatory framework can be used for development / experimental purposes for up to 180 days while testing is carried out so long as this "experimental" use is expressed to the appropriate authority - getting this experimental use licence is free of charge; although unfortunately I don't know about the price of the Technical Conformity Mark certification.
I live in Japan and am quite concerned that I may have to cancel my Braveheart order and that if this hurdle is not passed, and that myself and others will not be able to use the pinephone in the future either. This in turn might hinder the progress of multilingual support in the future with fewer language-specific bug reports being posted etc.
Some indication of what the future holds would be very much appreciated, and if approval is on the way, I'll be sure to spread the message as far and wide as I can.
In case they are useful, I found the following resources which have some information about applications / rules etc.:
Here is a super casual end of year update. I've been rather busy these past 2 weeks, and will be busy for another week or so, but after that I'll sit down and write a proper update for mid-January 2020. By that time PinePhones ought to be shipping and there will be plenty to talk about.
Let me take this opportunity to say that I am very thankful to you all for helping PINE64 grow into what it is today. Its been quite an exciting (and stressful year) and we appreciate you being with us throughout this journey. You have shown patience with the delays and a high degree of understanding at various hiccups and shortcomings; this tells me we've fostered a great and mature environment that we all can be proud of.
I'd also like to thank all developers from within the community and the partner projects. I hope and trust that we managed to make a friendly and enjoyable framework for us to cooperate and work in. On our end, its been a real pleasure as well as a lot of fun.
Last and not least, a shutout to moderators on the forum, in particular to @evilbunny who's been quietly at it for years, and our newcomers @tophneal and @Arwen for doing a great job on here. And a very special thank you to @fire219 for getting the forums and website in order ... and endlessly fixing broken bridges in the chats (hopefully something we can further improve in 2020).
FOSDEM 2020
Its hard to believe it but FOSDEM 2020 is just a month away. What the hell happened to 2019 ... it feels like it just began and now its over. Anyways, we'll have a stall on Sunday (Feb 2) so if you're around make sure to pop by and say hello. On Saturday we'll be walking around, checking out stalls and going to talks. We'll probably linger at some befriended stalls too. So if you see me or TL feel free to stop us for a chat. Also, I know a nice secret spot nearby the Free University of Brussels with decent food, so you're welcome to PM me if you wan to join me for lunch.
We will be making a couple of announcement at or just a day before FOSDEM starts, but I expect that the PinePhone and Pinebook Pro will still steal the show on our stall. Speaking of the PinePhone, for those of you who will be rocking your PinePhones at the conference we may just have something special So make sure to take your PinePhone with you if you're attending.
Pinebook Pro (ISO & ANSI)
ISO Pinebook Pros have already gone out and, from the looks of Twitter / Mastodon tweets/toots, many have already been delivered.
The ANSI keyboard batch will start going out at the beginning of January. I am looking forward to hearing how you ANSI folks find the keyboard - I have only tried the prototype keyboard, so I am keen to hear how the end-product turned out (I'm an ISO person, so won't be getting/using an ANSI version). I hope and trust its on par with the ISO offering.
If you have ordered a Pinebook Pro in the last ~7-10 days or so, then your unit will ship out later in January (after Brave Heart PinePhones). So please do not bombard the shipping or pinebook team with questions such as 'why hasn't mine shipped yet?', if you placed an order just recently.
The default OS Build has gotten some major improvements in recent weeks and more are coming in January (we've got some nice tweaks in the works). Full acceleration for Chromium, improved performance and rock-solid stability of Firefox and support for (many/ most) USB-C docks are just some of the highlights of the default Debian OS in the past month. Regardless of if you want to run mainline OS images such as Manjaro, or novel alternatives such as Q4OS or Ubuntu MATE, lets take a minute to recognize the work @Mrfixit2001 has put into this default build. It's amazing to always have a good out-of-the-box experience and a solid image to fall back on.
I am also happy to let you know that we'll soon be seeing Recalbox for the Pinebook Pro. I for one am very much looking forward to that!
Lastly, huge shutout to those who helped draft the welcome letter for the Pinebook Pro! I highly appreciate your help.
PinePhone
There is currently so much happening in the PinePhone sphere that I literally have no time to cover it all. I've recently released a video showing 4 OSs running on the PinePhone. I have been told that the video is garbage - and I appreciate that it true - but just turn off the audio and your experience will improve by ~40%
The Brave Heart edition phones will ship some 5-7 days later than we initially anticipated. This has nothing to do with production or some issues - the reason is simply that Pinebook Pro ANSI need to be shipped first. As to why the decision was made to ship ANSI Pinebook Pros before Brave Heart PinePhones, I don't know. My guess is that Pinebook Pros, as a batch, take up physically much more space and hence its preferable to clear them out first as they take up much space. This is just my guess.
In anticipation of your questions regarding why these devices can't ship at the same time: there is only one shipping team and they can only handle one device at a time. PinePhones and Pinebook Pros are manufactured at different factories, shipped using different means, and probably also require different paperwork when crossing into Hong Kong. I know you're all eager to get your devices - but its just a few days delay. Thanks for your patience!
Speaking of shipping, you'll get a shipping notification from PINE64 once your phone ships out. In my experience, tracking for Asendia is so-so but shipping is rather quick (some 10-14 days to EU). Here is my experience with getting the PinePhone in a nutshell: the parcel was registered as outgoing in HK then there were no more updates until it reached the destination country. When It reached Europe, I plotted the tracking number into the local couriers tracking system and got updates where the phone is. BTW, I wasn't asked to pay tax and it looks like most EU based devs weren't asked to pay import tax either... *fingers corssed*.
The PinePhone (with a screen protector installed ... if you love it, great. If you hate it, peal it off).
A welcome letter,written by the community (many thanks to those who offered suggestions and help!)
A high quality charging USB-C cable (its a really good cable - use it)
There is no USB PSU included. We assume most of you have a modern-ish Android phone that has a PSU capable of outputting 15W, so we decided not to bump the price nor add another thing to the landfill. In the event you don't have a 15W charger, then you can use chargers with lower wattage (will take longer to charge) for now and wait for suggestions / reports from community members to learn what PSUs work best.
Lastly, I've seen the see-though silicone (soft) case for the PinePhone and it really does look good.
PineTime
Current batch of PineTime dev kits has now started being delivered for a week or so. There seems to be a lot of cool developments in the PineTime area - for the first time, I've seen the PT connect to an android phone, obtain time data from it and sync correctly. From the looks of the short video by JF also shows BT and battery status on the GUI, and the push-button working (to turn off the LCD).
Given how short time the PineTime has had, this is really quite impressive stuff. Even more impressive is the amount and depth of engagement we have witnessed so far from the development crowd. This is very cool stuff and I have high hopes that a real daily-driver candidate OS for the watch will emerge in the first half of 2020, so the PineTime can be sold to FOSS enthusiasts who don't necessarily want to (or know how-to) write their own code.
Stuff that doesn't fit under the headings above
I know many of you want more information about the PineTab early-adopters edition - don't worry, it's coming. I'll have some solid information in the January community update. In short, it's still happening but our focus right now is on getting Brave Heart out the door and getting everything for FOSDEM ready. So stay tuned for now.
Thanks to all who answered my poll regarding how we did and what we could do better. Approx 40% indicated that the one thing they'd like to see is more shipping options and 30% had no complaints at all. Another 10% felt we could do better on communicating with the community and 15% felt that the store support was lacking. We already have started looking at shipping options; for instance, we're experimenting with Asendia for the PinePhone Brave Heart edition. If this turns out to be success, then I think we'll be considering this as an alternative to other shipping methods. It falls somewhere in the middle between the standard shipment and DHL in that its faster and all-around 'better' than the standard option while being significantly cheaper than DHL. It also - from the limited experience we have - limits the likelihood of you being charged import tax in some geographical areas. As for store support - I think it has improved significantly already over the past year, and I am certain that it will further improve in the next 12 months time.
Speaking of store support, a kind request to everyone waiting for a Pinebook Pro or/and PinePhone; I understand that you are really excited and want your device as soon as possible, and this prompts you to seek out answers. I really get it. But unless you feel like we've missed your shipment after having done some research on shipping dates, rather then emailing support post a question on the forum or in the chats. Support emails are filled with 'When is X shipping?' questions and this detracts from support staff getting back to people who are experiencing issues with their orders or equipment. For those who do not know, dates can usually (if not always) be found in latest blog posts and on social media (twitter / mastodon) as well as on the forums (someone usually asked a shipping question already, and its been answered). You can usually also get a quick answer to this question in the chats.
Lastly, thank you all for doing such a great job on the Wiki! Especially the Pinebook Pro wiki looks absolutely great now and is filled to the brink with useful information. I think this is the new golden standard for wiki pages.
![[Image: giteki_news.jpg]](https://www.tele.soumu.go.jp/e/adm/monitoring/illegal/monitoring_qa/mobile/__icsFiles/artimage/2009/02/01/c_keitaidenw/giteki_news.jpg){kind=small}
[in Japanese 技適 (giteki)] is present somewhere on the device. Without this approval using the phone may be technically illegal or at least possibly so.
So make sure to take your PinePhone with you if you're attending. 