Beginner’s Guide to Installing Linux Mint 19

HOW TO INSTALL LINUX MINT 19

PREPARATION

1. Create bootable DVD or USB media.

* Download ISO image from https://linuxmint.com/
* You can burn a bootable DVD in Windows 7 and up simply by inserting a blank DVD and then double-clicking the ISO file.
* Creating a bootable USB drive will require you to install software. Find out more here: https://mintguide.org/tools/317-make-a-bootable-flash-drive-from-an-iso-image-on-linux-mint.html

2. Boot Linux Mint 18.

* You will have to turn off Secure Boot in your computer’s BIOS setting to be able to boot from a DVD or USB drive.
* Once you get Linux Mint 19 booted, take time to play around and ensure that all of you hardware is working properly.
* Check to see if you will need any proprietary drives for your system.
* Take some time to read through the Linux Mint User’s Guide to familiarize your self with the system.

3. Backup ALL Data You Wish To Keep!

* Do NOT use commercial backup software or the built-in Windows backup utility. Linux Mint MUST be able to read the files you create.
* Backups MUST be stored on a USB drive or other removable media.
* It is OK to store backup data in a Zip file. Linux Mint can open them with Archive Manager.

INSTALLATION

WARNING! Proceed at your own risk. Installing Linux Mint will wipe out your current Windows installation and all data you have stored on the computer. There is no way to “uninstall” Linux Mint!
* It is a good idea to have another computer, smartphone or tablet available so you can have access to the Internet in case you need to look something up.
* Turn off Secure Boot in your computer’s BIOS settings.
* Hook computer to the Internet with an Ethernet cable if drivers will be needed to use Wi-Fi.
* Boot Linux Mint
* Launch Linux Mint’s installer and follow the directions.
* Restart the computer. You are now Running Linux Mint!

POST-INSTALLATION SETUP

Follow the “First Steps” outlined in the Welcome Screen:
* Setup Timeshift
* Change to local mirrors
* Install ALL updates!
* Check for and install drivers.
* Restart the computer.

Tweaks:
* Open GNOME Disks and enable Write Cache for all internal drives.
* Enable recommended packages in Synaptic Package Manager
* Configure the Desktop and choose startup applications.
* Optional: Install Google Chrome browser: https://www.google.com/chrome/index.html
* Restart and have fun!

Linux Mint is now fully installed and ready to use.

Please be sure to give EzeeLinux a ‘Like’ on Facebook! Thanks! https://www.facebook.com/EzeeLinux
Check out http://www.ezeelinux.com for more about Linux.

Joe Collins

Joe Collins worked in radio and TV stations for over 20 years where he installed, maintained and programmed computer automation systems. Joe also worked for Gateway Computer for a short time as a Senior Technical Support Professional in the early 2000’s and has offered freelance home computer technical support and repair for over a decade.

Joe is a fan of Ubuntu Linux and Open Source software and recently started offering Ubuntu installation and support for those just starting out with Linux through EzeeLinux.com. The goal of EzeeLinux is to make Linux easy and start them on the right foot so they can have the best experience possible.

Joe lives in historic Portsmouth, VA in a hundred year old house with three cats, three kids and a network of computers built from scrounged parts, all happily running Linux.

Source

Linux Today – Complete guide to Dual Boot Ubuntu 18.XX with Windows 10

Oct 17, 2018, 07:00 (0 Talkback[s])

(Other stories by Shusain)

Learn how to Dual boot Ubuntu 18.xx along with Windows 10. Ubuntu 18.04 aka Bionic Beaver was released on April 26th, 2018 with a lot of changes on front end as well as on backend. Major change that anybody who has ever used Ubuntu, will notice is the Desktop Environment.

Complete Story

Related Stories:

Source

Imunify360 3.6.6 is here – Imunify360 Blog

Imunify360 3.6.6 is here

We are pleased to announce that a new updated Imunify360 version 3.6.6 is now available. This latest version embodies further improvements of the product as well as bugfixes.

Tasks

  • DEF-6162: AI-BOLIT vulnerabilities are now marked as suspicious.

Fixes

  • DEF-6170: blacklisted IP is no longer put into Gray List by sensor alert.;
  • DEF-6205: do not fail if /etc/virtual/domainowners has wrong UTF-8 data;
  • DEF-6220: fixed CLNError() is not JSON serializable;
  • DEF-6221: fixed SEND_ADDITIONAL_DATA.enable label in settings in UI.

