From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: PAE-Kernel for Core 132 missing...
Date: Thu, 13 Jun 2019 09:32:40 +0100 [thread overview]
Message-ID: <6BBFDAF7-41F5-4EF2-8784-1F61EDFE5D74@ipfire.org> (raw)
In-Reply-To: <387e996c-1226-4d7b-74c4-54f95de05215@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Do you have enough space on /boot?
Does pakfire show a pending update?
> On 13 Jun 2019, at 09:16, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> it seems, I'm the only one running 32bit?
>
> Because today I found by chance that after updating to Core 132, I'm
> running an SMP kernel. Again... ;-)
>
> root(a)ipfire: /boot # ls -l
> total 44816
> -rw-r--r-- 1 root root 162972 May 3 04:27 config-4.14.113-ipfire-pae
> -rw-r--r-- 1 root root 163354 May 23 08:02 config-4.14.121-ipfire
> drwxr-xr-x 5 root root 4096 Jun 9 08:54 grub
> -rw-r--r-- 1 root root 15165872 Jun 9 08:55
> initramfs-4.14.113-ipfire-pae.img
> -rw-r--r-- 1 root root 15049772 May 23 08:04 initramfs-4.14.121-ipfire.img
> drwx------ 2 root root 16384 Mar 9 2016 lost+found
> -rw-r--r-- 1 root root 2732812 May 3 04:27 System.map-4.14.113-ipfire-pae
> -rw-r--r-- 1 root root 2688754 May 23 08:02 System.map-4.14.121-ipfire
> -rw-r--r-- 1 root root 4971328 May 3 04:27 vmlinuz-4.14.113-ipfire-pae
> -rw-r--r-- 1 root root 4922912 May 23 08:02 vmlinuz-4.14.121-ipfire
> ***SNAP***
>
> Could someone please take a look?
>
> Best,
> Matthias
next prev parent reply other threads:[~2019-06-13 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 8:16 Matthias Fischer
2019-06-13 8:32 ` Michael Tremer [this message]
2019-06-13 8:55 ` Matthias Fischer
2019-06-13 10:05 ` Arne Fitzenreiter
2019-06-13 10:38 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6BBFDAF7-41F5-4EF2-8784-1F61EDFE5D74@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox