blinktenlights

I picked up a pimoroni blinkt in a swag bag recently, and I think I should make a colour clock out of it. There’s a simple one-liner for installation of all required libraries, but it pipes to bash.

That is against my religion. I like to know for myself how I’m messing things up. I like to make sure the checksums are right. Disappointingly, I did it through aptitude, and it didn’t go wrong /at all/.

init.d/wtf

When using a shell script in /etc/init.d to start up a command, make sure you put the shell script there, and not the compiled program.

It didn’t work anyhow, so I’m calling it as a cron job on reboot, but I’m pretty sure the point still stands.

ETA: Aaah. So, there are things called runlevels, and Rasbian is based on Debian, which has them. I’m more a systemd person, so I was looking at the wrong sort of help file.

Lasers

A while back I decided for safety reasons not to put laser cutting capability onto my Art Bot. So, the laser and heatsink bundle arrived today. I’m going to be messing with the voltage and current using a dummy load (also bought that, rather than scraping it together) and nothing could possibly go wrong.

I’ve already written the software.

Motion Sensing

I’m trying to use a Raspberry Pi 3 and camera for motion sensing and recording. Here’s how I’ve got on so far:

  • Arch: Didn’t fucking work. motion started and kept dying. Power throttling killed the SD card.
  • Jessie Lite after buying a new SD card: wpa_supplicant didn’t fucking work.
  • Jessie Lite after three hours dealing with wpa_supplicant: motion didn’t fucking work.
  • MotionEyeOS: Required wired network to start for the first time. Walked back and forth between screens a lot. Can only alter root password through web interface. Weirdest fucking distro I have ever seen.
  • MotionEyeOS with a set-up script: May actually have fucking worked.

ETA: It fucking worked!

Kernel Fun

The current linux kernel is messing with the intel graphics chip on my laptop, which consequently thinks it’s helping to run a Cathode Ray Tube, and this is less than perfect.

My options are running a 3 month old kernel, which is perfectly sensible, or using linux-lts, which is also perfectly sensible. So, I’ve gone for the third option. I’m going to have the newest release kernel and also linux-lts as a fallback. This is unusual for me in that it’s a third option that is also perfectly sensible.

However, it does rely on me not building the lts kernel with the wrong name, so as to over-write the kernel I already have. So, I’m going to be here for a while.

It would have gone a lot better if the power lead hadn’t fallen out half an hour before I typed ‘make’.

C++: Cake or Death?

Oddly happy. I’ve got a program where if I run it in the debugger, it completes, and if I run it in the command line it segfaults. This pleases me obscurely.

Yes, I’ve checked it’s the same source file and the same build. No, I’m probably not going to dig into it, I’m just going to fix it and move onto the next problem. However, I’m pleased that I can build something that breaks, because it’s a good step on the road to building something that doesn’t break.

ETA: Wasn’t finding file to make it when edited either. Now is. Still no segfault though.