To install the new Imunify360 version 3.6.6 please follow the instructions in the documentation.

The upgrading is available since Imunify360 version 2.0-19.

To upgrade Imunify360 on CentOS/CloudLinux systems, run the command:

yum update imunify360-firewall

To upgrade Imunify360 on Ubuntu systems, rut the command:

apt-get update
apt-get install –only-upgrade imunify360-firewall

More information on Imunify360 can be found here.
Source

How to Connect Ubuntu Linux Remotely from Windows via RDP

xrdp linux desktop remote rdp

How often do you access Linux Desktop? What tools do you use to access remote desktop?

Xrdp is an open source tool which allows users to access the Linux remote desktop via Windows RDP. Apart from Windows RDP, xrdp tool also accepts connections from other RDP clients like FreeRDP, rdesktop and NeutrinoRDP

Xrdp Requirement

  • xrdp and xorgxrdp packages
  • Listens on 3389/tcp. Make sure your firewall accepts connections

In this article, I will show how you can remotely connect to Ubuntu Desktop from a Windows machine using Xrdp tool.

1) Installation on Linux

on Ubuntu 18.04

First, you need to install Xrdp on Ubuntu

# apt install xrdp
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following additional packages will be installed:
xorgxrdp
Suggested packages:
guacamole xrdp-pulseaudio-installer
The following NEW packages will be installed:
xorgxrdp xrdp
0 upgraded, 2 newly installed, 0 to remove and 256 not upgraded.
Need to get 498 kB of archives.
After this operation, 3,303 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

You have to configure the polkit rule to avoid an authenticate popup after inputting the username and password at the xrdp login screen on windows

# vim /etc/polkit-1/localauthority.conf.d/02-allow-colord.conf

polkit.addRule(function(action, subject) {
if ((action.id == “org.freedesktop.color-manager.create-device” || action.id == “org.freedesktop.color-manager.create-profile” || action.id == “org.freedesktop.color-manager.delete-device” || action.id == “org.freedesktop.color-manager.delete-profile” || action.id == “org.freedesktop.color-manager.modify-device” || action.id == “org.freedesktop.color-manager.modify-profile”) && subject.isInGroup(“”))
{
return polkit.Result.YES;
}
});

restart the xrdp service

# systemctl restart xrdp

Then make sure that the service is running

# systemctl status xrdp
● xrdp.service – xrdp daemon
Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: en
Active: active (running) since Tue 2018-10-16 02:05:21 WAT; 11min ago
Docs: man:xrdp(8)
man:xrdp.ini(5)
Main PID: 2654 (xrdp)
Tasks: 1 (limit: 2290)
CGroup: /system.slice/xrdp.service
└─2654 /usr/sbin/xrdp

Now make sure to automatically start the service at the system startup

# systemctl enable xrdp
Synchronizing state of xrdp.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable xrdp

Now you will need to check your ip address because you will need it for the connection

# ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0c:29:ef:f6:9b brd ff:ff:ff:ff:ff:ff
inet 172.16.8.177/24 brd 172.16.8.255 scope global dynamic noprefixroute ens33

My ip address is 172.16.8.177. So keeps yours it in your mind.

Xrdp works with port 3389 so make sure to open it. UFW is disabled by default so you will need to enable the firewall and create a rule for xrdp

# ufw enable
# ufw allow 3389/tcp

Now you can continue the configuration on windows side

On Centos/Redhat 7

Make sure to install the Epel repositories before

# rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

Now install xrdp packages

# yum update && yum -y install xrdp tigervnc-server

Add a rule in the firewall. On Centos/RedHat is not ufw but firewalld to configure

# firewall-cmd –permanent –zone=public –add-port=3389/tcp

Then reload the firewall

# firewall-cmd –reload

Now enable and restart the xrdp service

# systemctl enable xrdp && systemctl restart xrdp

Check your ip address for the remote connection on Windows

2) Connect from Windows

On your windows machine such as windows 10 in our case, launch the default remote desktop connection tool.

You will need to enter the ip address of your machine and you will be asked to enter the username

Access Remote desktop of Ubuntu/CentOS

Enter the ip address and the username

Now confirm the information and launch the connection. If you are not logged out in local, the remote login would fail.

Now you will be asked for your password

Now confirm your credentials. You can see the IP address of my Ubuntu on the top and the login page. Enter your password and enjoy

Are you aware of any other tools? Please advise us on the comments

Read Also:

Source

