You are not logged in.

Pages: 1

#1 2014-01-13 21:26:40

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

depmod error messages during linux-lts update, more after reinstalling

I just updated and during the module dependencies update of the linux-lts package (i686) the following depmod errors appeared:

>>> Updating module dependencies. Please wait ...
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/i2c/busses/i2c-piix4.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/i2c/busses/i2c-ocores.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/i2c/busses/i2c-pxa.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/comedi_test.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/serial2002.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/amplc_dio200.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/pcl812.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/rti800.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/rti802.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/das6402.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/dt2801.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/ni_at_ao.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/multiq3.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/addi_apci_2200.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/addi_apci_3501.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/adl_pci9111.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/adv_pci1724.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/contec_pci_dio.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/ni_pcimio.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/comedi/drivers/ni_mio_cs.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/rtl8187se/r8187se.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/rtl8192u/r8192u_usb.ko.gz: Invalid argument
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/vt6655/vt6655_stage.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/wlags49_h2/wlags49_h2_cs.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/wlags49_h25/wlags49_h25_cs.ko.gz: Exec format error
depmod: ERROR: failed to load symbols from /lib/modules/3.10.26-1-lts/kernel/drivers/staging/speakup/speakup.ko.gz: Exec format error

As far as I can tell the later process of building the images (normal and fallback) went on without any issues despite these.

If I try to reinstall the package the error messages change into extract errors f.e.

