Latest status of the testing repository [20 Aug 2018 - 17 Oct 2018]

Today landed in [testing] two new kernels:

  • linux-4.18.3
  • linux-lts-4.4.150

This is an important milestone for Chakra because from now on the kernel can be updated easily with a script and the gitlab CI instance will build them automatically. So, expect more up to date releases to stay closer to the upstream patches.

We removed nvidia-304xx because was no more compatible with the latest kernel release, but if you want to stay with the proprietary version then you can install the lts kernel alongside the nvidia 304 driver.
If you have nvidia-304xx installed then or you switch to the lts kernel or you use the nouveau driver.

Important for LTS users: after the update you have to call sudo update-grub, reboot the PC and call again sudo update-grub. Seems that the first call does not see all the partitions but after a reboot the list is correctly populated.
Please report any issues found here or on our bugtracker.

5 Likes

only nvidia-304 users?
why update-grub? why must the configuration file be rewritten? is see no reason to do it because the initramfs name haven’t changed.

Is this ok?

$ journalctl -b -p 3
aug 22 11:06:18 kepsz-pc systemd-modules-load[236]: Failed to find module 'acpi_call'
aug 22 11:06:18 kepsz-pc systemd-modules-load[236]: Failed to find module 'vhba'

acpi_call packag are installed. vhba-module also installed.

Also, i’m in at vacation, but i can not connect to my apartman’s wifi. I’m using my ThinkPad T410’s internal wifi. This laptop with win10 are able to connect and all of my other devices are able to connect to that wifi.

$ dmesg | grep failed
[    0.263126] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[    0.264011] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
[    3.521192] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads
[    3.995064] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.995070] cfg80211: failed to load regulatory.db
[    4.140169] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[    4.140215] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2

$ dmesg | grep iwlwifi
[    4.125026] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[    4.140169] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[    4.140215] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
[    4.143645] iwlwifi 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm
[    4.387229] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG enabled
[    4.387233] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[    4.387235] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[    4.387238] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6200 AGN, REV=0x74
[    4.477260] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[    4.797103] iwlwifi 0000:03:00.0: Radio type=0x1-0x3-0x1
[    5.030417] iwlwifi 0000:03:00.0: Radio type=0x1-0x3-0x1
[    5.130614] iwlwifi 0000:03:00.0: Radio type=0x1-0x3-0x1
[    5.366505] iwlwifi 0000:03:00.0: Radio type=0x1-0x3-0x1

$ iwconfig 
enp0s25   no wireless extensions.

wlp3s0    IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.

wlp0s26u1u1  IEEE 802.11  ESSID:"Telekom-412865"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: 9C:6F:52:0B:40:F3   
          Bit Rate=52 Mb/s   Tx-Power=20 dBm   
          Retry short  long limit:2   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=63/70  Signal level=-47 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1327  Invalid misc:1829   Missed beacon:0

I’m using an USB based external wifi radio, that works fine here.

@kepszlok
i would try to reinstall or recompile vhba and acpi_call

excellent point! that is necessary only for the LTS version, but looking more closely I saw now that the mkinitcpio preset is not correct, I will rebuild LTS and fix it.

1 Like

With the new Linux and acpi-call packages, there are some problem during upgrade:

See step one here:

:: Running post-transaction hooks...
( 1/11) Updating linux module dependencies...
call to execv failed (No such file or directory)
error: command failed to execute correctly
( 2/11) Install DKMS modules
( 3/11) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.18.5-1-CHAKRA
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.18.5-1-CHAKRA
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
( 4/11) Updating fontconfig cache...
( 5/11) Updating icon theme caches...
( 6/11) Reloading system manager configuration...
( 7/11) Reloading device manager configuration...
( 8/11) Arming ConditionNeedsUpdate...
( 9/11) Updating the desktop file MIME type cache...
(10/11) Updating the MIME type database...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
(11/11) Updating X fontdir indices...