DragonFlyBSD Continues Squeezing More Performance Out Of AMD’s Threadripper 2990WX

DragonFlyBSD 5.4 should be a really great release if you are a BSD user and have an AMD Threadripper 2 box, particularly the flagship Threadripper 2990WX 32-core / 64-thread processor.

 

 

The project leader of this long ago fork from FreeBSD, Matthew Dillon, has been quite outspoken about the Threadripper 2990WX since he purchased one earlier this summer. This prolific BSD developer has been praising the performance out of the Threadripper 2990WX since he got the system working on the current DragonFlyBSD 5.3 development builds.

 

Since getting DragonFlyBSD running on the Threadripper 2 hardware in August, he’s routinely been making performance tuning optimizations to DragonFly’s kernel to benefit the 2990WX given its NUMA design.

 

Just earlier this week he landed another NUMA optimization where by reducing the NUMA memory contention he was able to help his kernel’s build speed improve by about 8%.

 

Given the excitement over Threadripper 2 and Matthew Dillon’s continued optimizations, I ran some benchmarks to see where the performance is currently at with the latest daily image of DragonFlyBSD 5.3-DEVEL for what will eventually be released as DragonFlyBSD 5.4.0 stable.

 

I compared these performance results on the same system to some DragonFlyBSD 5.3 snapshots I did back in August when he initially added the Threadripper 2 support and following some early performance optimizations. Since August has been more performance tuning as well as upgrading the default GCC compiler, continued work on its HAMMER2 file-system, and much more as shared routinely with our DragonFlyBSD coverage on Phoronix. Obviously DragonFlyBSD 5.2 (the current stable release) couldn’t be tested for this comparison since the X399 + Threadripper 2 has only been working on the 5.3 development series.

 

 

The system used the entire time was the AMD Threadripper 2990WX running at stock speeds on the ASUS ROG ZENITH EXTREME motherboard, 4 x 8GB DDR4-3200 memory, and Samsung 970 EVO NVMe SSD. Benchmarks were carried out in a fully-automated and reproducible manner using the Phoronix Test Suite.

Source

elementary OS 5 ‘Juno’ Linux distribution is ready to replace Windows 10

Using a computer should be fun and inspiring. Windows used to be enjoyable for many consumers, but Microsoft’s latest operating system just isn’t. Not only is Windows 10 very buggy — deleting user files is as bad as it gets, folks — but the spyware nature with the excessive telemetry can make the user feel like a visitor on their own computer. Hey, you spent good money on your PC — you should feel at home on it, right?

Enter Linux. God bless the open source kernel. Thanks to Linux-based operating systems and excellent free open source software, it is possible to return to the better days of computing. One operating system in particular has put a ton of focus on the user experience — elementary OS. This is an oversimplification, but the interface feels like a blend between GNOME and macOS. It looks good, is intuitive, and is an absolute pleasure to use. October may be the month of Halloween, but it feels more like Christmas, because the latest version of the operating system — Juno — is ready to be unwrapped like a gift.

“We’ve always prided ourselves on the design of elementary OS. The very origins of elementary OS come from iconography and a bit of pixel-perfect-obsessive design. We don’t believe in drastic redesigns for the sake of redesigns — after all, good design is long-lasting — but we are constantly evolving, adapting, and improving the design of elementary OS. In Juno, we’ve continued that trend and refined the smallest details for a more pleasant experience,” says Cassidy James Blaede, UX Architect and Open Source Contributor, elementary OS.

ALSO READ: Plex for Linux now available as a Snap

Blaede further says, “With every release comes a smorgasbord of under-the-hood improvements, library updates, etc. and elementary OS 5 Juno is no exception. It comes with Linux 4.15, which brings improved hardware support and performance over previous versions. Mobile broadband device support has been added to the networking stack. Capnet Assist, our captive portal login helper, now uses configuration and detection from network manager; consequently, it’s more reliable and configurable.”

The total number of changes and improvements is massive and overwhelming, so I urge you to read the official release announcement found here. Quite frankly, the care put into the lengthy and detailed announcement shows just how passionate the developers are. The focus on the little things (which do matter) is reminiscent of Steve Jobs with Apple — on a much smaller software-only scale, of course.

If you are ready to ditch Windows 10 and reclaim your computer as your own, you can grab the elementary OS 5 Juno ISO here. Keep in mind, while it looks like you must pay for the operating system, you actually don’t — you can pay what you want, including nothing. I’m sure the developers would love if you sent some money their way, but if you select “custom” and enter “0” without quotes, the “Purchase” button changes to “Download.” Well done, ya cheapskate!

