2016-12-06 https://macvendors.com

Look up your MAC address vendor :D Quite handy when going thru my logs with about a dozen unknown MAC's on my LAN.

Enjoy.

2016-09-27 OnePlusOne Woes - Tales of reflashing without explicit GNU/Linux support

THE ISSUE

About a year ago I ran into some corruption issues with my OnePlus One and that issue rendered ADB to have a fit, as did OTA updates, USB mode, and fastboot. Tech support wanted me to use Windows to fix it via a remote desktop session. Needless to say I was not about to let them goad me into going Windows. Well this corruption was abosulutely annoying and I was short on time and willpower to devote much of either into a literal spare device.

Alas I did. Sorta. I figured since I just got this ironed out I would share the ever so pleasant experience in getting this nightmare sorted out. I installed 8.1 onto an old disk and got it up and running long enough to get the thing fixed. If you find yourself in the same boat,below is what you want to do.

FIXING THE BOOTLOADER

  1. Download and install the Samsung Drivers for Windows.
  2. Reboot afterwards. And yes do reboot, its necessary.
  3. Download and install the ADB Installer. Do not need to install the drivers, just ADB and fastboot.
  4. Reboot just in case it is necessary. I did. Besides we all know Windows needs to be rebooted every 5min or so :D
  5. Plug in your phone. Windows should ask about drivers, if not no biggie. If you do get the dialogue, you can cancel it.
  6. Go into Device Manager and find the ADB heading -> The ADB device -> Right Click to the Update Driver Software -> Choose Browse my computer -> Choose Let Me Pick -> Show All Devices -> Have Disk -> Point to where the Samsung drivers were installed.
  7. That should get things working again. Once you can copy stuff to the phone, you can reinstall your recovery and OS via fastboot and the recovery respectively.

FLASHING OXYGENOS

Download links are in the forums. You need to grab the build and then the Windows package and instructions. The instructions will add a few details to what I have laid out, but same process.

https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/