(Can't create '/usr/lib/modules/3.10.26-1-lts/kernel/drivers/net/ethernet/atheros/atl1e/atl1e.ko.gz')

And end up much worse,

>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 3.10.26-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `cnic'
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `cnic'
==> ERROR: module not found: `cdrom'
==> ERROR: module not found: `parport'
==> ERROR: module not found: `enclosure'
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `parport'
==> ERROR: module not found: `target_core_mod'
==> ERROR: module not found: `cxgb4'
==> ERROR: module not found: `cxgb3'
==> ERROR: module not found: `cdrom'
==> ERROR: module not found: `tifm_core'
==> ERROR: module not found: `usbcore'
==> ERROR: module not found: `tifm_core'
==> ERROR: module not found: `cb710'
==> ERROR: module not found: `rtsx_pci'
==> ERROR: module not found: `usbcore'
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `encrypted-keys'
==> ERROR: module not found: `quota_tree'
==> ERROR: module not found: `ocfs2_nodemanager'
==> ERROR: module not found: `ocfs2_dlm'
==> ERROR: module not found: `ocfs2_nodemanager'
==> ERROR: module not found: `dlm'
==> ERROR: module not found: `mtd'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `nfs_acl'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
  -> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 3.10.26-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `cnic'
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `cnic'
==> ERROR: module not found: `cdrom'
==> ERROR: module not found: `parport'
==> ERROR: module not found: `enclosure'
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: aic94xx
==> ERROR: module not found: `libfc'
==> ERROR: module not found: `parport'
==> ERROR: module not found: `target_core_mod'
==> ERROR: module not found: `cxgb4'
==> ERROR: module not found: `cxgb3'
==> ERROR: module not found: `cdrom'
==> ERROR: module not found: `tifm_core'
==> ERROR: module not found: `usbcore'
==> ERROR: module not found: `tifm_core'
==> ERROR: module not found: `cb710'
==> ERROR: module not found: `rtsx_pci'
==> ERROR: module not found: `usbcore'
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `encrypted-keys'
==> ERROR: module not found: `quota_tree'
==> ERROR: module not found: `ocfs2_nodemanager'
==> ERROR: module not found: `ocfs2_dlm'
==> ERROR: module not found: `ocfs2_nodemanager'
==> ERROR: module not found: `dlm'
==> ERROR: module not found: `mtd'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `nfs_acl'
==> ERROR: module not found: `fscache'
==> ERROR: module not found: `fscache'
  -> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
==> ERROR: module not found: `i2c-core'
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

Any hint on what is happening here? Fortunately I am using lts as backup kernel though others may not be that lucky if they encounter the same issue(s).

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#2 2014-01-13 23:13:08

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

After rebooting due to the new kernel update I encountered the (expected?) inconsistencies notificitation due to the LTS kernel. Once they were fixed I rebooted again and now find myself stuck in X using links.
The error message I receive from X is the following,

/usr/bin/X: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory

As far as I have seen in the forums there has been a problem with the libgcrypt package not updating for them. But in my case it did without any error messages :-?
I will try to reinstall and see if that fixes the problem...

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#3 2014-01-13 23:21:12

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,598
Website

Re: depmod error messages during linux-lts update, more after reinstalling

Try a more up-to-date mirror.  I recommend using reflector to find one.  See my "upp" alias for syntax (.zshrc in my sig).

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

Offline

#4 2014-01-13 23:47:09

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

graysky wrote:

Try a more up-to-date mirror.  I recommend using reflector to find one.  See my "upp" alias for syntax (.zshrc in my sig).

As far as I can tell, taking a look at the mirror status site, the mirrors I am using are up to date (using the .us/.de leaseweb ones). The .us one "scores" top1 right now. Even changing the .de one (which is good) to a "better" .pl mirror does not seem to change anything in terms of telling me about new updates.
Therefore I don't think that, as I have mentioned in a previous reply to this thread, I am lacking f.e. the libgcrypt package everyone else had problems upgrading.
When running pacman -Qi libgcrypt it tells me that I have indeed libgcrypt 1.6.0-1 .

So far I have generated again the linux-lts kernel (no errors this time) and also the main one.

Maybe as X (using 1.12.4-1) is the one complaining about the new libgcrypt I should try to reinstall that one too?

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#5 2014-01-14 08:53:24

rubenvb
Member
Registered: 2011-01-14
Posts: 99

Re: depmod error messages during linux-lts update, more after reinstalling

I ran into this today (the cannot find libgcrypt error), and for certainty I reinstalled linux-lts after the big update, and the second mkinitcpio didn't give these errors.

I believe this may be due to systemd being updated simultenaously with libgcrypt, with linux-lts being squeezed in the middle:

[...]
Packages (30): cryptsetup-1.6.3-2  dirmngr-1.1.1-2  ffmpeg-1:2.1.2-1  gdbm-1.11-1  gettext-0.18.3.2-1       
               gnupg-2.0.22-2  iproute2-3.12.0-1  iptables-1.4.21-1  libgcrypt-1.6.0-1  libquvi-0.9.4-2     
               libsecret-0.16-2  libwbclient-4.1.4-1  libxshmfence-1.1-1  libxslt-1.1.28-3  libzip-0.11.2-1 
               linux-lts-3.10.26-1  linux-lts-headers-3.10.26-1  man-pages-3.56-1  perl-5.18.2-2            
               pth-2.0.7-5  rasqal-1:0.9.30-4  smbclient-4.1.4-1  systemd-208-10                            
               virtualbox-guest-modules-lts-4.3.6-3  virtualbox-guest-utils-4.3.6-3  vlc-2.1.2-2            
               xextproto-7.3.0-1  xf86-input-evdev-2.8.2-2  xorg-server-1.15.0-5                            
               xorg-server-common-1.15.0-5  
[...]
( 1/30) upgrade bezig libgcrypt                                  [####################################] 100%
[...]
(16/30) upgrade bezig linux-lts                                  [####################################] 100%
[...]
==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl' 
[...]
(22/30) upgrade bezig systemd                                    [####################################] 100%
[...]

Running "pacman -S linux-lts" again after this upgrade built the images without errors.

But this is just my intuition. If it's right, there may be something wrong with the install order in this kind of upgrade. Is it something Pacman should be able to handle?

Last edited by rubenvb (2014-01-14 08:54:07)

Offline

#6 2014-01-14 19:47:47

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

@rubenvb

Do you refer to the exact same libgcrypt error in relation to the version I have quoted in #2?
I ask because as far as I have been testing the error of libgcrypt.so.11 is related to xorg-server version 1.12.4-1. The latter does still rely on the previous version of libgcrypt and, as it is not up to date, therefore does not start X.
Once I upgrade xorg-server to the latest package(s) it loads the X again.
This seems to be the finishing blow to those who, as myself, were still using the 1.12.4-1 xorg-server package (and related dependencies) to take full advantage of their old graphic cards. Now this seems to be not possible anymore unless libgcrypt and systemd (kernels even?) are downgraded/frozen too. Being core system packages (especially systemd?) it does not seem wise to do so in terms of a rolling release.

Regarding pacman being supposed to handle this kind of situations it seems that, on the basis of a moderator comment, this should merely be considered a 'glitch' (aka 'shit happens'?).

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#7 2014-01-14 19:49:17

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,574

Re: depmod error messages during linux-lts update, more after reinstalling

You can always rebuild xorg 1.12.4 against the new libgcrypt. It won't be done for you, though; this is exactly why partial updates are not supported. It's not a glitch, it's the way things are designed to work.

@rubenvb, what package called systemctl? You cut out too much info. Off the top of my head, I can't think of anything that would use systemctl in it's install scripts.

Last edited by Scimmia (2014-01-14 19:57:10)

Offline

#8 2014-01-14 20:38:11

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

@Scimmia

That rebuilding option sounds interesting indeed (especially taking into account the other issues I have encountered once I have upgraded to the up-to-date xorg files). I am aware that it won't be done for me but I would really appreciate if you could point me in the right direction. Thanks in advance.

Regarding the 'glitch' issue I doubt I am the right one to say if it was/is or not as it was not me who called it that way wink

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#9 2014-01-15 14:17:47

rubenvb
Member
Registered: 2011-01-14
Posts: 99

Re: depmod error messages during linux-lts update, more after reinstalling

@root: Sorry for kind of hijacking your thread, but it seems like our issues are related. It is the same libgcrypt version, but I'm getting a similar error by just upgrading linux-lts, systemd, and libgcrypt at the same time. Oh, and you should know better than use ancient versions of X11 in Arch ;-)

@scimmia: here is the full pacman.log snippet, including the original "pacman -Syu" and the followup "pacman -S linux-lts". It is the linux-lts mkinitcpio [systemd] hook that complains about unsatisfied dependencies, nothing "calls" systemctl:

[2014-01-13 17:05] [PACMAN] Running 'pacman -Syu'
[2014-01-13 17:05] [PACMAN] synchronizing package lists
[2014-01-13 17:05] [PACMAN] starting full system upgrade
[2014-01-13 17:06] [PACMAN] upgraded libgcrypt (1.5.3-1 -> 1.6.0-1)
[2014-01-13 17:06] [PACMAN] upgraded cryptsetup (1.6.3-1 -> 1.6.3-2)
[2014-01-13 17:06] [PACMAN] upgraded pth (2.0.7-4 -> 2.0.7-5)
[2014-01-13 17:06] [PACMAN] upgraded dirmngr (1.1.1-1 -> 1.1.1-2)
[2014-01-13 17:06] [PACMAN] upgraded ffmpeg (1:2.1.1-3 -> 1:2.1.2-1)
[2014-01-13 17:06] [PACMAN] upgraded gdbm (1.10-3 -> 1.11-1)
[2014-01-13 17:06] [PACMAN] upgraded gettext (0.18.3.1-2 -> 0.18.3.2-1)
[2014-01-13 17:06] [PACMAN] upgraded gnupg (2.0.22-1 -> 2.0.22-2)
[2014-01-13 17:06] [PACMAN] upgraded iptables (1.4.20-1 -> 1.4.21-1)
[2014-01-13 17:06] [PACMAN] upgraded iproute2 (3.11.0-1 -> 3.12.0-1)
[2014-01-13 17:06] [PACMAN] upgraded libquvi (0.9.4-1 -> 0.9.4-2)
[2014-01-13 17:06] [PACMAN] upgraded libsecret (0.16-1 -> 0.16-2)
[2014-01-13 17:06] [PACMAN] upgraded libwbclient (4.1.3-1 -> 4.1.4-1)
[2014-01-13 17:06] [PACMAN] upgraded libxslt (1.1.28-2 -> 1.1.28-3)
[2014-01-13 17:06] [PACMAN] upgraded libzip (0.11.1-2 -> 0.11.2-1)
[2014-01-13 17:06] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-01-13 17:06] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Starting build: 3.10.26-1-lts
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/lib/systemd/systemd-journald'
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Starting build: 3.10.26-1-lts
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/bin/systemctl'
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> ERROR: binary dependency `libgcrypt.so.11' not found for `/usr/lib/systemd/systemd-journald'
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-01-13 17:06] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
[2014-01-13 17:06] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-13 17:06] [PACMAN] upgraded linux-lts (3.10.25-1 -> 3.10.26-1)
[2014-01-13 17:06] [PACMAN] upgraded linux-lts-headers (3.10.25-1 -> 3.10.26-1)
[2014-01-13 17:06] [PACMAN] upgraded man-pages (3.55-1 -> 3.56-1)
[2014-01-13 17:06] [PACMAN] upgraded perl (5.18.1-1 -> 5.18.2-2)
[2014-01-13 17:06] [PACMAN] upgraded rasqal (1:0.9.30-3 -> 1:0.9.30-4)
[2014-01-13 17:06] [PACMAN] upgraded smbclient (4.1.3-1 -> 4.1.4-1)
[2014-01-13 17:06] [PACMAN] upgraded systemd (208-3 -> 208-10)
[2014-01-13 17:06] [PACMAN] upgraded virtualbox-guest-modules-lts (4.3.6-2 -> 4.3.6-3)
[2014-01-13 17:06] [PACMAN] upgraded xorg-server-common (1.14.5-2 -> 1.15.0-5)
[2014-01-13 17:06] [PACMAN] upgraded xf86-input-evdev (2.8.2-1 -> 2.8.2-2)
[2014-01-13 17:06] [PACMAN] installed libxshmfence (1.1-1)
[2014-01-13 17:06] [PACMAN] upgraded xorg-server (1.14.5-2 -> 1.15.0-5)
[2014-01-13 17:06] [PACMAN] upgraded virtualbox-guest-utils (4.3.6-2 -> 4.3.6-3)
[2014-01-13 17:06] [PACMAN] upgraded vlc (2.1.2-1 -> 2.1.2-2)
[2014-01-13 17:06] [PACMAN] upgraded xextproto (7.2.1-1 -> 7.3.0-1)
[2014-01-13 17:07] [PACMAN] Running 'pacman -S linux-lts'
[2014-01-13 17:07] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-01-13 17:07] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.26-1-lts
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Starting build: 3.10.26-1-lts
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [systemd]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-01-13 17:07] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
[2014-01-13 17:07] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-01-13 17:07] [PACMAN] reinstalled linux-lts (3.10.26-1)

