Language Selection

English French German Italian Portuguese Spanish

Fallen Under the Spell of Arch Voodoo

Filed under
Linux
Reviews
-s

I received an email the other day from a visitor saying how much he enjoyed reading my reviews, but he was a disappointed as it seems tuxmachines had been ignoring his favorite distro. As it was a nice distro and a new version was released three weeks ago, he felt it deserved some attention. So when my new burner arrived, it was the first distro I tested. In fact, I've been using it for a couple of days now and the author of that email was correct when he said it was fast, stable, and up-to-date. I refer to Arch Linux 0.8 Voodoo.

I used the torrent to pull Arch in, and it came in surprisingly fast. At 300KB/s, it was just about the fastest torrent pull I've experienced, at least recently. 561MB arrived in short order and became the distro that tested if my new dvd/cd burner worked. Not 100% sure what to expect, I mkfs.ext3 this old partition I had laying around and booted the install disk.

The first screen that appears offers some helpful information and the available boot options. I didn't think I needed any and just pressed Enter. They system booted with typical linux standard output and brought me to another information screen with instructions for some of the various installation options, such as the logfile, keymap, or setup method. The setup methods are Normal or Expert. If one chooses the Normal install, they start a setup routine very similar to what is found with Slackware.

The installer for Arch and Slackware are what I refer to as ascii-graphical. I just made up that term years ago to distinguish the ncurses interface from actual text-installs. To this day some folks still call these Slack derived installers "text." Text is just that, text. It's where one must type in every command to accomplish the install. The installer in Slackware, Arch, and Zenwalk, etc, is not text. It might be keyboard driven, but one is offered choices and after navigation with the arrow keys, one clicks OK using the Enter key instead of clicking with the mouse.

After the welcome screen, one chooses the install source. Your choices are from cdrom or ftp. I had downloaded the install iso, so I chose cdrom. One can get a boot image and install over the net from an ftp repository if they prefer. Then one is taken to the setup menu, again similar to Slack's. Here one can prepare their harddrive using cfdisk or allow the Arch install program to auto-prepare the disk. This latter method takes over the whole drive and makes the necessary partitions. If one doesn't need to make partitions, they can skip ahead to selecting the swap and / partitions and choosing the filesystem. One can choose their favorite filesystem from reiserfs, ext2 & 3, jfs, xfs, and vfat (iirc).

Next one selects the packages for installation. One screen suggested that one only install the base system first and then install the rest after making sure the base boots. Or that's how I understood it, and that's what I did. I selected base install and Yes to all packages by default. It took no time for this step to finish and I went on to number 4 in the menu, Configure System.

During the first phase of Configure System, one can opt to have their hardware auto-detected. This is always a good idea and when presented with the choice, I always go with auto-detection. This step includes answering some preference questions concerning support for USB devices, firewire, pcmcia, nfs shares, raid, lvm volumes, or encrpted volumes. Then one is asked which is their preferred text editor, vim or nano, so that they can edit the system configuration files.

Editing the system configuration files is not as complicated as it sounds. During this step, one is presented a list of files for review. For the most part, they are already configured. One just needs to glance over them to make sure no changes are in order. For example in /etc/rc.conf you might want to input your hostname, change the timezone, or set your internet connection information. Next is /etc/hosts. In that one you might want to put your ip and hostname.domainname hostname. /etc/fstab will already be set up for your current system, but you can add any partitions you might wish mounted at boot. The /etc/mkinitcpio.conf sounds a bit scary, but it's pretty much ready. I added support for my chosen filesystem, but it might not have been needed. /etc/modprobe.conf is available if you have any exotic hardware. For the most part, this isn't need as most is auto-detected. You will probably want to add your nameservers to the /etc/resolv.conf file. /etc/locales.gen offers a lot of examples and lists of locales, so it's not difficult to pick out yours. And finally there is the root password. This is the interactive portion where one inputs their chosen root password as found in Slack's installer or issuing passwd at the commandline. So, all in all, there really isn't much to do during System Configuration, but one should not skip it.