If you like the operating system after trying it, you can always go back and donate money later. You could also buy some of the official elementary OS merchandise — such as a t-shirt — here. This way, you can contribute funds to the developers and look stylish too!

Source

Puppeteer VS Selenium | Linux Hint

Today when it comes to automated web testing, Puppeteer and Selenium are the two names that come up. One of the main reasons why they are well-known is their ability to execute headless browsers. Therefore before we proceed with the article, let’s have a quick look at what headless browsers are and their advantages.

In basic terms, headless browsers are browsers that can be used for testing usability of web pages and executing browser interactions just like you would with your regular browser. The only difference here is that there is no Graphical User Interface (GUI) and they are usually executed from the terminal.

Headless browsers:

  • help reduce resource usage greatly
  • they are faster
  • they are ideal for web scraping purposes
  • they can be used to monitor network application performance

Now that we have known a major factor for both tools, we can proceed.

Puppeteer is a Node library from Google that provides a simple API to control headless Chrome. Through Puppeteer, common tasks such as typing in inputs, clicking on buttons, testing usability of web pages and even web scraping can be carried out easily.

Puppeteer is official from the Chrome team, and uses the Chrome Remote Debug Protocol, just as we would find with the Chrome Devtools. This library supports the modern JavaScript syntax available in Google Chrome.

Setup

Installing and getting started with Puppeteer is very easy. Since Puppeteer is a Node library, it can be installed using the npm tool.

Installation can be done with the command below:

Running the command above installs Puppeteer. It is expected to also download a recent version of Chromium that would work with the API.

The size of Chromium is varies according to operating system:

  • ~170MB for Mac
  • ~282MB for Linux
  • ~280MB for Windows

After installation of Puppeteer, you can find out more information on how to get started, you can as well check out more code examples.

Features

While Puppeteer’s ability to launch a headless browser is one feature that has gained it some fame, that is not the only feature that makes it awesome. Puppeteer also has a couple of other features that makes it useful, let’s take a quick look at some of them.

Easy Automation:

While there are other tools that can be used for web automation, Puppeteer comes out tops. This is due to the fact that it works fine for one browser only, which is the Headless Chrome browser, therefore it carries out web automation tasks in the most efficient way possible. Puppeteer also works fine with popular unit testing libraries such as Mocha and Jasmine.

Screenshot Testing:

This is a vital feature for any automated web testing task. Screenshots are important, and help keep track of result of interactions with elements on a web page. Libraries such as Puppeteer-screenshot-tester also exist in Puppeteer that provides the capability of comparing screenshots generated while testing. Asides generating screenshots of tests, PDFs can also be generated from tested web pages in puppeteer.

Performance Testing:

Chrome provides DevTools that allow the recording of the Performance Timeline of web pages, and Puppeteer takes advantage of this too. With Puppeteer, timeline traces of websites can be captured to examine performance issues. Due to the Puppeteer’s high-level API control over Chrome Developers Tools Protocol, it gives users the ability to control service workers and test caching of websites.

Web Scraping:

A talk about features would not be completed without acknowledging the ability of Puppeteer to be used for web scraping purposes. Learning to use Puppeteer as a web scraper is quite easy, take a look at the API documentation.

Pros

  1. Works fine for visual testing.
  2. Great for end to end testing.
  3. Fast when compared to Selenium.
  4. Can take screenshots of webpages.
  5. More control over tests through Chrome.
  6. Can test offline mode.

Cons

  1. Supports only JavaScript (Node)
  2. Supports only Chrome

Selenium

Selenium is a powerful web testing framework, that has the capability of automating web applications for testing purposes. Selenium is also known for its ability to automate web based administration tasks.

Selenium comes in two parts; the Selenium WebDriver for creating powerful, browser based automation suites and test and the Selenium IDE for creating quick bug reproduction scripts.

Not forgetting that Selenium also supports headless browsers as seen with Puppeteer.

Setup

Unlike with Puppeteer, setting up Selenium is not straightforward. Selenium supports many languages and different browsers, therefore those possible conditions need to be taken care of.

Listed below are links to official tutorials on how to setup Selenium bindings for different languages.

Asides supporting different languages, Selenium also supports multiple browsers. Unlike Puppeteer which installs Chromium during installation, you may have to install web drivers for the web browser of your choice.

