[Stable Update i686] 2018-11-25 - Quite Literally Everything™

update
stable
manjaro32

#1

Hello i686ers!

This is a pretty obscene update. Pretty much every package in the repos has been updated - there are nearly 8,000 updated packages in total. Therefore,

I recommend that you:

  1. Make a backup before performing this update
  2. Prepare a boot medium in case you need to chroot in
  3. Make absolutely certain your mirror is up to date
  4. Make sure you’re on AC power
  5. Run the update from a text console using pacman -Syu

The update set has been reported to work fine from within Pamac or Octopi but for this number of updates I really wouldn’t risk it. As @sueridgepipe observed in the x32-testing thread you’re essentially reinstalling the entire OS. Running from a text console should prevent any issues (possibly even better, from runmode 3, e.g. tag a “3” to the end of your GRUB boot line then boot direct to a text console).

As far as I, and all the other people who have tested so far, can tell, there shouldn’t be any major issues. However - I still wish you luck with this one. :slight_smile:


Anyone who would like to help out testing the upstream packages, please read the archlinux32 thread for details about how they automate their testing process and how to get involved:

https://bbs.archlinux32.org/viewtopic.php?id=171

(running this in an archlinux32 VM would be fine, there will hopefully be a way of doing this directly from within manjaro32 in the future)


Available kernels

Series Version PAE
linux316 3.16.61 No
linux318 3.18.126 No
linux44 4.4.164 No
linux49 4.9.140 No
linux414 4.14.83 No
linux419 4.19.4 Yes

archlinux32

If you find manjaro32 useful please consider donating to, or helping out with, archlinux32. It’s a small team taking on a huge project and any help will no doubt be very much appreciated.

Why aren’t the available packages/package versions the same as x86_64?

archlinux32 packages are based on Arch packages but may need editing to build correctly. Builds of less-popular packages are lower priority.

Manjaro-specific packages may lag behind x86_64 because there aren’t as many packagers. If you notice an important package is lagging please report it; at the moment it’s only me packaging for i686:

I’m only packaging current LTS kernels. Any marked as EOL are dropped. I’ll not be building the mainline kernel.

What about security updates?

I cannot guarantee timely security updates on x32-stable. If this is critical for you I recommend you switch to x32-testing or cherry-pick those packages from x32-testing or x32-unstable as they become available.

Something broke. Isn’t this meant to be stable?

“Stable” means “infrequently changing”, not “everything will work perfectly all the time”. If you want it to mean everything works, you need to help test the things you’re interested in.

What about installer images?

There’s a rapidly ageing image over here:

A new image will arrive when I find the time, which may be never. :sleeping:

What about x32-testing and x32-unstable?

These are already available, and I recommend you use x32-testing if you can to make sure testing is done.

x32-unstable should be used by anyone who wants to try and find any issues before they impact other people. If you have multiple/many machines you really should run one of those on x32-unstable.

Full list of changes

Full list of changes is available here.


Any problems?

  • No issues, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself. (Please post your solution)
  • Yes I am currently experiencing an issue due to the update. (Please post about it)

0 voters



[Testing Update i686] 2018-10-25 to 11-24 - The Pretty Much Everything™ Update
#2

Known issues and solutions

This is a wiki post; please edit as necessary.


signature from "Erich Eckner (just to sign arch packages) <arch@eckner.net>" is invalid

Update the archlinux32-keyring package first, then try the update again:

sudo pacman -Sy archlinux32-keyring
sudo pacman -Syu


#4

I’m on stable branch but when I do

pacman -Syu

The system doesn’t find any updates. pacman just report “The system is up to date” :confused:

Any help is welcome please, as I can’t get the last update :frowning:

More info:

When I do

sudo pacman-mirrors -g && sudo pacman -Syy && sudo pacman -S manjaro-keyring && sudo pacman -Syu

The system reports:

.: INFO Downloading mirrors from repo.manjaro.org
.: INFO Using default mirror file
.: INFO Querying mirrors - This may take some time
   ..... Canada         : https://osmirror.org/manjaro/
   ..... Denmark        : https://www.uex.dk/public/manjaro/
   ..... Germany        : https://mirror.alpix.eu/manjaro/
   ..... Germany        : http://mirror.ragenetwork.de/manjaro/
   ..... Germany        : https://mirror.philpot.de/manjaro/
   ..... Germany        : http://mirror.philpot.de/manjaro/
   ..... Germany        : https://manjaro.moson.eu/
   ..... Germany        : http://manjaro.moson.eu/
   ..... United_Kingdom : http://manjaro.mirrors.uk2.net/