In my case I went from a broken CyanogenMod 12.1 to OxygenOS 2.1.4. The process was then, once adb/fastboot was fixed, was:

  1. Run from an Administrator mode command prompt "fastboot oem unlock"
  2. Run the patch companion download's batch file to flash the recovery, AllInOne.bat and choose option 2.
  3. Reboot phone and then copy over the Bacon OxygenOS 2.1.4 zip to the phone if its not already there
  4. Reboot phone to recovery and do a cache and data wipe install the bacon zip.
  5. After you reboot into Oxygen and go thru the new device setup song and dance, enable developer mode (Settings -> 6. About Phone -> Tap Build Number a bunch of times until dev mode unlocks)
  6. Turn on ADB support (Settings -> Developer Options -> Usb Debugging

FIXING ADB ON THE LINUX SYSTEM

Now replug the phone into your Linux rig and you should see two partitions pop up, including the drivers partition. Run the ADB fix for linux shell script:

Pre script, as you can see the only device is my other phone:

[root@big-red-wireless ~]# adb devices -l  
List of devices attached  
5VT7N15A25000587 device usb:1-2 product:angler model:Nexus_6P device:angler

Post script, and it sees but can't do anything with the phone yet:

[root@big-red-wireless ~]# '/run/media/andrew/OnePlus Drivers/adb_config_Linux_OSX.sh'   
android home is exist!  
config adb ...  
OK! You can use adb now!  
[root@big-red-wireless ~]# adb devices -l  
* daemon not running. starting it now on port 5037 *  
* daemon started successfully *  
List of devices attached  
d6dea608 offline usb:1-1  
5VT7N15A25000587 device usb:1-2 product:angler model:Nexus_6P device:angler  

Accepted the connection on phone:

[root@big-red-wireless ~]# adb devices -l  
List of devices attached  
d6dea608 device usb:1-1 product:bacon model:A0001 device:A0001  
5VT7N15A25000587 device usb:1-2 product:angler model:Nexus_6P device:angler  
[root@big-red-wireless ~]#

Done. Working great now. Would have been nice to know what I needed to do to get this functional on Linux from jump street, as it would have saved me a good 4hrs of my time screwing around with this. I do firmly believe that there was an issue somwhere with an update to the recovery image. The image I have now is much nicer than the one from the factory. And there was a setting that was ticked in CM that allowed for recovery updates. Just that nothing worked. My first stab was to download and install the latest CM13 for bacon and use the recovery to install it. Nope, didn't work. Thats how I eventually stumbled across ADB and Fastboot being borked here. For safe keeping I did back up my recovery files partition so if things go wonky again I am not forced to deal with this level of fun again. And by fun, I mean 6 hours of pure pain of having to touch Windows and screw around with their miserable driver model. And 8.1 sucks golf balls thru a garden hose.

2015-08-14 RHEL7 with OpenVPN in NetworkManager

OK, put simply there are issues immediately due to SELinux in getting NetworkManager to connect up to your VPN properly. If you setup your connection and certificates as follows you will have no issues whatsoever connecting as any user.

1.Copy all your certificate files into ~/.cert

2.Check your SELinux context and validate it is appropriate:

unconfined_u:object_r:home_cert_t:s0

You need to have something like this:

[andrew@big-red-wireless .cert]$ pwd  
/home/andrew/.cert  
[andrew@big-red-wireless .cert]$ ls -Z  
-rw-r--r--. andrew andrew unconfined_u:object_r:home_cert_t:s0 andrew.crt  
-rw-------. andrew andrew unconfined_u:object_r:home_cert_t:s0 andrew.key  
-rw-r--r--. andrew andrew unconfined_u:object_r:home_cert_t:s0 ca.crt  
[andrew@big-red-wireless .cert]$  

3.If you need to reset the contexts, issue the following command as root:

restorecon -R -v /home/$USERNAME/.cert

4.Create a NetworkManager VPN entry with your cert files from the ~/.cert folder.

5.Connect!

Took me a few minutes to understand why the connection was barfing out. Once I noticed some SELinux alerts it dawned on me -- I never set the contexts. A quick Google showed me also, that there is a convenient location to dump all certificates into. Double win!

2015-8-08 I learnt something new - cu

Inside the uucp package is a nifty tool that I just picked up on called cu. This is for serial connection management and it works beautifully, and simply. I had a few old machines that I needed to tap into via serial and a friend admin I was with recently mentioned her love of this command. So having a selectively great memory, I gave it a stab.

1.First get uucp installed. I see that it comes from EPEL on RHEL7.

[andrew@big-red-wireless Desktop]$ sudo yum info uucp  
Loaded plugins: langpacks, nvidia, product-id, subscription-manager  
Installed Packages  
Name : uucp  
Arch : x86_64  
Version : 1.07  
Release : 41.el7  
Size : 2.7 M  
Repo : installed  
From repo : epel  
Summary : A set of utilities for operations between systems  
URL : http://www.airs.com/ian/uucp.html  
License : GPLv2+  
Description : The uucp command copies files between systems. Uucp is primarily  
: used by remote machines downloading and uploading email and news  
: files to local machines.  

[andrew@big-red-wireless Desktop]$
  1. Secondly determine your connection parameters. I have a USB to serial hodgepodge of cabling and adapters that I tote around and stash in places useful. So in my case its /dev/ttyUSB0 for the device, and of course each connection has its flow control and bitrate and parity, etc... Know that all. In my case the devices preferred to speak 19200b, 8N1, FC Off (manuals say so). But being hasty I just slapped into the terminal:
[andrew@big-red-wireless ~]# sudo cu -l /dev/ttyUSB0 -s 19200  

And things just worked. For a full reference guide for various settings and such:

http://linux.die.net/man/1/cu
http://www.jann.cc/2013/02/10/the_cu_command.html

2015-08-04 RHEL7 + Intel 7260AC Wireless Card

There are known issues with older kernels that cause major issues with the 7260 with regards to power management and the 5GHz spectra. After dealing with a dying i7 IMC issue, I finally could spend time troubleshooting my issues.

Firstly, ensure your router/AP isn't crap. I had that issue regardless of devices and their respective OS's. Once you are sure that there isn't anything dead/dying or just plain flaky, there are a few things that can be done, one of which you have a potential choice as to how to deal with it. Supposedly kernels beyond 3.16/3.17 have this rectified. As we are pegged on EL7 to 3.10, until Red Hat backports the changes we have to deal with it ourselves.

Next, there are several lines we need to put into your /etc/modprobe.d/iwlwifi.conf

Here is how I went, and I will detail what each line means:

  • Not necessarily needed as of RHEL 7.3, newer iwl drivers have cleaned up alot of cuft and bugs). I have found that stock settings are perfectly fine now. Leaving this details present in case someone is locked to 7.0/7.1/7.2 and cannot update to a newer iwl release.
