<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bert&#039;s notes &#187; Ubuntu</title>
	<atom:link href="https://a20.net/bert/tag/ubuntu/feed/" rel="self" type="application/rss+xml" />
	<link>https://a20.net/bert</link>
	<description></description>
	<lastBuildDate>Mon, 02 Nov 2020 10:47:22 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.5</generator>
	<item>
		<title>Issue with Ubuntu 16.04 cross compiler gcc-arm-linux-gnueabihf version 4:5.3.1-1ubuntu1</title>
		<link>https://a20.net/bert/2016/07/13/issue-with-ubuntu-16-04-cross-compiler-gcc-arm-linux-gnueabihf-version-45-3-1-1ubuntu1/</link>
		<comments>https://a20.net/bert/2016/07/13/issue-with-ubuntu-16-04-cross-compiler-gcc-arm-linux-gnueabihf-version-45-3-1-1ubuntu1/#comments</comments>
		<pubDate>Wed, 13 Jul 2016 08:20:32 +0000</pubDate>
		<dc:creator><![CDATA[bert]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cross compile]]></category>
		<category><![CDATA[gas]]></category>
		<category><![CDATA[gcc]]></category>
		<category><![CDATA[Linaro]]></category>
		<category><![CDATA[u-boot]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Ubuntu 16.04]]></category>
		<category><![CDATA[xenial]]></category>

		<guid isPermaLink="false">https://a20.net/bert/?p=74</guid>
		<description><![CDATA[Adding this here because Google didn&#8217;t show very obvious matches for this problem. I was trying to build a recent u-boot (for olinuxino-lime2), with the Ubuntu 16.04 supplied arm-linux-gnueabihf-as as supplied in package binutils-arm-linux-gnueabihf 2.26-8ubuntu2.1 that was installed as a dependency with apt-get install gcc-arm-linux-gnueabihf 4:5.3.1-1ubuntu1. I then got the following error: CC arch/arm/cpu/armv7/sunxi/psci.o {standard [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Adding this here because Google didn&#8217;t show very obvious matches for this problem.</p>
<p>I was trying to build a recent u-boot (for olinuxino-lime2), with the Ubuntu 16.04 supplied arm-linux-gnueabihf-as as supplied in package binutils-arm-linux-gnueabihf 2.26-8ubuntu2.1 that was installed as a dependency with apt-get install gcc-arm-linux-gnueabihf 4:5.3.1-1ubuntu1. I then got the following error:</p>
<pre>  CC      arch/arm/cpu/armv7/sunxi/psci.o
{standard input}: Assembler messages:
{standard input}:302: Error: push/pop do not support {reglist}^ -- `pop {r0,r1,r2,r3,r4,r9,ip,pc}^'
scripts/Makefile.build:280: recipe for target 'arch/arm/cpu/armv7/sunxi/psci.o' failed
make[2]: *** [arch/arm/cpu/armv7/sunxi/psci.o] Error 1
scripts/Makefile.build:425: recipe for target 'arch/arm/cpu/armv7/sunxi' failed
make[1]: *** [arch/arm/cpu/armv7/sunxi] Error 2
Makefile:1210: recipe for target 'arch/arm/cpu/armv7' failed
make: *** [arch/arm/cpu/armv7] Error 2</pre>
<p>This appears out to be due to a bug in gcc, possibly <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70830">https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70830</a>. I had better luck with Linaro&#8217;s <code>https:</code><code>//releases.linaro.org/components/toolchain/binaries/5.3-2016.02/arm-linux-gnueabihf/gcc-linaro-5.3-2016.02-x86_64_arm-linux-gnueabihf.tar.xz</code> <a title="as mentioned by Robert Nelson" href="https://eewiki.net/display/linuxonarm/A20-OLinuXino-LIME">as mentioned by Robert Nelson</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://a20.net/bert/2016/07/13/issue-with-ubuntu-16-04-cross-compiler-gcc-arm-linux-gnueabihf-version-45-3-1-1ubuntu1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ubuntu Server 14.04 installation: CD could not be mounted</title>
		<link>https://a20.net/bert/2015/10/17/ubuntu-server-14-04-installation-cd-could-not-be-mounted/</link>
		<comments>https://a20.net/bert/2015/10/17/ubuntu-server-14-04-installation-cd-could-not-be-mounted/#comments</comments>
		<pubDate>Sat, 17 Oct 2015 09:30:22 +0000</pubDate>
		<dc:creator><![CDATA[bert]]></dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[cdrom not found]]></category>
		<category><![CDATA[installation issues]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[ubuntu server]]></category>

		<guid isPermaLink="false">https://a20.net/bert/?p=45</guid>
		<description><![CDATA[This happens a lot when trying to install Ubuntu Server 14.04 from USB stick (14.04.3 still has the issue). [!! Detect and mount CD-ROM] Your installation CD-ROM couldn't be mounted. This probably means that the CD-ROM was not in the drive. If so you can insert it and try again. Retry mounting the CD-ROM? .. [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>This happens a lot when trying to install Ubuntu Server 14.04 from USB stick (14.04.3 still has the issue).</p>
<p><code>[!! Detect and mount CD-ROM]<br />
Your installation CD-ROM couldn't be mounted. This probably means that the CD-ROM was not in the drive. If so you can insert it and try again.<br />
Retry mounting the CD-ROM?</code></p>
<p>.. and of course there is no CD-ROM at all, the installation media are on the USB drive. An easy way to work around this:</p>
<ol>
<li>Open a second console with Alt-F2 (get back to the installation dialogue with Alt-F1 later)</li>
<li>Press enter to activate it</li>
<li>Enter the following command to make /cdrom a softlink to /media:<br />
<blockquote><p><code>rmdir /cdrom; ln -s media /cdrom</code></p></blockquote>
</li>
<li>Go back to the installation process with Alt-F1</li>
<li>Answer &#8216;yes&#8217; to the question <em>Retry mounting the CD-ROM?</em></li>
</ol>
<p>From here on the installation should go on as normal.</p>
]]></content:encoded>
			<wfw:commentRss>https://a20.net/bert/2015/10/17/ubuntu-server-14-04-installation-cd-could-not-be-mounted/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TRIM on Linux not supported for modern Samsung SATA drives?</title>
		<link>https://a20.net/bert/2015/07/23/discardtrim-not-getting-through-kvmlvmmdsatassd-stack/</link>
		<comments>https://a20.net/bert/2015/07/23/discardtrim-not-getting-through-kvmlvmmdsatassd-stack/#comments</comments>
		<pubDate>Thu, 23 Jul 2015 13:44:18 +0000</pubDate>
		<dc:creator><![CDATA[bert]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[14.04]]></category>
		<category><![CDATA[discard]]></category>
		<category><![CDATA[KVM]]></category>
		<category><![CDATA[LTS]]></category>
		<category><![CDATA[LVM]]></category>
		<category><![CDATA[TRIM]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[virtio]]></category>

		<guid isPermaLink="false">https://a20.net/bert/?p=10</guid>
		<description><![CDATA[Previous title: Discard/TRIM not getting through KVM/LVM/MD/SATA/SSD stack I thought my TRIMs were being blocked by the virtualization/LVM stack, but it turns out the bare device won&#8217;t be TRIMmed either. # fstrim /mnt/sde/ fstrim: /mnt/sde/: FITRIM ioctl failed: Operation not supported According to this Algolia blog article there has been an kernel bug affecting these [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Previous title: Discard/TRIM not getting through KVM/LVM/MD/SATA/SSD stack</p>
<p>I thought my TRIMs were being blocked by the virtualization/LVM stack, but it turns out the bare device won&#8217;t be TRIMmed either.</p>
<blockquote><p># fstrim /mnt/sde/<br />
fstrim: /mnt/sde/: FITRIM ioctl failed: Operation not supported</p></blockquote>
<p>According to <a href="https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/">this Algolia blog article</a> there has been an kernel bug affecting these drives (mine is a Samsung 850 PRO 1TB), so I guess it has been blacklisted for the time being.</p>
]]></content:encoded>
			<wfw:commentRss>https://a20.net/bert/2015/07/23/discardtrim-not-getting-through-kvmlvmmdsatassd-stack/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
