| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,858
» Latest member: authorjaw
» Forum threads: 16,313
» Forum posts: 117,376
Full Statistics
|
|
|
| Temperature precision |
|
Posted by: joey - 05-01-2017, 04:37 PM - Forum: Heat Dissipation and Overclock Topic
- No Replies
|
 |
I just started playing with my Pine64 again, and I'm looking at including its temperature information in my home-grown graphing system. I found that it seems like mostly valid data in the /sys/class/thermal/thermal_zone0/temp file, but I noticed that it has zero digits of precision. It's currently reporting 36C idling on my desk, and if I run "stress --cpu 4" for a few seconds, it shoots up to about 80C within 10 seconds, so I can assume it's measuring real data.
Is integer precision the best I'm going to get? My RPis are reporting to about 3 decimals of precision. It's not a big deal, but an integer graph is pretty boring.
|
|
|
|
| question about my order |
|
Posted by: ta2025 - 05-01-2017, 02:25 PM - Forum: General Discussion on Pinebook
- Replies (3)
|
 |
I received my invitation for the 11" on April 26 and promptly paid for it via paypal and got an order confirmation.
Today, on the 27th I got a message that the 11" are out of stock but it appears to be a general message. Does this mean that there is an 11" model with my name on it already in the queue or does this mean that I didn't make the cutoff and I need to reorder a 14" model?
Thanks!
|
|
|
|
| Installing VS Code (& Chromium) |
|
Posted by: Prophesi - 04-30-2017, 01:44 PM - Forum: Linux on Pinebook
- Replies (21)
|
 |
INSTALLING VS CODE
You'll need to enable multiarch with armhf support, as you'll be using an armhf build of VS Code since arm64 support is still in the works. (TODO: add github issue link where the VS Code team discusses this)
Code: sudo dpkg --add-architecture armhf
sudo apt-get update
Now you'll need to head over to code.headmelted.com and get his latest armhf build. (The installer script won't work).
Code: https://bintray.com/headmelted/deb-code-oss/download_file?file_path=code-oss_1.10.0-201722210_armhf.deb
Next up, you'll want to use gdebi to help guide the installation and install the required dependencies.
Code: sudo gdebi code*.deb
You should now have code-oss installed! Huzzah! But if you try to run it in its current state, it won't boot up and complain about not being able to open certain shared libraries. There are still two packages left to install. You already have their arm64 version, but VS Code wants armhf.
Code: sudo apt-get install libxtst6:armhf
sudo apt-get install libasound2:armhf
Huzzah! VS Code should now boot up when you run code-oss in your terminal. The first boot will take a minute or two. Every subsequent boot of VS Code should be much faster. VS Code is probably loading up a thousand npm modules or whatever wizardry is required to get Electron apps to do their magic.
Enjoy! It's actually more performant than I expected an Electron app to be. Not a bad coding experience.
INSTALLING PIROLOCITO'S CHROMIUM
NOTICE: These steps are no longer necessary on Ayufan's newer builds, starting with 0.5.2, as chromium-browser comes preinstalled and does not need the --disable-seccomp-filter-sandbox flag.
While I'm at it, here's how you add Pirolocito's awesome Chromium build. It's the most recent chromium, and runs much faster and smoother than the Pinebook's default Firefox. If you're running ayufan's latest Linux build, you're in for a delightful web browsing experience.
Code: sudo add-apt-repository ppa:osomon/chromium-next
sudo apt-get update
sudo apt-get install chromium-browser
It requires the --disable-seccomp-filter-sandbox flag, so let's write an alias to save our poor human brain from having to remember and type that every time.
Code: echo "alias chrome=\"chromium-browser --disable-seccomp-filter-sandbox\"" >> ~/.bash_aliases
All subsequent terminal sessions will now be able to start chromium with its required flag by just running "chrome".
Now add a script/ad blocking extension! For your sanity's sake, and to speed up chromium.
SPEEDING UP CHROMIUM
We've got some new flags to set that should speed up Chromium considerably! All thanks go to Lukasz and longsleep for fiddling with this.
If you're running longsleep's build, then it should already be using these following flags by default.
Run the following with root privileges:
(05-14-2017, 04:59 AM)longsleep Wrote: cat > "/etc/chromium-browser/default" <<EOF
# Default settings for chromium-browser. This file is sourced by /bin/sh from
# /usr/bin/chromium-browser
# Options to pass to chromium-browser
CHROMIUM_FLAGS="\
--disable-smooth-scrolling \
--disable-low-res-tiling \
--enable-low-end-device-mode \
--num-raster-threads=4 \
--profiler-timing=0 \
--disable-composited-antialiasing \
"
EOF
Here are the flags Lukasz would like for us to test as well. I stripped out the ones already specified in longsleep's code:
(05-13-2017, 07:53 AM)Luke Wrote: These settings considerably improve chromium performance- please test them out and offer feedback.
In chromium searchbar type: Chrome://flags
Set the following:
Experimental canvas features - enable
Memory ablation experiment - enable (or 100mb - try both)
And as longsleep notes, it's also worthwhile to install the "No MouseWheel Zoom" extension to stop accidentally activating the Pinebook's two finger zooming.
|
|
|
|
| 11-inch backslash / pipe key |
|
Posted by: pagesix1536 - 04-30-2017, 10:55 AM - Forum: Linux on Pinebook
- No Replies
|
 |