$ cat /etc/modprobe.d/iwlwifi.conf  
options iwlmvm power_scheme=1  
options iwlwifi bt_coex_active=N swcrypto=1 11n_disable=8
  • The power_scheme option is to set the power to full bore at all times. The default is to 2 on most installations which is the adaptive mode. This can cause issues with the device going to sleep at rather inopportune moments. Although not necessarily your issue, something to keep note of.

  • The bt_coex_active option is for coexistence of BlueTooth and wireless. They operate on the same frequency range and can cause issues.

  • The swcrypto option is for forcing the cryptography off of the card and onto your system CPU. High workloads

  • The 11n_disable option is where I was referring to a choice. Setting the disable to 1 will force the card into G only speeds. This does indeed work on AC networks just fine, but will limit your connection to 54Mb/s speeds max. Setting this to 8 will not cause that restriction but rather a link aggregation. Here is the information from the module on this parameter:

$modinfo iwlwifi | grep 11n_disable  
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)

Once you have made a choice as to what of these option you are going to implement, you can do the following commands (as root) to unload/load the kernel, of course taking the new parameters on reload.

$ sudo rmmod iwlmvm  
$ sudo rmmod iwlwifi  
$ sudo modprobe iwlwifi

Hopefully this information is as useful to you as it was me. This fully rectified my constant disconnections while on AC networks with this card.

2015-07-01 https://www.cpubenchmark.net

Found a companion site to the video card benchmark site:
https://www.cpubenchmark.net/

2015-04-05 https://www.videocardbenchmark.net

Found a bit back a nifty site for figuring out relative performances of all the video cards out on the market. Posting in lieu of poor memory and assumption I am not the only one interested in this information :D

http://wwws.videocardbenchmark.net/

2015-03-30 RHEL7 + NVIDIA Driver Installation

EL & NVIDIA workes quite well with the elrepo kmod-nvidia rpms that are in the stable repo.

  1. Install ELRepo
