read write.as

from OrganizedChaos.Space

Surface Go – Fix Wireless for Linux!

The Surface Go harkens back to a day when the Eeepc was a pretty compact and kick ass piece of kit. Fast forward in time and we have the Surface Go. When Microsoft said they were going to embrace Linux, who knew they would make a smashing piece of gear for the platform. Here we get wireless sorted....

The Surface GO Wireless Hack

The Surface Go leverages the Wifi (Qualcomm Atheros QCA6174 rev 32): to make this little guy scream through the airwaves we need to complete a couple of steps to get it going... Simple as Fuck G! ;–)

Follow the steps below and rock on.....

First: we need to remove /usr/lib/firmware/ath10k/QCA6174/board-2.bin. Depending on your installation of Linux they maybe in subfolders such as hw2.1 and hw3.1 as they are in Manjaro Linux. Only the *board.bin files need to be removed.

rm /usr/lib/firmware/ath10k/QCA6174/hw2.1/board*.bin rm /usr/lib/firmware/ath10k/QCA6174/hw3.1/board*.bin

Ubuntu/Xubuntu location is /lib/firmware/ath10k/QCA6174

Second: replace /usr/lib/firmware/ath10k/QCA6174/board.bin with the working board.bin file that you will download from www.killernetworking.com.

In Manjaro this was not required, but to be honest I added it to the file anyway as a refernce item. It is required for Ubuntu flavors of Linux tjpugh. Add “options ath10kcore skipotp=y” in /etc/modprobe.d/ath10k.conf.

nano /etc/modprobe.d/ath10k.conf

Third: reboot and enjoy! If you have questions SearX them. :–) Or you can reach me on mastodon.sdf.org. 🤓


#Linux #Ubuntu #HowTo

— G.Love

 
Read more...

from Can't Wait to Meditate

#HowTo Improve Your Focus in Three Easy Steps

1) Stick a thumbtack on the wall, about three feet from the ground.

2) Take a chair and set it facing the tack, about three feet away.

3) Sit as straight as possible and stare at the tack for at least 15 minutes. Do it without thinking, without creating narratives or playing music in the background of your mind. Simply stare at the tack.

Your mind will thrash like a fish on land, and you may even nod off. When this happens, refocus on the tack on the wall.

If your eyes get sore from staring in one spot (and they will), do the opposite: stare at all the space around the tack, but not the tack itself. Alternate between staring at the tack and the negative space.


An experimental blog by Jason S. Comely. Thanks for reading.

 
Read more...

from OrganizedChaos.Space

WTF! Can't Boot After Autoremove

WTF!

So we talked about the golden rule, Patch Patch Patch. Even went as far to write a nifty article on the 3 simple commands to make you a patching fool! But then disater strikes! As mentioned in that article the two commands you should pay attention to apt-get autoremove & apt-get autoclean.

So in all faireness this has been fixed as of two days ago. But it's still worth walking through. So what is it we are talking about? It's the fact that direct dependencies of ubiquity should not be autoremovable!.

In a clean install of Xubuntu 18.10, if an unsuspecting user (ME!) runs 'apt autoremove', it will remove 'cryptsetup' and 'lvm2' making the system non-bootable at next restart if an encrypted(LUKS+LVM) root partition was selected during the ubiquity installer wizard:


$    sudo apt update && sudo apt --auto-remove full-upgrade && cat /run/reboo*
     The following packages will be REMOVED:
     cryptsetup cryptsetup-bin cryptsetup-initramfs cryptsetup-run dmeventd 
     libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2

This will make the system non-bootable upon restart if LUKS+LVM are active on the root partition. This would, by extension, make any auto-mounted partitions(home, etc.) unavailable after boot as well!

And it sure did and it sure sucks! So with a little help from my friend SearX. I was able to recover, the article linked about goes into a lot more detail, and outlines a fair number of steps. I only had to do a portion of those to get back in working order.

When boot failed I can reboot and see the boot options menu. At this point I select the Advanced Options and boot off the old kernel. Score! As I am able to unlock my drive and boot the system. Great but I want to use the new Kernel! And here is how we do it....

Run the following commands in this order...

Install lvm 2


$ sudo apt install lvm2

dpkg: error processing package lvm2 (--configure):
installed lvm2 package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.130ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic
Errors were encountered while processing:
lvm2
E: Sub-process /usr/bin/dpkg returned an error code (1)

Remove lvm2


$ sudo apt remove lvm2

Purge lvm 2


$ sudo apt purge lvm2

Install lvm2 again