Last edited by rubenvb (2014-01-15 14:19:48)

Offline

#10 2014-01-15 17:12:57

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,574

Re: depmod error messages during linux-lts update, more after reinstalling

@rubenvb, ah, ok, you're using the systemd hook in your initramfs. The error makes sense now, and you handled it exactly the right way. This isn't something that that pacman should handle by itself, but something there's usually an announcement about. Honestly, though, if people ignore the output of pacman, it's their own fault.

@root, the glitch was that there was a 20 minute period where all of the packages that used the new libgcrypt were moved to core/extra, but the actual libgcrypt package was still in testing. Someone made a mistake, it happens to everyone. I don't believe that glitch caused the problems either you or rubenvb are seeing, though.

Offline

#11 2014-01-22 20:31:17

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

@rubenvb

No complaints on my behalf. And if they are related I presume even the mod staff appreciates the 'issue grouping' in one single thread. I would indeed.
Regarding the use of an 'ancient' version of X, it is the one that still has XAA support so, despite "popular belief", it does actually make a difference when using/taking advantage of older cards.

As far as I am concerned the systemd hook might still 'refer' to the old libgcrypt version just like the old X version does...

@Scimmia

I just wanted to draw your attention on the fact that if you did not agree on the 'glitch' term (which you did in the end apparently tongue) you would have to start disagreeing with the user/mod that used it in the first place as I just borrowed it wink
Thus there was no pointing of (accusing) finger, neither intended nor unintended, to anyone.