.: INFO Writing mirror list
   Germany         : http://mirror.ragenetwork.de/manjaro/x32-stable
   Germany         : https://mirror.philpot.de/manjaro/x32-stable
   Germany         : https://manjaro.moson.eu/x32-stable
   Germany         : https://mirror.alpix.eu/manjaro/x32-stable
   Denmark         : https://www.uex.dk/public/manjaro/x32-stable
   United_Kingdom  : http://manjaro.mirrors.uk2.net/x32-stable
   Canada          : https://osmirror.org/manjaro/x32-stable
.: INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Sincronizando las bases de datos de los paquetes...
 core                     187,5 KiB   127K/s 00:01 [######################] 100%
 extra                      2,3 MiB   239K/s 00:10 [######################] 100%
advertencia: falta el archivo de bloqueo /var/lib/pacman/db.lck
 community                  5,3 MiB  1077K/s 00:05 [######################] 100%
advertencia: manjaro-keyring-20180607-1 está actualizado -- reinstalándolo
resolviendo dependencias...
buscando conflictos entre paquetes...

Paquetes (1) manjaro-keyring-20180607-1

Tamaño total de la descarga:    0,09 MiB
Tamaño total de la instalación:  0,12 MiB
Tamaño neto tras actualizar:    0,00 MiB

:: ¿Continuar con la instalación? [S/n] s
:: Obteniendo los paquetes...
 manjaro-keyring-201...    90,9 KiB   313K/s 00:00 [######################] 100%
(1/1) comprobando las claves del depósito          [######################] 100%
(1/1) verificando la integridad de los paquetes    [######################] 100%
(1/1) cargando los archivos de los paquetes        [######################] 100%
(1/1) comprobando conflictos entre archivos        [######################] 100%
:: Procesando los cambios de los paquetes...
(1/1) reinstalando manjaro-keyring                 [######################] 100%
==> Añadiendo las claves de manjaro.gpg...
==> Firmando localmente las claves de confianza en el depósito...
  -> Firmando localmente la clave 75C1B95A4D9514A57EB2DAE71817DC63CD3B5DF5...
  -> Firmando localmente la clave 16DC688DF3EECC72323954237EC47C82A42D53A2...
  -> Firmando localmente la clave 76C6E477042BFE985CC220BD9C08A255442FAFF0...
  -> Firmando localmente la clave 2D14560CDCE6A75BB186DB758238651DDF5E0594...
  -> Firmando localmente la clave B4663188A692DB1E45A98EE95BD96CC4247B52CC...
  -> Firmando localmente la clave 04BB537F5BC2D399BFA72F8F17C752B61B2F2E90...
  -> Firmando localmente la clave 35B4FF23EA9477582C2A0AF12B80869C5C0102A6...
  -> Firmando localmente la clave 77DC01C9971AC3C39A0626F72C089F09AC97B894...
  -> Firmando localmente la clave 39F0EC1AE50B37E5F3196F09DAD3B211663CA268...
  -> Firmando localmente la clave E4CDFE50A2DA85D58C8A8C70CAA6A59611C7F07E...
  -> Firmando localmente la clave 7C89F4D439B2BFACF425107B62443D89B35859F8...
  -> Firmando localmente la clave 22C903DE964E6FE321656E318DB9F8C18DF53602...
  -> Firmando localmente la clave 5A97ED6B72418199F0C22B23137C934B5DCB998E...
  -> Firmando localmente la clave 2C688B52E3FC0144B7484BABE3B3F44AC45EE0AA...
  -> Firmando localmente la clave 1E7908935AAB9A00D6B47503363DFFFD59152F77...
  -> Firmando localmente la clave 74C2F2CC05A0AB7D859839938934292D604F8BA2...
==> Importando los valores de los propietarios de confianza...
==> Desactivando las claves revocadas en el depósito...
  -> Desactivando la clave FAA6840E8C3FC7F89BEE0DC8AC7AB10BCB6CDD17...
  -> Desactivando la clave 540DE7083B89314CF70EA6F0C1B1AD0DA80EBF3E...
==> Actualizando la base de datos de claves de confianza...
gpg: siguiente comprobación de base de datos de confianza el: 2019-03-29
:: Ejecutando los «hooks» de posinstalación...
(1/1) Arming ConditionNeedsUpdate...
advertencia: falta el archivo de bloqueo /var/lib/pacman/db.lck
:: Sincronizando las bases de datos de los paquetes...
error: no se pudo obtener el archivo «core.db» desde mirror.ragenetwork.de: Resolving timed out after 10000 milliseconds
 core está actualizado
 extra está actualizado
 community está actualizado
:: Iniciando actualización completa del sistema...
...el sistema ya está actualizado.

Hope it helps to solve this problem


#5

EDIT: Seems like

pacman-mirrors -c all

Solved the problem!!! Thanks a lot forma al this hard work!!


#6
signature from "Erich Eckner (just to sign arch packages) <arch@eckner.net>" is invalid

I’ll bypass it.


#7

Ah, there’s an archlinux32-keyring update in there. Update that package first.


#8

I already updated the system, but I used --noconfirm. I should have thought of that. Thanks.


#9

SDDM crashes at boot, but then it eventually starts:

nov 25 23:16:09 manjaro sddm[703]: Display server failed to start. Exiting
nov 25 23:16:10 manjaro sddm-helper[1224]: Received a wrong opcode instead of AUTHENTICATED: 0
nov 25 23:16:10 manjaro systemd-coredump[1334]: Process 703 (sddm) of user 0 dumped core.
                                                
                                                Stack trace of thread 703:
                                                #0  0x00000000b770ad21 __kernel_vsyscall (linux-gate.so.1)
                                                #1  0x00000000b6712736 raise (libc.so.6)
                                                #2  0x00000000b66fc1e3 abort (libc.so.6)
                                                #3  0x00000000b6a8a775 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                                                #4  0x00000000004d9494 n/a (sddm)
                                                #5  0x000000000051d39b _ZN4SDDM4Seat13createDisplayEi (sddm)
                                                #6  0x000000000051d5c9 _ZN4SDDM4SeatC2ERK7QStringP7QObject (sddm)
                                                #7  0x000000000051f526 _ZN4SDDM11SeatManager10createSeatERK7QString (sddm)
                                                #8  0x00000000005202f4 n/a (sddm)
                                                #9  0x00000000b6c97744 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
                                                #10 0x000000000051e629 _ZN4SDDM10LogindSeat19canGraphicalChangedEb (sddm)
                                                #11 0x000000000051f3fc _ZN4SDDM10LogindSeat17propertiesChangedERK7QStringRK4QMapIS1_8QVariantERK11QStringList >
                                                #12 0x00000000005211bf _ZN4SDDM10LogindSeat11qt_metacallEN11QMetaObject4CallEiPPv (sddm)
                                                #13 0x00000000b763c1a5 n/a (libQt5DBus.so.5)
                                                #14 0x00000000b76466f9 n/a (libQt5DBus.so.5)
                                                #15 0x00000000b6c97e8b _ZN7QObject5eventEP6QEvent (libQt5Core.so.5)
                                                #16 0x00000000b6c6c4f2 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
                                                #17 0x00000000b6c6f81a _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.>
                                                #18 0x00000000b6c6fc29 _ZN16QCoreApplication16sendPostedEventsEP7QObjecti (libQt5Core.so.5)
                                                #19 0x00000000b6cc4064 n/a (libQt5Core.so.5)
                                                #20 0x00000000b5ad4a8e g_main_context_dispatch (libglib-2.0.so.0)
                                                #21 0x00000000b5ad6b6a n/a (libglib-2.0.so.0)
                                                #22 0x00000000b5ad6bb6 g_main_context_iteration (libglib-2.0.so.0)
                                                #23 0x00000000b6cc35cb _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (li>
                                                #24 0x00000000b6c6afa6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                #25 0x00000000b6c737db _ZN16QCoreApplication4execEv (libQt5Core.so.5)
                                                #26 0x00000000004ddb3b main (sddm)
                                                #27 0x00000000b66fda49 __libc_start_main (libc.so.6)
                                                #28 0x00000000004dde20 _start (sddm)
-- Subject: Process 703 (sddm) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 703 (sddm) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

I think this is related with Xorg:

[    14.649] (EE) RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter
[    14.663] (EE) RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter

Besides that, all seems to be working fine.

965 packages, nearly 1.8GB. Impressive! Thanks a lot for your work :wink:


#10

Well after a day of testing, I must to say that all in the new update works as expected, except the new 4.19 kernel. I was unable to start the computer after installing the 4.19 kernel. The system is even unable to reach the TTy so I can’t track the problem… fir this reason I suspect that there is some problem with the graphical driver. My computer is a Intel Core Solo 1.2GHz with 1Gb RAM and a Intel Graphics Media Accelerator 950 Graphics Card. All LTS Kernels beloow the 4.19 works as expected but not the 4.19. Would be there any solution? Thanks for your work!


#11

Did this kernel work previously? It’s the only one with PAE enabled, and if I remember correctly the Core Solo might not support PAE.


#12

The vast, vast majority of praise should go to the arch32 maintainers. I essentially curate their packages and sprinkle some Manjaro on top.


#13

No, the 4.19 kernel never worked on the Core Solo, so it might be the PAE feature. There is no option to get a 4.19 kernel without the PAE enabled? Can’t my beloved Core Solo get newest kernels? :frowning:


#14

No; I’m not building every kernel twice with different configuration. There was a demand for PAE, so that’s in 4.19 only. Any CPU which doesn’t support PAE won’t benefit from 4.19 anyway.


#15

Ok. I understand completely your decision. Anyway, thanks for your awesome work maintaining the 32 bit in Manjaro. But most of the 32bit processor and its motherboard will not support more than 3Gb (in best case). There is no reason, I think, to add this feature only for VM while leaving the real hadware without new kernels support.


#16

Update on 1 Machine and 1 VB without Problems, exept one thing:

Kernel 4.19 is not starting on my old Toshiba NB.

Looks like its the PAE thing with my Ancient Pentium 4 Mobile or the Graphics with the old Radeon 9700 Pro.

I don’t know. The System makes a Auto-Full-Reset during Boot when switching to the Login-Manager.

Kernel 4.14 works without Problems.

DK3


#17

Well, I think most of the users here using old processors will have a lot of problems using a PAE enabled kernels. Even nobody nor nothing has warmed that users of the lack of support of its processors with the new PAE feature compilation, with the only news that their machines are no booting from one day to other :frowning:

I think that maybe it would have to be reconsidered the use of a new feature (PAE) in old hardware. Most of that old hardware, in which Manjaro32 distro is focused, will be banned with no reason. To be honest, I think that non PAE kernels support would have to be maintained and included as it has been till now.


#18

Well done folks, good work.
I’m on an acer TM 290, Single Core Intel Pentium M (Centrino) running linux318 kernel with 2GB RAM. It has an Intel Corporation 82852/855GM Integrated Graphics device (i915 modules, xf86-video-intel)

Well, there are some issues still existing with linux44 (system freeze after dm-tool switch-to-greeter) or linux414 (black screen after resume from disk). Linux419 shows the same behaviour. The latter may be with configuring i915.

But well, I can live with linux318 and linux49 (had to enable GuC after this last heavy update to be able to login on vt [tty(n)]; Endless error-messages occur after entering a username:
< [drm:intel_pipe_update_end [i915]] ERROR Atomic update failure on
pipe A (start=1877089778 end=637675863) time 10 us, min 476,
max 479, scanline start 141, end 479 > )

Really new to me is an error in pamac v. 7.3.1. It cannot update the database! Couldn’t download community.files from server. The requested URL returned error: 416. Got pamac v. 7.2.0 which had been working flawless from somewhere and put it on the ignore list in pacman.conf. Tested pamac-classic too, But like the new pamac. Please update to a working version of pamac


#19

If a bug has been filed and fixed then I’ll package the new version as soon as it is released.


#20

thank you in advance


#21

For old hardware, use the 4.9 kernel (if it works,) since that kernel series will be around for some time. All kernel series get security updates and relevant bug fixes. As mentioned, the newer kernel series are important mainly for the newest hardware releases. For my recent baytrail with 32 bit UEFI, I’ve seen no advantage to 4.19 over 4.16. Well, there is one advantage - I had to build 4.16 myself. 4.19 works OOTB.

Longterm release kernels Version Maintainer Released Projected EOL
4.19 Greg Kroah-Hartman 2018-10-22 Dec, 2020
4.14 Greg Kroah-Hartman 2017-11-12 Jan, 2020
4.9 Greg Kroah-Hartman 2016-12-11 Jan, 2023
4.4 Greg Kroah-Hartman 2016-01-10 Feb, 2022
3.16 Ben Hutchings 2014-08-03 Apr, 2020