Linux Mint Cinnamon upgrade 17.1 to 17.3 – Cinnamon crash with nvidia-304

I’ve been using Mint Cinnamon 17.1 as my main desktop OS, of all the Linux distros I’ve played with in the past couple of years, this is my favorite by far (in terms of simplicity of the Desktop Environment).

17.3 Rosa came out recently, so I hadn’t upgraded for a while, so updated via the menu link in the software package manager.

I realized from installing and configuring 17.1 before that I needed to use the older nvidia-304 graphics – I have an older HP mobo with nvidia 6150SE graphics on the motherboard, and the best driver seems to be nvidia-304.

The upgrade itself was without issue, but after rebooting and logging on, within a few sessions I got the message “Cinnamon just crashed. You are currently running in Fallback Mode” and various parts of the screen started not refreshing. At one point when I pressed Yes on the dialog, but that resulted in more corruption to the point where individual characters became scrambled and not readable.

Seems like others are having the same issue too:

From feedback from others, it seems 17.2 was the last stable version for them, so I reinstalled 17.2 from a dvd, completely wiping my / partition. Luckily my docs and everything else I needed to keep was on a separate /home partition, so this worked out for me.

Usually any issues with a distro are on the initial install. This is the first time I can think of that doing an upgrade had significant issues, so hopefully they can get it sorted.

Running AROS / Icaros Desktop on VirtualBox

I love to install and check out different operating systems. Installing on something like VirtualBox means you can install as a guest, play with it, and either continue to use it or delete the disk image, with no impact to your host OS. So here’s an unusual one to check out:

AROS is an open source implementation of the AmigaOS 3.1 apis, that runs on Intel and PowerPC cpus (Amigas were originally Motorola 68k based). It seems there’s a couple of different variations, the one I installed was Icaros Desktop, which comes with a live CD, which you can also install from.

One installed, it boots from a GRUB menu, and wow, does it boot quick, within a couple of seconds (running under VirtualBox on my i7 MacBook Pro). It boots so fast I might be tempted to install this as a bare metal install on an old PC and play around with it for a while. It also looks very pretty 🙂

Industries that build their own tools

Here’s an interesting observation, and maybe something you haven’t thought of before. If you work in IT, particular in software development, the tools that you use as a developer were built by other developers.

Think about that for a minute. Can you imagine if chefs built their own ovens, or doctors made their own medicines?

Is there any other industry that builds it’s own tools?

Packet radio: Direwolf and pilinbpq

I’ve been playing around recently with setting up some packet radio software on the Raspberry Pi. The next thing I was interested in getting working was a BPQ32 node with BBS and Chat. G8BPQ’s instructions here are pretty easy to follow. What I got stuck on however was whether BPQ needed or used ax25, and apparently it doesn’t. So from the simplest direwolf and linbpq setup, you start direwolf, configure linbpq to point to Direwolf’s virtual kiss tnc serial port, and off you go.

I played around testing with 2 radios, one with Direwolf, linbpq and a Rigblaster connected to a Yaesu FT-60 HT, and the second, an Icom 880 connected with a Rigblaster Plug and Play to a desktop running Linux Mint, also using Direwolf. There was some random oddness wth connecting from one to the other, maybe because of the radios in close proximity, that turned out I just needed to increase default timeout settings. I set these both to the same in direwolf.conf and bpq32.cfg:

TXDELAY=300

TXTAIL=30

Once I’d added these (based on other suggested settings elsewhere in other people’s BPQ configs), then I was off and running. Looks good!