By the way, the 'building against' procedure (there was even a new libgcrypt update some days back), would it be using ABS?
I have checked the wiki and there is no reference to 'building against' anything.
Or would it be better to ask for guidance/support in the 'Creating & Modifying Packages' forum?

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#12 2014-01-22 21:33:52

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,574

Re: depmod error messages during linux-lts update, more after reinstalling

To build it against the new libs, you would just build it on a system with those libs installed. The dynamic linker will point it to the new versions and everything works (or atleast should work).

Yes, the ABS is one way of doing that. I think using SVN directly is better, because you can get the old version of the PKGBUILD that way.

https://www.archlinux.org/svn/
https://wiki.archlinux.org/index.php?ti … S_From_SVN

Last edited by Scimmia (2014-01-22 21:35:28)

Offline

#13 2014-01-31 22:45:09

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

Yes, I am indeed looking to (re)built an earlier version.

I finally managed to grab the old PKGBUILD (thanks for the helpful links) doing the following (yes, I am writing down a roadmap for myself and anyone else interested in doing the same when encountering this problem just as I have done in the past):

1st step - install subversion which is needed to grab the old PKGBUILD

2nd step - do the non-recursive checkout for, among others, extra

3rd step - check out the related package (I jumped directly to checking out an older version but it returned an error - not sure if intended to be that way; nevertheless doing this prior to the log one works just fine)

