[Gelöst] Core 128 - PAE-Kernel wurde nicht installiert

Post Reply
User avatar
FischerM
Community Developer
Community Developer
Posts: 942
Joined: November 2nd, 2011, 12:28 pm

[Gelöst] Core 128 - PAE-Kernel wurde nicht installiert

Post by FischerM » March 14th, 2019, 9:04 pm

Ahmt,

das Update von Core 127 nach Core 128 (32bit) lief laut Pakfire fehlerfrei, aber:

Es gab einen "Schluckauf":

Code: Select all

...
20:50:05	pakfire:	MIRROR INFO: 21 servers found in list
20:50:05	pakfire:	DOWNLOAD INFO: Host: mirror.ueb.edu.ec (HTTPS) - File: ipfire/pakfire2/2.21/pak s/core-upgrade-2.21-128.ipfire
20:50:06	pakfire:	DOWNLOAD INFO: ipfire/pakfire2/2.21/paks/core-upgrade-2.21-128.ipfire has size of 54385517 bytes
20:50:58	pakfire:	DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
20:50:58	pakfire:	DOWNLOAD INFO: File received. Start checking signature...
20:50:59	pakfire:	DOWNLOAD ERROR: The downloaded file (ipfire/pakfire2/2.21/paks/core-upgrade-2.2 1-128.ipfire) wasn't verified by IPFire.org. Sorry - Exiting...
20:50:59	pakfire:	TIME INFO: Time Server 193.175.73.151 has -0.093144 sec offset to localtime.
...
Beim zweiten Versuch lief das Update dann fehlerfrei durch, es wurden keine weiteren Probleme angezeigt:

Code: Select all

...
20:53:41	pakfire:	DOWNLOAD INFO: Host: mirror.uce.edu.ec (HTTPS) - File: ipfire/pakfire2/2.21/pak s/core-upgrade-2.21-128.ipfire
20:53:42	pakfire:	DOWNLOAD INFO: ipfire/pakfire2/2.21/paks/core-upgrade-2.21-128.ipfire has size of 54385517 bytes
20:53:52	pakfire:	DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
20:53:52	pakfire:	DOWNLOAD INFO: File received. Start checking signature...
20:53:54	pakfire:	DOWNLOAD INFO: Signature of core-upgrade-2.21-128.ipfire is fine.
20:53:55	pakfire:	DOWNLOAD FINISHED: ipfire/pakfire2/2.21/paks/core-upgrade-2.21-128.ipfire
...
20:54:43	pakfire:	PAKFIRE UPGR: We are going to install all packages listed above.
20:54:43	pakfire:	PAKFIRE UPGR: linux-pae: Decrypting...
20:54:43	pakfire:	CLEANUP: tmp
20:54:43	pakfire:	DECRYPT STARTED: linux-pae
20:54:46	pakfire:	DECRYPT FINISHED: linux-pae - Status: 0
20:54:46	pakfire:	PAKFIRE UPGR: linux-pae: Upgrading files and running post-upgrading scripts...
...
Nach dem - problemlosen - Neustart läuft die Duo Box jetzt aber auf einmal mit der SMP-Kernel-Version von Core 128:

Linux ipfire.localdomain 4.14.103-ipfire #1 SMP

Vorher lief, mit Core 127, der PAE-Kernel.

In /boot liegen jetzt nach dem Update der alte PAE- und der neue SMP-Kernel:

Code: Select all

root@ipfire: /boot # ls -l
total 41396
-rw-r--r-- 1 root root   163089 Feb 23 21:39 config-4.14.103-ipfire
-rw-r--r-- 1 root root   162728 Dec 10 15:28 config-4.14.86-ipfire-pae
drwxr-xr-x 5 root root     4096 Mar 14 20:54 grub
-rw-r--r-- 1 root root 12519064 Feb 23 21:41 initramfs-4.14.103-ipfire.img
-rw-r--r-- 1 root root 14209780 Mar 14 20:55 initramfs-4.14.86-ipfire-pae.img
drwx------ 2 root root    16384 Mar  9  2016 lost+found
-rw-r--r-- 1 root root  2686423 Feb 23 21:39 System.map-4.14.103-ipfire
-rw-r--r-- 1 root root  2729728 Dec 10 15:28 System.map-4.14.86-ipfire-pae
-rw-r--r-- 1 root root  4914528 Feb 23 21:39 vmlinuz-4.14.103-ipfire
-rw-r--r-- 1 root root  4964704 Dec 10 15:28 vmlinuz-4.14.86-ipfire-pae
df -u sagt mir:

Code: Select all

root@ipfire: /boot # df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.4G  4.0K  1.4G   1% /dev
tmpfs           1.4G   12K  1.4G   1% /dev/shm
tmpfs           1.4G  576K  1.4G   1% /run
/dev/sda3       2.0G  1.1G  771M  58% /
/dev/sda1        59M   46M  9.3M  83% /boot
/dev/sda4        27G  921M   25G   4% /var
/var/lock       8.0M   12K  8.0M   1% /var/lock
none            1.4G   24K  1.4G   1% /var/log/vnstat
none            1.4G   28M  1.4G   3% /var/log/rrd
War da zu wenig Platz oder was hat da eventuell nicht geklappt? Es wurden keinerlei Fehler ausgegeben!
Lt. der PakFire-Addonliste ist 'linux-pae' installiert, dass bezieht sich aber anscheinend auf die vorherige Version.

Was könnte ich tun - außer einer Neuinstallation ;) - um den PAE-Kernel zu installieren?

Meine Überlegung: per Pakfire das "Addon" linux-pae zunächst deinstallieren und per Pakfire-GUI nochmal installieren. Wäre das eine gangbare Lösung?

Viele Grüße,
Matthias

User avatar
Roberto Peña
Posts: 730
Joined: July 16th, 2014, 3:56 pm
Location: Bilbao (España)
Contact:

Re: Core 128 - PAE-Kernel wurde nicht installiert

Post by Roberto Peña » March 15th, 2019, 6:55 am

Good morning FischerM.

This means that you change from PAE to SMP?.

According to this table:
Flavors.jpg
Is not this change a regression?

The 32-bit IPFire will no longer support more than 4Gb of ram. It is not like this?.

I speak from ignorance.

Greetings.
Image
Image

╔════════════════════════════════════════════════╗
Donate to improve IPFire: https://www.ipfire.org/donate
╚════════════════════════════════════════════════╝

User avatar
FischerM
Community Developer
Community Developer
Posts: 942
Joined: November 2nd, 2011, 12:28 pm

Re: Core 128 - PAE-Kernel wurde nicht installiert

Post by FischerM » March 15th, 2019, 9:37 am

Hi,
Roberto Peña wrote:This means that you change from PAE to SMP?
But this wasn't intentional. Its "under investigation".
Roberto Peña wrote:Is not this change a regression?
Yes. ;)

Best,
Matthias

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8184
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: Core 128 - PAE-Kernel wurde nicht installiert

Post by Arne.F » March 16th, 2019, 8:06 am

Run pakfire again. I have missed to copy the latest pae-kernel to the stable tree.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

User avatar
FischerM
Community Developer
Community Developer
Posts: 942
Joined: November 2nd, 2011, 12:28 pm

Re: Core 128 - PAE-Kernel wurde nicht installiert

Post by FischerM » March 16th, 2019, 8:35 am

Hi,

I see...

Done.

Rebooted.

Works => THANKS! ;)

Best,
Matthias

Post Reply