Next one installs the kernel and bootloader. Again menu-driven one just chooses their preferences. Grub and lilo are both available. At this point the install is finished and I rebooted into my base Arch install.

At that time I had no X nor window manager. Arch uses pacman for the package manager and it functions in much the same way as apt-get in Debian and derivatives. In fact, the steps are almost identical. One must set up a configuration file of repositories and update the database before using it. As with most distros these days, Arch's pacman.conf already has sufficient repositories configured. You can add your own or uncomment some of the extra choices such as unstable or community. One then updates, or refreshes as pacman calls it, the database with pacman --sync --refresh. It is recommended that we then update the system to current and even after just three weeks there were several updates available for me. I accomplished that with pacman --sync --sysupgrade. There are several handy options to use with pacman, but for the most part, one will only need to issue pacman --sync <package name>. Sync pulls packages in from remote ftp mirrors while -add will install local compressed tarballs. See the online wiki for more options or man pacman is complete as well.

So, in my case I merely typed pacman --sync xorg kde. It took a while to download the 300+MB of packages and with so many, I was a bit nervous that installing them might fail. However, it did not. After downloading for a couple hours, the system worked away for a bit installing packages. A progress bar for each package was displayed to let me know things were proceeding along. And finally it was done. There was no /etc/X11/xorg.conf file present, so I issued the xorgconfig command. It's the same procedure as the old xfree86config. It is an interactive X setup. If you've ever configured or paid attention when accepting the defaults in any Linux install, this configuration shouldn't be much of a problem. Choices are offered and many times only hitting the enter key is required to use the defaults. All one really needs to know is their video card. Knowing the horizonal sync and vertical refresh is quite helpful, but if you don't just pick one of the lower safe choices.

Pacman reported that there wasn't a kdm or xdm available, so I just use xinit /opt/kde/bin/startkde to start KDE. Gnome and XFCE4 are also available. Installing kde pulled in a lot of dependencies (including gtk, *sql libs, cups, lm_sensors, cairo, media codecs, etc) so that with just xorg and kde, I had a complete system ready for use already. After starting KDE, I installed The Gimp and Firefox. OpenOffice.org, koffice, and abiword are also in pacman repos. The KDE version is 3.5.6, the kernel is 2.6.20, gcc is 4.1.2, gimp is 2.2.13, firefox is 2.2.0.3, gnome is 2.18, and xfce4 is 4.4.1. A full list of current and extra, as well as testing and unstable, packages can be found here.

In the KDE desktop, one finds the complete KDE suite. It's mostly default, but Arch has added their own customized wallpaper and splash screen. It a really pretty blue background with a nice modernistic almost jellied version of the Arch arch in the center with the system identification in the lower right corner. The busy cursor is a teny tiny little blue arch as well. That's pretty cute. In the menu one finds an entry labelled Archlinux that leads one to handy links to the various hotspots on the Arch website, such as Documentation, Forum, Donate, and homepage.

        


I searched the forum for a few answers, such as how to improve the gtk fonts, and I found that the forum is quite active and full of information. It seems from a cursorary glance that all questions are answered in a useful and friendly manner. The Documentation could use a bit more detail in certain areas, but they have a lot more documentation some others. So, all in all, it's quite useful.

This release marks the end of an era for Arch. Beginning with the next release, there will no longer be the .7, .8, or 1.0 type version numbers. They state that from now on they will be versioning their releases to coincide with the release date, year and month.

In conclusion I found Arch to be just what it advertises. "Arch is fast, lightweight, flexible and simple." Some say that it may not be newbie friendly, but I tend to disagree somewhat. Sure there's a bit of configuration needed, but nothing that should be overwhelming. Anyone that has installed any Linux before can probably handle installing and configuring Arch.

I think Arch's most significant strong point is in the fact that it's so customizable. Unlike some distros that install everything or offer rigid defaults, one installs just what they need and want with Arch. With the surprisingly complete repos, one can install how little or much software they choose. With the trend in Linux these days of making things so easy for the newcomer, sometimes one loses most of the choices once offered. So, Arch Linux is a refreshing change of pace. What user configurations are needed are not complicated and sane defaults or useful real-world examples are offered for most. All my hardware was auto-detected, so no configuration was needed in that area. My only complaint is I'm going to have to do some more work on the fonts. Whereas the fonts aren't what one might classify as ugly, they aren't as pretty as on some systems. I would also suggest they dress-up KDE a bit more.