$ sudo apt install lvm2
Reading package lists... Done
Building dependency tree 
Reading state information... Done
Suggested packages:
thin-provisioning-tools
The following NEW packages will be installed:
lvm2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 929 kB of archives.
After this operation, 3.391 kB of additional disk space will be used.
Get:1 http://id.archive.ubuntu.com/ubuntu bionic/main amd64 lvm2 amd64 2.02.176-4.1ubuntu3 [929 kB]
Fetched 929 kB in 5s (195 kB/s)
Selecting previously unselected package lvm2.
(Reading database ... 186578 files and directories currently installed.)
Preparing to unpack .../lvm2_2.02.176-4.1ubuntu3_amd64.deb ...
Unpacking lvm2 (2.02.176-4.1ubuntu3) ...
Processing triggers for ureadahead (0.100.0-20) ...
Setting up lvm2 (2.02.176-4.1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Created symlink /etc/systemd/system/sysinit.target.wants/blk-availability.service → /lib/systemd/system/blk-availability.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-monitor.service → /lib/systemd/system/lvm2-monitor.service.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket → /lib/systemd/system/lvm2-lvmetad.socket.
Created symlink /etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket → /lib/systemd/system/lvm2-lvmpolld.socket.
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for initramfs-tools (0.130ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic

Reboot and enjoy your system! You'll be back to normal. Again I can't stress enough to be cautious when using automated routines. And be prepared to do some work especially if you wing it. Which I still think is part of the fun. But not when you only have one system, so being cautious can save you a little grief. As mentioned earlier this has now be fixed as of 2/26/2019, but if you are like me you didn't have all the new bits when you firedaway. So I hope this helps you if you find yourself in a similar situation.

So with that reboot and enjoy! If you have questions SearX them. :–) Or you can reach me on mastodon.sdf.org. 🤓


#Linux #Xubuntu #HowTo

— G.Love

 
Read more...

from OrganizedChaos.Space

Update Via The Terminal

Patch patch patch

The golden rule, patch all your systems. Maintain good operational health, and ensure your security. Which I agree! It is the simple things that count. And while not the all-in-one solution to proper security practices. Patching is a necessary evil, but also effective. So beyond that security stuff..you have the cool things to look forward to like updates, new features, or corrective items to somethings that may not have worked properly.

So I was inspired to toss out this really simple document. Why? Because I keep getting asked by the Windows Admins, who are playing around with Ubuntu in their low cost VPS. How do I patch without a gui? So without dragging this on longer than necessary. I bring you the magic three lines.

Follow the steps below and rock on.....

First: we want to make sure all our repositories are up to date and fetch those updates, so run the following:

sudo apt-get update # Fetches the list of available updates

Second: We'll start with upgrading the current packages on the system:

sudo apt-get upgrade # Strictly upgrades the current packages

Third: We'll go out and install any distro updates also known as...“The New Shit”:

sudo apt-get dist-upgrade # Installs updates (new ones)

Now as you go through this process you may be asked to invoke commands such as

apt-get autoremove & apt-get autoclean

Exercise caution and in my next post you'll understand why. As people make mistakes and sometimes autoremove is not coded properly. Yes it contains a bug. For example after running autoclean on Xubuntu, you will soon realize you can no longer boot your system! If...your primary drive is full disk encrypted. Now that is FUN! I have a post following this one on how to get out of that jam. But regardless, dependencies were missed and items removed that shouldn't have been. So before running any automated task, read through the output and make sure you understand what it is going to do. If you don't you can always wing it, or like me I'll do it anyway to see how bad it's gonna get.

But be prepared to have fun when things break!.... Because tossing the laptop across the room will only get you a broken os and now a broken laptop!

So with that reboot and enjoy! If you have questions SearX them. :–) Or you can reach me on mastodon.sdf.org. 🤓


#Linux #Ubuntu #HowTo

— G.Love

 
Read more...

from OrganizedChaos.Space

Record Streaming Audio in Linux

Audio Recorder is the updated version of Gnome applet ‘Audio Rec’. It is an easy to use but extremely powerful app that caters to all of your audio recording needs in Ubuntu and Linux mint. Let’s see how to install Audio Recorder in Ubuntu & Linux mint.

Launch “Terminal”. You can use Ctrl+Alt+T shortcut.

    sudo apt-add-repository ppa:audio-recorder/ppa
    sudo apt-get update
    sudo apt-get install audio-recorder

For other Linux distributions, it is available as an unofficial Snap package in beta mode:

sudo snap install audio-recorder --beta

You can download the source code from launchpad. Once installed, you can start the application from Unity.

Audio Recorder can record form all sources or from music apps directly like Rythmbox and Clementine.

To record streaming audio, select the appropriate source. For example, if you are playing streaming radio in Clementine then select Clementine.

Audio Recorder also presents you the option of setting a timer. With the timer you have the ability to start, stop or pause recordings at a specific time or at a defined time interval. You can also set a limit on the recorded file size. The most captivating feature which I enjoy the most, is that you can choose to pause and split tracks when their is no audio (or very low sound) and resume it when sound comes back audible levels without having to edit them later on. To use the timer you just need to modify the text examples in the Timer panel. Comment # out the “rules” that you don’t want to apply and edit the ones pertinent to you.

Another gem. You can save the recorded file in your favorite file format. Supported type of file format are OGG audio, Flac, MP3, SPX and WAV. You can choose whichever format you prefer. Depending on the stream quality MP3 is flexible. The saved files are stored in ~/Audio.

So, if you looking for a way to record sound in Ubuntu or Linux in general, Audio Recorder is a must-have for your recording arsenal.

Mission Completed! You can now record streaming audio, and capture those online moments.


#Linux #Ubuntu #HowTo

— G.Love

 
Read more...

from OrganizedChaos.Space

How to install New Yaru Theme of Ubuntu 18.10, in Ubuntu 18.04.

Launch “Terminal”. You can use Ctrl+Alt+T shortcut.

STEP 1: Enter the following command in the Terminal and press enter. Note that the theme is still called communitheme in the repo. It’s the old name and will be renamed as Yaru in the future.

sudo snap install communitheme

STEP 2: Enter the root password when prompted.

STEP 3: After installation is completed, wait for the message “communitheme xxx from ‘didrocks’ installed”.

STEP 4: Restart the computer. At the login screen click on the settings icon and select “Ubuntu with communitheme snap” or if you are using Wayland select select “Ubuntu with communitheme snap on Wayland”

Mission Completed! you now will see the brand new theme on your desktop!


#Linux #Ubuntu #HowTo

— G.Love

 
Read more...

Join the writers and thinkers on Write.as

Start writing or create a public blog