This feed does not validate.
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
<?xml version="1.0"?><rss version="2.0"> <channel> <title>blogit.vapaasuomi.fi</title> <link>default</link> <language>en</language> <description>blogit.vapaasuomi.fi - default</description> <item> <title>Ville-Pekka Vainio: How to find the current ChromeOS Flex image</title> <guid isPermaLink="false">https://vpv.kapsi.fi/blog/?p=207</guid> <link>https://vpv.kapsi.fi/blog/2022/08/how-to-find-the-current-chromeos-flex-image/</link> <description><p>Edit: The quick answer to the question by a reader of my blog, Julien:</p> <blockquote class="wp-block-quote"><p>The info to download Chrome OS Flex from Linux is a bit hidden, but official info and link is available here: <a href="https://support.google.com/chromeosflex/answer/11543105?hl=en#zippy=%2Chow-do-i-create-a-chromeos-flex-usb-installer-on-linux">https://support.google.com/chromeosflex/answer/11543105?hl=en#zippy=%2Chow-do-i-create-a-chromeos-flex-usb-installer-on-linux</a></p></blockquote> <p>My dad has an Acer Chromebook 14 CB3-431, codenamed Edgar. Google just stopped supporting it with ChromeOS, but it’s still working well. Luckily, <a href="https://cloud.google.com/blog/products/chrome-enterprise/chromeos-flex-ready-to-scale-to-pcs-and-macs">Google also just released the first stable version of ChromeOS Flex.</a> </p> <p>I decided to install the full UEFI image to the Chromebook from <a href="https://mrchromebox.tech/">https://mrchromebox.tech/</a> so that starting Flex would be as easy as possible. That went well after <a href="https://www.ifixit.com/Teardown/Acer+Chromebook+14+Teardown/76353">finding and removing the write protect screw</a>.</p> <p>But it wasn’t too easy to find the URL to download the current ChromeOS Flex installation image. Google’s Chromebook recovery extension for Chrome does not work on Linux. By reading through some reddit threads, I found out that you can get the download URLs from this json file: <a href="https://dl.google.com/dl/edgedl/chromeos/recovery/cloudready_recovery2.json">https://dl.google.com/dl/edgedl/chromeos/recovery/cloudready_recovery2.json</a> So as of this writing, the current image is <a href="https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_14816.99.0_reven_recovery_stable-channel_mp-v2.bin.zip">https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_14816.99.0_reven_recovery_stable-channel_mp-v2.bin.zip</a></p> <p>Use <code>dd</code> to write the image straight to a USB stick (not to a partition) and you should be good to go. Flex installs pretty much like a regular Linux distribution and seems to work well.</p></description> <pubDate>Wed, 03 Aug 2022 16:02:51 +0000</pubDate></item><item> <title>Ville-Pekka Vainio: SAS2008 LBA, Seagate Ironwolfs and scary log messages</title> <guid isPermaLink="false">http://vpv.kapsi.fi/blog/?p=202</guid> <link>https://vpv.kapsi.fi/blog/2022/07/sas2008-lba-seagate-ironwolfs-and-scary-log-messages/</link> <description><p>I built a home NAS two years ago, that was the first COVID summer and I finally had the time. It’s running Proxmox, which is running TrueNAS (then Core, now Scale) as a VM. An HBA card is passed directly to the TrueNAS VM. The HBA card is a Dell PERC H310, but I’ve crossflashed it so that now it shows up as an LSI SAS2008 PCI-Express Fusion-MPT SAS-2. The system originally had five ST4000VN008 disks (4 TB) in a RAIDZ2.</p> <p>Pretty much from the beginning I noticed the system was spewing out storage related error messages when booting up. ZFS also noticed, but after the TrueNAS VM was completely up, there were no more errors and I quite rarely rebooted or shut down the system, so I wasn’t too worried. The few read errors I got each boot I cleared with <code>zpool clear</code>, which probably was not the best idea.</p> <p>Last summer we had very cheap electricity here in Finland, something like 1-3 c/kWh plus transfer and taxes. Well, this summer it can be even 60 c/kWh during the worst times. I started shutting down my NAS when I knew we would not need it for a while. This made the disk issues worse.</p> <p><em>I know the high electricity prices are partly due to Russia’s attack in Ukraine and the sanctions against Russia. I completely support Ukraine, they are fighting for the freedom of all of the Eastern EU border states. <a href="https://www.defendukraine.org/donate">Please donate to support Ukraine.</a></em></p> <p>TrueNAS keeps only one day of systemd journal data (why?) so I’ve already lost the actual error messages. By going through my Google search history I was able to find some of the errors I got. They were like this:</p> <pre class="wp-block-preformatted">Unaligned partial completion ...tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE ...print_req_error: critical medium error ... </pre> <p>Because there’s quite a lot of discussion on the web about Ironwolf firmware issues, issues with NCQ etc. I hoped this was something that could be fixed with software. I tried passing many kernel options found by googling to the TrueNAS Scale kernel. I came up with <code>libata.force=noncq mpt3sas.msix_disable=1 mpt3sas.max_queue_depth=10000</code>. For more discussion on these issues, see <a href="https://www.reddit.com/r/synology/comments/eri5dg/ds1019_ironwolf_8tb_softlocks_high_io_waits/">here</a>, <a href="https://www.truenas.com/community/threads/synchronize-cache-command-timeout-error.55067/">here</a>, <a href="https://forums.servethehome.com/index.php?threads/lsi9211-8i-on-ubuntu-15-10-timeouts.8820/page-2">here</a>, <a href="https://forum.proxmox.com/threads/solved-proxmox-7-linux-5-11-22-issue-with-lsi-2008-controllers.93781/page-2">here</a>. <a href="https://blog.quindorian.org/2019/09/ironwolf10tbfirmwarefix.html/">Seagate has actually released a firmware update from SC60 to SC61 for the larger Ironwolfs</a>, but I have the 4 TB ones without an update available.</p> <p>None of these options helped. Eventually the whole disk just disappeared. At this point it was clear to me that the issue was not a kernel bug, a disk firmware bug, an HBA firmware bug or anything like that. The disk had been faulty already on arrival.</p> <p>I noticed Seagate has come up with new versions of the Ironwolfs. The 4 TB version is now ST4000VN006 with 256 MB of cache instead of 64 MB. The new version is also physically thinner and might run cooler. I ordered one of those. Unfortunately the firmware version is still SC60.</p> <p>I replaced the faulty disk with the new one, ZFS resilvered the pool in about 8 hours and all is good again. I guess the moral of the story is that it seems like a disk could be defective, it probably is and you should start by replacing it.</p></description> <pubDate>Sun, 03 Jul 2022 15:50:56 +0000</pubDate></item><item> <title>Losca: Unboxing Dell XPS 13 - openSUSE Tumbleweed alongside preinstalled Ubuntu</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31939153.post-5725411947102284158</guid> <link>https://losca.blogspot.com/2022/01/unboxing-dell-xps-13-opensuse.html</link> <description><h2 class="post-subheading">A look at the 2021 model of Dell XPS 13 - available with Linux pre-installed</h2><div style="text-align: left;" class="post-subheading">I received a new laptop for work - a Dell XPS 13. Dell has been long famous for offering certain models with pre-installed Linux as a supported option, and opting for those is nice for moving some euros/dollars from certain PC desktop OS monopoly towards Linux desktop engineering costs. Notably Lenovo also offers Ubuntu and Fedora options on many models these days (like Carbon X1 and P15 Gen 2).</div><div style="text-align: left;" class="post-subheading"><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEicuZ7XvyUKRebCvC7ZmFWeS4Tilqv82EK5B42kscToOaLrCUZKKB0aup1bC9ZEEHLWGrh2uwT58I_3cs2N6KWxVy7WVQpxtA4E-DA0BIJ-xzGuW-L8S9G4OZ4P7LXB-Byk0qBJ6zFXLW07aUGnOImbvF78nqCSJ0Lqi7AcvlarHGlYfLUrhtk=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEicuZ7XvyUKRebCvC7ZmFWeS4Tilqv82EK5B42kscToOaLrCUZKKB0aup1bC9ZEEHLWGrh2uwT58I_3cs2N6KWxVy7WVQpxtA4E-DA0BIJ-xzGuW-L8S9G4OZ4P7LXB-Byk0qBJ6zFXLW07aUGnOImbvF78nqCSJ0Lqi7AcvlarHGlYfLUrhtk=w400-h301" alt="black box" border="0" width="400" height="301" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEhAQXfzLQ6p0ZMmSSoWQggPqiS_cGyQIoyc2kSTN_5vNYzB2nKhqzRQ_hMmgsMzl4KDDmX_A3hTmfW9Hx4vJO8VYjcF-1BIyzzRzJaxGAoEwdY5CEYkpCu39-AO0MSAjUKsHq1lyq_TVsq9RwShP0LKiVm85KYWG5g7hg-7Toypf_j3LeptQYA=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEhAQXfzLQ6p0ZMmSSoWQggPqiS_cGyQIoyc2kSTN_5vNYzB2nKhqzRQ_hMmgsMzl4KDDmX_A3hTmfW9Hx4vJO8VYjcF-1BIyzzRzJaxGAoEwdY5CEYkpCu39-AO0MSAjUKsHq1lyq_TVsq9RwShP0LKiVm85KYWG5g7hg-7Toypf_j3LeptQYA=w301-h400" alt="opened box" border="0" width="301" height="400" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEhY-amtMR4CO1VWwAQoD_BIXTjqQTIea0fwtCyQi0hqprxvK5kqI7n02Zw45xcVF1ORm6m_IWAyaBLcGjTb6fK0M9PqzzXfeyIFawYEMCvZ36YKHjzVYtd_w7YD6Owj00mgoSrdrB4R5qegCxeI08PiKVZ8ZIeQk9l0Oyau4Q9tx8Xz8mJooJQ=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEhY-amtMR4CO1VWwAQoD_BIXTjqQTIea0fwtCyQi0hqprxvK5kqI7n02Zw45xcVF1ORm6m_IWAyaBLcGjTb6fK0M9PqzzXfeyIFawYEMCvZ36YKHjzVYtd_w7YD6Owj00mgoSrdrB4R5qegCxeI08PiKVZ8ZIeQk9l0Oyau4Q9tx8Xz8mJooJQ=w640-h482" alt="accessories and a leaflet about Linux support" border="0" width="640" height="482" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEgM8700UA5ss6nvfXr6oJ67bJSemgNd02PRmopJL18UtqKPKpGMBv4SEmfZdO-zURQYEyXtnEL4IO7R2ng9vbAGFgKcC6K0VtaQGsiCd7Bo3_bmzOy4S2k13aRVsgjtZH1NvgkGd8ysgSnCAW6Rd1Ynb5u6kjGrlPa87ukclm7mikOTdw-6Heg=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEgM8700UA5ss6nvfXr6oJ67bJSemgNd02PRmopJL18UtqKPKpGMBv4SEmfZdO-zURQYEyXtnEL4IO7R2ng9vbAGFgKcC6K0VtaQGsiCd7Bo3_bmzOy4S2k13aRVsgjtZH1NvgkGd8ysgSnCAW6Rd1Ynb5u6kjGrlPa87ukclm7mikOTdw-6Heg=w640-h482" alt="laptop lifted from the box, closed" border="0" width="640" height="482" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEjIvFbutG71WrXAlWVonB2TIVv-sCeS4eXafJ9DBtTjTa0wmpW-mm-lDgPOJlZWeueZ_aji5T7FHVV1sLXWdcwG2u9orijyoBXyRE_94FPpoX2uwClQWY8CiUncJtbgLOmR6IYICcb6PNpBCXmDxZ4Qa-0-2E4UTZzZkp2U7sJQMZvQyNhU5VM=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEjIvFbutG71WrXAlWVonB2TIVv-sCeS4eXafJ9DBtTjTa0wmpW-mm-lDgPOJlZWeueZ_aji5T7FHVV1sLXWdcwG2u9orijyoBXyRE_94FPpoX2uwClQWY8CiUncJtbgLOmR6IYICcb6PNpBCXmDxZ4Qa-0-2E4UTZzZkp2U7sJQMZvQyNhU5VM=w301-h400" alt="laptop with lid open" border="0" width="301" height="400" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEier6fU4z3Q0aPa-bhKlO5p5Z--2juSL2x7d8-N7hazlotVgL1f5kfI9UkVbdsqdpmGDu_s_3BIq3s5uhFhClXBm8HSAG2LlHFT_Er2pXlRQqUs9-ixGY4vD7B-8YHcvkWUGBor3d7MZ7eRPjy24KzYom-Pi4HqNzqQtCA26lYi2t9OogkxBCA=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEier6fU4z3Q0aPa-bhKlO5p5Z--2juSL2x7d8-N7hazlotVgL1f5kfI9UkVbdsqdpmGDu_s_3BIq3s5uhFhClXBm8HSAG2LlHFT_Er2pXlRQqUs9-ixGY4vD7B-8YHcvkWUGBor3d7MZ7eRPjy24KzYom-Pi4HqNzqQtCA26lYi2t9OogkxBCA=w640-h360" alt="Ubuntu running" border="0" width="640" height="360" /></a></div><br /><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEioIl_Uw-sF5LkYjrM1DC52PjBmxDLSktOn5x5LRdl9Lsh4txT5TFM8hfMFt5WtWhME-DBPsLAXsOg8F3Ek5CbP0D3tY7n9RjSMVJ7UxirSpa2KQKmPYXkyICcFR8ME_S40paJG_TQYsX-YXor7gLHZq4zzI9ivgCrzq8m95MIPIyCDXRQ17J0=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEioIl_Uw-sF5LkYjrM1DC52PjBmxDLSktOn5x5LRdl9Lsh4txT5TFM8hfMFt5WtWhME-DBPsLAXsOg8F3Ek5CbP0D3tY7n9RjSMVJ7UxirSpa2KQKmPYXkyICcFR8ME_S40paJG_TQYsX-YXor7gLHZq4zzI9ivgCrzq8m95MIPIyCDXRQ17J0=w640-h360" alt="openSUSE runnin" border="0" width="640" height="360" /></a></div> </div><div style="text-align: left;" class="post-subheading">Obviously a smooth, ready-to-rock Ubuntu installation is nice for most people already, but I need openSUSE, so after checking everything is fine with Ubuntu, I continued to install openSUSE Tumbleweed as a dual boot option. As I’m a funny little tinkerer, I obviously went with some special things. I wanted:<ul><li>Ubuntu to remain as the reference supported OS on a small(ish) partition, useful to compare to if trying out new development versions of software on openSUSE and finding oddities.</li><li>openSUSE as the OS consuming most of the space.</li><li>LUKS encryption for openSUSE without LVM.</li><li>ext4’s new fancy ‘fast_commit’ feature in use during filesystem creation.</li><li>As a result of all that, I ended up juggling back and forth installation screens a couple of times (even more than shown below, and also because I forgot I wanted to use encryption the first time around).</li></ul>First boots to pre-installed Ubuntu and installation of openSUSE Tumbleweed as the dual-boot option: </div><div style="text-align: left;" class="post-subheading"><div style="clear: both; text-align: center;" class="separator"></div><div style="clear: both; text-align: center;" class="separator"></div><div style="clear: both; text-align: center;" class="separator"></div><div style="clear: both; text-align: center;" class="separator"></div><div style="clear: both; text-align: center;" class="separator"></div></div><div style="text-align: left;" class="post-subheading"> </div><div style="text-align: left;" class="post-subheading">(if the embedded video is not shown, use a <a href="https://timojyrinki.gitlab.io/hugo/post/2022-01-26-dell-xps-13-developer-edition-ubuntu-opensuse/dellxps13video.webm">direct link</a>) <br /></div><div style="text-align: left;" class="post-subheading"> </div><div style="text-align: left;" class="post-subheading">Some notes from the openSUSE installation:<ul><li>openSUSE installer’s partition editor apparently does not support resizing or automatically installing side-by-side another Linux distribution, so I did part of the setup completely on my own.</li><li>Installation package download hanged a couple of times, only passed when I entered a mirror manually. On my TW I’ve also noticed download problems recently, there might be a problem with some mirror I need to escalate.</li><li>The installer doesn’t very clearly show encryption status of the target installation - it took me a couple of attempts before I even noticed the small “encrypted” column and icon (well, very small, see below), which also did not spell out the device mapper name but only the main partition name. In the end it was going to do the right thing right away and use my pre-created encrypted target partition as I wanted, but it could be a better UX. Then again I was doing my very own tweaks anyway.</li><li>Let’s not go to the details why I’m so old-fashioned and use ext4 :)</li><li>openSUSE’s installer does not work fine with HiDPI screen. Funnily the tty consoles seem to be fine and with a big font.</li><li>At the end of the video I install the two GNOME extensions I can’t live without, Dash to Dock and Sound Input &amp; Output Device Chooser.</li></ul></div></description> <pubDate>Wed, 26 Jan 2022 12:51:00 +0000</pubDate> <author>noreply@blogger.com (TJ)</author></item><item> <title>Losca: Working and warming up cats</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31939153.post-7024444298640709527</guid> <link>https://losca.blogspot.com/2021/12/working-and-warming-up-cats.html</link> <description><h2 class="post-subheading">How to disable internal keyboard/touchpad when a cat arrives</h2><article class="blog-post"> <p>I’m using an external keyboard (<span style="color: red;"><b>1</b></span>) and mouse (<span style="color: red;"><b>2</b></span>), but the laptop lid is usually still open for better cooling. That means the internal keyboard (<span style="color: red;"><b>3</b></span>) and touchpad (<span style="color: red;"><b>4</b></span>) – made of comfortable materials – are open to be used by a cat searching for warmth (<span style="color: red;"><b>7</b></span>), in the obvious “every time” case that a normal non-heated nest (<span style="color: red;"><b>6</b></span>) is not enough.</p><div style="clear: both; text-align: center;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://blogger.googleusercontent.com/img/a/AVvXsEjNVHf4gKBafCOycb9ngwogjPRA8YCyUl89dGgv0Mnd4dX7wkDB-b7sDCqR65vC3blHsvSO1evqeLkklAVAx3ot65RBQAi-xiJ7seM18tw1GZjnr3dUWB74yRp0RFUJkTYY_uhojiVTBqiqOKayd-pxWfNsfylhmP2Bp4XXxvUAAc0GHMyFvi8=s1280"><img src="https://blogger.googleusercontent.com/img/a/AVvXsEjNVHf4gKBafCOycb9ngwogjPRA8YCyUl89dGgv0Mnd4dX7wkDB-b7sDCqR65vC3blHsvSO1evqeLkklAVAx3ot65RBQAi-xiJ7seM18tw1GZjnr3dUWB74yRp0RFUJkTYY_uhojiVTBqiqOKayd-pxWfNsfylhmP2Bp4XXxvUAAc0GHMyFvi8=w640-h525" border="0" width="640" height="525" /></a></div><p></p><p>The problem is, everything goes chaotic at that point in the default configuration. The solution is to have quick shortcuts in my Dash to Dock (<span style="color: red;"><b>8</b></span>) to both disable (<span style="color: red;"><b>10</b></span>) and enable (<span style="color: red;"><b>9</b></span>) keyboard and touchpad at a very rapid pace.</p><p>It is to be noted that I’m not disabling the touch screen (<span style="color: red;"><b>5</b></span>) by default, because most of the time the cat is not leaning on it – there is also the added benefit that if one forgets about the internal keyboard and touchpad disabling and detaches the laptop from the USB-C monitor (<span style="color: red;"><b>11</b></span>), there’s the possibility of using the touch screen and on-screen keyboard to type in the password and tap on the keyboard/touchpad enabling shortcut button again. If also touch screen was disabled, the only way would be to go back to an external keyboard or reboot.</p><p>So here are the scripts. First, the disabling script (pardon my copy-paste use of certain string manipulation tools):</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs">dconf write /org/gnome/desktop/peripherals/touchpad/send-events <span class="s2"><span class="hljs-string">"'disabled'"</span></span><br />sudo killall evtest<br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"AT Translated Set 2 keyboard"</span></span> <span class="p">|</span> tail -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"Dell WMI"</span></span> <span class="p">|</span> tail -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"Power"</span></span> <span class="p">|</span> grep Kernel <span class="p">|</span> tail -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"Power"</span></span> <span class="p">|</span> grep Kernel <span class="p">|</span> head -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"Sleep"</span></span> <span class="p">|</span> grep Kernel <span class="p">|</span> tail -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"HID"</span></span> <span class="p">|</span> grep Kernel <span class="p">|</span> head -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br />sudo evtest --grab <span class="k">$(</span>sudo libinput list-devices <span class="p">|</span> grep -A <span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"HID"</span></span> <span class="p">|</span> tail -n <span class="m"><span class="hljs-number">1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\/dev/\/dev/'</span></span><span class="k">)</span> <span class="p">&amp;</span><br /><span class="c1"><span class="hljs-comment">#sudo evtest --grab $(sudo libinput list-devices | grep -A 1 "ELAN" | tail -n 1 | sed 's/.*\/dev/\/dev/') # Touch screen</span></span><br /></code></pre></div><p>And the associated ~/.local/share/applications/disable-internal-input.desktop:</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs"><span class="o">[</span>Desktop Entry<span class="o">]</span><br /><span class="nv">Version</span><span class="o">=</span><span class="hljs-number">1.0</span><br /><span class="nv">Name</span><span class="o">=</span>Disable internal input<br /><span class="nv">GenericName</span><span class="o">=</span>Disable internal input<br /><span class="nv">Exec</span><span class="o">=</span>/bin/bash -c /home/timo/Asiakirjat/helpers/<span class="hljs-built_in">disable</span>-internal-input.sh<br /><span class="nv">Icon</span><span class="o">=</span>yast-keyboard<br /><span class="nv">Type</span><span class="o">=</span>Application<br /><span class="nv">Terminal</span><span class="o">=</span><span class="nb"><span class="hljs-literal">false</span></span><br /><span class="nv">Categories</span><span class="o">=</span>Utility<span class="p">;</span>Development<span class="p">;</span><br /></code></pre></div><p>Here’s the enabling script:</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs">dconf write /org/gnome/desktop/peripherals/touchpad/send-events <span class="s2"><span class="hljs-string">"'enabled'"</span></span><br />sudo killall evtest<br /></code></pre></div><p>and the desktop file:</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs"><span class="o">[</span>Desktop Entry<span class="o">]</span><br /><span class="nv">Version</span><span class="o">=</span><span class="hljs-number">1.0</span><br /><span class="nv">Name</span><span class="o">=</span>Enable internal input<br /><span class="nv">GenericName</span><span class="o">=</span>Enable internal input<br /><span class="nv">Exec</span><span class="o">=</span>/bin/bash -c /home/timo/Asiakirjat/helpers/<span class="hljs-built_in">enable</span>-internal-input.sh<br /><span class="nv">Icon</span><span class="o">=</span>/home/timo/.local/share/icons/hicolor/scalable/apps/yast-keyboard-enable.png<br /><span class="nv">Type</span><span class="o">=</span>Application<br /><span class="nv">Terminal</span><span class="o">=</span><span class="nb"><span class="hljs-literal">false</span></span><br /><span class="nv">Categories</span><span class="o">=</span>Utility<span class="p">;</span>Development<span class="p">;</span><br /></code></pre></div><p>With these, if I sense a cat or am just proactive enough, I press <i>Super+9</i>. If I’m about to detach my laptop from the monitor, I press <i>Super+8</i>. If I forget the latter (usually this is the case) and haven’t yet locked the screen, I just tap the enabling icon on the touch screen.</p> </article></description> <pubDate>Tue, 14 Dec 2021 07:29:00 +0000</pubDate> <author>noreply@blogger.com (TJ)</author></item><item> <title>Ville-Pekka Vainio: How I made Firefox much faster with an Estonian ID card</title> <guid isPermaLink="false">http://vpv.kapsi.fi/blog/?p=187</guid> <link>https://vpv.kapsi.fi/blog/2021/10/how-i-made-firefox-much-faster-with-an-estonian-id-card/</link> <description><p>I haven’t blogged in almost ten years, wow. This time I discovered something that I think deserves a blog post.<br />I have an <a href="https://e-resident.gov.ee/">Estonian e-Residency</a> because I speak Estonian and visit quite often (at least when there’s not a pandemic going on). My default Firefox profile is easily more than 10 years old. With the Estonian ID card inserted into a card reader, Firefox has always been very slow with that profile, pretty much unusable.</p> <p>With a fresh Firefox profile everything has worked very well, there’s a bit of slowness that I can see when browsing with the ID card inserted compared to when the card is not in the reader, but it’s not significant. Today I wanted to register as a reader at the <a href="https://keskraamatukogu.ee/">Tallinn Central Library</a>, because they offer Estonian e-books that I would like to read. Having to open a fresh Firefox profile to browse a library web site irritated me enough that I started looking for a solution. I found the solution by reading the <a href="https://wiki.archlinux.org/title/Common_Access_Card">CAC page of the Arch wiki</a>.</p> <p>I went to Edit <code>-&gt;</code> Settings <code>-&gt;</code> Privacy &amp; Security <code>-&gt;</code> Security Devices. I saw that my old profile had both “OpenSC PKCS” and “OpenSC PKCS#11 Module” in there. The fresh profiles did not have the “OpenSC PKSC” entry. So I removed that one and now the browser works faster.</p> <p>I typically use Finnish on the desktop, just because I believe everyone should be able to use free and open source software in their native language. I’ll attach a screenshot, which is in Finnish. The entry marked with a square is the one I had to remove. I’m using Firefox 93 on Fedora 35.</p> <p> </p> <figure class="wp-block-image size-medium is-resized"><a href="https://vpv.kapsi.fi/blog/wp-content/uploads/2021/10/security_devices.png"><img src="https://vpv.kapsi.fi/blog/wp-content/uploads/2021/10/security_devices-300x132.png" alt="Screenshot of the security devices screen in Firefox." width="464" class="wp-image-192" height="204" /></a></figure></description> <pubDate>Thu, 28 Oct 2021 19:09:34 +0000</pubDate></item><item> <title>Losca: MotionPhoto / MicroVideo File Formats on Pixel Phones</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31939153.post-8073088443065920753</guid> <link>https://losca.blogspot.com/2021/03/motionphoto-microvideo-file-formats-on.html</link> <description><p>Google Pixel phones support what they call ”Motion Photo” which is essentially a photo with a short video clip attached to it. They are quite nice since they bring the moment alive, especially as the capturing of the video starts a small moment before the shutter button is pressed. For most viewing programs they simply show as static JPEG photos, but there is more to the files. </p><article class="blog-post"><p>I’d really love proper Shotwell support for these file formats, so I posted a longish explanation with many of the details in this blog post to a ticket there too. Examples of the newer format are linked there too.</p><p><a href="https://gitlab.gnome.org/GNOME/shotwell/-/issues/233#note_1064700"></a></p><div style="clear: both; text-align: left;" class="separator"><a style="margin-left: 1em; margin-right: 1em;" href="https://gitlab.gnome.org/GNOME/shotwell/-/issues/233" target="_blank"><img src="https://1.bp.blogspot.com/-813s7YZ_2Cs/YGRVpi_V9PI/AAAAAAAADZc/Nv7pTzlTuK4kaH5INxnj9LkHW_eV4cRXQCLcBGAsYHQ/w251-h320/format-info-shotwell-ticket_small.png" alt="Info posted to Shotwell ticket" border="0" width="251" height="320" /></a></div><br /><p></p><p>There are actually two different formats, an old one that is already obsolete, and a newer current format. The older ones are those that your Pixel phone recorded as ”MVIMG_[datetime].jpg", and they have the following meta-data:</p><pre><code class="hljs">Xmp.GCamera.MicroVideo XmpText 1 1<br />Xmp.GCamera.MicroVideoVersion XmpText 1 1<br />Xmp.GCamera.MicroVideoOffset XmpText 7 4022143<br />Xmp.GCamera.MicroVideoPresentationTimestampUs XmpText 7 1331607<br /></code></pre><p>The offset is actually from <i>the end of the file</i>, so one needs to calculate accordingly. But it is exact otherwise, so one simply extract a file with that meta-data information:</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs"><span class="cp"><span class="hljs-shebang">#!/bin/bash</span><br /></span><span class="cp"></span><span class="c1"><span class="hljs-comment">#</span></span><br /><span class="c1"><span class="hljs-comment"># Extracts the microvideo from a MVIMG_*.jpg file</span></span><br /><br /><span class="c1"><span class="hljs-comment"># The offset is from the ending of the file, so calculate accordingly</span></span><br /><span class="nv">offset</span><span class="o">=</span><span class="k">$(</span>exiv2 -p X <span class="s2"><span class="hljs-string">"</span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="s2"><span class="hljs-string">"</span></span> <span class="p">|</span> grep MicroVideoOffset <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/.*\"\(.*\)"/\1/'</span></span><span class="k">)</span><br /><span class="nv">filesize</span><span class="o">=</span><span class="k">$(</span>du --apparent-size --block<span class="o">=</span><span class="m"><span class="hljs-number">1</span></span> <span class="s2"><span class="hljs-string">"</span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="s2"><span class="hljs-string">"</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/^\([0-9]*\).*/\1/'</span></span><span class="k">)</span><br /><span class="nv">extractposition</span><span class="o">=</span><span class="k">$(</span>expr <span class="nv"><span class="hljs-variable">$filesize</span></span> - <span class="nv"><span class="hljs-variable">$offset</span></span><span class="k">)</span><br /><span class="nb"><span class="hljs-built_in">echo</span></span> offset: <span class="nv"><span class="hljs-variable">$offset</span></span><br /><span class="nb"><span class="hljs-built_in">echo</span></span> filesize: <span class="nv"><span class="hljs-variable">$filesize</span></span><br /><span class="nb"><span class="hljs-built_in">echo</span></span> <span class="nv">extractposition</span><span class="o">=</span><span class="nv"><span class="hljs-variable">$extractposition</span></span><br />dd <span class="k"><span class="hljs-keyword">if</span></span><span class="o">=</span><span class="s2"><span class="hljs-string">"</span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="s2"><span class="hljs-string">"</span></span> <span class="nv">skip</span><span class="o">=</span><span class="m"><span class="hljs-number">1</span></span> <span class="nv">bs</span><span class="o">=</span><span class="nv"><span class="hljs-variable">$extractposition</span></span> <span class="nv">of</span><span class="o">=</span><span class="s2"><span class="hljs-string">"</span></span><span class="k"><span class="hljs-string"><span class="hljs-variable">$(</span></span></span><span class="hljs-string"><span class="hljs-variable">basename -s .jpg </span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="k"><span class="hljs-string"><span class="hljs-variable">)</span></span></span><span class="s2"><span class="hljs-string">.mp4"</span></span><br /></code></pre></div><p>The newer format is recorded in filenames called ”PXL_[datetime].MP.jpg”, and they have a _lot_ of additional metadata:</p><pre><code class="hljs ruby"><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">GCamera</span>.<span class="hljs-constant">MotionPhoto</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">1</span> <span class="hljs-number">1</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">GCamera</span>.<span class="hljs-constant">MotionPhotoVersion</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">1</span> <span class="hljs-number">1</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">GCamera</span>.<span class="hljs-constant">MotionPhotoPresentationTimestampUs</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">6</span> <span class="hljs-number">233320</span><br /><span class="hljs-constant">Xmp</span>.xmpNote.<span class="hljs-constant">HasExtendedXMP</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">32</span> <span class="hljs-constant">E1F7505D2DD64EA6948D2047449F0FFA</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">0</span> type=<span class="hljs-string">"Seq"</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>] <span class="hljs-constant">XmpText</span> <span class="hljs-number">0</span> type=<span class="hljs-string">"Struct"</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">0</span> type=<span class="hljs-string">"Struct"</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Mime</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">10</span> image/jpeg<br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Semantic</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">7</span> <span class="hljs-constant">Primary</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Length</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">1</span> <span class="hljs-number">0</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">1</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Padding</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">1</span> <span class="hljs-number">0</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>] <span class="hljs-constant">XmpText</span> <span class="hljs-number">0</span> type=<span class="hljs-string">"Struct"</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">0</span> type=<span class="hljs-string">"Struct"</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Mime</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">9</span> video/mp4<br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Semantic</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">11</span> <span class="hljs-constant">MotionPhoto</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Length</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">7</span> <span class="hljs-number">1679555</span><br /><span class="hljs-constant">Xmp</span>.<span class="hljs-constant">Container</span>.<span class="hljs-constant">Directory</span>[<span class="hljs-number">2</span>]/<span class="hljs-constant">Container</span><span class="hljs-symbol">:Item/Item</span><span class="hljs-symbol">:Padding</span> <span class="hljs-constant">XmpText</span> <span class="hljs-number">1</span> <span class="hljs-number">0</span><br /></code></pre><p>Sounds like fun and lots of information. However I didn’t see why the “length” in first item is 0 and I didn’t see how to use the latter Length info. But I can use the mp4 headers to extract it:</p><div class="highlight"><pre class="chroma"><code class="language-bash hljs"><span class="cp"><span class="hljs-shebang">#!/bin/bash</span><br /></span><span class="c1"><span class="hljs-comment">#</span></span><br /><span class="c1"><span class="hljs-comment"># Extracts the motion part of a MotionPhoto file PXL_*.MP.mp4</span></span><br /><br /><span class="nv">extractposition</span><span class="o">=</span><span class="k">$(</span>grep --binary --byte-offset --only-matching --text \<br />-P <span class="s2"><span class="hljs-string">"\x00\x00\x00\x18\x66\x74\x79\x70\x6d\x70\x34\x32"</span></span> <span class="nv"><span class="hljs-variable">$1</span></span> <span class="p">|</span> sed <span class="s1"><span class="hljs-string">'s/^\([0-9]*\).*/\1/'</span></span><span class="k">)</span><br /><br />dd <span class="k"><span class="hljs-keyword">if</span></span><span class="o">=</span><span class="s2"><span class="hljs-string">"</span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="s2"><span class="hljs-string">"</span></span> <span class="nv">skip</span><span class="o">=</span><span class="m"><span class="hljs-number">1</span></span> <span class="nv">bs</span><span class="o">=</span><span class="nv"><span class="hljs-variable">$extractposition</span></span> <span class="nv">of</span><span class="o">=</span><span class="s2"><span class="hljs-string">"</span></span><span class="k"><span class="hljs-string"><span class="hljs-variable">$(</span></span></span><span class="hljs-string"><span class="hljs-variable">basename -s .jpg </span></span><span class="nv"><span class="hljs-string"><span class="hljs-variable">$1</span></span></span><span class="k"><span class="hljs-string"><span class="hljs-variable">)</span></span></span><span class="s2"><span class="hljs-string">.mp4"</span></span><br /></code></pre></div><p><b>UPDATE: I wrote most of this blog post earlier. When now actually getting to publishing it a week later, I see the obvious ie the ”Length” is again simply the offset from the end of the file so one could do the same less brute force approach as for MVIMG. I’ll leave the above as is however for the ❤️ of binary grepping.</b></p><p><b>UPDATE 08/2021: Here's the script to extract also MP without brute force:</b></p><p><code class="language-bash hljs"><span class="cp"><span class="hljs-shebang">#!/bin/bash</span></span></code><code class="language-bash hljs"><br />#<br /># Extracts the motion part of a MotionPhoto file PXL_*.MP.mp4<br /><br />set -e<br /># Brute force<br />#extractposition=$(grep --binary --byte-offset --only-matching --text -P "\x00\x00\x00\x18\x66\x74\x79\x70\x6d\x70\x34\x32" $1 | sed 's/^\([0-9]*\).*/\1/')<br /><br /># Metadata<br />offset=$(exiv2 -p x "$1" | grep Length | tail -n 1 | rev | cut -d ' ' -f 1 | rev)<br />echo offset: ${offset}<br />re='^[0-9]+$'<br />if ! [[ $offset =~ $re ]] ; then<br /> echo "offset not found"<br /> exit 1<br />fi<br />filesize=$(du --apparent-size --block=1 "$1" | sed 's/^\([0-9]*\).*/\1/')<br /><br />echo filesize: $filesize<br />extractposition=$(expr $filesize - $offset)<br />echo extractposition=$extractposition<br /><br />dd if="$1" skip=1 bs=$extractposition of="$(basename -s .jpg $1).mp4"<br /></code></p><p><span style="font-size: xx-small;">(cross-posted to my <a href="https://timojyrinki.gitlab.io/hugo/post/2021-03-30-pixel-motionphoto-microvideo-file-formats/">other blog</a>)</span><b><br /></b></p> </article></description> <pubDate>Wed, 31 Mar 2021 11:06:00 +0000</pubDate> <author>noreply@blogger.com (TJ)</author></item><item> <title>Riku Voipio: This is the year not to fly</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-997920555510565452.post-1077727399903521805</guid> <link>http://suihkulokki.blogspot.com/2020/03/this-is-year-not-to-fly.html</link> <description><img src="https://kos.to/plane.jpg" width="488" height="320" /> <p>If you have to choose one year when you won't fly, this year, 2020, is the one to choose. Why? Because CORSIA.</p> <h3>What the heck is CORSIA?</h3> <p><a href="https://www.icao.int/environmental-protection/CORSIA/Pages/default.aspx">CORSIA</a> is not a novel virus, but "Carbon Offsetting and Reduction Scheme for International Aviation". In a nutshell, the aviation industry says they will freeze their co2 emissions from growing. Actually, aviation emissions are still going to grow. The airlines will just pay someone else to reduce emissions with the same amount aviation emissions rise - the "Offsetting" word in CORSIA. If that sounds like greenwashing, well it pretty much is. But that was expected. Getting every country and airline abroad CORSIA would not have been possible if the scheme would actually bite. So it's pretty much a joke. </p> <img src="https://kos.to/corsia.png" width="488" height="227" /> <h3>What does it have to do with *this* Year?</h3> <p>The first phase of CORSIA will start next year, so the emissions are frozen to year 2020 levels. Due to certain recent events, lots of flights have already been cancelled - which means the reference year aviation emissions are already a lot less than the aviation industry was expecting. By avoiding flying this year, the aviation emissions are going to be frozen at an even lower level. This will increase cost of co2 offsetting for airlines, and the joke is going to be on them. </p> <p>So consider skipping business travel and taking your holiday trip this year with something else than a plane. Wouldn't recommend a cruise ship, tho...</p></description> <pubDate>Wed, 11 Mar 2020 20:43:18 +0000</pubDate> <author>noreply@blogger.com (Riku Voipio)</author></item><item> <title>Viikon VALO: Jupyter Notebook</title> <guid isPermaLink="true">https://viikonvalo.fi/jupyter_notebook/</guid> <link>https://viikonvalo.fi/jupyter_notebook/</link> <description>Jupyter Notebook on datatieteilijöiden keskuudessa suosittu ohjelmointiympäristö, jolla luodaan tekstiä, kuvia ja ohjelmointikieltä yhdistäviä muistioita.Tietotekniikan maailmassa on noussut trendikkääksi termiksi datatiede, jolla pyritään tilastollisin menetelmin ja koneoppimisen keinoin löytämään tietomassasta poikkeamia, toistuvia malleja ja sääntöjä. Esimerkiksi datatieteilijä voi selvittää asiakkaan ostohistorian perusteella, mitä tuotetta kannattaa seuraavaksi suositella. Tämän tyylisiä analyyseja voi tehdä useilla eri välineillä, mutta suosituiksi työkaluiksi ovat tulleet Python-ohjelmointikieli ja sen kehitysympäristö Jupyter Notebook.Jupyter Notebook on selaimella käytettävä ohjelmointityökalu, jolla voi Pythonin lisäksi ohjelmoida useilla eri kielillä, kuten R:llä, Julialla tai Octavella, kunhan asentaa tarvittavat ytimet.</description> <pubDate>Sat, 08 Jun 2019 05:30:00 +0000</pubDate></item><item> <title>Riku Voipio: On the #uploadfilter problem</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-997920555510565452.post-4202697587559438234</guid> <link>http://suihkulokki.blogspot.com/2019/03/on-uploadfilter-problem.html</link> <description>The copyright holders in europe are pushing hard mandate upload filters for internet. We have been here before - when they outlawed circumventing DRM. Both have roots in the same problem. The copyright holders look at computers and see bad things happening to their revenue. They come to IT companies and say "FIX IT". It industry comes back and says.. "We cant.. <b>making data impossible to copy is like trying to make water not wet!</b>". But we fail at convincing copyright holders in how perfect DRM or upload filter is not possible. Then copyright holders go to law makers and ask them in turn to fix it. <p>We need to turn tables around. If they want something impossible, it should be upto them to implement it. </p><p>It is simply unfair to require each online provider to implement an AI to detect copyright infringement, manage a database of copyrighted content and pay for the costs running it all.. ..And getting slapped with a lawsuit anyways, since copyrighted content is still slipping through. </p><p><b>The burden of implementing #uploadfilter should be on the copyright holder organizations</b>. Implement as a SaaS. Youtube other web platforms call your API and pay $0.01 each time a pirate content is detected. On the other side, to ensure correctness of the filter, copyright holders have to pay any lost revenue, court costs and so on for each false positive. </p><p>Filtering uploads is still problematic. But it's now the copyright holders problem. Instead people blaming web companies for poor filters, it's the copyright holders now who have to answer to the public why their filters are rejecting content that doesn't belong to them. </p><p></p></description> <pubDate>Sat, 23 Mar 2019 16:07:46 +0000</pubDate> <author>noreply@blogger.com (Riku Voipio)</author></item><item> <title>Riku Voipio: Linus Torvalds is wrong - PC no longer defines a platform</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-997920555510565452.post-3110818024758392672</guid> <link>http://suihkulokki.blogspot.com/2019/02/linus-torvalds-is-wrong-pc-not-longer.html</link> <description>Hey, I can do these clickbait headlines too! Recently it has gotten <a href="https://www.theregister.co.uk/2019/02/23/linus_torvalds_arm_x86_servers/">media's attention</a> that Linus is <a href="https://www.realworldtech.com/forum/?threadid=183440&amp;curpostid=183486">dismissive of ARM servers</a>. The argument is roughly "Developers use X86 PCs, cross-platform development is painful, and therefor devs will use X86 servers, unless they get ARM PCs to play with". <p>This ignores the reality where majority of developers do cross-platform development every day. They develop on <a href="https://insights.stackoverflow.com/survey/2018/#technology-developers-primary-operating-systems">Mac and Windows PC's</a> and deploy on Linux servers or mobile phones. The two biggest Linux success stories, cloud and Android, are built on cross-platform development. Yes, cross-platform development sucks. But it's just one of the many things that sucks in software development. </p><p>More importantly, the ship of "local dev enviroment" has long since sailed. Using Linus's other great innovation, git, developers push their code to a <a href="https://github.com/">Microsoft server</a>, which triggers a Rube Goldberg machine of software build, container assembly, unit tests, deployment to test environment and so on - all in cloud servers. </p><p>Yes, the ability to easily by a cheap whitebox PC from CompUSA was the important factor in making X86 dominate server space. But people get cheap servers from cloud now, and even that is getting out of fashion. Services like <a href="https://aws.amazon.com/lambda/">AWS lambda</a> abstract the whole server away, and the instruction set becomes irrelevant. Which CPU and architecture will be used to run these "serverless" services is not going to depend on developers having Arm Linux Desktop PC's. </p><p>Of course there are still plenty of people like me who use Linux Desktop and run things locally. But in the big picture things are just going one way. The way where it gets easier to test things in your git-based CI loop rather than in local development setup. </p><p>But like Linus, I still do want to see an powerful PC-like Arm NUC or Laptop. One that could run mainline Linux kernel and offer a PC-like desktop experience. Not because ARM depends on it to succeed in server space (what it needs is out of scope for this blogpost) - but because PC's are useful in their own.</p></description> <pubDate>Tue, 26 Feb 2019 21:03:30 +0000</pubDate> <author>noreply@blogger.com (Riku Voipio)</author></item><item> <title>Viikon VALO: Power Ampache</title> <guid isPermaLink="true">https://viikonvalo.fi/powerampache/</guid> <link>https://viikonvalo.fi/powerampache/</link> <description>Power Ampache on musiikkia verkon yli Ampache-palvelimelta soittava Android-sovellus.Musiikin soittamisessa on viime vuosina tapahtunut voimakas siirtymä ostetuista cd-levyistä ja omalla laitteella olevista musiikkitiedostoista verkon suoratoistopalveluiden, kuten Spotifyn käyttöön. Kun mobiililaitteiden verkkoyhteyksistä on tullut nopeampia ja luotettavampia, eivät käyttäjät vaivaudu enää kopioimaan haluamaansa musiikkia mobililaitteelleen vaan kuuntelevat musiikin usein suoraan verkosta. Musiikkitiedostoja ei tarvitse myöskään synkronoida useamman laitteen välillä.Toisinaan on kuitenkin syitä, joiden takia itselle ostetut ja omalle laitteelle ladatut musiikkitiedostot ovat parempi vaihtoehto.</description> <pubDate>Sun, 28 Oct 2018 12:30:00 +0000</pubDate></item><item> <title>Viikon VALO: Nextcloud</title> <guid isPermaLink="true">https://viikonvalo.fi/nextcloud/</guid> <link>https://viikonvalo.fi/nextcloud/</link> <description>Nextcloud on pilvipalvelualusta, jonka voi asentaa omalle palvelimelle. Omassa ylläpidossa oma data on omassa hallinnassa.Kun on tarve käyttää pilveen synkronoitavia palveluita, kuten tiedostojen, yhteystietojen ja kalenterin synkronointia useamman laitteen välillä, muttei halua luottaa tietojaan suurten palveluntarjoajien haltuun, on itse omalla palvelimella ylläpidettävä Nextcloud hyvä vaihtoehto. Näkyvimpänä ominaisuutena Nextcloudissa on tiedostojen pilvitallennus, joka vastaa esimerkiksi Dropbox-, GoogleDrive- ja OneCloud-palveluita. Sen lisäksi Nextcloud voi kuitenkin sisältää myös monia muita sovelluksia, joita siihen on mahdollista asentaa sisäänrakennetun sovellusvalikoiman kautta.</description> <pubDate>Sat, 01 Sep 2018 12:02:01 +0000</pubDate></item><item> <title>Losca: Repeated prompts for SSH key passphrase after upgrading to Ubuntu 18.04 LTS?</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31939153.post-890521543510982914</guid> <link>https://losca.blogspot.com/2018/08/repeated-prompts-for-ssh-key-passphrase.html</link> <description>This was a tricky one (for me, anyway) so posting a note to help others.<br /><br />The problem was that after upgrading to Ubuntu 18.04 LTS from 16.04 LTS, I had trouble with my SSH agent. I was always being asked for the passphrase again and again, even if I had just used the key. This wouldn't have been a showstopper otherwise, but it made using virt-manager over SSH impossible because it was asking for the passphrase tens of times.<br /><br />I didn't find anything on the web, and I didn't find any legacy software or obsolete configs to remove to fix the problem. I only got a hint when I tried <span>ssh-add -l</span>, with which I got the error message ”<i>error fetching identities: Invalid key length</i>”. This lead me on the right track, since after a while I started suspecting my old keys in .ssh that I hadn't used for years. And right on: after I removed one id_dsa (!) key and one old RSA key from .ssh directory (with GNOME's Keyring app to be exact), <span>ssh-add -l</span> started working and at the same time the familiar SSH agent behavior resumed and I was able to use my remote VMs fine too!<br /><br />Hope this helps.<br /><br /><b>ps. While at the topic, remember to upgrade your private keys' internal format to the new OpenSSH format from the ”worse than plaintext” format with the <span>-o</span> option: <a href="https://latacora.singles/2018/08/03/the-default-openssh.html">blog post</a> – tl; dr; <span>ssh-keygen -p -o -f id_rsa</span> and retype your passphrase. </b></description> <pubDate>Tue, 28 Aug 2018 07:46:00 +0000</pubDate> <author>noreply@blogger.com (TJ)</author></item><item> <title>Viikon VALO: Joplin</title> <guid isPermaLink="true">https://viikonvalo.fi/joplin/</guid> <link>https://viikonvalo.fi/joplin/</link> <description>Vapaa ojelmisto muistiinpanojen ja tehtävälistojen tekemiseen, järjestämiseen muistikirjoiksi sekä synkronoimiseen eri laitteille.Joplinissa käyttäjä voi organisoida muistiinpanonsa muistikirjoiksi, joita voi järjestellä myös sisäkkäin. Yksittäiset muistiinpanot ovat tyypiltään joko pelkkiä muistiinpanoja taikka tehtäviä.Muistiinpano on Markdown-kielellä kirjoitettu teksti. Teksti voi sisältää muun muassa: otsikoita kappaleita listoja todo-listoja, joissa lista-alkion eteen tulee rastiruutu linkkejä kuvia Tavallisten Markdown-ominaisuuksien lisäksi Joplin tukee LaTeX-muodossa kirjoitettua matematiikkaa. Muistiinpanoon voi lisäksi liittää liitetiedostoja, esimerkiksi kuvia tai muita liitteitä, sekä aihetunnisteita (tageja).</description> <pubDate>Sun, 26 Aug 2018 08:04:19 +0000</pubDate></item><item> <title>Losca: Converting an existing installation to LUKS using luksipc - 2018 notes</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31939153.post-7802255375998902821</guid> <link>https://losca.blogspot.com/2018/05/converting-existing-installation-to.html</link> <description>Time for a laptop upgrade. Encryption was still not the default for the new Dell XPS 13 Developer Edition (9370) that shipped with Ubuntu 16.04 LTS, so I followed <a href="http://losca.blogspot.fi/2015/11/converting-existing-installation-to.html">my own notes</a> from 3 years ago together with the <a href="https://www.johannes-bauer.com/linux/luksipc/">official documentation</a> to convert the unencrypted OEM Ubuntu installation to LUKS during the weekend. This only took under 1h altogether.<br /><br />On this new laptop model, EFI boot was already in use, Secure Boot was enabled and the SSD had GPT from the beginning. The only thing I wanted to change thus was the / to be encrypted.<br /><br />Some notes for 2018 to clarify what is needed and what is not needed:<br /><ul><li>Before luksipc, remember to resize existing partitions to have 10 MB of free space at the end of the / partition, and also create a new partition of eg 1 GB size partition for /boot.</li><li>To get the code and compile luksipc on Ubuntu 16.04.4 LTS live USB, just <span>apt install git build-essential</span> is needed. cryptsetup package is already installed.</li><li>After luksipc finishes and you've added your own passphrase and removed the initial key (slot 0), it's useful to <span>cryptsetup luksOpen</span> it and mount it still under the live session - however, when using ext4, the mounting fails due to a size mismatch in ext4 metadata! This is simple to correct: <span>sudo resize2fs /dev/mapper/root</span>. Nothing else is needed.</li><li>I mounted both the newly encrypted volume (to /mnt) and the new /boot volume (to /mnt2 which I created), and moved /boot/* from the former to latter.</li><li>I edited /etc/fstab of the encrypted volume to add the /boot partition</li><li>Mounted as following in /mnt:</li><ul><li><span>mount -o bind /dev dev</span></li><li><span>mount -o bind /sys sys</span></li><li><span>mount -t proc proc proc</span></li></ul><li>Then:</li><ul><li><span>chroot /mnt</span></li><li><span>mount -a</span> # (to mount /boot and /boot/efi)</li><li>Edited files /etc/crypttab (added one line: root UUID none luks) and /etc/grub/default (I copied over my overkill configuration that specifies all of cryptopts and cryptdevice some of which may be obsolete, but at least one of them and root=/dev/mapper/root is probably needed). </li><li>Ran <span>grub-install ; update-grub ; mkinitramfs -k all -c</span> (notably no other parameters were needed)<span><span style="font-family: inherit;"></span><br /></span></li><li>Rebooted.</li></ul><li>What I did not need to do:</li><ul><li>Modify anything in /etc/initramfs-tools.</li></ul></ul>If the passphrase input shows on your next boot, but your correct passphrase isn't accepted, it's likely that the initramfs wasn't properly updated yet. I first forgot to run the mkinitramfs command and faced this.<br /></description> <pubDate>Mon, 07 May 2018 11:08:00 +0000</pubDate> <author>noreply@blogger.com (TJ)</author></item><item> <title>Riku Voipio: Making sense of /proc/cpuinfo on ARM</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-997920555510565452.post-7520974196815490000</guid> <link>http://suihkulokki.blogspot.com/2018/02/making-sense-of-proccpuinfo-on-arm.html</link> <description>Ever stared at output of /proc/cpuinfo and wondered what the CPU is? <pre><br />...<br />processor : 7<br />BogoMIPS : 2.40<br />Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid<br />CPU implementer : 0x41<br />CPU architecture: 8<br />CPU variant : 0x0<br />CPU part : 0xd03<br />CPU revision : 3<br /></pre>Or maybe like: <pre><br />$ cat /proc/cpuinfo<br />processor : 0<br />model name : ARMv7 Processor rev 2 (v7l)<br />BogoMIPS : 50.00<br />Features : half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt vfpd32 lpae<br />CPU implementer : 0x56<br />CPU architecture: 7<br />CPU variant : 0x2<br />CPU part : 0x584<br />CPU revision : 2<br />...<br /></pre>The bits "CPU implementer" and "CPU part" could be mapped to human understandable strings. But the Kernel developers are heavily against the idea. Therefor, to the next idea: Parse in userspace. Turns out, there is a common tool almost everyone has installed does similar stuff. <a href="https://manpages.debian.org/unstable/util-linux/lscpu.1.en.html">lscpu(1)</a> from util-linux. So I proposed a patch to do <a href="https://github.com/karelzak/util-linux/pull/564">ID mapping</a> on arm/arm64 to util-linux, and it was accepted! So using lscpu from util-linux 2.32 (hopefully to be released soon) the above two systems look like: <pre><br />Architecture: aarch64<br />Byte Order: Little Endian<br />CPU(s): 8<br />On-line CPU(s) list: 0-7<br />Thread(s) per core: 1<br />Core(s) per socket: 4<br />Socket(s): 2<br />NUMA node(s): 1<br />Vendor ID: ARM<br />Model: 3<br />Model name: Cortex-A53<br />Stepping: r0p3<br />CPU max MHz: 1200.0000<br />CPU min MHz: 208.0000<br />BogoMIPS: 2.40<br />L1d cache: unknown size<br />L1i cache: unknown size<br />L2 cache: unknown size<br />NUMA node0 CPU(s): 0-7<br />Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid<br /></pre>And <pre><br />$ lscpu<br />Architecture: armv7l<br />Byte Order: Little Endian<br />CPU(s): 4<br />On-line CPU(s) list: 0-3<br />Thread(s) per core: 1<br />Core(s) per socket: 4<br />Socket(s): 1<br />Vendor ID: Marvell<br />Model: 2<br />Model name: PJ4B-MP<br />Stepping: 0x2<br />CPU max MHz: 1333.0000<br />CPU min MHz: 666.5000<br />BogoMIPS: 50.00<br />Flags: half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt vfpd32 lpae<br /></pre>As we can see, lscpu is quite versatile and can show more information than just what is available in cpuinfo.</description> <pubDate>Tue, 13 Feb 2018 19:18:06 +0000</pubDate> <author>noreply@blogger.com (Riku Voipio)</author></item><item> <title>Riku Voipio: Cross-compiling with debian stretch</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-997920555510565452.post-4226478412660458507</guid> <link>http://suihkulokki.blogspot.com/2017/06/cross-compiling-with-debian-stretch.html</link> <description>Debian stretch comes with cross-compiler packages for selected architectures: <pre> $ apt-cache search cross-build-essential<br />crossbuild-essential-arm64 - Informational list of cross-build-essential packages for<br />crossbuild-essential-armel - ...<br />crossbuild-essential-armhf - ...<br />crossbuild-essential-mipsel - ...<br />crossbuild-essential-powerpc - ...<br />crossbuild-essential-ppc64el - ...<br />⏎ <br /></pre> Lets have a quick exact steps guide. But first - while you can use do all this in your desktop PC rootfs, it is more wise to contain yourself. Fortunately, Debian comes with a container tool out of box: <pre><br />sudo debootstrap stretch /var/lib/container/stretch http://deb.debian.org/debian<br />echo "strech_cross" | sudo tee /var/lib/container/stretch/etc/debian_chroot<br />sudo systemd-nspawn -D /var/lib/container/stretch<br /></pre> Then we set up cross-building enviroment for arm64 inside the container: <pre><br /># Tell dpkg we can install arm64<br />dpkg --add-architecture arm64<br /># Add src line to make "apt-get source" work<br />echo "deb-src http://deb.debian.org/debian stretch main" &gt;&gt; /etc/apt/sources.list<br />apt-get update<br /># Install cross-compiler and other essential build tools<br />apt install --no-install-recommends build-essential crossbuild-essential-arm64<br /></pre> Now we have a nice build enviroment, lets choose something more complicated than the usual kernel/BusyBox to cross-build, qemu: <pre><br /># Get qemu sources from debian<br />apt-get source qemu<br />cd qemu-*<br /># New in stretch: build-dep works in unpacked source tree <br />apt-get build-dep -a arm64 .<br /># Cross-build Qemu for arm64<br />dpkg-buildpackage -aarm64 -j6 -b<br /></pre> Now that works perfectly for Qemu. For other packages, challenges may appear. For example you may have to se "nocheck" flag to skip build-time unit tests. Or some of the build-dependencies may not be multiarch-enabled. So work continues :)</description> <pubDate>Sat, 24 Jun 2017 16:03:40 +0000</pubDate> <author>noreply@blogger.com (Riku Voipio)</author></item><item> <title>Viikon VALO: ReText</title> <guid isPermaLink="true">https://viikonvalo.fi/retext/</guid> <link>https://viikonvalo.fi/retext/</link> <description>ReText on yksinkertainen, mutta tehokas, työkalu tekstien ja muistiinpanojen kirjoittamiseen Markdown-, reStructuredText- tai Textile-merkintäkielillä.Markdown, reStructuredText ja Textile ovat merkintäkieliä, joilla muotoiluja sisältäviä tekstidokumentteja voidaan kirjoittaa puhtaasti tekstimuotoisena. Valmis dokumentti käännetään yleensä näytettäväksi johonkin toiseen muotoon, kuten html- tai pdf-tiedostoiksi. Näissä kielissä muotoilut merkitään mahdollisimman luonnollisilla tavoin, jolloin myös merkintäkielinen alkuperäinen teksti pysyy helposti luettavana. Esimerkiksi luettelot merkitään rivin aloittavilla "-"-merkeillä.ReText on sovellus, jolla näillä kielillä kirjoitettujen dokumenttien muokkaaminen on helppoa.</description> <pubDate>Sun, 01 Jan 2017 14:00:00 +0000</pubDate></item><item> <title>Jouni Roivas: QGraphicsWidget</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31063096.post-4995488537144050308</guid> <link>http://osstalk.blogspot.com/2013/03/usually-its-easy-to-get-things-working.html</link> <description>Usually it's easy to get things working with Qt (<a href="http://qt-project.org">http://qt-project.org</a>), but recently I encoutered an issue when trying to implement simple component derived from QGraphicsWidget. My initial idea was to use QGraphicsItem, so I made this little class: <pre><br />class TestItem : public QGraphicsItem<br />{<br />public:<br /> TestItem(QGraphicsItem *parent=0) : QGraphicsItem(parent) {}<br /> void paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget = 0);<br /> virtual QRectF boundingRect () const;<br /><br />protected:<br /> virtual void mousePressEvent(QGraphicsSceneMouseEvent *event);<br /> virtual void mouseReleaseEvent(QGraphicsSceneMouseEvent *event);<br />};<br /><br />void TestItem::mousePressEvent(QGraphicsSceneMouseEvent *event)<br />{<br /> qDebug() &lt;&lt; __PRETTY_FUNCTION__ &lt;&lt; "press";<br />}<br /><br />void TestItem::mouseReleaseEvent(QGraphicsSceneMouseEvent *event)<br />{<br /> qDebug() &lt;&lt; __PRETTY_FUNCTION__ &lt;&lt; "release";<br />}<br /><br />void TestItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget)<br />{<br /> Q_UNUSED(option)<br /> Q_UNUSED(widget)<br /> painter-&gt;fillRect(boundingRect(), QColor(255,0,0,100));<br />}<br /><br />QRectF TestItem::boundingRect () const<br />{<br /> return QRectF(-100, -40, 100, 40);<br />}<br /></pre> Everything was working like expected, but in order to use a QGraphicsLayout, I wanted to derive that class from QGraphicsWidget. The naive way was to make minimal changes: <pre><br />class TestWid : public QGraphicsWidget<br />{<br /> Q_OBJECT<br />public:<br /> TestWid(QGraphicsItem *parent=0) : QGraphicsWidget(parent) { }<br /> void paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget = 0);<br /> virtual QRectF boundingRect () const;<br /><br />protected:<br /> virtual void mousePressEvent(QGraphicsSceneMouseEvent *event);<br /> virtual void mouseReleaseEvent(QGraphicsSceneMouseEvent *event);<br />};<br /><br />void TestWid::mousePressEvent(QGraphicsSceneMouseEvent *event)<br />{<br /> qDebug() &lt;&lt; __PRETTY_FUNCTION__ &lt;&lt; "press";<br />}<br /><br />void TestWid::mouseReleaseEvent(QGraphicsSceneMouseEvent *event)<br />{<br /> qDebug() &lt;&lt; __PRETTY_FUNCTION__ &lt;&lt; "release";<br />}<br /><br />void TestWid::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget)<br />{<br /> Q_UNUSED(option)<br /> Q_UNUSED(widget)<br /> painter-&gt;fillRect(boundingRect(), QColor(0,0,255,100));<br />}<br /><br />QRectF TestWid::boundingRect () const<br />{<br /> return QRectF(-100, -40, 100, 40);<br />}<br /></pre> <p>Pretty straightforward, isn't it? It showed and painted things like expected, but I didn't get any mouse events. Wait what? </p> <p>I spent hours just trying out things and googling this problem. I knew I had this very same issue earlier but didn't remember how I solved it. Until I figured out a very crucial thing, in case of QGraphicsWidget you must <b>NOT</b> implement boundingRect(). Instead use setGeometry for the object. </p> <p>So the needed changes was to remote the boundingRect() method, and to call setGeometry in TestWid constructor: </p> <pre>setGeometry(QRectF(-100, -40, 100, 40));</pre> <p>After these very tiny little changes I finally got everthing working. That all thing made me really frustrated. Solving this issue didn't cause good feeling, I was just feeling stupid. Sometimes programming is a great waste of time.</p></description> <pubDate>Sat, 30 Mar 2013 13:57:01 +0000</pubDate> <author>noreply@blogger.com (Jouni Roivas)</author></item><item> <title>Jouni Roivas: Adventures in Ubuntu land with Ivy Bridge</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31063096.post-7718605479664373682</guid> <link>http://osstalk.blogspot.com/2012/08/adventures-in-ubuntu-land-with-ivy.html</link> <description>Recently I got a Intel Ivy Bridge based laptop. Generally I'm quite satisfied with it. Of course installed latest Ubuntu on it. First problem was EFI boot and BIOS had no other options. Best way to work around it was to use EFI aware grub2. I wanted to keep the preinstalled Windows 7 there for couple of things, so needed dual boot.<br /><br />After digging around this German links was most relevant and helpful: <a href="http://thinkpad-forum.de/threads/123262-EFI-Grub2-Multiboot-HowTo">http://thinkpad-forum.de/threads/123262-EFI-Grub2-Multiboot-HowTo</a>. <br /><br />In the end all I needed to do was to install Grub2 to EFI boot parition (/dev/sda1 on my case) and create the grub.efi binary under that. Then just copy /boot/grub/grub.cfg under it as well. On BIOS set up new boot label to boot \EFI\grub\grub.efi <br /><br />After using the system couple of days found out random crashes. The system totally hanged. Finally traced the problem to HD4000 graphics driver: <a href="http://partiallysanedeveloper.blogspot.fi/2012/05/ivy-bridge-hd4000-linux-freeze.html">http://partiallysanedeveloper.blogspot.fi/2012/05/ivy-bridge-hd4000-linux-freeze.html</a> <br /><br />Needed to update Kernel. But which one? After multiple tries, I took the "latest" and "shiniest" one: <a href="http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/">http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/</a>. With that kernel I got almost all the functionality and stability I needed. <br /><br />However one BIG problem: headphones. I got sound normally from the speakers but after plugging in the headphones I got nothing. This problem seems to be on almost all the kernels I tried. Then I somehow figured out a important thing related to this. When I boot with headphone plugged in I got no sound from them. When I boot WITHOUT headphones plugged then they work just fine. Of course I debugged this problem all the time with the headphones plugged in and newer noticed this could be some weird detection problem. Since I kind of found solution for this I didn't bother to google it down. And of course Canonical does not provide support for unsupported kernels. If I remember correctly with the original Ubuntu 12.04 kernel this worked, but the HD4000 problem is on my scale bigger one than remember to boot without plugging anything to the 3.5" jack.... <br /><br />Of course my hopes are on 12.10 and don't want to dig it deeper, just wanted to inform you about this one.</description> <pubDate>Fri, 31 Aug 2012 19:57:17 +0000</pubDate> <author>noreply@blogger.com (Jouni Roivas)</author></item><item> <title>Ville-Pekka Vainio: SSD TRIM/discard on Fedora 17 with encypted partitions</title> <guid isPermaLink="false">http://vpv.kapsi.fi/blog/?p=147</guid> <link>https://vpv.kapsi.fi/blog/2012/07/ssd-trimdiscard-on-fedora-17-with-encypted-partitions/</link> <description><p>I have not blogged for a while, now that I am on summer holiday and got a new laptop I finally have something to blog about. I got a <a href="http://en.wikipedia.org/wiki/ThinkPad_T_Series">Thinkpad T430</a> and installed a <a href="http://www.anandtech.com/show/4863/the-samsung-ssd-830-review">Samsung SSD 830</a> myself. The 830 is not actually the best choice for a Linux user because you can only download firmware updates with a Windows tool. The tool does let you make a bootable FreeDOS USB disk with which you can apply the update, so you can use a Windows system to download the update and apply it just fine on a Linux system. The reason I got this SSD is that it is 7 mm in height and fits into the T430 without removing any spacers.</p><p>I installed Fedora 17 on the laptop and selected drive encryption in the Anaconda installer. I used ext4 and did not use LVM, I do not think it would be of much use on a laptop. After the installation I discovered that Fedora 17 does not enable SSD <a href="http://en.wikipedia.org/wiki/TRIM">TRIM</a>/discard automatically. That is probably a good default, apparently all SSDs do not support it. When you have ext4 partitions encrypted with <a href="http://en.wikipedia.org/wiki/LUKS">LUKS</a> as Anaconda does it, you need to change two files and regenerate your <a href="http://en.wikipedia.org/wiki/Initrd">initramfs</a> to enable TRIM.</p><p>First, edit your <tt>/etc/fstab</tt> and add <tt>discard</tt> to each ext4 mount. Here is an example of my root mount:<br /><code>/dev/mapper/luks-secret-id-here / ext4 defaults,discard 1 1</code></p><p>Second, edit your <tt>/etc/crypttab</tt> and add <tt>allow-discards</tt> to each line to allow the <a href="http://en.wikipedia.org/wiki/Dm-crypt">dmcrypt</a> layer to pass TRIM requests to the disk. Here is an example:<br /><code>luks-secret-id-here UUID=uuid-here none allow-discards</code></p><p>You need at least <a href="https://admin.fedoraproject.org/updates/FEDORA-2012-9847/dracut-018-78.git20120622.fc17">dracut-018-78.git20120622.fc17</a> for this to work, which you should already have on an up-to-date Fedora 17.</p><p>Third, regenerate your initramfs by doing <tt>dracut -f</tt>. You may want to take a backup of the old initramfs file in <tt>/boot</tt> but then again, real hackers do not make backups <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f609.png" alt="😉" style="height: 1em;" class="wp-smiley" /> .</p><p>Fourth, reboot and check with <tt>cryptsetup status luks-secret-id-here</tt> and <tt>mount</tt> that your file systems actually use discard now.</p><p><a href="http://www.truecrypt.org/docs/?s=trim-operation">Please note that apparently enabling TRIM on encrypted file systems may reveal unencrypted data.</a></p></description> <pubDate>Wed, 04 Jul 2012 18:14:43 +0000</pubDate></item><item> <title>Ville-Pekka Vainio: Getting Hauppauge WinTV-Nova-TD-500 working with VDR 1.6.0 and Fedora 16</title> <guid isPermaLink="false">http://vpv.kapsi.fi/blog/?p=142</guid> <link>https://vpv.kapsi.fi/blog/2011/10/hauppauge-wintv-nova-td-500-vdr-16/</link> <description><p>The <a href="http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#WinTV-NOVA-TD-500" title="Hauppauge WinTV-Nova-TD-500">Hauppauge WinTV-Nova-TD-500</a> is a nice dual tuner DVB-T PCI card (well, actually it’s a PCI-USB thing and the system sees it as a USB device). It works out-of-the-box with the upcoming Fedora 16. It needs a firmware, but that’s available by default in the linux-firmware package.</p><p>However, when using the Nova-TD-500 with <a href="http://www.tvdr.de/" title="VDR">VDR</a> a couple of settings need to be tweaked or the signal will eventually disappear for some reason. The logs (typically /var/log/messages in Fedora) will have something like this in them:<br /><tt>vdr: [pidnumber] PES packet shortened to n bytes (expected: m bytes)</tt><br />Maybe the drivers or the firmware have a bug which is only triggered by VDR. This problem can be fixed by tweaking VDR’s <a href="http://en.wikipedia.org/wiki/Electronic_program_guide" title="EPG">EPG</a> scanning settings. I’ll post the settings here in case someone is experiencing the same problems. These go into /etc/vdr/setup.conf in Fedora:</p><p><tt><br />EPGBugfixLevel = 0<br />EPGLinger = 0<br />EPGScanTimeout = 0<br /></tt></p><p>It is my understanding that these settings will disable all EPG scanning which is done in the background and VDR will only scan the EPGs of the channels on the transmitters it is currently tuned to. In Finland, most of the interesting free-to-air channels are on two transmitters and the Nova-TD-500 has two tuners, so in practice this should not cause much problems with outdated EPG data.</p></description> <pubDate>Sat, 29 Oct 2011 18:07:14 +0000</pubDate></item><item> <title>Jouni Roivas: Wayland</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31063096.post-7894039376973318483</guid> <link>http://osstalk.blogspot.com/2011/03/wayland.html</link> <description>Recently Wayland have become a hot topic. Canonical has announced that <a href="http://www.markshuttleworth.com/archives/551">Ubuntu will go to Wayland</a>. Also <a href="http://meego.com/">MeeGo</a> has <a href="http://permalink.gmane.org/gmane.comp.handhelds.meego.devel/6643">great interest</a> on it.<br /><br />Qt has had (experimental) <a href="http://qt.gitorious.org/qt/qt/trees/master/src/plugins/platforms/wayland">Wayland client</a> support for some time now.<br /><br />A very new thing is support for Qt as <a href="http://labs.qt.nokia.com/2011/03/18/multi-process-lighthouse/">Wayland server</a>. With that one can easily make own Qt based Wayland compositor. This is huge. Since this the only working Wayland compositor has been under wayland-demos. Using Qt for this opens many opportunities.<br /><br />My vision is that Wayland is the future. And the future might be there sooner than you think...</description> <pubDate>Mon, 21 Mar 2011 09:42:11 +0000</pubDate> <author>noreply@blogger.com (Jouni Roivas)</author></item><item> <title>Jouni Roivas: MeeGo status</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31063096.post-7540060911156827764</guid> <link>http://osstalk.blogspot.com/2011/02/meego-status.html</link> <description>Our CEO started a blog: <a href="http://cannedbypasi.blogspot.com/">http://cannedbypasi.blogspot.com/</a><br /><br />He wrote first entry about <a href="http://cannedbypasi.blogspot.com/2011/02/meego-qt-alive-and-kicking.html">MeeGo and Qt status</a>.<br /><br />Shortly: <a href="http://meego.com">MeeGo</a> is alive and kicking.</description> <pubDate>Thu, 24 Feb 2011 11:10:21 +0000</pubDate> <author>noreply@blogger.com (Jouni Roivas)</author></item><item> <title>Jouni Roivas: Encrypted rootfs on MeeGo 1.1 netbook</title> <guid isPermaLink="false">tag:blogger.com,1999:blog-31063096.post-7830115184477138393</guid> <link>http://osstalk.blogspot.com/2010/11/encrypted-rootfs-on-meego-11-netbook.html</link> <description>I promised my scripts to encrypt the rootfs on my Lenovo Ideapad running MeeGo 1.1. It's currently just a dirty hack but thought it could be nice to share it with you.<br /><br />My scripts uses cryptoloop. Unfortunately MeeGo 1.1 netbook stock kernel didn't support md_crypt so that was a no go. Of course I could compile the module myself but I wanted out-of-the box solution.<br /><br />Basic idea is to create custom initrd and use it. My solution needs Live USB stick to boot and do the magic. Also another USB drive is needed to get the current root filesystem in safe while encrypting the partition. I don't know if it's possible to encrypt "in place" meaning to use two loopback devices. However this is the safe solution.<br /><br />For the busy ones, just boot the MeeGo 1.1 Live USB and grab these files:<br /><pre><a href="http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/crypt_hd.sh">http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/crypt_hd.sh</a><br /><a href="http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/mkcryptrd.sh">http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/mkcryptrd.sh</a></pre><br />Then: <pre>chmod a+x crypt_hd.sh mkcryptrd.sh<br />su<br />./crypt_hd.sh</pre><br />And follow the instructions.<br /><br />The ones who have more time and want to double check everything, please follow instructions at: <a href="http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/README">http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/README</a><br /><br />This solution has at least one drawback. Once the kernel updates you have to recreate the initrd. For that purposes I created a tiny script than can be run after kernel update:<pre><a href="http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/update_initrd.sh">http://kaaos.huutonauru.net/meego/netbook_rootfs_crypt/update_initrd.sh</a></pre><br />That script also needs the mkcryptrd.sh script above.<br /><br />Of course that may break your system at any time, so be warned.<br /><br />For my Lenovo Ideapad S10-3t and MeeGo 1.1 netbook it worked fine. My test case was to make very fresh installation first from the Live/installation USB. Boot again and setup the cryptoloop from Live USB. After that I could easily boot my crypted MeeGo 1.1. It asks password in very early phase of boot process. After it's written correctly the MeeGo 1.1 system should boot up normally.<br /><br />This worked for me, and I give no guarantee that this works for you. However you're welcome to send patches and improvements.<br /><br />UPDATE 29.11.2010:<br />Some people have reported problems when they have different kernel version than on Live USB. The're unable to boot back to their system. I try to figure out solution for this issue.</description> <pubDate>Mon, 29 Nov 2010 12:48:07 +0000</pubDate> <author>noreply@blogger.com (Jouni Roivas)</author></item><item> <title>Vapaakoodi: Finhack tulee taas, tule sinäkin!</title> <guid isPermaLink="false">http://vapaakoodi.wordpress.com/?p=64</guid> <link>https://vapaakoodi.wordpress.com/2009/10/12/finhack-tulee-taas-tule-sinakin/</link> <description><div><p>Finhack on kahdesti vuodessa järjestettävä vapaa tapaaminen suomalaisille vapaaohjelmistoaktiiveille. Finhack Syksy ‘09 järjestetään tällä kertaa ensi lauantaina 17.10 Forssan Ammattikorkeakoululla (<a href="http://maps.google.com/maps?f=q&amp;source=s_q&amp;hl=fi&amp;geocode=&amp;q=Wahreeninkatu+11,+forssa&amp;sll=37.0625,-95.677068&amp;sspn=54.005807,60.732422&amp;ie=UTF8&amp;hq=Wahreeninkatu+11,&amp;hnear=Forssa,+Suomi&amp;z=16">Wahreeninkatu 11</a>). Ohjelmassa on mm. <a href="http://podcastit.tv/?q=blog/6">LinuCastin</a> nauhoitusta Henrik Anttosen johdolla, Timo Jyringin ja Niklas Laxströmin <a href="http://www.debian.org/intl/l10n/ddtp">DDTP-työpaja</a>, Hannu Mäkäräisen johdanto Freejam projektiin sekä Otto Kekäläisen tilannekatsaus Suomen vapaaohjelmistoelämään ja <a href="http://fsfe.org/">FSFE:n</a> suomen jaoston perustaminen.</p><p>Lisää tietoa ohjelmasta löydät Finhackin <a href="http://finhack.org/doku.php?id=aikataulu">kotisivuilta</a>.</p><p>Tapahtumaan on vapaa pääsy, eikä edellytä etukäteisrekisteröintiä. Kuitenkin järjestäjiä auttaisi, jos pistäisit nimesi <a href="http://finhack.org/doku.php?id=osallistujalista">osallistujalistaan</a>.</p><p>Nähdään paikanpäällä!</p><p>Terveisin,<br />Ville “Solarius” Sundell<br />Järjestäjä</p><p>PS. Tätä viestiä saa levittää vapaasti muuttamattomana, blogeissa, foorumeilla, postituslistoilla ja missä nyt ikinä keksitkään <img src="https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f642.png" alt="🙂" style="height: 1em;" class="wp-smiley" /></p></div></description> <pubDate>Mon, 12 Oct 2009 11:29:51 +0000</pubDate></item><item> <title>Vapaakoodi: Kiitä kehittäjää!</title> <guid isPermaLink="false">http://vapaakoodi.wordpress.com/?p=61</guid> <link>https://vapaakoodi.wordpress.com/2009/03/27/kiita-kehittajaa/</link> <description><p>Nyt on ensimmäinen kansainvälinen<a href="https://vapaakoodi.wordpress.com/feed/thankadev.wordpress.com"> Kiitä kehittäjääsi</a>-päivä, keitä sinä ajattelit kiittää? Itse aamuyöstä kiitin <a href="http://en.wikipedia.org/wiki/DJB">Daniel J. Bernsteiniä</a> tietoturvallisista ratkaisuista, sekä Transmission-bittorrent asiakasohjelman nykyistä kehittäjää Charles Kerriä hyvästä ohjelmasta, sekä <a href="http://users.tkk.fi/~tajyrink/">Timo Jyrinkiä</a> pitkäaikaisesta työstä suomalaisen vapaaohjelmistoyhteisön hyväksi. Tänään olisi tarkoitus lähettää vielä <a href="http://en.wikipedia.org/wiki/JWM">JWM</a>:n kehittäjälle postia, sekä luultavasti pariin muuhunkin projektiin.</p><p>Kiitä sinäkin kehittäjiä jotka ovat vaikuttaneet tietokoneen käyttöösi!</p></description> <pubDate>Fri, 27 Mar 2009 12:29:01 +0000</pubDate></item><item> <title>Vapaakoodi: Arvosta vapaiden ohjelmistojen kehittäjiä – Thank a Dev Day</title> <guid isPermaLink="false">http://vapaakoodi.wordpress.com/?p=57</guid> <link>https://vapaakoodi.wordpress.com/2009/03/07/arvosta-vapaiden-ohjelmistojen-kehittajia-thank-a-dev-day/</link> <description><p><a href="http://thankadev.wordpress.com">Thank a Dev Day</a> on päivä, jonka tarkoituksena on muistaa niitä henkilöitä, jotka ovat suosikkikoodisi takana. Tänävuonna sitä vietetään 27.3, ja tästä eteenpäin joka vuoden maaliskuun viimeinen perjantai.</p><p>Muista sinäkin sitä henkilöä, jonka koet muuttaneesi sinun tietokoneen käyttöä, tai muuten vaan saanut hyvälle mielelle!</p></description> <pubDate>Sat, 07 Mar 2009 00:57:56 +0000</pubDate></item><item> <title>Vapaakoodi: Finhack tapaaminen tulee – tule sinäkin!</title> <guid isPermaLink="false">http://vapaakoodi.wordpress.com/?p=54</guid> <link>https://vapaakoodi.wordpress.com/2008/11/22/finhack-tapaaminen-tulee-tule-sinakin/</link> <description><p>Eli, Finhack vapaaohjelmisto-tapahtuma järjestetään <strong>Lauantaina 29.11 HAMKin Forssan toimipisteellä</strong>.</p><p>Kaikki vapaista ohjelmistoista kiinnostuneet ovat tervetulleita.</p><p>Lisätietoa löytyy täältä: <a href="http://finhack.pieni.net">finhack.pieni.net</a></p></description> <pubDate>Sat, 22 Nov 2008 13:26:41 +0000</pubDate></item><item> <title>Vapaakoodi: identi.ca & laconi.ca – vapaata mikroblogausta</title> <guid isPermaLink="false">http://vapaakoodi.wordpress.com/?p=51</guid> <link>https://vapaakoodi.wordpress.com/2008/07/15/identica-laconica-vapaata-mikroblogausta/</link> <description><p><a href="http://www.identi.ca">www.identi.ca</a> on mikroblogi-sivusto, muista, kuten Twitteristä ja Jaikusta poiketen, se kuitenkin perustuu Laconica-ohjelmistoon, joka on Affero GPL:n alla.</p><p>Tästä sivustosta vinkin antoi Mirv, #vapaakoodi-kanavalla.</p></description> <pubDate>Tue, 15 Jul 2008 22:03:10 +0000</pubDate></item> </channel></rss> 
