1 Comment For years I have been taking less-than-adequate photos. I take photos on my hiking excursions and various equipment setups.
Next year I will be traveling internationally and to the Eastern States of Australia, and I plan to write a travelogue, with lots of photos.
I have owned a couple of digital cameras, very cheap ones. The main complaint that I had with them was poor indoor shots, in particular hunting during auto-focus -- those cameras did not offer the alternative of manual focus.
I gave away my last camera, and for the last couple of years have been using my phone. Which is very mediocre for indoor shots.
So, what is out there, that ticks all the boxes? I want highly portable (pocketable), very large CMOS sensor, optional manual focus, USB-recharging. Still shots, not so concerned about video performance.
The problem is, I have found "just the right" camera, but it is not cheap. It is the Canon PowerShot G9 X, and costs between AU$500 -- AU$700.
What I really like is the touchscreen. Having become familiar with using the camera on my phone, I love being able to just touch somewhere on the screen to set focus at that point -- which the Canon G9X also supports.
For such a tiny camera, it has a very large CMOS sensor, 1 inch, which is 15.85x13.2mm. Information on sensor sizes:
Don't know if I will actually buy it though, currently just "window shopping".
No comments Running Quirky on the Odroid XU4, when I launched SNS (Simple Network Setup), it identified the network interface as 'enx*' (where the * is a long string), instead of the old familiar 'eth0'.
Explanation of why is given here:
How to get 'eth0' back is explained here:
The kernel knows the interfaces as eth0, eth1, etc., and the culprit that changes the names is the udev rule:
The udev package (actually, 'eudev' in the case of Quirky, 'systemd' for most other distros) provides the rules in /lib/udev/rules.d.
Any of these can be overridden in /etc/udev/rules.d.
However, in Quirky I don't just use the rules from the udev package, instead I have a cutdown set in /etc/udev and /lib/udev.
So, I have just removed 80-net-name-slot.rules.
I have just finished compiling the 3.10.103 kernel for the XU4, running it right now. And, oddly, the old naming has come back anyway, I didn't have to remove that rule.
But, I have removed it, so it won't be in woofQ builds.
1 Comment I posted about compiling the 4.8.0rc Linux kernel for the Odroid XU4:
They worked, but audio, wireless and usb3 are broken. And who knows what else?
The 3.10.x source however, is very mature. It has been heavily patched to work with the Odroid boards.
My main reason for wanting to move up to a later kernel, is I wanted Overlay FS. However, if I am going to compile the kernel myself, why not patch with Aufs, as have always done.
So I downloaded the Aufs patch, which I found here:
And downloaded the Odroid kernel source:
...see how active it is, the last commit 7 days ago.
Hey, I discovered that the Odroid source already has Aufs!
I have shoehorned the Odroid source into my standard build scripts, and the kernel is compiling now.
No comments On-going testing of Quirky on the Odroid XU4.
I reported that I could not get any of my USB-wifi adaptors to work. There is another one on its way from Amazon, however, I want to get online now.
So I bought one of these, a TP-Link 300M Range Extender:
Lovely product, easy-peasy to connect to my wifi hotspot. It comes with an ethernet cable, which I plugged into the Odroid, ran SNS to choose the ethernet interface, then ran the web browser, a few clicks and enter the wifi password, and I was online.
The great thing about this is most of these little arm boards have an ethernet socket, which is ready to go. The XU4 only has three USB sockets, so it is great having them all available for other purposes.
I bought the TP-Link 300M Range Extender, model TL-WA850RE, from my local Kmart store, for AU$49. It can be purchased online a bit cheaper.
Here is a photo of my XU4:
The ethernet cable can be seen, but the TP-Link Range Extender is out of sight behind the monitor.
What you can see in the photo is my Toshiba 1TB hard drive. Yep, it works, but not with the 4.8-rc kernel that I compiled. With that kernel, I can plug in a flash stick and it is recognised, but plug in my 1TB drive and the kernel won't recognise its existence.
On the otherhand, running Quirky with the official-stable kernel, 3.10.96, the 1TB drive works fine.
Which has got me thinking. I wanted a later kernel as I want Overlay FS, however, I might patch the Odroid 3.10.96 kernel with aufs. That will solve my immediate need, to use the XU4 as a host for running woofQ.
3Comments This is a very useful bit of information. A couple of weeks ago, I downloaded a project from a git repository, and it was 5.5GB, which used up the rest of my monthly data allowance (which is only 12GB, from Virgin Mobile, 4G wireless, using the Optus network).
Now, I want to compile the Linux kernel on my Odroid XU4, and followed the instructionss here:
# git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git linux_odroid
...it started to download, but I did a CTRL-C when I realised it is 5GB.
So, I did a bit of reading, found this:
# git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git linux_odroid --depth 1
Which is only 59MB.
Pages:      ...