Arch Linux Homepage
Arch @ Distrowatch





ArchLinux

One note. Kdm is part of kdebase, it's not a seperate package.
Also, I really recommend you try gnome under ArchLinux as it works much better than kde.
I've been running gnome for over a year and a half on ArchLinux and I am very satisfied with the current gnome 2.18
Here's my current ArchLinux desktop http://img362.imageshack.us/img362/3408/screenshotzp9.png
Finally, thank you for writing this excellent review of ArchLinux.

ArchLinux

I really recommend you try kde under ArchLinux as it works much better than gnome.
I've been running kde for over a year and a half on ArchLinux and I am very satisfied with the current kde 3.5.6

You think so?

I'm running arch since 2004 now, without gnome even installed. I never had any problems with KDE, or any cooponent of it, and think the kde maintainers do a great work on it (working with kde since version 1 or 1.2 of kde, and for me it always made a better impression than gnome).

What gnome differs from kde: not that many apps are installed with gnome. More choice is given, but i like even xfce more than gnome. At least - with arch we have the choice.

The review is pretty much what i feel about arch. There could be done a lot of making it easier for several "special" usage, and in some terms more user friendly (network scripts and similar), but it's a complete and friendly distribution. Personally, i liked the comment about the forum best, since that is what actually makes archlinux to what it is - the communtiy.

Though, i'm developing on the system, and don't "work" in a common way (mail, office, watching movies, playing mp3s, ..). For Office and Mail i use Citrix, which is fully integrated into the linux desktop since version 10.

ArchLinux

bugme, I never said KDE is bad. Both Gnome and KDE are equally good. It's a matter of taste and I just happen to prefer Gnome over KDE.

silly and sad

It's sad that someone would lie when what they wrote is right there in black and white, and silly when it's something so inconsequential as a desktop preference.

Great review

Thanks for the great ArchLinux review. We currently have a little list going on the main archlinux.org page of reviews of the distro - would you mind if we linked here?

re: Great review

Naw, I don't mind at all. Thanks. Congrats on a fine release too.

Arch Linux on laptops

Arch Linux seems to be a great distribution for laptops as well. CPU frequency scaling as well as suspend to disk and RAM work with minimal effort when following their wiki. I have been using Arch Linux for several months now without any serious issues and I really love the fact that I can do an entire system upgrade periodically without too much trouble and without having to burn new CDs. Also, I was able to install the earlier version of Arch Linux with LVM using the command line even though I am a relative newcomer to using Linux. Apart from this Arch Linux also offers the option to install packages from source if necessary! Indeed a great distribution!

re: arch on laptops

That is wonderful news. Thanks so much for sharing. I felt a little bad I didn't test it on my laptop, but I knew basic support was there. I saw some of the packages being pulled in for the KDE install.

thanks again.

Arch on laptops

By the way, I forgot to mention that I am using the 64 bit flavor of Arch Linux on my laptop and it works beautifully! For those that may not be already aware, Arch also offers a 64 bit version. Among the hundreds of Linux distributions listed on Distrowatch, there are very few distributions that offer 64 bit support. Given how involved it is to get Gentoo Linux set up and running, Arch is an ideal compromise between binary and source based distribution and a real breeze to keep up to date.

Excellent review about an excellent distro!

Yeah it's me the grandmaster of offtopic blabbering from #PCLinuxOS Wink
I've been using the latest Arch now for some weeks and IMO it truly shines
as a distro for us not so newbie users ... I was waiting for you
to review it and my waiting was worth it thank you srlinuxx Smile

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

How to Install Latest MS Paint Alternative Pinta in Ubuntu and Other Linux

This guide explains the steps required to install the latest Pinta software in Ubuntu and other Linux distributions such as Linux Mint, Fedora, and others. Read more

More Progress for Mageia 8 – Beta 1 is available for testing

