Installed these packages and all others associated with the desktop kernel 4.14.5 update on a 64-bit system on my HP Probook 6550b. (i3, 8GB, Intel graphics, Intel wifi) The idea was to simulate a user getting thes updates all at once.

All packages installed cleanly, and everything seems to be functioning as it should. Common apps (Firefox, GIMP, vlc) all work.

CC: (none) => andrewsfarm

After installing the new nvidia340 driver, I updated the firmware and all other appropriate packages related to the 4.14.5 server kernel update, on 64-bit and 32-bit systems on the same hardware:

ASRock motherboard, AMD Athlon X2 7750 processor, 8GB RAM, nvidia 9800GT graphics, Atheros AR9485 wifi adapter.

And, I executed the "dracut -f" command on each system.

After the reboot, both systems seemed to be running fine. No regressions noted.

Mageia 6 :: x86_64

I still do not know if these special updates (connected with the kernel 4.14.1 rollout) need to be tested on a variety of hardware so here goes.

updated iproute2 and installed the other two packages.
Not familiar with iproute but ip seems to be associated with it so gave that a run, just for getting information.  It has to be run as root.

$ sudo ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 192.168.1.156/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever

Wifi not enabled on this machine but there is an interface:
$ sudo ip link ls wlp4s0
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether c0:18:85:12:92:33 brd ff:ff:ff:ff:ff:ff

$ sudo ip link ls lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

$ sudo ip link ls enp2s0
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 18:03:73:42:40:d4 brd ff:ff:ff:ff:ff:ff
$ sudo ip addr ls enp2s0
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 18:03:73:42:40:d4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.156/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::1a03:73ff:fe42:40d4/64 scope link 
       valid_lft forever preferred_lft forever

As far as I can tell all the information is correct.

Giving iproute2 the OK for 64 bits but withholding until the situation is clarified.

CC: (none) => tarazed25

Advisory, added to svn:

type: bugfix
subject: Updated iproute2 packages adds support for kernel 4.14
src:
  6:
   core:
     - iproute2-4.14.1-1.mga6
description: |
  Updated iproute2 adds support for new features found in 4.14 series
  kernels.
references:
 - https://bugs.mageia.org/show_bug.cgi?id=22165

Keywords: (none) => advisory

Is that normal: I am still on kernel-desktop-4.9.56. when I select the new iproute from testing, no complaints on the kernel version. Should I go thru or first update the kernel??

CC: (none) => herman.viaene

(In reply to Herman Viaene from comment #5)
> Is that normal: I am still on kernel-desktop-4.9.56. when I select the new
> iproute from testing, no complaints on the kernel version. Should I go thru
> or first update the kernel??

It's ok.

Most (pretty much all) kernel related tools/utils are backward/forward compatible, so they will work with older/newer kernels ...

@Herman: re comment 5

Did you complete that test Herman - i586?

MGA6-32 on Dell Latitude D600 MATE
No installation issues
Following Len's tests above:
# ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: wlp0s29f7u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 192.168.2.6/24 brd 192.168.2.255 scope global wlp0s29f7u3
       valid_lft forever preferred_lft forever

# ip link ls lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

# ip link ls wlp0s29f7u3
3: wlp0s29f7u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000
    link/ether 80:1f:02:4a:fd:eb brd ff:ff:ff:ff:ff:ff

# ip addr ls wlp0s29f7u3
3: wlp0s29f7u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 80:1f:02:4a:fd:eb brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.6/24 brd 192.168.2.255 scope global wlp0s29f7u3
       valid_lft forever preferred_lft forever
    inet6 fe80::821f:2ff:fe4a:fdeb/64 scope link 
       valid_lft forever preferred_lft forever

All OK for me

Whiteboard: (none) => MGA6-32-OK

MGA6-64-OK from Len's test (thanks for same) and Thomas' comment 6.
Validating.

Whiteboard: MGA6-32-OK => MGA6-32-OK MGA6-64-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2017-0134.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED