From: Mentalic <mentalic@cox.net>
To: development@lists.ipfire.org
Subject: RE: Core 134 test
Date: Wed, 03 Jul 2019 08:58:55 -0500 [thread overview]
Message-ID: <001201d531a7$76217020$62645060$@net> (raw)
In-Reply-To: <4c3de7e941379419bfbc9ae60f7ec24e@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
Right, I had updated my test box as soon as it was posted. No problems with
it.
Wayne
-----Original Message-----
From: Arne Fitzenreiter [mailto:Arne.Fitzenreiter(a)ipfire.org]
Sent: Wednesday, July 3, 2019 4:08 AM
To: Mentalic
Cc: 'IPFire: Development-List'
Subject: Re: Core 134 test
On 2019-06-27 01:43, Mentalic wrote:
> Core 134 Geoip had the same string of geoip boot errors as Core update
> 133 does. Tried the missing folder fix I found for core update 133
> but if fails on to fix core update 134. So somewhat different problem.
>
If you have installed core134 before the kernel update to 4.14.131 the
geoip modules was still missing and the old 4.14.121 modules from older
cores will not work with 4.14.129... so reinstall the update by setting
/opt/pakfire/db/core/mine back to 133
prev parent reply other threads:[~2019-07-03 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001d01d52c79$00f13390$02d39ab0$@net>
2019-07-03 9:08 ` Arne Fitzenreiter
2019-07-03 13:58 ` Mentalic [this message]
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='001201d531a7$76217020$62645060$@net' \
--to=mentalic@cox.net \
--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