We are happy to announce the release of Mageia 8 Beta 1. After the good feedback from Alpha 1, there have been some improvements and fixes for this release, we look forward to hearing your feedback and thoughts so that we can continue to get Mageia 8 ready for release. A full list of included packages is available in the .idx file for the installation media. For those that want to jump in and test straight away, the images can be downloaded here, as always with pre-release images, use your best judgement. Read more Also: Mageia 8 Beta 1 Released With Many Improvements

today's leftovers

  • By embracing blockchain, a California bill takes the wrong step forward.

    The California legislature is currently considering a bill directing a public board to pilot the use of blockchain-type tools to communicate Covid-19 test results and other medical records. We believe the bill unduly dictates one particular technical approach, and does so without considering the privacy, security, and equity risks it poses. We urge the California Senate to reconsider. The bill in question is A.B. 2004, which would direct the Medical Board of California to create a pilot program using verifiable digital credentials as electronic patient records to communicate COVID-19 test results and other medical information. The bill seems like a well-intentioned attempt to use modern technology to address an important societal problem, the ongoing pandemic. However, by assuming the suitability of cryptography-based verifiable credential models for this purpose, rather than setting out technology-neutral principles and guidelines for the proposed pilot program, the bill would set a dangerous precedent by effectively legislating particular technology outcomes. Furthermore, the chosen direction risks exacerbating the potential for discrimination and exclusion, a lesson Mozilla has learned in our work on digital identity models being proposed around the world. While we appreciate the safeguards that have been introduced into the legislation in its current form, such as its limitations on law enforcement use, they are insufficient. A new approach, one that maximizes public good while minimizing harms of privacy and exclusion, is needed.

  • Karl Dubost: Browser developer tools timeline

    I was reading In a Land Before Dev Tools by Amber, and I thought, Oh here missing in the history the beautifully chiseled Opera Dragonfly and F12 for Internet Explorer. So let's see what are all the things I myself didn't know.

  • Daniel Stenberg: Using fixed port numbers for curl tests is now history!

    The curl test suite fires up a whole bunch of test servers for the various supported protocols, and then command lines using curl or libcurl-using dedicated test apps are run against those servers to make sure curl is acting exactly as it is supposed to.

  • Mycroft: an open-source voice assistant

    Mycroft is a free and open-source software project aimed at providing voice-assistant technology, licensed under the Apache 2.0 license. It is an interesting alternative to closed-source commercial offerings such as Amazon Alexa, Google Home, or Apple Siri. Use of voice assistants has become common among consumers, but the privacy concerns surrounding them are far-reaching. There have been multiple instances of law enforcement's interest in the data these devices produce for use against their owners. Mycroft claims to offer a privacy-respecting, open-source alternative, giving users a choice on how much of their personal data is shared and with whom. The Mycroft project is backed by the Mycroft AI company. The company was originally funded by a successful one-million-dollar crowdfunding campaign involving over 1,500 supporters. In recent years, it has developed two consumer-focused "smart speaker" devices: the Mark 1 and Mark 2. Both devices were funded through successful Kickstarter campaigns, with the most recent Mark 2 raising $394,572 against a $50,000 goal. In the press, the company has indicated its intention is to focus on the enterprise market for its commercial offerings, while keeping the project free to individual users and developers. On the subject of developers, contributors are expected to sign a contributor license agreement (CLA) to participate in the project. The actual CLA was unavailable at the time of publication, but the project claims it grants the project a license to the contributed code, while retaining ownership of the contribution to the developer.

  • GSoC 2020 Second Evaluation Report: Curses Library Automated Testing

    My GSoC project under NetBSD involves the development of test framework of curses library. This blog report is second in series of blog reports; you can have a look at the first report. This report would cover the progress made in second coding phase along with providing some insights into the libcurses.

  • Accelerating the value of multicloud environments: A collaborative DevSecOps approach is critical

    Cloud Native development is not so much about where you run your application, but more about how you develop it. It is an interesting moment in time for enterprise developers, as more emphasis shifts to application modernization and cloud native development. The responsibility is shifting to the application for critical success factors for hybrid cloud environments, including security, reliability, and manageability. I have found that these “interesting” challenges are best addressed by collaborative, cross-disciplinary DevSecOps teams that understand the entire software development lifecycle. In this new environment, your role as developers is more demanding, and we all need better tools. You have increased responsibility for understanding and working directly with security engineers on governance and related management policies. You are being tasked with prioritizing service reliability, and the best practice is to address potential problems early in the application lifecycle. You also need to proactively detect and resolve potential issues with production environments before they have a negative business impact.

  • Play Minecraft with Fedora Friends at Nest 2020 [Ed: Fedora is boosting Microsoft and "Fedora Minecraft/Spigot server follows the same Code of Conduct as Fedora Nest and the wider Fedora Community. Be kind, be respectful, and have fun!" (unlike Microsoft)]
  • Linux Foundation New Course To Help Developers Create Enterprise Blockchain Applications

    The Linux Foundation has announced a new training course, LFD272 – Hyperledger Fabric for Developers. The course, developed in conjunction with Hyperledger, is designed for developers who want to master Hyperledger Fabric chaincode – Fabric’s smart contracts – and application development.

  • The Linux Foundation release innovative training course

    The Linux Foundation is a  nonprofit organization enabling mass innovation through open source.

  • Google Details Its Open Source Contributions

    Most of Google’s open source work is done within two hosting platforms: GitHub and Google’s own Git service, git-on-borg, which hosts Android and Chromium. According to the report, Google hosts over 8,000 public repositories on GitHub and more than 1,000 public repositories on git-on-borg.

  • Open source by the numbers at Google

    At Google, open source is at the core of our infrastructure, processes, and culture. As such, participation in these communities is vital to our productivity. Within OSPO (Open Source Programs Office), our mission is to bring the value of open source to Google and the resources of Google to open source. To ensure our actions match our commitment, in this post we will explore a variety of metrics intended to increase context, transparency, and accountability across all of the communities we engage with.

  • libredwg-0.11 released
  • Best free tools for small businesses
  • 7-Zip 20.01 Alpha

    The unRAR code is under a mixed license: GNU LGPL + unRAR restrictions. Check license information here: 7-Zip license.

  • Kiwi TCMS Enterprise v8.5.2-mt

    We're happy to announce Kiwi TCMS Enterprise version 8.5.2-mt and extended support hours for subscribers in America.

  • Jonathan Dowland: Vimwiki

    At the start of the year I begun keeping a daily diary for work as a simple text file. I've used various other approaches for this over the years, including many paper diaries and more complex digital systems. One great advantage of the one-page text file was it made assembling my weekly status report email very quick, nearly just a series of copies and pastes. But of course there are drawbacks and room for improvement. vimwiki is a personal wiki plugin for the vim and neovim editors. I've tried to look at it before, years ago, but I found it too invasive, changing key bindings and display settings for any use of vim, and I use vim a lot. I decided to give it another look. The trigger was actually something completely unrelated: Steve Losh's blog post "Coming Home to vim". I've been using vim for around 17 years but I still learned some new things from that blog post. In particular, I've never bothered to Use The Leader for user-specific shortcuts.

  • Gmail Desktop

    There is a new application available for Sparkers: Gmail Desktop

  • Wine 5.0.2 Released With Fixes For Various Games, Windows Applications

    For those using Wine in a production environment for running Windows software on Linux, Wine 5.0.2 is out as the latest stable update. While Wine continues chugging along with a lot of great feature work with the Wine 5.x bi-weekly snapshots leading up to the Wine 6.0 release early next year, Wine 5.0.2 is the latest stable point release with a variety of bug-fixes back-ported to this code-base that was minted at the start of this year. There are no new features but exclusively bug fixes.