Here are links to web drivers for Mozilla Firefox and Google Chrome.

If you wish to use the Selenium IDE too, it also exists for multiple browsers. Here are links to Selenium IDE for Mozilla Firefox and Google Chrome.

Features

It’s ability to work with headless browsers has made it unarguably the most popular web automation tool, but there are other features that make it powerful.

Multi-Language Support:

This is one very important Selenium feature. With its multiple language support, more developers can get to use the tool for their web automation testing tasks. While one may think its multi-language support would make it slow, Selenium still runs at a good speed as starting up a server in Web Driver is not required.

Multi-Platform Support:

The same way Selenium is not restricted by language barriers, it is also not restricted by platform barrier. It is no news that web application behave differently on multiple platforms. Selenium gives testers the ability to test across major web browsers to provide a smooth user experience for users across different browsers. Asides browsers, Selenium can also be used to test on mobile such as Android, iOS, Windows, Blackberry apps.

Recording Tool:

With Selenium IDE, it is easy to record web automation tests. Selenium IDE allows testers make use of the recording capability as well as the autocomplete support and ability to navigate commands. The Recording Tool has stopped working on Firefox 55 and later versions, however there are other plugins on Firefox that serve the same purpose. Therefore, the ability to record tests remains a major Selenium feature.

Web Scraping:

While Selenium is used for testing web applications, it also scales well as a web scraper. Selenium can be used to scrape AJAX websites and the most difficult websites to scrape, provided you can understand the HTML structure. You can check out this tutorial on using Selenium for web scraping with Python.

Pros

  1. Multi-platform support.
  2. Multi-language support.
  3. Ability to record tests.
  4. Can take screenshots too.
  5. Huge community of users.

Cons

  1. Slow when compared to Puppeteer.
  2. Limited control over tests when compared to Puppeteer.

Conclusion

If you are not bothered about testing web pages on other platforms asides Chrome, then you are fine working with Puppeteer, provided you are able to work with JavaScript(Node). However if you are concerned about multiple platforms, then using Selenium is a no-brainer. Talking about their web scraping abilities, both tools even themselves out there. It should be noted though that Puppeteer could be faster than Selenium.

Any tool you choose at the end of the day should be fine, just enjoy writing your automation scripts.

Source

Sysadmin tools, secrets of Kconfig/kbuild, 11 KDE apps, tcpdump, Laverna, Python, and more

Find out what readers were into on the site last week.

You probably know (or can guess) what alerting and visualization tools are used for. Why would we…

Dive into understanding how the Linux config/build system works.

This flexible, powerful command-line tool helps ease the pain of troubleshooting network issues.

Which fun or quirky app do you need today?

Keep your notes secure yet accessible with this basic, easy-to-use open source app.

Here’s how I used Python to discover a strategy for cost-effective fill-ups.

A step-by-step guide for running Minikube.

These best practices will make your employees more savvy and your organization more secure.

Driving large-scale organizational change is painful, but when it comes to DevOps, the payoff is…

Learn the fascinating story of Ada Lovelace, a gifted mathematician, in this book review.

About the author

Rikki Endsley

Rikki Endsley is a community architect and editor for Opensource.com. In the past, she worked as the community evangelist on the Open Source and Standards (OSAS) team at Red Hat; a freelance tech journalist; community manager for the USENIX Association; associate publisher of Linux Pro Magazine, ADMIN, and Ubuntu User; and as the managing editor of Sys Admin magazine and UnixReview.com. Follow her on Twitter at: @rikkiends.

Source

CubieBoard9 SBC cranks up Actions S900 SoC

Oct 5, 2018 — by Eric Brown

CubieTech has posted specs for a “CubieBoard9” SBC with a quad -A53 Actions S900 SoC with 3GB LPDDR3, 16GB eMMC, WiFi/BT, and dual independent displays with HDMI, MIPI-DSI, LVDS, and eDP.

A product page has appeared on the CubieTech website for an unpriced CubieBoard9 SBC that appears to be a replacement for the Cubieboard4. We don’t recall seeing the CubieBoard9 when we checked the site in May for our catalog of 116 hacker boards. We have not heard back from CubieTech about the status of the SBC, which has yet to appear on the Cubieboard.org community site. Considering its prominent placement on the CubieTech home page, however, we’re gambling that the SBC will avoid the fate of the Allwinner A80 based CubieBoard8, which was announced in 2014, but never reached market.

CubieBoard9, front and back
(click images to enlarge)

 

