update weirdness

Topic: update weirdness (Read 3184 times) previous topic - next topic

0 Members and 4 Guests are viewing this topic.

update weirdness

04 November 2017, 19:15:18

(1/8) Updating linux-lts initcpios
==> 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: 4.9.59-1-lts
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
findmnt: error while loading shared libraries: libudev.so.1: wrong ELF class: ELFCLASS32
==> ERROR: failed to detect root filesystem
findmnt: error while loading shared libraries: libudev.so.1: wrong ELF class: ELFCLASS32

Re: update weirdness

Reply #1 – 05 November 2017, 00:35:58

Re-install libeudev.

Re: update weirdness

Reply #2 – 05 November 2017, 00:44:11

Quote from: nous – on 05 November 2017, 00:35:58

Re-install libeudev.

We talked about this on IRC and it looks like reinstalling libeudev helped.

I kind of think that these post update scripts should be rerun or whole update should be rerun in order to get things to work properly or you might end with more problems.

Re: update weirdness

Reply #3 – 05 November 2017, 07:47:44

how do you redo the whole update?

Re: update weirdness

Reply #4 – 05 November 2017, 14:14:50

Quote from: mrbrklyn – on 05 November 2017, 07:47:44

how do you redo the whole update?

I don't know if there is better way.
I would check the log and manually reinstalled these packages.

Re: update weirdness

Reply #5 – 05 November 2017, 16:30:36

==> 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: 4.9.59-1-lts
-> 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: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]

Re: update weirdness

Reply #6 – 06 November 2017, 23:02:08

Quote from: mrbrklyn – on 05 November 2017, 16:30:36

==> 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: 4.9.59-1-lts
-> 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: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]

nothing to worry about its on the fallback image which wants every module loaded even if the module does not apply to your kernel as long as you never see the message on the normal build script nothing to worry about.

Re: update weirdness

Reply #7 – 07 November 2017, 02:50:57

Are you running on an old Dell GX7** ?
Because I use to have the same warnings. I looked the drivers/firmware up, installed them, and the warnings went away.

Here, read this https://sysdfree.wordpress.com/140

Re: update weirdness

Reply #8 – 07 November 2017, 07:26:51

Quote from: fungalnet – on 07 November 2017, 02:50:57

Are you running on an old Dell GX7** ?
Because I use to have the same warnings. I looked the drivers/firmware up, installed them, and the warnings went away.

Here, read this https://sysdfree.wordpress.com/140

No, it is a fit/pc and an HP Z240

Re: update weirdness

Reply #9 – 07 November 2017, 21:42:04

They keyword in those messages is "Possibly missing"
aic94xx is a sequencer from adaptec
wd719x is for a western digital SCSI card

If you don't have those 2 pieces of hardware in your computer those messages can be safely ignored.

Re: update weirdness

Reply #10 – 08 November 2017, 03:15:37

Quote

aic94xx is a sequencer from adaptec

I thought that was an old scsi card as well, perhaps an IDE based one.

Re: update weirdness

Reply #11 – 08 November 2017, 03:16:38

I'm used to updates with no warning messages

Re: update weirdness

Reply #12 – 08 November 2017, 19:42:06

If you don't want to see those messages you can install the firmware for those devices from the AUR. Those firmware will then be added to fallback initcpio image.

Re: update weirdness

Reply #13 – 09 November 2017, 02:57:58

I didn't mean that as anything other than a constructive comment, but let me ask a couple of questions with regard to this.

First, are those devices only workable with binary non-free blobs? If not, wouldn't it be best for the update to facilitate free kernel modules? Either way, wouldn't it make sense for the update to be consistant with the default system installation and for the firmware modules to be only updates if the firmware packages are loaded with pacman? It is obviously not critical, but over time these kinds of things can snowball into confusion.

Re: update weirdness

Reply #14 – 09 November 2017, 23:40:57

I wasn't trying to sound harsh if it came across that way. Was just trying to inform you as to how you can remove those warnings.

Those are not kernel modules. Those are binary firmware blobs. Also the problem isn't the update system. The warnings come from mkinitcpio which tries to add those to the fallback image. To address this problem a bug report should be filed against mkinitcpio, however these warnings have been around in arch linux for many years so I doubt they will do anything now.