The officially official Devuan Forum!

sgage

Member

Registered: 2016-12-01

Posts: 341  

quick note on chimaera installs (attn: fsmithred)

Here are some notes on two recent installations of Chimaera, pretty much directed to fsmithred. I just thought this would be easier than #devuan...

Yesterday I installed your latest 'experimental' live cd version. It went very smoothly.

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's all working just fine.

One seeming omission: it seems that you didn't have any ssl certs installed -
hexchat complained loudly, as did a couple of other programs I use.

I did some poking around, and installed ca-certificates, ca-certificate-java, and python3-certifi - all was well.

---

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&feel a bit, and it really seems quite solid - I'm using it right now to post this.

---

Let me know if there are any specific things you'd like me to test, and I'll try to accomodate...

fsmithred

Administrator

Registered: 2016-11-25

Posts: 2,486  

Re: quick note on chimaera installs (attn: fsmithred)

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't take notes, so I don't have instructions for anyone.

This was with xfce. I think it was a refracta-ascii that I upgraded to beowulf a year ago. Now it's chimaera and seems to be working ok.

sgage

Member

Registered: 2016-12-01

Posts: 341  

Re: quick note on chimaera installs (attn: fsmithred)

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.

I wonder if it wasn't something left over from ascii... I have a beowulf that I upgraded from ascii ages ago - next time I'm over there I'm gonna see what polkit stuff it uses. It's so old that I can'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.  I have mostly used MATE for years now, probably since Debian Wheezy, so pretty much my entire experience with Devuan has been MATE.

Geoff 42

Member

Registered: 2016-12-15

Posts: 462  

Re: quick note on chimaera installs (attn: fsmithred)

I did a fresh netinstall of Beowulf on a Xen VM (Dom0).
I had installed claws-mail, but that was about all and
then upgraded it to Chimaera. This went with no problems.

So I then tried upgrading my laptop. I can't remember
how it got to Beowulf, but probably started with Debian
and migrated via Jessie, ASCII to Beowulf.

Trying to upgrade with apt suggested some problems, so
I used aptitude, which suggested a way round the incompatibilities.
I accepted these and let it proceed. It had almost finished but
ended with :-

Error: Sub-process /usr/bin/dpkg returned an error code (1)

I ran aptitude full-upgrade again and it removed fdisk.
A further run ended without doing anything.

I then then tried to reboot, although I am running OpenRC
and have replaced SysV init with openrc-init. The reboot
failed to shut down, so I did sync;sync and hit the power
button. After this it booted ok and I have since been
able to shutdown and to reboot ok.

I am running Postgresql. This needs some action on upgrades,
but this failed as version 12 had failed to install! All I
needed to do was install postgresql v12 (I used Synaptic).
Then I could do the upgrade from 11 to 12 and then remove v11.

I have spotted some messages in red from dmesg. These seem
to suggest problems with firmware. I wonder whether these
may be related to the new kernel. Linux version 5.6.0-2-amd64
Most of these messages seem to involve firmware or DMAR.

dmesg | grep -i firm

[    0.102714] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    1.938244] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x381f00)
[    3.714040] platform regulatory.0: firmware: failed to load regulatory.db (-2)
[    3.716311] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    3.718592] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.762349] r8152 2-3:1.0: firmware: failed to load rtl_nic/rtl8153a-2.fw (-2)
[    3.764731] r8152 2-3:1.0: Direct firmware load for rtl_nic/rtl8153a-2.fw failed with error -2
[    3.766146] r8152 2-3:1.0: unable to load firmware patch rtl_nic/rtl8153a-2.fw (-2)
[    3.844857] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode
[    3.847508] iwlwifi 0000:02:00.0: loaded firmware version 29.1044073957.0 7265D-29.ucode op_mode iwlmvm
[    4.383327] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[    4.383331] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[    4.696649] Bluetooth: hci0: Intel firmware patch completed and activated

I guess that the regulatory.db is related to the wi-fi

dmesg | grep -i DMAR

[    0.014217] ACPI: DMAR 0x00000000DB73D600 0000A8 (v01 INTEL  BDW      00000001 INTL 00000001)
[    0.078292] DMAR: Host address width 39
[    0.078294] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.078301] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e
[    0.078304] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.078309] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
[    0.078312] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff
[    0.078315] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff
[    0.078318] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.078320] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.078322] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.078323] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    0.078853] DMAR-IR: Enabled IRQ remapping in xapic mode
[    0.363921] pci 0000:00:02.0: DMAR: Disabling IOMMU for graphics on this chipset
[    0.963647] DMAR: No ATSR found
[    0.963679] DMAR: dmar1: Using Queued invalidation
[    0.966059] DMAR: Intel(R) Virtualization Technology for Directed I/O
[    3.548242] DMAR: DRHD: handling fault status reg 3
[    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
[    5.546801] DMAR: DRHD: handling fault status reg 3
[    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
[    5.547152] DMAR: DRHD: handling fault status reg 3
[    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
[    5.547274] DMAR: DRHD: handling fault status reg 3

I must try booting with an older kernel to check that these
messages do not occur there.

I had no problems with polkit.

Geoff

Geoff 42

Member

Registered: 2016-12-15

Posts: 462  

Re: quick note on chimaera installs (attn: fsmithred)

Booting an older kernel Linux version 4.19.0-9-amd64

dmesg|grep -i firm

[    0.276745] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    2.259278] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x381f00)
[    3.568715] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode
[    3.570990] iwlwifi 0000:02:00.0: loaded firmware version 29.1044073957.0 op_mode iwlmvm

dmesg|grep -i DMAR

[    0.014851] ACPI: DMAR 0x00000000DB73D600 0000A8 (v01 INTEL  BDW      00000001 INTL 00000001)
[    0.253577] DMAR: Host address width 39
[    0.253579] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.253586] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e
[    0.253589] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.253594] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
[    0.253598] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff
[    0.253600] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff
[    0.253604] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.253606] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.253608] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.253609] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.
[    0.254139] DMAR-IR: Enabled IRQ remapping in xapic mode

