This post is largely to remind myself of the details next time I hit something similar; I found bits of relevant information all over the place, but not in one single location.
I love Kodi. These days the Debian packages give me a nice out of the box experience that is easy to use. The problem comes in dealing with remote controls and making best use of the available buttons. In particular I want to upgrade the VDR setup my parents have to a more modern machine that’s capable of running Kodi. In this instance an AMD E350 nettop, which isn’t recent but does have sufficient hardware acceleration of video decoding to do the job. Plus it has a built in fintek CIR setup.
First step was finding a decent remote. The fintek is a proper IR receiver supported by the in-kernel decoding options, so I had a lot of flexibility. As it happened I ended up with a surplus to requirements Virgin V Box HD remote (URC174000-04R01). This has the advantage of looking exactly like a STB remote, because it is one.
Pointed it at the box, saw that the
fintek_cir module was already installed and fired up
irrecord. Failed to get it to actually record properly. Googled lots. Found
ir-keytable. Fired up
ir-keytable -t and managed to get sensible output with the RC-5 decoder. Used
irrecord -l to get a list of valid button names and proceed to construct a vboxhd file which I dropped in
/etc/rc_keymaps/. I then added a
fintek-cir * vboxhd
/etc/rc_maps.cfg to force my new keymap to be loaded on boot.
That got my remote working, but then came the issue of dealing with the fact that some keys worked fine in Kodi and others didn’t. This seems to be an issue with scancodes above 0xff. I could have remapped the remote not to use any of these, but instead I went down the
inputlirc approach (which is already in use on the existing VDR box).
For this I needed a stable device file to point it at; the
/dev/input/eventN file wasn’t stable and as a platform device it didn’t end up with a useful entry in
/dev/input/by-id. A ‘quick’
udevadm info -a -p $(udevadm info -q path -n /dev/input/eventN)
provided me with the PNP id (FIT0002) allowing me to create
/etc/defaults/inputlirc ended up containing:
EVENTS="/dev/input/remote" OPTIONS="-g -m 0"
The options tell it to grab the device for its own exclusive use, and to take all scancodes rather than letting the keyboard ones through to the normal keyboard layer. I didn’t want anything other than things specifically configured to use the remote to get the key presses.
At this point Kodi refused to actually do anything with the key presses. Looking at
~kodi/.kodi/temp/kodi.log I could see them getting seen, but not understood. Further searching led me to construct an Lircmap.xml - in particular the piece I needed was the
<remote device="/dev/input/remote"> bit. The existing
/usr/share/kodi/system/Lircmap.xml provided a good starting point for what I wanted and I dropped my generated file in
(Sadly it turns out I got lucky with the remote; it seems to be using the RC-5x variant which was broken in 3.17; works fine with the 3.16 kernel in Debian 8 (jessie) but nothing later. I’ve narrowed down the offending commit and raised #117221.)
Helpful pages included:
Whoop! Looking forward to it already (though will probably spend it feeling I should be finishing my dissertation).
2016-07-01 15:20 DUB -> 16:45 LHR BA0837 2016-07-01 21:35 LHR -> 10:00 CPT BA0059
2016-07-10 19:20 CPT -> 06:15 LHR BA0058 2016-07-11 09:20 LHR -> 10:45 DUB BA0828
(image stolen from Gunnar)
That’s a longer title than I’d like, but I want to try and catch the attention of anyone who might have missed more directed notifications about this. If you’re not an SPI contributing member there’s probably nothing to see here…
Although I decided not to stand for re-election at the Software in the Public Interest (SPI) board elections last July, I haven’t stopped my involvement with the organisation. In particular I’ve spent some time working on an overhaul of the members website and rolling it out. One of the things this has enabled is implementation of 2009-11-04.jmd.1: Contributing membership expiry, by tracking activity in elections and providing an easy way for a member to indicate they consider themselves active even if they haven’t voted.
The plan is that this will run at some point after the completion of every board election. A first pass of cleanups was completed nearly a month ago, contacting all contributing members who’d never been seen to vote and asking them to update their status if they were still active. A second round, of people who didn’t vote in the last board election (in 2014), is currently under way. Affected members will have been emailed directly and there was a mail to spi-announce, but I’m aware people often overlook these things or filter mail off somewhere that doesn’t get read often.
If you are an SPI Contributing member who considers themselves an active member I strongly recommend you login to the SPI Members Website and check the “Last active” date displayed is after 2014-07-14 (i.e. post the start of the last board election). If it’s not, click on the “Update” link beside the date. The updated date will be shown once you’ve done so.
Why does pruning inactive members matter? The 2015 X.Org election results provide at least one indication of why ensuring you have an engaged membership is important - they failed to make a by-laws change that a vast majority of votes were in favour of, due to failing to make quorum. (If you’re an X.org member, go vote!)
[I wrote this as part of BelFOSS but I think it’s worth posting here.]
My Free Software journey starts with The Cuckoo’s Egg. Back in the early 90s a family friend suggested I might enjoy reading it. He was right; I was fascinated by the world of interconnected machines it introduced me to. That helped start my involvement in FidoNet, but it also got me interested in Unix. So when I saw a Linux book at the Queen’s University bookshop (sadly no longer with us) with a Slackware CD in the back I had to have it.
The motivation at this point was to have a low cost version of Unix I could run on the PC hardware I already owned. I had no knowledge of the GNU Project before this point, and as I wasn’t a C programmer I had no interest in looking at the source code. I spent some time futzing around with it and that partition (I was dual booting with DOS 6.22) fell into disuse. It wasn’t until I’d learnt some C and turned up to university, which provided me with an internet connection and others who were either already using Linux or interested in doing so, that I started running a Linux box full time.
Once I was doing that I became a lot more interested in the Open Source side of the equation. Rather than running a closed operating system that even the API for wasn’t properly specified (or I wouldn’t have needed my copy of Undocumented DOS) I had the complete source to both the underlying OS and all the utilities that it was using. For someone doing a computer science degree this was invaluable. Minix may have been the OS discussed in the OS Design module I studied, but Linux was a much more feature complete option that I was running on my desktop and could also peer under the hood of.
In my professional career I’ve always welcomed the opportunities to work with Open Source. A long time ago I experienced a particularly annoying issue when writing a device driver under QNX. The documentation didn’t seem to match the observed behaviour of the subsystem I was interfacing with. However due to licensing issues only a small number of people in the organisation were able to actually look at the QNX source. So I ended up wasting a much more senior engineer’s time with queries like “I think it’s actually doing x, y and z instead of a, b and c; can you confirm?”. Instances where I can look directly at the source code myself make me much more productive.
Commercial development also started to make me more understanding of the Free Software nature of the code I was running. It wasn’t just the ability to look at the code which was useful, but also the fact there was no need to reinvent the wheel. Need a base OS to build an appliance on? Debian ensures that the main component is Free for all usage. No need to worry about rolling your own compilers, base libraries etc. From a commercial perspective that allows you to concentrate on the actual product. And when you hit problems, the source is available and you can potentially fix it yourself or at least more easily find out if there’s been a fix for that issue released (being able to see code development in version control systems rather than getting a new upstream release with a whole heap on unrelated fixes in it really helps with that).
I had thus progressed from using FLOSS because it was free-as-in-beer, to appreciating the benefits of Open Source in my own learning and employment experiences, to a deeper understanding of the free-as-in-speech benefits that could be gained. However at this point I was still thinking very much from a developer mindset. Even my thoughts about how users can benefit from Free Software were in the context of businesses being able to easily switch suppliers or continue to maintain legacy software because they had the source to their systems available.
One of the major factors that has helped me to see beyond this is the expansion of the Internet of Things (IoT). With desktop or server software there is by and large a choice about what to use. This is not the case with appliances. While manufacturers will often produce a few revisions of software for their devices, usually eventually there is a newer and shiny model and the old one is abandoned. This is problematic for many reasons. For example, historically TVs have been long lived devices (I had one I bought second hand that happily lasted me 7+ years). However the “smart” capabilities of the TV I purchased in 2012 are already of limited usefulness, and LG have moved on to their current models. I have no intention of replacing the device any time soon, so have had to accept it is largely acting as a dumb display. More serious is the lack of security updates. For a TV that doesn’t require a network connection to function this is not as important, but the IoT is a trickier proposition. For example Matthew Garrett had an awful experience with some ‘intelligent’ light bulbs, which effectively circumvented any home network security you might have set up. The manufacturer’s defence? No longer manufactured or supported.
It’s cases like these that have slowly led me to a more complete understanding of the freedom that Free Software truly offers to users. It’s not just about cost free/low cost software. It’s not just about being able to learn from looking at the source to the programs you are running. It’s not even about the freedom to be able to modify the programs that we use. It’s about giving users true Freedom to use and modify their devices as they see fit. From this viewpoint it is much easier to understand the protections against Tivoization that were introduced with GPLv3, and better appreciate the argument sometimes made that the GPL offers more freedom than BSD style licenses.
I have a Brother HL-3040CN networked colour laser printer. I bought it 5 years ago and I kinda wish I hadn’t. I’d done the appropriate research to confirm it worked with Linux, but I didn’t realise it only worked via a 32-bit binary driver. It’s the only reason I have 32 bit enabled on my house server and I really wish I’d either bought a GDI printer that had an open driver (Samsung were great for this in the past) or something that did PCL or Postscript (my parents have an Xerox Phaser that Just Works). However I don’t print much (still just on my first set of toner) and once setup the driver hasn’t needed much kicking.
A more major problem comes with firmware updates. Brother only ship update software for Windows and OS X. I have a Windows VM but the updater wants the full printer driver setup installed and that seems like overkill. I did a bit of poking around and found reference in the service manual to the ability to do an update via USB and a firmware file. Further digging led me to a page on resurrecting a Brother HL-2250DN, which discusses recovering from a failed firmware flash. It provided a way of asking the Brother site for the firmware information.
First I queried my printer details:
$ snmpwalk -v 2c -c public hl3040cn.local iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2 iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.1 = STRING: "MODEL=\"HL-3040CN series\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.2 = STRING: "SERIAL=\"G0JXXXXXX\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.3 = STRING: "SPEC=\"0001\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.4 = STRING: "FIRMID=\"MAIN\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.5 = STRING: "FIRMVER=\"1.11\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.6 = STRING: "FIRMID=\"PCLPS\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.7 = STRING: "FIRMVER=\"1.02\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.8 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.9 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.10 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.11 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.12 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.13 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.14 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.15 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.16 = STRING: ""
I used that to craft an update file which I sent to Brother via curl:
curl -X POST -d @hl3040cn-update.xml https://firmverup.brother.co.jp/kne_bh7_update_nt_ssl/ifax2.asmx/fileUpdate -H "Content-Type:text/xml" --sslv3
This gave me back some XML with a URL for the latest main firmware, version 1.19, filename
LZ2599_N.djif. I downloaded that and took a look at it, discovering it looked like a PJL file. I figured I’d see what happened if I sent it to the printer:
cat LZ2599_N.djf | nc hl3040cn.local 9100
The LCD on the front of printer proceeded to display something like “Updating Program” and eventually the printer re-DHCPed and indicated the main firmware had gone from 1.11 to 1.19. Great! However the PCLPS firmware was still at 1.02 and I’d got the impression that 1.04 was out. I didn’t manage to figure out how to get the Brother update website to give me the 1.04 firmware, but I did manage to find a copy of
LZ2600_D.djf which I was then able to send to the printer in the same way. This led to:
$ snmpwalk -v 2c -c public hl3040cn.local iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2 iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.1 = STRING: "MODEL=\"HL-3040CN series\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.2 = STRING: "SERIAL=\"G0JXXXXXX\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.3 = STRING: "SPEC=\"0001\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.4 = STRING: "FIRMID=\"MAIN\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.5 = STRING: "FIRMVER=\"1.19\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.6 = STRING: "FIRMID=\"PCLPS\"" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.7 = STRING: "FIRMVER=\"1.04\"" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.8 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.9 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.10 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.11 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.12 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.13 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.14 = STRING: "" iso.188.8.131.52.1.24184.108.40.206.220.127.116.11.1.2.15 = STRING: "" iso.18.104.22.168.1.2422.214.171.124.126.96.36.199.1.2.16 = STRING: ""
[Disclaimer: This worked for me. I’ve no idea if it’ll work for anyone else. Don’t come running to me if you brick your printer.]
subscribe via RSS