Open Hardware, Raspberry Pi and More

  • When Will Open Source Hardware Become a Thing?

    my honest opinion, Free and Open Source Software (FOSS) is probably the best of all innovation to come out of the tech industry in the past four or five decades. As far as I can tell, the Open Source Initiative is predated by Richard Stallman’s famous Free Software Foundation (FSF) (1985), which itself is predated by his own GNU project (1983) which seems as if it pretty much kick-started what we would call Free and Open Source today. Whilst it is true that software programs were often shared amongst academics before GNU, the software industry was a fraction of what it is today and so I believe that it was indeed GNU that kicked it all off. [...] Open Source firmware and drivers have been harder to come by in general than software. However, there have been major efforts made by Open Source and Free Software community members to create projects such as Libreboot which aims to replace proprietary boot firmware. Firmware is often a more contentious issue than software since most hardware we buy comes with firmware baked in. Reverse engineering a device’s firmware is not necessarily a particularly easy task, at least not when compared to just rebuilding an existing software project (eg. LibreOffice and Microsoft Office). To make matters worse, It can be much easier for companies to embed potentially malicious code since it is harder to analyse. I think that Open Source firmware will slowly become a bigger thing. However, its growth will probably be driven by the rise of Open Source hardware. [...] We’ve also seen the introduction of devices for the everyday user (not just hobbyists and tinkerers) including mobile phones and laptops. The company Purism has recently released both Laptops and a model of mobile phone which seem promising. Unfortunately, their laptops do rely on Intel CPUs, even if they claim to have disabled the management engine. It does seem like it will certainly take a while for these devices to meet mainstream though. Still, promising…

  • SAMD21 Lite is a Stamp-sized, MikroBus Compatible Cortex-M0+ MCU Board

    If you’re a fan of tiny microcontroller boards, you’ll be pleased with BOKRA SAMD21 Lite board powered by Microchip SAMD21 Arm Cortex-M0+ MCU, exposing I/Os in a way compatible with MikroBus socket, and adding a Grove connector for good measure.

  • TLS gets a boost from Arduino for IoT devices

    Arduino devices are a favorite among do-it-yourself (DIY) enthusiasts to create, among other things, Internet of Things (IoT) devices. We have previously covered the Espressif ESP8266 family of devices that can be programmed using the Arduino SDK, but the Arduino project itself also provides WiFi-enabled devices such as the Arduino MKR WiFi 1010 board. Recently, the Arduino Security Team raised the problem of security shortcomings of IoT devices in a post, and how the Arduino project is working to make improvements. We will take the opportunity to share some interesting things from that, and also look at the overall state of TLS support in the Arduino and Espressif SDK projects. When it comes to making a secure IoT device, an important consideration is the TLS implementation. At minimum, TLS can prevent eavesdropping on the communications, but, properly implemented, can also address a number of other security concerns as well (such as man-in-the-middle attacks). Moreover, certificate-based authentication for IoT endpoints is a considerably better approach than usernames and passwords. In certificate-based authentication, a client presents a certificate that can be cryptographically verified as to the client's identity, rather than relying on a username and password to do the same. These certificates are issued by trusted and cryptographically verifiable authorities so they are considerably more difficult to compromise than a simple username and password. Still, according to the team: "As of today, a lot of embedded devices still do not properly implement the full TLS stack". As an example, it pointed out that "a lot of off-brand boards use code that does not actually validate the server's certificate, making them an easy target for server impersonation and man-in-the-middle attacks." The reason for this is often simply a lack of resources available on the device — some devices only offer 32KB of RAM and many TLS implementations require more memory to function. Moreover, validating server certificates requires storing a potentially large number of trusted root certificates. Storing all of the data for Mozilla-trusted certificate authorities on a device takes up over 170KB in a system that potentially only has 1MB of available total flash memory. A general lack of education regarding the importance of security in this space unfortunately also plays a role. After all, TLS isn't the most straightforward subject to begin with, and having to implement it on a resource-limited platform does not make implementing it correctly any easier of a problem to solve.

  • Open-source CNCing

    Last year Sienci Labs finished its Kickstarter campaign for the open-source LongMill Benchtop CNC Router — its second successful open-source CNC machine Kickstarter campaign. CNC routers allow users to mill things (like parts) from raw materials (like a block of aluminum) based on a 3D-model. The LongMill is a significant improvement over the original sold-out Mill One and makes professional-quality machining based entirely on open-source technology a reality. As an owner of a LongMill, I will walk through the various open-source technologies that make this tool a cornerstone of my home workshop. Hardware The Sienci Labs LongMill is an impressive feat of engineering, using a combination of off-the-shelf hardware components alongside a plethora of 3D-printed parts. The machine, once assembled, is designed to be mounted to a board. This board, called a spoilboard, is a board the machine can "accidentally" cut into or otherwise suffer damage — designed to be occasionally replaced. In most circumstances, the spoilboard is the top of a table for the machine, and Sienci provides documentation on several different table builds done by the community. For builders short on space, the machine can be mounted on a wall. The complete 3D plans for the machine are available for download, including a full bill of materials of all of the parts needed. The project also provides instructions to assemble the machine and how best to 3D print relevant components. The machine is controlled by the LongBoard CNC Controller, and Sienci Labs provides full schematics [23MB ZIP] of that as well. All mentioned materials are licensed under a Creative Commons BY-SA 4.0 license. In addition to the open-source design of the machine itself, an open-source-minded community has formed around the project. The company's Facebook user group has 1,600 members, and an active community forum is hosted by the company, which discusses everything from tips to machine support. Community members contribute, among other things, various modifications to improve the original design or to add new features such as a laser engraver.

  • iWave Telematics Control Unit Supports GPS, 4G LTE, WiFi, and Bluetooth

    We’ve often written about iWave Systems’ single board computers, development kits, and systems-on-module, but the company has also been offering automotive products such as a Linux based OBD-II Dongle.

  • First Tiger Lake SBCs emerge

    Aaeon and Kontron are prepping 3.5-inch SBCs — and Advantech will offer a 2.5-incher — that debut Intel’s 11th Gen, 10nm Tiger Lake CPUs. The 15-28W TDP Tiger Lake offers better graphics than Ice Lake, including support for up to 4x 4K displays. Intel’s recent announcement of an additional six months delay in delivering 7nm CPUs, pushing back its original roadmap by a year to late 2022 or 2023 has led to further questions about the company’s future dominance. The 7nm defects are severe enough that Intel says it will expand its outsourcing of manufacturing to TSMC. Yet, Intel’s strong quarterly earnings and news that 10nm fabricated, 11th Gen Tiger Lake processors will meet their revised Q4 2020 deadline are helping to salve the wound.

  • RAK2287 Mini PCIe LoRaWAN Concentrator Module Supports up to 500 Nodes per km2

    The company provides a Raspbian based Raspberry Pi 3/4 firmware in the Wiki, but it’s obviously possible to use the card with other Linux hardware, and instructions to build an x86 Linux gateway are also provided. That’s for RAK2247, but it will work for RAK2287 as well.

  • How A Raspberry Pi 4 Performs Against Intel's Latest Celeron, Pentium CPUs

    Following the recent Intel Comet Lake Celeron and Pentium CPU benchmarking against other x86_64 Intel/AMD CPUs, here was a bit of fun... Seeing how these budget Intel CPUs compare to a Raspberry Pi 4 in various processor benchmarks, all tested on Debian Linux. The Celeron part tested was the G5900 as a $42 processor as a dual-core 3.4GHz processor with 2MB cache and UHD Graphics 610.

  • MEGA-RTD Raspberry Pi HAT Offers up to 64 Resistance Temperature Detectors (Crowdfunding)

    Sequent Microsystems like to make stackable Raspberry Pi HATs. After their stackable 4-relay board allowing for up to 32 relays controlled by a Raspberry Pi board, the company has now launched MEGA-RTD 8-channel RTD Raspberry Pi HAT enabling up to 64 resistance temperature detectors via 8x MEGA RTD board stacked on top of a Raspberry Pi board.

  • The State of Robotics – July 2020

    Looking for an easy way to get familiar with ROS 2? We recently published a few helpers on how to simulate robots with turtlesim to help our readers get a rolling start on ROS2. [...] CIS has a long and successful history of creating community-consensus best practice recommendations for security. The first CIS benchmark for ROS is currently under consideration and covers Melodic running on Ubuntu Server 18.04.