And after a restart, there are still no acpi_call or vhba modules

I would say no, but I verified on my system an both are loaded correctly. Please check if you have the latest kernel and you are in sync with [testing]

This is also strange, the error is generated by depmod but I don’t know why. If you reinstall the kernel the error disapper.
Suggestion: try to reinstall linux or run sudo depmod 4.18.5-1-CHAKRA

This is the pacman hook called when running “Updating linux module dependencies…”

[Trigger]
Type = File
Operation = Install
Operation = Upgrade
Operation = Remove
Target = usr/lib/modules/4.18.5-1-CHAKRA/*
Target = usr/lib/modules/extramodules-CHAKRA/*

[Action]
Description = Updating linux module dependencies...
When = PostTransaction
Exec = /usr/bin/depmod 4.18.5-1-CHAKRA

let me know the results

Didn’t you plan to remove the -CHAKRA part from the kernel? Or has this not been implemented yet?

this is the cause from the problem: our depmod is in /sbin

[tom@frija ~]$ locate depmod
/etc/depmod.d
/etc/etc/depmod.d
/usr/lib/depmod.d
/usr/lib/depmod.d/search.conf
/usr/lib/kernel/install.d/50-depmod.install
/usr/sbin/depmod
/usr/share/man/man5/depmod.d.5.gz
/usr/share/man/man8/depmod.8.gz

@kepszlok
as work a round for now:

sudo ln -s /sbin/depmod /bin/depmod

@AlmAck
is something like this possible?

1 Like

I’m using the main server for [testing], to avoid syncing issues.

Results

Chakra install #1:
Running sudo pacman -S linux had no output. Running sudo depmod 4.18.5-1-CHAKRA had also no output. After a reboot, the vhba and acpi module errors are gone.

Chakra install #2:
Running sudo pacman -S linux had that error what i posted before. So i rebooted. Then sudo depmod 4.18.5-1-CHAKRA had no output, so that seems ok. After this reboot, the vhba and acpi module errors are gone. So in this case, depmod command fixed the problem.

Chakra install #3:
Started with linux 4.18.3, than i ran sudo pacman -Syu. When linux package got upgraded, i got the same error. After a reboot, sudo pacman -S linux did not fixed the problem. Then sudo depmod 4.18.5-1-CHAKRA fixed it.

Oh! you got it, good catch! I will fix the pkg immediately :smile:

@kepszlok the upcoming update should fix your problem too, that is strange it Chakra Install #1

Seems good here.

Btw, we shoud also deal with these warnings:
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x

$ modinfo wd719x
modinfo: ERROR: Module alias wd719x not found.
$ modinfo aic94xx
modinfo: ERROR: Module alias aic94xx not found.

Possible simple solution here:
https://gist.github.com/imrvelj/c65cd5ca7f5505a65e59204f5a3f7a6d

https://wiki.archlinux.org/index.php/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX

1 Like

This package php-7.1.22-1-x86_64.pkg.tar.xz are broken and blocks system update.

Should be fixed now, I just uploaded php-7.1.22-2

1 Like

It works now. Thanx!

Btw, mkvtoolnix packages are still problematic:

sudo pacman -S mkvtoolnix-gui
resolving dependencies…
looking for conflicting packages…

Packages (2) mkvtoolnix-cli-26.0.0-1 mkvtoolnix-gui-26.0.0-1

Total Installed Size: 24.05 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring [################################] 100%
(2/2) checking package integrity [################################] 100%
(2/2) loading package files [################################] 100%
(2/2) checking for file conflicts [################################] 100%
error: failed to commit transaction (conflicting files)
/usr/share/metainfo/org.bunkus.mkvtoolnix-gui.appdata.xml exists in both ‘mkvtoolnix-cli’ and ‘mkvtoolnix-gui’
Errors occurred, no packages were upgraded.

They shoud be merged into a single package, if you asks me.

Everything has now moved into the stable repositories.