So it seems that several of the errors only come with the newer kernel.

Checking up on the regulatory db, I found this :-
https://www.linuxquestions.org/question … 175622954/

crda is not installed so I installed it.
I can now see :-

v /lib/firmware/regu*

lrwxrwxrwx 1 root root   31 Jun 11 14:47 /lib/firmware/regulatory.db -> /etc/alternatives/regulatory.db
-rw-r--r-- 1 root root 4248 Apr 12 19:28 /lib/firmware/regulatory.db-debian
lrwxrwxrwx 1 root root   35 Jun 11 14:47 /lib/firmware/regulatory.db.p7s -> /etc/alternatives/regulatory.db.p7s
-rw-r--r-- 1 root root 1225 Apr 12 19:28 /lib/firmware/regulatory.db.p7s-debian
-rw-r--r-- 1 root root 1182 Apr 12 19:28 /lib/firmware/regulatory.db.p7s-upstream
-rw-r--r-- 1 root root 4248 Apr 12 19:28 /lib/firmware/regulatory.db-upstream

v /etc/alternatives/regulatory.db*

lrwxrwxrwx 1 root root 34 Jun 11 14:47 /etc/alternatives/regulatory.db -> /lib/firmware/regulatory.db-debian
lrwxrwxrwx 1 root root 38 Jun 11 14:47 /etc/alternatives/regulatory.db.p7s -> /lib/firmware/regulatory.db.p7s-debian

after a reboot, dmesg now reports

[    3.538453] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[    3.540418] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s

Checking on the Realtek firmware I found this :-

https://unix.stackexchange.com/question … 68g-3-fw-2

I installed firmware-realtek. This seems to have installed some likely looking files,
although not the exact numbered one reported in the error.

https://askubuntu.com/questions/898128/ … untu-16-10

suggests getting it from Realtek
https://www.realtek.com/en/component/zo … 0-software

which seems to want my email address.

https://www.realtek.com/en/products/com … em/rtl8153

https://www.pcsuggest.com/install-rtl8153-driver-linux/

suggests that the generic cdc_ether driver is often used.

lsmod| grep ether

cdc_ether              24576  0
usbnet                 53248  1 cdc_ether
usbcore               315392  8 xhci_hcd,usbnet,usbhid,uvcvideo,btusb,xhci_pci,cdc_ether,r8152

which also mentions the r8152 module.

The wired ether seems to work ok with the error messages in dmesg.

https://wiki.debian.org/Firmware

doesn't seem to find this driver.

Geoff

Geoff 42

Member

Registered: 2016-12-15

Posts: 462  

Re: quick note on chimaera installs (attn: fsmithred)

I had a look at the DMAR errors and found this :-

https://bugzilla.kernel.org/show_bug.cgi?id=202723

which suggests

intel_iommu=igfx_off

This didn't stop the errors but

intel_iommu=off

does now stop all of the DMAR errors in dmesg.
I added this in /etc/default/grub to

GRUB_CMDLINE_LINUX_DEFAULT="earlyprintk=vga,keep net.ifnames=0 init=/sbin/openrc-init intel_iommu=off"
and then ran update-grub.
There is documentation about this at :-

https://wiki.gentoo.org/wiki/IOMMU_SWIOTLB

Geoff

Geoff 42

Member

Registered: 2016-12-15

Posts: 462  

Re: quick note on chimaera installs (attn: fsmithred)

Looking further at the Realtek firmware.

The download link at Realtek is for the driver r8152, which we already have, rather than
the firmware. I found this firmware at Google Chromium :-

https://chromium.googlesource.com/chrom … 3/rtl_nic/

I downloaded the tgz file and unpacked it and then copied
rtl8153a-2.fw to /lib/firmware/rtl/

I rebooted and now dmesg has no lines in red and reports :-

dmesg|grep 8153

[    1.990237] usb 2-3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[    3.732900] r8152 2-3:1.0: firmware: direct-loading firmware rtl_nic/rtl8153a-2.fw
[    3.764785] r8152 2-3:1.0: load rtl8153a-2 v1 10/23/19 successfully

Geoff

Last edited by Geoff 42 (2020-06-12 08:46:24)

Geoff 42

Member

Registered: 2016-12-15

Posts: 462  

Re: quick note on chimaera installs (attn: fsmithred)

Investigating the x2apic report in dmesg :-

[    0.078322] DMAR-IR: x2apic is disabled because BIOS sets x2apic opt out bit.
[    0.078323] DMAR-IR: Use 'intremap=no_x2apic_optout' to override the BIOS setting.

I added intremap=no_x2apic_optout to GRUB_CMDLINE_LINUX_DEFAULT
in /etc/default/grub and ran update-grub.

After a reboot, dmesg reports :-

[    0.077685] DMAR: Host address width 39
[    0.077687] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.077694] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 7e1ff0505e
[    0.077697] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.077702] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c20660462 ecap f010da
[    0.077705] DMAR: RMRR base: 0x000000dce3d000 end: 0x000000dce4bfff
[    0.077707] DMAR: RMRR base: 0x000000dd800000 end: 0x000000dfffffff
[    0.077711] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed91000 IOMMU 1
[    0.077713] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.077715] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
[    0.078240] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.078244] x2apic enabled
[    0.078251] Switched APIC routing to cluster x2apic.
[    0.078815] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1

This is referred to at :-

https://lkml.org/lkml/2011/7/31/201

Geoff