The CubieBoard8 may have been shelved because CubieTech became an official distributor of Actions Technology application processors in July 2017, and then

launched four Actions-based open source SBCs

with Cubieboard.org community support. These include the CubieBoard7, built around the quad-core Cortex-A53 Actions S700, and the CubieBoard6, which instead taps the quad -A9 Actions S500. CubieTech also released two sandwich-style versions — the CubieAIO-S700 and CubieAIO-S500 — which use the same SoCs via its Einstein compute modules.

The 115 x 111mm CubieBoard9 is larger than the CubieBoard6 and 7, with a layout that closely approximates that of the 111 x 111mm CubieBoard4. While the CubieBoard4 is equipped with an octa-core Allwinner A80 (quad -A15 and quad -A7), the CubieBoard9 instead features the quad-core Actions S900, which is found on uCRobotics’ 96Boards compatible Bubblegum-96.

CubieBoard9 with case (left) and running dual independent displays
(click images to enlarge)

 

The Actions S900’s four Cortex-A53 cores have a faster 1.8GHz clock rate compared to the S700, at least according to uCRobotics (CubieTech lists no clock rate). It also switches from a Mali-450 GPU to the same 600MHz PowerVR G6230 found on the CubieBoard4.

CubieTech makes no mention of OS support except to note support for 64-bit operating systems. Presumably you’ll get the same Actions-tailored images for Android 5.1 and Debian with Linux Kernel 3.10 found on the CubieBoard7. Like other CubieBoards, this latest model should be an open hardware SBC supported with schematics.

CubieBoard9 detail and portside views
(click images to enlarge)

 

The CubieBoard9 integrates 3GB LPDDR3 and 16GB eMMC plus a microSD slot. The product page mentions a 10/100 Ethernet port — just like the CubieBoard6 and 7 — which is disappointing considering that the CubieBoard4 has a 10/100/1000 GbE port.

The CubieBoard9 also provides a wireless module with 2.4GHz/5GHz 802.11b/g/n/ac and Bluetooth 4.1 via an Ampak AP6255 module. This week, as part of its WiFi 6 (802.11ax) announcement (or more accurately Wi-Fi 6 for those who are not too lazy to use hyphens), the Wi-Fi Alliance has simplified the WiFi naming scheme. The 802.11n spec is now called WiFi 4, 802.11ac is WiFi 5, and 802.11ax is WiFi 6.

The CubieBoard9 features far more media interfaces than the Cubieboard4. You get dual independent displays with a choice of 2x HDMI 1.4 ports for [email protected] video plus 2x LVDS and single MIPI-DSI and eDP interfaces. These are joined by dual MIPI-CSI connections and dual audio jacks.

CubieBoard9 dimensions (left) and package contents
(click images to enlarge)

Norwegian slang for “party on.”

Preliminary specifications listed for the CubieBoard9 include:

  • Processor — Actions Semiconductor Actions S900 (4x Cortex-A53 cores @ up to 1.8GHz); PowerVR G6230 GPU @ 600MHz with OpenGL ES 3.1
  • Memory/storage:
    • 3GB LPDDR3-800 64-bit RAM (possible option for 2GB)
    • 16GB eMMC
    • MicroSD slot
  • Wireless — Dual-band (2.4GHz/5GHz) WiFi 5 (ac) with Bluetooth 4.1 (Ampak AP6255) with ant. connector and ext. antenna
  • Networking — 10/100 Ethernet port
  • Display/media I/O:
    • 2x HDMI 1.4a ports at up to 4K @ 30fps
    • MIPI-DSI
    • 2x LVDS (DSI)
    • eDP (DSI)
    • MIPI-CSI
    • MIPI/DVP-CSI
    • Dual independent display support
    • 2x audio jacks (mic-in, earphone out); second mic-in header
  • Other I/O:
    • USB 3.0 OTG port
    • 4x USB 2.0 host ports
    • 2x GPIO headers
    • UART header
  • Other features — IR receiver; RTC with cell battery connector; 2x LEDs; power, reset keys; ADFU key; heatsink; acrylic case kit
  • Power — 5V DC jack; Li-Po battery connector
  • Dimensions — 115 x 111 x 18mm

Further information

No pricing or availability information was provided for the CubieBoard9. More information may be found on the CubieTech CubieBoard9 product page, and information may eventually appear on Cubieboard.org.

Source

WP2Social Auto Publish Powered By : XYZScripts.com