[http://elrepo.org/tiki/tiki-index.php](http://elrepo.org/tiki/tiki-index.php)
  1. Follow the instructions here for normal installs on 7.0 (RHEL or clone)
[http://elrepo.org/tiki/kmod-nvidia](http://elrepo.org/tiki/kmod-nvidia)
  1. To install the rpms use the following command:
yum install kmod-nvidia nvidia-x11-drv-32bit nvidia-x11-drv  
  1. To finish up, we need to ensure that nouveau is blacklisted and glamoregl is disabled.
  2. The F/LOSS module, nouveau, should automatically get blacklisted, but lets ensure that the RPM did the job:
[andrew@big-red-wireless ~]$ sudo grep --color -e nouveau /etc/default/grubGRUB_CMDLINE_LINUX="rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau"  
[andrew@big-red-wireless ~]$
  1. Providing it is we can move to dealing with glamoregl. There are several ways to deal with this one, personally I chose to remove it via yum cleanly. The mailing list description is here:
[http://lists.elrepo.org/pipermail/elrepo/2013-November/002058.htm](http://lists.elrepo.org/pipermail/elrepo/2013-November/002058.htm)
  1. To do what I did:
yum remove xorg-x11-glamor
  1. Reboot.

2015-03-21 RHEL + Steam

[Remade this page to include the fact that epel now has the steam rpms]

There are two methods for getting Steam installed in RHEL7 these days:

There is a difference in the two packages, as negativo has a specific goal in how he will package anything up. I found that on Fedora his packages are better. Here its a tossup. I suppose if you have a thing for making scripts that recreate all your repos, and this one is in the mix, fine. But please do check out his other repos as they are quality choices, and well made RPMs.

Now, for what I did:

  1. Install the EPEL repo:
[http://mirror.us.leaseweb.net/epel/7/x86_64/repoview/epel-release.html](http://mirror.us.leaseweb.net/epel/7/x86_64/repoview/epel-release.html)
  1. Install steam
yum install steam

Package info:

date && sudo yum info steam  
Mon Mar 21 20:07:52 CDT 2016  
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-  
: manager  
Installed Packages  
Name : steam  
Arch : i686  
Version : 1.0.0.51  
Release : 6.el7  
Size : 2.6 M  
Repo : installed  
From repo : epel-steam  
Summary : Installer for the Steam software distribution service  
URL : http://www.steampowered.com/  
License : Steam License Agreement  
Description : Installer for the Steam software distribution service.  
: Steam is a software distribution service with an online store,  
: automated installation, automatic updates, achievements,  
: SteamCloud synchronized savegame and screenshot functionality,  
: and many social features.  

2015-03-21 RHEL + Mumble

I just dropped RHEL 7.1 onto my main workstation and had to relive and relearn how to install mumble onto it. Here is what you need to do.

  1. Install nux-desktop repo.
http://li.nux.ro/repos.html
  1. Enable desktop-optional-rpms for your RHEL flavor.
  2. Install mumble:
yum install mumble

All done, there should be a GNOME 3 entry already. Happy voice-chatting!

=============================================  
Package              Arch   Version         Repository                    Size  
=============================================  
Installing:  
mumble               x86_64 1.2.6-5.el7.nux nux-dextop                   3.0 M  
Installing for dependencies:  
avahi-compat-libdns_sd  
x86_64 0.6.31-14.el7   rhel-7-desktop-optional-rpms  33 k  
celt071              x86_64 0.7.1-8.el7.nux nux-dextop                    61 k  
protobuf             x86_64 2.5.0-7.el7     epel                         338 k  

Transaction Summary  
=============================================

2015-03-21 RHEL + LibreOffice

LibreOffice is my go-to office tool, and it is not in the standard yum repos. But, all hope is not lost, Red Hat does indeed distribute this. Goto your subscription manager and edit the repos you are subscribed to add in the "optional-rpms" category for your flavor of RHEL:

[andrew@big-red-wireless ~]$ sudo yum info libreoffice  
[sudo] password for andrew:  
Loaded plugins: langpacks, product-id, subscription-manager  
Installed Packages  
Name : libreoffice  
Arch : x86_64  
Epoch : 1  
Version : 4.2.6.3  
Release : 5.el7  
Size : 0.0  
Repo : installed  
From repo : rhel-7-server-optional-rpms  
Summary : Free Software Productivity Suite  
URL : http://www.libreoffice.org/  
License : (MPLv1.1 or LGPLv3+) and LGPLv3 and LGPLv2+ and BSD and (MPLv1.1  
: or GPLv2 or LGPLv2 or Netscape) and Public Domain and ASL 2.0 and  
: Artistic and MPLv2.0  
Description : LibreOffice is an Open Source, community-developed, office  
: productivity suite. It includes the key desktop applications, such  
: as a word processor, spreadsheet, presentation manager, formula  
: editor and drawing program, with a user interface and feature set  
: similar to other office suites. Sophisticated and flexible,  
: LibreOffice also works transparently with a variety of file  
: formats, including Microsoft Office File Formats.  
[andrew@big-red-wireless ~]$