<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=3577&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / quick note on chimaera installs (attn: fsmithred)]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=3577</link>
		<description><![CDATA[The most recent posts in quick note on chimaera installs (attn: fsmithred).]]></description>
		<lastBuildDate>Fri, 12 Jun 2020 10:43:18 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22582#p22582</link>
			<description><![CDATA[<p>Investigating the x2apic report in dmesg :-</p><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.078322] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.<br />[&#160; &#160; 0.078323] DMAR-IR: Use &#039;intremap=no_x2apic_optout&#039; to override the BIOS setting.</p></div></blockquote></div><p>I added <span class="bbc">intremap=no_x2apic_optout</span> to <span class="bbc">GRUB_CMDLINE_LINUX_DEFAULT</span><br />in <span class="bbc">/etc/default/grub</span> and ran <span class="bbc">update-grub</span>.</p><p>After a reboot, dmesg reports :-</p><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.077685] DMAR: Host address width 39<br />[&#160; &#160; 0.077687] DMAR: DRHD base: 0x000000fed90000 flags: 0x0<br />[&#160; &#160; 0.077694] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e<br />[&#160; &#160; 0.077697] DMAR: DRHD base: 0x000000fed91000 flags: 0x1<br />[&#160; &#160; 0.077702] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da<br />[&#160; &#160; 0.077705] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff<br />[&#160; &#160; 0.077707] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff<br />[&#160; &#160; 0.077711] DMAR-IR: IOAPIC id 2 under DRHD base&#160; 0xfed91000 IOMMU 1<br />[&#160; &#160; 0.077713] DMAR-IR: HPET id 0 under DRHD base 0xfed91000<br />[&#160; &#160; 0.077715] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.<br />[&#160; &#160; 0.078240] DMAR-IR: Enabled IRQ remapping in x2apic mode<br />[&#160; &#160; 0.078244] x2apic enabled<br />[&#160; &#160; 0.078251] Switched APIC routing to cluster x2apic.<br />[&#160; &#160; 0.078815] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1</p></div></blockquote></div><p>This is referred to at :-</p><p><a href="https://lkml.org/lkml/2011/7/31/201" rel="nofollow">https://lkml.org/lkml/2011/7/31/201</a></p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Fri, 12 Jun 2020 10:43:18 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22582#p22582</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22581#p22581</link>
			<description><![CDATA[<p>Looking further at the Realtek firmware.</p><p>The download link at Realtek is for the driver r8152, which we already have, rather than<br />the firmware. I found this firmware at Google Chromium :-</p><p><a href="https://chromium.googlesource.com/chromiumos/third_party/linux-firmware/+/22082765c5160df1c8a2d89cef728974cc2f8963/rtl_nic/" rel="nofollow">https://chromium.googlesource.com/chrom … 3/rtl_nic/</a></p><p>I downloaded the tgz file and unpacked it and then copied<br /><span class="bbc">rtl8153a-2.fw</span> to <span class="bbc">/lib/firmware/rtl/</span></p><p>I rebooted and now dmesg has no lines in red and reports :-</p><div class="codebox"><pre><code>dmesg|grep 8153</code></pre></div><div class="quotebox"><blockquote><div><p>[&#160; &#160; 1.990237] usb 2-3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00<br />[&#160; &#160; 3.732900] r8152 2-3:1.0: firmware: direct-loading firmware rtl_nic/rtl8153a-2.fw<br />[&#160; &#160; 3.764785] r8152 2-3:1.0: load rtl8153a-2 v1 10/23/19 successfully</p></div></blockquote></div><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Fri, 12 Jun 2020 08:44:57 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22581#p22581</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22574#p22574</link>
			<description><![CDATA[<p>I had a look at the DMAR errors and found this :-</p><p><a href="https://bugzilla.kernel.org/show_bug.cgi?id=202723" rel="nofollow">https://bugzilla.kernel.org/show_bug.cgi?id=202723</a></p><p>which suggests</p><p><span class="bbc">intel_iommu=igfx_off</span></p><p>This didn&#039;t stop the errors but</p><p><span class="bbc">intel_iommu=off</span></p><p>does now stop all of the DMAR errors in <span class="bbc">dmesg</span>.<br />I added this in <span class="bbc">/etc/default/grub</span> to</p><p><span class="bbc">GRUB_CMDLINE_LINUX_DEFAULT=&quot;earlyprintk=vga,keep net.ifnames=0 init=/sbin/openrc-init intel_iommu=off&quot;</span><br />and then ran <span class="bbc">update-grub</span>.<br />There is documentation about this at :-</p><p><a href="https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB" rel="nofollow">https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB</a></p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Thu, 11 Jun 2020 18:41:23 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22574#p22574</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22572#p22572</link>
			<description><![CDATA[<p>Booting an older kernel Linux version 4.19.0-9-amd64</p><div class="codebox"><pre><code>dmesg|grep -i firm</code></pre></div><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.276745] Spectre V2 : Enabling Restricted Speculation for firmware calls<br />[&#160; &#160; 2.259278] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x381f00)<br />[&#160; &#160; 3.568715] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode<br />[&#160; &#160; 3.570990] iwlwifi 0000:02:00.0: loaded firmware version 29.1044073957.0 op_mode iwlmvm</p></div></blockquote></div><div class="codebox"><pre><code>dmesg|grep -i DMAR</code></pre></div><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.014851] ACPI: DMAR 0x00000000DB73D600 0000A8 (v01 INTEL&#160; BDW&#160; &#160; &#160; 00000001 INTL 00000001)<br />[&#160; &#160; 0.253577] DMAR: Host address width 39<br />[&#160; &#160; 0.253579] DMAR: DRHD base: 0x000000fed90000 flags: 0x0<br />[&#160; &#160; 0.253586] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e<br />[&#160; &#160; 0.253589] DMAR: DRHD base: 0x000000fed91000 flags: 0x1<br />[&#160; &#160; 0.253594] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da<br />[&#160; &#160; 0.253598] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff<br />[&#160; &#160; 0.253600] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff<br />[&#160; &#160; 0.253604] DMAR-IR: IOAPIC id 2 under DRHD base&#160; 0xfed91000 IOMMU 1<br />[&#160; &#160; 0.253606] DMAR-IR: HPET id 0 under DRHD base 0xfed91000<br />[&#160; &#160; 0.253608] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.<br />[&#160; &#160; 0.253609] DMAR-IR: Use &#039;intremap=no_x2apic_optout&#039; to override the BIOS setting.<br />[&#160; &#160; 0.254139] DMAR-IR: Enabled IRQ remapping in xapic mode</p></div></blockquote></div><p>So it seems that several of the errors only come with the newer kernel.</p><p>Checking up on the regulatory db, I found this :-<br /><a href="https://www.linuxquestions.org/questions/linux-kernel-70/kernel-platform-regulatory-0-direct-firmware-load-for-regulatory-db-failed-with-error-2-a-4175622954/" rel="nofollow">https://www.linuxquestions.org/question … 175622954/</a></p><p><span class="bbc">crda</span> is not installed so I installed it.<br />I can now see :-</p><div class="codebox"><pre><code>v /lib/firmware/regu*</code></pre></div><div class="quotebox"><blockquote><div><p>lrwxrwxrwx 1 root root&#160; &#160;31 Jun 11 14:47 /lib/firmware/regulatory.db -&gt; /etc/alternatives/regulatory.db<br />-rw-r--r-- 1 root root 4248 Apr 12 19:28 /lib/firmware/regulatory.db-debian<br />lrwxrwxrwx 1 root root&#160; &#160;35 Jun 11 14:47 /lib/firmware/regulatory.db.p7s -&gt; /etc/alternatives/regulatory.db.p7s<br />-rw-r--r-- 1 root root 1225 Apr 12 19:28 /lib/firmware/regulatory.db.p7s-debian<br />-rw-r--r-- 1 root root 1182 Apr 12 19:28 /lib/firmware/regulatory.db.p7s-upstream<br />-rw-r--r-- 1 root root 4248 Apr 12 19:28 /lib/firmware/regulatory.db-upstream</p></div></blockquote></div><div class="codebox"><pre><code>v /etc/alternatives/regulatory.db*</code></pre></div><div class="quotebox"><blockquote><div><p>lrwxrwxrwx 1 root root 34 Jun 11 14:47 /etc/alternatives/regulatory.db -&gt; /lib/firmware/regulatory.db-debian<br />lrwxrwxrwx 1 root root 38 Jun 11 14:47 /etc/alternatives/regulatory.db.p7s -&gt; /lib/firmware/regulatory.db.p7s-debian</p></div></blockquote></div><p>after a reboot, dmesg now reports</p><div class="quotebox"><blockquote><div><p>[&#160; &#160; 3.538453] platform regulatory.0: firmware: direct-loading firmware regulatory.db<br />[&#160; &#160; 3.540418] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s</p></div></blockquote></div><p>Checking on the Realtek firmware I found this :-</p><p><a href="https://unix.stackexchange.com/questions/384403/debian-stretch-failed-to-load-firmware-rtl-nic-rtl8168g-3-fw-2" rel="nofollow">https://unix.stackexchange.com/question … 68g-3-fw-2</a></p><p>I installed <span class="bbc">firmware-realtek</span>. This seems to have installed some likely looking files,<br />although not the exact numbered one reported in the error.</p><p><a href="https://askubuntu.com/questions/898128/install-realtek-8152-or-8153-drivers-on-ubuntu-16-10" rel="nofollow">https://askubuntu.com/questions/898128/ … untu-16-10</a></p><p>suggests getting it from Realtek<br /><a href="https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-usb-3-0-software" rel="nofollow">https://www.realtek.com/en/component/zo … 0-software</a></p><p>which seems to want my email address.</p><p><a href="https://www.realtek.com/en/products/communications-network-ics/item/rtl8153" rel="nofollow">https://www.realtek.com/en/products/com … em/rtl8153</a></p><p><a href="https://www.pcsuggest.com/install-rtl8153-driver-linux/" rel="nofollow">https://www.pcsuggest.com/install-rtl8153-driver-linux/</a></p><p>suggests that the generic <span class="bbc">cdc_ether</span> driver is often used.</p><div class="codebox"><pre><code>lsmod| grep ether</code></pre></div><div class="quotebox"><blockquote><div><p>cdc_ether&#160; &#160; &#160; &#160; &#160; &#160; &#160; 24576&#160; 0<br />usbnet&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;53248&#160; 1 cdc_ether<br />usbcore&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;315392&#160; 8 xhci_hcd,usbnet,usbhid,uvcvideo,btusb,xhci_pci,cdc_ether,r8152</p></div></blockquote></div><p>which also mentions the <span class="bbc">r8152</span> module.</p><p>The wired ether seems to work ok with the error messages in dmesg.</p><p><a href="https://wiki.debian.org/Firmware" rel="nofollow">https://wiki.debian.org/Firmware</a></p><p>doesn&#039;t seem to find this driver.</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Thu, 11 Jun 2020 15:18:29 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22572#p22572</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22551#p22551</link>
			<description><![CDATA[<p>I did a fresh netinstall of Beowulf on a Xen VM (Dom0).<br />I had installed <span class="bbc">claws-mail</span>, but that was about all and<br />then upgraded it to Chimaera. This went with no problems.</p><p>So I then tried upgrading my laptop. I can&#039;t remember<br />how it got to Beowulf, but probably started with Debian<br />and migrated via Jessie, ASCII to Beowulf.</p><p>Trying to upgrade with <span class="bbc">apt</span> suggested some problems, so<br />I used <span class="bbc">aptitude</span>, which suggested a way round the incompatibilities.<br />I accepted these and let it proceed. It had almost finished but<br />ended with :-</p><div class="quotebox"><blockquote><div><p>Error: Sub-process /usr/bin/dpkg returned an error code (1)</p></div></blockquote></div><p>I ran <span class="bbc">aptitude full-upgrade</span> again and it removed <span class="bbc">fdisk</span>.<br />A further run ended without doing anything.</p><p>I then then tried to reboot, although I am running OpenRC<br />and have replaced <span class="bbc">SysV init</span> with <span class="bbc">openrc-init</span>. The reboot<br />failed to shut down, so I did <span class="bbc">sync;sync</span> and hit the power<br />button. After this it booted ok and I have since been<br />able to shutdown and to reboot ok.</p><p>I am running <span class="bbc">Postgresql</span>. This needs some action on upgrades,<br />but this failed as version 12 had failed to install! All I<br />needed to do was install postgresql v12 (I used Synaptic).<br />Then I could do the upgrade from 11 to 12 and then remove v11.</p><p>I have spotted some messages in red from <span class="bbc">dmesg</span>. These seem<br />to suggest problems with firmware. I wonder whether these<br />may be related to the new kernel. Linux version 5.6.0-2-amd64<br />Most of these messages seem to involve firmware or DMAR.</p><div class="codebox"><pre><code>dmesg | grep -i firm</code></pre></div><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.102714] Spectre V2 : Enabling Restricted Speculation for firmware calls<br />[&#160; &#160; 1.938244] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x381f00)<br />[&#160; &#160; 3.714040] platform regulatory.0: firmware: failed to load regulatory.db (-2)<br />[&#160; &#160; 3.716311] firmware_class: See <a href="https://wiki.debian.org/Firmware" rel="nofollow">https://wiki.debian.org/Firmware</a> for information about missing firmware<br />[&#160; &#160; 3.718592] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2<br />[&#160; &#160; 3.762349] r8152 2-3:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)<br />[&#160; &#160; 3.764731] r8152 2-3:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with error -2<br />[&#160; &#160; 3.766146] r8152 2-3:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)<br />[&#160; &#160; 3.844857] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode<br />[&#160; &#160; 3.847508] iwlwifi 0000:02:00.0: loaded firmware version 29.1044073957.0 7265D-29.ucode op_mode iwlmvm<br />[&#160; &#160; 4.383327] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq<br />[&#160; &#160; 4.383331] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq<br />[&#160; &#160; 4.696649] Bluetooth: hci0: Intel firmware patch completed and activated</p></div></blockquote></div><p>I guess that the regulatory.db is related to the wi-fi</p><div class="codebox"><pre><code>dmesg | grep -i DMAR</code></pre></div><div class="quotebox"><blockquote><div><p>[&#160; &#160; 0.014217] ACPI: DMAR 0x00000000DB73D600 0000A8 (v01 INTEL&#160; BDW&#160; &#160; &#160; 00000001 INTL 00000001)<br />[&#160; &#160; 0.078292] DMAR: Host address width 39<br />[&#160; &#160; 0.078294] DMAR: DRHD base: 0x000000fed90000 flags: 0x0<br />[&#160; &#160; 0.078301] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e<br />[&#160; &#160; 0.078304] DMAR: DRHD base: 0x000000fed91000 flags: 0x1<br />[&#160; &#160; 0.078309] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da<br />[&#160; &#160; 0.078312] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff<br />[&#160; &#160; 0.078315] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff<br />[&#160; &#160; 0.078318] DMAR-IR: IOAPIC id 2 under DRHD base&#160; 0xfed91000 IOMMU 1<br />[&#160; &#160; 0.078320] DMAR-IR: HPET id 0 under DRHD base 0xfed91000<br />[&#160; &#160; 0.078322] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.<br />[&#160; &#160; 0.078323] DMAR-IR: Use &#039;intremap=no_x2apic_optout&#039; to override the BIOS setting.<br />[&#160; &#160; 0.078853] DMAR-IR: Enabled IRQ remapping in xapic mode<br />[&#160; &#160; 0.363921] pci 0000:00:02.0: DMAR: Disabling IOMMU for graphics on this chipset<br />[&#160; &#160; 0.963647] DMAR: No ATSR found<br />[&#160; &#160; 0.963679] DMAR: dmar1: Using Queued invalidation<br />[&#160; &#160; 0.966059] DMAR: Intel(R) Virtualization Technology for Directed I/O<br />[&#160; &#160; 3.548242] DMAR: DRHD: handling fault status reg 3<br />[&#160; &#160; 3.550361] DMAR: [DMA Read] Request device [00:16.7] PASID ffffffff fault addr dcfff000 [fault reason 02] Present bit in context entry is clear<br />[&#160; &#160; 5.546801] DMAR: DRHD: handling fault status reg 3<br />[&#160; &#160; 5.546808] DMAR: [DMA Read] Request device [00:16.7] PASID ffffffff fault addr dcfff000 [fault reason 02] Present bit in context entry is clear<br />[&#160; &#160; 5.547152] DMAR: DRHD: handling fault status reg 3<br />[&#160; &#160; 5.547159] DMAR: [DMA Write] Request device [00:16.7] PASID ffffffff fault addr dcfff000 [fault reason 02] Present bit in context entry is clear<br />[&#160; &#160; 5.547274] DMAR: DRHD: handling fault status reg 3</p></div></blockquote></div><p>I must try booting with an older kernel to check that these<br />messages do not occur there.</p><p>I had no problems with <span class="bbc">polkit</span>.</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Wed, 10 Jun 2020 12:55:10 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22551#p22551</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22466#p22466</link>
			<description><![CDATA[<p>No problem with polkit stuff here. I now see that -backend is gone. The upgrade from fresh clean-installed beowulf seemed to take it in stride.</p><p> I wonder if it wasn&#039;t something left over from ascii... I have a beowulf that I upgraded from ascii ages ago - next time I&#039;m over there I&#039;m gonna see what polkit stuff it uses. It&#039;s so old that I can&#039;t possibly recall all the wrestling I did with it over the months when beowulf was pretty rough. Some of the workarounds for weird circular dependency dilemmas were like magic spells - had to do everything in just the right order.&#160; I have mostly used MATE for years now, probably since Debian Wheezy, so pretty much my entire experience with Devuan has been MATE.</p>]]></description>
			<author><![CDATA[dummy@example.com (sgage)]]></author>
			<pubDate>Sun, 07 Jun 2020 19:05:42 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22466#p22466</guid>
		</item>
		<item>
			<title><![CDATA[Re: quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22459#p22459</link>
			<description><![CDATA[<p>Thanks. I just finished a dist-upgrade from beowulf to chimaera on a laptop. Had some trouble with conflicts and had to remove libpolkit-backend-1-0 manually (it no longer exists) and upgrade one of the libpolkit packages manually. Also used a combination of apt and aptitude to get through it. I didn&#039;t take notes, so I don&#039;t have instructions for anyone. </p><p>This was with xfce. I think it was a refracta-ascii that I upgraded to beowulf a year ago. Now it&#039;s chimaera and seems to be working ok.</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Sun, 07 Jun 2020 17:22:43 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22459#p22459</guid>
		</item>
		<item>
			<title><![CDATA[quick note on chimaera installs (attn: fsmithred)]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=22454#p22454</link>
			<description><![CDATA[<p>Here are some notes on two recent installations of Chimaera, pretty much directed to fsmithred. I just thought this would be easier than #devuan...</p><p>Yesterday I installed your latest &#039;experimental&#039; live cd version. It went very smoothly.</p><p>I confess that openbox is a bit minimalistic for me, so I installed MATE (and slim), and the rest of my usual stuff, no problems. It&#039;s all working just fine.</p><p>One seeming omission: it seems that you didn&#039;t have any ssl certs installed -<br />hexchat complained loudly, as did a couple of other programs I use.</p><p>I did some poking around, and installed ca-certificates, ca-certificate-java, and python3-certifi - all was well.</p><p>---</p><p>Today I made a fresh install of beowulf/MATE from the netinst iso and then dist-upgraded to chimaera. All I can really say is that, again, it went very smoothly. I installed my usual programs and tweaked the look&amp;feel a bit, and it really seems quite solid - I&#039;m using it right now to post this.</p><p>---</p><p>Let me know if there are any specific things you&#039;d like me to test, and I&#039;ll try to accomodate...</p>]]></description>
			<author><![CDATA[dummy@example.com (sgage)]]></author>
			<pubDate>Sun, 07 Jun 2020 16:31:09 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=22454#p22454</guid>
		</item>
	</channel>
</rss>