cd packages
svn update xorg-server

4th step - Checking out the older version (1.12.4)

cd packages
svn log xorg-server > xorg-server.log

* I used > xorg-server.log (not listed in the wiki) in order to have a local log file which is much easier to handle than looking up the console/terminal used (especially if the text ends up cut f.e. in my urxvtc)

5th step - Search the log file for the right revision (when the trunk is moved to the extra repo) and download it (replaces the (current) one download in the 3rd step)

svn update -r165604 xorg-server

6th step - After downloading the PKGBUILD file access the folder where it is stored (in my case the file I am interested in is in repos/extra-i686) and build the package using 

makepkg -s

After some time (if I remember correctly it didn't take long on this PIII) the packages will be available in the same folder where the PKGBUILD was downloaded.

7th step - Once the new xorg-server package is created it is time to install it (in multi-user, check wiki) together with the following packages:

xorg-server-common (is build in the same process along with the xorg-server one)
xf86-input-evdev (2.7.3-1)
xf86-video-savage (2.3.6-1)
savage-dri (currently used: 7.11.2-5)*

*According to my tests without this package even if all related to X appears to run as it should one may end up with a black screen (and the setup hardlocked).

Last edited by root (2014-02-08 01:18:52)

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

#14 2014-02-01 04:43:12

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,574

Re: depmod error messages during linux-lts update, more after reinstalling

The linker is part of the build process, don't worry about that. Just build the package as normal and it will link against the new libs. You will have to rebuild it each time there is a soname bump in a lib it's linked to, but luckily xorg isn't linked to that many external libs.

Offline

#15 2014-02-07 22:43:26

root
Member
From: 127.0.0.1
Registered: 2012-04-13
Posts: 297

Re: depmod error messages during linux-lts update, more after reinstalling

I have updated my previous reply with the following steps I was able to achieve but I didn't go far.
After successfully building the packages (I received some repetitive warnings about QWindow or something similar during the process but I guess it was nothing 'serious' as there was no error notification once the process finished) I rebooted into multi-user in order to install them.

The thing is that after doing so and rebooting I end up having a black screen, the backlight appears to be on though. In the same way it seems the laptop ends up locked as I can't access any console to shut down X.

I have checked the Xorg logs, journalctl and boot process and nothing unusual appears there hinting what may be causing this behaviour.

Is it possible that besides the Xorg package I would have to rebuild the related (default) savage driver too as it may not work well if at all with the new rebuild Xorg package?

I tried to rebuild the savage driver too but it didn't help at all. It wasn't event recognized as a valid driver and an ABI version error appeared too.

Still it seems that in the end I have been succesful. I am not sure why but it seems that the savage-dri package has "changed" from optional to mandatory in this case as after installing it my login manager succesfully appeared.
I haven't been using it in my previous savage driver install before the Xorg upgrade thus I haven't tried it before. This time I did it out of curiosity after seen a related error in the Xorg log. As said, that error has appeared in the past but never was fatal.
I will try now again removing the package (not fond of crashing my setup but it is the only way to get the confirmation) and update my previous post accordingly depending on the result.

Confirmed, without the savage-dri package the black screen appears and setup locks. Now I just need to find out the lib files that are related to Xorg and may lead to the necessary rebuild. I check the package page but it is quite confusing...

Last edited by root (2014-02-08 01:21:00)

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

Offline

Pages: 1

Board footer

Powered by FluxBB