The 11-inch Pinebook seems to have a odd issue with the backslash/pipe key which types out a greater than and less than symbol (< >). Here's how to fix it. Put this in one of your login scripts like .bashrc or /etc/profile or /etc/bash.bashrc
xmodmap -e 'keycode 94 = backslash bar'
|
|
|
|
| No HDMI Output |
|
Posted by: martinarcher - 04-27-2017, 07:00 PM - Forum: General Discussion on PINE A64(+)
- Replies (2)
|
|
Hello all! Finally getting around to trying my 2GB Pine 64 I got through the Kickstarter. Setting it up as a home calendar in the kitchen to replace a Raspberry PI version I have running that is beyond ready to retire.
-I bought a Samsung EVO+ 32GB microSD off Amazon. I figured not skimping on the boot drive was the way to go for these boards.
-I also bought a Anker 3A 5V supply with "Qualcomms IQ" support. I use these chargers on some really big backup battery packs and know they can put out a good bit of current. I am also using a really good MicroUSB cable.
-I have a tested HDMI I used with the Raspberry PI.
-I have 3 different monitors. A Dell, Samsung, and a touch screen Lenovo I intend on using.
-I have tried 4 different images (Android 6.0, Android 6.0 rooted, Remix OS 2.0, and Android 7.0
-I have used Win32Imager, Etcher, and am now flashing a image via Pine64Installer (very cool program by the way - talk about making it easy to image a card!)
I have tried prepping the card different ways using diskpart and cleaning the partition off the disk and still haven't had any luck getting the board to boot (or so I thought).
I then hooked up Wireshark to the Pine board and sure enough, ~55 seconds after applying power (Remix test) I get Ethernet activity whoch tells me the board is booting but not putting out any HDMI. I've tried 3 different displays. The Samsung won't even allow me to select the HDMI input as it says no HDMI device is detected.
Any idea how to get the HDMI output working on these boards? Do they need configured for HD displays after booting with a different display type (LCD)?
Thanks!
|
|
|
|
| Why not SOPINE? |
|
Posted by: bobpaul - 04-26-2017, 05:23 PM - Forum: Pinebook Hardware and Accessories
- Replies (3)
|
|
If this was discussed already, please forgive me. I only discovered Pine64 and Pinebook recently.
From what I've read about the Pinebook it looks like it basically uses a product specific laptop motherboard derived from the Pine64. When I first saw the product I was excited and assumed it contained a Pine64 or a SOPine. Then when a faster Pine64 SOC is released I could just swap boards for a cheap upgrade.
I'm just curious why that route wasn't taken. $100 is a cheap laptop for sure, but I'd be willing to bet the keyboard, screen, and wifi etc are still good in 2 or 3 years and it would be nice to be able to re-use via upgrade. Maybe this is something you can consider for future models?
|
|
|
|
|
