I just did the last update and it broke netflix, which stops now every 5 seconds or less.
Reinstalling the patch did not solve anything.
For the rest everything seems working fine but as I missed the forum news for more than a month I wonder if i missed some patch or update and that is the reason why this is happening.
Just wanted to shout out to the folks at Pine64 I ordered a 128M emmc module and some other stuff and it looks like it shipped. :-) just wanted to say a big thanks for your efforts under extreme circumstances, just make sure you all stay safe, I'll take a computer virus any day over the kinda shit you've had to deal with over the last month.
Just wanted to report that I've recently installed the Samsung 960 EVO 500GB MZ-V6E500 2280. Running Manjaro ARM as primary drive. I wasn't sure it would work since the wiki shows the 970s don't work. I haven't noticed any heat from the drive but then I haven't done any particularly large read/writes. Seems stable thus far. Been using it about a week at this point.
What tests should I run before updating the wiki to note this thing is good to go?
Is there any other information anyone else would like about this?
Is there a standard for testing or verifying drives before we add them to the wiki? Perhaps I missed this somewhere if it already exists. Maybe worth noting at the top of the page or linking to those type of instructions here if/when they exist. https://wiki.pine64.org/index.php/Pinebo...patibility
Code:
smartctl 7.1 2019-12-30 r5022 [aarch64-linux-5.5.0-3.1-MANJARO-ARM] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 960 EVO 500GB
Serial Number: S3X4NB0K501841X
Firmware Version: 3B7QCXE7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500,107,862,016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500,107,862,016 [500 GB]
Namespace 1 Utilization: 285,444,767,744 [285 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 5581b4b31f
Local Time is: Mon Feb 24 23:24:31 2020 CST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0007): Security Format Frmw_DL
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 512 Pages
Warning Comp. Temp. Threshold: 83 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 34 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 1%
Data Units Read: 8,699,295 [4.45 TB]
Data Units Written: 9,937,895 [5.08 TB]
Host Read Commands: 86,990,454
Host Write Commands: 60,449,849
Controller Busy Time: 357
Power Cycles: 195
Power On Hours: 243
Unsafe Shutdowns: 44
Media and Data Integrity Errors: 0
Error Information Log Entries: 83
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 34 Celsius
Temperature Sensor 2: 39 Celsius
Last week on Manjaro I got a whole stack of updates to GNOME and some system packages. After rebooting, both gdm and GNOME give me black screens with cursors, journalctl /usr/bin/gnome-shell gives me a bunch of errors:
Code:
Failed to open gpu '/dev/dri/card0':
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
Installed Budgie a little earlier to get another DE going, and to see if it'd run since it shares a lot with Gnome. It runs without any issue.
Have any other GNOME3 users experienced similar issues from the most recent updates?
I would like to see a PineTime LTE (eSIM) version...if there is even an OpenSource/FreeSoftware OS that supports this. I gather Google hasn't bothered to open source WearOS.
My RockPro64 finally arrived, and when I unpacked it, I realised that I forgot to include a CPU heatsink on my order.
I have read in a number of places that the RK3399 get very hot, so it would be foolish to run it without a heatsink, but as my last order took 6 weeks to arrive, I don't want to order just a heatsink from the PINE store and wait that long before I can start using my new RockPro64.
Can anyone suggest where I might get a substitute heatsink from? Does the heatsink spec match a well known standard from elsewhere in the electronics industry? Looking at the board it is clear that a CPU cooler from a desktop CPU would not fit, and the mounting would be totally different, but would a chipset heatsink likely fit?
First off, I read all the other threads on vibrating and motors on this forum for the pinephone. I don't see a fix for my problem with an otherwise cool phone. I got my really cool pinephone in the mail earlier this month, and it vibrates all the time it is on. Before the booting even shows light on the screen, the motor is vibrating. It vibrated from the first moment I turned it on. It vibrates after the screen shuts down, and up until the phone is completely off. It vibrates now. I tried booting a different OS to see if it the motor still runs all the time, it does, it still has the same issue. So, it likely isn't a programming issue. When I contacted support I was told:
Hello (Motor_why),
Please to inform you that the PinePhone batch consider as developer state, for more info on PinePhone bring up, please visit PINE64 forum and also communicate with developers at PinePhone IRC, http://www.pine64.xyz, /join #pinephone
Your understanding and patience is greatly appreciated.
support team#2...
I don't know what to do. I am now posting here, Reddit. The private outreach didn't work, and since I can't return it for a phone that is vibrating all over, I'm willing to do what people recommend.
Have been having trouble getting mobile data on any of the available distributions, and finally with the help of IRC, manpages, and a few guides, I managed to get mobile data on my operator, which requires setting up an APN with user and password.
So for me it wasn't a simple matter of using ofonoctl wan --connect --append-dns, or simply enabling ofonod, or anything of the sorts. I had to dig in deeper.
This has only been tested under pmOS + Phosh so far, because it uses NetworkManager and it's easy to install ModemManager without messing up the whole system (like I did once under Ubuntu Touch). YMMV on other distributions.
Step 1
Install pmOS your favorite way, and make sure to install modemmanager
Code:
apk add modemmanager
Step 2
Disable ofono, enable modemmanager at startup
As root:
Code:
rc-service ofono stop
rc-update del ofono
rc-update del ofono-auto-enable
rc-update add modemmanager
rc-service modemmanger start
Step 3
Wait 10-20 seconds and check the status of your modem with:
Code:
mmcli -L
mmcli -m 0
If all is good, you can also see the 4G and modem icons in the status bar.
Once you've done the above successfully, you should see a new device in network manager (previously it was alled ttyUSB2) : cdc-wdm0
This is the device name to use in the next step
Step 5
Now configure the connection with nmcli, I'm not sure if you need to specify tall the APN info all over again or not, I'll have to try without and update this guide:
nmcli c add type gsm ifname cdc-wdm0 con-name OPERATOR-NAME apn APN.NAME user USERNAME password PASSWORD
Step 6
Verify connectivity with all the usual commands
Code:
nmcli c # check status of the connection named OPERATOR-NAME as above
nmcli d # check status of cdc-wdm0
ip addr # check for wwan0
Press 's' at any time to take a photo. Press 'q' to exit.
I recommend making this into a script and copying it to your SD card so you can avoid typing it in by hand.
Troubleshooting
The pmOS wiki states that the entity name is "ov5640 2-003c". I found that not to work.
If you get a message stating "Invalid argument (22)" then you may have the wrong entity name. Fortunately, you can get it like this:
Code:
media-ctl -d /dev/media1 -p
There should be two entities listed, one a source and the other a sink. You want the entity name for the sink. It will look like the ones mentioned above.
